#: hook.c:251
#, c-format
msgid "unhook: Can't do unhook * from within a hook."
-@@ -5378,3 +5382,45 @@
+@@ -2766,7 +2770,7 @@
+ msgid "Mailbox is corrupt!"
+ msgstr "Mailbox fehlerhaft!"
+
+-#: mbox.c:678
++#: mbox.c:678 compress.c:203 mbox.c:661
+ msgid "Mailbox was corrupted!"
+ msgstr "Mailbox wurde zerstört!"
+
+@@ -2774,10 +2778,11 @@
+ msgid "Fatal error! Could not reopen mailbox!"
+ msgstr "Fataler Fehler, konnte Mailbox nicht erneut öffnen!"
+
+-#: mbox.c:746
++#: mbox.c:746 compress.c:264 compress.c:246 compress.c:367 compress.c:443 mbox.c:706
+ msgid "Unable to lock mailbox!"
+ msgstr "Kann Mailbox nicht für exklusiven Zugriff sperren!"
+
++
+ #. this means ctx->changed or ctx->deleted was set, but no
+ #. * messages were found to be changed or deleted. This should
+ #. * never happen, is we presume it is a bug in mutt.
+@@ -5378,3 +5383,32 @@
#~ msgid "Authentication method is unknown."
#~ msgstr "Authentifizierungsmethode unbekannt."
+
-+#: compress.c:203 mbox.c:661
-+msgid "Mailbox was corrupted!"
-+msgstr "Mailbox wurde zerstört!"
-+
+#: compress.c:228 compress.c:253
+#, c-format
+msgid "Decompressing %s...\n"
+msgstr "Entpacke %s...\n"
+
-+#: compress.c:246 compress.c:367 compress.c:443 mbox.c:706
-+msgid "Unable to lock mailbox!"
-+msgstr "Kann Mailbox nicht für exklusiven Zugriff sperren!"
-+
-+#: compress.c:264
-+#, c-format
-+msgid "Error executing: %s : unable to open the mailbox!\n"
-+msgstr "Fehler beim Ausführen von %s : Kann die Mailbox nicht öffnen!\n"
-+
+#: compress.c:350 compress.c:377 compress.c:423 compress.c:454
+#, c-format
+msgid "Compressing %s...\n"
if (Context && Context->path)
{
strfcpy (tmp, Context->path, sizeof (tmp));
---- a/PATCHES
-+++ b/PATCHES
-@@ -1 +1,2 @@
-+patch-1.5.18.rr.compressed.1
- patch-1.5.13.cd.ifdef.2
FREE (&value);
return;
}
---- a/PATCHES
-+++ b/PATCHES
-@@ -1,2 +1,3 @@
-+patch-1.5.19.sidebar.20090522.txt
- patch-1.5.18.rr.compressed.1
- patch-1.5.13.cd.ifdef.2
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-
-
-VPATH = ..
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-EXTRA_PROGRAMS = mutt_dotlock$(EXEEXT) pgpring$(EXEEXT) \
- pgpewrap$(EXEEXT) mutt_md5$(EXEEXT)
-bin_PROGRAMS = mutt$(EXEEXT) mutt_dotlock$(EXEEXT) pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-subdir = .
-DIST_COMMON = README $(am__configure_deps) $(srcdir)/Makefile.am \
- $(srcdir)/Makefile.in $(srcdir)/config.h.in \
- $(srcdir)/hcachever.sh.in $(srcdir)/muttbug.sh.in \
- $(top_srcdir)/configure $(top_srcdir)/intl/Makefile.in \
- ABOUT-NLS ChangeLog INSTALL NEWS TODO config.guess config.sub \
- depcomp install-sh missing mkinstalldirs regex.c setenv.c \
- snprintf.c strcasecmp.c strdup.c strsep.c strtok_r.c
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
- configure.lineno config.status.lineno
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = config.h
-CONFIG_CLEAN_FILES = intl/Makefile hcachever.sh muttbug.sh
-am__installdirs = "$(DESTDIR)$(bindir)" "$(DESTDIR)$(bindir)"
-binPROGRAMS_INSTALL = $(INSTALL_PROGRAM)
-PROGRAMS = $(bin_PROGRAMS) $(noinst_PROGRAMS)
-am_mutt_OBJECTS = addrbook.$(OBJEXT) alias.$(OBJEXT) attach.$(OBJEXT) \
- base64.$(OBJEXT) browser.$(OBJEXT) buffy.$(OBJEXT) \
- color.$(OBJEXT) crypt.$(OBJEXT) cryptglue.$(OBJEXT) \
- compress.$(OBJEXT) commands.$(OBJEXT) complete.$(OBJEXT) \
- compose.$(OBJEXT) copy.$(OBJEXT) curs_lib.$(OBJEXT) \
- curs_main.$(OBJEXT) date.$(OBJEXT) edit.$(OBJEXT) \
- enter.$(OBJEXT) flags.$(OBJEXT) init.$(OBJEXT) \
- filter.$(OBJEXT) from.$(OBJEXT) getdomain.$(OBJEXT) \
- group.$(OBJEXT) handler.$(OBJEXT) hash.$(OBJEXT) \
- hdrline.$(OBJEXT) headers.$(OBJEXT) help.$(OBJEXT) \
- hook.$(OBJEXT) keymap.$(OBJEXT) main.$(OBJEXT) mbox.$(OBJEXT) \
- menu.$(OBJEXT) mh.$(OBJEXT) mx.$(OBJEXT) pager.$(OBJEXT) \
- parse.$(OBJEXT) pattern.$(OBJEXT) postpone.$(OBJEXT) \
- query.$(OBJEXT) recvattach.$(OBJEXT) recvcmd.$(OBJEXT) \
- rfc822.$(OBJEXT) rfc1524.$(OBJEXT) rfc2047.$(OBJEXT) \
- rfc2231.$(OBJEXT) rfc3676.$(OBJEXT) score.$(OBJEXT) \
- send.$(OBJEXT) sendlib.$(OBJEXT) signal.$(OBJEXT) \
- sort.$(OBJEXT) status.$(OBJEXT) system.$(OBJEXT) \
- thread.$(OBJEXT) charset.$(OBJEXT) history.$(OBJEXT) \
- lib.$(OBJEXT) muttlib.$(OBJEXT) editmsg.$(OBJEXT) \
- mbyte.$(OBJEXT) url.$(OBJEXT) ascii.$(OBJEXT) \
- crypt-mod.$(OBJEXT) sidebar.$(OBJEXT)
-am__objects_1 = patchlist.$(OBJEXT)
-nodist_mutt_OBJECTS = $(am__objects_1)
-mutt_OBJECTS = $(am_mutt_OBJECTS) $(nodist_mutt_OBJECTS)
-am__DEPENDENCIES_1 =
-am_mutt_dotlock_OBJECTS = mutt_dotlock.$(OBJEXT)
-mutt_dotlock_OBJECTS = $(am_mutt_dotlock_OBJECTS)
-am_mutt_md5_OBJECTS = mutt_md5-md5.$(OBJEXT)
-mutt_md5_OBJECTS = $(am_mutt_md5_OBJECTS)
-mutt_md5_DEPENDENCIES =
-mutt_md5_LINK = $(CCLD) $(mutt_md5_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) \
- $(LDFLAGS) -o $@
-pgpewrap_SOURCES = pgpewrap.c
-pgpewrap_OBJECTS = pgpewrap.$(OBJEXT)
-pgpewrap_LDADD = $(LDADD)
-pgpewrap_DEPENDENCIES =
-am_pgpring_OBJECTS = pgppubring.$(OBJEXT) pgplib.$(OBJEXT) \
- lib.$(OBJEXT) extlib.$(OBJEXT) sha1.$(OBJEXT) md5.$(OBJEXT) \
- pgppacket.$(OBJEXT) ascii.$(OBJEXT)
-pgpring_OBJECTS = $(am_pgpring_OBJECTS)
-binSCRIPT_INSTALL = $(INSTALL_SCRIPT)
-SCRIPTS = $(bin_SCRIPTS)
-DEFAULT_INCLUDES = -I. -I$(srcdir)
-depcomp = $(SHELL) $(top_srcdir)/depcomp
-am__depfiles_maybe = depfiles
-COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
- $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
-CCLD = $(CC)
-LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
-SOURCES = $(mutt_SOURCES) $(EXTRA_mutt_SOURCES) $(nodist_mutt_SOURCES) \
- $(mutt_dotlock_SOURCES) $(mutt_md5_SOURCES) pgpewrap.c \
- $(pgpring_SOURCES)
-DIST_SOURCES = $(mutt_SOURCES) $(EXTRA_mutt_SOURCES) \
- $(mutt_dotlock_SOURCES) $(mutt_md5_SOURCES) pgpewrap.c \
- $(pgpring_SOURCES)
-RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
- html-recursive info-recursive install-data-recursive \
- install-dvi-recursive install-exec-recursive \
- install-html-recursive install-info-recursive \
- install-pdf-recursive install-ps-recursive install-recursive \
- installcheck-recursive installdirs-recursive pdf-recursive \
- ps-recursive uninstall-recursive
-RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \
- distclean-recursive maintainer-clean-recursive
-ETAGS = etags
-CTAGS = ctags
-DIST_SUBDIRS = m4 po intl doc contrib imap
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-distdir = $(PACKAGE)-$(VERSION)
-top_distdir = $(distdir)
-am__remove_distdir = \
- { test ! -d $(distdir) \
- || { find $(distdir) -type d ! -perm -200 -exec chmod u+w {} ';' \
- && rm -fr $(distdir); }; }
-DIST_ARCHIVES = $(distdir).tar.gz
-GZIP_ENV = --best
-distuninstallcheck_listfiles = find . -type f -print
-distcleancheck_listfiles = find . -type f -print
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DPKGDATADIR=\"$(pkgdatadir)\" -DSYSCONFDIR=\"$(sysconfdir)\" \
- -DBINDIR=\"$(bindir)\" -DMUTTLOCALEDIR=\"$(datadir)/locale\" \
- -DHAVE_CONFIG_H=1
-
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/..
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ..
-sysconfdir = /etc
-target_alias =
-top_build_prefix =
-top_builddir = .
-top_srcdir = ..
-AUTOMAKE_OPTIONS = 1.6 foreign
-IMAP_SUBDIR = imap
-IMAP_INCLUDES = -I$(top_srcdir)/imap
-SUBDIRS = m4 po intl doc contrib $(IMAP_SUBDIR)
-bin_SCRIPTS = muttbug flea smime_keys
-BUILT_SOURCES = keymap_defs.h patchlist.c reldate.h hcversion.h
-mutt_SOURCES = \
- addrbook.c alias.c attach.c base64.c browser.c buffy.c color.c \
- crypt.c cryptglue.c compress.c \
- commands.c complete.c compose.c copy.c curs_lib.c curs_main.c date.c \
- edit.c enter.c flags.c init.c filter.c from.c \
- getdomain.c group.c \
- handler.c hash.c hdrline.c headers.c help.c hook.c keymap.c \
- main.c mbox.c menu.c mh.c mx.c pager.c parse.c pattern.c \
- postpone.c query.c recvattach.c recvcmd.c \
- rfc822.c rfc1524.c rfc2047.c rfc2231.c rfc3676.c \
- score.c send.c sendlib.c signal.c sort.c \
- status.c system.c thread.c charset.c history.c lib.c \
- muttlib.c editmsg.c mbyte.c \
- url.c ascii.c crypt-mod.c crypt-mod.h \
- sidebar.c
-
-nodist_mutt_SOURCES = $(BUILT_SOURCES)
-mutt_LDADD = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o $(LIBIMAP) $(MUTTLIBS) \
- $(INTLLIBS) $(LIBICONV) $(GPGME_LIBS)
-
-mutt_DEPENDENCIES = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o $(LIBIMAPDEPS) \
- $(INTLDEPS)
-
-AM_CPPFLAGS = -I. -I$(top_srcdir) $(IMAP_INCLUDES) $(GPGME_CFLAGS) -Iintl
-EXTRA_mutt_SOURCES = account.c bcache.c crypt-gpgme.c crypt-mod-pgp-classic.c \
- crypt-mod-pgp-gpgme.c crypt-mod-smime-classic.c \
- crypt-mod-smime-gpgme.c dotlock.c gnupgparse.c hcache.c md5.c \
- mutt_idna.c mutt_sasl.c mutt_socket.c mutt_ssl.c mutt_ssl_gnutls.c \
- mutt_tunnel.c pgp.c pgpinvoke.c pgpkey.c pgplib.c pgpmicalg.c \
- pgppacket.c pop.c pop_auth.c pop_lib.c remailer.c resize.c sha1.c \
- smime.c smtp.c utf8.c wcwidth.c \
- bcache.h browser.h hcache.h mbyte.h mutt_idna.h remailer.h url.h
-
-EXTRA_DIST = COPYRIGHT GPL OPS OPS.PGP OPS.CRYPT OPS.SMIME TODO UPDATING \
- configure account.h compress.h \
- attach.h buffy.h charset.h copy.h crypthash.h dotlock.h functions.h gen_defs \
- globals.h hash.h history.h init.h keymap.h mutt_crypt.h \
- mailbox.h mapping.h md5.h mime.h mutt.h mutt_curses.h mutt_menu.h \
- mutt_regex.h mutt_sasl.h mutt_socket.h mutt_ssl.h mutt_tunnel.h \
- mx.h pager.h pgp.h pop.h protos.h rfc1524.h rfc2047.h \
- rfc2231.h rfc822.h rfc3676.h sha1.h sort.h mime.types VERSION prepare \
- _regex.h OPS.MIX README.SECURITY remailer.c remailer.h browser.h \
- mbyte.h lib.h extlib.c pgpewrap.c smime_keys.pl pgplib.h \
- README.SSL smime.h \
- muttbug pgppacket.h depcomp ascii.h BEWARE PATCHES patchlist.sh \
- ChangeLog mkchangelog.sh mutt_idna.h \
- snprintf.c regex.c crypt-gpgme.h hcachever.sh.in
-
-EXTRA_SCRIPTS = smime_keys
-mutt_dotlock_SOURCES = mutt_dotlock.c
-mutt_dotlock_LDADD =
-mutt_dotlock_DEPENDENCIES =
-pgpring_SOURCES = pgppubring.c pgplib.c lib.c extlib.c sha1.c md5.c pgppacket.c ascii.c
-pgpring_LDADD = $(INTLLIBS)
-pgpring_DEPENDENCIES = $(INTLDEPS)
-mutt_md5_SOURCES = md5.c
-mutt_md5_CFLAGS = -DMD5UTIL
-mutt_md5_LDADD =
-noinst_PROGRAMS = $(MUTT_MD5)
-CLEANFILES = mutt_dotlock.c keymap_alldefs.h $(BUILT_SOURCES)
-DISTCLEANFILES = flea smime_keys
-ACLOCAL_AMFLAGS = -I m4
-LDADD =
-all: $(BUILT_SOURCES) config.h
- $(MAKE) $(AM_MAKEFLAGS) all-recursive
-
-.SUFFIXES:
-.SUFFIXES: .c .o .obj
-am--refresh:
- @:
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- echo ' cd $(srcdir) && $(AUTOMAKE) --foreign '; \
- cd $(srcdir) && $(AUTOMAKE) --foreign \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --foreign Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- echo ' $(SHELL) ./config.status'; \
- $(SHELL) ./config.status;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- $(SHELL) ./config.status --recheck
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(srcdir) && $(AUTOCONF)
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
-
-config.h: stamp-h1
- @if test ! -f $@; then \
- rm -f stamp-h1; \
- $(MAKE) $(AM_MAKEFLAGS) stamp-h1; \
- else :; fi
-
-stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status
- @rm -f stamp-h1
- cd $(top_builddir) && $(SHELL) ./config.status config.h
-$(srcdir)/config.h.in: # $(am__configure_deps)
- cd $(top_srcdir) && $(AUTOHEADER)
- rm -f stamp-h1
- touch $@
-
-distclean-hdr:
- -rm -f config.h stamp-h1
-intl/Makefile: $(top_builddir)/config.status $(top_srcdir)/intl/Makefile.in
- cd $(top_builddir) && $(SHELL) ./config.status $@
-hcachever.sh: $(top_builddir)/config.status $(srcdir)/hcachever.sh.in
- cd $(top_builddir) && $(SHELL) ./config.status $@
-muttbug.sh: $(top_builddir)/config.status $(srcdir)/muttbug.sh.in
- cd $(top_builddir) && $(SHELL) ./config.status $@
-install-binPROGRAMS: $(bin_PROGRAMS)
- @$(NORMAL_INSTALL)
- test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)"
- @list='$(bin_PROGRAMS)'; for p in $$list; do \
- p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \
- if test -f $$p \
- ; then \
- f=`echo "$$p1" | sed 's,^.*/,,;$(transform);s/$$/$(EXEEXT)/'`; \
- echo " $(INSTALL_PROGRAM_ENV) $(binPROGRAMS_INSTALL) '$$p' '$(DESTDIR)$(bindir)/$$f'"; \
- $(INSTALL_PROGRAM_ENV) $(binPROGRAMS_INSTALL) "$$p" "$(DESTDIR)$(bindir)/$$f" || exit 1; \
- else :; fi; \
- done
-
-uninstall-binPROGRAMS:
- @$(NORMAL_UNINSTALL)
- @list='$(bin_PROGRAMS)'; for p in $$list; do \
- f=`echo "$$p" | sed 's,^.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/'`; \
- echo " rm -f '$(DESTDIR)$(bindir)/$$f'"; \
- rm -f "$(DESTDIR)$(bindir)/$$f"; \
- done
-
-clean-binPROGRAMS:
- -test -z "$(bin_PROGRAMS)" || rm -f $(bin_PROGRAMS)
-
-clean-noinstPROGRAMS:
- -test -z "$(noinst_PROGRAMS)" || rm -f $(noinst_PROGRAMS)
-mutt$(EXEEXT): $(mutt_OBJECTS) $(mutt_DEPENDENCIES)
- @rm -f mutt$(EXEEXT)
- $(LINK) $(mutt_OBJECTS) $(mutt_LDADD) $(LIBS)
-mutt_dotlock$(EXEEXT): $(mutt_dotlock_OBJECTS) $(mutt_dotlock_DEPENDENCIES)
- @rm -f mutt_dotlock$(EXEEXT)
- $(LINK) $(mutt_dotlock_OBJECTS) $(mutt_dotlock_LDADD) $(LIBS)
-mutt_md5$(EXEEXT): $(mutt_md5_OBJECTS) $(mutt_md5_DEPENDENCIES)
- @rm -f mutt_md5$(EXEEXT)
- $(mutt_md5_LINK) $(mutt_md5_OBJECTS) $(mutt_md5_LDADD) $(LIBS)
-pgpewrap$(EXEEXT): $(pgpewrap_OBJECTS) $(pgpewrap_DEPENDENCIES)
- @rm -f pgpewrap$(EXEEXT)
- $(LINK) $(pgpewrap_OBJECTS) $(pgpewrap_LDADD) $(LIBS)
-pgpring$(EXEEXT): $(pgpring_OBJECTS) $(pgpring_DEPENDENCIES)
- @rm -f pgpring$(EXEEXT)
- $(LINK) $(pgpring_OBJECTS) $(pgpring_LDADD) $(LIBS)
-install-binSCRIPTS: $(bin_SCRIPTS)
- @$(NORMAL_INSTALL)
- test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)"
- @list='$(bin_SCRIPTS)'; for p in $$list; do \
- if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
- if test -f $$d$$p; then \
- f=`echo "$$p" | sed 's|^.*/||;$(transform)'`; \
- echo " $(binSCRIPT_INSTALL) '$$d$$p' '$(DESTDIR)$(bindir)/$$f'"; \
- $(binSCRIPT_INSTALL) "$$d$$p" "$(DESTDIR)$(bindir)/$$f"; \
- else :; fi; \
- done
-
-uninstall-binSCRIPTS:
- @$(NORMAL_UNINSTALL)
- @list='$(bin_SCRIPTS)'; for p in $$list; do \
- f=`echo "$$p" | sed 's|^.*/||;$(transform)'`; \
- echo " rm -f '$(DESTDIR)$(bindir)/$$f'"; \
- rm -f "$(DESTDIR)$(bindir)/$$f"; \
- done
-
-mostlyclean-compile:
- -rm -f *.$(OBJEXT)
-
-distclean-compile:
- -rm -f *.tab.c
-
-#include $(DEPDIR)/regex.Po
-#include $(DEPDIR)/setenv.Po
-#include $(DEPDIR)/snprintf.Po
-#include $(DEPDIR)/strcasecmp.Po
-#include $(DEPDIR)/strdup.Po
-#include $(DEPDIR)/strsep.Po
-#include $(DEPDIR)/strtok_r.Po
-#include ./$(DEPDIR)/account.Po
-#include ./$(DEPDIR)/addrbook.Po
-#include ./$(DEPDIR)/alias.Po
-#include ./$(DEPDIR)/ascii.Po
-#include ./$(DEPDIR)/attach.Po
-#include ./$(DEPDIR)/base64.Po
-#include ./$(DEPDIR)/bcache.Po
-#include ./$(DEPDIR)/browser.Po
-#include ./$(DEPDIR)/buffy.Po
-#include ./$(DEPDIR)/charset.Po
-#include ./$(DEPDIR)/color.Po
-#include ./$(DEPDIR)/commands.Po
-#include ./$(DEPDIR)/complete.Po
-#include ./$(DEPDIR)/compose.Po
-#include ./$(DEPDIR)/compress.Po
-#include ./$(DEPDIR)/copy.Po
-#include ./$(DEPDIR)/crypt-gpgme.Po
-#include ./$(DEPDIR)/crypt-mod-pgp-classic.Po
-#include ./$(DEPDIR)/crypt-mod-pgp-gpgme.Po
-#include ./$(DEPDIR)/crypt-mod-smime-classic.Po
-#include ./$(DEPDIR)/crypt-mod-smime-gpgme.Po
-#include ./$(DEPDIR)/crypt-mod.Po
-#include ./$(DEPDIR)/crypt.Po
-#include ./$(DEPDIR)/cryptglue.Po
-#include ./$(DEPDIR)/curs_lib.Po
-#include ./$(DEPDIR)/curs_main.Po
-#include ./$(DEPDIR)/date.Po
-#include ./$(DEPDIR)/dotlock.Po
-#include ./$(DEPDIR)/edit.Po
-#include ./$(DEPDIR)/editmsg.Po
-#include ./$(DEPDIR)/enter.Po
-#include ./$(DEPDIR)/extlib.Po
-#include ./$(DEPDIR)/filter.Po
-#include ./$(DEPDIR)/flags.Po
-#include ./$(DEPDIR)/from.Po
-#include ./$(DEPDIR)/getdomain.Po
-#include ./$(DEPDIR)/gnupgparse.Po
-#include ./$(DEPDIR)/group.Po
-#include ./$(DEPDIR)/handler.Po
-#include ./$(DEPDIR)/hash.Po
-#include ./$(DEPDIR)/hcache.Po
-#include ./$(DEPDIR)/hdrline.Po
-#include ./$(DEPDIR)/headers.Po
-#include ./$(DEPDIR)/help.Po
-#include ./$(DEPDIR)/history.Po
-#include ./$(DEPDIR)/hook.Po
-#include ./$(DEPDIR)/init.Po
-#include ./$(DEPDIR)/keymap.Po
-#include ./$(DEPDIR)/lib.Po
-#include ./$(DEPDIR)/main.Po
-#include ./$(DEPDIR)/mbox.Po
-#include ./$(DEPDIR)/mbyte.Po
-#include ./$(DEPDIR)/md5.Po
-#include ./$(DEPDIR)/menu.Po
-#include ./$(DEPDIR)/mh.Po
-#include ./$(DEPDIR)/mutt_dotlock.Po
-#include ./$(DEPDIR)/mutt_idna.Po
-#include ./$(DEPDIR)/mutt_md5-md5.Po
-#include ./$(DEPDIR)/mutt_sasl.Po
-#include ./$(DEPDIR)/mutt_socket.Po
-#include ./$(DEPDIR)/mutt_ssl.Po
-#include ./$(DEPDIR)/mutt_ssl_gnutls.Po
-#include ./$(DEPDIR)/mutt_tunnel.Po
-#include ./$(DEPDIR)/muttlib.Po
-#include ./$(DEPDIR)/mx.Po
-#include ./$(DEPDIR)/pager.Po
-#include ./$(DEPDIR)/parse.Po
-#include ./$(DEPDIR)/patchlist.Po
-#include ./$(DEPDIR)/pattern.Po
-#include ./$(DEPDIR)/pgp.Po
-#include ./$(DEPDIR)/pgpewrap.Po
-#include ./$(DEPDIR)/pgpinvoke.Po
-#include ./$(DEPDIR)/pgpkey.Po
-#include ./$(DEPDIR)/pgplib.Po
-#include ./$(DEPDIR)/pgpmicalg.Po
-#include ./$(DEPDIR)/pgppacket.Po
-#include ./$(DEPDIR)/pgppubring.Po
-#include ./$(DEPDIR)/pop.Po
-#include ./$(DEPDIR)/pop_auth.Po
-#include ./$(DEPDIR)/pop_lib.Po
-#include ./$(DEPDIR)/postpone.Po
-#include ./$(DEPDIR)/query.Po
-#include ./$(DEPDIR)/recvattach.Po
-#include ./$(DEPDIR)/recvcmd.Po
-#include ./$(DEPDIR)/remailer.Po
-#include ./$(DEPDIR)/resize.Po
-#include ./$(DEPDIR)/rfc1524.Po
-#include ./$(DEPDIR)/rfc2047.Po
-#include ./$(DEPDIR)/rfc2231.Po
-#include ./$(DEPDIR)/rfc3676.Po
-#include ./$(DEPDIR)/rfc822.Po
-#include ./$(DEPDIR)/score.Po
-#include ./$(DEPDIR)/send.Po
-#include ./$(DEPDIR)/sendlib.Po
-#include ./$(DEPDIR)/sha1.Po
-#include ./$(DEPDIR)/sidebar.Po
-#include ./$(DEPDIR)/signal.Po
-#include ./$(DEPDIR)/smime.Po
-#include ./$(DEPDIR)/smtp.Po
-#include ./$(DEPDIR)/sort.Po
-#include ./$(DEPDIR)/status.Po
-#include ./$(DEPDIR)/system.Po
-#include ./$(DEPDIR)/thread.Po
-#include ./$(DEPDIR)/url.Po
-#include ./$(DEPDIR)/utf8.Po
-#include ./$(DEPDIR)/wcwidth.Po
-
-.c.o:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c $<
-
-.c.obj:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'`
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c `$(CYGPATH_W) '$<'`
-
-mutt_md5-md5.o: md5.c
-# $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -MT mutt_md5-md5.o -MD -MP -MF $(DEPDIR)/mutt_md5-md5.Tpo -c -o mutt_md5-md5.o `test -f 'md5.c' || echo '$(srcdir)/'`md5.c
-# mv -f $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po
-# source='md5.c' object='mutt_md5-md5.o' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -c -o mutt_md5-md5.o `test -f 'md5.c' || echo '$(srcdir)/'`md5.c
-
-mutt_md5-md5.obj: md5.c
-# $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -MT mutt_md5-md5.obj -MD -MP -MF $(DEPDIR)/mutt_md5-md5.Tpo -c -o mutt_md5-md5.obj `if test -f 'md5.c'; then $(CYGPATH_W) 'md5.c'; else $(CYGPATH_W) '$(srcdir)/md5.c'; fi`
-# mv -f $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po
-# source='md5.c' object='mutt_md5-md5.obj' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -c -o mutt_md5-md5.obj `if test -f 'md5.c'; then $(CYGPATH_W) 'md5.c'; else $(CYGPATH_W) '$(srcdir)/md5.c'; fi`
-
-# This directory's subdirectories are mostly independent; you can cd
-# into them and run `make' without going through this Makefile.
-# To change the values of `make' variables: instead of editing Makefiles,
-# (1) if the variable is set in `config.status', edit `config.status'
-# (which will cause the Makefiles to be regenerated when you run `make');
-# (2) otherwise, pass the desired values on the `make' command line.
-$(RECURSIVE_TARGETS):
- @failcom='exit 1'; \
- for f in x $$MAKEFLAGS; do \
- case $$f in \
- *=* | --[!k]*);; \
- *k*) failcom='fail=yes';; \
- esac; \
- done; \
- dot_seen=no; \
- target=`echo $@ | sed s/-recursive//`; \
- list='$(SUBDIRS)'; for subdir in $$list; do \
- echo "Making $$target in $$subdir"; \
- if test "$$subdir" = "."; then \
- dot_seen=yes; \
- local_target="$$target-am"; \
- else \
- local_target="$$target"; \
- fi; \
- (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
- || eval $$failcom; \
- done; \
- if test "$$dot_seen" = "no"; then \
- $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
- fi; test -z "$$fail"
-
-$(RECURSIVE_CLEAN_TARGETS):
- @failcom='exit 1'; \
- for f in x $$MAKEFLAGS; do \
- case $$f in \
- *=* | --[!k]*);; \
- *k*) failcom='fail=yes';; \
- esac; \
- done; \
- dot_seen=no; \
- case "$@" in \
- distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
- *) list='$(SUBDIRS)' ;; \
- esac; \
- rev=''; for subdir in $$list; do \
- if test "$$subdir" = "."; then :; else \
- rev="$$subdir $$rev"; \
- fi; \
- done; \
- rev="$$rev ."; \
- target=`echo $@ | sed s/-recursive//`; \
- for subdir in $$rev; do \
- echo "Making $$target in $$subdir"; \
- if test "$$subdir" = "."; then \
- local_target="$$target-am"; \
- else \
- local_target="$$target"; \
- fi; \
- (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
- || eval $$failcom; \
- done && test -z "$$fail"
-tags-recursive:
- list='$(SUBDIRS)'; for subdir in $$list; do \
- test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
- done
-ctags-recursive:
- list='$(SUBDIRS)'; for subdir in $$list; do \
- test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
- done
-
-ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- mkid -fID $$unique
-tags: TAGS
-
-TAGS: tags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- here=`pwd`; \
- if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
- include_option=--etags-include; \
- empty_fix=.; \
- else \
- include_option=--include; \
- empty_fix=; \
- fi; \
- list='$(SUBDIRS)'; for subdir in $$list; do \
- if test "$$subdir" = .; then :; else \
- test ! -f $$subdir/TAGS || \
- tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
- fi; \
- done; \
- list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
- test -n "$$unique" || unique=$$empty_fix; \
- $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
- $$tags $$unique; \
- fi
-ctags: CTAGS
-CTAGS: ctags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- test -z "$(CTAGS_ARGS)$$tags$$unique" \
- || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
- $$tags $$unique
-
-GTAGS:
- here=`$(am__cd) $(top_builddir) && pwd` \
- && cd $(top_srcdir) \
- && gtags -i $(GTAGS_ARGS) $$here
-
-distclean-tags:
- -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
-distdir: $(DISTFILES)
- $(am__remove_distdir)
- test -d $(distdir) || mkdir $(distdir)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
- list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
- if test "$$subdir" = .; then :; else \
- test -d "$(distdir)/$$subdir" \
- || $(MKDIR_P) "$(distdir)/$$subdir" \
- || exit 1; \
- distdir=`$(am__cd) $(distdir) && pwd`; \
- top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
- (cd $$subdir && \
- $(MAKE) $(AM_MAKEFLAGS) \
- top_distdir="$$top_distdir" \
- distdir="$$distdir/$$subdir" \
- am__remove_distdir=: \
- am__skip_length_check=: \
- distdir) \
- || exit 1; \
- fi; \
- done
- -find $(distdir) -type d ! -perm -777 -exec chmod a+rwx {} \; -o \
- ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \
- ! -type d ! -perm -400 -exec chmod a+r {} \; -o \
- ! -type d ! -perm -444 -exec $(install_sh) -c -m a+r {} {} \; \
- || chmod -R a+r $(distdir)
-dist-gzip: distdir
- tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
- $(am__remove_distdir)
-
-dist-bzip2: distdir
- tardir=$(distdir) && $(am__tar) | bzip2 -9 -c >$(distdir).tar.bz2
- $(am__remove_distdir)
-
-dist-lzma: distdir
- tardir=$(distdir) && $(am__tar) | lzma -9 -c >$(distdir).tar.lzma
- $(am__remove_distdir)
-
-dist-tarZ: distdir
- tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z
- $(am__remove_distdir)
-
-dist-shar: distdir
- shar $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).shar.gz
- $(am__remove_distdir)
-
-dist-zip: distdir
- -rm -f $(distdir).zip
- zip -rq $(distdir).zip $(distdir)
- $(am__remove_distdir)
-
-dist dist-all: distdir
- tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
- $(am__remove_distdir)
-
-# This target untars the dist file and tries a VPATH configuration. Then
-# it guarantees that the distribution is self-contained by making another
-# tarfile.
-distcheck: dist
- case '$(DIST_ARCHIVES)' in \
- *.tar.gz*) \
- GZIP=$(GZIP_ENV) gunzip -c $(distdir).tar.gz | $(am__untar) ;;\
- *.tar.bz2*) \
- bunzip2 -c $(distdir).tar.bz2 | $(am__untar) ;;\
- *.tar.lzma*) \
- unlzma -c $(distdir).tar.lzma | $(am__untar) ;;\
- *.tar.Z*) \
- uncompress -c $(distdir).tar.Z | $(am__untar) ;;\
- *.shar.gz*) \
- GZIP=$(GZIP_ENV) gunzip -c $(distdir).shar.gz | unshar ;;\
- *.zip*) \
- unzip $(distdir).zip ;;\
- esac
- chmod -R a-w $(distdir); chmod a+w $(distdir)
- mkdir $(distdir)/_build
- mkdir $(distdir)/_inst
- chmod a-w $(distdir)
- dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \
- && dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \
- && cd $(distdir)/_build \
- && ../configure --srcdir=.. --prefix="$$dc_install_base" \
- $(DISTCHECK_CONFIGURE_FLAGS) \
- && $(MAKE) $(AM_MAKEFLAGS) \
- && $(MAKE) $(AM_MAKEFLAGS) dvi \
- && $(MAKE) $(AM_MAKEFLAGS) check \
- && $(MAKE) $(AM_MAKEFLAGS) install \
- && $(MAKE) $(AM_MAKEFLAGS) installcheck \
- && $(MAKE) $(AM_MAKEFLAGS) uninstall \
- && $(MAKE) $(AM_MAKEFLAGS) distuninstallcheck_dir="$$dc_install_base" \
- distuninstallcheck \
- && chmod -R a-w "$$dc_install_base" \
- && ({ \
- (cd ../.. && umask 077 && mkdir "$$dc_destdir") \
- && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" install \
- && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" uninstall \
- && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" \
- distuninstallcheck_dir="$$dc_destdir" distuninstallcheck; \
- } || { rm -rf "$$dc_destdir"; exit 1; }) \
- && rm -rf "$$dc_destdir" \
- && $(MAKE) $(AM_MAKEFLAGS) dist \
- && rm -rf $(DIST_ARCHIVES) \
- && $(MAKE) $(AM_MAKEFLAGS) distcleancheck
- $(am__remove_distdir)
- @(echo "$(distdir) archives ready for distribution: "; \
- list='$(DIST_ARCHIVES)'; for i in $$list; do echo $$i; done) | \
- sed -e 1h -e 1s/./=/g -e 1p -e 1x -e '$$p' -e '$$x'
-distuninstallcheck:
- @cd $(distuninstallcheck_dir) \
- && test `$(distuninstallcheck_listfiles) | wc -l` -le 1 \
- || { echo "ERROR: files left after uninstall:" ; \
- if test -n "$(DESTDIR)"; then \
- echo " (check DESTDIR support)"; \
- fi ; \
- $(distuninstallcheck_listfiles) ; \
- exit 1; } >&2
-distcleancheck: distclean
- @if test '$(srcdir)' = . ; then \
- echo "ERROR: distcleancheck can only run from a VPATH build" ; \
- exit 1 ; \
- fi
- @test `$(distcleancheck_listfiles) | wc -l` -eq 0 \
- || { echo "ERROR: files left in build directory after distclean:" ; \
- $(distcleancheck_listfiles) ; \
- exit 1; } >&2
-check-am: all-am
-check: $(BUILT_SOURCES)
- $(MAKE) $(AM_MAKEFLAGS) check-recursive
-all-am: Makefile $(PROGRAMS) $(SCRIPTS) config.h
-installdirs: installdirs-recursive
-installdirs-am:
- for dir in "$(DESTDIR)$(bindir)" "$(DESTDIR)$(bindir)"; do \
- test -z "$$dir" || $(MKDIR_P) "$$dir"; \
- done
-install: $(BUILT_SOURCES)
- $(MAKE) $(AM_MAKEFLAGS) install-recursive
-install-exec: install-exec-recursive
-install-data: install-data-recursive
-uninstall: uninstall-recursive
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-recursive
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
- -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES)
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
- -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
- -test -z "$(BUILT_SOURCES)" || rm -f $(BUILT_SOURCES)
-clean: clean-recursive
-
-clean-am: clean-binPROGRAMS clean-generic clean-noinstPROGRAMS \
- mostlyclean-am
-
-distclean: distclean-recursive
- -rm -f $(am__CONFIG_DISTCLEAN_FILES)
- -rm -rf $(DEPDIR) ./$(DEPDIR)
- -rm -f Makefile
-distclean-am: clean-am distclean-compile distclean-generic \
- distclean-hdr distclean-tags
-
-dvi: dvi-recursive
-
-dvi-am:
-
-html: html-recursive
-
-info: info-recursive
-
-info-am:
-
-install-data-am: install-data-local
-
-install-dvi: install-dvi-recursive
-
-install-exec-am: install-binPROGRAMS install-binSCRIPTS
- @$(NORMAL_INSTALL)
- $(MAKE) $(AM_MAKEFLAGS) install-exec-hook
-
-install-html: install-html-recursive
-
-install-info: install-info-recursive
-
-install-man:
-
-install-pdf: install-pdf-recursive
-
-install-ps: install-ps-recursive
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-recursive
- -rm -f $(am__CONFIG_DISTCLEAN_FILES)
- -rm -rf $(top_srcdir)/autom4te.cache
- -rm -rf $(DEPDIR) ./$(DEPDIR)
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-recursive
-
-mostlyclean-am: mostlyclean-compile mostlyclean-generic
-
-pdf: pdf-recursive
-
-pdf-am:
-
-ps: ps-recursive
-
-ps-am:
-
-uninstall-am: uninstall-binPROGRAMS uninstall-binSCRIPTS \
- uninstall-local
-
-.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
- install-exec-am install-strip
-
-.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
- all all-am am--refresh check check-am clean clean-binPROGRAMS \
- clean-generic clean-noinstPROGRAMS ctags ctags-recursive dist \
- dist-all dist-bzip2 dist-gzip dist-lzma dist-shar dist-tarZ \
- dist-zip distcheck distclean distclean-compile \
- distclean-generic distclean-hdr distclean-tags distcleancheck \
- distdir distuninstallcheck dvi dvi-am html html-am info \
- info-am install install-am install-binPROGRAMS \
- install-binSCRIPTS install-data install-data-am \
- install-data-local install-dvi install-dvi-am install-exec \
- install-exec-am install-exec-hook install-html install-html-am \
- install-info install-info-am install-man install-pdf \
- install-pdf-am install-ps install-ps-am install-strip \
- installcheck installcheck-am installdirs installdirs-am \
- maintainer-clean maintainer-clean-generic mostlyclean \
- mostlyclean-compile mostlyclean-generic pdf pdf-am ps ps-am \
- tags tags-recursive uninstall uninstall-am \
- uninstall-binPROGRAMS uninstall-binSCRIPTS uninstall-local
-
-
-mutt_dotlock.c: dotlock.c
- cp $(srcdir)/dotlock.c mutt_dotlock.c
-
-flea: muttbug.sh
- cp muttbug.sh flea
- chmod +x flea
-
-smime_keys: $(srcdir)/smime_keys.pl
- cp $(srcdir)/smime_keys.pl smime_keys
- chmod +x smime_keys
-
-keymap_defs.h: $(OPS) $(srcdir)/gen_defs
- $(srcdir)/gen_defs $(OPS) > keymap_defs.h
-
-keymap_alldefs.h: $(srcdir)/OPS $(srcdir)/OPS.PGP $(srcdir)/OPS.MIX $(srcdir)/OPS.CRYPT $(srcdir)/OPS.SMIME $(srcdir)/gen_defs
- rm -f $@
- $(srcdir)/gen_defs $(srcdir)/OPS $(srcdir)/OPS.PGP \
- $(srcdir)/OPS.MIX $(srcdir)/OPS.CRYPT $(srcdir)/OPS.SMIME \
- > keymap_alldefs.h
-
-reldate.h: $(srcdir)/ChangeLog
- echo 'const char *ReleaseDate = "'`head -n 1 $(srcdir)/ChangeLog | LC_ALL=C cut -d ' ' -f 1`'";' > reldate.h.tmp; \
- cmp -s reldate.h.tmp reldate.h || cp reldate.h.tmp reldate.h; \
- rm reldate.h.tmp
-
-hcversion.h: $(srcdir)/mutt.h $(srcdir)/rfc822.h hcachever.sh $(MUTT_MD5)
- ( echo '#include "config.h"'; echo '#include "mutt.h"'; ) \
- | $(CPP) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) - | sh ./hcachever.sh hcversion.h
-
-patchlist.c: $(srcdir)/PATCHES $(srcdir)/patchlist.sh
- $(srcdir)/patchlist.sh < $(srcdir)/PATCHES > patchlist.c
-
-install-exec-hook:
- if test -f $(DESTDIR)$(bindir)/mutt.dotlock && test -f $(DESTDIR)$(bindir)/mutt_dotlock ; then \
- rm -f $(DESTDIR)$(bindir)/mutt.dotlock ; \
- ln -sf $(DESTDIR)$(bindir)/mutt_dotlock $(DESTDIR)$(bindir)/mutt.dotlock ; \
- fi
- if test -f $(DESTDIR)$(bindir)/mutt_dotlock && test xmail != x ; then \
- chgrp mail $(DESTDIR)$(bindir)/mutt_dotlock && \
- chmod 2755 $(DESTDIR)$(bindir)/mutt_dotlock || \
- { echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
- fi
-
-install-data-local:
- $(srcdir)/mkinstalldirs $(DESTDIR)$(sysconfdir)
- $(INSTALL) -m 644 $(srcdir)/mime.types $(DESTDIR)$(sysconfdir)/mime.types.dist
- -if [ ! -f $(DESTDIR)$(sysconfdir)/mime.types ]; then \
- $(INSTALL) -m 644 $(srcdir)/mime.types $(DESTDIR)$(sysconfdir); \
- fi
-
-uninstall-local:
- for i in mime.types ; do \
- if cmp -s $(DESTDIR)$(sysconfdir)/$$i.dist $(DESTDIR)$(sysconfdir)/$$i ; then \
- rm $(DESTDIR)$(sysconfdir)/$$i ; \
- fi ; \
- rm $(DESTDIR)$(sysconfdir)/$${i}.dist ; \
- done
-
-pclean:
- cat /dev/null > $(top_srcdir)/PATCHES
-
-check-security:
- (cd $(top_srcdir) && ./check_sec.sh)
-
-commit:
- @echo "make commit is obsolete; use hg-commit"; false
-
-update-changelog:
- (cd $(top_srcdir); \
- sh ./mkchangelog.sh | cat - ChangeLog > ChangeLog.$$$$ && mv ChangeLog.$$$$ ChangeLog; \
- $${VISUAL:-vi} ChangeLog)
-
-mutt-dist:
- (cd $(srcdir) && ./build-release )
-
-update-doc:
- (cd doc && $(MAKE) update-doc)
-
-.PHONY: commit pclean check-security
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-/* config.h. Generated from config.h.in by configure. */
-/* config.h.in. Generated from configure.ac by autoheader. */
-
-/* Define if building universal (internal helper macro) */
-/* #undef AC_APPLE_UNIVERSAL_BUILD */
-
-/* Define to one of `_getb67', `GETB67', `getb67' for Cray-2 and Cray-YMP
- systems. This function is required for `alloca.c' support on those systems.
- */
-/* #undef CRAY_STACKSEG_END */
-
-/* Define if you want classic PGP support. */
-#define CRYPT_BACKEND_CLASSIC_PGP 1
-
-/* Define if you want clasic S/MIME support. */
-#define CRYPT_BACKEND_CLASSIC_SMIME 1
-
-/* Define if you use GPGME to support OpenPGP */
-#define CRYPT_BACKEND_GPGME 1
-
-/* Define to 1 if using `alloca.c'. */
-/* #undef C_ALLOCA */
-
-/* Define to enable debugging info. */
-#define DEBUG 1
-
-/* Define if you want to use an external dotlocking program. */
-#define DL_STANDALONE 1
-
-/* Define your domain name. */
-/* #undef DOMAIN */
-
-/* Define to 1 if translation of program messages to the user's native
- language is requested. */
-#define ENABLE_NLS 1
-
-/* Enable exact regeneration of email addresses as parsed? NOTE: this requires
- significant more memory when defined. */
-/* #undef EXACT_ADDRESS */
-
-/* program to use for shell commands */
-#define EXECSHELL "/bin/sh"
-
-/* Define to 1 if you have `alloca', as a function or macro. */
-#define HAVE_ALLOCA 1
-
-/* Define to 1 if you have <alloca.h> and it should be used (not on Ultrix).
- */
-#define HAVE_ALLOCA_H 1
-
-/* Define to 1 if you have the <argz.h> header file. */
-#define HAVE_ARGZ_H 1
-
-/* Define to 1 if you have the `bind_textdomain_codeset' function. */
-#define HAVE_BIND_TEXTDOMAIN_CODESET 1
-
-/* Define if you have bkgdset, as a function or macro. */
-#define HAVE_BKGDSET 1
-
-/* Define if you have the C99 integer types */
-#define HAVE_C99_INTTYPES 1
-
-/* Define if your curses library supports color. */
-#define HAVE_COLOR 1
-
-/* Define if you have curs_set, as a function or macro. */
-#define HAVE_CURS_SET 1
-
-/* Berkeley DB4 Support */
-/* #undef HAVE_DB4 */
-
-/* Define to 1 if you have the `dcgettext' function. */
-#define HAVE_DCGETTEXT 1
-
-/* Define to 1 if you have the declaration of `sys_siglist', and to 0 if you
- don't. */
-#define HAVE_DECL_SYS_SIGLIST 1
-
-/* Define to 1 if your system has the dirent::d_ino member */
-#define HAVE_DIRENT_D_INO 1
-
-/* Define to 1 if you have the `fchdir' function. */
-#define HAVE_FCHDIR 1
-
-/* Define to 1 if you have the `feof_unlocked' function. */
-#define HAVE_FEOF_UNLOCKED 1
-
-/* Define to 1 if you have the `fgetpos' function. */
-#define HAVE_FGETPOS 1
-
-/* Define to 1 if you have the `fgets_unlocked' function. */
-#define HAVE_FGETS_UNLOCKED 1
-
-/* Define to 1 if fseeko (and presumably ftello) exists and is declared. */
-#define HAVE_FSEEKO 1
-
-/* Define to 1 if you have the `ftruncate' function. */
-#define HAVE_FTRUNCATE 1
-
-/* GDBM Support */
-#define HAVE_GDBM 1
-
-/* Define to 1 if you have the `getaddrinfo' function. */
-#define HAVE_GETADDRINFO 1
-
-/* Define to 1 if you have the `getcwd' function. */
-#define HAVE_GETCWD 1
-
-/* Define to 1 if you have the `getegid' function. */
-#define HAVE_GETEGID 1
-
-/* Define to 1 if you have the `geteuid' function. */
-#define HAVE_GETEUID 1
-
-/* Define to 1 if you have the `getgid' function. */
-#define HAVE_GETGID 1
-
-/* Define to 1 if you have the <getopt.h> header file. */
-#define HAVE_GETOPT_H 1
-
-/* Define to 1 if you have the `getpagesize' function. */
-#define HAVE_GETPAGESIZE 1
-
-/* Define to 1 if you have the `getsid' function. */
-#define HAVE_GETSID 1
-
-/* Define if the GNU gettext() function is already present or preinstalled. */
-#define HAVE_GETTEXT 1
-
-/* Define to 1 if you have the `getuid' function. */
-#define HAVE_GETUID 1
-
-/* Define if GPGME supports PKA */
-#define HAVE_GPGME_PKA_TRUST 1
-
-/* Define if your GSSAPI implementation is Heimdal */
-/* #undef HAVE_HEIMDAL */
-
-/* Define if you have the iconv() function. */
-#define HAVE_ICONV 1
-
-/* Define to 1 if you have the <iconv.h> header file. */
-#define HAVE_ICONV_H 1
-
-/* Define if <iconv.h> defines iconv_t. */
-#define HAVE_ICONV_T_DEF 1
-
-/* Define to 1 if you have the `idna_to_ascii_8z' function. */
-#define HAVE_IDNA_TO_ASCII_8Z 1
-
-/* Define to 1 if you have the `idna_to_ascii_from_locale' function. */
-/* #undef HAVE_IDNA_TO_ASCII_FROM_LOCALE */
-
-/* Define to 1 if you have the `idna_to_ascii_from_utf8' function. */
-/* #undef HAVE_IDNA_TO_ASCII_FROM_UTF8 */
-
-/* Define to 1 if you have the `idna_to_ascii_lz' function. */
-#define HAVE_IDNA_TO_ASCII_LZ 1
-
-/* Define to 1 if you have the `idna_to_unicode_8z8z' function. */
-#define HAVE_IDNA_TO_UNICODE_8Z8Z 1
-
-/* Define to 1 if you have the `idna_to_unicode_utf8_from_utf8' function. */
-/* #undef HAVE_IDNA_TO_UNICODE_UTF8_FROM_UTF8 */
-
-/* Define to 1 if you have the <inttypes.h> header file. */
-#define HAVE_INTTYPES_H 1
-
-/* Define to 1 if you have the <ioctl.h> header file. */
-/* #undef HAVE_IOCTL_H */
-
-/* Define to 1 if you have the `iswalnum' function. */
-#define HAVE_ISWALNUM 1
-
-/* Define to 1 if you have the `iswalpha' function. */
-#define HAVE_ISWALPHA 1
-
-/* Define to 1 if you have the `iswcntrl' function. */
-#define HAVE_ISWCNTRL 1
-
-/* Define to 1 if you have the `iswdigit' function. */
-#define HAVE_ISWDIGIT 1
-
-/* Define to 1 if you have the `iswgraph' function. */
-#define HAVE_ISWGRAPH 1
-
-/* Define to 1 if you have the `iswlower' function. */
-#define HAVE_ISWLOWER 1
-
-/* Define to 1 if you have the `iswprint' function. */
-#define HAVE_ISWPRINT 1
-
-/* Define to 1 if you have the `iswpunct' function. */
-#define HAVE_ISWPUNCT 1
-
-/* Define to 1 if you have the `iswspace' function. */
-#define HAVE_ISWSPACE 1
-
-/* Define to 1 if you have the `iswupper' function. */
-#define HAVE_ISWUPPER 1
-
-/* Define to 1 if you have the `iswxdigit' function. */
-#define HAVE_ISWXDIGIT 1
-
-/* Define if you have <langinfo.h> and nl_langinfo(CODESET). */
-#define HAVE_LANGINFO_CODESET 1
-
-/* Define if you have <langinfo.h> and nl_langinfo(YESEXPR). */
-#define HAVE_LANGINFO_YESEXPR 1
-
-/* Define if your <locale.h> file defines LC_MESSAGES. */
-#define HAVE_LC_MESSAGES 1
-
-/* Define to 1 if you have the `idn' library */
-#define HAVE_LIBIDN 1
-
-/* Define to 1 if you have the `intl' library (-lintl). */
-/* #undef HAVE_LIBINTL */
-
-/* Define to 1 if you have the `nsl' library (-lnsl). */
-/* #undef HAVE_LIBNSL */
-
-/* Define to 1 if you have the `sasl2' library (-lsasl2). */
-#define HAVE_LIBSASL2 1
-
-/* Define to 1 if you have the `socket' library (-lsocket). */
-/* #undef HAVE_LIBSOCKET */
-
-/* Define to 1 if you have the `ssl' library (-lssl). */
-/* #undef HAVE_LIBSSL */
-
-/* Define to 1 if you have the `termlib' library (-ltermlib). */
-/* #undef HAVE_LIBTERMLIB */
-
-/* Define to 1 if you have the `x' library (-lx). */
-/* #undef HAVE_LIBX */
-
-/* Define to 1 if you have the <limits.h> header file. */
-#define HAVE_LIMITS_H 1
-
-/* Define to 1 if you have the <locale.h> header file. */
-#define HAVE_LOCALE_H 1
-
-/* Define to 1 if you have the <malloc.h> header file. */
-#define HAVE_MALLOC_H 1
-
-/* Define to 1 if you have the `memmove' function. */
-#define HAVE_MEMMOVE 1
-
-/* Define to 1 if you have the <memory.h> header file. */
-#define HAVE_MEMORY_H 1
-
-/* Define to 1 if you have the `mempcpy' function. */
-#define HAVE_MEMPCPY 1
-
-/* Define if you have meta, as a function or macro. */
-#define HAVE_META 1
-
-/* Define to 1 if you have a working `mmap' system call. */
-#define HAVE_MMAP 1
-
-/* Define to 1 if you have the `munmap' function. */
-#define HAVE_MUNMAP 1
-
-/* Define to 1 if you have the <ncursesw/ncurses.h> header file. */
-#define HAVE_NCURSESW_NCURSES_H 1
-
-/* Define to 1 if you have the <ncurses.h> header file. */
-/* #undef HAVE_NCURSES_H */
-
-/* Define to 1 if you have the <ncurses/ncurses.h> header file. */
-/* #undef HAVE_NCURSES_NCURSES_H */
-
-/* Define to 1 if you have the <nl_types.h> header file. */
-#define HAVE_NL_TYPES_H 1
-
-/* Define to 1 if you have the `putenv' function. */
-#define HAVE_PUTENV 1
-
-/* QDBM Support */
-/* #undef HAVE_QDBM */
-
-/* Define to 1 if you have the `RAND_egd' function. */
-/* #undef HAVE_RAND_EGD */
-
-/* Define to 1 if you have the `RAND_status' function. */
-/* #undef HAVE_RAND_STATUS */
-
-/* Define to 1 if you have the `regcomp' function. */
-#define HAVE_REGCOMP 1
-
-/* Define if you have resizeterm, as a function or macro. */
-#define HAVE_RESIZETERM 1
-
-/* Define to 1 if you have the `setegid' function. */
-#define HAVE_SETEGID 1
-
-/* Define to 1 if you have the `setenv' function. */
-#define HAVE_SETENV 1
-
-/* Define to 1 if you have the `setlocale' function. */
-#define HAVE_SETLOCALE 1
-
-/* Define to 1 if you have the `setrlimit' function. */
-#define HAVE_SETRLIMIT 1
-
-/* Define to 1 if you have a C99 compliant snprintf function. */
-#define HAVE_SNPRINTF 1
-
-/* Define to 1 if you have the `srand48' function. */
-#define HAVE_SRAND48 1
-
-/* Define if you have start_color, as a function or macro. */
-#define HAVE_START_COLOR 1
-
-/* Define to 1 if you have the <stdarg.h> header file. */
-#define HAVE_STDARG_H 1
-
-/* Define to 1 if you have the <stddef.h> header file. */
-#define HAVE_STDDEF_H 1
-
-/* Define to 1 if you have the <stdint.h> header file. */
-#define HAVE_STDINT_H 1
-
-/* Define to 1 if you have the <stdlib.h> header file. */
-#define HAVE_STDLIB_H 1
-
-/* Define to 1 if you have the `stpcpy' function. */
-#define HAVE_STPCPY 1
-
-/* Define to 1 if you have the `strcasecmp' function. */
-#define HAVE_STRCASECMP 1
-
-/* Define to 1 if you have the `strchr' function. */
-#define HAVE_STRCHR 1
-
-/* Define to 1 if you have the `strdup' function. */
-#define HAVE_STRDUP 1
-
-/* Define to 1 if you have the `strerror' function. */
-#define HAVE_STRERROR 1
-
-/* Define to 1 if you have the `strftime' function. */
-#define HAVE_STRFTIME 1
-
-/* Define to 1 if you have the <strings.h> header file. */
-#define HAVE_STRINGS_H 1
-
-/* Define to 1 if you have the <string.h> header file. */
-#define HAVE_STRING_H 1
-
-/* Define to 1 if you have the `strsep' function. */
-#define HAVE_STRSEP 1
-
-/* Define to 1 if you have the `strtok_r' function. */
-#define HAVE_STRTOK_R 1
-
-/* Define to 1 if you have the `strtoul' function. */
-#define HAVE_STRTOUL 1
-
-/* Define to 1 if you have the <sysexits.h> header file. */
-#define HAVE_SYSEXITS_H 1
-
-/* Define to 1 if you have the <sys/ioctl.h> header file. */
-#define HAVE_SYS_IOCTL_H 1
-
-/* Define to 1 if you have the <sys/param.h> header file. */
-#define HAVE_SYS_PARAM_H 1
-
-/* Define to 1 if you have the <sys/resource.h> header file. */
-#define HAVE_SYS_RESOURCE_H 1
-
-/* Define to 1 if you have the <sys/select.h> header file. */
-#define HAVE_SYS_SELECT_H 1
-
-/* Define to 1 if you have the <sys/stat.h> header file. */
-#define HAVE_SYS_STAT_H 1
-
-/* Define to 1 if you have the <sys/time.h> header file. */
-#define HAVE_SYS_TIME_H 1
-
-/* Define to 1 if you have the <sys/types.h> header file. */
-#define HAVE_SYS_TYPES_H 1
-
-/* Tokyo Cabinet Support */
-/* #undef HAVE_TC */
-
-/* Define to 1 if you have the `towlower' function. */
-#define HAVE_TOWLOWER 1
-
-/* Define to 1 if you have the `towupper' function. */
-#define HAVE_TOWUPPER 1
-
-/* Define to 1 if you have the `tsearch' function. */
-#define HAVE_TSEARCH 1
-
-/* Define if you have typeahead, as a function or macro. */
-#define HAVE_TYPEAHEAD 1
-
-/* Define to 1 if you have the <unistd.h> header file. */
-#define HAVE_UNISTD_H 1
-
-/* Define to 1 if you have the <unix.h> header file. */
-/* #undef HAVE_UNIX_H */
-
-/* Define if you have use_default_colors, as a function or macro. */
-#define HAVE_USE_DEFAULT_COLORS 1
-
-/* Define to 1 if you have the <villa.h> header file. */
-/* #undef HAVE_VILLA_H */
-
-/* Define to 1 if you have a C99 compliant vsnprintf function. */
-#define HAVE_VSNPRINTF 1
-
-/* Define to 1 if you have the <wchar.h> header file. */
-#define HAVE_WCHAR_H 1
-
-/* Define to 1 if you have the <wctype.h> header file. */
-#define HAVE_WCTYPE_H 1
-
-/* Define if you are using the system's wchar_t functions. */
-#define HAVE_WC_FUNCS 1
-
-/* Define to 1 if you have the `__argz_count' function. */
-#define HAVE___ARGZ_COUNT 1
-
-/* Define to 1 if you have the `__argz_next' function. */
-#define HAVE___ARGZ_NEXT 1
-
-/* Define to 1 if you have the `__argz_stringify' function. */
-#define HAVE___ARGZ_STRINGIFY 1
-
-/* Is mail spooled to the user's home directory? If defined, MAILPATH should
- be set to the filename of the spool mailbox relative the the home
- directory. use: configure --with-homespool=FILE */
-/* #undef HOMESPOOL */
-
-/* Define as const if the declaration of iconv() needs const. */
-#define ICONV_CONST
-
-/* Define as 1 if iconv() only converts exactly and we should treat all return
- values other than (size_t)(-1) as equivalent. */
-#define ICONV_NONTRANS 0
-
-/* Where to find ispell on your system. */
-/* #undef ISPELL */
-
-/* Define if the result of isprint() is unreliable. */
-/* #undef LOCALES_HACK */
-
-/* Where new mail is spooled. */
-#define MAILPATH "/var/mail"
-
-/* Define if you want complete documentation. */
-#define MAKEDOC_FULL 1
-
-/* Where to find mixmaster on your system. */
-#define MIXMASTER "mixmaster"
-
-/* Define if you have problems with mutt not detecting new/old mailboxes over
- NFS. Some NFS implementations incorrectly cache the attributes of small
- files. */
-/* #undef NFS_ATTRIBUTE_HACK */
-
-/* Name of package */
-#define PACKAGE "mutt"
-
-/* Define to the address where bug reports for this package should be sent. */
-#define PACKAGE_BUGREPORT ""
-
-/* Define to the full name of this package. */
-#define PACKAGE_NAME ""
-
-/* Define to the full name and version of this package. */
-#define PACKAGE_STRING ""
-
-/* Define to the one symbol short name of this package. */
-#define PACKAGE_TARNAME ""
-
-/* Define to the version of this package. */
-#define PACKAGE_VERSION ""
-
-/* Define to 1 if the C compiler supports function prototypes. */
-#define PROTOTYPES 1
-
-/* Define as the return type of signal handlers (`int' or `void'). */
-#define RETSIGTYPE void
-
-/* Where to find sendmail on your system. */
-#define SENDMAIL "/usr/sbin/sendmail"
-
-/* Some systems declare sig_atomic_t as volatile, some others -- no. This
- define will have value `sig_atomic_t' or `volatile sig_atomic_t'
- accordingly. */
-#define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-
-/* The size of `int', as computed by sizeof. */
-#define SIZEOF_INT 4
-
-/* The size of `long', as computed by sizeof. */
-#define SIZEOF_LONG 4
-
-/* The size of `long long', as computed by sizeof. */
-#define SIZEOF_LONG_LONG 8
-
-/* The size of `off_t', as computed by sizeof. */
-#define SIZEOF_OFF_T 8
-
-/* The size of `short', as computed by sizeof. */
-#define SIZEOF_SHORT 2
-
-/* If using the C implementation of alloca, define if you know the
- direction of stack growth for your system; otherwise it will be
- automatically deduced at runtime.
- STACK_DIRECTION > 0 => grows toward higher addresses
- STACK_DIRECTION < 0 => grows toward lower addresses
- STACK_DIRECTION = 0 => direction of growth unknown */
-/* #undef STACK_DIRECTION */
-
-/* Define to 1 if you have the ANSI C header files. */
-#define STDC_HEADERS 1
-
-/* Define to enable Sun mailtool attachments support. */
-/* #undef SUN_ATTACHMENT */
-
-/* Define to support compressed folders. */
-#define USE_COMPRESSED 1
-
-/* Define to use dotlocking for mailboxes. */
-#define USE_DOTLOCK 1
-
-/* Define to use fcntl() to lock folders. */
-#define USE_FCNTL 1
-
-/* Define to use flock() to lock mailboxes. */
-/* #undef USE_FLOCK */
-
-/* Define if you want to use the included regex.c. */
-/* #undef USE_GNU_REGEX */
-
-/* Define if you have GSSAPI libraries available */
-#define USE_GSS 1
-
-/* Enable header caching */
-#define USE_HCACHE 1
-
-/* Define if you want support for the IMAP protocol. */
-#define USE_IMAP 1
-
-/* Define if you want support for the POP3 protocol. */
-#define USE_POP 1
-
-/* Define if want to use the Cyrus SASL library for POP/IMAP authentication.
- */
-#define USE_SASL 1
-
-/* Define if mutt should run setgid "mail". */
-#define USE_SETGID 1
-
-/* Define if you compile with SLang instead of curses/ncurses. */
-/* #undef USE_SLANG_CURSES */
-
-/* Include internal SMTP relay support */
-#define USE_SMTP 1
-
-/* Include code for socket support. Set automatically if you enable POP3 or
- IMAP */
-#define USE_SOCKET 1
-
-/* Define if you want support for SSL. */
-#define USE_SSL 1
-
-/* Define if you want support for SSL via GNUTLS. */
-#define USE_SSL_GNUTLS 1
-
-/* Define if you want support for SSL via OpenSSL. */
-/* #undef USE_SSL_OPENSSL */
-
-/* Enable extensions on AIX 3, Interix. */
-#ifndef _ALL_SOURCE
-# define _ALL_SOURCE 1
-#endif
-/* Enable GNU extensions on systems that have them. */
-#ifndef _GNU_SOURCE
-# define _GNU_SOURCE 1
-#endif
-/* Enable threading extensions on Solaris. */
-#ifndef _POSIX_PTHREAD_SEMANTICS
-# define _POSIX_PTHREAD_SEMANTICS 1
-#endif
-/* Enable extensions on HP NonStop. */
-#ifndef _TANDEM_SOURCE
-# define _TANDEM_SOURCE 1
-#endif
-/* Enable general extensions on Solaris. */
-#ifndef __EXTENSIONS__
-# define __EXTENSIONS__ 1
-#endif
-
-
-/* Version number of package */
-#define VERSION "1.5.19"
-
-/* Define WORDS_BIGENDIAN to 1 if your processor stores words with the most
- significant byte first (like Motorola and SPARC, unlike Intel). */
-#if defined AC_APPLE_UNIVERSAL_BUILD
-# if defined __BIG_ENDIAN__
-# define WORDS_BIGENDIAN 1
-# endif
-#else
-# ifndef WORDS_BIGENDIAN
-/* # undef WORDS_BIGENDIAN */
-# endif
-#endif
-
-#ifndef HAVE_C99_INTTYPES
-# if SIZEOF_SHORT == 4
-typedef unsigned short uint32_t;
-# elif SIZEOF_INT == 4
-typedef unsigned int uint32_t;
-# elif SIZEOF_LONG == 4
-typedef unsigned long uint32_t;
-# endif
-# if SIZEOF_INT == 8
-typedef unsigned int uint64_t;
-# elif SIZEOF_LONG == 8
-typedef unsigned long uint64_t;
-# elif SIZEOF_LONG_LONG == 8
-typedef unsigned long long uint64_t;
-# endif
-#endif
-
-
-/* Number of bits in a file offset, on hosts where this is settable. */
-#define _FILE_OFFSET_BITS 64
-
-/* Define to 1 to make fseeko visible on some hosts (e.g. glibc 2.2). */
-/* #undef _LARGEFILE_SOURCE */
-
-/* Define for large files, on AIX-style hosts. */
-/* #undef _LARGE_FILES */
-
-/* Define to 1 if on MINIX. */
-/* #undef _MINIX */
-
-/* Define to 2 if the system does not provide POSIX.1 features except with
- this defined. */
-/* #undef _POSIX_1_SOURCE */
-
-/* Define to 1 if you need to in order for `stat' and other things to work. */
-/* #undef _POSIX_SOURCE */
-
-/* Define like PROTOTYPES; this can be used by system headers. */
-#define __PROTOTYPES 1
-
-/* Define to empty if `const' does not conform to ANSI C. */
-/* #undef const */
-
-/* Define to `__inline__' or `__inline' if that's what the C compiler
- calls it, or to nothing if 'inline' is not supported under any name. */
-#ifndef __cplusplus
-/* #undef inline */
-#endif
-
-/* Define to 'int' if system headers don't define. */
-/* #undef mbstate_t */
-
-/* Define to `long int' if <sys/types.h> does not define. */
-/* #undef off_t */
-
-/* Define to `int' if <sys/types.h> does not define. */
-/* #undef pid_t */
-
-/* Define to `int' if <sys/types.h> does not define. */
-/* #undef sig_atomic_t */
-
-/* Define to `unsigned int' if <sys/types.h> does not define. */
-/* #undef size_t */
-
-/* Define to 'int' if <sys/socket.h> doesn't have it. */
-/* #undef socklen_t */
-
-/* Define to `int' if <sys/types.h> does not define. */
-/* #undef ssize_t */
-
-/* define if va_copy is not available */
-/* #undef va_copy */
-
-/* Define to 'int' if system headers don't define. */
-/* #undef wchar_t */
-
-/* Define to 'int' if system headers don't define. */
-/* #undef wint_t */
-
-/* fseeko portability defines */
-#ifdef HAVE_FSEEKO
-# define LOFF_T off_t
-# if HAVE_C99_INTTYPES && HAVE_INTTYPES_H
-# if SIZEOF_OFF_T == 8
-# define OFF_T_FMT "%" PRId64
-# else
-# define OFF_T_FMT "%" PRId32
-# endif
-# else
-# if (SIZEOF_OFF_T == 8) && (SIZEOF_LONG == 4)
-# define OFF_T_FMT "%lld"
-# else
-# define OFF_T_FMT "%ld"
-# endif
-# endif
-#else
-# define LOFF_T long
-# define fseeko fseek
-# define ftello ftell
-# define OFF_T_FMT "%ld"
-#endif
-
-#include "config-debian.h"
+++ /dev/null
-This file contains any messages produced by compilers while
-running configure, to aid debugging if configure makes a mistake.
-
-It was created by configure, which was
-generated by GNU Autoconf 2.63. Invocation command line was
-
- $ ../configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-sharedir=/usr/share/mutt --with-docdir=/usr/share/doc --with-mailpath=/var/mail --disable-dependency-tracking --enable-compressed --enable-debug --enable-fcntl --enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-inodesort --enable-pop --with-curses --with-gnutls --with-gss --with-idn --with-mixmaster --with-sasl --without-qdbm --without-bdb --without-tokyocabinet --build i486-linux-gnu
-
-## --------- ##
-## Platform. ##
-## --------- ##
-
-hostname = debian
-uname -m = i686
-uname -r = 2.6.26-1-686
-uname -s = Linux
-uname -v = #1 SMP Sat Jan 10 18:29:31 UTC 2009
-
-/usr/bin/uname -p = unknown
-/bin/uname -X = unknown
-
-/bin/arch = unknown
-/usr/bin/arch -k = unknown
-/usr/convex/getsysinfo = unknown
-/usr/bin/hostinfo = unknown
-/bin/machine = unknown
-/usr/bin/oslevel = unknown
-/bin/universe = unknown
-
-PATH: /usr/sbin
-PATH: /usr/bin
-PATH: /sbin
-PATH: /bin
-PATH: /usr/bin/X11
-
-
-## ----------- ##
-## Core tests. ##
-## ----------- ##
-
-configure:2040: checking for a BSD-compatible install
-configure:2108: result: /usr/bin/install -c
-configure:2119: checking whether build environment is sane
-configure:2162: result: yes
-configure:2187: checking for a thread-safe mkdir -p
-configure:2226: result: /bin/mkdir -p
-configure:2239: checking for gawk
-configure:2255: found /usr/bin/gawk
-configure:2266: result: gawk
-configure:2277: checking whether make sets $(MAKE)
-configure:2299: result: yes
-configure:2483: checking whether to enable maintainer-specific portions of Makefiles
-configure:2492: result: no
-configure:2520: checking for style of include used by make
-configure:2548: result: GNU
-configure:2618: checking for gcc
-configure:2634: found /usr/bin/gcc
-configure:2645: result: gcc
-configure:2877: checking for C compiler version
-configure:2885: gcc --version >&5
-gcc (Debian 4.3.3-5) 4.3.3
-Copyright (C) 2008 Free Software Foundation, Inc.
-This is free software; see the source for copying conditions. There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
-configure:2889: $? = 0
-configure:2896: gcc -v >&5
-Using built-in specs.
-Target: i486-linux-gnu
-Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-5' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
-Thread model: posix
-gcc version 4.3.3 (Debian 4.3.3-5)
-configure:2900: $? = 0
-configure:2907: gcc -V >&5
-gcc: '-V' option must have argument
-configure:2911: $? = 1
-configure:2934: checking for C compiler default output file name
-configure:2956: gcc -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:2960: $? = 0
-configure:2998: result: a.out
-configure:3017: checking whether the C compiler works
-configure:3027: ./a.out
-configure:3031: $? = 0
-configure:3050: result: yes
-configure:3057: checking whether we are cross compiling
-configure:3059: result: no
-configure:3062: checking for suffix of executables
-configure:3069: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:3073: $? = 0
-configure:3099: result:
-configure:3105: checking for suffix of object files
-configure:3131: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:3135: $? = 0
-configure:3160: result: o
-configure:3164: checking whether we are using the GNU C compiler
-configure:3193: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:3200: $? = 0
-configure:3217: result: yes
-configure:3226: checking whether gcc accepts -g
-configure:3256: gcc -c -g -I/usr/include/qdbm conftest.c >&5
-configure:3263: $? = 0
-configure:3364: result: yes
-configure:3381: checking for gcc option to accept ISO C89
-configure:3455: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:3462: $? = 0
-configure:3485: result: none needed
-configure:3505: checking dependency style of gcc
-configure:3596: result: none
-configure:3617: checking how to run the C preprocessor
-configure:3657: gcc -E -I/usr/include/qdbm conftest.c
-configure:3664: $? = 0
-configure:3695: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
-configure:3702: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| /* end confdefs.h. */
-| #include <ac_nonexistent.h>
-configure:3735: result: gcc -E
-configure:3764: gcc -E -I/usr/include/qdbm conftest.c
-configure:3771: $? = 0
-configure:3802: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
-configure:3809: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| /* end confdefs.h. */
-| #include <ac_nonexistent.h>
-configure:3849: checking for grep that handles long lines and -e
-configure:3909: result: /bin/grep
-configure:3914: checking for egrep
-configure:3978: result: /bin/grep -E
-configure:3983: checking for ANSI C header files
-configure:4013: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4020: $? = 0
-configure:4119: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4123: $? = 0
-configure:4129: ./conftest
-configure:4133: $? = 0
-configure:4151: result: yes
-configure:4175: checking for sys/types.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for sys/stat.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for stdlib.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for string.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for memory.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for strings.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for inttypes.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for stdint.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for unistd.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4245: checking minix/config.h usability
-configure:4262: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:53:26: error: minix/config.h: No such file or directory
-configure:4269: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| #include <minix/config.h>
-configure:4283: result: no
-configure:4287: checking minix/config.h presence
-configure:4302: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:20:26: error: minix/config.h: No such file or directory
-configure:4309: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| /* end confdefs.h. */
-| #include <minix/config.h>
-configure:4323: result: no
-configure:4351: checking for minix/config.h
-configure:4358: result: no
-configure:4389: checking whether it is safe to define __EXTENSIONS__
-configure:4417: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4424: $? = 0
-configure:4439: result: yes
-configure:4472: checking build system type
-configure:4490: result: i486-pc-linux-gnu
-configure:4512: checking host system type
-configure:4527: result: i486-pc-linux-gnu
-configure:4550: checking for prefix
-configure:4557: result: /usr
-configure:4608: checking for gcc
-configure:4635: result: gcc
-configure:4867: checking for C compiler version
-configure:4875: gcc --version >&5
-gcc (Debian 4.3.3-5) 4.3.3
-Copyright (C) 2008 Free Software Foundation, Inc.
-This is free software; see the source for copying conditions. There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
-configure:4879: $? = 0
-configure:4886: gcc -v >&5
-Using built-in specs.
-Target: i486-linux-gnu
-Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-5' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
-Thread model: posix
-gcc version 4.3.3 (Debian 4.3.3-5)
-configure:4890: $? = 0
-configure:4897: gcc -V >&5
-gcc: '-V' option must have argument
-configure:4901: $? = 1
-configure:4904: checking whether we are using the GNU C compiler
-configure:4957: result: yes
-configure:4966: checking whether gcc accepts -g
-configure:5104: result: yes
-configure:5121: checking for gcc option to accept ISO C89
-configure:5225: result: none needed
-configure:5245: checking dependency style of gcc
-configure:5336: result: none
-configure:5351: checking for library containing strerror
-configure:5392: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:5399: $? = 0
-configure:5430: result: none required
-configure:5438: checking for function prototypes
-configure:5441: result: yes
-configure:5471: checking for string.h
-configure:5478: result: yes
-configure:5623: checking how to run the C preprocessor
-configure:5741: result: gcc -E
-configure:5770: gcc -E -I/usr/include/qdbm conftest.c
-configure:5777: $? = 0
-configure:5808: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:28:28: error: ac_nonexistent.h: No such file or directory
-configure:5815: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| /* end confdefs.h. */
-| #include <ac_nonexistent.h>
-configure:5854: checking whether make sets $(MAKE)
-configure:5876: result: yes
-configure:5899: checking for a BSD-compatible install
-configure:5967: result: /usr/bin/install -c
-configure:6021: checking for ranlib
-configure:6037: found /usr/bin/ranlib
-configure:6048: result: ranlib
-configure:6113: checking for ar
-configure:6129: found /usr/bin/ar
-configure:6140: result: ar
-configure:6163: checking for inline
-configure:6189: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:6196: $? = 0
-configure:6214: result: inline
-configure:6233: checking for an ANSI C-conforming const
-configure:6308: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:57: warning: 't' is used uninitialized in this function
-conftest.c:73: warning: 'b' may be used uninitialized in this function
-conftest.c:79: warning: 'cs[0]' is used uninitialized in this function
-configure:6315: $? = 0
-configure:6330: result: yes
-configure:6341: checking whether byte ordering is bigendian
-configure:6366: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:29: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'a'
-configure:6373: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| /* end confdefs.h. */
-| #ifndef __APPLE_CC__
-| not a universal capable compiler
-| #endif
-| typedef int dummy;
-|
-configure:6423: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:6430: $? = 0
-configure:6462: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:35: error: 'not' undeclared (first use in this function)
-conftest.c:35: error: (Each undeclared identifier is reported only once
-conftest.c:35: error: for each function it appears in.)
-conftest.c:35: error: expected ';' before 'big'
-configure:6469: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| /* end confdefs.h. */
-| #include <sys/types.h>
-| #include <sys/param.h>
-|
-| int
-| main ()
-| {
-| #if BYTE_ORDER != BIG_ENDIAN
-| not big endian
-| #endif
-|
-| ;
-| return 0;
-| }
-configure:6721: result: no
-configure:6754: checking for special C compiler options needed for large files
-configure:6849: result: no
-configure:6855: checking for _FILE_OFFSET_BITS value needed for large files
-configure:6890: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:34: warning: left shift count >= width of type
-conftest.c:34: warning: left shift count >= width of type
-conftest.c:36: error: size of array 'off_t_is_large' is negative
-configure:6897: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| /* end confdefs.h. */
-| #include <sys/types.h>
-| /* Check that off_t can represent 2**63 - 1 correctly.
-| We can't simply define LARGE_OFF_T to be 9223372036854775807,
-| since some C++ compilers masquerading as C compilers
-| incorrectly reject 9223372036854775807. */
-| #define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62))
-| int off_t_is_large[(LARGE_OFF_T % 2147483629 == 721
-| && LARGE_OFF_T % 2147483647 == 1)
-| ? 1 : -1];
-| int
-| main ()
-| {
-|
-| ;
-| return 0;
-| }
-configure:6941: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:6948: $? = 0
-configure:6966: result: 64
-configure:7103: checking for _LARGEFILE_SOURCE value needed for large files
-configure:7132: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:7139: $? = 0
-configure:7212: result: no
-configure:7239: checking size of off_t
-configure:7544: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:7548: $? = 0
-configure:7554: ./conftest
-configure:7558: $? = 0
-configure:7584: result: 8
-configure:7597: checking for dbx
-configure:7628: result: no
-configure:7638: checking for gdb
-configure:7656: found /usr/bin/gdb
-configure:7669: result: /usr/bin/gdb
-configure:7679: checking for sdb
-configure:7710: result: no
-configure:7759: checking for inttypes.h
-configure:7766: result: yes
-configure:7900: checking for uint32_t
-configure:7928: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:7935: $? = 0
-configure:7962: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:68: error: expected expression before ')' token
-configure:7969: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((uint32_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:7992: result: yes
-configure:8006: checking size of short
-configure:8311: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:8315: $? = 0
-configure:8321: ./conftest
-configure:8325: $? = 0
-configure:8351: result: 2
-configure:8365: checking size of int
-configure:8670: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:8674: $? = 0
-configure:8680: ./conftest
-configure:8684: $? = 0
-configure:8710: result: 4
-configure:8724: checking size of long
-configure:9029: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:9033: $? = 0
-configure:9039: ./conftest
-configure:9043: $? = 0
-configure:9069: result: 4
-configure:9083: checking size of long long
-configure:9388: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:9392: $? = 0
-configure:9398: ./conftest
-configure:9402: $? = 0
-configure:9428: result: 8
-configure:9442: checking for sendmail
-configure:9461: found /usr/sbin/sendmail
-configure:9474: result: /usr/sbin/sendmail
-configure:9490: checking whether to build with GPGME support
-configure:9502: result: yes
-configure:9517: checking for gpgme-config
-configure:9535: found /usr/bin/gpgme-config
-configure:9548: result: /usr/bin/gpgme-config
-configure:9576: checking for GPGME - version >= 1.0.0
-configure:9617: result: yes
-configure:9648: checking for GPGME - version >= 1.1.1
-configure:9689: result: yes
-configure:9716: checking for GPGME - version >= 1.0.0
-configure:9757: result: yes
-configure:9850: checking for ispell
-configure:9881: result: no
-configure:10172: checking for initscr
-configure:10228: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-/tmp/ccm6dj5h.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:78: undefined reference to `initscr'
-collect2: ld returned 1 exit status
-configure:10235: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| /* end confdefs.h. */
-| /* Define initscr to an innocuous variant, in case <limits.h> declares initscr.
-| For example, HP-UX 11i <limits.h> declares gettimeofday. */
-| #define initscr innocuous_initscr
-|
-| /* System header to define __stub macros and hopefully few prototypes,
-| which can conflict with char initscr (); below.
-| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
-| <limits.h> exists even on freestanding compilers. */
-|
-| #ifdef __STDC__
-| # include <limits.h>
-| #else
-| # include <assert.h>
-| #endif
-|
-| #undef initscr
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char initscr ();
-| /* The GNU C library defines this for functions which it implements
-| to always fail with ENOSYS. Some functions are actually named
-| something starting with __ and the normal name is an alias. */
-| #if defined __stub_initscr || defined __stub___initscr
-| choke me
-| #endif
-|
-| int
-| main ()
-| {
-| return initscr ();
-| ;
-| return 0;
-| }
-configure:10255: result: no
-configure:10265: checking for waddnwstr in -lncurses
-configure:10300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncurses >&5
-/tmp/ccEFgr2w.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:55: undefined reference to `waddnwstr'
-collect2: ld returned 1 exit status
-configure:10307: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| /* end confdefs.h. */
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char waddnwstr ();
-| int
-| main ()
-| {
-| return waddnwstr ();
-| ;
-| return 0;
-| }
-configure:10330: result: no
-configure:10265: checking for waddnwstr in -lncursesw
-configure:10300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncursesw >&5
-configure:10307: $? = 0
-configure:10330: result: yes
-configure:10340: checking for initscr in -lncursesw
-configure:10375: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncursesw >&5
-configure:10382: $? = 0
-configure:10405: result: yes
-configure:10429: checking ncursesw/ncurses.h usability
-configure:10446: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:10453: $? = 0
-configure:10467: result: yes
-configure:10471: checking ncursesw/ncurses.h presence
-configure:10486: gcc -E -I/usr/include/qdbm conftest.c
-configure:10493: $? = 0
-configure:10507: result: yes
-configure:10535: checking for ncursesw/ncurses.h
-configure:10544: result: yes
-configure:11615: checking for start_color declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:50: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for typeahead declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:51: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for bkgdset declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for curs_set declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:53: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for meta declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:54: error: conflicting types for 'meta'
-conftest.c:54: note: an argument type that has a default promotion can't match an empty parameter name list declaration
-/usr/include/ncursesw/ncurses.h:604: error: previous declaration of 'meta' was here
-configure:11650: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| /* end confdefs.h. */
-| #include <ncursesw/ncurses.h>
-| int
-| main ()
-| {
-| #ifndef meta
-| extern int meta();
-| #endif
-| ;
-| return 0;
-| }
-configure:11714: result: yes
-configure:11615: checking for use_default_colors declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:55: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for resizeterm declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:56: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11745: checking for ANSI C header files
-configure:11913: result: yes
-configure:11943: checking stdarg.h usability
-configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11967: $? = 0
-configure:11981: result: yes
-configure:11985: checking stdarg.h presence
-configure:12000: gcc -E -I/usr/include/qdbm conftest.c
-configure:12007: $? = 0
-configure:12021: result: yes
-configure:12049: checking for stdarg.h
-configure:12058: result: yes
-configure:11943: checking sys/ioctl.h usability
-configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11967: $? = 0
-configure:11981: result: yes
-configure:11985: checking sys/ioctl.h presence
-configure:12000: gcc -E -I/usr/include/qdbm conftest.c
-configure:12007: $? = 0
-configure:12021: result: yes
-configure:12049: checking for sys/ioctl.h
-configure:12058: result: yes
-configure:11943: checking ioctl.h usability
-configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:89:19: error: ioctl.h: No such file or directory
-configure:11967: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| #include <ioctl.h>
-configure:11981: result: no
-configure:11985: checking ioctl.h presence
-configure:12000: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:56:19: error: ioctl.h: No such file or directory
-configure:12007: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| /* end confdefs.h. */
-| #include <ioctl.h>
-configure:12021: result: no
-configure:12049: checking for ioctl.h
-configure:12058: result: no
-configure:11943: checking sysexits.h usability
-configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11967: $? = 0
-configure:11981: result: yes
-configure:11985: checking sysexits.h presence
-configure:12000: gcc -E -I/usr/include/qdbm conftest.c
-configure:12007: $? = 0
-configure:12021: result: yes
-configure:12049: checking for sysexits.h
-configure:12058: result: yes
-configure:12090: checking sys/time.h usability
-configure:12107: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12114: $? = 0
-configure:12128: result: yes
-configure:12132: checking sys/time.h presence
-configure:12147: gcc -E -I/usr/include/qdbm conftest.c
-configure:12154: $? = 0
-configure:12168: result: yes
-configure:12196: checking for sys/time.h
-configure:12205: result: yes
-configure:12090: checking sys/resource.h usability
-configure:12107: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12114: $? = 0
-configure:12128: result: yes
-configure:12132: checking sys/resource.h presence
-configure:12147: gcc -E -I/usr/include/qdbm conftest.c
-configure:12154: $? = 0
-configure:12168: result: yes
-configure:12196: checking for sys/resource.h
-configure:12205: result: yes
-configure:12236: checking unix.h usability
-configure:12253: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:92:18: error: unix.h: No such file or directory
-configure:12260: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| #include <unix.h>
-configure:12274: result: no
-configure:12278: checking unix.h presence
-configure:12293: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:59:18: error: unix.h: No such file or directory
-configure:12300: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| /* end confdefs.h. */
-| #include <unix.h>
-configure:12314: result: no
-configure:12342: checking for unix.h
-configure:12351: result: no
-configure:12372: checking for setrlimit
-configure:12428: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12435: $? = 0
-configure:12457: result: yes
-configure:12372: checking for getsid
-configure:12428: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12435: $? = 0
-configure:12457: result: yes
-configure:12470: checking return type of signal handlers
-configure:12498: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:67: error: void value not ignored as it ought to be
-configure:12505: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| /* end confdefs.h. */
-| #include <sys/types.h>
-| #include <signal.h>
-|
-| int
-| main ()
-| {
-| return *(signal (0, 0)) (0) == 1;
-| ;
-| return 0;
-| }
-configure:12520: result: void
-configure:12529: checking for sig_atomic_t in signal.h
-configure:12563: result: yes, non volatile
-configure:12696: checking whether sys_siglist is declared
-configure:12731: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12738: $? = 0
-configure:12753: result: yes
-configure:12773: checking for pid_t
-configure:12801: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12808: $? = 0
-configure:12835: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:100: error: expected expression before ')' token
-configure:12842: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((pid_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:12865: result: yes
-configure:12877: checking for ssize_t
-configure:12905: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12912: $? = 0
-configure:12939: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:100: error: expected expression before ')' token
-configure:12946: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((ssize_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:12969: result: yes
-configure:12990: checking for fgetpos
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:12990: checking for memmove
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:88: warning: conflicting types for built-in function 'memmove'
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:12990: checking for setegid
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:12990: checking for srand48
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:12990: checking for strerror
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:13096: checking for setenv
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13096: checking for strcasecmp
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:93: warning: conflicting types for built-in function 'strcasecmp'
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13096: checking for strdup
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:94: warning: conflicting types for built-in function 'strdup'
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13096: checking for strsep
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13096: checking for strtok_r
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13202: checking for getopt
-configure:13258: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13265: $? = 0
-configure:13285: result: yes
-configure:13305: checking getopt.h usability
-configure:13322: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13329: $? = 0
-configure:13343: result: yes
-configure:13347: checking getopt.h presence
-configure:13362: gcc -E -I/usr/include/qdbm conftest.c
-configure:13369: $? = 0
-configure:13383: result: yes
-configure:13411: checking for getopt.h
-configure:13420: result: yes
-configure:13438: checking for snprintf
-configure:13494: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:98: warning: conflicting types for built-in function 'snprintf'
-configure:13501: $? = 0
-configure:13521: result: yes
-configure:13529: checking for vsnprintf
-configure:13585: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:98: warning: conflicting types for built-in function 'vsnprintf'
-configure:13592: $? = 0
-configure:13612: result: yes
-configure:13621: checking whether your system's snprintf is C99 compliant
-configure:13651: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13655: $? = 0
-configure:13661: ./conftest
-configure:13665: $? = 0
-configure:13682: result: yes
-configure:13688: checking whether your system's vsnprintf is C99 compliant
-configure:13728: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13732: $? = 0
-configure:13738: ./conftest
-configure:13742: $? = 0
-configure:13759: result: yes
-configure:13787: checking for va_copy
-configure:13810: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:81: warning: 'ap2' is used uninitialized in this function
-configure:13817: $? = 0
-configure:13825: result: va_copy
-configure:13903: checking for ftruncate
-configure:13959: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13966: $? = 0
-configure:13988: result: yes
-configure:14081: checking for strftime
-configure:14137: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:101: warning: conflicting types for built-in function 'strftime'
-configure:14144: $? = 0
-configure:14166: result: yes
-configure:14259: checking for fchdir
-configure:14315: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14322: $? = 0
-configure:14344: result: yes
-configure:14368: checking for regcomp
-configure:14424: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14431: $? = 0
-configure:14453: result: yes
-configure:14471: checking whether your system's regexp library is completely broken
-configure:14496: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:84: warning: return type defaults to 'int'
-configure:14500: $? = 0
-configure:14506: ./conftest
-configure:14510: $? = 0
-configure:14527: result: no
-configure:14614: checking if /var/mail is world writable
-configure:14647: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14651: $? = 0
-configure:14657: ./conftest
-configure:14661: $? = 1
-configure: program exited with status 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| /* end confdefs.h. */
-| #include <sys/types.h>
-| #include <sys/stat.h>
-| #include <stdlib.h>
-|
-| int main (int argc, char **argv)
-| {
-| struct stat s;
-|
-| stat ("/var/mail", &s);
-| if (s.st_mode & S_IWOTH) exit (0);
-| exit (1);
-| }
-configure:14678: result: no
-configure:14690: checking if /var/mail is group writable
-configure:14723: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14727: $? = 0
-configure:14733: ./conftest
-configure:14737: $? = 0
-configure:14754: result: yes
-configure:14799: checking where to put the documentation
-configure:14809: result: /usr/share/doc
-configure:14923: checking sys/select.h usability
-configure:14940: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14947: $? = 0
-configure:14961: result: yes
-configure:14965: checking sys/select.h presence
-configure:14980: gcc -E -I/usr/include/qdbm conftest.c
-configure:14987: $? = 0
-configure:15001: result: yes
-configure:15029: checking for sys/select.h
-configure:15038: result: yes
-configure:15053: checking for socklen_t
-configure:15066: result: yes
-configure:15079: checking for gethostent
-configure:15135: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:15142: $? = 0
-configure:15162: result: yes
-configure:15244: checking for setsockopt
-configure:15300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:15307: $? = 0
-configure:15327: result: yes
-configure:15413: checking for getaddrinfo
-configure:15469: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:15476: $? = 0
-configure:15498: result: yes
-configure:15545: checking for krb5-config
-configure:15563: found /usr/bin/krb5-config
-configure:15576: result: /usr/bin/krb5-config
-configure:15833: checking GSSAPI implementation
-configure:15835: result: MIT
-configure:16370: checking for pkg-config
-configure:16388: found /usr/bin/pkg-config
-configure:16400: result: /usr/bin/pkg-config
-configure:16425: checking pkg-config is at least version 0.9.0
-configure:16428: result: yes
-configure:16439: checking for GNUTLS
-configure:16447: $PKG_CONFIG --exists --print-errors "gnutls"
-configure:16450: $? = 0
-configure:16465: $PKG_CONFIG --exists --print-errors "gnutls"
-configure:16468: $? = 0
-configure:16510: result: yes
-configure:16562: checking for sasl_client_init in -lsasl2
-configure:16597: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm conftest.c -lsasl2 >&5
-configure:16604: $? = 0
-configure:16625: result: yes
-configure:16704: checking whether struct dirent defines d_ino
-configure:16728: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm conftest.c >&5
-configure:16735: $? = 0
-configure:16761: result: yes
-configure:17433: checking for gdbm_open
-configure:17461: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c -lgdbm >&5
-configure:17468: $? = 0
-configure:17489: result: yes
-configure:17650: checking for off_t
-configure:17678: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:17685: $? = 0
-configure:17712: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:139: error: expected expression before ')' token
-configure:17719: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((off_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:17742: result: yes
-configure:17754: checking for size_t
-configure:17782: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:17789: $? = 0
-configure:17816: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:139: error: expected expression before ')' token
-configure:17823: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((size_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:17846: result: yes
-configure:17860: checking for working alloca.h
-configure:17887: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:17894: $? = 0
-configure:17914: result: yes
-configure:17924: checking for alloca
-configure:17971: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:17978: $? = 0
-configure:17998: result: yes
-configure:18241: checking for stdlib.h
-configure:18248: result: yes
-configure:18241: checking for unistd.h
-configure:18248: result: yes
-configure:18386: checking for getpagesize
-configure:18442: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18449: $? = 0
-configure:18471: result: yes
-configure:18483: checking for working mmap
-configure:18630: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18634: $? = 0
-configure:18640: ./conftest
-configure:18644: $? = 0
-configure:18661: result: yes
-configure:18673: checking whether we are using the GNU C Library 2.1 or newer
-configure:18704: result: yes
-configure:18737: checking argz.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking argz.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for argz.h
-configure:18852: result: yes
-configure:18737: checking limits.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking limits.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for limits.h
-configure:18852: result: yes
-configure:18737: checking locale.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking locale.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for locale.h
-configure:18852: result: yes
-configure:18737: checking nl_types.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking nl_types.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for nl_types.h
-configure:18852: result: yes
-configure:18737: checking malloc.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking malloc.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for malloc.h
-configure:18852: result: yes
-configure:18737: checking stddef.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking stddef.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for stddef.h
-configure:18852: result: yes
-configure:18726: checking for stdlib.h
-configure:18733: result: yes
-configure:18726: checking for string.h
-configure:18733: result: yes
-configure:18726: checking for unistd.h
-configure:18733: result: yes
-configure:18737: checking sys/param.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking sys/param.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for sys/param.h
-configure:18852: result: yes
-configure:18893: checking for feof_unlocked
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for fgets_unlocked
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for getcwd
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for getegid
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for geteuid
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for getgid
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for getuid
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for mempcpy
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c:149: warning: conflicting types for built-in function 'mempcpy'
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for munmap
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for putenv
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for setenv
-configure:18978: result: yes
-configure:18893: checking for setlocale
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for stpcpy
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c:154: warning: conflicting types for built-in function 'stpcpy'
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for strchr
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c:155: warning: conflicting types for built-in function 'strchr'
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for strcasecmp
-configure:18978: result: yes
-configure:18893: checking for strdup
-configure:18978: result: yes
-configure:18893: checking for strtoul
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for tsearch
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for __argz_count
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for __argz_stringify
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for __argz_next
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:19005: checking for iconv
-configure:19037: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:19044: $? = 0
-configure:19121: result: yes
-configure:19129: checking for iconv declaration
-configure:19168: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:19175: $? = 0
-configure:19194: result:
- extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
-configure:19210: checking for nl_langinfo and CODESET
-configure:19236: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:146: warning: unused variable 'cs'
-configure:19243: $? = 0
-configure:19264: result: yes
-configure:19275: checking for LC_MESSAGES
-configure:19301: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:19308: $? = 0
-configure:19328: result: yes
-configure:19338: checking whether NLS is requested
-configure:19347: result: yes
-configure:19361: checking whether included gettext is requested
-configure:19371: result: no
-configure:19391: checking libintl.h usability
-configure:19408: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:19415: $? = 0
-configure:19429: result: yes
-configure:19433: checking libintl.h presence
-configure:19448: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:19455: $? = 0
-configure:19469: result: yes
-configure:19497: checking for libintl.h
-configure:19504: result: yes
-configure:19509: checking for GNU gettext in libc
-configure:19537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:19544: $? = 0
-configure:19564: result: yes
-configure:19649: checking for dcgettext
-configure:19705: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c:169: warning: conflicting types for built-in function 'dcgettext'
-configure:19712: $? = 0
-configure:19734: result: yes
-configure:19750: checking for msgfmt
-configure:19777: result: /usr/bin/msgfmt
-configure:19786: checking for gmsgfmt
-configure:19817: result: /usr/bin/msgfmt
-configure:19828: checking for xgettext
-configure:19855: result: /usr/bin/xgettext
-configure:20032: checking for bison
-configure:20048: found /usr/bin/bison
-configure:20059: result: bison
-configure:20073: checking version of bison
-configure:20082: result: 2.4.1, ok
-configure:20121: checking for catalogs to be installed
-configure:20141: result: de eu ru it es uk fr pl nl cs id sk ko el zh_TW zh_CN pt_BR eo gl sv da lt tr ja hu et ca bg ga
-configure:20185: checking iconv.h usability
-configure:20202: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:20209: $? = 0
-configure:20223: result: yes
-configure:20227: checking iconv.h presence
-configure:20242: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:20249: $? = 0
-configure:20263: result: yes
-configure:20291: checking for iconv.h
-configure:20300: result: yes
-configure:20310: checking whether iconv.h defines iconv_t
-configure:20323: result: yes
-configure:20341: checking whether this iconv is good enough
-configure:20379: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:20383: $? = 0
-configure:20389: ./conftest
-configure:20393: $? = 0
-configure:20411: result: yes
-configure:20419: checking whether iconv is non-transcribing
-configure:20458: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:162: warning: passing argument 2 of 'iconv' from incompatible pointer type
-configure:20462: $? = 0
-configure:20468: ./conftest
-configure:20472: $? = 0
-configure:20490: result: no
-configure:20519: checking for bind_textdomain_codeset
-configure:20575: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c >&5
-configure:20582: $? = 0
-configure:20604: result: yes
-configure:20647: checking for library containing stringprep_check_version
-configure:20688: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c >&5
-/tmp/ccCU8kre.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:162: undefined reference to `stringprep_check_version'
-collect2: ld returned 1 exit status
-configure:20695: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| #define HAVE_ALLOCA_H 1
-| #define HAVE_ALLOCA 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_GETPAGESIZE 1
-| #define HAVE_MMAP 1
-| #define HAVE_ARGZ_H 1
-| #define HAVE_LIMITS_H 1
-| #define HAVE_LOCALE_H 1
-| #define HAVE_NL_TYPES_H 1
-| #define HAVE_MALLOC_H 1
-| #define HAVE_STDDEF_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_SYS_PARAM_H 1
-| #define HAVE_FEOF_UNLOCKED 1
-| #define HAVE_FGETS_UNLOCKED 1
-| #define HAVE_GETCWD 1
-| #define HAVE_GETEGID 1
-| #define HAVE_GETEUID 1
-| #define HAVE_GETGID 1
-| #define HAVE_GETUID 1
-| #define HAVE_MEMPCPY 1
-| #define HAVE_MUNMAP 1
-| #define HAVE_PUTENV 1
-| #define HAVE_SETENV 1
-| #define HAVE_SETLOCALE 1
-| #define HAVE_STPCPY 1
-| #define HAVE_STRCHR 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRTOUL 1
-| #define HAVE_TSEARCH 1
-| #define HAVE___ARGZ_COUNT 1
-| #define HAVE___ARGZ_STRINGIFY 1
-| #define HAVE___ARGZ_NEXT 1
-| #define HAVE_ICONV 1
-| #define ICONV_CONST
-| #define HAVE_LANGINFO_CODESET 1
-| #define HAVE_LC_MESSAGES 1
-| #define ENABLE_NLS 1
-| #define HAVE_GETTEXT 1
-| #define HAVE_DCGETTEXT 1
-| #define HAVE_ICONV_H 1
-| #define HAVE_ICONV_T_DEF 1
-| #define ICONV_NONTRANS 0
-| #define HAVE_BIND_TEXTDOMAIN_CODESET 1
-| /* end confdefs.h. */
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char stringprep_check_version ();
-| int
-| main ()
-| {
-| return stringprep_check_version ();
-| ;
-| return 0;
-| }
-configure:20688: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-configure:20695: $? = 0
-configure:20726: result: -lidn
-configure:20746: checking for idna_to_unicode_utf8_from_utf8
-configure:20802: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-/tmp/ccstCW6K.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:186: undefined reference to `idna_to_unicode_utf8_from_utf8'
-collect2: ld returned 1 exit status
-configure:20809: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| #define HAVE_ALLOCA_H 1
-| #define HAVE_ALLOCA 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_GETPAGESIZE 1
-| #define HAVE_MMAP 1
-| #define HAVE_ARGZ_H 1
-| #define HAVE_LIMITS_H 1
-| #define HAVE_LOCALE_H 1
-| #define HAVE_NL_TYPES_H 1
-| #define HAVE_MALLOC_H 1
-| #define HAVE_STDDEF_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_SYS_PARAM_H 1
-| #define HAVE_FEOF_UNLOCKED 1
-| #define HAVE_FGETS_UNLOCKED 1
-| #define HAVE_GETCWD 1
-| #define HAVE_GETEGID 1
-| #define HAVE_GETEUID 1
-| #define HAVE_GETGID 1
-| #define HAVE_GETUID 1
-| #define HAVE_MEMPCPY 1
-| #define HAVE_MUNMAP 1
-| #define HAVE_PUTENV 1
-| #define HAVE_SETENV 1
-| #define HAVE_SETLOCALE 1
-| #define HAVE_STPCPY 1
-| #define HAVE_STRCHR 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRTOUL 1
-| #define HAVE_TSEARCH 1
-| #define HAVE___ARGZ_COUNT 1
-| #define HAVE___ARGZ_STRINGIFY 1
-| #define HAVE___ARGZ_NEXT 1
-| #define HAVE_ICONV 1
-| #define ICONV_CONST
-| #define HAVE_LANGINFO_CODESET 1
-| #define HAVE_LC_MESSAGES 1
-| #define ENABLE_NLS 1
-| #define HAVE_GETTEXT 1
-| #define HAVE_DCGETTEXT 1
-| #define HAVE_ICONV_H 1
-| #define HAVE_ICONV_T_DEF 1
-| #define ICONV_NONTRANS 0
-| #define HAVE_BIND_TEXTDOMAIN_CODESET 1
-| #define HAVE_LIBIDN 1
-| /* end confdefs.h. */
-| /* Define idna_to_unicode_utf8_from_utf8 to an innocuous variant, in case <limits.h> declares idna_to_unicode_utf8_from_utf8.
-| For example, HP-UX 11i <limits.h> declares gettimeofday. */
-| #define idna_to_unicode_utf8_from_utf8 innocuous_idna_to_unicode_utf8_from_utf8
-|
-| /* System header to define __stub macros and hopefully few prototypes,
-| which can conflict with char idna_to_unicode_utf8_from_utf8 (); below.
-| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
-| <limits.h> exists even on freestanding compilers. */
-|
-| #ifdef __STDC__
-| # include <limits.h>
-| #else
-| # include <assert.h>
-| #endif
-|
-| #undef idna_to_unicode_utf8_from_utf8
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char idna_to_unicode_utf8_from_utf8 ();
-| /* The GNU C library defines this for functions which it implements
-| to always fail with ENOSYS. Some functions are actually named
-| something starting with __ and the normal name is an alias. */
-| #if defined __stub_idna_to_unicode_utf8_from_utf8 || defined __stub___idna_to_unicode_utf8_from_utf8
-| choke me
-| #endif
-|
-| int
-| main ()
-| {
-| return idna_to_unicode_utf8_from_utf8 ();
-| ;
-| return 0;
-| }
-configure:20831: result: no
-configure:20746: checking for idna_to_unicode_8z8z
-configure:20802: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-configure:20809: $? = 0
-configure:20831: result: yes
-configure:20848: checking for idna_to_ascii_from_utf8
-configure:20904: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-/tmp/ccWw2b3k.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:187: undefined reference to `idna_to_ascii_from_utf8'
-collect2: ld returned 1 exit status
-configure:20911: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| #define HAVE_ALLOCA_H 1
-| #define HAVE_ALLOCA 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_GETPAGESIZE 1
-| #define HAVE_MMAP 1
-| #define HAVE_ARGZ_H 1
-| #define HAVE_LIMITS_H 1
-| #define HAVE_LOCALE_H 1
-| #define HAVE_NL_TYPES_H 1
-| #define HAVE_MALLOC_H 1
-| #define HAVE_STDDEF_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_SYS_PARAM_H 1
-| #define HAVE_FEOF_UNLOCKED 1
-| #define HAVE_FGETS_UNLOCKED 1
-| #define HAVE_GETCWD 1
-| #define HAVE_GETEGID 1
-| #define HAVE_GETEUID 1
-| #define HAVE_GETGID 1
-| #define HAVE_GETUID 1
-| #define HAVE_MEMPCPY 1
-| #define HAVE_MUNMAP 1
-| #define HAVE_PUTENV 1
-| #define HAVE_SETENV 1
-| #define HAVE_SETLOCALE 1
-| #define HAVE_STPCPY 1
-| #define HAVE_STRCHR 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRTOUL 1
-| #define HAVE_TSEARCH 1
-| #define HAVE___ARGZ_COUNT 1
-| #define HAVE___ARGZ_STRINGIFY 1
-| #define HAVE___ARGZ_NEXT 1
-| #define HAVE_ICONV 1
-| #define ICONV_CONST
-| #define HAVE_LANGINFO_CODESET 1
-| #define HAVE_LC_MESSAGES 1
-| #define ENABLE_NLS 1
-| #define HAVE_GETTEXT 1
-| #define HAVE_DCGETTEXT 1
-| #define HAVE_ICONV_H 1
-| #define HAVE_ICONV_T_DEF 1
-| #define ICONV_NONTRANS 0
-| #define HAVE_BIND_TEXTDOMAIN_CODESET 1
-| #define HAVE_LIBIDN 1
-| #define HAVE_IDNA_TO_UNICODE_8Z8Z 1
-| /* end confdefs.h. */
-| /* Define idna_to_ascii_from_utf8 to an innocuous variant, in case <limits.h> declares idna_to_ascii_from_utf8.
-| For example, HP-UX 11i <limits.h> declares gettimeofday. */
-| #define idna_to_ascii_from_utf8 innocuous_idna_to_ascii_from_utf8
-|
-| /* System header to define __stub macros and hopefully few prototypes,
-| which can conflict with char idna_to_ascii_from_utf8 (); below.
-| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
-| <limits.h> exists even on freestanding compilers. */
-|
-| #ifdef __STDC__
-| # include <limits.h>
-| #else
-| # include <assert.h>
-| #endif
-|
-| #undef idna_to_ascii_from_utf8
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char idna_to_ascii_from_utf8 ();
-| /* The GNU C library defines this for functions which it implements
-| to always fail with ENOSYS. Some functions are actually named
-| something starting with __ and the normal name is an alias. */
-| #if defined __stub_idna_to_ascii_from_utf8 || defined __stub___idna_to_ascii_from_utf8
-| choke me
-| #endif
-|
-| int
-| main ()
-| {
-| return idna_to_ascii_from_utf8 ();
-| ;
-| return 0;
-| }
-configure:20933: result: no
-configure:20848: checking for idna_to_ascii_8z
-configure:20904: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-configure:20911: $? = 0
-configure:20933: result: yes
-configure:20950: checking for idna_to_ascii_lz
-configure:21006: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-configure:21013: $? = 0
-configure:21035: result: yes
-configure:20950: checking for idna_to_ascii_from_locale
-configure:21006: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-/tmp/ccwwbzQR.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/conftest.c:189: undefined reference to `idna_to_ascii_from_locale'
-collect2: ld returned 1 exit status
-configure:21013: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| #define HAVE_ALLOCA_H 1
-| #define HAVE_ALLOCA 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_GETPAGESIZE 1
-| #define HAVE_MMAP 1
-| #define HAVE_ARGZ_H 1
-| #define HAVE_LIMITS_H 1
-| #define HAVE_LOCALE_H 1
-| #define HAVE_NL_TYPES_H 1
-| #define HAVE_MALLOC_H 1
-| #define HAVE_STDDEF_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_SYS_PARAM_H 1
-| #define HAVE_FEOF_UNLOCKED 1
-| #define HAVE_FGETS_UNLOCKED 1
-| #define HAVE_GETCWD 1
-| #define HAVE_GETEGID 1
-| #define HAVE_GETEUID 1
-| #define HAVE_GETGID 1
-| #define HAVE_GETUID 1
-| #define HAVE_MEMPCPY 1
-| #define HAVE_MUNMAP 1
-| #define HAVE_PUTENV 1
-| #define HAVE_SETENV 1
-| #define HAVE_SETLOCALE 1
-| #define HAVE_STPCPY 1
-| #define HAVE_STRCHR 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRTOUL 1
-| #define HAVE_TSEARCH 1
-| #define HAVE___ARGZ_COUNT 1
-| #define HAVE___ARGZ_STRINGIFY 1
-| #define HAVE___ARGZ_NEXT 1
-| #define HAVE_ICONV 1
-| #define ICONV_CONST
-| #define HAVE_LANGINFO_CODESET 1
-| #define HAVE_LC_MESSAGES 1
-| #define ENABLE_NLS 1
-| #define HAVE_GETTEXT 1
-| #define HAVE_DCGETTEXT 1
-| #define HAVE_ICONV_H 1
-| #define HAVE_ICONV_T_DEF 1
-| #define ICONV_NONTRANS 0
-| #define HAVE_BIND_TEXTDOMAIN_CODESET 1
-| #define HAVE_LIBIDN 1
-| #define HAVE_IDNA_TO_UNICODE_8Z8Z 1
-| #define HAVE_IDNA_TO_ASCII_8Z 1
-| #define HAVE_IDNA_TO_ASCII_LZ 1
-| /* end confdefs.h. */
-| /* Define idna_to_ascii_from_locale to an innocuous variant, in case <limits.h> declares idna_to_ascii_from_locale.
-| For example, HP-UX 11i <limits.h> declares gettimeofday. */
-| #define idna_to_ascii_from_locale innocuous_idna_to_ascii_from_locale
-|
-| /* System header to define __stub macros and hopefully few prototypes,
-| which can conflict with char idna_to_ascii_from_locale (); below.
-| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
-| <limits.h> exists even on freestanding compilers. */
-|
-| #ifdef __STDC__
-| # include <limits.h>
-| #else
-| # include <assert.h>
-| #endif
-|
-| #undef idna_to_ascii_from_locale
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char idna_to_ascii_from_locale ();
-| /* The GNU C library defines this for functions which it implements
-| to always fail with ENOSYS. Some functions are actually named
-| something starting with __ and the normal name is an alias. */
-| #if defined __stub_idna_to_ascii_from_locale || defined __stub___idna_to_ascii_from_locale
-| choke me
-| #endif
-|
-| int
-| main ()
-| {
-| return idna_to_ascii_from_locale ();
-| ;
-| return 0;
-| }
-configure:21035: result: no
-configure:21067: checking wchar.h usability
-configure:21084: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-configure:21091: $? = 0
-configure:21105: result: yes
-configure:21109: checking wchar.h presence
-configure:21124: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c
-configure:21131: $? = 0
-configure:21145: result: yes
-configure:21173: checking for wchar.h
-configure:21182: result: yes
-configure:21198: checking for wchar_t
-configure:21230: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:166: warning: unused variable 'wc'
-configure:21237: $? = 0
-configure:21252: result: yes
-configure:21263: checking for wint_t
-configure:21295: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:166: warning: unused variable 'wc'
-configure:21302: $? = 0
-configure:21317: result: yes
-configure:21344: checking wctype.h usability
-configure:21361: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-configure:21368: $? = 0
-configure:21382: result: yes
-configure:21386: checking wctype.h presence
-configure:21401: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c
-configure:21408: $? = 0
-configure:21422: result: yes
-configure:21450: checking for wctype.h
-configure:21459: result: yes
-configure:21481: checking for iswalnum
-configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:180: warning: conflicting types for built-in function 'iswalnum'
-configure:21544: $? = 0
-configure:21566: result: yes
-configure:21481: checking for iswalpha
-configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:181: warning: conflicting types for built-in function 'iswalpha'
-configure:21544: $? = 0
-configure:21566: result: yes
-configure:21481: checking for iswcntrl
-configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:182: warning: conflicting types for built-in function 'iswcntrl'
-configure:21544: $? = 0
-configure:21566: result: yes
-configure:21481: checking for iswdigit
-configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:183: warning: conflicting types for built-in function 'iswdigit'
-configure:21544: $? = 0
-configure:21566: result: yes
-configure:21587: checking for iswgraph
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:184: warning: conflicting types for built-in function 'iswgraph'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswlower
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:185: warning: conflicting types for built-in function 'iswlower'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswprint
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:186: warning: conflicting types for built-in function 'iswprint'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswpunct
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:187: warning: conflicting types for built-in function 'iswpunct'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswspace
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:188: warning: conflicting types for built-in function 'iswspace'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswupper
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:189: warning: conflicting types for built-in function 'iswupper'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21690: checking for iswxdigit
-configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:190: warning: conflicting types for built-in function 'iswxdigit'
-configure:21753: $? = 0
-configure:21775: result: yes
-configure:21690: checking for towupper
-configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:191: warning: conflicting types for built-in function 'towupper'
-configure:21753: $? = 0
-configure:21775: result: yes
-configure:21690: checking for towlower
-configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:192: warning: conflicting types for built-in function 'towlower'
-configure:21753: $? = 0
-configure:21775: result: yes
-configure:21788: checking for mbstate_t
-configure:21820: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:180: warning: unused variable 's'
-configure:21827: $? = 0
-configure:21842: result: yes
-configure:21862: checking for wchar_t functions
-configure:21899: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c: In function 'main':
-conftest.c:184: warning: statement with no effect
-conftest.c:184: warning: statement with no effect
-conftest.c:184: warning: statement with no effect
-conftest.c:184: warning: statement with no effect
-conftest.c:185: warning: statement with no effect
-configure:21906: $? = 0
-configure:21926: result: yes
-configure:21941: checking for nl_langinfo and CODESET
-configure:21967: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c: In function 'main':
-conftest.c:175: warning: unused variable 'cs'
-configure:21974: $? = 0
-configure:21994: result: yes
-configure:22004: checking for nl_langinfo and YESEXPR
-configure:22030: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c: In function 'main':
-conftest.c:176: warning: unused variable 'cs'
-configure:22037: $? = 0
-configure:22057: result: yes
-configure:22070: checking for ospcat
-configure:22088: found /usr/bin/ospcat
-configure:22101: result: /usr/bin/ospcat
-configure:22111: checking for openjade docbook stylesheets
-configure:22126: result: not found: PDF documentation will not be built.
-configure:22309: creating ./config.status
-
-## ---------------------- ##
-## Running config.status. ##
-## ---------------------- ##
-
-This file was extended by config.status, which was
-generated by GNU Autoconf 2.63. Invocation command line was
-
- CONFIG_FILES =
- CONFIG_HEADERS =
- CONFIG_LINKS =
- CONFIG_COMMANDS =
- $ ./config.status
-
-on debian
-
-config.status:1011: creating Makefile
-config.status:1011: creating contrib/Makefile
-config.status:1011: creating doc/Makefile
-config.status:1011: creating imap/Makefile
-config.status:1011: creating intl/Makefile
-config.status:1011: creating m4/Makefile
-config.status:1011: creating po/Makefile.in
-config.status:1011: creating hcachever.sh
-config.status:1011: creating muttbug.sh
-config.status:1011: creating doc/instdoc.sh
-config.status:1011: creating config.h
-config.status:1278: executing depfiles commands
-config.status:1278: executing default-1 commands
-configure:23670: WARNING: unrecognized options: --with-sharedir, --enable-inodesort
-
-## ---------------- ##
-## Cache variables. ##
-## ---------------- ##
-
-ac_cv_build=i486-pc-linux-gnu
-ac_cv_c_bigendian=no
-ac_cv_c_compiler_gnu=yes
-ac_cv_c_const=yes
-ac_cv_c_inline=inline
-ac_cv_dirent_d_ino=yes
-ac_cv_env_CC_set=
-ac_cv_env_CC_value=
-ac_cv_env_CFLAGS_set=set
-ac_cv_env_CFLAGS_value='-Wall -g -O2'
-ac_cv_env_CPPFLAGS_set=set
-ac_cv_env_CPPFLAGS_value=-I/usr/include/qdbm
-ac_cv_env_CPP_set=
-ac_cv_env_CPP_value=
-ac_cv_env_GNUTLS_CFLAGS_set=
-ac_cv_env_GNUTLS_CFLAGS_value=
-ac_cv_env_GNUTLS_LIBS_set=
-ac_cv_env_GNUTLS_LIBS_value=
-ac_cv_env_LDFLAGS_set=set
-ac_cv_env_LDFLAGS_value=
-ac_cv_env_LIBS_set=
-ac_cv_env_LIBS_value=
-ac_cv_env_PKG_CONFIG_set=
-ac_cv_env_PKG_CONFIG_value=
-ac_cv_env_build_alias_set=set
-ac_cv_env_build_alias_value=i486-linux-gnu
-ac_cv_env_host_alias_set=
-ac_cv_env_host_alias_value=
-ac_cv_env_target_alias_set=
-ac_cv_env_target_alias_value=
-ac_cv_func___argz_count=yes
-ac_cv_func___argz_next=yes
-ac_cv_func___argz_stringify=yes
-ac_cv_func_alloca_works=yes
-ac_cv_func_bind_textdomain_codeset=yes
-ac_cv_func_dcgettext=yes
-ac_cv_func_decl_bkgdset=yes
-ac_cv_func_decl_curs_set=yes
-ac_cv_func_decl_meta=yes
-ac_cv_func_decl_resizeterm=yes
-ac_cv_func_decl_start_color=yes
-ac_cv_func_decl_typeahead=yes
-ac_cv_func_decl_use_default_colors=yes
-ac_cv_func_fchdir=yes
-ac_cv_func_feof_unlocked=yes
-ac_cv_func_fgetpos=yes
-ac_cv_func_fgets_unlocked=yes
-ac_cv_func_ftruncate=yes
-ac_cv_func_getaddrinfo=yes
-ac_cv_func_getcwd=yes
-ac_cv_func_getegid=yes
-ac_cv_func_geteuid=yes
-ac_cv_func_getgid=yes
-ac_cv_func_gethostent=yes
-ac_cv_func_getopt=yes
-ac_cv_func_getpagesize=yes
-ac_cv_func_getsid=yes
-ac_cv_func_getuid=yes
-ac_cv_func_idna_to_ascii_8z=yes
-ac_cv_func_idna_to_ascii_from_locale=no
-ac_cv_func_idna_to_ascii_from_utf8=no
-ac_cv_func_idna_to_ascii_lz=yes
-ac_cv_func_idna_to_unicode_8z8z=yes
-ac_cv_func_idna_to_unicode_utf8_from_utf8=no
-ac_cv_func_initscr=no
-ac_cv_func_iswalnum=yes
-ac_cv_func_iswalpha=yes
-ac_cv_func_iswcntrl=yes
-ac_cv_func_iswdigit=yes
-ac_cv_func_iswgraph=yes
-ac_cv_func_iswlower=yes
-ac_cv_func_iswprint=yes
-ac_cv_func_iswpunct=yes
-ac_cv_func_iswspace=yes
-ac_cv_func_iswupper=yes
-ac_cv_func_iswxdigit=yes
-ac_cv_func_memmove=yes
-ac_cv_func_mempcpy=yes
-ac_cv_func_mmap_fixed_mapped=yes
-ac_cv_func_munmap=yes
-ac_cv_func_putenv=yes
-ac_cv_func_regcomp=yes
-ac_cv_func_setegid=yes
-ac_cv_func_setenv=yes
-ac_cv_func_setlocale=yes
-ac_cv_func_setrlimit=yes
-ac_cv_func_setsockopt=yes
-ac_cv_func_snprintf=yes
-ac_cv_func_srand48=yes
-ac_cv_func_stpcpy=yes
-ac_cv_func_strcasecmp=yes
-ac_cv_func_strchr=yes
-ac_cv_func_strdup=yes
-ac_cv_func_strerror=yes
-ac_cv_func_strftime=yes
-ac_cv_func_strsep=yes
-ac_cv_func_strtok_r=yes
-ac_cv_func_strtoul=yes
-ac_cv_func_towlower=yes
-ac_cv_func_towupper=yes
-ac_cv_func_tsearch=yes
-ac_cv_func_vsnprintf=yes
-ac_cv_gdbmopen=yes
-ac_cv_gnu_library_2_1=yes
-ac_cv_have_decl_sys_siglist=yes
-ac_cv_header_argz_h=yes
-ac_cv_header_getopt_h=yes
-ac_cv_header_iconv_h=yes
-ac_cv_header_inttypes_h=yes
-ac_cv_header_ioctl_h=no
-ac_cv_header_libintl_h=yes
-ac_cv_header_limits_h=yes
-ac_cv_header_locale_h=yes
-ac_cv_header_malloc_h=yes
-ac_cv_header_memory_h=yes
-ac_cv_header_minix_config_h=no
-ac_cv_header_ncursesw_ncurses_h=yes
-ac_cv_header_nl_types_h=yes
-ac_cv_header_stdarg_h=yes
-ac_cv_header_stdc=yes
-ac_cv_header_stddef_h=yes
-ac_cv_header_stdint_h=yes
-ac_cv_header_stdlib_h=yes
-ac_cv_header_string_h=yes
-ac_cv_header_strings_h=yes
-ac_cv_header_sys_ioctl_h=yes
-ac_cv_header_sys_param_h=yes
-ac_cv_header_sys_resource_h=yes
-ac_cv_header_sys_select_h=yes
-ac_cv_header_sys_stat_h=yes
-ac_cv_header_sys_time_h=yes
-ac_cv_header_sys_types_h=yes
-ac_cv_header_sysexits_h=yes
-ac_cv_header_unistd_h=yes
-ac_cv_header_unix_h=no
-ac_cv_header_wchar_h=yes
-ac_cv_header_wctype_h=yes
-ac_cv_host=i486-pc-linux-gnu
-ac_cv_lib_ncurses___waddnwstr=no
-ac_cv_lib_ncursesw___initscr=yes
-ac_cv_lib_ncursesw___waddnwstr=yes
-ac_cv_lib_sasl2_sasl_client_init=yes
-ac_cv_objext=o
-ac_cv_path_DBX=no
-ac_cv_path_EGREP='/bin/grep -E'
-ac_cv_path_GDB=/usr/bin/gdb
-ac_cv_path_GMSGFMT=/usr/bin/msgfmt
-ac_cv_path_GPGME_CONFIG=/usr/bin/gpgme-config
-ac_cv_path_GREP=/bin/grep
-ac_cv_path_ISPELL=no
-ac_cv_path_KRB5CFGPATH=/usr/bin/krb5-config
-ac_cv_path_MSGFMT=/usr/bin/msgfmt
-ac_cv_path_OSPCAT=/usr/bin/ospcat
-ac_cv_path_SDB=no
-ac_cv_path_SENDMAIL=/usr/sbin/sendmail
-ac_cv_path_XGETTEXT=/usr/bin/xgettext
-ac_cv_path_ac_pt_PKG_CONFIG=/usr/bin/pkg-config
-ac_cv_path_install='/usr/bin/install -c'
-ac_cv_path_mkdir=/bin/mkdir
-ac_cv_prog_AWK=gawk
-ac_cv_prog_CPP='gcc -E'
-ac_cv_prog_INTLBISON=bison
-ac_cv_prog_ac_ct_AR=ar
-ac_cv_prog_ac_ct_CC=gcc
-ac_cv_prog_ac_ct_RANLIB=ranlib
-ac_cv_prog_cc_c89=
-ac_cv_prog_cc_g=yes
-ac_cv_prog_make_make_set=yes
-ac_cv_safe_to_define___extensions__=yes
-ac_cv_search_strerror='none required'
-ac_cv_search_stringprep_check_version=-lidn
-ac_cv_sizeof_int=4
-ac_cv_sizeof_long=4
-ac_cv_sizeof_long_long=8
-ac_cv_sizeof_off_t=8
-ac_cv_sizeof_short=2
-ac_cv_sys_file_offset_bits=64
-ac_cv_sys_largefile_CC=no
-ac_cv_sys_largefile_source=no
-ac_cv_type_off_t=yes
-ac_cv_type_pid_t=yes
-ac_cv_type_sig_atomic_t=yes
-ac_cv_type_signal=void
-ac_cv_type_size_t=yes
-ac_cv_type_ssize_t=yes
-ac_cv_type_uint32_t=yes
-ac_cv_working_alloca_h=yes
-am_cv_CC_dependencies_compiler_type=none
-am_cv_func_iconv=yes
-am_cv_langinfo_codeset=yes
-am_cv_lib_iconv=no
-am_cv_proto_iconv='extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);'
-am_cv_proto_iconv_arg1=
-am_cv_val_LC_MESSAGES=yes
-cf_cv_ncurses_header=ncursesw/ncurses.h
-gt_cv_func_gnugettext1_libc=yes
-mutt_cv_c99_snprintf=yes
-mutt_cv_c99_vsnprintf=yes
-mutt_cv_curses=/usr
-mutt_cv_docdir=/usr/share/doc
-mutt_cv_fcntl=yes
-mutt_cv_func_snprintf=yes
-mutt_cv_func_vsnprintf=yes
-mutt_cv_groupwrite=yes
-mutt_cv_iconv_good=yes
-mutt_cv_iconv_nontrans=no
-mutt_cv_langinfo_codeset=yes
-mutt_cv_langinfo_yesexpr=yes
-mutt_cv_mailpath=/var/mail
-mutt_cv_mbstate_t=yes
-mutt_cv_prefix=/usr
-mutt_cv_regex=no
-mutt_cv_regex_broken=no
-mutt_cv_setgid=yes
-mutt_cv_version=1.5.19
-mutt_cv_warnings=yes
-mutt_cv_wc_funcs=yes
-mutt_cv_wchar_t=yes
-mutt_cv_wint_t=yes
-mutt_cv_worldwrite=no
-nls_cv_force_use_gnu_gettext=no
-nls_cv_header_intl=
-nls_cv_header_libgt=
-nls_cv_use_gnu_gettext=no
-pkg_cv_GNUTLS_CFLAGS=' '
-pkg_cv_GNUTLS_LIBS='-lgnutls '
-
-## ----------------- ##
-## Output variables. ##
-## ----------------- ##
-
-ACLOCAL='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10'
-ALLOCA=''
-AMDEPBACKSLASH=''
-AMDEP_FALSE=''
-AMDEP_TRUE='#'
-AMTAR='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar'
-ANSI2KNR=''
-AR='ar'
-AUTOCONF='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf'
-AUTOHEADER='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader'
-AUTOMAKE='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10'
-AWK='gawk'
-BUILD_IMAP_FALSE='#'
-BUILD_IMAP_TRUE=''
-BUILD_INCLUDED_LIBINTL='no'
-CATALOGS=' de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo'
-CATOBJEXT='.gmo'
-CC='gcc'
-CCDEPMODE='depmode=none'
-CFLAGS='-Wall -pedantic -Wno-long-long -Wall -g -O2'
-CONFIG_STATUS_DEPENDENCIES='$(top_srcdir)/VERSION'
-CPP='gcc -E'
-CPPFLAGS='-I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl'
-CYGPATH_W='echo'
-DATADIRNAME='share'
-DBX='no'
-DEBUGGER='/usr/bin/gdb'
-DEFS='-DHAVE_CONFIG_H'
-DEPDIR='.deps'
-DOTLOCK_GROUP='mail'
-DOTLOCK_PERMISSION='2755'
-DOTLOCK_TARGET='mutt_dotlock$(EXEEXT)'
-DSLROOT=''
-ECHO_C=''
-ECHO_N='-n'
-ECHO_T=''
-EGREP='/bin/grep -E'
-EXEEXT=''
-GDB='/usr/bin/gdb'
-GENCAT='gencat'
-GLIBC21='yes'
-GMOFILES=' de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo'
-GMSGFMT='/usr/bin/msgfmt'
-GNUTLS_CFLAGS=' '
-GNUTLS_LIBS='-lgnutls '
-GPGME_CFLAGS=''
-GPGME_CONFIG='/usr/bin/gpgme-config'
-GPGME_LIBS='-lgpgme -lgpg-error'
-GREP='/bin/grep'
-INSTALL_DATA='${INSTALL} -m 644'
-INSTALL_PROGRAM='${INSTALL}'
-INSTALL_SCRIPT='${INSTALL}'
-INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
-INSTOBJEXT='.mo'
-INTLBISON='bison'
-INTLLIBS=''
-INTLOBJS=''
-INTL_LIBTOOL_SUFFIX_PREFIX=''
-ISPELL='no'
-KRB5CFGPATH='/usr/bin/krb5-config'
-LDFLAGS=' -L/lib'
-LIBICONV=''
-LIBIMAP='-Limap -limap'
-LIBIMAPDEPS='$(top_srcdir)/imap/imap.h imap/libimap.a'
-LIBOBJS=''
-LIBS='-lidn '
-LTLIBOBJS=''
-MAINT='#'
-MAINTAINER_MODE_FALSE=''
-MAINTAINER_MODE_TRUE='#'
-MAKEINFO='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo'
-MKDIR_P='/bin/mkdir -p'
-MKINSTALLDIRS='../mkinstalldirs'
-MSGFMT='/usr/bin/msgfmt'
-MUTTLIBS=' -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm'
-MUTT_LIB_OBJECTS=' crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o'
-MUTT_MD5='mutt_md5'
-OBJEXT='o'
-OPS='$(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT '
-OSPCAT='/usr/bin/ospcat'
-PACKAGE='mutt'
-PACKAGE_BUGREPORT=''
-PACKAGE_NAME=''
-PACKAGE_STRING=''
-PACKAGE_TARNAME=''
-PACKAGE_VERSION=''
-PATH_SEPARATOR=':'
-PGPAUX_TARGET='pgpring$(EXEEXT) pgpewrap$(EXEEXT)'
-PKG_CONFIG='/usr/bin/pkg-config'
-POFILES=' de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po'
-POSUB='po'
-RANLIB='ranlib'
-SDB='no'
-SENDMAIL='/usr/sbin/sendmail'
-SET_MAKE=''
-SHELL='/bin/sh'
-SMIMEAUX_TARGET='smime_keys'
-STRIP=''
-U=''
-USE_GSS_FALSE='#'
-USE_GSS_TRUE=''
-USE_INCLUDED_LIBINTL='no'
-USE_NLS='yes'
-USE_SASL_FALSE='#'
-USE_SASL_TRUE=''
-USE_SSL_FALSE='#'
-USE_SSL_TRUE=''
-VERSION='1.5.19'
-XGETTEXT='/usr/bin/xgettext'
-ac_ct_CC='gcc'
-am__fastdepCC_FALSE=''
-am__fastdepCC_TRUE='#'
-am__include='include'
-am__isrc=' -I$(srcdir)'
-am__leading_dot='.'
-am__quote=''
-am__tar='${AMTAR} chof - "$$tardir"'
-am__untar='${AMTAR} xf -'
-bindir='${exec_prefix}/bin'
-build='i486-pc-linux-gnu'
-build_alias='i486-linux-gnu'
-build_cpu='i486'
-build_os='linux-gnu'
-build_vendor='pc'
-datadir='${datarootdir}'
-datarootdir='${prefix}/share'
-docdir='/usr/share/doc'
-dvidir='${docdir}'
-exec_prefix='${prefix}'
-host='i486-pc-linux-gnu'
-host_alias=''
-host_cpu='i486'
-host_os='linux-gnu'
-host_vendor='pc'
-htmldir='${docdir}'
-includedir='${prefix}/include'
-infodir='${datarootdir}/info'
-install_sh='$(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh'
-libdir='${exec_prefix}/lib'
-libexecdir='${exec_prefix}/libexec'
-localedir='${datarootdir}/locale'
-localstatedir='${prefix}/var'
-mandir='/usr/share/man'
-mkdir_p='/bin/mkdir -p'
-oldincludedir='/usr/include'
-pdfdir='${docdir}'
-prefix='/usr'
-program_transform_name='s,x,x,'
-psdir='${docdir}'
-sbindir='${exec_prefix}/sbin'
-sharedstatedir='${prefix}/com'
-sysconfdir='/etc'
-target_alias=''
-
-## ----------- ##
-## confdefs.h. ##
-## ----------- ##
-
-#define PACKAGE_NAME ""
-#define PACKAGE_TARNAME ""
-#define PACKAGE_VERSION ""
-#define PACKAGE_STRING ""
-#define PACKAGE_BUGREPORT ""
-#define PACKAGE "mutt"
-#define VERSION "1.5.19"
-#define STDC_HEADERS 1
-#define HAVE_SYS_TYPES_H 1
-#define HAVE_SYS_STAT_H 1
-#define HAVE_STDLIB_H 1
-#define HAVE_STRING_H 1
-#define HAVE_MEMORY_H 1
-#define HAVE_STRINGS_H 1
-#define HAVE_INTTYPES_H 1
-#define HAVE_STDINT_H 1
-#define HAVE_UNISTD_H 1
-#define __EXTENSIONS__ 1
-#define _ALL_SOURCE 1
-#define _GNU_SOURCE 1
-#define _POSIX_PTHREAD_SEMANTICS 1
-#define _TANDEM_SOURCE 1
-#define PROTOTYPES 1
-#define __PROTOTYPES 1
-#define HAVE_STRING_H 1
-#define _FILE_OFFSET_BITS 64
-#define HAVE_FSEEKO 1
-#define SIZEOF_OFF_T 8
-#define HAVE_INTTYPES_H 1
-#define HAVE_C99_INTTYPES 1
-#define SIZEOF_SHORT 2
-#define SIZEOF_INT 4
-#define SIZEOF_LONG 4
-#define SIZEOF_LONG_LONG 8
-#define SENDMAIL "/usr/sbin/sendmail"
-#define CRYPT_BACKEND_GPGME 1
-#define HAVE_GPGME_PKA_TRUST 1
-#define CRYPT_BACKEND_GPGME 1
-#define CRYPT_BACKEND_CLASSIC_PGP 1
-#define CRYPT_BACKEND_CLASSIC_SMIME 1
-#define MIXMASTER "mixmaster"
-#define HAVE_NCURSESW_NCURSES_H 1
-#define HAVE_START_COLOR 1
-#define HAVE_TYPEAHEAD 1
-#define HAVE_BKGDSET 1
-#define HAVE_CURS_SET 1
-#define HAVE_META 1
-#define HAVE_USE_DEFAULT_COLORS 1
-#define HAVE_RESIZETERM 1
-#define HAVE_COLOR 1
-#define STDC_HEADERS 1
-#define HAVE_STDARG_H 1
-#define HAVE_SYS_IOCTL_H 1
-#define HAVE_SYSEXITS_H 1
-#define HAVE_SYS_TIME_H 1
-#define HAVE_SYS_RESOURCE_H 1
-#define HAVE_SETRLIMIT 1
-#define HAVE_GETSID 1
-#define RETSIGTYPE void
-#define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-#define HAVE_DECL_SYS_SIGLIST 1
-#define HAVE_FGETPOS 1
-#define HAVE_MEMMOVE 1
-#define HAVE_SETEGID 1
-#define HAVE_SRAND48 1
-#define HAVE_STRERROR 1
-#define HAVE_SETENV 1
-#define HAVE_STRCASECMP 1
-#define HAVE_STRDUP 1
-#define HAVE_STRSEP 1
-#define HAVE_STRTOK_R 1
-#define HAVE_GETOPT_H 1
-#define HAVE_SNPRINTF 1
-#define HAVE_VSNPRINTF 1
-#define HAVE_FTRUNCATE 1
-#define HAVE_STRFTIME 1
-#define HAVE_FCHDIR 1
-#define HAVE_REGCOMP 1
-#define MAILPATH "/var/mail"
-#define USE_DOTLOCK 1
-#define USE_SETGID 1
-#define DL_STANDALONE 1
-#define USE_POP 1
-#define USE_IMAP 1
-#define USE_SMTP 1
-#define HAVE_SYS_SELECT_H 1
-#define HAVE_GETADDRINFO 1
-#define USE_SOCKET 1
-#define USE_GSS 1
-#define USE_SSL 1
-#define USE_SSL_GNUTLS 1
-#define HAVE_LIBSASL2 1
-#define USE_SASL 1
-#define DEBUG 1
-#define USE_FCNTL 1
-#define HAVE_DIRENT_D_INO 1
-#define USE_COMPRESSED 1
-#define EXECSHELL "/bin/sh"
-#define USE_HCACHE 1
-#define HAVE_GDBM 1
-#define HAVE_ALLOCA_H 1
-#define HAVE_ALLOCA 1
-#define HAVE_STDLIB_H 1
-#define HAVE_UNISTD_H 1
-#define HAVE_GETPAGESIZE 1
-#define HAVE_MMAP 1
-#define HAVE_ARGZ_H 1
-#define HAVE_LIMITS_H 1
-#define HAVE_LOCALE_H 1
-#define HAVE_NL_TYPES_H 1
-#define HAVE_MALLOC_H 1
-#define HAVE_STDDEF_H 1
-#define HAVE_STDLIB_H 1
-#define HAVE_STRING_H 1
-#define HAVE_UNISTD_H 1
-#define HAVE_SYS_PARAM_H 1
-#define HAVE_FEOF_UNLOCKED 1
-#define HAVE_FGETS_UNLOCKED 1
-#define HAVE_GETCWD 1
-#define HAVE_GETEGID 1
-#define HAVE_GETEUID 1
-#define HAVE_GETGID 1
-#define HAVE_GETUID 1
-#define HAVE_MEMPCPY 1
-#define HAVE_MUNMAP 1
-#define HAVE_PUTENV 1
-#define HAVE_SETENV 1
-#define HAVE_SETLOCALE 1
-#define HAVE_STPCPY 1
-#define HAVE_STRCHR 1
-#define HAVE_STRCASECMP 1
-#define HAVE_STRDUP 1
-#define HAVE_STRTOUL 1
-#define HAVE_TSEARCH 1
-#define HAVE___ARGZ_COUNT 1
-#define HAVE___ARGZ_STRINGIFY 1
-#define HAVE___ARGZ_NEXT 1
-#define HAVE_ICONV 1
-#define ICONV_CONST
-#define HAVE_LANGINFO_CODESET 1
-#define HAVE_LC_MESSAGES 1
-#define ENABLE_NLS 1
-#define HAVE_GETTEXT 1
-#define HAVE_DCGETTEXT 1
-#define HAVE_ICONV_H 1
-#define HAVE_ICONV_T_DEF 1
-#define ICONV_NONTRANS 0
-#define HAVE_BIND_TEXTDOMAIN_CODESET 1
-#define HAVE_LIBIDN 1
-#define HAVE_IDNA_TO_UNICODE_8Z8Z 1
-#define HAVE_IDNA_TO_ASCII_8Z 1
-#define HAVE_IDNA_TO_ASCII_LZ 1
-#define HAVE_WCHAR_H 1
-#define HAVE_WCTYPE_H 1
-#define HAVE_ISWALNUM 1
-#define HAVE_ISWALPHA 1
-#define HAVE_ISWCNTRL 1
-#define HAVE_ISWDIGIT 1
-#define HAVE_ISWGRAPH 1
-#define HAVE_ISWLOWER 1
-#define HAVE_ISWPRINT 1
-#define HAVE_ISWPUNCT 1
-#define HAVE_ISWSPACE 1
-#define HAVE_ISWUPPER 1
-#define HAVE_ISWXDIGIT 1
-#define HAVE_TOWUPPER 1
-#define HAVE_TOWLOWER 1
-#define HAVE_WC_FUNCS 1
-#define HAVE_LANGINFO_CODESET 1
-#define HAVE_LANGINFO_YESEXPR 1
-#define MAKEDOC_FULL 1
-
-configure: exit 0
+++ /dev/null
-#! /bin/sh
-# Generated by configure.
-# Run this file to recreate the current configuration.
-# Compiler output produced by configure, useful for debugging
-# configure, is in config.log if it exists.
-
-debug=false
-ac_cs_recheck=false
-ac_cs_silent=false
-SHELL=${CONFIG_SHELL-/bin/sh}
-## --------------------- ##
-## M4sh Initialization. ##
-## --------------------- ##
-
-# Be more Bourne compatible
-DUALCASE=1; export DUALCASE # for MKS sh
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
- emulate sh
- NULLCMD=:
- # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
- setopt NO_GLOB_SUBST
-else
- case `(set -o) 2>/dev/null` in
- *posix*) set -o posix ;;
-esac
-
-fi
-
-
-
-
-# PATH needs CR
-# Avoid depending upon Character Ranges.
-as_cr_letters='abcdefghijklmnopqrstuvwxyz'
-as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
-as_cr_Letters=$as_cr_letters$as_cr_LETTERS
-as_cr_digits='0123456789'
-as_cr_alnum=$as_cr_Letters$as_cr_digits
-
-as_nl='
-'
-export as_nl
-# Printing a long string crashes Solaris 7 /usr/bin/printf.
-as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
-if (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
- as_echo='printf %s\n'
- as_echo_n='printf %s'
-else
- if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
- as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
- as_echo_n='/usr/ucb/echo -n'
- else
- as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
- as_echo_n_body='eval
- arg=$1;
- case $arg in
- *"$as_nl"*)
- expr "X$arg" : "X\\(.*\\)$as_nl";
- arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
- esac;
- expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
- '
- export as_echo_n_body
- as_echo_n='sh -c $as_echo_n_body as_echo'
- fi
- export as_echo_body
- as_echo='sh -c $as_echo_body as_echo'
-fi
-
-# The user is always right.
-if test "${PATH_SEPARATOR+set}" != set; then
- PATH_SEPARATOR=:
- (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
- (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
- PATH_SEPARATOR=';'
- }
-fi
-
-# Support unset when possible.
-if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then
- as_unset=unset
-else
- as_unset=false
-fi
-
-
-# IFS
-# We need space, tab and new line, in precisely that order. Quoting is
-# there to prevent editors from complaining about space-tab.
-# (If _AS_PATH_WALK were called with IFS unset, it would disable word
-# splitting by setting IFS to empty value.)
-IFS=" "" $as_nl"
-
-# Find who we are. Look in the path if we contain no directory separator.
-case $0 in
- *[\\/]* ) as_myself=$0 ;;
- *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
-done
-IFS=$as_save_IFS
-
- ;;
-esac
-# We did not find ourselves, most probably we were run as `sh COMMAND'
-# in which case we are not to be found in the path.
-if test "x$as_myself" = x; then
- as_myself=$0
-fi
-if test ! -f "$as_myself"; then
- $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
- { (exit 1); exit 1; }
-fi
-
-# Work around bugs in pre-3.0 UWIN ksh.
-for as_var in ENV MAIL MAILPATH
-do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var
-done
-PS1='$ '
-PS2='> '
-PS4='+ '
-
-# NLS nuisances.
-LC_ALL=C
-export LC_ALL
-LANGUAGE=C
-export LANGUAGE
-
-# Required to use basename.
-if expr a : '\(a\)' >/dev/null 2>&1 &&
- test "X`expr 00001 : '.*\(...\)'`" = X001; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
- as_basename=basename
-else
- as_basename=false
-fi
-
-
-# Name of the executable.
-as_me=`$as_basename -- "$0" ||
-$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X/"$0" |
- sed '/^.*\/\([^/][^/]*\)\/*$/{
- s//\1/
- q
- }
- /^X\/\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\/\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
-
-# CDPATH.
-$as_unset CDPATH
-
-
-
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x`expr $as_lineno_1 + 1`" = "x$as_lineno_2" || {
-
- # Create $as_me.lineno as a copy of $as_myself, but with $LINENO
- # uniformly replaced by the line number. The first 'sed' inserts a
- # line-number line after each line using $LINENO; the second 'sed'
- # does the real work. The second script uses 'N' to pair each
- # line-number line with the line containing $LINENO, and appends
- # trailing '-' during substitution so that $LINENO is not a special
- # case at line end.
- # (Raja R Harinath suggested sed '=', and Paul Eggert wrote the
- # scripts with optimization help from Paolo Bonzini. Blame Lee
- # E. McMahon (1931-1989) for sed's syntax. :-)
- sed -n '
- p
- /[$]LINENO/=
- ' <$as_myself |
- sed '
- s/[$]LINENO.*/&-/
- t lineno
- b
- :lineno
- N
- :loop
- s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
- t loop
- s/-\n.*//
- ' >$as_me.lineno &&
- chmod +x "$as_me.lineno" ||
- { $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2
- { (exit 1); exit 1; }; }
-
- # Don't try to exec as it changes $[0], causing all sort of problems
- # (the dirname of $[0] is not the place where we might find the
- # original and so on. Autoconf is especially sensitive to this).
- . "./$as_me.lineno"
- # Exit status is that of the last command.
- exit
-}
-
-
-if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
- as_dirname=dirname
-else
- as_dirname=false
-fi
-
-ECHO_C= ECHO_N= ECHO_T=
-case `echo -n x` in
--n*)
- case `echo 'x\c'` in
- *c*) ECHO_T=' ';; # ECHO_T is single tab character.
- *) ECHO_C='\c';;
- esac;;
-*)
- ECHO_N='-n';;
-esac
-if expr a : '\(a\)' >/dev/null 2>&1 &&
- test "X`expr 00001 : '.*\(...\)'`" = X001; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-rm -f conf$$ conf$$.exe conf$$.file
-if test -d conf$$.dir; then
- rm -f conf$$.dir/conf$$.file
-else
- rm -f conf$$.dir
- mkdir conf$$.dir 2>/dev/null
-fi
-if (echo >conf$$.file) 2>/dev/null; then
- if ln -s conf$$.file conf$$ 2>/dev/null; then
- as_ln_s='ln -s'
- # ... but there are two gotchas:
- # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
- # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
- # In both cases, we have to default to `cp -p'.
- ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
- as_ln_s='cp -p'
- elif ln conf$$.file conf$$ 2>/dev/null; then
- as_ln_s=ln
- else
- as_ln_s='cp -p'
- fi
-else
- as_ln_s='cp -p'
-fi
-rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
-rmdir conf$$.dir 2>/dev/null
-
-if mkdir -p . 2>/dev/null; then
- as_mkdir_p=:
-else
- test -d ./-p && rmdir ./-p
- as_mkdir_p=false
-fi
-
-if test -x / >/dev/null 2>&1; then
- as_test_x='test -x'
-else
- if ls -dL / >/dev/null 2>&1; then
- as_ls_L_option=L
- else
- as_ls_L_option=
- fi
- as_test_x='
- eval sh -c '\''
- if test -d "$1"; then
- test -d "$1/.";
- else
- case $1 in
- -*)set "./$1";;
- esac;
- case `ls -ld'$as_ls_L_option' "$1" 2>/dev/null` in
- ???[sx]*):;;*)false;;esac;fi
- '\'' sh
- '
-fi
-as_executable_p=$as_test_x
-
-# Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
-
-# Sed expression to map a string onto a valid variable name.
-as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
-
-
-exec 6>&1
-
-# Save the log message, to keep $[0] and so on meaningful, and to
-# report actual input values of CONFIG_FILES etc. instead of their
-# values after options handling.
-ac_log="
-This file was extended by $as_me, which was
-generated by GNU Autoconf 2.63. Invocation command line was
-
- CONFIG_FILES = $CONFIG_FILES
- CONFIG_HEADERS = $CONFIG_HEADERS
- CONFIG_LINKS = $CONFIG_LINKS
- CONFIG_COMMANDS = $CONFIG_COMMANDS
- $ $0 $@
-
-on `(hostname || uname -n) 2>/dev/null | sed 1q`
-"
-
-# Files that config.status was made for.
-config_files=" Makefile contrib/Makefile doc/Makefile imap/Makefile intl/Makefile m4/Makefile po/Makefile.in hcachever.sh muttbug.sh doc/instdoc.sh"
-config_headers=" config.h"
-config_commands=" depfiles default-1"
-
-ac_cs_usage="\
-\`$as_me' instantiates files from templates according to the
-current configuration.
-
-Usage: $0 [OPTION]... [FILE]...
-
- -h, --help print this help, then exit
- -V, --version print version number and configuration settings, then exit
- -q, --quiet, --silent
- do not print progress messages
- -d, --debug don't remove temporary files
- --recheck update $as_me by reconfiguring in the same conditions
- --file=FILE[:TEMPLATE]
- instantiate the configuration file FILE
- --header=FILE[:TEMPLATE]
- instantiate the configuration header FILE
-
-Configuration files:
-$config_files
-
-Configuration headers:
-$config_headers
-
-Configuration commands:
-$config_commands
-
-Report bugs to <bug-autoconf@gnu.org>."
-
-ac_cs_version="\
-config.status
-configured by ../configure, generated by GNU Autoconf 2.63,
- with options \"'--prefix=/usr' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-sharedir=/usr/share/mutt' '--with-docdir=/usr/share/doc' '--with-mailpath=/var/mail' '--disable-dependency-tracking' '--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-inodesort' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' '--without-qdbm' '--without-bdb' '--without-tokyocabinet' '--build' 'i486-linux-gnu' 'build_alias=i486-linux-gnu' 'CFLAGS=-Wall -g -O2' 'LDFLAGS=' 'CPPFLAGS=-I/usr/include/qdbm'\"
-
-Copyright (C) 2008 Free Software Foundation, Inc.
-This config.status script is free software; the Free Software Foundation
-gives unlimited permission to copy, distribute and modify it."
-
-ac_pwd='/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched'
-srcdir='..'
-INSTALL='/usr/bin/install -c'
-MKDIR_P='/bin/mkdir -p'
-AWK='gawk'
-test -n "$AWK" || AWK=awk
-# The default lists apply if the user does not specify any file.
-ac_need_defaults=:
-while test $# != 0
-do
- case $1 in
- --*=*)
- ac_option=`expr "X$1" : 'X\([^=]*\)='`
- ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'`
- ac_shift=:
- ;;
- *)
- ac_option=$1
- ac_optarg=$2
- ac_shift=shift
- ;;
- esac
-
- case $ac_option in
- # Handling of the options.
- -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
- ac_cs_recheck=: ;;
- --version | --versio | --versi | --vers | --ver | --ve | --v | -V )
- $as_echo "$ac_cs_version"; exit ;;
- --debug | --debu | --deb | --de | --d | -d )
- debug=: ;;
- --file | --fil | --fi | --f )
- $ac_shift
- case $ac_optarg in
- *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
- esac
- CONFIG_FILES="$CONFIG_FILES '$ac_optarg'"
- ac_need_defaults=false;;
- --header | --heade | --head | --hea )
- $ac_shift
- case $ac_optarg in
- *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
- esac
- CONFIG_HEADERS="$CONFIG_HEADERS '$ac_optarg'"
- ac_need_defaults=false;;
- --he | --h)
- # Conflict between --help and --header
- { $as_echo "$as_me: error: ambiguous option: $1
-Try \`$0 --help' for more information." >&2
- { (exit 1); exit 1; }; };;
- --help | --hel | -h )
- $as_echo "$ac_cs_usage"; exit ;;
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil | --si | --s)
- ac_cs_silent=: ;;
-
- # This is an error.
- -*) { $as_echo "$as_me: error: unrecognized option: $1
-Try \`$0 --help' for more information." >&2
- { (exit 1); exit 1; }; } ;;
-
- *) ac_config_targets="$ac_config_targets $1"
- ac_need_defaults=false ;;
-
- esac
- shift
-done
-
-ac_configure_extra_args=
-
-if $ac_cs_silent; then
- exec 6>/dev/null
- ac_configure_extra_args="$ac_configure_extra_args --silent"
-fi
-
-if $ac_cs_recheck; then
- set X '/bin/sh' '../configure' '--prefix=/usr' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-sharedir=/usr/share/mutt' '--with-docdir=/usr/share/doc' '--with-mailpath=/var/mail' '--disable-dependency-tracking' '--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-inodesort' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' '--without-qdbm' '--without-bdb' '--without-tokyocabinet' '--build' 'i486-linux-gnu' 'build_alias=i486-linux-gnu' 'CFLAGS=-Wall -g -O2' 'LDFLAGS=' 'CPPFLAGS=-I/usr/include/qdbm' $ac_configure_extra_args --no-create --no-recursion
- shift
- $as_echo "running CONFIG_SHELL=/bin/sh $*" >&6
- CONFIG_SHELL='/bin/sh'
- export CONFIG_SHELL
- exec "$@"
-fi
-
-exec 5>>config.log
-{
- echo
- sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
-## Running $as_me. ##
-_ASBOX
- $as_echo "$ac_log"
-} >&5
-
-#
-# INIT-COMMANDS
-#
-AMDEP_TRUE="#" ac_aux_dir=".."
-
-
-
-# Handling of arguments.
-for ac_config_target in $ac_config_targets
-do
- case $ac_config_target in
- "config.h") CONFIG_HEADERS="$CONFIG_HEADERS config.h" ;;
- "depfiles") CONFIG_COMMANDS="$CONFIG_COMMANDS depfiles" ;;
- "default-1") CONFIG_COMMANDS="$CONFIG_COMMANDS default-1" ;;
- "Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;;
- "contrib/Makefile") CONFIG_FILES="$CONFIG_FILES contrib/Makefile" ;;
- "doc/Makefile") CONFIG_FILES="$CONFIG_FILES doc/Makefile" ;;
- "imap/Makefile") CONFIG_FILES="$CONFIG_FILES imap/Makefile" ;;
- "intl/Makefile") CONFIG_FILES="$CONFIG_FILES intl/Makefile" ;;
- "m4/Makefile") CONFIG_FILES="$CONFIG_FILES m4/Makefile" ;;
- "po/Makefile.in") CONFIG_FILES="$CONFIG_FILES po/Makefile.in" ;;
- "hcachever.sh") CONFIG_FILES="$CONFIG_FILES hcachever.sh" ;;
- "muttbug.sh") CONFIG_FILES="$CONFIG_FILES muttbug.sh" ;;
- "doc/instdoc.sh") CONFIG_FILES="$CONFIG_FILES doc/instdoc.sh" ;;
-
- *) { { $as_echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5
-$as_echo "$as_me: error: invalid argument: $ac_config_target" >&2;}
- { (exit 1); exit 1; }; };;
- esac
-done
-
-
-# If the user did not use the arguments to specify the items to instantiate,
-# then the envvar interface is used. Set only those that are not.
-# We use the long form for the default assignment because of an extremely
-# bizarre bug on SunOS 4.1.3.
-if $ac_need_defaults; then
- test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
- test "${CONFIG_HEADERS+set}" = set || CONFIG_HEADERS=$config_headers
- test "${CONFIG_COMMANDS+set}" = set || CONFIG_COMMANDS=$config_commands
-fi
-
-# Have a temporary directory for convenience. Make it in the build tree
-# simply because there is no reason against having it here, and in addition,
-# creating and moving files from /tmp can sometimes cause problems.
-# Hook for its removal unless debugging.
-# Note that there is a small window in which the directory will not be cleaned:
-# after its creation but before its name has been assigned to `$tmp'.
-$debug ||
-{
- tmp=
- trap 'exit_status=$?
- { test -z "$tmp" || test ! -d "$tmp" || rm -fr "$tmp"; } && exit $exit_status
-' 0
- trap '{ (exit 1); exit 1; }' 1 2 13 15
-}
-# Create a (secure) tmp directory for tmp files.
-
-{
- tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` &&
- test -n "$tmp" && test -d "$tmp"
-} ||
-{
- tmp=./conf$$-$RANDOM
- (umask 077 && mkdir "$tmp")
-} ||
-{
- $as_echo "$as_me: cannot create a temporary directory in ." >&2
- { (exit 1); exit 1; }
-}
-
-# Set up the scripts for CONFIG_FILES section.
-# No need to generate them if there are no CONFIG_FILES.
-# This happens for instance with `./config.status config.h'.
-if test -n "$CONFIG_FILES"; then
-
-
-ac_cr='\r'
-ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' </dev/null 2>/dev/null`
-if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then
- ac_cs_awk_cr='\\r'
-else
- ac_cs_awk_cr=$ac_cr
-fi
-
-echo 'BEGIN {' >"$tmp/subs1.awk" &&
-cat >>"$tmp/subs1.awk" <<\_ACAWK &&
-S["LTLIBOBJS"]=""
-S["DSLROOT"]=""
-S["OSPCAT"]="/usr/bin/ospcat"
-S["INTL_LIBTOOL_SUFFIX_PREFIX"]=""
-S["MKINSTALLDIRS"]="../mkinstalldirs"
-S["GENCAT"]="gencat"
-S["INSTOBJEXT"]=".mo"
-S["DATADIRNAME"]="share"
-S["POSUB"]="po"
-S["POFILES"]=" de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po "\
-"ja.po hu.po et.po ca.po bg.po ga.po"
-S["INTLOBJS"]=""
-S["INTLLIBS"]=""
-S["GMOFILES"]=" de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gm"\
-"o da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo"
-S["CATOBJEXT"]=".gmo"
-S["CATALOGS"]=" de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gm"\
-"o da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo"
-S["USE_INCLUDED_LIBINTL"]="no"
-S["BUILD_INCLUDED_LIBINTL"]="no"
-S["INTLBISON"]="bison"
-S["XGETTEXT"]="/usr/bin/xgettext"
-S["GMSGFMT"]="/usr/bin/msgfmt"
-S["MSGFMT"]="/usr/bin/msgfmt"
-S["USE_NLS"]="yes"
-S["LIBICONV"]=""
-S["GLIBC21"]="yes"
-S["ALLOCA"]=""
-S["LIBIMAPDEPS"]="$(top_srcdir)/imap/imap.h imap/libimap.a"
-S["LIBIMAP"]="-Limap -limap"
-S["MUTT_LIB_OBJECTS"]=" crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-"\
-"classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mut"\
-"t_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o"
-S["MUTTLIBS"]=" -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm"
-S["MUTT_MD5"]="mutt_md5"
-S["USE_SASL_FALSE"]="#"
-S["USE_SASL_TRUE"]=""
-S["USE_SSL_FALSE"]="#"
-S["USE_SSL_TRUE"]=""
-S["GNUTLS_LIBS"]="-lgnutls "
-S["GNUTLS_CFLAGS"]=" "
-S["PKG_CONFIG"]="/usr/bin/pkg-config"
-S["USE_GSS_FALSE"]="#"
-S["USE_GSS_TRUE"]=""
-S["KRB5CFGPATH"]="/usr/bin/krb5-config"
-S["BUILD_IMAP_FALSE"]="#"
-S["BUILD_IMAP_TRUE"]=""
-S["DOTLOCK_PERMISSION"]="2755"
-S["DOTLOCK_GROUP"]="mail"
-S["DOTLOCK_TARGET"]="mutt_dotlock$(EXEEXT)"
-S["LIBOBJS"]=""
-S["ISPELL"]="no"
-S["SMIMEAUX_TARGET"]="smime_keys"
-S["PGPAUX_TARGET"]="pgpring$(EXEEXT) pgpewrap$(EXEEXT)"
-S["OPS"]="$(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT "
-S["GPGME_LIBS"]="-lgpgme -lgpg-error"
-S["GPGME_CFLAGS"]=""
-S["GPGME_CONFIG"]="/usr/bin/gpgme-config"
-S["SENDMAIL"]="/usr/sbin/sendmail"
-S["DEBUGGER"]="/usr/bin/gdb"
-S["SDB"]="no"
-S["GDB"]="/usr/bin/gdb"
-S["DBX"]="no"
-S["AR"]="ar"
-S["RANLIB"]="ranlib"
-S["ANSI2KNR"]=""
-S["U"]=""
-S["host_os"]="linux-gnu"
-S["host_vendor"]="pc"
-S["host_cpu"]="i486"
-S["host"]="i486-pc-linux-gnu"
-S["build_os"]="linux-gnu"
-S["build_vendor"]="pc"
-S["build_cpu"]="i486"
-S["build"]="i486-pc-linux-gnu"
-S["EGREP"]="/bin/grep -E"
-S["GREP"]="/bin/grep"
-S["CPP"]="gcc -E"
-S["am__fastdepCC_FALSE"]=""
-S["am__fastdepCC_TRUE"]="#"
-S["CCDEPMODE"]="depmode=none"
-S["AMDEPBACKSLASH"]=""
-S["AMDEP_FALSE"]=""
-S["AMDEP_TRUE"]="#"
-S["am__quote"]=""
-S["am__include"]="include"
-S["DEPDIR"]=".deps"
-S["OBJEXT"]="o"
-S["EXEEXT"]=""
-S["ac_ct_CC"]="gcc"
-S["CPPFLAGS"]="-I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl"
-S["LDFLAGS"]=" -L/lib"
-S["CFLAGS"]="-Wall -pedantic -Wno-long-long -Wall -g -O2"
-S["CC"]="gcc"
-S["CONFIG_STATUS_DEPENDENCIES"]="$(top_srcdir)/VERSION"
-S["MAINT"]="#"
-S["MAINTAINER_MODE_FALSE"]=""
-S["MAINTAINER_MODE_TRUE"]="#"
-S["am__untar"]="${AMTAR} xf -"
-S["am__tar"]="${AMTAR} chof - \"$$tardir\""
-S["AMTAR"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar"
-S["am__leading_dot"]="."
-S["SET_MAKE"]=""
-S["AWK"]="gawk"
-S["mkdir_p"]="/bin/mkdir -p"
-S["MKDIR_P"]="/bin/mkdir -p"
-S["INSTALL_STRIP_PROGRAM"]="$(install_sh) -c -s"
-S["STRIP"]=""
-S["install_sh"]="$(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh"
-S["MAKEINFO"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo"
-S["AUTOHEADER"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader"
-S["AUTOMAKE"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10"
-S["AUTOCONF"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf"
-S["ACLOCAL"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10"
-S["VERSION"]="1.5.19"
-S["PACKAGE"]="mutt"
-S["CYGPATH_W"]="echo"
-S["am__isrc"]=" -I$(srcdir)"
-S["INSTALL_DATA"]="${INSTALL} -m 644"
-S["INSTALL_SCRIPT"]="${INSTALL}"
-S["INSTALL_PROGRAM"]="${INSTALL}"
-S["target_alias"]=""
-S["host_alias"]=""
-S["build_alias"]="i486-linux-gnu"
-S["LIBS"]="-lidn "
-S["ECHO_T"]=""
-S["ECHO_N"]="-n"
-S["ECHO_C"]=""
-S["DEFS"]="-DHAVE_CONFIG_H"
-S["mandir"]="/usr/share/man"
-S["localedir"]="${datarootdir}/locale"
-S["libdir"]="${exec_prefix}/lib"
-S["psdir"]="${docdir}"
-S["pdfdir"]="${docdir}"
-S["dvidir"]="${docdir}"
-S["htmldir"]="${docdir}"
-S["infodir"]="${datarootdir}/info"
-S["docdir"]="/usr/share/doc"
-S["oldincludedir"]="/usr/include"
-S["includedir"]="${prefix}/include"
-S["localstatedir"]="${prefix}/var"
-S["sharedstatedir"]="${prefix}/com"
-S["sysconfdir"]="/etc"
-S["datadir"]="${datarootdir}"
-S["datarootdir"]="${prefix}/share"
-S["libexecdir"]="${exec_prefix}/libexec"
-S["sbindir"]="${exec_prefix}/sbin"
-S["bindir"]="${exec_prefix}/bin"
-S["program_transform_name"]="s,x,x,"
-S["prefix"]="/usr"
-S["exec_prefix"]="${prefix}"
-S["PACKAGE_BUGREPORT"]=""
-S["PACKAGE_STRING"]=""
-S["PACKAGE_VERSION"]=""
-S["PACKAGE_TARNAME"]=""
-S["PACKAGE_NAME"]=""
-S["PATH_SEPARATOR"]=":"
-S["SHELL"]="/bin/sh"
-_ACAWK
-cat >>"$tmp/subs1.awk" <<_ACAWK &&
- for (key in S) S_is_set[key] = 1
- FS = "\a"
-
-}
-{
- line = $ 0
- nfields = split(line, field, "@")
- substed = 0
- len = length(field[1])
- for (i = 2; i < nfields; i++) {
- key = field[i]
- keylen = length(key)
- if (S_is_set[key]) {
- value = S[key]
- line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3)
- len += length(value) + length(field[++i])
- substed = 1
- } else
- len += 1 + keylen
- }
-
- print line
-}
-
-_ACAWK
-if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then
- sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g"
-else
- cat
-fi < "$tmp/subs1.awk" > "$tmp/subs.awk" \
- || { { $as_echo "$as_me:$LINENO: error: could not setup config files machinery" >&5
-$as_echo "$as_me: error: could not setup config files machinery" >&2;}
- { (exit 1); exit 1; }; }
-fi # test -n "$CONFIG_FILES"
-
-# Set up the scripts for CONFIG_HEADERS section.
-# No need to generate them if there are no CONFIG_HEADERS.
-# This happens for instance with `./config.status Makefile'.
-if test -n "$CONFIG_HEADERS"; then
-cat >"$tmp/defines.awk" <<\_ACAWK ||
-BEGIN {
-D["PACKAGE_NAME"]=" \"\""
-D["PACKAGE_TARNAME"]=" \"\""
-D["PACKAGE_VERSION"]=" \"\""
-D["PACKAGE_STRING"]=" \"\""
-D["PACKAGE_BUGREPORT"]=" \"\""
-D["PACKAGE"]=" \"mutt\""
-D["VERSION"]=" \"1.5.19\""
-D["STDC_HEADERS"]=" 1"
-D["HAVE_SYS_TYPES_H"]=" 1"
-D["HAVE_SYS_STAT_H"]=" 1"
-D["HAVE_STDLIB_H"]=" 1"
-D["HAVE_STRING_H"]=" 1"
-D["HAVE_MEMORY_H"]=" 1"
-D["HAVE_STRINGS_H"]=" 1"
-D["HAVE_INTTYPES_H"]=" 1"
-D["HAVE_STDINT_H"]=" 1"
-D["HAVE_UNISTD_H"]=" 1"
-D["__EXTENSIONS__"]=" 1"
-D["_ALL_SOURCE"]=" 1"
-D["_GNU_SOURCE"]=" 1"
-D["_POSIX_PTHREAD_SEMANTICS"]=" 1"
-D["_TANDEM_SOURCE"]=" 1"
-D["PROTOTYPES"]=" 1"
-D["__PROTOTYPES"]=" 1"
-D["HAVE_STRING_H"]=" 1"
-D["_FILE_OFFSET_BITS"]=" 64"
-D["HAVE_FSEEKO"]=" 1"
-D["SIZEOF_OFF_T"]=" 8"
-D["HAVE_INTTYPES_H"]=" 1"
-D["HAVE_C99_INTTYPES"]=" 1"
-D["SIZEOF_SHORT"]=" 2"
-D["SIZEOF_INT"]=" 4"
-D["SIZEOF_LONG"]=" 4"
-D["SIZEOF_LONG_LONG"]=" 8"
-D["SENDMAIL"]=" \"/usr/sbin/sendmail\""
-D["CRYPT_BACKEND_GPGME"]=" 1"
-D["HAVE_GPGME_PKA_TRUST"]=" 1"
-D["CRYPT_BACKEND_GPGME"]=" 1"
-D["CRYPT_BACKEND_CLASSIC_PGP"]=" 1"
-D["CRYPT_BACKEND_CLASSIC_SMIME"]=" 1"
-D["MIXMASTER"]=" \"mixmaster\""
-D["HAVE_NCURSESW_NCURSES_H"]=" 1"
-D["HAVE_START_COLOR"]=" 1"
-D["HAVE_TYPEAHEAD"]=" 1"
-D["HAVE_BKGDSET"]=" 1"
-D["HAVE_CURS_SET"]=" 1"
-D["HAVE_META"]=" 1"
-D["HAVE_USE_DEFAULT_COLORS"]=" 1"
-D["HAVE_RESIZETERM"]=" 1"
-D["HAVE_COLOR"]=" 1"
-D["STDC_HEADERS"]=" 1"
-D["HAVE_STDARG_H"]=" 1"
-D["HAVE_SYS_IOCTL_H"]=" 1"
-D["HAVE_SYSEXITS_H"]=" 1"
-D["HAVE_SYS_TIME_H"]=" 1"
-D["HAVE_SYS_RESOURCE_H"]=" 1"
-D["HAVE_SETRLIMIT"]=" 1"
-D["HAVE_GETSID"]=" 1"
-D["RETSIGTYPE"]=" void"
-D["SIG_ATOMIC_VOLATILE_T"]=" volatile sig_atomic_t"
-D["HAVE_DECL_SYS_SIGLIST"]=" 1"
-D["HAVE_FGETPOS"]=" 1"
-D["HAVE_MEMMOVE"]=" 1"
-D["HAVE_SETEGID"]=" 1"
-D["HAVE_SRAND48"]=" 1"
-D["HAVE_STRERROR"]=" 1"
-D["HAVE_SETENV"]=" 1"
-D["HAVE_STRCASECMP"]=" 1"
-D["HAVE_STRDUP"]=" 1"
-D["HAVE_STRSEP"]=" 1"
-D["HAVE_STRTOK_R"]=" 1"
-D["HAVE_GETOPT_H"]=" 1"
-D["HAVE_SNPRINTF"]=" 1"
-D["HAVE_VSNPRINTF"]=" 1"
-D["HAVE_FTRUNCATE"]=" 1"
-D["HAVE_STRFTIME"]=" 1"
-D["HAVE_FCHDIR"]=" 1"
-D["HAVE_REGCOMP"]=" 1"
-D["MAILPATH"]=" \"/var/mail\""
-D["USE_DOTLOCK"]=" 1"
-D["USE_SETGID"]=" 1"
-D["DL_STANDALONE"]=" 1"
-D["USE_POP"]=" 1"
-D["USE_IMAP"]=" 1"
-D["USE_SMTP"]=" 1"
-D["HAVE_SYS_SELECT_H"]=" 1"
-D["HAVE_GETADDRINFO"]=" 1"
-D["USE_SOCKET"]=" 1"
-D["USE_GSS"]=" 1"
-D["USE_SSL"]=" 1"
-D["USE_SSL_GNUTLS"]=" 1"
-D["HAVE_LIBSASL2"]=" 1"
-D["USE_SASL"]=" 1"
-D["DEBUG"]=" 1"
-D["USE_FCNTL"]=" 1"
-D["HAVE_DIRENT_D_INO"]=" 1"
-D["USE_COMPRESSED"]=" 1"
-D["EXECSHELL"]=" \"/bin/sh\""
-D["USE_HCACHE"]=" 1"
-D["HAVE_GDBM"]=" 1"
-D["HAVE_ALLOCA_H"]=" 1"
-D["HAVE_ALLOCA"]=" 1"
-D["HAVE_STDLIB_H"]=" 1"
-D["HAVE_UNISTD_H"]=" 1"
-D["HAVE_GETPAGESIZE"]=" 1"
-D["HAVE_MMAP"]=" 1"
-D["HAVE_ARGZ_H"]=" 1"
-D["HAVE_LIMITS_H"]=" 1"
-D["HAVE_LOCALE_H"]=" 1"
-D["HAVE_NL_TYPES_H"]=" 1"
-D["HAVE_MALLOC_H"]=" 1"
-D["HAVE_STDDEF_H"]=" 1"
-D["HAVE_STDLIB_H"]=" 1"
-D["HAVE_STRING_H"]=" 1"
-D["HAVE_UNISTD_H"]=" 1"
-D["HAVE_SYS_PARAM_H"]=" 1"
-D["HAVE_FEOF_UNLOCKED"]=" 1"
-D["HAVE_FGETS_UNLOCKED"]=" 1"
-D["HAVE_GETCWD"]=" 1"
-D["HAVE_GETEGID"]=" 1"
-D["HAVE_GETEUID"]=" 1"
-D["HAVE_GETGID"]=" 1"
-D["HAVE_GETUID"]=" 1"
-D["HAVE_MEMPCPY"]=" 1"
-D["HAVE_MUNMAP"]=" 1"
-D["HAVE_PUTENV"]=" 1"
-D["HAVE_SETENV"]=" 1"
-D["HAVE_SETLOCALE"]=" 1"
-D["HAVE_STPCPY"]=" 1"
-D["HAVE_STRCHR"]=" 1"
-D["HAVE_STRCASECMP"]=" 1"
-D["HAVE_STRDUP"]=" 1"
-D["HAVE_STRTOUL"]=" 1"
-D["HAVE_TSEARCH"]=" 1"
-D["HAVE___ARGZ_COUNT"]=" 1"
-D["HAVE___ARGZ_STRINGIFY"]=" 1"
-D["HAVE___ARGZ_NEXT"]=" 1"
-D["HAVE_ICONV"]=" 1"
-D["ICONV_CONST"]=" "
-D["HAVE_LANGINFO_CODESET"]=" 1"
-D["HAVE_LC_MESSAGES"]=" 1"
-D["ENABLE_NLS"]=" 1"
-D["HAVE_GETTEXT"]=" 1"
-D["HAVE_DCGETTEXT"]=" 1"
-D["HAVE_ICONV_H"]=" 1"
-D["HAVE_ICONV_T_DEF"]=" 1"
-D["ICONV_NONTRANS"]=" 0"
-D["HAVE_BIND_TEXTDOMAIN_CODESET"]=" 1"
-D["HAVE_LIBIDN"]=" 1"
-D["HAVE_IDNA_TO_UNICODE_8Z8Z"]=" 1"
-D["HAVE_IDNA_TO_ASCII_8Z"]=" 1"
-D["HAVE_IDNA_TO_ASCII_LZ"]=" 1"
-D["HAVE_WCHAR_H"]=" 1"
-D["HAVE_WCTYPE_H"]=" 1"
-D["HAVE_ISWALNUM"]=" 1"
-D["HAVE_ISWALPHA"]=" 1"
-D["HAVE_ISWCNTRL"]=" 1"
-D["HAVE_ISWDIGIT"]=" 1"
-D["HAVE_ISWGRAPH"]=" 1"
-D["HAVE_ISWLOWER"]=" 1"
-D["HAVE_ISWPRINT"]=" 1"
-D["HAVE_ISWPUNCT"]=" 1"
-D["HAVE_ISWSPACE"]=" 1"
-D["HAVE_ISWUPPER"]=" 1"
-D["HAVE_ISWXDIGIT"]=" 1"
-D["HAVE_TOWUPPER"]=" 1"
-D["HAVE_TOWLOWER"]=" 1"
-D["HAVE_WC_FUNCS"]=" 1"
-D["HAVE_LANGINFO_CODESET"]=" 1"
-D["HAVE_LANGINFO_YESEXPR"]=" 1"
-D["MAKEDOC_FULL"]=" 1"
- for (key in D) D_is_set[key] = 1
- FS = "\a"
-}
-/^[\t ]*#[\t ]*(define|undef)[\t ]+[_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ][_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]*([\t (]|$)/ {
- line = $ 0
- split(line, arg, " ")
- if (arg[1] == "#") {
- defundef = arg[2]
- mac1 = arg[3]
- } else {
- defundef = substr(arg[1], 2)
- mac1 = arg[2]
- }
- split(mac1, mac2, "(") #)
- macro = mac2[1]
- prefix = substr(line, 1, index(line, defundef) - 1)
- if (D_is_set[macro]) {
- # Preserve the white space surrounding the "#".
- print prefix "define", macro P[macro] D[macro]
- next
- } else {
- # Replace #undef with comments. This is necessary, for example,
- # in the case of _POSIX_SOURCE, which is predefined and required
- # on some systems where configure will not decide to define it.
- if (defundef == "undef") {
- print "/*", prefix defundef, macro, "*/"
- next
- }
- }
-}
-{ print }
-_ACAWK
- { { $as_echo "$as_me:$LINENO: error: could not setup config headers machinery" >&5
-$as_echo "$as_me: error: could not setup config headers machinery" >&2;}
- { (exit 1); exit 1; }; }
-fi # test -n "$CONFIG_HEADERS"
-
-
-eval set X " :F $CONFIG_FILES :H $CONFIG_HEADERS :C $CONFIG_COMMANDS"
-shift
-for ac_tag
-do
- case $ac_tag in
- :[FHLC]) ac_mode=$ac_tag; continue;;
- esac
- case $ac_mode$ac_tag in
- :[FHL]*:*);;
- :L* | :C*:*) { { $as_echo "$as_me:$LINENO: error: invalid tag $ac_tag" >&5
-$as_echo "$as_me: error: invalid tag $ac_tag" >&2;}
- { (exit 1); exit 1; }; };;
- :[FH]-) ac_tag=-:-;;
- :[FH]*) ac_tag=$ac_tag:$ac_tag.in;;
- esac
- ac_save_IFS=$IFS
- IFS=:
- set x $ac_tag
- IFS=$ac_save_IFS
- shift
- ac_file=$1
- shift
-
- case $ac_mode in
- :L) ac_source=$1;;
- :[FH])
- ac_file_inputs=
- for ac_f
- do
- case $ac_f in
- -) ac_f="$tmp/stdin";;
- *) # Look for the file first in the build tree, then in the source tree
- # (if the path is not absolute). The absolute path cannot be DOS-style,
- # because $ac_f cannot contain `:'.
- test -f "$ac_f" ||
- case $ac_f in
- [\\/$]*) false;;
- *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";;
- esac ||
- { { $as_echo "$as_me:$LINENO: error: cannot find input file: $ac_f" >&5
-$as_echo "$as_me: error: cannot find input file: $ac_f" >&2;}
- { (exit 1); exit 1; }; };;
- esac
- case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac
- ac_file_inputs="$ac_file_inputs '$ac_f'"
- done
-
- # Let's still pretend it is `configure' which instantiates (i.e., don't
- # use $as_me), people would be surprised to read:
- # /* config.h. Generated by config.status. */
- configure_input='Generated from '`
- $as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g'
- `' by configure.'
- if test x"$ac_file" != x-; then
- configure_input="$ac_file. $configure_input"
- { $as_echo "$as_me:$LINENO: creating $ac_file" >&5
-$as_echo "$as_me: creating $ac_file" >&6;}
- fi
- # Neutralize special characters interpreted by sed in replacement strings.
- case $configure_input in #(
- *\&* | *\|* | *\\* )
- ac_sed_conf_input=`$as_echo "$configure_input" |
- sed 's/[\\\\&|]/\\\\&/g'`;; #(
- *) ac_sed_conf_input=$configure_input;;
- esac
-
- case $ac_tag in
- *:-:* | *:-) cat >"$tmp/stdin" \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; } ;;
- esac
- ;;
- esac
-
- ac_dir=`$as_dirname -- "$ac_file" ||
-$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$ac_file" : 'X\(//\)[^/]' \| \
- X"$ac_file" : 'X\(//\)$' \| \
- X"$ac_file" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$ac_file" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- { as_dir="$ac_dir"
- case $as_dir in #(
- -*) as_dir=./$as_dir;;
- esac
- test -d "$as_dir" || { $as_mkdir_p && mkdir -p "$as_dir"; } || {
- as_dirs=
- while :; do
- case $as_dir in #(
- *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
- *) as_qdir=$as_dir;;
- esac
- as_dirs="'$as_qdir' $as_dirs"
- as_dir=`$as_dirname -- "$as_dir" ||
-$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$as_dir" : 'X\(//\)[^/]' \| \
- X"$as_dir" : 'X\(//\)$' \| \
- X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$as_dir" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- test -d "$as_dir" && break
- done
- test -z "$as_dirs" || eval "mkdir $as_dirs"
- } || test -d "$as_dir" || { { $as_echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5
-$as_echo "$as_me: error: cannot create directory $as_dir" >&2;}
- { (exit 1); exit 1; }; }; }
- ac_builddir=.
-
-case "$ac_dir" in
-.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
-*)
- ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
- # A ".." for each directory in $ac_dir_suffix.
- ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
- case $ac_top_builddir_sub in
- "") ac_top_builddir_sub=. ac_top_build_prefix= ;;
- *) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
- esac ;;
-esac
-ac_abs_top_builddir=$ac_pwd
-ac_abs_builddir=$ac_pwd$ac_dir_suffix
-# for backward compatibility:
-ac_top_builddir=$ac_top_build_prefix
-
-case $srcdir in
- .) # We are building in place.
- ac_srcdir=.
- ac_top_srcdir=$ac_top_builddir_sub
- ac_abs_top_srcdir=$ac_pwd ;;
- [\\/]* | ?:[\\/]* ) # Absolute name.
- ac_srcdir=$srcdir$ac_dir_suffix;
- ac_top_srcdir=$srcdir
- ac_abs_top_srcdir=$srcdir ;;
- *) # Relative name.
- ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
- ac_top_srcdir=$ac_top_build_prefix$srcdir
- ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
-esac
-ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
-
-
- case $ac_mode in
- :F)
- #
- # CONFIG_FILE
- #
-
- case $INSTALL in
- [\\/$]* | ?:[\\/]* ) ac_INSTALL=$INSTALL ;;
- *) ac_INSTALL=$ac_top_build_prefix$INSTALL ;;
- esac
- ac_MKDIR_P=$MKDIR_P
- case $MKDIR_P in
- [\\/$]* | ?:[\\/]* ) ;;
- */*) ac_MKDIR_P=$ac_top_build_prefix$MKDIR_P ;;
- esac
-# If the template does not know about datarootdir, expand it.
-# FIXME: This hack should be removed a few years after 2.60.
-ac_datarootdir_hack=; ac_datarootdir_seen=
-
-ac_sed_dataroot='
-/datarootdir/ {
- p
- q
-}
-/@datadir@/p
-/@docdir@/p
-/@infodir@/p
-/@localedir@/p
-/@mandir@/p
-'
-case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in
-*datarootdir*) ac_datarootdir_seen=yes;;
-*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*)
- { $as_echo "$as_me:$LINENO: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5
-$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;}
- ac_datarootdir_hack='
- s&@datadir@&${datarootdir}&g
- s&@docdir@&/usr/share/doc&g
- s&@infodir@&${datarootdir}/info&g
- s&@localedir@&${datarootdir}/locale&g
- s&@mandir@&/usr/share/man&g
- s&\${datarootdir}&${prefix}/share&g' ;;
-esac
-ac_sed_extra="
-
-:t
-/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
-s|@configure_input@|$ac_sed_conf_input|;t t
-s&@top_builddir@&$ac_top_builddir_sub&;t t
-s&@top_build_prefix@&$ac_top_build_prefix&;t t
-s&@srcdir@&$ac_srcdir&;t t
-s&@abs_srcdir@&$ac_abs_srcdir&;t t
-s&@top_srcdir@&$ac_top_srcdir&;t t
-s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t
-s&@builddir@&$ac_builddir&;t t
-s&@abs_builddir@&$ac_abs_builddir&;t t
-s&@abs_top_builddir@&$ac_abs_top_builddir&;t t
-s&@INSTALL@&$ac_INSTALL&;t t
-s&@MKDIR_P@&$ac_MKDIR_P&;t t
-$ac_datarootdir_hack
-"
-eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$tmp/subs.awk" >$tmp/out \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; }
-
-test -z "$ac_datarootdir_hack$ac_datarootdir_seen" &&
- { ac_out=`sed -n '/\${datarootdir}/p' "$tmp/out"`; test -n "$ac_out"; } &&
- { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' "$tmp/out"`; test -z "$ac_out"; } &&
- { $as_echo "$as_me:$LINENO: WARNING: $ac_file contains a reference to the variable \`datarootdir'
-which seems to be undefined. Please make sure it is defined." >&5
-$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir'
-which seems to be undefined. Please make sure it is defined." >&2;}
-
- rm -f "$tmp/stdin"
- case $ac_file in
- -) cat "$tmp/out" && rm -f "$tmp/out";;
- *) rm -f "$ac_file" && mv "$tmp/out" "$ac_file";;
- esac \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; }
- ;;
- :H)
- #
- # CONFIG_HEADER
- #
- if test x"$ac_file" != x-; then
- {
- $as_echo "/* $configure_input */" \
- && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs"
- } >"$tmp/config.h" \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; }
- if diff "$ac_file" "$tmp/config.h" >/dev/null 2>&1; then
- { $as_echo "$as_me:$LINENO: $ac_file is unchanged" >&5
-$as_echo "$as_me: $ac_file is unchanged" >&6;}
- else
- rm -f "$ac_file"
- mv "$tmp/config.h" "$ac_file" \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; }
- fi
- else
- $as_echo "/* $configure_input */" \
- && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs" \
- || { { $as_echo "$as_me:$LINENO: error: could not create -" >&5
-$as_echo "$as_me: error: could not create -" >&2;}
- { (exit 1); exit 1; }; }
- fi
-# Compute "$ac_file"'s index in $config_headers.
-_am_arg="$ac_file"
-_am_stamp_count=1
-for _am_header in $config_headers :; do
- case $_am_header in
- $_am_arg | $_am_arg:* )
- break ;;
- * )
- _am_stamp_count=`expr $_am_stamp_count + 1` ;;
- esac
-done
-echo "timestamp for $_am_arg" >`$as_dirname -- "$_am_arg" ||
-$as_expr X"$_am_arg" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$_am_arg" : 'X\(//\)[^/]' \| \
- X"$_am_arg" : 'X\(//\)$' \| \
- X"$_am_arg" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$_am_arg" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`/stamp-h$_am_stamp_count
- ;;
-
- :C) { $as_echo "$as_me:$LINENO: executing $ac_file commands" >&5
-$as_echo "$as_me: executing $ac_file commands" >&6;}
- ;;
- esac
-
-
- case $ac_file$ac_mode in
- "depfiles":C) test x"$AMDEP_TRUE" != x"" || for mf in $CONFIG_FILES; do
- # Strip MF so we end up with the name of the file.
- mf=`echo "$mf" | sed -e 's/:.*$//'`
- # Check whether this is an Automake generated Makefile or not.
- # We used to match only the files named `Makefile.in', but
- # some people rename them; so instead we look at the file content.
- # Grep'ing the first line is not enough: some people post-process
- # each Makefile.in and add a new line on top of each file to say so.
- # Grep'ing the whole file is not good either: AIX grep has a line
- # limit of 2048, but all sed's we know have understand at least 4000.
- if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then
- dirpart=`$as_dirname -- "$mf" ||
-$as_expr X"$mf" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$mf" : 'X\(//\)[^/]' \| \
- X"$mf" : 'X\(//\)$' \| \
- X"$mf" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$mf" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- else
- continue
- fi
- # Extract the definition of DEPDIR, am__include, and am__quote
- # from the Makefile without running `make'.
- DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"`
- test -z "$DEPDIR" && continue
- am__include=`sed -n 's/^am__include = //p' < "$mf"`
- test -z "am__include" && continue
- am__quote=`sed -n 's/^am__quote = //p' < "$mf"`
- # When using ansi2knr, U may be empty or an underscore; expand it
- U=`sed -n 's/^U = //p' < "$mf"`
- # Find all dependency output files, they are included files with
- # $(DEPDIR) in their names. We invoke sed twice because it is the
- # simplest approach to changing $(DEPDIR) to its actual value in the
- # expansion.
- for file in `sed -n "
- s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \
- sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do
- # Make sure the directory exists.
- test -f "$dirpart/$file" && continue
- fdir=`$as_dirname -- "$file" ||
-$as_expr X"$file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$file" : 'X\(//\)[^/]' \| \
- X"$file" : 'X\(//\)$' \| \
- X"$file" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$file" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- { as_dir=$dirpart/$fdir
- case $as_dir in #(
- -*) as_dir=./$as_dir;;
- esac
- test -d "$as_dir" || { $as_mkdir_p && mkdir -p "$as_dir"; } || {
- as_dirs=
- while :; do
- case $as_dir in #(
- *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
- *) as_qdir=$as_dir;;
- esac
- as_dirs="'$as_qdir' $as_dirs"
- as_dir=`$as_dirname -- "$as_dir" ||
-$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$as_dir" : 'X\(//\)[^/]' \| \
- X"$as_dir" : 'X\(//\)$' \| \
- X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$as_dir" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- test -d "$as_dir" && break
- done
- test -z "$as_dirs" || eval "mkdir $as_dirs"
- } || test -d "$as_dir" || { { $as_echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5
-$as_echo "$as_me: error: cannot create directory $as_dir" >&2;}
- { (exit 1); exit 1; }; }; }
- # echo "creating $dirpart/$file"
- echo '# dummy' > "$dirpart/$file"
- done
-done
- ;;
- "default-1":C) for ac_file in $CONFIG_FILES; do
- # Support "outfile[:infile[:infile...]]"
- case "$ac_file" in
- *:*) ac_file=`echo "$ac_file"|sed 's%:.*%%'` ;;
- esac
- # PO directories have a Makefile.in generated from Makefile.in.in.
- case "$ac_file" in */Makefile.in)
- # Adjust a relative srcdir.
- ac_dir=`echo "$ac_file"|sed 's%/[^/][^/]*$%%'`
- ac_dir_suffix="/`echo "$ac_dir"|sed 's%^\./%%'`"
- ac_dots=`echo "$ac_dir_suffix"|sed 's%/[^/]*%../%g'`
- # In autoconf-2.13 it is called $ac_given_srcdir.
- # In autoconf-2.50 it is called $srcdir.
- test -n "$ac_given_srcdir" || ac_given_srcdir="$srcdir"
- case "$ac_given_srcdir" in
- .) top_srcdir=`echo $ac_dots|sed 's%/$%%'` ;;
- /*) top_srcdir="$ac_given_srcdir" ;;
- *) top_srcdir="$ac_dots$ac_given_srcdir" ;;
- esac
- if test -f "$ac_given_srcdir/$ac_dir/POTFILES.in"; then
- rm -f "$ac_dir/POTFILES"
- test -n "$as_me" && echo "$as_me: creating $ac_dir/POTFILES" || echo "creating $ac_dir/POTFILES"
- sed -e "/^#/d" -e "/^[ ]*\$/d" -e "s,.*, $top_srcdir/& \\\\," -e "\$s/\(.*\) \\\\/\1/" < "$ac_given_srcdir/$ac_dir/POTFILES.in" > "$ac_dir/POTFILES"
- test -n "$as_me" && echo "$as_me: creating $ac_dir/Makefile" || echo "creating $ac_dir/Makefile"
- sed -e "/POTFILES =/r $ac_dir/POTFILES" "$ac_dir/Makefile.in" > "$ac_dir/Makefile"
- fi
- ;;
- esac
- done ;;
-
- esac
-done # for ac_tag
-
-
-{ (exit 0); exit 0; }
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# contrib/Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-
-# $Id$
-VPATH = ../../contrib
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES =
-SOURCES =
-DIST_SOURCES =
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DHAVE_CONFIG_H
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/contrib
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/../contrib
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ../../contrib
-sysconfdir = /etc
-target_alias =
-top_build_prefix = ../
-top_builddir = ..
-top_srcdir = ../..
-subdir = contrib
-SAMPLES = Mush.rc Pine.rc gpg.rc pgp2.rc pgp5.rc pgp6.rc Tin.rc \
- sample.muttrc sample.mailcap sample.muttrc-tlr \
- colors.default colors.linux smime.rc \
- ca-bundle.crt smime_keys_test.pl mutt_xtitle
-
-EXTRA_DIST = language.txt language50.txt \
- patch.slang-1.2.2.keypad.1 \
- $(SAMPLES) \
- iconv/README \
- iconv/make.sh
-
-distdir = ../$(PACKAGE)-$(VERSION)/$(subdir)
-all: all-am
-
-.SUFFIXES:
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu contrib/Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --gnu contrib/Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-tags: TAGS
-TAGS:
-
-ctags: CTAGS
-CTAGS:
-
-
-distdir: $(DISTFILES)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
- $(MAKE) $(AM_MAKEFLAGS) \
- top_distdir="$(top_distdir)" distdir="$(distdir)" \
- dist-hook
-check-am: all-am
-check: check-am
-all-am: Makefile
-installdirs:
-install: install-am
-install-exec: install-exec-am
-install-data: install-data-am
-uninstall: uninstall-am
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-am
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
-clean: clean-am
-
-clean-am: clean-generic mostlyclean-am
-
-distclean: distclean-am
- -rm -f Makefile
-distclean-am: clean-am distclean-generic
-
-dvi: dvi-am
-
-dvi-am:
-
-html: html-am
-
-info: info-am
-
-info-am:
-
-install-data-am: install-data-local
-
-install-dvi: install-dvi-am
-
-install-exec-am:
-
-install-html: install-html-am
-
-install-info: install-info-am
-
-install-man:
-
-install-pdf: install-pdf-am
-
-install-ps: install-ps-am
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-am
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-am
-
-mostlyclean-am: mostlyclean-generic
-
-pdf: pdf-am
-
-pdf-am:
-
-ps: ps-am
-
-ps-am:
-
-uninstall-am: uninstall-local
-
-.MAKE: install-am install-strip
-
-.PHONY: all all-am check check-am clean clean-generic dist-hook \
- distclean distclean-generic distdir dvi dvi-am html html-am \
- info info-am install install-am install-data install-data-am \
- install-data-local install-dvi install-dvi-am install-exec \
- install-exec-am install-html install-html-am install-info \
- install-info-am install-man install-pdf install-pdf-am \
- install-ps install-ps-am install-strip installcheck \
- installcheck-am installdirs maintainer-clean \
- maintainer-clean-generic mostlyclean mostlyclean-generic pdf \
- pdf-am ps ps-am uninstall uninstall-am uninstall-local
-
-
-install-data-local:
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(docdir)/samples $(DESTDIR)$(docdir)/samples/iconv
- for f in $(SAMPLES) ; do \
- $(INSTALL) -m 644 $(srcdir)/$$f $(DESTDIR)$(docdir)/samples ; \
- done
- for f in $(srcdir)/iconv/*.rc ; do \
- $(INSTALL) -m 644 $$f $(DESTDIR)$(docdir)/samples/iconv ; \
- done
-
-uninstall-local:
- for f in $(SAMPLES) ; do \
- rm -f $(DESTDIR)$(docdir)/samples/$$f ; \
- done
- -rm -rf $(DESTDIR)$(docdir)/samples/iconv
- -rmdir $(DESTDIR)$(docdir)/samples
- -rmdir $(DESTDIR)$(docdir)
-dist-hook: Makefile $(DISTFILES)
- mkdir -p $(distdir)/iconv
- for file in $(srcdir)/iconv/*.rc ; do \
- ln $$file $(distdir)/iconv 2> /dev/null \
- || cp -p $$file $(distdir)/iconv ; \
- done
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# doc/Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-
-VPATH = ../../doc
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-noinst_PROGRAMS = makedoc$(EXEEXT)
-DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in \
- $(srcdir)/instdoc.sh.in TODO
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES = instdoc.sh
-PROGRAMS = $(noinst_PROGRAMS)
-makedoc_SOURCES = makedoc.c
-makedoc_OBJECTS = makedoc.$(OBJEXT)
-makedoc_LDADD = $(LDADD)
-DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)
-depcomp = $(SHELL) $(top_srcdir)/depcomp
-am__depfiles_maybe = depfiles
-COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
- $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
-CCLD = $(CC)
-LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
-SOURCES = makedoc.c
-DIST_SOURCES = makedoc.c
-ETAGS = etags
-CTAGS = ctags
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DSYSCONFDIR=\"$(sysconfdir)\" -DBINDIR=\"$(bindir)\" -DHAVE_CONFIG_H=1
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/doc
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/../doc
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ../../doc
-sysconfdir = /etc
-target_alias =
-top_build_prefix = ../
-top_builddir = ..
-top_srcdir = ../..
-subdir = doc
-AM_CPPFLAGS = -I. -I.. -I$(includedir) -I$(top_srcdir)
-MAKEDOC_CPP = $(CPP) $(AM_CPPFLAGS) $(DEFS) $(CPPFLAGS) -D_MAKEDOC -C
-EXTRA_DIST = dotlock.man \
- smime_keys.man \
- muttbug.man \
- mutt.man \
- PGP-Notes.txt \
- applying-patches.txt \
- devel-notes.txt \
- gen-map-doc \
- muttrc.man.head \
- muttrc.man.tail \
- mbox.man \
- mmdf.man \
- manual.xml.head \
- manual.xml.tail \
- instdoc.sh.in \
- patch-notes.txt \
- smime-notes.txt \
- Muttrc Muttrc.head stamp-doc-rc \
- makedoc.c makedoc-defs.h \
- mutt.css mutt.xsl html.xsl chunk.xsl $(BUILT_DISTFILES)
-
-HTML_DOCFILES = manual.html index.html intro.html gettingstarted.html \
- configuration.html mimesupport.html advancedusage.html \
- optionalfeatures.html tuning.html reference.html miscellany.html
-
-BUILT_DISTFILES = stamp-doc-xml stamp-doc-chunked manual.txt $(HTML_DOCFILES)
-srcdir_DOCFILES = PGP-Notes.txt applying-patches.txt \
- devel-notes.txt patch-notes.txt smime-notes.txt
-
-topsrcdir_DOCFILES = COPYRIGHT GPL INSTALL ChangeLog \
- README NEWS TODO README.SECURITY README.SSL
-
-DISTCLEANFILES = manual.txt manual.html manual.xml manual.pdf html \
- instdoc Muttrc
-
-EDIT = sed -e 's,@sysconfdir\@,$(sysconfdir),g' \
- -e 's,@bindir\@,$(bindir),g' \
- -e 's,@docdir\@,$(docdir),g'
-
-all: all-am
-
-.SUFFIXES:
-.SUFFIXES: .c .o .obj
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu doc/Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --gnu doc/Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-instdoc.sh: $(top_builddir)/config.status $(srcdir)/instdoc.sh.in
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
-
-clean-noinstPROGRAMS:
- -test -z "$(noinst_PROGRAMS)" || rm -f $(noinst_PROGRAMS)
-makedoc$(EXEEXT): $(makedoc_OBJECTS) $(makedoc_DEPENDENCIES)
- @rm -f makedoc$(EXEEXT)
- $(LINK) $(makedoc_OBJECTS) $(makedoc_LDADD) $(LIBS)
-
-mostlyclean-compile:
- -rm -f *.$(OBJEXT)
-
-distclean-compile:
- -rm -f *.tab.c
-
-#include ./$(DEPDIR)/makedoc.Po
-
-.c.o:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c $<
-
-.c.obj:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'`
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c `$(CYGPATH_W) '$<'`
-
-ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- mkid -fID $$unique
-tags: TAGS
-
-TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- here=`pwd`; \
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
- test -n "$$unique" || unique=$$empty_fix; \
- $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
- $$tags $$unique; \
- fi
-ctags: CTAGS
-CTAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- test -z "$(CTAGS_ARGS)$$tags$$unique" \
- || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
- $$tags $$unique
-
-GTAGS:
- here=`$(am__cd) $(top_builddir) && pwd` \
- && cd $(top_srcdir) \
- && gtags -i $(GTAGS_ARGS) $$here
-
-distclean-tags:
- -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
-distdir: $(DISTFILES)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
-check-am: all-am
-check: check-am
-all-am: Makefile $(PROGRAMS)
-installdirs:
-install: install-am
-install-exec: install-exec-am
-install-data: install-data-am
-uninstall: uninstall-am
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-am
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
- -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
-clean: clean-am
-
-clean-am: clean-generic clean-local clean-noinstPROGRAMS \
- mostlyclean-am
-
-distclean: distclean-am
- -rm -rf ./$(DEPDIR)
- -rm -f Makefile
-distclean-am: clean-am distclean-compile distclean-generic \
- distclean-tags
-
-dvi: dvi-am
-
-dvi-am:
-
-html: html-am
-
-info: info-am
-
-info-am:
-
-install-data-am: install-data-local
-
-install-dvi: install-dvi-am
-
-install-exec-am:
-
-install-html: install-html-am
-
-install-info: install-info-am
-
-install-man:
-
-install-pdf: install-pdf-am
-
-install-ps: install-ps-am
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-am
- -rm -rf ./$(DEPDIR)
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-am
-
-mostlyclean-am: mostlyclean-compile mostlyclean-generic
-
-pdf: pdf-am
-
-pdf-am:
-
-ps: ps-am
-
-ps-am:
-
-uninstall-am: uninstall-local
-
-.MAKE: install-am install-strip
-
-.PHONY: CTAGS GTAGS all all-am check check-am clean clean-generic \
- clean-local clean-noinstPROGRAMS ctags distclean \
- distclean-compile distclean-generic distclean-tags distdir dvi \
- dvi-am html html-am info info-am install install-am \
- install-data install-data-am install-data-local install-dvi \
- install-dvi-am install-exec install-exec-am install-html \
- install-html-am install-info install-info-am install-man \
- install-pdf install-pdf-am install-ps install-ps-am \
- install-strip installcheck installcheck-am installdirs \
- maintainer-clean maintainer-clean-generic mostlyclean \
- mostlyclean-compile mostlyclean-generic pdf pdf-am ps ps-am \
- tags uninstall uninstall-am uninstall-local
-
-
-all: makedoc-all
-
-makedoc-all: mutt.1 smime_keys.1 muttrc.man manual.html stamp-doc-rc stamp-doc-chunked manual.txt
-
-install-data-local: makedoc-all instdoc
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(mandir)/man1
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(mandir)/man5
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(sysconfdir)
- ./instdoc mutt.1 $(DESTDIR)$(mandir)/man1/mutt.1
- ./instdoc smime_keys.1 $(DESTDIR)$(mandir)/man1/smime_keys.1
- ./instdoc $(srcdir)/muttbug.man $(DESTDIR)$(mandir)/man1/flea.1
- ./instdoc $(srcdir)/muttbug.man $(DESTDIR)$(mandir)/man1/muttbug.1
- test xmutt_dotlock$(EXEEXT) = x || ./instdoc $(srcdir)/dotlock.man \
- $(DESTDIR)$(mandir)/man1/mutt_dotlock.1
- ./instdoc muttrc.man $(DESTDIR)$(mandir)/man5/muttrc.5
- ./instdoc $(srcdir)/mbox.man $(DESTDIR)$(mandir)/man5/mbox.5
- ./instdoc $(srcdir)/mmdf.man $(DESTDIR)$(mandir)/man5/mmdf.5
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(docdir)
- for f in $(topsrcdir_DOCFILES) ; do \
- $(INSTALL) -m 644 $(top_srcdir)/$$f $(DESTDIR)$(docdir) ; \
- done
- for f in $(srcdir_DOCFILES) ; do \
- $(INSTALL) -m 644 $(srcdir)/$$f $(DESTDIR)$(docdir) ; \
- done
- -$(INSTALL) -m 644 manual.txt $(DESTDIR)$(docdir)
- -for f in $(HTML_DOCFILES) ; do \
- $(INSTALL) -m 644 $$f $(DESTDIR)$(docdir) ; \
- done
- $(INSTALL) -m 644 Muttrc $(DESTDIR)$(sysconfdir)/Muttrc.dist
- -if [ -f $(DESTDIR)$(pkgdatadir)/Muttrc ] ; then \
- mv $(DESTDIR)$(pkgdatadir)/Muttrc* $(DESTDIR)$(sysconfdir) ; \
- elif [ -f $(DESTDIR)$(pkgdatadir)/../Muttrc ] ; then \
- mv $(DESTDIR)$(pkgdatadir)/../Muttrc* $(DESTDIR)$(sysconfdir) ; \
- elif [ ! -f $(DESTDIR)$(sysconfdir)/Muttrc ] ; then \
- $(INSTALL) -m 644 Muttrc $(DESTDIR)$(sysconfdir) ; \
- fi
-
-uninstall-local:
- for f in mutt.1 mutt_dotlock.1 flea.1 muttbug.1 smime_keys.1; do \
- rm -f $(DESTDIR)$(mandir)/man1/$$f ; \
- done
- for f in muttrc.5 mbox.5 mmdf.5 ; do \
- rm -f $(DESTDIR)$(mandir)/man5/$$f ; \
- done
- for f in $(srcdir_DOCFILES) $(topsrcdir_DOCFILES) $(HTML_DOCFILES) ; \
- do \
- rm -f $(DESTDIR)$(docdir)/$$f ; \
- done
- -rm -f $(DESTDIR)$(docdir)/manual.txt
- for i in Muttrc ; do \
- if cmp -s $(DESTDIR)$(sysconfdir)/$$i.dist $(DESTDIR)$(sysconfdir)/$$i ; then \
- rm $(DESTDIR)$(sysconfdir)/$$i ; \
- fi ; \
- rm $(DESTDIR)$(sysconfdir)/$${i}.dist ; \
- done
-
-check:
-manual.txt: manual.html
- links.main -dump $< > $@ || links -dump $< > $@ || \
- LC_ALL=C lynx -dump -nolist -with_backspaces manual.html > $@ || \
- LC_ALL=C w3m -dump manual.html > $@ || \
- LC_ALL=C elinks -dump -no-numbering -no-references manual.html | sed -e 's,\\001, ,g' > $@
-
-Muttrc: stamp-doc-rc
-
-stamp-doc-rc: $(top_srcdir)/init.h makedoc$(EXEEXT) $(srcdir)/Muttrc.head
- -rm -f Muttrc stamp-doc-rc
- sed -e 's,[@]docdir[@],$(docdir),' $(srcdir)/Muttrc.head > Muttrc
- $(CPP) $(AM_CPPFLAGS) $(DEFS) $(CPPFLAGS) -D_MAKEDOC -C \
- $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -c >> Muttrc
- touch stamp-doc-rc
-
-manual.html: $(srcdir)/html.xsl $(srcdir)/mutt.xsl stamp-doc-xml $(srcdir)/mutt.css
- xsltproc --nonet -o $@ $(srcdir)/html.xsl manual.xml
-
-stamp-doc-chunked: $(srcdir)/chunk.xsl $(srcdir)/mutt.xsl stamp-doc-xml $(srcdir)/mutt.css
- xsltproc --nonet $(srcdir)/chunk.xsl manual.xml
- touch stamp-doc-chunked
-
-$(HTML_DOCFILES): stamp-doc-chunked
-
-manual.pdf: manual.tex
- -if test -f manual.tex; then pdfjadetex manual.tex; fi
-
-manual.tex: stamp-doc-xml
- -if test -n "$(DSLROOT)"; then \
- openjade -t tex -D $(DSLROOT) -d print/docbook.dsl dtds/decls/xml.dcl manual.xml; \
- fi
-
-validate: stamp-doc-xml
- xmllint --noout --noblanks --postvalid manual.xml
-
-spellcheck:
- -aspell -l en --mode sgml -c manual.xml.head && \
- -aspell -l en --mode nroff -c muttrc.man.head
-
-clean-local:
- rm -f *~ *.html *.orig *.rej stamp-doc-* *.ps mutt.1 smime_keys.1 muttrc.man
- rm -f *.aux *.log *.tex *.out
-
-instdoc: instdoc.sh
- cat instdoc.sh > instdoc
- chmod a+x instdoc
-
-update-doc: stamp-doc-xml stamp-doc-chunked stamp-doc-rc manual.txt manual.html
-
-muttrc.man: makedoc$(EXEEXT) $(top_srcdir)/init.h muttrc.man.head muttrc.man.tail
- $(MAKEDOC_CPP) $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -m | \
- cat $(srcdir)/muttrc.man.head - $(srcdir)/muttrc.man.tail\
- > muttrc.man
-
-mutt.1: $(srcdir)/mutt.man
- $(EDIT) $(srcdir)/mutt.man > $@
-
-smime_keys.1: $(srcdir)/smime_keys.man
- $(EDIT) $(srcdir)/smime_keys.man > $@
-
-stamp-doc-xml: makedoc$(EXEEXT) $(top_srcdir)/init.h \
- manual.xml.head $(top_srcdir)/functions.h $(top_srcdir)/OPS* manual.xml.tail \
- $(srcdir)/gen-map-doc $(top_srcdir)/VERSION $(top_srcdir)/ChangeLog
- ( date=`head -n 1 $(top_srcdir)/ChangeLog | LC_ALL=C cut -d ' ' -f 1` && \
- sed -e "s/@VERSION\@/`cat $(top_srcdir)/VERSION` ($$date)/" $(srcdir)/manual.xml.head && \
- $(MAKEDOC_CPP) $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -s && \
- $(MAKEDOC_CPP) $(top_srcdir)/functions.h | \
- perl $(srcdir)/gen-map-doc $(srcdir)/manual.xml.tail $(top_srcdir)/OPS* \
- ) > manual.xml
- touch stamp-doc-xml
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-#
-# System configuration file for Mutt
-#
-
-# Default list of header fields to weed when displaying.
-# Ignore all lines by default...
-ignore *
-
-# ... then allow these through.
-unignore from: subject to cc date x-mailer x-url user-agent
-
-# Display the fields in this order
-hdr_order date from to cc subject
-
-# emacs-like bindings
-bind editor "\e<delete>" kill-word
-bind editor "\e<backspace>" kill-word
-
-# map delete-char to a sane value
-bind editor <delete> delete-char
-
-# some people actually like these settings
-#set pager_stop
-#bind pager <up> previous-line
-#bind pager <down> next-line
-
-# Specifies how to sort messages in the index menu.
-set sort=threads
-
-# Uncomment if your MTA does not strip Bcc: headers.
-# (exim4 and postfix strip them, exim(3) does not.)
-#unset write_bcc
-# Postfix and qmail use Delivered-To for detecting loops
-unset bounce_delivered
-
-set mixmaster="mixmaster-filter"
-
-# System-wide CA file managed by the ca-certificates package
-set ssl_ca_certificates_file="/etc/ssl/certs/ca-certificates.crt"
-
-# imitate the old search-body function
-macro index \eb "<search>~b " "search in message bodies"
-
-# simulate the old url menu
-macro index,pager,attach,compose \cb "\
-<enter-command> set my_pipe_decode=\$pipe_decode pipe_decode<Enter>\
-<pipe-message> urlview<Enter>\
-<enter-command> set pipe_decode=\$my_pipe_decode; unset my_pipe_decode<Enter>" \
-"call urlview to extract URLs out of a message"
-
-# Show documentation when pressing F1
-macro generic,pager <F1> "<shell-escape> zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager<enter>" "show Mutt documentation"
-
-# show the incoming mailboxes list (just like "mutt -y") and back when pressing "y"
-macro index,pager y "<change-folder>?<toggle-mailboxes>" "show incoming mailboxes list"
-bind browser y exit
-
-# Use folders which match on \\.gz$ as gzipped folders:
-# open-hook \\.gz$ "gzip -cd %f > %t"
-# close-hook \\.gz$ "gzip -c %t > %f"
-# append-hook \\.gz$ "gzip -c %t >> %f"
-
-# If Mutt is unable to determine your site's domain name correctly, you can
-# set the default here. (better: fix /etc/mailname)
-#
-# set hostname=cs.hmc.edu
-
-# If your sendmail supports the -B8BITMIME flag, enable the following
-#
-# set use_8bitmime
-
-# Use mime.types to look up handlers for application/octet-stream. Can
-# be undone with unmime_lookup.
-mime_lookup application/octet-stream
-
-##
-## *** DEFAULT SETTINGS FOR THE ATTACHMENTS PATCH ***
-##
-
-##
-## Please see the manual (section "attachments") for detailed
-## documentation of the "attachments" command.
-##
-## 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
-
-# enable mime lookup by extension
-mime_lookup application/octet-stream
-
-##
-## More settings
-##
-
-
-# set abort_nosubject=ask-yes
-#
-# Name: abort_nosubject
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# If set to yes, when composing messages and no subject is given
-# at the subject prompt, composition will be aborted. If set to
-# no, composing messages with no subject given at the subject
-# prompt will never be aborted.
-#
-#
-# set abort_unmodified=yes
-#
-# Name: abort_unmodified
-# Type: quadoption
-# Default: yes
-#
-#
-# If set to yes, composition will automatically abort after
-# editing the message body if no changes are made to the file (this
-# check only happens after the first edit of the file). When set
-# to no, composition will never be aborted.
-#
-#
-# set alias_file="~/.muttrc"
-#
-# Name: alias_file
-# Type: path
-# Default: "~/.muttrc"
-#
-#
-# The default file in which to save aliases created by the
-# <create-alias> function. Entries added to this file are
-# encoded in the character set specified by $config_charset if it
-# is set or the current character set otherwise.
-#
-# Note: Mutt will not automatically source this file; you must
-# explicitly use the ``source'' command for it to be executed in case
-# this option points to a dedicated alias file.
-#
-# The default for this option is the currently used muttrc file, or
-# ``~/.muttrc'' if no user muttrc was found.
-#
-#
-# set alias_format="%4n %2f %t %-10a %r"
-#
-# Name: alias_format
-# Type: string
-# Default: "%4n %2f %t %-10a %r"
-#
-#
-# Specifies the format of the data displayed for the ``alias'' menu. The
-# following printf(3)-style sequences are available:
-# %a alias name
-# %f flags - currently, a ``d'' for an alias marked for deletion
-# %n index number
-# %r address which alias expands to
-# %t character which indicates if the alias is tagged for inclusion
-#
-#
-# set allow_8bit=yes
-#
-# Name: allow_8bit
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether 8-bit data is converted to 7-bit using either Quoted-
-# Printable or Base64 encoding when sending mail.
-#
-#
-# set allow_ansi=no
-#
-# Name: allow_ansi
-# Type: boolean
-# Default: no
-#
-#
-# Controls whether ANSI color codes in messages (and color tags in
-# rich text messages) are to be interpreted.
-# Messages containing these codes are rare, but if this option is set,
-# their text will be colored accordingly. Note that this may override
-# your color choices, and even present a security problem, since a
-# message could include a line like
-# [-- PGP output follows ...
-#
-# and give it the same color as your attachment color (see also
-# $crypt_timestamp).
-#
-#
-# set arrow_cursor=no
-#
-# Name: arrow_cursor
-# Type: boolean
-# Default: no
-#
-#
-# When set, an arrow (``->'') will be used to indicate the current entry
-# in menus instead of highlighting the whole line. On slow network or modem
-# links this will make response faster because there is less that has to
-# be redrawn on the screen when moving to the next or previous entries
-# in the menu.
-#
-#
-# set ascii_chars=no
-#
-# Name: ascii_chars
-# Type: boolean
-# Default: no
-#
-#
-# If set, Mutt will use plain ASCII characters when displaying thread
-# and attachment trees, instead of the default ACS characters.
-#
-#
-# set askbcc=no
-#
-# Name: askbcc
-# Type: boolean
-# Default: no
-#
-#
-# If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
-# before editing an outgoing message.
-#
-#
-# set askcc=no
-#
-# Name: askcc
-# Type: boolean
-# Default: no
-#
-#
-# If set, Mutt will prompt you for carbon-copy (Cc) recipients before
-# editing the body of an outgoing message.
-#
-#
-# set assumed_charset=""
-#
-# Name: assumed_charset
-# Type: string
-# Default: ""
-#
-#
-# This variable is a colon-separated list of character encoding
-# schemes for messages without character encoding indication.
-# Header field values and message body content without character encoding
-# indication would be assumed that they are written in one of this list.
-# By default, all the header fields and message body without any charset
-# indication are assumed to be in ``us-ascii''.
-#
-# For example, Japanese users might prefer this:
-# set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-#
-# However, only the first content is valid for the message body.
-#
-#
-# set attach_charset=""
-#
-# Name: attach_charset
-# Type: string
-# Default: ""
-#
-#
-# This variable is a colon-separated list of character encoding
-# schemes for text file attachments. Mutt uses this setting to guess
-# which encoding files being attached are encoded in to convert them to
-# a proper character set given in $send_charset.
-#
-# If unset, the value of $charset will be used instead.
-# For example, the following configuration would work for Japanese
-# text handling:
-# set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-#
-# Note: for Japanese users, ``iso-2022-*'' must be put at the head
-# of the value as shown above if included.
-#
-#
-# set attach_format="%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
-#
-# Name: attach_format
-# Type: string
-# Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
-#
-#
-# This variable describes the format of the ``attachment'' menu. The
-# following printf(3)-style sequences are understood:
-# %C charset
-# %c requires charset conversion (``n'' or ``c'')
-# %D deleted flag
-# %d description
-# %e MIME content-transfer-encoding
-# %f filename
-# %I disposition (``I'' for inline, ``A'' for attachment)
-# %m major MIME type
-# %M MIME subtype
-# %n attachment number
-# %Q ``Q'', if MIME part qualifies for attachment counting
-# %s size
-# %t tagged flag
-# %T graphic tree characters
-# %u unlink (=to delete) flag
-# %X number of qualifying MIME parts in this part and its children
-# (please see the ``attachments'' section for possible speed effects)
-# %>X right justify the rest of the string and pad with character ``X''
-# %|X pad to the end of the line with character ``X''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# For an explanation of ``soft-fill'', see the $index_format documentation.
-#
-#
-# set attach_sep="\n"
-#
-# Name: attach_sep
-# Type: string
-# Default: "\n"
-#
-#
-# The separator to add between attachments when operating (saving,
-# printing, piping, etc) on a list of tagged attachments.
-#
-#
-# set attach_split=yes
-#
-# Name: attach_split
-# Type: boolean
-# Default: yes
-#
-#
-# If this variable is unset, when operating (saving, printing, piping,
-# etc) on a list of tagged attachments, Mutt 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 will operate on the attachments one by one.
-#
-#
-# set attribution="On %d, %n wrote:"
-#
-# Name: attribution
-# Type: string
-# Default: "On %d, %n wrote:"
-#
-#
-# This is the string that will precede a message which has been included
-# in a reply. For a full listing of defined printf(3)-like sequences see
-# the section on $index_format.
-#
-#
-# set autoedit=no
-#
-# Name: autoedit
-# Type: boolean
-# Default: no
-#
-#
-# When set along with $edit_headers, Mutt will skip the initial
-# send-menu (prompting for subject and recipients) and allow you to
-# immediately begin editing the body of your
-# message. The send-menu may still be accessed once you have finished
-# editing the body of your message.
-#
-# Also see $fast_reply.
-#
-#
-# set auto_tag=no
-#
-# Name: auto_tag
-# Type: boolean
-# Default: no
-#
-#
-# When set, functions in the index menu which affect a message
-# will be applied to all tagged messages (if there are any). When
-# unset, you must first use the <tag-prefix> function (bound to ``;''
-# by default) to make the next function apply to all tagged messages.
-#
-#
-# set beep=yes
-#
-# Name: beep
-# Type: boolean
-# Default: yes
-#
-#
-# When this variable is set, mutt will beep when an error occurs.
-#
-#
-# set beep_new=no
-#
-# Name: beep_new
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, mutt will beep whenever it prints a message
-# notifying you of new mail. This is independent of the setting of the
-# $beep variable.
-#
-#
-# set bounce=ask-yes
-#
-# Name: bounce
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# Controls whether you will be asked to confirm bouncing messages.
-# If set to yes you don't get asked if you want to bounce a
-# message. Setting this variable to no is not generally useful,
-# and thus not recommended, because you are unable to bounce messages.
-#
-#
-# set bounce_delivered=yes
-#
-# Name: bounce_delivered
-# Type: boolean
-# Default: yes
-#
-#
-# When this variable is set, mutt will include Delivered-To headers when
-# bouncing messages. Postfix users may wish to unset this variable.
-#
-# Note: On Debian systems, this option is unset by default in
-# /etc/Muttrc.
-#
-#
-# set braille_friendly=no
-#
-# Name: braille_friendly
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, mutt will place the cursor at the beginning
-# of the current line in menus, even when the $arrow_cursor variable
-# is unset, making it easier for blind persons using Braille displays to
-# follow these menus. The option is unset by default because many
-# visual terminals don't permit making the cursor invisible.
-#
-#
-# set check_mbox_size=no
-#
-# Name: check_mbox_size
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, mutt will use file size attribute instead of
-# access time when checking for new mail in mbox and mmdf folders.
-#
-# This variable is unset by default and should only be enabled when
-# new mail detection for these folder types is unreliable or doesn't work.
-#
-# Note that enabling this variable should happen before any ``mailboxes''
-# directives occur in configuration files regarding mbox or mmdf folders
-# because mutt needs to determine the initial new mail status of such a
-# mailbox by performing a fast mailbox scan when it is defined.
-# Afterwards the new mail status is tracked by file size changes.
-#
-#
-# set charset=""
-#
-# Name: charset
-# Type: string
-# Default: ""
-#
-#
-# Character set your terminal uses to display and enter textual data.
-# It is also the fallback for $send_charset.
-#
-# Upon startup Mutt tries to derive this value from environment variables
-# such as $LC_CTYPE or $LANG.
-#
-# Note: It should only be set in case Mutt isn't abled to determine the
-# character set used correctly.
-#
-#
-# set check_new=yes
-#
-# Name: check_new
-# Type: boolean
-# Default: yes
-#
-#
-# Note: this option only affects maildir and MH style
-# mailboxes.
-#
-# When set, Mutt 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
-# this variable is unset, no check for new mail is performed
-# while the mailbox is open.
-#
-#
-# set collapse_unread=yes
-#
-# Name: collapse_unread
-# Type: boolean
-# Default: yes
-#
-#
-# When unset, Mutt will not collapse a thread if it contains any
-# unread messages.
-#
-#
-# set uncollapse_jump=no
-#
-# Name: uncollapse_jump
-# Type: boolean
-# Default: no
-#
-#
-# When set, Mutt will jump to the next unread message, if any,
-# when the current thread is uncollapsed.
-#
-#
-# set compose_format="-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-"
-#
-# Name: compose_format
-# Type: string
-# Default: "-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-"
-#
-#
-# Controls the format of the status line displayed in the ``compose''
-# menu. This string is similar to $status_format, but has its own
-# set of printf(3)-like sequences:
-# %a total number of attachments
-# %h local hostname
-# %l approximate size (in bytes) of the current message
-# %v Mutt version string
-#
-#
-# See the text describing the $status_format option for more
-# information on how to set $compose_format.
-#
-#
-# set config_charset=""
-#
-# Name: config_charset
-# Type: string
-# Default: ""
-#
-#
-# When defined, Mutt will recode commands in rc files from this
-# encoding to the current character set as specified by $charset
-# and aliases written to $alias_file from the current character set.
-#
-# Please note that if setting $charset it must be done before
-# setting $config_charset.
-#
-# Recoding should be avoided as it may render unconvertable
-# characters as question marks which can lead to undesired
-# side effects (for example in regular expressions).
-#
-#
-# set confirmappend=yes
-#
-# Name: confirmappend
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will prompt for confirmation when appending messages to
-# an existing mailbox.
-#
-#
-# set confirmcreate=yes
-#
-# Name: confirmcreate
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will prompt for confirmation when saving messages to a
-# mailbox which does not yet exist before creating it.
-#
-#
-# set connect_timeout=30
-#
-# Name: connect_timeout
-# Type: number
-# Default: 30
-#
-#
-# Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-# many seconds if the connection is not able to be established. A negative
-# value causes Mutt to wait indefinitely for the connection attempt to succeed.
-#
-#
-# set content_type="text/plain"
-#
-# Name: content_type
-# Type: string
-# Default: "text/plain"
-#
-#
-# Sets the default Content-Type for the body of newly composed messages.
-#
-#
-# set copy=yes
-#
-# Name: copy
-# Type: quadoption
-# Default: yes
-#
-#
-# 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''.
-#
-#
-# set crypt_use_gpgme=no
-#
-# Name: crypt_use_gpgme
-# Type: boolean
-# Default: no
-#
-#
-# This variable controls the use of the GPGME-enabled crypto backends.
-# If it is set and Mutt was built with gpgme support, the gpgme code for
-# S/MIME and PGP will be used instead of the classic code. Note that
-# you need to set this option in .muttrc; it won't have any effect when
-# used interactively.
-#
-#
-# set crypt_use_pka=no
-#
-# Name: crypt_use_pka
-# Type: boolean
-# Default: no
-#
-#
-# Controls whether mutt uses PKA
-# (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
-# verification (only supported by the GPGME backend).
-#
-#
-# set crypt_autopgp=yes
-#
-# Name: crypt_autopgp
-# Type: boolean
-# Default: yes
-#
-#
-# This variable controls whether or not mutt may automatically enable
-# PGP encryption/signing for messages. See also $crypt_autoencrypt,
-# $crypt_replyencrypt,
-# $crypt_autosign, $crypt_replysign and $smime_is_default.
-#
-#
-# set crypt_autosmime=yes
-#
-# Name: crypt_autosmime
-# Type: boolean
-# Default: yes
-#
-#
-# This variable controls whether or not mutt may automatically enable
-# S/MIME encryption/signing for messages. See also $crypt_autoencrypt,
-# $crypt_replyencrypt,
-# $crypt_autosign, $crypt_replysign and $smime_is_default.
-#
-#
-# set date_format="!%a, %b %d, %Y at %I:%M:%S%p %Z"
-#
-# Name: date_format
-# Type: string
-# Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
-#
-#
-# This variable controls the format of the date printed by the ``%d''
-# sequence in $index_format. This is passed to the strftime(3)
-# function to process the date, see the man page for the proper syntax.
-#
-# 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).
-#
-#
-# set default_hook="~f %s !~P | (~P ~C %s)"
-#
-# Name: default_hook
-# Type: string
-# Default: "~f %s !~P | (~P ~C %s)"
-#
-#
-# This variable controls how ``message-hook'', ``reply-hook'', ``send-hook'',
-# ``send2-hook'', ``save-hook'', and ``fcc-hook'' 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.
-#
-#
-# set delete=ask-yes
-#
-# Name: delete
-# 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.
-#
-#
-# set delete_untag=yes
-#
-# Name: delete_untag
-# Type: boolean
-# Default: yes
-#
-#
-# If this option is set, mutt 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.
-#
-#
-# set digest_collapse=yes
-#
-# Name: digest_collapse
-# Type: boolean
-# Default: yes
-#
-#
-# If this option is set, mutt'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.
-#
-#
-# set display_filter=""
-#
-# Name: display_filter
-# Type: path
-# 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.
-#
-#
-# set dotlock_program="/usr/bin/mutt_dotlock"
-#
-# Name: dotlock_program
-# Type: path
-# Default: "/usr/bin/mutt_dotlock"
-#
-#
-# Contains the path of the mutt_dotlock(8) binary to be used by
-# mutt.
-#
-#
-# set dsn_notify=""
-#
-# Name: dsn_notify
-# Type: string
-# Default: ""
-#
-#
-# 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.
-#
-# Example:
-# set dsn_notify="failure,delay"
-#
-# Note: when using $sendmail for delivery, you should not enable
-# this unless you are either using Sendmail 8.8.x or greater or a MTA
-# providing a sendmail(1)-compatible interface supporting the -N option
-# for DSN. For SMTP delivery, DSN support is autodetected so that it
-# depends on the server whether DSN will be used or not.
-#
-#
-# set dsn_return=""
-#
-# Name: dsn_return
-# Type: string
-# Default: ""
-#
-#
-# 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.
-#
-# Example:
-# set dsn_return=hdrs
-#
-# Note: when using $sendmail for delivery, you should not enable
-# this unless you are either using Sendmail 8.8.x or greater or a MTA
-# providing a sendmail(1)-compatible interface supporting the -R option
-# for DSN. For SMTP delivery, DSN support is autodetected so that it
-# depends on the server whether DSN will be used or not.
-#
-#
-# set duplicate_threads=yes
-#
-# Name: duplicate_threads
-# Type: boolean
-# Default: yes
-#
-#
-# This variable controls whether mutt, when $sort is set to threads, threads
-# messages with the same Message-Id together. If it is set, it will indicate
-# that it thinks they are duplicates of each other with an equals sign
-# in the thread tree.
-#
-#
-# set edit_headers=no
-#
-# Name: edit_headers
-# Type: boolean
-# Default: no
-#
-#
-# This option allows you to edit the header of your outgoing messages
-# along with the body of your message.
-#
-# Note that changes made to the References: and Date: headers are
-# ignored for interoperability reasons.
-#
-#
-# set editor=""
-#
-# Name: editor
-# Type: path
-# Default: ""
-#
-#
-# This variable specifies which editor is used by mutt.
-# It defaults to the value of the $VISUAL, or $EDITOR, environment
-# variable, or to the string ``/usr/bin/editor'' if neither of those are set.
-#
-#
-# set encode_from=no
-#
-# Name: encode_from
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will quoted-printable encode messages when
-# they contain the string ``From '' (note the trailing space) in the beginning of a line.
-# This is useful to avoid the tampering certain mail delivery and transport
-# agents tend to do with messages (in order to prevent tools from
-# misinterpreting the line as a mbox message separator).
-#
-#
-# set envelope_from_address=""
-#
-# Name: envelope_from_address
-# Type: e-mail address
-# Default: ""
-#
-#
-# Manually sets the envelope sender for outgoing messages.
-# This value is ignored if $use_envelope_from is unset.
-#
-#
-# set escape="~"
-#
-# Name: escape
-# Type: string
-# Default: "~"
-#
-#
-# Escape character to use for functions in the builtin editor.
-#
-#
-# set fast_reply=no
-#
-# Name: fast_reply
-# Type: boolean
-# Default: no
-#
-#
-# 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.
-#
-# Note: this variable has no effect when the $autoedit
-# variable is set.
-#
-#
-# set fcc_attach=yes
-#
-# Name: fcc_attach
-# Type: boolean
-# Default: yes
-#
-#
-# This variable controls whether or not attachments on outgoing messages
-# are saved along with the main body of your message.
-#
-#
-# set fcc_clear=no
-#
-# Name: fcc_clear
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, FCCs will be stored unencrypted and
-# unsigned, even when the actual message is encrypted and/or
-# signed.
-# (PGP only)
-#
-#
-# set folder="~/Mail"
-#
-# Name: folder
-# Type: path
-# Default: "~/Mail"
-#
-#
-# 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
-# when handling the ``mailboxes'' command.
-#
-#
-# set folder_format="%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
-#
-# Name: folder_format
-# Type: string
-# Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
-#
-#
-# 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:
-# %C current file number
-# %d date/time folder was last modified
-# %f filename
-# %F file permissions
-# %g group name (or numeric gid, if missing)
-# %l number of hard links
-# %N N if folder has new mail, blank otherwise
-# %s size in bytes
-# %t ``*'' 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''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# For an explanation of ``soft-fill'', see the $index_format documentation.
-#
-#
-# set followup_to=yes
-#
-# Name: followup_to
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether or not the ``Mail-Followup-To:'' header field is
-# generated when sending mail. When set, Mutt will generate this
-# field when you are replying to a known mailing list, specified with
-# the ``subscribe'' or ``lists'' commands.
-#
-# This field has two purposes. First, preventing you from
-# receiving duplicate copies of replies to messages which you send
-# to mailing lists, and 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.
-#
-#
-# set force_name=no
-#
-# Name: force_name
-# Type: boolean
-# Default: no
-#
-#
-# This variable is similar to $save_name, except that Mutt 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.
-#
-#
-# set forward_decode=yes
-#
-# Name: forward_decode
-# Type: boolean
-# Default: yes
-#
-#
-# 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.
-#
-#
-# set forward_edit=yes
-#
-# Name: 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''.
-#
-#
-# set forward_format="[%a: %s]"
-#
-# Name: forward_format
-# 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.
-#
-#
-# set forward_quote=no
-#
-# Name: 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.
-#
-#
-# set from=""
-#
-# Name: from
-# Type: e-mail address
-# Default: ""
-#
-#
-# When set, this variable contains a default from address. It
-# can be overridden using ``my_hdr'' (including from a ``send-hook'') and
-# $reverse_name. This variable is ignored if $use_from is unset.
-#
-# This setting defaults to the contents of the environment variable $EMAIL.
-#
-#
-# set gecos_mask="^[^,]*"
-#
-# Name: gecos_mask
-# Type: regular expression
-# Default: "^[^,]*"
-#
-#
-# A regular expression used by mutt to parse the GECOS field of a password
-# entry when expanding the alias. The default value
-# will return the string up to the first ``,'' encountered.
-# If the GECOS field contains a string like ``lastname, firstname'' then you
-# should set it to ``.*''.
-#
-# This can be useful if you see the following behavior: you address an e-mail
-# to user ID ``stevef'' whose full name is ``Steve Franklin''. If mutt 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 will expand
-# ``Franklin'' to ``Franklin, Steve''.
-#
-#
-# set hdrs=yes
-#
-# Name: 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.
-#
-#
-# set header=no
-#
-# Name: header
-# Type: boolean
-# Default: no
-#
-#
-# When set, this variable causes Mutt to include the header
-# of the message you are replying to into the edit buffer.
-# The $weed setting applies.
-#
-#
-# set help=yes
-#
-# Name: 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 is
-# running. Since this variable is primarily aimed at new users, neither
-# of these should present a major problem.
-#
-#
-# set hidden_host=no
-#
-# Name: hidden_host
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt 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-IDs, and it will not lead to the
-# cut-off of first-level domains.
-#
-#
-# set hide_limited=no
-#
-# Name: hide_limited
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will not show the presence of messages that are hidden
-# by limiting, in the thread tree.
-#
-#
-# set hide_missing=yes
-#
-# Name: hide_missing
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will not show the presence of missing messages in the
-# thread tree.
-#
-#
-# set hide_thread_subject=yes
-#
-# Name: hide_thread_subject
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will not show the subject of messages in the thread
-# tree that have the same subject as their parent or closest previously
-# displayed sibling.
-#
-#
-# set hide_top_limited=no
-#
-# Name: hide_top_limited
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt 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_limited is set, this option will have no effect.
-#
-#
-# set hide_top_missing=yes
-#
-# Name: hide_top_missing
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will not show the presence of missing messages at the
-# top of threads in the thread tree. Note that when $hide_missing is
-# set, this option will have no effect.
-#
-#
-# set history=10
-#
-# Name: history
-# Type: number
-# Default: 10
-#
-#
-# This variable controls the size (in number of strings remembered) of
-# the string history buffer per category. The buffer is cleared each time the
-# variable is set.
-#
-#
-# set history_file="~/.mutthistory"
-#
-# Name: history_file
-# Type: path
-# Default: "~/.mutthistory"
-#
-#
-# The file in which Mutt will save its history.
-#
-#
-# set honor_followup_to=yes
-#
-# Name: honor_followup_to
-# Type: quadoption
-# Default: yes
-#
-#
-# This variable controls whether or not a Mail-Followup-To header is
-# honored when group-replying to a message.
-#
-#
-# set hostname=""
-#
-# Name: hostname
-# Type: string
-# Default: ""
-#
-#
-# Specifies the fully-qualified hostname of the system mutt is running on
-# containing the host's name and the DNS domain it belongs to. It is used
-# as the domain part (after ``@'') for local email addresses as well as
-# Message-Id headers.
-#
-# Its value is determined at startup as follows: If the node's name
-# as returned by the uname(3) function contains the hostname and the
-# domain, these are used to construct $hostname. If there is no
-# domain part returned, Mutt will look for a ``domain'' or ``search''
-# line in /etc/resolv.conf to determine the domain. Optionally, Mutt
-# can be compiled with a fixed domain name in which case a detected
-# one is not used.
-#
-# Also see $use_domain and $hidden_host.
-#
-# Note: On Debian systems, the default for this variable is obtained
-# from /etc/mailname when Mutt starts.
-#
-#
-# set ignore_linear_white_space=no
-#
-# Name: ignore_linear_white_space
-# Type: boolean
-# Default: no
-#
-#
-# This option replaces linear-white-space between encoded-word
-# and text to a single space to prevent the display of MIME-encoded
-# ``Subject:'' field from being divided into multiple lines.
-#
-#
-# set ignore_list_reply_to=no
-#
-# Name: ignore_list_reply_to
-# Type: boolean
-# Default: no
-#
-#
-# Affects the behaviour of the <reply> function when replying to
-# messages from mailing lists (as defined by the ``subscribe'' or
-# ``lists'' commands). When set, if the ``Reply-To:'' field is
-# set to the same value as the ``To:'' field, Mutt assumes that the
-# ``Reply-To:'' 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.
-#
-#
-# set imap_authenticators=""
-#
-# Name: imap_authenticators
-# Type: string
-# Default: ""
-#
-#
-# This is a colon-delimited list of authentication methods mutt may
-# attempt to use to log in to an IMAP server, in the order mutt should
-# try them. Authentication methods are either ``login'' or the right
-# side of an IMAP ``AUTH=xxx'' capability string, eg ``digest-md5'', ``gssapi''
-# or ``cram-md5''. This option is case-insensitive. If it's
-# unset (the default) mutt will try all available methods,
-# in order from most-secure to least-secure.
-#
-# Example:
-# set imap_authenticators="gssapi:cram-md5:login"
-#
-# Note: Mutt will only fall back to other authentication methods if
-# the previous methods are unavailable. If a method is available but
-# authentication fails, mutt will not connect to the IMAP server.
-#
-#
-# set imap_check_subscribed=no
-#
-# Name: imap_check_subscribed
-# 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 just as if you had issued individual ``mailboxes''
-# commands.
-#
-#
-# set imap_delim_chars="/."
-#
-# Name: imap_delim_chars
-# Type: string
-# Default: "/."
-#
-#
-# 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.
-#
-#
-# set imap_headers=""
-#
-# Name: imap_headers
-# Type: string
-# Default: ""
-#
-#
-# Mutt 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:'', ``List-Post:'', ``X-Label:'') from IMAP
-# servers before displaying the index menu. You may want to add more
-# headers for spam detection.
-#
-# Note: This is a space separated list, items should be uppercase
-# and not contain the colon, e.g. ``X-BOGOSITY X-SPAM-STATUS'' for the
-# ``X-Bogosity:'' and ``X-Spam-Status:'' header fields.
-#
-#
-# set imap_idle=no
-#
-# Name: imap_idle
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will attempt to use the IMAP IDLE extension
-# to check for new mail in the current mailbox. Some servers
-# (dovecot was the inspiration for this option) react badly
-# to mutt's implementation. If your connection seems to freeze
-# up periodically, try unsetting this.
-#
-#
-# set imap_keepalive=900
-#
-# Name: imap_keepalive
-# Type: number
-# Default: 900
-#
-#
-# This variable specifies the maximum amount of time in seconds that mutt
-# will wait before polling open IMAP connections, to prevent the server
-# from closing them before mutt 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.
-#
-#
-# set imap_list_subscribed=no
-#
-# Name: imap_list_subscribed
-# Type: boolean
-# Default: no
-#
-#
-# 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.
-#
-#
-# set imap_login=""
-#
-# Name: imap_login
-# Type: string
-# Default: ""
-#
-#
-# Your login name on the IMAP server.
-#
-# This variable defaults to the value of $imap_user.
-#
-#
-# set imap_pass=""
-#
-# Name: imap_pass
-# Type: string
-# Default: ""
-#
-#
-# Specifies the password for your IMAP account. If unset, Mutt will
-# prompt you for your password when you invoke the <fetch-mail> function
-# or try to open an IMAP folder.
-#
-# Warning: you should only use this option when you are on a
-# fairly secure machine, because the superuser can read your muttrc even
-# if you are the only one who can read the file.
-#
-#
-# set imap_passive=yes
-#
-# Name: imap_passive
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will not open new IMAP connections to check for new
-# mail. Mutt 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 invocation, or if opening the connection
-# is slow.
-#
-#
-# set imap_peek=yes
-#
-# Name: imap_peek
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt 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.
-#
-#
-# set imap_pipeline_depth=15
-#
-# Name: imap_pipeline_depth
-# Type: number
-# Default: 15
-#
-#
-# Controls the number of IMAP commands that may be queued up before they
-# are sent to the server. A deeper pipeline reduces the amount of time
-# mutt must wait for the server, and can make IMAP servers feel much
-# more responsive. But not all servers correctly handle pipelined commands,
-# so if you have problems you might want to try setting this variable to 0.
-#
-# Note: Changes to this variable have no effect on open connections.
-#
-#
-# set imap_servernoise=yes
-#
-# Name: imap_servernoise
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt 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.
-#
-#
-# set imap_user=""
-#
-# Name: imap_user
-# Type: string
-# Default: ""
-#
-#
-# 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.
-#
-#
-# set implicit_autoview=no
-#
-# Name: implicit_autoview
-# Type: boolean
-# Default: no
-#
-#
-# If set to ``yes'', mutt 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 will
-# use the viewer defined in that entry to convert the body part to text
-# form.
-#
-#
-# set include=ask-yes
-#
-# Name: 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.
-#
-#
-# set include_onlyfirst=no
-#
-# Name: include_onlyfirst
-# Type: boolean
-# Default: no
-#
-#
-# Controls whether or not Mutt includes only the first attachment
-# of the message you are replying.
-#
-#
-# set indent_string="> "
-#
-# Name: 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.
-#
-# This option is a format string, please see the description of
-# $index_format for supported printf(3)-style sequences.
-#
-# Because for format=lowed style messages the quoting mechanism
-# is strictly defined, this setting is ignored if $text_flowed is
-# set.
-#
-#
-# set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"
-#
-# Name: 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 details).
-# The following sequences are defined in Mutt:
-# %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 sender (address + real name), either From: or Return-Path:
-# %F author name, or recipient name if the message is from you
-# %H spam attribute(s) of this message
-# %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 original save folder where mutt would formerly have
-# stashed the message: list name or recipient name
-# if not sent to a list
-# %P progress indicator for the builtin pager (how much of the file has been displayed)
-# %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
-# %X number of attachments
-# (please see the ``attachments'' section for possible speed effects)
-# %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(3); 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(3); a leading bang disables locales
-# %(fmt) the local date and time when the message was received.
-# ``fmt'' is expanded by the library function strftime(3);
-# a leading bang disables locales
-# %<fmt> the current local time. ``fmt'' is expanded by the library
-# function strftime(3); 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''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# ``Soft-fill'' deserves some explanation: Normal right-justification
-# will print everything to the left of the ``%>'', displaying padding and
-# whatever lies to the right only if there's room. By contrast,
-# soft-fill gives priority to the right-hand side, guaranteeing space
-# to display it and showing padding only if there's still room. If
-# necessary, soft-fill will eat text leftwards to make room for
-# rightward text.
-#
-# Note that these expandos are supported in
-# ``save-hook'', ``fcc-hook'' and ``fcc-save-hook'', too.
-#
-#
-# set ispell="ispell"
-#
-# Name: ispell
-# Type: path
-# Default: "ispell"
-#
-#
-# How to invoke ispell (GNU's spell-checking software).
-#
-#
-# set keep_flagged=no
-#
-# Name: 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.
-#
-#
-# set locale="C"
-#
-# Name: 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 environment variable $LC_TIME.
-#
-#
-# set mail_check=5
-#
-# Name: mail_check
-# Type: number
-# Default: 5
-#
-#
-# This variable configures how often (in seconds) mutt should look for
-# new mail. Also see the $timeout variable.
-#
-#
-# set mailcap_path=""
-#
-# Name: mailcap_path
-# Type: string
-# Default: ""
-#
-#
-# This variable specifies which files to consult when attempting to
-# display MIME bodies not directly supported by Mutt.
-#
-#
-# set mailcap_sanitize=yes
-#
-# Name: mailcap_sanitize
-# Type: boolean
-# Default: yes
-#
-#
-# If set, mutt 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!
-#
-#
-# set maildir_mtime=no
-#
-# Name: maildir_mtime
-# Type: boolean
-# Default: no
-#
-#
-# If set, the sort-by-date option in the browser will sort maildirs
-# smartly, not using the mtime of the maildir itself but that of the
-# newest message in the new subdirectory, making the sorting by
-# reverse date much more useful. People with maildirs over NFS may
-# wish to leave this option unset.
-#
-#
-# set header_cache=""
-#
-# Name: header_cache
-# Type: path
-# Default: ""
-#
-#
-# This variable points to the header cache database.
-# If pointing to a directory Mutt will contain a header cache
-# database file per folder, if pointing to a file that file will
-# be a single global header cache. By default it is unset so no header
-# caching will be used.
-#
-# Header caching can greatly improve speed when opening POP, IMAP
-# MH or Maildir folders, see ``caching'' for details.
-#
-#
-# set maildir_header_cache_verify=yes
-#
-# Name: maildir_header_cache_verify
-# Type: boolean
-# Default: yes
-#
-#
-# Check for Maildir unaware programs other than mutt having modified maildir
-# files when the header cache is in use. This incurs one stat(2) per
-# message every time the folder is opened (which can be very slow for NFS
-# folders).
-#
-#
-# set header_cache_pagesize="16384"
-#
-# Name: header_cache_pagesize
-# Type: string
-# Default: "16384"
-#
-#
-# When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-# this option changes the database page size. Too large or too small
-# values can waste space, memory, or CPU time. The default should be more
-# or less optimal for most use cases.
-#
-#
-# set maildir_trash=no
-#
-# Name: maildir_trash
-# Type: boolean
-# Default: no
-#
-#
-# If set, messages marked as deleted will be saved with the maildir
-# trashed flag instead of unlinked. Note: this only applies
-# to maildir-style mailboxes. Setting it will have no effect on other
-# mailbox types.
-#
-#
-# set mark_old=yes
-#
-# Name: mark_old
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether or not mutt marks new unread
-# messages as old if you exit a mailbox without reading them.
-# With this option set, the next time you start mutt, the messages
-# will show up with an ``O'' next to them in the index menu,
-# indicating that they are old.
-#
-#
-# set markers=yes
-#
-# Name: 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.
-#
-#
-# set mask="!^\\.[^.]"
-#
-# Name: 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.
-#
-#
-# set mbox="~/mbox"
-#
-# Name: mbox
-# Type: path
-# Default: "~/mbox"
-#
-#
-# This specifies the folder into which read mail in your $spoolfile
-# folder will be appended.
-#
-# Also see the $move variable.
-#
-#
-# set mbox_type=mbox
-#
-# Name: 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''.
-#
-#
-# set metoo=no
-#
-# Name: metoo
-# Type: boolean
-# Default: no
-#
-#
-# If unset, Mutt will remove your address (see the ``alternates''
-# command) from the list of recipients when replying to a message.
-#
-#
-# set menu_context=0
-#
-# Name: 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.)
-#
-#
-# set menu_move_off=yes
-#
-# Name: 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.
-#
-#
-# set menu_scroll=no
-#
-# Name: 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).
-#
-#
-# set meta_key=no
-#
-# Name: meta_key
-# Type: boolean
-# Default: no
-#
-#
-# If set, forces Mutt 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''.
-#
-#
-# set mh_purge=no
-#
-# Name: mh_purge
-# Type: boolean
-# Default: no
-#
-#
-# When unset, mutt will mimic mh's behaviour and rename deleted messages
-# to ,<old file name> in mh folders instead of really deleting
-# them. This leaves the message on disk but makes programs reading the folder
-# ignore it. If the variable is set, the message files will simply be
-# deleted.
-#
-# This option is similar to $maildir_trash for Maildir folders.
-#
-#
-# set mh_seq_flagged="flagged"
-#
-# Name: mh_seq_flagged
-# Type: string
-# Default: "flagged"
-#
-#
-# The name of the MH sequence used for flagged messages.
-#
-#
-# set mh_seq_replied="replied"
-#
-# Name: mh_seq_replied
-# Type: string
-# Default: "replied"
-#
-#
-# The name of the MH sequence used to tag replied messages.
-#
-#
-# set mh_seq_unseen="unseen"
-#
-# Name: mh_seq_unseen
-# Type: string
-# Default: "unseen"
-#
-#
-# The name of the MH sequence used for unseen messages.
-#
-#
-# set mime_forward=no
-#
-# Name: mime_forward
-# Type: quadoption
-# Default: no
-#
-#
-# When set, the message you are forwarding will be attached as a
-# separate message/rfc822 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.
-#
-#
-# set mime_forward_decode=no
-#
-# Name: 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.
-#
-#
-# set mime_forward_rest=yes
-#
-# Name: mime_forward_rest
-# Type: quadoption
-# Default: yes
-#
-#
-# When forwarding multiple attachments of a MIME message from the attachment
-# menu, attachments which cannot be decoded in a reasonable manner will
-# be attached to the newly composed message if this option is set.
-#
-#
-# set mix_entry_format="%4n %c %-16s %a"
-#
-# Name: mix_entry_format
-# Type: string
-# Default: "%4n %c %-16s %a"
-#
-#
-# 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.
-#
-#
-# set mixmaster="mixmaster"
-#
-# Name: mixmaster
-# Type: path
-# Default: "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.
-#
-# Note: On Debian systems, this option is set by default to
-# ``mixmaster-filter'' in /etc/Muttrc.
-#
-#
-# set move=no
-#
-# Name: move
-# Type: quadoption
-# Default: no
-#
-#
-# Controls whether or not Mutt will move read messages
-# from your spool mailbox to your $mbox mailbox, or as a result of
-# a ``mbox-hook'' command.
-#
-#
-# set message_cachedir=""
-#
-# Name: message_cachedir
-# Type: path
-# Default: ""
-#
-#
-# Set this to a directory and mutt will cache copies of messages from
-# your IMAP and POP servers here. You are free to remove entries at any
-# time.
-#
-# When setting this variable to a directory, mutt needs to fetch every
-# remote message only once and can perform regular expression searches
-# as fast as for local folders.
-#
-# Also see the $message_cache_clean variable.
-#
-#
-# set message_cache_clean=no
-#
-# Name: message_cache_clean
-# Type: boolean
-# Default: no
-#
-#
-# If set, mutt will clean out obsolete entries from the message cache when
-# the mailbox is synchronized. You probably only want to set it
-# every once in a while, since it can be a little slow
-# (especially for large folders).
-#
-#
-# set message_format="%s"
-#
-# Name: 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.
-#
-#
-# set narrow_tree=no
-#
-# Name: narrow_tree
-# Type: boolean
-# Default: no
-#
-#
-# This variable, when set, makes the thread tree narrower, allowing
-# deeper threads to fit on the screen.
-#
-#
-# set net_inc=10
-#
-# Name: 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, $write_inc and $net_inc.
-#
-#
-# set pager="builtin"
-#
-# Name: pager
-# Type: path
-# Default: "builtin"
-#
-#
-# This variable specifies which pager you would like to use to view
-# messages. The value ``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 functions
-# directly from the pager, and screen resizes cause lines longer than
-# the screen width to be badly formatted in the help menu.
-#
-#
-# set pager_context=0
-#
-# Name: 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 will display the line after the last one on the screen
-# at the top of the next page (0 lines of context).
-#
-#
-# set pager_format="-%Z- %C/%m: %-20.20n %s%* -- (%P)"
-#
-# Name: pager_format
-# Type: string
-# Default: "-%Z- %C/%m: %-20.20n %s%* -- (%P)"
-#
-#
-# 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.
-#
-#
-# set pager_index_lines=0
-#
-# Name: 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 setting 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.
-#
-#
-# set pager_stop=no
-#
-# Name: 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.
-#
-#
-# set crypt_autosign=no
-#
-# Name: crypt_autosign
-# Type: boolean
-# Default: no
-#
-#
-# Setting this variable will cause Mutt 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 instead of the pgp menu.
-# (Crypto only)
-#
-#
-# set crypt_autoencrypt=no
-#
-# Name: crypt_autoencrypt
-# Type: boolean
-# Default: no
-#
-#
-# Setting this variable will cause Mutt 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 instead.
-# (Crypto only)
-#
-#
-# set pgp_ignore_subkeys=yes
-#
-# Name: pgp_ignore_subkeys
-# Type: boolean
-# Default: yes
-#
-#
-# Setting this variable will cause Mutt 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)
-#
-#
-# set crypt_replyencrypt=yes
-#
-# Name: crypt_replyencrypt
-# Type: boolean
-# Default: yes
-#
-#
-# If set, automatically PGP or OpenSSL encrypt replies to messages which are
-# encrypted.
-# (Crypto only)
-#
-#
-# set crypt_replysign=no
-#
-# Name: crypt_replysign
-# Type: boolean
-# Default: no
-#
-#
-# If set, automatically PGP or OpenSSL sign replies to messages which are
-# signed.
-#
-# Note: this does not work on messages that are encrypted
-# and signed!
-# (Crypto only)
-#
-#
-# set crypt_replysignencrypted=no
-#
-# Name: crypt_replysignencrypted
-# Type: boolean
-# Default: no
-#
-#
-# 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 is not able
-# to find out whether an encrypted message is also signed.
-# (Crypto only)
-#
-#
-# set crypt_timestamp=yes
-#
-# Name: crypt_timestamp
-# Type: boolean
-# Default: yes
-#
-#
-# If set, mutt 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)
-#
-#
-# set sidebar_delim="|"
-#
-# Name: sidebar_delim
-# Type: string
-# Default: "|"
-#
-#
-# This specifies the delimiter between the sidebar (if visible) and
-# other screens.
-#
-#
-# set sidebar_visible=no
-#
-# Name: sidebar_visible
-# Type: boolean
-# Default: no
-#
-#
-# This specifies whether or not to show sidebar (left-side list of folders).
-#
-#
-# set sidebar_width=0
-#
-# Name: sidebar_width
-# Type: number
-# Default: 0
-#
-#
-# The width of the sidebar.
-#
-#
-# set pgp_use_gpg_agent=no
-#
-# Name: pgp_use_gpg_agent
-# Type: boolean
-# Default: no
-#
-#
-# If set, mutt will use a possibly-running gpg-agent(1) process.
-# (PGP only)
-#
-#
-# set crypt_verify_sig=yes
-#
-# Name: crypt_verify_sig
-# Type: quadoption
-# Default: yes
-#
-#
-# If ``yes'', always attempt to verify PGP or S/MIME signatures.
-# If ``ask-*'', ask whether or not to verify the signature.
-# If \Fi``no'', never attempt to verify cryptographic signatures.
-# (Crypto only)
-#
-#
-# set smime_is_default=no
-#
-# Name: smime_is_default
-# Type: boolean
-# Default: no
-#
-#
-# The default behaviour of mutt 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 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)
-#
-#
-# set smime_ask_cert_label=yes
-#
-# Name: 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)
-#
-#
-# set smime_decrypt_use_default_key=yes
-#
-# Name: smime_decrypt_use_default_key
-# Type: boolean
-# Default: yes
-#
-#
-# If set (default) this tells mutt to use the default key for decryption. Otherwise,
-# if managing multiple certificate-key-pairs, mutt 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)
-#
-#
-# set pgp_entry_format="%4n %t%f %4l/0x%k %-4a %2c %u"
-#
-# Name: 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)
-#
-#
-# set pgp_good_sign=""
-#
-# Name: 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)
-#
-#
-# set pgp_check_exit=yes
-#
-# Name: pgp_check_exit
-# Type: boolean
-# Default: yes
-#
-#
-# If set, mutt 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)
-#
-#
-# set pgp_long_ids=no
-#
-# Name: pgp_long_ids
-# Type: boolean
-# Default: no
-#
-#
-# If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs.
-# (PGP only)
-#
-#
-# set pgp_retainable_sigs=no
-#
-# Name: 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)
-#
-#
-# set pgp_autoinline=no
-#
-# Name: pgp_autoinline
-# Type: boolean
-# Default: no
-#
-#
-# This option controls whether Mutt 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 might automatically use PGP/MIME for messages
-# which consist of more than a single MIME part. Mutt can be
-# configured to ask before sending PGP/MIME messages when inline
-# (traditional) would not work.
-#
-# Also see the $pgp_mime_auto variable.
-#
-# Also note that using the old-style PGP message format is strongly
-# deprecated.
-# (PGP only)
-#
-#
-# set pgp_replyinline=no
-#
-# Name: pgp_replyinline
-# Type: boolean
-# Default: no
-#
-#
-# Setting this variable will cause Mutt 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
-# internals for previously checked/flagged messages.
-#
-# Note that Mutt might automatically use PGP/MIME for messages
-# which consist of more than a single MIME part. Mutt can be
-# configured to ask before sending PGP/MIME messages when inline
-# (traditional) would not work.
-#
-# Also see the $pgp_mime_auto variable.
-#
-# Also note that using the old-style PGP message format is strongly
-# deprecated.
-# (PGP only)
-#
-#
-# set pgp_show_unusable=yes
-#
-# Name: pgp_show_unusable
-# Type: boolean
-# Default: yes
-#
-#
-# If set, mutt 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)
-#
-#
-# set pgp_sign_as=""
-#
-# Name: 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)
-#
-#
-# set pgp_strict_enc=yes
-#
-# Name: pgp_strict_enc
-# Type: boolean
-# Default: yes
-#
-#
-# If set, Mutt 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)
-#
-#
-# set pgp_timeout=300
-#
-# Name: pgp_timeout
-# Type: number
-# Default: 300
-#
-#
-# The number of seconds after which a cached passphrase will expire if
-# not used.
-# (PGP only)
-#
-#
-# set pgp_sort_keys=address
-#
-# Name: pgp_sort_keys
-# Type: sort order
-# Default: address
-#
-#
-# Specifies how the entries in the pgp 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)
-#
-#
-# set pgp_mime_auto=ask-yes
-#
-# Name: pgp_mime_auto
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# This option controls whether Mutt 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 strongly
-# deprecated.
-# (PGP only)
-#
-#
-# set pgp_auto_decode=no
-#
-# Name: pgp_auto_decode
-# Type: boolean
-# Default: no
-#
-#
-# If set, mutt 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 will automatically
-# check the message for traditional pgp.
-#
-#
-# set pgp_mime_signature_filename="signature.asc"
-#
-# Name: pgp_mime_signature_filename
-# Type: string
-# Default: "signature.asc"
-#
-#
-# This option sets the filename used for signature parts in PGP/MIME
-# signed messages.
-#
-#
-# set pgp_mime_signature_description="Digital signature"
-#
-# Name: pgp_mime_signature_description
-# Type: string
-# Default: "Digital signature"
-#
-#
-# This option sets the Content-Description used for signature parts in
-# PGP/MIME signed messages.
-#
-#
-# set pgp_decode_command=""
-#
-# Name: 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 and gpg sample configuration files in
-# the samples/ subdirectory which has been installed on your system
-# alongside the documentation.
-# (PGP only)
-#
-#
-# set pgp_getkeys_command=""
-#
-# Name: pgp_getkeys_command
-# Type: string
-# Default: ""
-#
-#
-# This command is invoked whenever mutt will need public key information.
-# Of the sequences supported by $pgp_decode_command, %r is the only
-# printf(3)-like sequence used with this format.
-# (PGP only)
-#
-#
-# set pgp_verify_command=""
-#
-# Name: pgp_verify_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to verify PGP signatures.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_decrypt_command=""
-#
-# Name: pgp_decrypt_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to decrypt a PGP encrypted message.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_clearsign_command=""
-#
-# Name: pgp_clearsign_command
-# Type: string
-# Default: ""
-#
-#
-# This format is used to create an old-style ``clearsigned'' PGP
-# message. Note that the use of this format is strongly
-# deprecated.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_sign_command=""
-#
-# Name: pgp_sign_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to create the detached PGP signature for a
-# multipart/signed PGP/MIME body part.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_encrypt_sign_command=""
-#
-# Name: pgp_encrypt_sign_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to both sign and encrypt a body part.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_encrypt_only_command=""
-#
-# Name: pgp_encrypt_only_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to encrypt a body part without signing it.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_import_command=""
-#
-# Name: pgp_import_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to import a key from a message into
-# the user's public key ring.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_export_command=""
-#
-# Name: pgp_export_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to export a public key from the user's
-# key ring.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_verify_key_command=""
-#
-# Name: pgp_verify_key_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to verify key information from the key selection
-# menu.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_list_secring_command=""
-#
-# Name: 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.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_list_pubring_command=""
-#
-# Name: 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.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set forward_decrypt=yes
-#
-# Name: forward_decrypt
-# 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)
-#
-#
-# set smime_timeout=300
-#
-# Name: smime_timeout
-# Type: number
-# Default: 300
-#
-#
-# The number of seconds after which a cached passphrase will expire if
-# not used.
-# (S/MIME only)
-#
-#
-# set smime_encrypt_with=""
-#
-# Name: 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'', ``rc2-128''.
-# If unset, ``3des'' (TripleDES) is used.
-# (S/MIME only)
-#
-#
-# set smime_keys=""
-#
-# Name: smime_keys
-# Type: path
-# Default: ""
-#
-#
-# Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-# storage and 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 option points to the location of the private keys.
-# (S/MIME only)
-#
-#
-# set smime_ca_location=""
-#
-# Name: 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)
-#
-# Note: On Debian systems, this defaults to the first existing file in
-# the following list: ~/.smime/ca-certificates.crt ~/.smime/ca-bundle.crt
-# /etc/ssl/certs/ca-certificates.crt.
-#
-#
-# set smime_certificates=""
-#
-# Name: smime_certificates
-# Type: path
-# Default: ""
-#
-#
-# Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-# the location of the certificates.
-# (S/MIME only)
-#
-#
-# set smime_decrypt_command=""
-#
-# Name: 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)
-#
-#
-# set smime_verify_command=""
-#
-# Name: smime_verify_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to verify S/MIME signatures of type multipart/signed.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_verify_opaque_command=""
-#
-# Name: smime_verify_opaque_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to verify S/MIME signatures of type
-# application/x-pkcs7-mime.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_sign_command=""
-#
-# Name: 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.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_sign_opaque_command=""
-#
-# Name: 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.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_encrypt_command=""
-#
-# Name: smime_encrypt_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to create encrypted S/MIME messages.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_pk7out_command=""
-#
-# Name: 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).
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_get_cert_command=""
-#
-# Name: smime_get_cert_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to extract X509 certificates from a PKCS7 structure.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_get_signer_cert_command=""
-#
-# Name: 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:'' field.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_import_cert_command=""
-#
-# Name: smime_import_cert_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to import a certificate via smime_keys.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_get_cert_email_command=""
-#
-# Name: 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).
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_default_key=""
-#
-# Name: 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)
-#
-#
-# set ssl_client_cert=""
-#
-# Name: ssl_client_cert
-# Type: path
-# Default: ""
-#
-#
-# The file containing a client certificate and its associated private
-# key.
-#
-#
-# set ssl_force_tls=no
-#
-# Name: ssl_force_tls
-# Type: boolean
-# Default: no
-#
-#
-# If this variable is set, Mutt 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.
-#
-#
-# set ssl_starttls=yes
-#
-# Name: ssl_starttls
-# Type: quadoption
-# Default: yes
-#
-#
-# If set (the default), mutt will attempt to use STARTTLS on servers
-# advertising the capability. When unset, mutt will not attempt to
-# use STARTTLS regardless of the server's capabilities.
-#
-#
-# set certificate_file="~/.mutt_certificates"
-#
-# Name: certificate_file
-# Type: path
-# Default: "~/.mutt_certificates"
-#
-#
-# This variable specifies the file where the certificates you trust
-# are saved. When an unknown certificate is encountered, you are asked
-# if you accept it or not. If you accept it, the certificate can also
-# be saved in this file and further connections are automatically
-# accepted.
-#
-# You can also manually add CA certificates in this file. Any server
-# certificate that is signed with one of these CA certificates is
-# also automatically accepted.
-#
-# Example:
-# set certificate_file=~/.mutt/certificates
-#
-#
-# set ssl_use_sslv3=yes
-#
-# Name: ssl_use_sslv3
-# Type: boolean
-# Default: yes
-#
-#
-# This variable specifies whether to attempt to use SSLv3 in the
-# SSL authentication process.
-#
-#
-# set ssl_use_tlsv1=yes
-#
-# Name: ssl_use_tlsv1
-# Type: boolean
-# Default: yes
-#
-#
-# This variable specifies whether to attempt to use TLSv1 in the
-# SSL authentication process.
-#
-#
-# set ssl_min_dh_prime_bits=0
-#
-# Name: ssl_min_dh_prime_bits
-# Type: number
-# Default: 0
-#
-#
-# 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.
-#
-#
-# set ssl_ca_certificates_file=""
-#
-# Name: 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 is also automatically accepted.
-#
-# Example:
-# set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-#
-# Note: On Debian systems, this variable defaults to the example
-# mentioned. This file is managed by the ``ca-certificates'' package.
-#
-#
-# set pipe_split=no
-#
-# Name: pipe_split
-# Type: boolean
-# Default: no
-#
-#
-# Used in connection with the <pipe-message> function following
-# <tag-prefix>. If this variable is unset, when piping a list of
-# tagged messages Mutt will concatenate the messages and will pipe them
-# all concatenated. When set, Mutt 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.
-#
-#
-# set pipe_decode=no
-#
-# Name: pipe_decode
-# Type: boolean
-# Default: no
-#
-#
-# Used in connection with the <pipe-message> command. When unset,
-# Mutt will pipe the messages without any preprocessing. When set, Mutt
-# will weed headers and will attempt to decode the messages
-# first.
-#
-#
-# set pipe_sep="\n"
-#
-# Name: pipe_sep
-# Type: string
-# Default: "\n"
-#
-#
-# The separator to add between messages when piping a list of tagged
-# messages to an external Unix command.
-#
-#
-# set pop_authenticators=""
-#
-# Name: pop_authenticators
-# Type: string
-# Default: ""
-#
-#
-# This is a colon-delimited list of authentication methods mutt may
-# attempt to use to log in to an POP server, in the order mutt should
-# try them. Authentication methods are either ``user'', ``apop'' or any
-# SASL mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''.
-# This option is case-insensitive. If this option is unset
-# (the default) mutt will try all available methods, in order from
-# most-secure to least-secure.
-#
-# Example:
-# set pop_authenticators="digest-md5:apop:user"
-#
-#
-# set pop_auth_try_all=yes
-#
-# Name: pop_auth_try_all
-# Type: boolean
-# Default: yes
-#
-#
-# If set, Mutt will try all available authentication methods.
-# When unset, Mutt will only fall back to other authentication
-# methods if the previous methods are unavailable. If a method is
-# available but authentication fails, Mutt will not connect to the POP server.
-#
-#
-# set pop_checkinterval=60
-#
-# Name: pop_checkinterval
-# Type: number
-# Default: 60
-#
-#
-# This variable configures how often (in seconds) mutt should look for
-# new mail in the currently selected mailbox if it is a POP mailbox.
-#
-#
-# set pop_delete=ask-no
-#
-# Name: pop_delete
-# Type: quadoption
-# Default: ask-no
-#
-#
-# If set, Mutt will delete successfully downloaded messages from the POP
-# server when using the <fetch-mail> function. When unset, Mutt will
-# download messages but also leave them on the POP server.
-#
-#
-# set pop_host=""
-#
-# Name: pop_host
-# Type: string
-# Default: ""
-#
-#
-# The name of your POP server for the <fetch-mail> function. You
-# can also specify an alternative port, username and password, ie:
-# [pop[s]://][username[:password]@]popserver[:port]
-#
-# where ``[...]'' denotes an optional part.
-#
-#
-# set pop_last=no
-#
-# Name: pop_last
-# Type: boolean
-# Default: no
-#
-#
-# If this variable is set, mutt will try to use the ``LAST'' POP command
-# for retrieving only unread messages from the POP server when using
-# the <fetch-mail> function.
-#
-#
-# set pop_reconnect=ask-yes
-#
-# Name: pop_reconnect
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# Controls whether or not Mutt will try to reconnect to the POP server if
-# the connection is lost.
-#
-#
-# set pop_user=""
-#
-# Name: pop_user
-# Type: string
-# Default: ""
-#
-#
-# Your login name on the POP server.
-#
-# This variable defaults to your user name on the local machine.
-#
-#
-# set pop_pass=""
-#
-# Name: pop_pass
-# Type: string
-# Default: ""
-#
-#
-# Specifies the password for your POP account. If unset, Mutt will
-# prompt you for your password when you open a POP mailbox.
-#
-# Warning: you should only use this option when you are on a
-# fairly secure machine, because the superuser can read your muttrc
-# even if you are the only one who can read the file.
-#
-#
-# set post_indent_string=""
-#
-# Name: post_indent_string
-# Type: string
-# Default: ""
-#
-#
-# Similar to the $attribution variable, Mutt will append this
-# string after the inclusion of a message which is being replied to.
-#
-#
-# set postpone=ask-yes
-#
-# Name: postpone
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# Controls whether or not messages are saved in the $postponed
-# mailbox when you elect not to send immediately.
-#
-# Also see the $recall variable.
-#
-#
-# set postponed="~/postponed"
-#
-# Name: postponed
-# Type: path
-# Default: "~/postponed"
-#
-#
-# Mutt allows you to indefinitely ``postpone sending a message'' which
-# you are editing. When you choose to postpone a message, Mutt saves it
-# in the mailbox specified by this variable.
-#
-# Also see the $postpone variable.
-#
-#
-# set preconnect=""
-#
-# Name: preconnect
-# Type: string
-# Default: ""
-#
-#
-# If set, a shell command to be executed if mutt 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 gives up opening the server. Example:
-# set 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.
-#
-# When set, Mutt uses the tunnel for all remote connections.
-# Please see ``account-hook'' in the manual for how to use different
-# tunnel commands per connection.
-#
-#
-# set print=ask-no
-#
-# Name: print
-# Type: quadoption
-# Default: ask-no
-#
-#
-# Controls whether or not Mutt really prints messages.
-# This is set to ``ask-no'' by default, because some people
-# accidentally hit ``p'' often.
-#
-#
-# set print_command="lpr"
-#
-# Name: print_command
-# Type: path
-# Default: "lpr"
-#
-#
-# This specifies the command pipe that should be used to print messages.
-#
-#
-# set print_decode=yes
-#
-# Name: 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.
-#
-#
-# set print_split=no
-#
-# Name: 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.
-#
-#
-# set prompt_after=yes
-#
-# Name: prompt_after
-# Type: boolean
-# Default: yes
-#
-#
-# If you use an external $pager, setting this variable will
-# cause Mutt to prompt you for a command when the pager exits rather
-# than returning to the index menu. If unset, Mutt will return to the
-# index menu when the external pager exits.
-#
-#
-# set query_command=""
-#
-# Name: query_command
-# Type: path
-# Default: ""
-#
-#
-# This specifies the command that mutt 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.
-#
-#
-# set query_format="%4c %t %-25.25a %-25.25n %?e?(%e)?"
-#
-# Name: query_format
-# Type: string
-# Default: "%4c %t %-25.25a %-25.25n %?e?(%e)?"
-#
-#
-# This variable describes the format of the ``query'' menu. The
-# following printf(3)-style sequences are understood:
-# %a destination address
-# %c current entry number
-# %e extra information *
-# %n destination name
-# %t ``*'' if current entry is tagged, a space otherwise
-# %>X right justify the rest of the string and pad with ``X''
-# %|X pad to the end of the line with ``X''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# For an explanation of ``soft-fill'', see the $index_format documentation.
-#
-# * = can be optionally printed if nonzero, see the $status_format documentation.
-#
-#
-# set quit=yes
-#
-# Name: quit
-# Type: quadoption
-# Default: yes
-#
-#
-# This variable controls whether ``quit'' and ``exit'' actually quit
-# from mutt. If this option is set, they do quit, if it is unset, 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.
-#
-#
-# set quote_regexp="^([ \t]*[|>:}#])+"
-#
-# Name: 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. Quoted text may be filtered
-# out using the <toggle-quoted> command, or colored according to the
-# ``color quoted'' family of directives.
-#
-# Higher levels of quoting may be colored differently (``color quoted1'',
-# ``color quoted2'', etc.). The quoting level is determined by removing
-# the last character from the matched text and recursively reapplying
-# the regular expression until it fails to produce a match.
-#
-# Match detection may be overridden by the $smileys regular expression.
-#
-#
-# set read_inc=10
-#
-# Name: read_inc
-# Type: number
-# Default: 10
-#
-#
-# If set to a value greater than 0, Mutt will display which message it
-# is currently on when reading a mailbox or when performing search actions
-# such as search and limit. The message is printed after
-# this many messages have been read or searched (e.g., if set to 25, Mutt will
-# print a message when it is at message 25, and then again when it gets
-# to message 50). This variable is meant to indicate progress when
-# reading or searching 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, $net_inc and $time_inc variables and the
-# ``tuning'' section of the manual for performance considerations.
-#
-#
-# set read_only=no
-#
-# Name: read_only
-# Type: boolean
-# Default: no
-#
-#
-# If set, all folders are opened in read-only mode.
-#
-#
-# set realname=""
-#
-# Name: 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 that this
-# variable will not be used when the user has set a real name
-# in the $from variable.
-#
-#
-# set recall=ask-yes
-#
-# Name: recall
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# Controls whether or not Mutt recalls postponed messages
-# when composing a new message.
-#
-# Setting this variable to is not generally useful, and thus not
-# recommended.
-#
-# Also see $postponed variable.
-#
-#
-# set record="~/sent"
-#
-# Name: record
-# Type: path
-# Default: "~/sent"
-#
-#
-# 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:'' 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.
-#
-#
-# set reply_regexp="^(re([\\[0-9\\]+])*|aw):[ \t]*"
-#
-# Name: 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:".
-#
-#
-# set reply_self=no
-#
-# Name: reply_self
-# Type: boolean
-# Default: no
-#
-#
-# If unset and you are replying to a message sent by you, Mutt will
-# assume that you want to reply to the recipients of that message rather
-# than to yourself.
-#
-# Also see the ``alternates'' command.
-#
-#
-# set reply_to=ask-yes
-#
-# Name: reply_to
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# If set, when replying to a message, Mutt will use the address listed
-# in the Reply-to: header 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.
-#
-#
-# set resolve=yes
-#
-# Name: 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.
-#
-#
-# set reverse_alias=no
-#
-# Name: reverse_alias
-# Type: boolean
-# Default: no
-#
-#
-# This variable controls whether or not Mutt 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.
-#
-#
-# set reverse_name=no
-#
-# Name: 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.
-#
-# Also see the ``alternates'' command.
-#
-#
-# set reverse_realname=yes
-#
-# Name: reverse_realname
-# Type: boolean
-# Default: yes
-#
-#
-# This variable fine-tunes the behaviour of the $reverse_name feature.
-# When it is set, mutt will use the address from incoming messages as-is,
-# possibly including eventual real names. When it is unset, mutt will
-# override any such real names with the setting of the $realname variable.
-#
-#
-# set rfc2047_parameters=no
-#
-# Name: rfc2047_parameters
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, Mutt will decode RFC2047-encoded MIME
-# parameters. You want to set this variable when mutt suggests you
-# to save attachments to files named like:
-# =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-#
-# When this variable is set interactively, the change won't be
-# active until you change folders.
-#
-# Note that this use of RFC2047'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 generates this kind of encoding. Instead, mutt will
-# unconditionally use the encoding specified in RFC2231.
-#
-#
-# set save_address=no
-#
-# Name: save_address
-# Type: boolean
-# Default: no
-#
-#
-# If set, mutt 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.
-#
-#
-# set save_empty=yes
-#
-# Name: 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 does not
-# delete MH and Maildir directories.
-#
-#
-# set save_history=0
-#
-# Name: save_history
-# Type: number
-# Default: 0
-#
-#
-# This variable controls the size of the history (per category) saved in the
-# $history_file file.
-#
-#
-# set save_name=no
-#
-# Name: 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.
-#
-#
-# set score=yes
-#
-# Name: 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 related are used.
-#
-#
-# set score_threshold_delete=-1
-#
-# Name: 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. Since
-# mutt scores are always greater than or equal to zero, the default setting
-# of this variable will never mark a message for deletion.
-#
-#
-# set score_threshold_flag=9999
-#
-# Name: 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".
-#
-#
-# set score_threshold_read=-1
-#
-# Name: 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. Since
-# mutt scores are always greater than or equal to zero, the default setting
-# of this variable will never mark a message read.
-#
-#
-# set send_charset="us-ascii:iso-8859-1:utf-8"
-#
-# Name: send_charset
-# Type: string
-# Default: "us-ascii:iso-8859-1:utf-8"
-#
-#
-# A colon-delimited list of character sets for outgoing messages. Mutt 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''.
-#
-# In case the text cannot be converted into one of these exactly,
-# mutt uses $charset as a fallback.
-#
-#
-# set sendmail="/usr/sbin/sendmail -oem -oi"
-#
-# Name: sendmail
-# Type: path
-# Default: "/usr/sbin/sendmail -oem -oi"
-#
-#
-# Specifies the program and arguments used to deliver mail sent by Mutt.
-# Mutt expects that the specified program interprets additional
-# arguments as recipient addresses.
-#
-#
-# set sendmail_wait=0
-#
-# Name: 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 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.
-#
-#
-# set shell=""
-#
-# Name: shell
-# Type: path
-# Default: ""
-#
-#
-# Command to use when spawning a subshell. By default, the user's login
-# shell from /etc/passwd is used.
-#
-#
-# set sig_dashes=yes
-#
-# Name: sig_dashes
-# Type: boolean
-# Default: yes
-#
-#
-# If set, a line containing ``-- '' (note the trailing 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 has the ability to highlight
-# the signature in a different color in the builtin pager.
-#
-#
-# set sig_on_top=no
-#
-# Name: 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.
-#
-#
-# set signature="~/.signature"
-#
-# Name: 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 standard output.
-#
-#
-# set simple_search="~f %s | ~s %s"
-#
-# Name: simple_search
-# Type: string
-# Default: "~f %s | ~s %s"
-#
-#
-# Specifies how Mutt should expand a simple search into a real search
-# pattern. A simple search is one that does not contain any of the ``~'' pattern
-# operators. See ``patterns'' for more information on search patterns.
-#
-# For example, if you simply type ``joe'' at a search or limit prompt, Mutt
-# will automatically expand it to the value specified by this variable by
-# replacing ``%s'' with the supplied string.
-# For the default value, ``joe'' would be expanded to: ``~f joe | ~s joe''.
-#
-#
-# set smart_wrap=yes
-#
-# Name: 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.
-#
-#
-# set smileys="(>From )|(:[-^]?[][)(><}{|/DP])"
-#
-# Name: smileys
-# Type: regular expression
-# Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
-#
-#
-# The pager uses this variable to catch some common false
-# positives of $quote_regexp, most notably smileys and not consider
-# a line quoted text if it also matches $smileys. This mostly
-# happens at the beginning of a line.
-#
-#
-# set sleep_time=1
-#
-# Name: 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.
-#
-#
-# set smtp_authenticators=""
-#
-# Name: smtp_authenticators
-# Type: string
-# Default: ""
-#
-#
-# This is a colon-delimited list of authentication methods mutt may
-# attempt to use to log in to an SMTP server, in the order mutt should
-# try them. Authentication methods are any SASL mechanism, eg
-# ``digest-md5'', ``gssapi'' or ``cram-md5''.
-# This option is case-insensitive. If it is ``unset''
-# (the default) mutt will try all available methods, in order from
-# most-secure to least-secure.
-#
-# Example:
-# set smtp_authenticators="digest-md5:cram-md5"
-#
-#
-# set smtp_pass=""
-#
-# Name: smtp_pass
-# Type: string
-# Default: ""
-#
-#
-# Specifies the password for your SMTP account. If unset, Mutt will
-# prompt you for your password when you first send mail via SMTP.
-# See $smtp_url to configure mutt to send mail via SMTP.
-#
-# Warning: you should only use this option when you are on a
-# fairly secure machine, because the superuser can read your muttrc even
-# if you are the only one who can read the file.
-#
-#
-# set smtp_url=""
-#
-# Name: smtp_url
-# Type: string
-# Default: ""
-#
-#
-# Defines the SMTP smarthost where sent messages should relayed for
-# delivery. This should take the form of an SMTP URL, eg:
-# smtp[s]://[user[:pass]@]host[:port]/
-#
-# \.\.\. where ``[...]'' denotes an optional part.
-# Setting this variable overrides the value of the $sendmail
-# variable.
-#
-#
-# set sort=date
-#
-# Name: 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'').
-#
-# Note: On Debian systems, this option is set by default to
-# ``threads'' in /etc/Muttrc.
-#
-#
-# set sort_alias=alias
-#
-# Name: 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)
-#
-#
-# set sort_aux=date
-#
-# Name: 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 will just use ``date-sent''). You can also
-# specify the ``last-'' prefix in addition to the ``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).
-#
-#
-# set sort_browser=alpha
-#
-# Name: 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'').
-#
-#
-# set sort_re=yes
-#
-# Name: 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 uses to thread messages by subject. With $sort_re set, mutt 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_re unset, mutt will attach
-# the message whether or not this is the case, as long as the
-# non-$reply_regexp parts of both messages are identical.
-#
-#
-# set spam_separator=","
-#
-# Name: spam_separator
-# Type: string
-# Default: ","
-#
-#
-# This variable 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 this variable's value as a
-# separator.
-#
-#
-# set spoolfile=""
-#
-# Name: spoolfile
-# Type: path
-# Default: ""
-#
-#
-# If your spool mailbox is in a non-default place where Mutt cannot find
-# it, you can specify its location with this variable. Mutt will
-# automatically set this variable to the value of the environment
-# variable $MAIL if it is not set.
-#
-#
-# set status_chars="-*%A"
-#
-# Name: 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).
-#
-#
-# set status_format="-%r-Mutt: %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)---"
-#
-# Name: status_format
-# Type: string
-# Default: "-%r-Mutt: %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 *
-# %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 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''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# For an explanation of ``soft-fill'', see the $index_format documentation.
-#
-# * = 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_string may 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.?
-#
-# You can also switch between two strings using the following construct:
-#
-# %?<sequence_char>?<if_string>&<else_string>?
-#
-# If the value of sequence_char is non-zero, if_string will
-# be expanded, otherwise else_string will be expanded.
-#
-# You can 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
-# will replace any dots in the expansion by underscores. This might be helpful
-# with IMAP folders that don't like dots in folder names.
-#
-#
-# set status_on_top=no
-#
-# Name: 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. If $help
-# is set, too it'll be placed at the bottom.
-#
-#
-# set strict_threads=no
-#
-# Name: strict_threads
-# Type: boolean
-# Default: no
-#
-#
-# If set, threading will only make use of the ``In-Reply-To'' and
-# ``References:'' 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 subjects like ``hi'' which will get grouped together. See also
-# $sort_re for a less drastic way of controlling this
-# behaviour.
-#
-#
-# set suspend=yes
-#
-# Name: suspend
-# Type: boolean
-# Default: yes
-#
-#
-# When unset, mutt won't stop when the user presses the terminal's
-# susp key, usually ``^Z''. This is useful if you run mutt
-# inside an xterm using a command like ``xterm -e mutt''.
-#
-#
-# set text_flowed=no
-#
-# Name: text_flowed
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will generate ``format=flowed'' bodies with a content type
-# of ``text/plain; format=flowed''.
-# 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.
-#
-#
-# set thread_received=no
-#
-# Name: thread_received
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt uses the date received rather than the date sent
-# to thread messages by subject.
-#
-#
-# set thorough_search=no
-#
-# Name: thorough_search
-# Type: boolean
-# Default: no
-#
-#
-# Affects the ~b and ~h search operations described in
-# section ``patterns''. If set, the headers and body/attachments of
-# messages to be searched are decoded before searching. If unset,
-# messages are searched as they appear in the folder.
-#
-# Users searching attachments or for non-ASCII characters should set
-# this value because decoding also includes MIME parsing/decoding and possible
-# character set conversions. Otherwise mutt will attempt to match against the
-# raw message received (for example quoted-printable encoded or with encoded
-# headers) which may lead to incorrect search results.
-#
-#
-# set tilde=no
-#
-# Name: tilde
-# Type: boolean
-# Default: no
-#
-#
-# When set, the internal-pager will pad blank lines to the bottom of the
-# screen with a tilde (``~'').
-#
-#
-# set time_inc=0
-#
-# Name: time_inc
-# Type: number
-# Default: 0
-#
-#
-# Along with $read_inc, $write_inc, and $net_inc, this
-# variable controls the frequency with which progress updates are
-# displayed. It suppresses updates less than $time_inc milliseconds
-# apart. This can improve throughput on systems with slow terminals,
-# or when running mutt on a remote system.
-#
-# Also see the ``tuning'' section of the manual for performance considerations.
-#
-#
-# set timeout=600
-#
-# Name: timeout
-# Type: number
-# Default: 600
-#
-#
-# When Mutt is waiting for user input either idleing in menus or
-# in an interactive prompt, Mutt would block until input is
-# present. Depending on the context, this would prevent certain
-# operations from working, like checking for new mail or keeping
-# an IMAP connection alive.
-#
-# This variable controls how many seconds Mutt will at most wait
-# until it aborts waiting for input, performs these operations and
-# continues to wait for input.
-#
-# A value of zero or less will cause Mutt to never time out.
-#
-#
-# set tmpdir=""
-#
-# Name: tmpdir
-# Type: path
-# Default: ""
-#
-#
-# This variable allows you to specify where Mutt 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.
-#
-#
-# set to_chars=" +TCFL"
-#
-# Name: 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. The second is used when you are the only
-# recipient of the message. The third is when your address
-# appears in the ``To:'' header field, but you are not the only recipient of
-# the message. 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 subscribe to.
-#
-#
-# set trash=""
-#
-# Name: 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 you have a way to clean the trash.
-#
-#
-# set tunnel=""
-#
-# Name: tunnel
-# Type: string
-# Default: ""
-#
-#
-# Setting this variable will cause mutt 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/SMTP server. Example:
-# set 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.
-#
-#
-# set use_8bitmime=no
-#
-# Name: 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 you may not be able to send mail.
-#
-# When set, Mutt will invoke $sendmail with the -B8BITMIME
-# flag when sending 8-bit messages to enable ESMTP negotiation.
-#
-#
-# set use_domain=yes
-#
-# Name: use_domain
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will qualify all local addresses (ones without the
-# ``@host'' portion) with the value of $hostname. If unset, no
-# addresses will be qualified.
-#
-#
-# set use_envelope_from=no
-#
-# Name: use_envelope_from
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will set the envelope sender of the message.
-# If $envelope_from_address is set, it will be used as the sender
-# address. If unset, mutt will attempt to derive the sender from the
-# ``From:'' header.
-#
-# Note that this information is passed to sendmail command using the
-# -f command line switch. Therefore setting this option is not useful
-# if the $sendmail variable already contains -f or if the
-# executable pointed to by $sendmail doesn't support the -f switch.
-#
-#
-# set use_from=yes
-#
-# Name: use_from
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt 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.
-#
-#
-# set use_idn=yes
-#
-# Name: use_idn
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will show you international domain names decoded.
-# Note: You can use IDNs for addresses even if this is unset.
-# This variable only affects decoding.
-#
-#
-# set use_ipv6=yes
-#
-# Name: use_ipv6
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will look for IPv6 addresses of hosts it tries to
-# contact. If this option is unset, Mutt will restrict itself to IPv4 addresses.
-# Normally, the default should work.
-#
-#
-# set user_agent=yes
-#
-# Name: user_agent
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will add a ``User-Agent:'' header to outgoing
-# messages, indicating which version of mutt was used for composing
-# them.
-#
-#
-# set visual=""
-#
-# Name: visual
-# Type: path
-# Default: ""
-#
-#
-# Specifies the visual editor to invoke when the ``~v'' command is
-# given in the builtin editor.
-#
-#
-# set wait_key=yes
-#
-# Name: wait_key
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether Mutt will ask you to press a key after an external command
-# has been invoked by these functions: <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 will always ask for a key. When unset, Mutt will wait
-# for a key only if the external command returned a non-zero status.
-#
-#
-# set weed=yes
-#
-# Name: weed
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will weed headers when displaying, forwarding,
-# printing, or replying to messages.
-#
-#
-# set wrap=0
-#
-# Name: wrap
-# Type: number
-# Default: 0
-#
-#
-# When set to a positive value, mutt will wrap text at $wrap characters.
-# When set to a negative value, mutt will wrap text so that there are $wrap
-# characters of empty space on the right side of the terminal.
-#
-#
-# set wrap_search=yes
-#
-# Name: wrap_search
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether searches wrap around the end.
-#
-# When set, searches will wrap around the first (or last) item. When
-# unset, incremental searches will not wrap.
-#
-#
-# set wrapmargin=0
-#
-# Name: wrapmargin
-# Type: number
-# Default: 0
-#
-#
-# (DEPRECATED) Equivalent to setting $wrap with a negative value.
-#
-#
-# set write_inc=10
-#
-# Name: 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, $net_inc and $time_inc variables and the
-# ``tuning'' section of the manual for performance considerations.
-#
-#
-# set write_bcc=yes
-#
-# Name: write_bcc
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether mutt writes out the ``Bcc:'' header when preparing
-# messages to be sent. Exim users may wish to unset this. If mutt
-# is set to deliver directly via SMTP (see $smtp_url), this
-# option does nothing: mutt will never write out the ``Bcc:'' header
-# in this case.
-#
-# Note: On Debian systems, exim4 and postfix strip BCC headers by
-# default. The above warning applies to exim3 users, see /etc/Muttrc.
-#
-#
-# set xterm_icon="M%?n?AIL&ail?"
-#
-# Name: xterm_icon
-# Type: string
-# Default: "M%?n?AIL&ail?"
-#
-#
-# Controls the format of the icon title, as long as xterm_set_titles
-# is enabled. This string is identical in formatting to the one used by
-# ``$status_format''.
-#
-#
-# set xterm_set_titles=no
-#
-# Name: xterm_set_titles
-# Type: boolean
-# Default: no
-#
-#
-# Controls whether mutt sets the xterm title bar and icon name
-# (as long as you are in an appropriate terminal).
-#
-#
-# set xterm_title="Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?"
-#
-# Name: xterm_title
-# Type: string
-# Default: "Mutt 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''.
-#
-#
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. Advanced Usage</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="configuration.html" title="Chapter 3. Configuration" /><link rel="next" href="mimesupport.html" title="Chapter 5. Mutt's MIME Support" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Advanced Usage</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="configuration.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="mimesupport.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="advancedusage"></a>Chapter 4. Advanced Usage</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="advancedusage.html#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="regexp"></a>1. Regular Expressions</h2></div></div></div><p>
-All string patterns in Mutt including those in more complex
-<a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> must be specified
-using regular expressions (regexp) in the “<span class="quote">POSIX extended</span>” 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.
-</p><p>
-The search is case sensitive if the pattern contains at least one upper
-case letter, and case insensitive otherwise.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that “<span class="quote">\</span>”
-must be quoted if used for a regular expression in an initialization
-command: “<span class="quote">\\</span>”.
-</p></div><p>
-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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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 <a class="xref" href="configuration.html#muttrc-syntax" title="2. Syntax of Initialization Files">Syntax of Initialization Files</a>
-for more information on " and ' delimiter processing. To match a
-literal " or ' you must preface it with \ (backslash).
-</p></div><p>
-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.
-</p><p>
-The period “<span class="quote">.</span>” matches any single character. The caret “<span class="quote">^</span>” and
-the dollar sign “<span class="quote">$</span>” are metacharacters that respectively match
-the empty string at the beginning and end of a line.
-</p><p>
-A list of characters enclosed by “<span class="quote">[</span>” and “<span class="quote">]</span>” matches any
-single character in that list; if the first character of the list
-is a caret “<span class="quote">^</span>” then it matches any character <span class="bold"><strong>not</strong></span> in the
-list. For example, the regular expression <span class="bold"><strong>[0123456789]</strong></span>
-matches any single digit. A range of ASCII characters may be specified
-by giving the first and last characters, separated by a hyphen
-“<span class="quote">-</span>”. Most metacharacters lose their special meaning inside
-lists. To include a literal “<span class="quote">]</span>” place it first in the list.
-Similarly, to include a literal “<span class="quote">^</span>” place it anywhere but first.
-Finally, to include a literal hyphen “<span class="quote">-</span>” place it last.
-</p><p>
-Certain named classes of characters are predefined. Character classes
-consist of “<span class="quote">[:</span>”, a keyword denoting the class, and “<span class="quote">:]</span>”.
-The following classes are defined by the POSIX standard in
-<a class="xref" href="advancedusage.html#posix-regex-char-classes" title="Table 4.1. POSIX regular expression character classes">Table 4.1, “POSIX regular expression character classes”</a>
-</p><div class="table"><a id="posix-regex-char-classes"></a><p class="title"><b>Table 4.1. POSIX regular expression character classes</b></p><div class="table-contents"><table summary="POSIX regular expression character classes" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Character class</th><th>Description</th></tr></thead><tbody><tr><td>[:alnum:]</td><td>Alphanumeric characters</td></tr><tr><td>[:alpha:]</td><td>Alphabetic characters</td></tr><tr><td>[:blank:]</td><td>Space or tab characters</td></tr><tr><td>[:cntrl:]</td><td>Control characters</td></tr><tr><td>[:digit:]</td><td>Numeric characters</td></tr><tr><td>[:graph:]</td><td>Characters that are both printable and visible. (A space is printable, but not visible, while an “<span class="quote">a</span>” is both)</td></tr><tr><td>[:lower:]</td><td>Lower-case alphabetic characters</td></tr><tr><td>[:print:]</td><td>Printable characters (characters that are not control characters)</td></tr><tr><td>[:punct:]</td><td>Punctuation characters (characters that are not letter, digits, control characters, or space characters)</td></tr><tr><td>[:space:]</td><td>Space characters (such as space, tab and formfeed, to name a few)</td></tr><tr><td>[:upper:]</td><td>Upper-case alphabetic characters</td></tr><tr><td>[:xdigit:]</td><td>Characters that are hexadecimal digits</td></tr></tbody></table></div></div><br class="table-break" /><p>
-A character class is only valid in a regular expression inside the
-brackets of a character list.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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, <span class="bold"><strong>[[:digit:]]</strong></span> is equivalent to
-<span class="bold"><strong>[0-9]</strong></span>.
-</p></div><p>
-Two additional special sequences can appear in character lists. These
-apply to non-ASCII character sets, which can have single symbols (called
-collating elements) that are represented with more than one character,
-as well as several characters that are equivalent for collating or
-sorting purposes:
-</p><div class="variablelist"><dl><dt><span class="term">Collating Symbols</span></dt><dd><p>
-A collating symbol is a multi-character collating element enclosed in
-“<span class="quote">[.</span>” and “<span class="quote">.]</span>”. For example, if “<span class="quote">ch</span>” is a collating
-element, then <span class="bold"><strong>[[.ch.]]</strong></span> is a regexp that matches
-this collating element, while <span class="bold"><strong>[ch]</strong></span> is a regexp that
-matches either “<span class="quote">c</span>” or “<span class="quote">h</span>”.
-</p></dd><dt><span class="term">Equivalence Classes</span></dt><dd><p>
-An equivalence class is a locale-specific name for a list of
-characters that are equivalent. The name is enclosed in “<span class="quote">[=</span>”
-and “<span class="quote">=]</span>”. For example, the name “<span class="quote">e</span>” might be used to
-represent all of “<span class="quote">è</span>” “<span class="quote">é</span>” and “<span class="quote">e</span>”. In this case,
-<span class="bold"><strong>[[=e=]]</strong></span> is a regexp that matches any of
-“<span class="quote">è</span>”, “<span class="quote">é</span>” and “<span class="quote">e</span>”.
-</p></dd></dl></div><p>
-A regular expression matching a single character may be followed by one
-of several repetition operators described in <a class="xref" href="advancedusage.html#regex-repeat" title="Table 4.2. Regular expression repetition operators">Table 4.2, “Regular expression repetition operators”</a>.
-</p><div class="table"><a id="regex-repeat"></a><p class="title"><b>Table 4.2. Regular expression repetition operators</b></p><div class="table-contents"><table summary="Regular expression repetition operators" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Operator</th><th>Description</th></tr></thead><tbody><tr><td>?</td><td>The preceding item is optional and matched at most once</td></tr><tr><td>*</td><td>The preceding item will be matched zero or more times</td></tr><tr><td>+</td><td>The preceding item will be matched one or more times</td></tr><tr><td>{n}</td><td>The preceding item is matched exactly <span class="emphasis"><em>n</em></span> times</td></tr><tr><td>{n,}</td><td>The preceding item is matched <span class="emphasis"><em>n</em></span> or more times</td></tr><tr><td>{,m}</td><td>The preceding item is matched at most <span class="emphasis"><em>m</em></span> times</td></tr><tr><td>{n,m}</td><td>The preceding item is matched at least <span class="emphasis"><em>n</em></span> times, but no more than <span class="emphasis"><em>m</em></span> times</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Two regular expressions may be concatenated; the resulting regular
-expression matches any string formed by concatenating two substrings
-that respectively match the concatenated subexpressions.
-</p><p>
-Two regular expressions may be joined by the infix operator “<span class="quote">|</span>”;
-the resulting regular expression matches any string matching either
-subexpression.
-</p><p>
-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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you compile Mutt with the GNU <span class="emphasis"><em>rx</em></span> package, the
-following operators may also be used in regular expressions as described in <a class="xref" href="advancedusage.html#regex-gnu-ext" title="Table 4.3. GNU regular expression extensions">Table 4.3, “GNU regular expression extensions”</a>.
-</p></div><div class="table"><a id="regex-gnu-ext"></a><p class="title"><b>Table 4.3. GNU regular expression extensions</b></p><div class="table-contents"><table summary="GNU regular expression extensions" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Expression</th><th>Description</th></tr></thead><tbody><tr><td>\\y</td><td>Matches the empty string at either the beginning or the end of a word</td></tr><tr><td>\\B</td><td>Matches the empty string within a word</td></tr><tr><td>\\<</td><td>Matches the empty string at the beginning of a word</td></tr><tr><td>\\></td><td>Matches the empty string at the end of a word</td></tr><tr><td>\\w</td><td>Matches any word-constituent character (letter, digit, or underscore)</td></tr><tr><td>\\W</td><td>Matches any character that is not word-constituent</td></tr><tr><td>\\`</td><td>Matches the empty string at the beginning of a buffer (string)</td></tr><tr><td>\\'</td><td>Matches the empty string at the end of a buffer</td></tr></tbody></table></div></div><br class="table-break" /><p>
-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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="patterns"></a>2. Patterns: Searching, Limiting and Tagging</h2></div></div></div><p>
-Many of Mutt's commands allow you to specify a pattern to match
-(<code class="literal">limit</code>, <code class="literal">tag-pattern</code>,
-<code class="literal">delete-pattern</code>, etc.). <a class="xref" href="advancedusage.html#tab-patterns" title="Table 4.4. Pattern modifiers">Table 4.4, “Pattern modifiers”</a>
-shows several ways to select messages.
-</p><div class="table"><a id="tab-patterns"></a><p class="title"><b>Table 4.4. Pattern modifiers</b></p><div class="table-contents"><table summary="Pattern modifiers" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Pattern modifier</th><th>Description</th></tr></thead><tbody><tr><td>~A</td><td>all messages</td></tr><tr><td>~b <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message body</td></tr><tr><td>=b <span class="emphasis"><em>STRING</em></span></td><td>messages which contain <span class="emphasis"><em>STRING</em></span> in the message body. If IMAP is enabled, searches for <span class="emphasis"><em>STRING</em></span> on the server, rather than downloading each message and searching it locally.</td></tr><tr><td>~B <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the whole message</td></tr><tr><td>~c <span class="emphasis"><em>EXPR</em></span></td><td>messages carbon-copied to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%c <span class="emphasis"><em>GROUP</em></span></td><td>messages carbon-copied to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~C <span class="emphasis"><em>EXPR</em></span></td><td>messages either to: or cc: <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%C <span class="emphasis"><em>GROUP</em></span></td><td>messages either to: or cc: to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~d [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-sent</span>” in a Date range</td></tr><tr><td>~D</td><td>deleted messages</td></tr><tr><td>~e <span class="emphasis"><em>EXPR</em></span></td><td>messages which contains <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>%e <span class="emphasis"><em>GROUP</em></span></td><td>messages which contain a member of <span class="emphasis"><em>GROUP</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>~E</td><td>expired messages</td></tr><tr><td>~F</td><td>flagged messages</td></tr><tr><td>~f <span class="emphasis"><em>EXPR</em></span></td><td>messages originating from <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%f <span class="emphasis"><em>GROUP</em></span></td><td>messages originating from any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~g</td><td>cryptographically signed messages</td></tr><tr><td>~G</td><td>cryptographically encrypted messages</td></tr><tr><td>~h <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message header</td></tr><tr><td>~H <span class="emphasis"><em>EXPR</em></span></td><td>messages with a spam attribute matching <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~i <span class="emphasis"><em>EXPR</em></span></td><td>messages which match <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Message-ID</span>” field</td></tr><tr><td>~k</td><td>messages which contain PGP key material</td></tr><tr><td>~L <span class="emphasis"><em>EXPR</em></span></td><td>messages either originated or received by <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%L <span class="emphasis"><em>GROUP</em></span></td><td>message either originated or received by any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~l</td><td>messages addressed to a known mailing list</td></tr><tr><td>~m [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~n [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a score in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~N</td><td>new messages</td></tr><tr><td>~O</td><td>old messages</td></tr><tr><td>~p</td><td>messages addressed to you (consults alternates)</td></tr><tr><td>~P</td><td>messages from you (consults alternates)</td></tr><tr><td>~Q</td><td>messages which have been replied to</td></tr><tr><td>~r [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-received</span>” in a Date range</td></tr><tr><td>~R</td><td>read messages</td></tr><tr><td>~s <span class="emphasis"><em>EXPR</em></span></td><td>messages having <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Subject</span>” field.</td></tr><tr><td>~S</td><td>superseded messages</td></tr><tr><td>~t <span class="emphasis"><em>EXPR</em></span></td><td>messages addressed to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~T</td><td>tagged messages</td></tr><tr><td>~u</td><td>messages addressed to a subscribed mailing list</td></tr><tr><td>~U</td><td>unread messages</td></tr><tr><td>~v</td><td>messages part of a collapsed thread.</td></tr><tr><td>~V</td><td>cryptographically verified messages</td></tr><tr><td>~x <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">References</span>” field</td></tr><tr><td>~X [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> attachments *)</td></tr><tr><td>~y <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">X-Label</span>” field</td></tr><tr><td>~z [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a size in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~=</td><td>duplicated messages (see <a class="link" href="reference.html#duplicate-threads" title="3.49. duplicate_threads">$duplicate_threads</a>)</td></tr><tr><td>~$</td><td>unreferenced messages (requires threaded view)</td></tr><tr><td>~(<span class="emphasis"><em>PATTERN</em></span>)</td><td>messages in threads
-containing messages matching <span class="emphasis"><em>PATTERN</em></span>, e.g. all
-threads containing messages from you: ~(~P)</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Where <span class="emphasis"><em>EXPR</em></span> is a
-<a class="link" href="advancedusage.html#regexp" title="1. Regular Expressions">regular expression</a>. Special attention has to be
-made when using regular expressions inside of patterns. Specifically,
-Mutt's parser for these patterns will strip one level of backslash (“<span class="quote">\</span>”),
-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 (“<span class="quote">\\</span>”). You can force mutt to treat <span class="emphasis"><em>EXPR</em></span> as a simple string
-instead of a regular expression by using = instead of ˜ in the
-pattern name. For example, <code class="literal">=b *.*</code> will find all messages that contain
-the literal string “<span class="quote">*.*</span>”. Simple string matches are less powerful than
-regular expressions but can be considerably faster. This is especially
-true for IMAP folders, because string matches can be performed on the
-server instead of by fetching every message. IMAP treats <code class="literal">=h</code> specially:
-it must be of the form "header: substring" and will not partially
-match header names. The substring part may be omitted if you simply
-wish to find messages containing a particular header without regard to
-its value.
-</p><p>
-*) The forms “<span class="quote"><[<span class="emphasis"><em>MAX</em></span>]</span>”, “<span class="quote">>[<span class="emphasis"><em>MIN</em></span>]</span>”,
-“<span class="quote">[<span class="emphasis"><em>MIN</em></span>]-</span>” and “<span class="quote">-[<span class="emphasis"><em>MAX</em></span>]</span>”
-are allowed, too.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="patterns-modifier"></a>2.1. Pattern Modifier</h3></div></div></div><div class="note"><h3 class="title">Note</h3><p>
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
-match if there is at least one match in the whole list. If you want to
-make sure that all elements of that list match, you need to prefix your
-pattern with “<span class="quote">^</span>”.
-This example matches all mails which only has recipients from Germany.
-</p></div><pre class="screen">
-^~C \.de$
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-patterns"></a>2.2. Simple Patterns</h3></div></div></div><p>
-Mutt supports two versions of so called “<span class="quote">simple searches</span>” which are
-issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
-one of these characters: “<span class="quote">˜</span>”, “<span class="quote">=</span>” or “<span class="quote">%</span>”). If the query is
-supposed to contain one of these special characters, they must be escaped
-by prepending a backslash (“<span class="quote">\</span>”).
-</p><p>
-The first type is by checking whether the query string equals
-a keyword case-insensitively from <a class="xref" href="advancedusage.html#tab-simplesearch-keywords" title="Table 4.5. Simple search keywords">Table 4.5, “Simple search keywords”</a>:
-If that is the case, Mutt will use the shown pattern modifier instead.
-If a keyword would conflict with your search keyword, you need to turn
-it into a regular expression to avoid matching the keyword table. For
-example, if you want to find all messages matching “<span class="quote">flag</span>”
-(using <a class="link" href="reference.html#simple-search" title="3.266. simple_search">$simple_search</a>)
-but don't want to match flagged messages, simply search for
-“<span class="quote"><code class="literal">[f]lag</code></span>”.
-</p><div class="table"><a id="tab-simplesearch-keywords"></a><p class="title"><b>Table 4.5. Simple search keywords</b></p><div class="table-contents"><table summary="Simple search keywords" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Keyword</th><th>Pattern modifier</th></tr></thead><tbody><tr><td>all</td><td>~A</td></tr><tr><td>.</td><td>~A</td></tr><tr><td>^</td><td>~A</td></tr><tr><td>del</td><td>~D</td></tr><tr><td>flag</td><td>~F</td></tr><tr><td>new</td><td>~N</td></tr><tr><td>old</td><td>~O</td></tr><tr><td>repl</td><td>~Q</td></tr><tr><td>read</td><td>~R</td></tr><tr><td>tag</td><td>~T</td></tr><tr><td>unread</td><td>~U</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The second type of simple search is to build a complex search
-pattern using <a class="link" href="reference.html#simple-search" title="3.266. simple_search">$simple_search</a>
-as a template. Mutt will insert your query properly quoted and search
-for the composed complex query.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="complex-patterns"></a>2.3. Complex Patterns</h3></div></div></div><p>
-Logical AND is performed by specifying more than one criterion. For
-example:
-</p><pre class="screen">
-~t mutt ~f elkins
-</pre><p>
-would select messages which contain the word “<span class="quote">mutt</span>” in the list of
-recipients <span class="bold"><strong>and</strong></span> that have the word “<span class="quote">elkins</span>” in the “<span class="quote">From</span>” header
-field.
-</p><p>
-Mutt also recognizes the following operators to create more complex search
-patterns:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-! -- logical NOT operator
-</p></li><li><p>
-| -- logical OR operator
-</p></li><li><p>
-() -- logical grouping operator
-</p></li></ul></div><p>
-Here is an example illustrating a complex search pattern. This pattern will
-select all messages which do not contain “<span class="quote">mutt</span>” in the “<span class="quote">To</span>” or “<span class="quote">Cc</span>”
-field and which are from “<span class="quote">elkins</span>”.
-</p><div class="example"><a id="ex-pattern-bool"></a><p class="title"><b>Example 4.1. Using boolean operators in patterns</b></p><div class="example-contents"><pre class="screen">
-!(~t mutt|~c mutt) ~f elkins
-</pre></div></div><br class="example-break" /><p>
-Here is an example using white space in the regular expression (note
-the ' and " delimiters). For this to match, the mail's subject must
-match the “<span class="quote">^Junk +From +Me$</span>” and it must be from either “<span class="quote">Jim +Somebody</span>”
-or “<span class="quote">Ed +SomeoneElse</span>”:
-</p><pre class="screen">
- '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
-</pre><div class="note"><h3 class="title">Note</h3><p>
-If a regular expression contains parenthesis, or a vertical bar
-("|"), you <span class="bold"><strong>must</strong></span> enclose the expression in double or single quotes since
-those characters are also used to separate different parts of Mutt's
-pattern language. For example: <code class="literal">~f "me@(mutt\.org|cs\.hmc\.edu)"</code>
-</p></div><p>
-Without the quotes, the parenthesis wouldn't end.
-This would be separated to two OR'd patterns: <span class="emphasis"><em>˜f me@(mutt\.org</em></span>
-and <span class="emphasis"><em>cs\.hmc\.edu)</em></span>. They are never what you want.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-patterns"></a>2.4. Searching by Date</h3></div></div></div><p>
-Mutt supports two types of dates, <span class="emphasis"><em>absolute</em></span> and <span class="emphasis"><em>relative</em></span>.
-</p><p>
-<span class="bold"><strong>Absolute</strong></span>. Dates <span class="bold"><strong>must</strong></span> be in DD/MM/YY format (month and year are
-optional, defaulting to the current month and year). An example of a valid
-range of dates is:
-</p><pre class="screen">
-Limit to messages matching: ~d 20/1/95-31/10
-</pre><p>
-If you omit the minimum (first) date, and just specify “<span class="quote">-DD/MM/YY</span>”, all
-messages <span class="emphasis"><em>before</em></span> the given date will be selected. If you omit the maximum
-(second) date, and specify “<span class="quote">DD/MM/YY-</span>”, all messages <span class="emphasis"><em>after</em></span> the given
-date will be selected. If you specify a single date with no dash (“<span class="quote">-</span>”),
-only messages sent on the given date will be selected.
-</p><p>
-<span class="bold"><strong>Error Margins</strong></span>. You can add error margins to absolute dates.
-An error margin is a sign (+ or -), followed by a digit, followed by
-one of the units in <a class="xref" href="advancedusage.html#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>. As a special case, you can replace the
-sign by a “<span class="quote">*</span>” character, which is equivalent to giving identical plus and minus error margins.
-</p><div class="table"><a id="tab-date-units"></a><p class="title"><b>Table 4.6. Date units</b></p><div class="table-contents"><table summary="Date units" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Unit</th><th>Description</th></tr></thead><tbody><tr><td>y</td><td>Years</td></tr><tr><td>m</td><td>Months</td></tr><tr><td>w</td><td>Weeks</td></tr><tr><td>d</td><td>Days</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Example: To select any messages two weeks around January 15, 2001,
-you'd use the following pattern:
-</p><pre class="screen">
-Limit to messages matching: ~d 15/1/2001*2w
-</pre><p>
-<span class="bold"><strong>Relative</strong></span>. This type of date is relative to the current date, and may
-be specified as:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-><span class="emphasis"><em>offset</em></span> (messages older than <span class="emphasis"><em>offset</em></span> units)
-</p></li><li><p>
-<<span class="emphasis"><em>offset</em></span> (messages newer than <span class="emphasis"><em>offset</em></span> units)
-</p></li><li><p>
-=<span class="emphasis"><em>offset</em></span> (messages exactly <span class="emphasis"><em>offset</em></span> units old)
-</p></li></ul></div><p>
-<span class="emphasis"><em>offset</em></span> is specified as a positive number with one of the units from <a class="xref" href="advancedusage.html#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>.
-</p><p>
-Example: to select messages less than 1 month old, you would use
-</p><pre class="screen">
-Limit to messages matching: ~d <1m
-</pre><div class="note"><h3 class="title">Note</h3><p>
-All dates used when searching are relative to the
-<span class="bold"><strong>local</strong></span> time zone, so unless you change the setting of your <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> to include a
-<code class="literal">%[...]</code> format, these are <span class="bold"><strong>not</strong></span> the dates shown
-in the main index.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tags"></a>3. Using Tags</h2></div></div></div><p>
-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 <code class="literal"><tag-pattern></code> function, which is bound to
-“<span class="quote">shift-T</span>” by default. Or you can select individual messages by
-hand using the <code class="literal"><tag-message></code> function, which is bound to “<span class="quote">t</span>” by
-default. See <a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> for Mutt's pattern
-matching syntax.
-</p><p>
-Once you have tagged the desired messages, you can use the
-“<span class="quote">tag-prefix</span>” operator, which is the “<span class="quote">;</span>” (semicolon) key by default.
-When the “<span class="quote">tag-prefix</span>” operator is used, the <span class="bold"><strong>next</strong></span> operation will
-be applied to all tagged messages if that operation can be used in that
-manner. If the <a class="link" href="reference.html#auto-tag" title="3.18. auto_tag">$auto_tag</a>
-variable is set, the next operation applies to the tagged messages
-automatically, without requiring the “<span class="quote">tag-prefix</span>”.
-</p><p>
-In <a class="link" href="configuration.html#macro" title="8. Keyboard macros">macros</a> or <a class="link" href="configuration.html#push" title="22. Adding key sequences to the keyboard buffer">push</a> commands,
-you can use the “<span class="quote">tag-prefix-cond</span>” operator. If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the “<span class="quote">end-cond</span>”
-operator; after this operator the rest of the macro will be executed as
-normal.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="hooks"></a>4. Using Hooks</h2></div></div></div><p>
-A <span class="emphasis"><em>hook</em></span> is a concept found in many other programs 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 world, a <span class="emphasis"><em>hook</em></span>
-consists of a <a class="link" href="advancedusage.html#regexp" title="1. Regular Expressions">regular expression</a> or
-<a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">pattern</a> along with a
-configuration option/command. See
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="link" href="configuration.html#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#message-hook" title="20. Change settings before formatting a message">message-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a>
-</p></li></ul></div><p>
-
-for specific details on each type of <span class="emphasis"><em>hook</em></span> available.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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:
-</p></div><div class="example"><a id="ex-send-hook-my-hdr"></a><p class="title"><b>Example 4.2. Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></b></p><div class="example-contents"><pre class="screen">
-send-hook . 'unmy_hdr From:'
-send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-</pre></div></div><br class="example-break" /><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pattern-hook"></a>4.1. Message Matching in Hooks</h3></div></div></div><p>
-Hooks that act upon messages (<code class="literal">message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook</code>) are evaluated in a
-slightly different manner. For the other
-types of hooks, a <a class="link" href="advancedusage.html#regexp" title="1. Regular Expressions">regular expression</a> 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.
-</p><p>
-Mutt allows the use of the <a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">search pattern</a>
-language for matching messages in hook commands. This works in
-exactly the same way as it would when <span class="emphasis"><em>limiting</em></span> or
-<span class="emphasis"><em>searching</em></span> 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.).
-</p><p>
-For example, if you wanted to set your return address based upon sending
-mail to a specific address, you could do something like:
-</p><pre class="screen">
-send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
-</pre><p>
-which would execute the given command when sending mail to
-<span class="emphasis"><em>me@cs.hmc.edu</em></span>.
-</p><p>
-However, it is not required that you write the pattern to match using the
-full searching language. You can still specify a simple <span class="emphasis"><em>regular
-expression</em></span> like the other hooks, in which case Mutt will translate your
-pattern into the full language, using the translation specified by the
-<a class="link" href="reference.html#default-hook" title="3.41. default_hook">$default_hook</a> variable. The
-pattern is translated at the time the hook is declared, so the value of
-<a class="link" href="reference.html#default-hook" title="3.41. default_hook">$default_hook</a> that is in effect
-at that time will be used.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="query"></a>5. External Address Queries</h2></div></div></div><p>
-Mutt 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 <a class="link" href="reference.html#query-command" title="3.234. query_command">$query_command</a> variable, you specify the wrapper
-command to use. For example:
-</p><pre class="screen">
-set query_command = "mutt_ldap_query.pl '%s'"
-</pre><p>
-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 then
-some other optional information. On error, or if there are no matching
-addresses, return a non-zero exit code and a one line error message.
-</p><p>
-An example multiple response output:
-</p><pre class="screen">
-Searching database ... 20 entries ... 3 matching:
-me@cs.hmc.edu Michael Elkins mutt dude
-blong@fiction.net Brandon Long mutt and more
-roessler@does-not-exist.org Thomas Roessler mutt pgp
-</pre><p>
-There are two mechanisms for accessing the query function of mutt. One
-is to do a query from the index menu using the <code class="literal"><query></code> 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 addresses
-to mail, start a new query, or have a new query appended to the current
-responses.
-</p><p>
-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 <code class="literal"><complete-query></code> 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 query
-menu. At the query menu, you can select one or more addresses to be
-added to the prompt.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailbox-formats"></a>6. Mailbox Formats</h2></div></div></div><p>
-Mutt 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 new
-mailboxes, Mutt uses the default specified with the <a class="link" href="reference.html#mbox-type" title="3.117. mbox_type">$mbox_type</a> variable.
-</p><p>
-<span class="bold"><strong>mbox</strong></span>. 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:
-</p><pre class="screen">
-From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-</pre><p>
-to denote the start of a new message (this is often referred to as the
-“<span class="quote">From_</span>” line).
-</p><p>
-<span class="bold"><strong>MMDF</strong></span>. This is a variant of the <span class="emphasis"><em>mbox</em></span> format. Each message is
-surrounded by lines containing “<span class="quote">^A^A^A^A</span>” (four control-A's).
-</p><p>
-<span class="bold"><strong>MH</strong></span>. A radical departure from <span class="emphasis"><em>mbox</em></span> and <span class="emphasis"><em>MMDF</em></span>, 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 displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
-detects this type of mailbox by looking for either <code class="literal">.mh_sequences</code>
-or <code class="literal">.xmhcache</code> (needed to distinguish normal directories from MH
-mailboxes).
-</p><p>
-<span class="bold"><strong>Maildir</strong></span>. The newest of the mailbox formats, used by the Qmail MTA (a
-replacement for sendmail). Similar to <span class="emphasis"><em>MH</em></span>, except that it adds three
-subdirectories of the mailbox: <span class="emphasis"><em>tmp</em></span>, <span class="emphasis"><em>new</em></span> and <span class="emphasis"><em>cur</em></span>. Filenames
-for the messages are chosen in such a way they are unique, even when two
-programs are writing the mailbox over NFS, which means that no file locking
-is needed.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="shortcuts"></a>7. Mailbox Shortcuts</h2></div></div></div><p>
-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.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-! -- refers to your <a class="link" href="reference.html#spoolfile" title="3.279. spoolfile">$spoolfile</a> (incoming) mailbox
-</p></li><li><p>
-> -- refers to your <a class="link" href="reference.html#mbox" title="3.116. mbox">$mbox</a> file
-</p></li><li><p>
-< -- refers to your <a class="link" href="reference.html#record" title="3.242. record">$record</a> file
-</p></li><li><p>
-^ -- refers to the current mailbox
-</p></li><li><p>
-- or !! -- refers to the file you've last visited
-</p></li><li><p>
-˜ -- refers to your home directory
-</p></li><li><p>
-= or + -- refers to your <a class="link" href="reference.html#folder" title="3.58. folder">$folder</a> directory
-</p></li><li><p>
-@<span class="emphasis"><em>alias</em></span> -- refers to the <a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">default save folder</a> as determined by the address of the alias
-</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-lists"></a>8. Handling Mailing Lists</h2></div></div></div><p>
-Mutt 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 <a class="link" href="configuration.html#lists" title="12. Mailing lists">lists and subscribe</a> commands in your muttrc.
-</p><p>
-Now that Mutt 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 <span class="emphasis"><em>index</em></span> menu display. This is useful to distinguish between
-personal and list mail in the same mailbox. In the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable, the escape “<span class="quote">%L</span>”
-will return the string “<span class="quote">To <list></span>” when “<span class="quote">list</span>” appears in the
-“<span class="quote">To</span>” field, and “<span class="quote">Cc <list></span>” when it appears in the “<span class="quote">Cc</span>”
-field (otherwise it returns the name of the author).
-</p><p>
-Often times the “<span class="quote">To</span>” and “<span class="quote">Cc</span>” fields in mailing list messages
-tend to get quite large. Most people do not bother to remove the
-author of the message they reply to from the list, resulting in
-two or more copies being sent to that person. The <code class="literal"><list-reply></code>
-function, which by default is bound to “<span class="quote">L</span>” in the <span class="emphasis"><em>index</em></span> menu
-and <span class="emphasis"><em>pager</em></span>, helps reduce the clutter by only replying to the
-known mailing list addresses instead of all recipients (except as
-specified by <code class="literal">Mail-Followup-To</code>, see below).
-</p><p>
-Mutt also supports the <code class="literal">Mail-Followup-To</code> header. When you send
-a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the <a class="link" href="reference.html#followup-to" title="3.60. followup_to">$followup_to</a> 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 “<span class="quote">followups</span>”) 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.
-</p><p>
-Conversely, when group-replying or list-replying to a message which
-has a <code class="literal">Mail-Followup-To</code> header, mutt will respect this header if
-the <a class="link" href="reference.html#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a> 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 <code class="literal">Mail-Followup-To</code>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-When header editing is enabled, you can create a
-<code class="literal">Mail-Followup-To</code> header manually. Mutt will only auto-generate
-this header if it doesn't exist when you send the message.
-</p></div><p>
-The other method some mailing list admins use is to generate a
-“<span class="quote">Reply-To</span>” 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 “<span class="quote">Reply-To</span>”
-field. Mutt uses the <a class="link" href="reference.html#reply-to" title="3.245. reply_to">$reply_to</a>
-variable to help decide which address to use. If set to <span class="emphasis"><em>ask-yes</em></span> or
-<span class="emphasis"><em>ask-no</em></span>, you will be
-prompted as to whether or not you would like to use the address given in
-the “<span class="quote">Reply-To</span>” field, or reply directly to the address given in the
-“<span class="quote">From</span>” field. When set to <span class="emphasis"><em>yes</em></span>, the “<span class="quote">Reply-To</span>” field will be used when
-present.
-</p><p>
-The “<span class="quote">X-Label:</span>” header field can be used to further identify mailing
-lists or list subject matter (or just to annotate messages
-individually). The <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable's “<span class="quote">%y</span>” and
-“<span class="quote">%Y</span>” escapes can be used to expand “<span class="quote">X-Label:</span>” fields in the
-index, and Mutt's pattern-matcher can match regular expressions to
-“<span class="quote">X-Label:</span>” fields with the “<span class="quote">˜y</span>” selector. “<span class="quote">X-Label:</span>” is not a
-standard message header field, but it can easily be inserted by procmail
-and other mail filtering agents.
-</p><p>
-Lastly, Mutt has the ability to <a class="link" href="reference.html#sort" title="3.273. sort">sort</a> the mailbox into
-<a class="link" href="gettingstarted.html#threads" title="4.3. Threaded Mode">threads</a>. 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 dealing
-with large volume mailing lists easier because you can easily delete
-uninteresting threads and quickly find topics of value.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="handling-folders"></a>9. Handling multiple folders</h2></div></div></div><p>
-Mutt supports setups with multiple folders, allowing all of them to
-be monitored for new mail (see <a class="xref" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">Section 14, “Monitoring incoming mail”</a> for details).
-</p><p>
-When in the index menu and being idle (also see
-<a class="link" href="reference.html#timeout" title="3.290. timeout">$timeout</a>), Mutt periodically checks
-for new mail in all folders which have been configured via the
-<code class="literal">mailboxes</code> command. The interval depends on the folder
-type: for local/IMAP folders it consults
-<a class="link" href="reference.html#mail-check" title="3.105. mail_check">$mail_check</a> and
-<a class="link" href="reference.html#pop-checkinterval" title="3.218. pop_checkinterval">$pop_checkinterval</a>
-for POP folders.
-</p><p>
-Outside the index menu the directory browser supports checking
-for new mail using the <code class="literal"><check-new></code> function which is
-unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the <code class="literal">mailboxes</code> command,
-and indicate which contain new messages. Mutt will automatically enter this
-mode when invoked from the command line with the <code class="literal">-y</code> option.
-</p><p>
-For the pager, index and directory browser menus, Mutt contains the
-<code class="literal"><buffy-list></code> function (bound to “<span class="quote">.</span>” by default)
-which will print a list of folders with new mail in the command line at
-the bottom of the screen.
-</p><p>
-For the index, by default Mutt displays the number of mailboxes with new
-mail in the status bar, please refer to the
-<a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>
-variable for details.
-</p><p>
-When changing folders, Mutt fills the prompt with the first folder from
-the mailboxes list containing new mail (if any), pressing
-<span class="emphasis"><em>space</em></span> will cycle through folders with new mail.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing-threads"></a>10. Editing threads</h2></div></div></div><p>
-Mutt 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.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="link-threads"></a>10.1. Linking threads</h3></div></div></div><p>
-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 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 <code class="literal"><link-threads></code> function (bound to & by default). The
-reply will then be connected to this "parent" message.
-</p><p>
-You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="break-threads"></a>10.2. Breaking threads</h3></div></div></div><p>
-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 <code class="literal"><break-thread></code> function (bound
-by default to #), which will turn the subthread starting from the
-current message into a whole different thread.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="dsn"></a>11. Delivery Status Notification (DSN) Support</h2></div></div></div><p>
-RFC1894 defines a set of MIME content types for relaying information
-about the status of electronic mail messages. These can be thought of as
-“<span class="quote">return receipts.</span>”
-</p><p>
-To support DSN, there are two variables. <a class="link" href="reference.html#dsn-notify" title="3.47. dsn_notify">$dsn_notify</a> is used to request receipts for
-different results (such as failed message, message delivered, etc.).
-<a class="link" href="reference.html#dsn-return" title="3.48. dsn_return">$dsn_return</a> requests how much
-of your message should be returned with the receipt (headers or full
-message).
-</p><p>
-When using <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a> for mail
-delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA
-supporting DSN command line options compatible to Sendmail: The -N and -R
-options can be used by the mail client to make requests as to what type of
-status messages should be returned. Please consider your MTA documentation
-whether DSN is supported.
-</p><p>
-For SMTP delivery using <a class="link" href="reference.html#smtp-url" title="3.272. smtp_url">$smtp_url</a>, it depends on the
-capabilities announced by the server whether mutt will attempt to
-request DSN or not.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="urlview"></a>12. Start a WWW Browser on URLs</h2></div></div></div><p>
-If a message contains URLs, 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
-<a class="ulink" href="ftp://ftp.mutt.org/mutt/contrib/" target="_top">ftp://ftp.mutt.org/mutt/contrib/</a>
-and the configuration commands:
-</p><pre class="screen">
-macro index \cb |urlview\n
-macro pager \cb |urlview\n
-</pre></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="configuration.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="mimesupport.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. Mutt's MIME Support</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. Configuration</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="gettingstarted.html" title="Chapter 2. Getting Started" /><link rel="next" href="advancedusage.html" title="Chapter 4. Advanced Usage" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gettingstarted.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="advancedusage.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="configuration"></a>Chapter 3. Configuration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="configuration.html#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="configuration.html#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="configuration.html#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="configuration.html#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="configuration.html#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="configuration.html#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="configuration.html#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="configuration.html#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="configuration.html#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="configuration.html#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="configuration.html#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="configuration.html#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="configuration.html#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="configuration.html#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="configuration.html#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="configuration.html#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="configuration.html#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="configuration.html#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="configuration.html#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="configuration.html#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="configuration.html#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="configuration.html#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="configuration.html#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="configuration.html#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="configuration.html#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="configuration.html#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="configuration.html#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="configuration.html#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="configuration.html#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="configuration.html#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="configuration.html#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="configuration.html#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="configuration.html#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="configuration.html#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="configuration-files"></a>1. Location of initialization files</h2></div></div></div><p>
-While the default configuration (or “<span class="quote">preferences</span>”) make Mutt
-usable right out of the box, it is often desirable to tailor Mutt to
-suit your own tastes. When Mutt is first invoked, it will attempt to
-read the “<span class="quote">system</span>” configuration file (defaults set by your local
-system administrator), unless the “<span class="quote">-n</span>” <a class="link" href="reference.html#commandline" title="1. Command line options">command line</a> option is specified. This file is typically
-<code class="literal">/usr/local/share/mutt/Muttrc</code> or <code class="literal">/etc/Muttrc</code>. Mutt
-will next look for a file named <code class="literal">.muttrc</code> in your home
-directory. If this file does not exist and your home directory has
-a subdirectory named <code class="literal">.mutt</code>, mutt try to load a file named
-<code class="literal">.mutt/muttrc</code>.
-</p><p>
-<code class="literal">.muttrc</code> is the file where you will usually place your <a class="link" href="reference.html#commands" title="2. Configuration Commands">commands</a> to configure Mutt.
-</p><p>
-In addition, mutt supports version specific configuration files that are
-parsed instead of the default files as explained above. For instance, if
-your system has a <code class="literal">Muttrc-0.88</code> file in the system configuration
-directory, and you are running version 0.88 of mutt, this file will be
-sourced instead of the <code class="literal">Muttrc</code> file. The same is true of the user
-configuration file, if you have a file <code class="literal">.muttrc-0.88.6</code> in your home
-directory, when you run mutt version 0.88.6, it will source this file
-instead of the default <code class="literal">.muttrc</code> file. The version number is the
-same which is visible using the “<span class="quote">-v</span>” <a class="link" href="reference.html#commandline" title="1. Command line options">command line</a> switch or using the <code class="literal">show-version</code> key (default:
-V) from the index menu.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttrc-syntax"></a>2. Syntax of Initialization Files</h2></div></div></div><p>
-An initialization file consists of a series of <a class="link" href="reference.html#commands" title="2. Configuration Commands">commands</a>. Each line of the file may contain one or more commands.
-When multiple commands are used, they must be separated by a semicolon
-(;).
-</p><div class="example"><a id="ex-rc-multiple-cmds"></a><p class="title"><b>Example 3.1. Multiple configuration commands per line</b></p><div class="example-contents"><pre class="screen">
-set realname='Mutt user' ; ignore x-
-</pre></div></div><br class="example-break" /><p>
-The hash mark, or pound sign
-(“<span class="quote">#</span>”), is used as a “<span class="quote">comment</span>” 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,
-</p><div class="example"><a id="ex-ec-comment"></a><p class="title"><b>Example 3.2. Commenting configuration files</b></p><div class="example-contents"><pre class="screen">
-my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
-</pre></div></div><br class="example-break" /><p>
-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, backticks are evaluated inside of double
-quotes, but <span class="bold"><strong>not</strong></span> for single quotes.
-</p><p>
-\ quotes the next character, just as in shells such as bash and zsh.
-For example, if want to put quotes “<span class="quote">"</span>” inside of a string, you can use
-“<span class="quote">\</span>” to force the next character to be a literal instead of interpreted
-character.
-</p><div class="example"><a id="ex-rc-quote"></a><p class="title"><b>Example 3.3. Escaping quotes in congfiguration files</b></p><div class="example-contents"><pre class="screen">
-set realname="Michael \"MuttDude\" Elkins"
-</pre></div></div><br class="example-break" /><p>
-“<span class="quote">\\</span>” means to insert a literal “<span class="quote">\</span>” into the line.
-“<span class="quote">\n</span>” and “<span class="quote">\r</span>” have their usual C meanings of linefeed and
-carriage-return, respectively.
-</p><p>
-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.
-</p><p>
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command in
-backticks (``). For example,
-</p><div class="example"><a id="ex-rc-backtick"></a><p class="title"><b>Example 3.4. Using external command's output in configuration files</b></p><div class="example-contents"><pre class="screen">
-my_hdr X-Operating-System: `uname -a`
-</pre></div></div><br class="example-break" /><p>
-The output of the Unix command “<span class="quote">uname -a</span>” will be substituted before the
-line is parsed.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Since initialization files are line oriented, only
-the first line of output from the Unix command will be substituted.
-</p></div><p>
-Both environment variables and mutt variables can be accessed by
-prepending “<span class="quote">$</span>” to the name of the variable. For example,
-</p><div class="example"><a id="ex-rc-env"></a><p class="title"><b>Example 3.5. Using environment variables in configuration files</b></p><div class="example-contents"><pre class="screen">
-set record=+sent_on_$HOSTNAME
-</pre></div></div><br class="example-break" /><p>
-will cause mutt to save outgoing messages to a folder named
-“<span class="quote">sent_on_kremvax</span>” if the environment variable HOSTNAME is set to
-“<span class="quote">kremvax.</span>” (See <a class="link" href="reference.html#record" title="3.242. record">$record</a> for
-details.)
-</p><p>
-Mutt expands the variable when it is assigned, not when it is used. If
-the value of a variable on the right-hand side of an assignment
-changes after the assignment, the variable on the left-hand side will
-not be affected.
-</p><p>
-The commands understood by mutt are explained in the next paragraphs.
-For a complete list, see the <a class="link" href="reference.html#commands" title="2. Configuration Commands">command reference</a>.
-</p><p>
-All configuration files are expected to be in the current locale as
-specified by the <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> variable
-which doesn't have a default value since it's determined by Mutt at startup.
-If a configuration file is not encoded in the same character set the
-<a class="link" href="reference.html#config-charset" title="3.30. config_charset">$config_charset</a>
-variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
-</p><p>
-This mechanism should be avoided if possible as it has the
-following implications:
-</p><div class="itemizedlist"><ul type="disc"><li><p>These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.</p></li><li><p>If $config_charset is set, it should be set
-in each configuration file because the value is global and <span class="emphasis"><em>not</em></span>
-per configuration file.</p></li><li><p>Because Mutt first recodes a line before it attempts to parse it,
-a conversion introducing question marks or other characters as
-part of errors (unconvertable characters, transliteration) may introduce syntax
-errors or silently change the meaning of certain tokens (e.g. inserting
-question marks into regular expressions).</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="addrgroup"></a>3. Address groups</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">group</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div><div class="cmdsynopsis"><p><code class="command">ungroup</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div><p>
-<code class="literal">group</code> is used to directly add either addresses or
-regular expressions to the specified group or groups. The different
-categories of arguments to the <code class="literal">group</code> command can be
-in any order. The flags <code class="literal">-rx</code> and
-<code class="literal">-addr</code> specify what the following strings (that cannot
-begin with a hyphen) should be interpreted as: either a regular
-expression or an email address, respectively.
-</p><p>
-These address groups can also be created implicitly by the
-<a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">alias</a>, <a class="link" href="configuration.html#lists" title="12. Mailing lists">lists</a>,
-<a class="link" href="configuration.html#lists" title="12. Mailing lists">subscribe</a> and
-<a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a> commands by specifying the
-optional <code class="literal">-group</code> option.
-</p><p>
-Once defined, these address groups can be used in
-<a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> to search for and limit the
-display to messages matching a group.
-</p><p>
-<code class="literal">ungroup</code> is used to remove addresses or regular
-expressions from the specified group or groups. The syntax is similar to
-the <code class="literal">group</code> command, however the special character
-<code class="literal">*</code> can be used to empty a group of all of its
-contents.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alias"></a>4. Defining/Using aliases</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alias</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>address</code></em>
- [
-<em class="replaceable"><code>address</code></em>
-...]</p></div><p>
-It's usually very cumbersome to remember or type out the address of someone
-you are communicating with. Mutt allows you to create “<span class="quote">aliases</span>” which map
-a short string to a full address.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you want to create an alias for more than
-one address, you <span class="bold"><strong>must</strong></span> separate the addresses with a comma (“<span class="quote">,</span>”).
-</p></div><p>
-The optional <code class="literal">-group</code> argument to
-<code class="literal">alias</code> causes the aliased address(es) to be added to
-the named <span class="emphasis"><em>group</em></span>.
-</p><p>
-To remove an alias or aliases (“<span class="quote">*</span>” means all aliases):
-</p><div class="cmdsynopsis"><p><code class="command">unalias</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>key</code></em>
-... }</p></div><pre class="screen">
-alias muttdude me@cs.hmc.edu (Michael Elkins)
-alias theguys manny, moe, jack
-</pre><p>
-Unlike other mailers, Mutt doesn't require aliases to be defined
-in a special file. The <code class="literal">alias</code> command can appear anywhere in
-a configuration file, as long as this file is <a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">sourced</a>. Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
-</p><p>
-On the other hand, the <a class="link" href="gettingstarted.html#create-alias"><code class="literal"><create-alias></code></a>
-function can use only one file, the one pointed to by the <a class="link" href="reference.html#alias-file" title="3.3. alias_file">$alias_file</a> variable (which is
-<code class="literal">˜/.muttrc</code> by default). This file is not special either,
-in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly <a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a> this file too.
-</p><p>
-For example:
-</p><div class="example"><a id="ex-alias-external"></a><p class="title"><b>Example 3.6. Configuring external alias files</b></p><div class="example-contents"><pre class="screen">
-source /usr/local/share/Mutt.aliases
-source ~/.mail_aliases
-set alias_file=~/.mail_aliases
-</pre></div></div><br class="example-break" /><p>
-To use aliases, you merely use the alias at any place in mutt where mutt
-prompts for addresses, such as the <span class="emphasis"><em>To:</em></span> or <span class="emphasis"><em>Cc:</em></span> prompt. You can
-also enter aliases in your editor at the appropriate headers if you have the
-<a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable set.
-</p><p>
-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.
-</p><p>
-In the alias menu, you can select as many aliases as you want with the
-<code class="literal">select-entry</code> key (default: <Return>), and use the
-<span class="emphasis"><em>exit</em></span> key (default: q) to return to the address prompt.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="bind"></a>5. Changing the default key bindings</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">bind</code>
-<em class="replaceable"><code>map</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>function</code></em>
- </p></div><p>
-This command allows you to change the default key bindings (operation
-invoked when pressing a key).
-</p><p>
-<span class="emphasis"><em>map</em></span> specifies in which menu the binding belongs. Multiple maps may
-be specified by separating them with commas (no additional whitespace is
-allowed). The currently defined maps are:
-</p><a id="maps"></a><div class="variablelist"><dl><dt><span class="term">generic</span></dt><dd><p>
-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 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.
-</p></dd><dt><span class="term">alias</span></dt><dd><p>
-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).
-</p></dd><dt><span class="term">attach</span></dt><dd><p>
-The attachment menu is used to access the attachments on received messages.
-</p></dd><dt><span class="term">browser</span></dt><dd><p>
-The browser is used for both browsing the local directory structure, and for
-listing all of your incoming mailboxes.
-</p></dd><dt><span class="term">editor</span></dt><dd><p>
-The editor is the line-based editor the user enters text data.
-</p></dd><dt><span class="term">index</span></dt><dd><p>
-The index is the list of messages contained in a mailbox.
-</p></dd><dt><span class="term">compose</span></dt><dd><p>
-The compose menu is the screen used when sending a new message.
-</p></dd><dt><span class="term">pager</span></dt><dd><p>
-The pager is the mode used to display message/attachment data, and help
-listings.
-</p></dd><dt><span class="term">pgp</span></dt><dd><p>
-The pgp menu is used to select the OpenPGP keys used to encrypt outgoing
-messages.
-</p></dd><dt><span class="term">smime</span></dt><dd><p>
-The smime menu is used to select the OpenSSL certificates used to encrypt outgoing
-messages.
-</p></dd><dt><span class="term">postpone</span></dt><dd><p>
-The postpone menu is similar to the index menu, except is used when
-recalling a message the user was composing, but saved until later.
-</p></dd><dt><span class="term">query</span></dt><dd><p>
-The query menu is the browser for results returned by
-<a class="link" href="reference.html#query-command" title="3.234. query_command">$query_command</a>.
-</p></dd><dt><span class="term">mix</span></dt><dd><p>
-The mixmaster screen is used to select remailer options for outgoing
-messages (if Mutt is compiled with Mixmaster support).
-</p></dd></dl></div><p>
-<span class="emphasis"><em>key</em></span> is the key (or key sequence) you wish to bind. To specify a
-control character, use the sequence <span class="emphasis"><em>\Cx</em></span>, where <span class="emphasis"><em>x</em></span> is the
-letter of the control character (for example, to specify control-A use
-“<span class="quote">\Ca</span>”). Note that the case of <span class="emphasis"><em>x</em></span> as well as <span class="emphasis"><em>\C</em></span> is
-ignored, so that <span class="emphasis"><em>\CA</em></span>, <span class="emphasis"><em>\Ca</em></span>, <span class="emphasis"><em>\cA</em></span> and <span class="emphasis"><em>\ca</em></span> are all
-equivalent. An alternative form is to specify the key as a three digit
-octal number prefixed with a “<span class="quote">\</span>” (for example <span class="emphasis"><em>\177</em></span> is
-equivalent to <span class="emphasis"><em>\c?</em></span>). In addition, <span class="emphasis"><em>key</em></span> may
-be a symbolic name as shown in <a class="xref" href="configuration.html#tab-key-names" title="Table 3.1. Symbolic key names">Table 3.1, “Symbolic key names”</a>.
-</p><div class="table"><a id="tab-key-names"></a><p class="title"><b>Table 3.1. Symbolic key names</b></p><div class="table-contents"><table summary="Symbolic key names" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Symbolic name</th><th>Meaning</th></tr></thead><tbody><tr><td>\t</td><td>tab</td></tr><tr><td><tab></td><td>tab</td></tr><tr><td><backtab></td><td>backtab / shift-tab</td></tr><tr><td>\r</td><td>carriage return</td></tr><tr><td>\n</td><td>newline</td></tr><tr><td>\e</td><td>escape</td></tr><tr><td><esc></td><td>escape</td></tr><tr><td><up></td><td>up arrow</td></tr><tr><td><down></td><td>down arrow</td></tr><tr><td><left></td><td>left arrow</td></tr><tr><td><right></td><td>right arrow</td></tr><tr><td><pageup></td><td>Page Up</td></tr><tr><td><pagedown></td><td>Page Down</td></tr><tr><td><backspace></td><td>Backspace</td></tr><tr><td><delete></td><td>Delete</td></tr><tr><td><insert></td><td>Insert</td></tr><tr><td><enter></td><td>Enter</td></tr><tr><td><return></td><td>Return</td></tr><tr><td><home></td><td>Home</td></tr><tr><td><end></td><td>End</td></tr><tr><td><space></td><td>Space bar</td></tr><tr><td><f1></td><td>function key 1</td></tr><tr><td><f10></td><td>function key 10</td></tr></tbody></table></div></div><br class="table-break" /><p>
-<span class="emphasis"><em>key</em></span> does not need to be enclosed in quotes unless it contains a
-space (“<span class="quote"> </span>”) or semi-colon (“<span class="quote">;</span>”).
-</p><p>
-<span class="emphasis"><em>function</em></span> specifies which action to take when <span class="emphasis"><em>key</em></span> is pressed.
-For a complete list of functions, see the <a class="link" href="reference.html#functions" title="4. Functions">reference</a>. The special function <code class="literal"><noop></code> unbinds the specified key
-sequence.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="charset-hook"></a>6. Defining aliases for character sets </h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">charset-hook</code>
-<em class="replaceable"><code>alias</code></em>
-
-<em class="replaceable"><code>charset</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">iconv-hook</code>
-<em class="replaceable"><code>charset</code></em>
-
-<em class="replaceable"><code>local-charset</code></em>
- </p></div><p>
-The <code class="literal">charset-hook</code> 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.
-</p><p>
-The <code class="literal">iconv-hook</code> 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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="folder-hook"></a>7. Setting variables based upon mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">folder-hook</code>
-<em class="replaceable"><code>[!]regexp</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-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. <span class="emphasis"><em>regexp</em></span> is a regular expression specifying
-in which mailboxes to execute <span class="emphasis"><em>command</em></span> before loading. If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you use the “<span class="quote">!</span>” shortcut for <a class="link" href="reference.html#spoolfile" title="3.279. spoolfile">$spoolfile</a> at the beginning of the pattern, you must place it
-inside of double or single quotes in order to distinguish it from the
-logical <span class="emphasis"><em>not</em></span> operator for the expression.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-Settings are <span class="emphasis"><em>not</em></span> restored when you leave the mailbox.
-For example, a command action to perform is to change the sorting method
-based upon the mailbox being read:
-</p></div><pre class="screen">
-folder-hook mutt set sort=threads
-</pre><p>
-However, the sorting method is not restored to its previous value when
-reading a different mailbox. To specify a <span class="emphasis"><em>default</em></span> command, use the
-pattern “<span class="quote">.</span>” before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
-The following example will set the <a class="link" href="reference.html#sort" title="3.273. sort">sort</a> variable
-to <code class="literal">date-sent</code> for all folders but to <code class="literal">threads</code>
-for all folders containing “<span class="quote">mutt</span>” in their name.
-</p><div class="example"><a id="ex-folder-sorting"></a><p class="title"><b>Example 3.7. Setting sort method based on mailbox name</b></p><div class="example-contents"><pre class="screen">
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="macro"></a>8. Keyboard macros</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">macro</code>
-<em class="replaceable"><code>menu</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>sequence</code></em>
- [
-<em class="replaceable"><code>description</code></em>
-]</p></div><p>
-Macros are useful when you would like a single key to perform a series of
-actions. When you press <span class="emphasis"><em>key</em></span> in menu <span class="emphasis"><em>menu</em></span>, Mutt will behave as if
-you had typed <span class="emphasis"><em>sequence</em></span>. So if you have a common sequence of commands
-you type, you can create a macro to execute those commands with a single
-key or fewer keys.
-</p><p>
-<span class="emphasis"><em>menu</em></span> is the <a class="link" href="configuration.html#maps">map</a> which the macro will be bound in.
-Multiple maps may be specified by separating multiple menu arguments by
-commas. Whitespace may not be used in between the menu arguments and the
-commas separating them.
-</p><p>
-<span class="emphasis"><em>key</em></span> and <span class="emphasis"><em>sequence</em></span> are expanded by the same rules as the
-<a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">key bindings</a> with some additions. The
-first is that control characters in <span class="emphasis"><em>sequence</em></span> can also be specified
-as <span class="emphasis"><em>^x</em></span>. In order to get a caret (“<span class="quote">^</span>”) you need to use
-<span class="emphasis"><em>^^</em></span>. Secondly, to specify a certain key such as <span class="emphasis"><em>up</em></span>
-or to invoke a function directly, you can use the format
-<span class="emphasis"><em><key name></em></span> and <span class="emphasis"><em><function name></em></span>. For a listing of key
-names see the section on <a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">key bindings</a>. Functions
-are listed in the <a class="link" href="reference.html#functions" title="4. Functions">reference</a>.
-</p><p>
-The advantage with using function names directly is that the macros will
-work regardless of the current key bindings, so they are not dependent on
-the user having particular key definitions. This makes them more robust
-and portable, and also facilitates defining of macros in files used by more
-than one user (e.g., the system Muttrc).
-</p><p>
-Optionally you can specify a descriptive text after <span class="emphasis"><em>sequence</em></span>,
-which is shown in the help screens.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Macro definitions (if any) listed in the help screen(s), are
-silently truncated at the screen width, and are not wrapped.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="color"></a>9. Using color and mono video attributes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">color</code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">color</code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">color</code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">uncolor</code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-If your terminal supports color, you can spice up Mutt by creating your own
-color scheme. To define the color of an object (type of information), you
-must specify both a foreground color <span class="bold"><strong>and</strong></span> a background color (it is not
-possible to only specify one or the other).
-</p><p>
-<span class="emphasis"><em>header</em></span> and <span class="emphasis"><em>body</em></span> match <span class="emphasis"><em>regexp</em></span>
-in the header/body of a message, <span class="emphasis"><em>index</em></span> matches <span class="emphasis"><em>pattern</em></span>
-(see <a class="xref" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">Section 2, “Patterns: Searching, Limiting and Tagging”</a>) in the message index.
-</p><p>
-<span class="emphasis"><em>object</em></span> can be one of:
-</p><div class="itemizedlist"><ul type="disc"><li><p>attachment</p></li><li><p>bold (hiliting bold patterns in the body of messages)</p></li><li><p>error (error messages printed by Mutt)</p></li><li><p>hdrdefault (default color of the message header in the pager)</p></li><li><p>indicator (arrow or bar used to indicate the current item in a menu)</p></li><li><p>markers (the “<span class="quote">+</span>” markers at the beginning of wrapped lines in the pager)</p></li><li><p>message (informational messages)</p></li><li><p>normal</p></li><li><p>quoted (text matching <a class="link" href="reference.html#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a> in the body of a message)</p></li><li><p>quoted1, quoted2, ..., quoted<span class="bold"><strong>N</strong></span> (higher levels of quoting)</p></li><li><p>search (hiliting of words in the pager)</p></li><li><p>signature</p></li><li><p>status (mode lines used to display info about the mailbox or message)</p></li><li><p>tilde (the “<span class="quote">˜</span>” used to pad blank lines in the pager)</p></li><li><p>tree (thread tree drawn in the message index and attachment menu)</p></li><li><p>underline (hiliting underlined patterns in the body of messages)</p></li></ul></div><p>
-<span class="emphasis"><em>foreground</em></span> and <span class="emphasis"><em>background</em></span> can be one of the following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>white</p></li><li><p>black</p></li><li><p>green</p></li><li><p>magenta</p></li><li><p>blue</p></li><li><p>cyan</p></li><li><p>yellow</p></li><li><p>red</p></li><li><p>default</p></li><li><p>color<span class="emphasis"><em>x</em></span></p></li></ul></div><p>
-<span class="emphasis"><em>foreground</em></span> can optionally be prefixed with the keyword <code class="literal">bright</code> to make
-the foreground color boldfaced (e.g., <code class="literal">brightred</code>).
-</p><p>
-If your terminal supports it, the special keyword <span class="emphasis"><em>default</em></span> can be
-used as a transparent color. The value <span class="emphasis"><em>brightdefault</em></span> is also valid.
-If Mutt is linked against the <span class="emphasis"><em>S-Lang</em></span> library, you also need to set
-the <span class="emphasis"><em>COLORFGBG</em></span> environment variable to the default colors of your
-terminal for this to work; for example (for Bourne-like shells):
-</p><pre class="screen">
-set COLORFGBG="green;black"
-export COLORFGBG
-</pre><div class="note"><h3 class="title">Note</h3><p>
-The <span class="emphasis"><em>S-Lang</em></span> library requires you to use the <span class="emphasis"><em>lightgray</em></span>
-and <span class="emphasis"><em>brown</em></span> keywords instead of <span class="emphasis"><em>white</em></span> and <span class="emphasis"><em>yellow</em></span> when
-setting this variable.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-The uncolor command can be applied to the index object only. It
-removes entries from the list. You <span class="bold"><strong>must</strong></span> specify the same pattern
-specified in the color command for it to be removed. The pattern “<span class="quote">*</span>” is
-a special token which means to clear the color index list of all entries.
-</p></div><p>
-Mutt also recognizes the keywords <span class="emphasis"><em>color0</em></span>, <span class="emphasis"><em>color1</em></span>, …,
-<span class="emphasis"><em>color</em></span><span class="bold"><strong>N-1</strong></span> (<span class="bold"><strong>N</strong></span> 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 <span class="emphasis"><em>color2</em></span>
-for your xterm), since color names may then lose their normal meaning.
-</p><p>
-If your terminal does not support color, it is still possible change the video
-attributes through the use of the “<span class="quote">mono</span>” command:
-</p><a id="mono"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mono</code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>attribute</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">mono</code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">mono</code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unmono</code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-For <span class="emphasis"><em>object</em></span>, see the color command. <span class="emphasis"><em>attribute</em></span>
-can be one of the following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>none</p></li><li><p>bold</p></li><li><p>underline</p></li><li><p>reverse</p></li><li><p>standout</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ignore"></a>10. Message header display</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">ignore</code>
-<em class="replaceable"><code>pattern</code></em>
- [
-<em class="replaceable"><code>pattern</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unignore</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-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 in the pager.
-</p><p>
-You do not need to specify the full header field name. For example,
-“<span class="quote">ignore content-</span>” will ignore all header fields that begin with the pattern
-“<span class="quote">content-</span>”. “<span class="quote">ignore *</span>” will ignore all headers.
-</p><p>
-To remove a previously added token from the list, use the “<span class="quote">unignore</span>” command.
-The “<span class="quote">unignore</span>” command will make Mutt display headers with the given pattern.
-For example, if you do “<span class="quote">ignore x-</span>” it is possible to “<span class="quote">unignore x-mailer</span>”.
-</p><p>
-“<span class="quote">unignore *</span>” will remove all tokens from the ignore list.
-</p><p>
-For example:
-</p><div class="example"><a id="ex-header-weeding"></a><p class="title"><b>Example 3.8. Header weeding</b></p><div class="example-contents"><pre class="screen">
-# 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:
-</pre></div></div><br class="example-break" /><a id="hdr-order"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">hdr_order</code>
-<em class="replaceable"><code>header</code></em>
- [
-<em class="replaceable"><code>header</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unhdr_order</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>header</code></em>
-... }</p></div><p>
-With the <code class="literal">hdr_order</code> command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
-</p><p>
-“<span class="quote">unhdr_order *</span>” will clear all previous headers from the order list,
-thus removing the header order effects set by the system-wide startup file.
-</p><div class="example"><a id="ex-hdr-order"></a><p class="title"><b>Example 3.9. Configuring header display order</b></p><div class="example-contents"><pre class="screen">
-hdr_order From Date: From: To: Cc: Subject:
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternates"></a>11. Alternative addresses</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alternates</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unalternates</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><p>
-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 <a class="link" href="reference.html#reply-to" title="3.245. reply_to">$reply_to</a>.)
-</p><p>
-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 <code class="literal">alternates</code> command: It takes a list of regular
-expressions, each of which can identify an address under which you
-receive e-mail.
-</p><p>
-As addresses are matched using regular expressions and not exact strict
-comparisons, you should make sure you specify your addresses as precise
-as possible to avoid mismatches. For example, if you specify:
-</p><pre class="screen">
-alternates user@example
-</pre><p>
-mutt will consider “<span class="quote"><code class="literal">some-user@example</code></span>” as
-being your address, too which may not be desired. As a solution, in such
-cases addresses should be specified as:
-</p><pre class="screen">
-alternates '^user@example$'
-</pre><p>
-The <code class="literal">-group</code> flag causes all of the subsequent regular expressions
-to be added to the named group.
-</p><p>
-The <code class="literal">unalternates</code> command can be used to write exceptions to
-<code class="literal">alternates</code> patterns. If an address matches something in an
-<code class="literal">alternates</code> command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an <code class="literal">unalternates</code>
-command.
-</p><p>
-To remove a regular expression from the <code class="literal">alternates</code> list, use the
-<code class="literal">unalternates</code> command with exactly the same <span class="emphasis"><em>regexp</em></span>.
-Likewise, if the <span class="emphasis"><em>regexp</em></span> for an <code class="literal">alternates</code> command matches
-an entry on the <code class="literal">unalternates</code> list, that <code class="literal">unalternates</code>
-entry will be removed. If the <span class="emphasis"><em>regexp</em></span> for <code class="literal">unalternates</code>
-is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries</em></span> on <code class="literal">alternates</code> will be removed.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="lists"></a>12. Mailing lists</h2></div></div></div><a id="subscribe"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">lists</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unlists</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><div class="cmdsynopsis"><p><code class="command">subscribe</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unsubscribe</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><p>
-Mutt has a few nice features for <a class="link" href="advancedusage.html#using-lists" title="8. Handling Mailing Lists">handling mailing lists</a>. 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 <a class="link" href="gettingstarted.html#list-reply"><code class="literal"><list-reply></code></a> 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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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
-<a class="link" href="reference.html#followup-to" title="3.60. followup_to">$followup_to</a>
-configuration variable.
-</p></div><p>
-More precisely, Mutt 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 “<span class="quote">lists</span>”
-command. To mark it as subscribed, use “<span class="quote">subscribe</span>”.
-</p><p>
-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
-“<span class="quote">subscribe [0-9]*@bugs.guug.de</span>”. Often, it's sufficient to just
-give a portion of the list's e-mail address.
-</p><p>
-Specify as much of the address as you need to to remove ambiguity. For
-example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed to <span class="emphasis"><em>mutt-users@mutt.org</em></span>. So, to tell Mutt
-that this is a mailing list, you could add “<span class="quote">lists mutt-users@</span>” to your
-initialization file. To tell mutt that you are subscribed to it,
-add “<span class="quote">subscribe mutt-users</span>” to your initialization file instead.
-If you also happen to get mail from someone whose address is
-<span class="emphasis"><em>mutt-users@example.com</em></span>, you could use
-“<span class="quote">lists ^mutt-users@mutt\\.org$</span>”
-or “<span class="quote">subscribe ^mutt-users@mutt\\.org$</span>” to
-match only mail from the actual list.
-</p><p>
-The <code class="literal">-group</code> flag adds all of the subsequent regular expressions
-to the named group.
-</p><p>
-The “<span class="quote">unlists</span>” command is used to remove a token from the list of
-known and subscribed mailing-lists. Use “<span class="quote">unlists *</span>” to remove all
-tokens.
-</p><p>
-To remove a mailing list from the list of subscribed mailing lists,
-but keep it on the list of known mailing lists, use “<span class="quote">unsubscribe</span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mbox-hook"></a>13. Using Multiple spool mailboxes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mbox-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to move read messages from a specified mailbox to a
-different mailbox automatically when you quit or change folders.
-<span class="emphasis"><em>pattern</em></span> is a regular expression specifying the mailbox to treat as a
-“<span class="quote">spool</span>” mailbox and <span class="emphasis"><em>mailbox</em></span> specifies where mail should be saved when
-read.
-</p><p>
-Unlike some of the other <span class="emphasis"><em>hook</em></span> commands, only the <span class="emphasis"><em>first</em></span> matching
-pattern is used (it is not possible to save read mail in more than a single
-mailbox).
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailboxes"></a>14. Monitoring incoming mail</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mailboxes</code>
-<em class="replaceable"><code>mailbox</code></em>
- [
-<em class="replaceable"><code>mailbox</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unmailboxes</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mailbox</code></em>
-... }</p></div><p>
-This command specifies folders which can receive mail and
-which will be checked for new messages periodically.
-</p><p>
-<span class="emphasis"><em>folder</em></span> can either be a local file or directory
-(Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP
-support, <span class="emphasis"><em>folder</em></span> can also be a POP/IMAP folder
-URL. The URL syntax is described in <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>,
-POP and IMAP are described in <a class="xref" href="optionalfeatures.html#pop" title="3. POP3 Support">Section 3, “POP3 Support”</a> and <a class="xref" href="optionalfeatures.html#imap" title="4. IMAP Support">Section 4, “IMAP Support”</a>
-respectively.
-</p><p>
-Mutt provides a number of advanced features for handling (possibly many)
-folders and new mail within them, please refer to
-<a class="xref" href="advancedusage.html#handling-folders" title="9. Handling multiple folders">Section 9, “Handling multiple folders”</a> for details (including in what
-situations and how often Mutt checks for new mail).
-</p><p>
-The “<span class="quote">unmailboxes</span>” command is used to remove a token from the list
-of folders which receive mail. Use “<span class="quote">unmailboxes *</span>” to remove all
-tokens.
-</p><div class="note"><h3 class="title">Note</h3><p>
-The folders in the <code class="literal">mailboxes</code> command are resolved when
-the command is executed, so if these names contain <a class="link" href="advancedusage.html#shortcuts" title="7. Mailbox Shortcuts">shortcut characters</a> (such as “<span class="quote">=</span>” and “<span class="quote">!</span>”), any variable
-definition that affects these characters (like <a class="link" href="reference.html#folder" title="3.58. folder">$folder</a> and <a class="link" href="reference.html#spoolfile" title="3.279. spoolfile">$spoolfile</a>)
-should be set before the <code class="literal">mailboxes</code> command. If
-none of these shorcuts are used, a local path should be absolute as
-otherwise mutt tries to find it relative to the directory
-from where mutt was started which may not always be desired.
-</p></div><p>
-For Mbox and Mmdf folders, new mail is detected by comparing access and/or
-modification times of files: Mutt assumes a folder has new mail if it wasn't
-accessed after it was last modified. Utilities like <code class="literal">biff</code> or
-<code class="literal">frm</code> or any other program which accesses the mailbox might cause
-Mutt to never detect new mail for that mailbox if they do not properly reset the
-access time. Other possible causes of Mutt not detecting new mail in these folders
-are backup tools (updating access times) or filesystems mounted without
-access time update support.
-</p><p>
-In cases where new mail detection for Mbox or Mmdf folders appears to be
-unreliable, the
-<a class="link" href="reference.html#check-mbox-size" title="3.24. check_mbox_size">$check_mbox_size</a>
-option can be used to make Mutt track and consult file sizes for new
-mail detection instead.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="my-hdr"></a>15. User defined headers</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">my_hdr</code>
-<em class="replaceable"><code>string</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unmy_hdr</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>field</code></em>
-... }</p></div><p>
-The <code class="literal">my_hdr</code> command allows you to create your own header
-fields which will be added to every message you send.
-</p><p>
-For example, if you would like to add an “<span class="quote">Organization:</span>” header field to
-all of your outgoing messages, you can put the command
-</p><div class="example"><a id="ex-my-hdr"></a><p class="title"><b>Example 3.10. Defining custom headers</b></p><div class="example-contents"><pre class="screen">
-my_hdr Organization: A Really Big Company, Anytown, USA
-</pre></div></div><br class="example-break" /><p>
-in your <code class="literal">.muttrc</code>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Space characters are <span class="emphasis"><em>not</em></span> allowed between the keyword and
-the colon (“<span class="quote">:</span>”). The standard for electronic mail (RFC2822) says that
-space is illegal there, so Mutt enforces the rule.
-</p></div><p>
-If you would like to add a header field to a single message, you should
-either set the <a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable,
-or use the <code class="literal"><edit-headers></code> function (default: “<span class="quote">E</span>”) in the compose menu so
-that you can edit the header of your message along with the body.
-</p><p>
-To remove user defined header fields, use the <code class="literal">unmy_hdr</code>
-command. You may specify an asterisk (“<span class="quote">*</span>”) to remove all header
-fields, or the fields to remove. For example, to remove all “<span class="quote">To</span>” and
-“<span class="quote">Cc</span>” header fields, you could use:
-</p><pre class="screen">
-unmy_hdr to cc
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="save-hook"></a>16. Specify default save mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">save-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to override the default mailbox used when saving
-messages. <span class="emphasis"><em>mailbox</em></span> will be used as the default if the message
-matches <span class="emphasis"><em>pattern</em></span>, see <a class="xref" href="advancedusage.html#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information
-on the exact format.
-</p><p>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> to
-<span class="emphasis"><em>mailbox</em></span> after it was expanded.
-</p><p>
-Examples:
-</p><div class="example"><a id="ex-save-hook-exando"></a><p class="title"><b>Example 3.11. Using %-expandos in <code class="literal">save-hook</code></b></p><div class="example-contents"><pre class="screen">
-# default: save all to ~/Mail/<author name>
-save-hook . ~/Mail/%F
-
-# save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
-save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
-# save from aol.com to $folder/spam
-save-hook aol\\.com$ +spam
-</pre></div></div><br class="example-break" /><p>
-Also see the <a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-hook"></a>17. Specify default Fcc: mailbox when composing</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to save outgoing mail in a mailbox other than
-<a class="link" href="reference.html#record" title="3.242. record">$record</a>. Mutt searches the initial list of
-message recipients for the first matching <span class="emphasis"><em>regexp</em></span> and uses <span class="emphasis"><em>mailbox</em></span>
-as the default Fcc: mailbox. If no match is found the message will be saved
-to <a class="link" href="reference.html#record" title="3.242. record">$record</a> mailbox.
-</p><p>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> to
-<span class="emphasis"><em>mailbox</em></span> after it was expanded.
-</p><p>
-See <a class="xref" href="advancedusage.html#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information on the exact format of <span class="emphasis"><em>pattern</em></span>.
-</p><p>
-Example: <code class="literal">fcc-hook [@.]aol\\.com$ +spammers</code>
-</p><p>
-The above will save a copy of all messages going to the aol.com domain to
-the `+spammers' mailbox by default. Also see the <a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-save-hook"></a>18. Specify default save filename and default Fcc: mailbox at once</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-save-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is a shortcut, equivalent to doing both a <a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
-and a <a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a> with its arguments,
-including %-expansion on <span class="emphasis"><em>mailbox</em></span> according
-to <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="send-hook"></a>19. Change settings based upon message recipients</h2></div></div></div><a id="reply-hook"></a><a id="send2-hook"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">reply-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">send-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">send2-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-These commands can be used to execute arbitrary configuration commands based
-upon recipients of the message. <span class="emphasis"><em>pattern</em></span> is used to match
-the message, see <a class="xref" href="advancedusage.html#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for details. <span class="emphasis"><em>command</em></span>
-is executed when <span class="emphasis"><em>pattern</em></span> matches.
-</p><p>
-<code class="literal">reply-hook</code> is matched against the message you are <span class="emphasis"><em>replying to</em></span>,
-instead of the message you are <span class="emphasis"><em>sending</em></span>. <code class="literal">send-hook</code> is
-matched against all messages, both <span class="emphasis"><em>new</em></span>
-and <span class="emphasis"><em>replies</em></span>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-<code class="literal">reply-hook</code>s are matched <span class="bold"><strong>before</strong></span> the <code class="literal">send-hook</code>, <span class="bold"><strong>regardless</strong></span>
-of the order specified in the user's configuration file.
-</p></div><p>
-<code class="literal">send2-hook</code> is matched every time a message is changed, either
-by editing it, or by using the compose menu to change its recipients
-or subject. <code class="literal">send2-hook</code> is executed after <code class="literal">send-hook</code>, and
-can, e.g., be used to set parameters such as the <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a> variable depending on the message's sender
-address.
-</p><p>
-For each type of <code class="literal">send-hook</code> or <code class="literal">reply-hook</code>, when multiple matches
-occur, commands are executed in the order they are specified in the muttrc
-(for that type of hook).
-</p><p>
-Example: <code class="literal">send-hook mutt "set mime_forward signature=''"</code>
-</p><p>
-Another typical use for this command is to change the values of the
-<a class="link" href="reference.html#attribution" title="3.16. attribution">$attribution</a>, <a class="link" href="reference.html#signature" title="3.265. signature">$signature</a> and <a class="link" href="reference.html#locale" title="3.104. locale">$locale</a>
-variables in order to change the language of the attributions and
-signatures based upon the recipients.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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
-<code class="literal">my_hdr</code> 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.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="message-hook"></a>20. Change settings before formatting a message</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">message-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-This command can be used to execute arbitrary configuration commands
-before viewing or formatting a message based upon information about the message.
-<span class="emphasis"><em>command</em></span> is executed if the <span class="emphasis"><em>pattern</em></span> matches the message to be
-displayed. When multiple matches occur, commands are executed in the order
-they are specified in the muttrc.
-</p><p>
-See <a class="xref" href="advancedusage.html#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for
-information on the exact format of <span class="emphasis"><em>pattern</em></span>.
-</p><p>
-Example:
-</p><pre class="screen">
-message-hook ~A 'set pager=builtin'
-message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="crypt-hook"></a>21. Choosing the cryptographic key of the recipient</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">crypt-hook</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>keyid</code></em>
- </p></div><p>
-When encrypting messages with PGP/GnuPG 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 would
-normally use. The <code class="literal">crypt-hook</code> 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.
-</p><p>
-The meaning of <span class="emphasis"><em>keyid</em></span> 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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="push"></a>22. Adding key sequences to the keyboard buffer</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">push</code>
-<em class="replaceable"><code>string</code></em>
- </p></div><p>
-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 <a class="link" href="configuration.html#macro" title="8. Keyboard macros">macro</a> 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:
-</p><div class="example"><a id="ex-folder-hook-push"></a><p class="title"><b>Example 3.12. Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></b></p><div class="example-contents"><pre class="screen">
-folder-hook . 'push <collapse-all>'
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exec"></a>23. Executing functions</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">exec</code>
-<em class="replaceable"><code>function</code></em>
- [
-<em class="replaceable"><code>function</code></em>
-...]</p></div><p>
-This command can be used to execute any function. Functions are
-listed in the <a class="link" href="reference.html#functions" title="4. Functions">function reference</a>.
-“<span class="quote">exec function</span>” is equivalent to “<span class="quote">push <function></span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="score-command"></a>24. Message Scoring</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">score</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>value</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unscore</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-The <code class="literal">score</code> commands adds <span class="emphasis"><em>value</em></span> to a message's score if <span class="emphasis"><em>pattern</em></span>
-matches it. <span class="emphasis"><em>pattern</em></span> is a string in the format described in the <a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> section (note: For efficiency reasons, patterns
-which scan information not available in the index, such as <code class="literal">˜b</code>,
-<code class="literal">˜B</code> or <code class="literal">˜h</code>, may not be used). <span class="emphasis"><em>value</em></span> is a
-positive or negative integer. A message's final score is the sum total of all
-matching <code class="literal">score</code> entries. However, you may optionally prefix <span class="emphasis"><em>value</em></span> with
-an equal sign (=) to cause evaluation to stop at a particular entry if there is
-a match. Negative final scores are rounded up to 0.
-</p><p>
-The <code class="literal">unscore</code> command removes score entries from the list. You <span class="bold"><strong>must</strong></span>
-specify the same pattern specified in the <code class="literal">score</code> command for it to be
-removed. The pattern “<span class="quote">*</span>” is a special token which means to clear the list
-of all score entries.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="spam"></a>25. Spam detection</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">spam</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>format</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">nospam</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
- }</p></div><p>
-Mutt has generalized support for external spam-scoring filters.
-By defining your spam patterns with the <code class="literal">spam</code> and <code class="literal">nospam</code>
-commands, you can <span class="emphasis"><em>limit</em></span>, <span class="emphasis"><em>search</em></span>, and <span class="emphasis"><em>sort</em></span> 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 <code class="literal">%H</code> selector in the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable. (Tip: try <code class="literal">%?H?[%H] ?</code>
-to display spam tags only when they are defined for a given message.)
-</p><p>
-Your first step is to define your external filter's spam patterns using
-the <code class="literal">spam</code> command. <span class="emphasis"><em>pattern</em></span> 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 “<span class="quote">spam tag</span>” or
-“<span class="quote">spam attribute</span>” (unless it also matches a <code class="literal">nospam</code> pattern -- see
-below.) The appearance of this attribute is entirely up to you, and is
-governed by the <span class="emphasis"><em>format</em></span> parameter. <span class="emphasis"><em>format</em></span> can be any static
-text, but it also can include back-references from the <span class="emphasis"><em>pattern</em></span>
-expression. (A regular expression “<span class="quote">back-reference</span>” refers to a
-sub-expression contained within parentheses.) <code class="literal">%1</code> is replaced with
-the first back-reference in the regex, <code class="literal">%2</code> with the second, etc.
-</p><p>
-If you're using multiple spam filters, a message can have more than
-one spam-related header. You can define <code class="literal">spam</code> 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 <span class="emphasis"><em>format</em></span> strings joined
-together, with the value of $spam_separator separating
-them.
-</p><p>
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-define these spam settings:
-</p><div class="example"><a id="ex-spam"></a><p class="title"><b>Example 3.13. Configuring spam detection</b></p><div class="example-contents"><pre class="screen">
-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=", "
-</pre></div></div><br class="example-break" /><p>
-If I then received a message that DCC registered with “<span class="quote">many</span>” hits
-under the “<span class="quote">Fuz2</span>” checksum, and that PureMessage registered with a
-97% probability of being spam, that message's spam tag would read
-<code class="literal">90+/DCC-Fuz2, 97/PM</code>. (The four characters before “<span class="quote">=many</span>” in a
-DCC report indicate the checksum used -- in this case, “<span class="quote">Fuz2</span>”.)
-</p><p>
-If the $spam_separator variable is unset, then each
-spam pattern match supersedes the previous one. Instead of getting
-joined <span class="emphasis"><em>format</em></span> strings, you'll get only the last one to match.
-</p><p>
-The spam tag is what will be displayed in the index when you use
-<code class="literal">%H</code> in the <code class="literal">$index_format</code> variable. It's also the
-string that the <code class="literal">˜H</code> pattern-matching expression matches against for
-<code class="literal"><search></code> and <code class="literal"><limit></code> functions. And it's what sorting by spam
-attribute will use as a sort key.
-</p><p>
-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.
-</p><p>
-Generally, when you sort by spam tag, mutt will sort <span class="emphasis"><em>lexically</em></span> --
-that is, by ordering strings alphanumerically. 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
-<code class="literal">sort -n</code>.) A message with no spam attributes at all -- that is, one
-that didn't match <span class="emphasis"><em>any</em></span> of your <code class="literal">spam</code> patterns -- is sorted at
-lowest priority. Numbers are sorted next, beginning with 0 and ranging
-upward. Finally, non-numeric strings are sorted, with “<span class="quote">a</span>” taking lower
-priority than “<span class="quote">z</span>”. 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.
-</p><p>
-The <code class="literal">nospam</code> command can be used to write exceptions to <code class="literal">spam</code>
-patterns. If a header pattern matches something in a <code class="literal">spam</code> command,
-but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a <code class="literal">nospam</code> command.
-</p><p>
-If the <span class="emphasis"><em>pattern</em></span> given to <code class="literal">nospam</code> is exactly the same as the
-<span class="emphasis"><em>pattern</em></span> on an existing <code class="literal">spam</code> list entry, the effect will be to
-remove the entry from the spam list, instead of adding an exception.
-Likewise, if the <span class="emphasis"><em>pattern</em></span> for a <code class="literal">spam</code> command matches an entry
-on the <code class="literal">nospam</code> list, that <code class="literal">nospam</code> entry will be removed. If the
-<span class="emphasis"><em>pattern</em></span> for <code class="literal">nospam</code> is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries on both lists</em></span>
-will be removed. This might be the default action if you use <code class="literal">spam</code>
-and <code class="literal">nospam</code> in conjunction with a <code class="literal">folder-hook</code>.
-</p><p>
-You can have as many <code class="literal">spam</code> or <code class="literal">nospam</code> commands as you like.
-You can even do your own primitive spam detection within mutt -- for
-example, if you consider all mail from <code class="literal">MAILER-DAEMON</code> to be spam,
-you can use a <code class="literal">spam</code> command like this:
-</p><pre class="screen">
-spam "^From: .*MAILER-DAEMON" "999"
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="set"></a>26. Setting and Querying Variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-commands"></a>26.1. Commands</h3></div></div></div><p>
-The following commands are available to manipulate and query variables:
-</p><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">set</code> {
-[ <code class="option">no</code> | <code class="option">inv</code> ]
-<em class="replaceable"><code>variable</code></em>
- |
-<em class="replaceable"><code>variable=value</code></em>
- } [...]</p></div><div class="cmdsynopsis"><p><code class="command">toggle</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unset</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">reset</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><p>
-This command is used to set (and unset) <a class="link" href="reference.html#variables" title="3. Configuration variables">configuration variables</a>. There are four basic types of variables:
-boolean, number, string and quadoption. <span class="emphasis"><em>boolean</em></span> variables can be
-<span class="emphasis"><em>set</em></span> (true) or <span class="emphasis"><em>unset</em></span> (false). <span class="emphasis"><em>number</em></span> variables can be
-assigned a positive integer value.
-<span class="emphasis"><em>string</em></span> variables consist of any number of printable characters and
-must be enclosed in quotes if they contain spaces or tabs. You
-may also use the escape sequences “<span class="quote">\n</span>” and “<span class="quote">\t</span>” for newline and tab, respectively.
-<span class="emphasis"><em>quadoption</em></span> variables are used to control whether or not to be prompted
-for certain actions, or to specify a default action. A value of <span class="emphasis"><em>yes</em></span>
-will cause the action to be carried out automatically as if you had answered
-yes to the question. Similarly, a value of <span class="emphasis"><em>no</em></span> will cause the
-action to be carried out as if you had answered “<span class="quote">no.</span>” A value of
-<span class="emphasis"><em>ask-yes</em></span> will cause a prompt with a default answer of “<span class="quote">yes</span>” and
-<span class="emphasis"><em>ask-no</em></span> will provide a default answer of “<span class="quote">no.</span>”
-</p><p>
-Prefixing a variable with “<span class="quote">no</span>” will unset it. Example: <code class="literal">set noaskbcc</code>.
-</p><p>
-For <span class="emphasis"><em>boolean</em></span> variables, you may optionally prefix the variable name with
-<code class="literal">inv</code> to toggle the value (on or off). This is useful when writing
-macros. Example: <code class="literal">set invsmart_wrap</code>.
-</p><p>
-The <code class="literal">toggle</code> command automatically prepends the <code class="literal">inv</code> prefix to all
-specified variables.
-</p><p>
-The <code class="literal">unset</code> command automatically prepends the <code class="literal">no</code> prefix to all
-specified variables.
-</p><p>
-Using the <code class="literal"><enter-command></code> function in the <span class="emphasis"><em>index</em></span> menu, you can query the
-value of a variable by prefixing the name of the variable with a question
-mark:
-</p><pre class="screen">
-set ?allow_8bit
-</pre><p>
-The question mark is actually only required for boolean and quadoption
-variables.
-</p><p>
-The <code class="literal">reset</code> command resets all given variables to the compile time
-defaults (hopefully mentioned in this manual). If you use the command
-<code class="literal">set</code> and prefix the variable with “<span class="quote">&</span>” this has the same
-behavior as the reset command.
-</p><p>
-With the <code class="literal">reset</code> command there exists the special variable “<span class="quote">all</span>”,
-which allows you to reset all variables to their system defaults.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-myvar"></a>26.2. User-defined variables</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-intro"></a>26.2.1. Introduction</h4></div></div></div><p>
-Along with the variables listed in the
-<a class="link" href="reference.html#variables" title="3. Configuration variables">Configuration variables</a> section, mutt
-supports user-defined variables with names starting
-with <code class="literal">my_</code> as in, for
-example, <code class="literal">my_cfgdir</code>.
-</p><p>
-The <code class="literal">set</code> command either creates a
-custom <code class="literal">my_</code> variable or changes its
-value if it does exist already. The <code class="literal">unset</code> and <code class="literal">reset</code>
-commands remove the variable entirely.
-</p><p>
-Since user-defined variables are expanded in the same way that
-environment variables are (except for
-the <a class="link" href="gettingstarted.html#shell-escape">shell-escape</a> command and
-backtick expansion), this feature can be used to make configuration
-files more readable.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-examples"></a>26.2.2. Examples</h4></div></div></div><p>
-The following example defines and uses the variable <code class="literal">my_cfgdir</code>
-to abbreviate the calls of the <a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a> command:
-</p><div class="example"><a id="ex-myvar1"></a><p class="title"><b>Example 3.14. Using user-defined variables for config file readability</b></p><div class="example-contents"><pre class="screen">
-set my_cfgdir = $HOME/mutt/config
-
-source $my_cfgdir/hooks
-source $my_cfgdir/macros
-# more source commands...
-</pre></div></div><br class="example-break" /><p>
-A custom variable can also be used in macros to backup the current value
-of another variable. In the following example, the value of the
-<a class="link" href="reference.html#delete" title="3.42. delete">$delete</a> is changed temporarily
-while its original value is saved as <code class="literal">my_delete</code>.
-After the macro has executed all commands, the original value of <a class="link" href="reference.html#delete" title="3.42. delete">$delete</a> is restored.
-</p><div class="example"><a id="ex-myvar2"></a><p class="title"><b>Example 3.15. Using user-defined variables for backing up other config option values</b></p><div class="example-contents"><pre class="screen">
-macro pager ,x '\
-<enter-command>set my_delete=$delete<enter>\
-<enter-command>set delete=yes<enter>\
-...\
-<enter-command>set delete=$my_delete<enter>'
-</pre></div></div><br class="example-break" /><p>
-Since mutt expands such values already when parsing the configuration
-file(s), the value of <code class="literal">$my_delete</code> in the
-last example would be the value of <code class="literal">$delete</code> exactly
-as it was at that point during parsing the configuration file. If
-another statement would change the value for <code class="literal">$delete</code>
-later in the same or another file, it would have no effect on
-<code class="literal">$my_delete</code>. However, the expansion can
-be deferred to runtime, as shown in the next example, when escaping the
-dollar sign.
-</p><div class="example"><a id="ex-myvar3"></a><p class="title"><b>Example 3.16. Deferring user-defined variable expansion to runtime</b></p><div class="example-contents"><pre class="screen">
-macro pager <PageDown> "\
-<enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
-<next-page>\
-<enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
-<enter-command> unset my_old_pager_stop<Enter>"
-</pre></div></div><br class="example-break" /><p>
-Note that there is a space
-between <code class="literal"><enter-command></code> and
-the <code class="literal">set</code> configuration command, preventing mutt from
-recording the macro's commands into its history.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="source"></a>27. Reading initialization commands from another file</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">source</code>
-<em class="replaceable"><code>filename</code></em>
- </p></div><p>
-This command allows the inclusion of initialization commands
-from other files. For example, I place all of my aliases in
-<code class="literal">˜/.mail_aliases</code> so that I can make my
-<code class="literal">˜/.muttrc</code> readable and keep my aliases private.
-</p><p>
-If the filename begins with a tilde (“<span class="quote">˜</span>”), it will be expanded to the
-path of your home directory.
-</p><p>
-If the filename ends with a vertical bar (|), then <span class="emphasis"><em>filename</em></span> is
-considered to be an executable program from which to read input (eg.
-<code class="literal">source ˜/bin/myscript|</code>).
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ifdef"></a>28. Configuring features conditionnaly</h2></div></div></div><p>
-Usage: <code class="literal">ifdef</code> <span class="emphasis"><em>item</em></span> <span class="emphasis"><em>command</em></span>
-</p><p>
-This command allows to test if a feature has been compiled in, before
-actually executing the command. Item can be either the name of a
-function, variable, or command. Example:
-</p><p>
-</p><pre class="screen">
-ifdef imap_keepalive 'source ~/.mutt/imap_setup'
-</pre><p>
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="unhook"></a>29. Removing hooks</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">unhook</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>hook-type</code></em>
- }</p></div><p>
-This command permits you to flush hooks you have previously defined.
-You can either remove all hooks by giving the “<span class="quote">*</span>” character as an
-argument, or you can remove all hooks of a specific type by saying
-something like <code class="literal">unhook send-hook</code>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="formatstrings"></a>30. Format Strings</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-basics"></a>30.1. Basic usage</h3></div></div></div><p>
-Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
-<a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>,
-<a class="link" href="reference.html#pager-format" title="3.140. pager_format">$pager_format</a>,
-<a class="link" href="reference.html#status-format" title="3.281. status_format">$status_format</a>,
-and other “<span class="quote">*_format</span>” variables. These can be very straightforward,
-and it's quite possible you already know how to use them.
-</p><p>
-The most basic format string element is a percent symbol followed
-by another character. For example, <code class="literal">%s</code>
-represents a message's Subject: header in the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable. The
-“<span class="quote">expandos</span>” available are documented with each format variable, but
-there are general modifiers available with all formatting expandos,
-too. Those are our concern here.
-</p><p>
-Some of the modifiers are borrowed right out of C (though you might
-know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in <code class="literal">%-12.12s</code>. As with
-such programming languages, these modifiers allow you to specify the
-minimum and maximum size of the resulting string, as well as its
-justification. If the “<span class="quote">-</span>” sign follows the percent, the string will
-be left-justified instead of right-justified. If there's a number
-immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
-will be padded out with spaces. If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
-permitted to exceed that width, no matter its natural size. Each of
-these three elements is optional, so that all these are legal format
-strings:
-<code class="literal">%-12s</code>
-<code class="literal">%4c</code>
-<code class="literal">%.15F</code>
-<code class="literal">%-12.15L</code>
-</p><p>
-Mutt adds some other modifiers to format strings. If you use an equals
-symbol (<code class="literal">=</code>) as a numeric prefix (like the minus
-above), it will force the string to be centered within its minimum
-space range. For example, <code class="literal">%=14y</code> will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-<code class="literal">$index_format</code>. If the expansion
-results in a string less than 14 characters, it will be centered in a
-14-character space. If the X-Label for a message were "test", that
-expansion would look like “<span class="quote"> test </span>”.
-</p><p>
-There are two very little-known modifiers that affect the way that an
-expando is replaced. If there is an underline (“<span class="quote">_</span>”) character
-between any format modifiers (as above) and the expando letter, it will
-expands in all lower case. And if you use a colon (“<span class="quote">:</span>”), it will
-replace all decimal points with underlines.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-filters"></a>30.2. Filters</h3></div></div></div><p>
-Any format string ending in a vertical bar (“<span class="quote">|</span>”) will be
-expanded and piped through the first word in the string, using spaces
-as separator. The string returned will be used for display.
-If the returned string ends in %, it will be passed through
-the formatter a second time. This allows the filter to generate a
-replacement format string including % expandos.
-</p><p>
-All % expandos in a format string are expanded before the script
-is called so that:
-</p><div class="example"><a id="ex-fmtpipe"></a><p class="title"><b>Example 3.17. Using external filters in format strings</b></p><div class="example-contents"><pre class="screen">
-set status_format="script.sh '%r %f (%L)'|"
-</pre></div></div><br class="example-break" /><p>
-will make mutt expand <code class="literal">%r</code>,
-<code class="literal">%f</code> and <code class="literal">%L</code>
-before calling the script. The example also shows that arguments can be
-quoted: the script will receive the expanded string between the single quotes
-as the only argument.
-</p><p>
-A practical example is the <code class="literal">mutt_xtitle</code>
-script installed in the <code class="literal">samples</code>
-subdirectory of the mutt documentation: it can be used as filter for
-<code class="literal">$status_format</code> to set the current
-terminal's title, if supported.
-</p></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gettingstarted.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="advancedusage.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Getting Started </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Advanced Usage</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Getting Started</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="intro.html" title="Chapter 1. Introduction" /><link rel="next" href="configuration.html" title="Chapter 3. Configuration" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Getting Started</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="intro.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="configuration.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="gettingstarted"></a>Chapter 2. Getting Started</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="gettingstarted.html#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#postponing-mail">7. Postponing Mail</a></span></dt></dl></div><p>
-This section is intended as a brief overview of how to use Mutt. There are
-many other features which are described elsewhere in the manual. There
-is even more information available in the Mutt FAQ and various web
-pages. See the <a class="ulink" href="http://www.mutt.org/" target="_top">Mutt homepage</a> for more details.
-</p><p>
-The keybindings described in this section are the defaults as distributed.
-Your local system administrator may have altered the defaults for your site.
-You can always type “<span class="quote">?</span>” in any menu to display the current bindings.
-</p><p>
-The first thing you need to do is invoke mutt, simply by typing <code class="literal">mutt</code>
-at the command line. There are various command-line options, see
-either the mutt man page or the <a class="link" href="reference.html#commandline" title="1. Command line options">reference</a>.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="core-concepts"></a>1. Core concepts</h2></div></div></div><p>
-Mutt is a text-based application which interacts with users through
-different menus which are mostly line-/entry-based or page-based. A
-line-based menu is the so-called “<span class="quote">index</span>” menu (listing all messages of
-the currently opened folder) or the “<span class="quote">alias</span>” menu (allowing you to
-select recipients from a list). Examples for page-based menus are the
-“<span class="quote">pager</span>” (showing one message at a time) or the “<span class="quote">help</span>” menu listing
-all available key bindings.
-</p><p>
-The user interface consists of a context sensitive help line at the top,
-the menu's contents followed by a context sensitive status line and
-finally the command line. The command line is used to display
-informational and error messages as well as for prompts and for entering
-interactive commands.
-</p><p>
-Because Mutt allows for customizing almost all key bindings, there are
-so-called “<span class="quote">functions</span>” which can be executed manually (using the
-command line) or in macros. Macros allow the user to bind a sequence of
-commands to a single key or a short key sequence instead of repeating a
-sequence of actions over and over.
-</p><p>
-Many commands (such as saving or copying a message to another folder)
-can be applied to a single message or a set of messages (so-called
-“<span class="quote">tagged</span>” messages). To help selecting messages, Mutt provides a rich
-set of message patterns (such as recipients, sender, body contents, date
-sent/received, etc.) which can be combined into complex expressions
-using the boolean <span class="emphasis"><em>and</em></span> and <span class="emphasis"><em>or</em></span>
-operations as well as negating. These patterns can also be used to (for
-example) search for messages or to limit the index to show only matching
-messages.
-</p><p>
-Mutt supports a “<span class="quote">hook</span>” concept which allows the user to execute
-arbitrary configuration commands and functions in certain situations
-such as entering a folder, starting a new message or replying to an
-existing one. These hooks can be used to highly customize Mutt's
-behaviour including managing multiple identities, customizing the
-display for a folder or even implementing auto-archiving based on a
-per-folder basis and much more.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="menus"></a>2. Moving Around in Menus</h2></div></div></div><p>
-The most important navigation keys common to all menus are shown in
-<a class="xref" href="gettingstarted.html#tab-keys-nav" title="Table 2.1. Most common navigation keys">Table 2.1, “Most common navigation keys”</a>.
-</p><div class="table"><a id="tab-keys-nav"></a><p class="title"><b>Table 2.1. Most common navigation keys</b></p><div class="table-contents"><table summary="Most common navigation keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>j or <Down></td><td><code class="literal"><next-entry></code></td><td>move to the next entry</td></tr><tr><td>k or <Up></td><td><code class="literal"><previous-entry></code></td><td>move to the previous entry</td></tr><tr><td>z or <PageDn></td><td><code class="literal"><page-down></code></td><td>go to the next page</td></tr><tr><td>Z or <PageUp></td><td><code class="literal"><page-up></code></td><td>go to the previous page</td></tr><tr><td>= or <Home></td><td><code class="literal"><first-entry></code></td><td>jump to the first entry</td></tr><tr><td>* or <End></td><td><code class="literal"><last-entry></code></td><td>jump to the last entry</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>exit the current menu</td></tr><tr><td>?</td><td><code class="literal"><help></code></td><td>list all keybindings for the current menu</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing"></a>3. Editing Input Fields</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-intro"></a>3.1. Introduction</h3></div></div></div><p>
-Mutt has a built-in line editor for inputting text, e.g. email
-addresses or filenames. The keys used to manipulate text input are
-very similar to those of Emacs. See <a class="xref" href="gettingstarted.html#tab-keys-editor" title="Table 2.2. Most common line editor keys">Table 2.2, “Most common line editor keys”</a> for a full
-reference of available functions, their default key bindings, and
-short descriptions.
-</p><div class="table"><a id="tab-keys-editor"></a><p class="title"><b>Table 2.2. Most common line editor keys</b></p><div class="table-contents"><table summary="Most common line editor keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^A or <Home></td><td><code class="literal"><bol></code></td><td>move to the start of the line</td></tr><tr><td>^B or <Left></td><td><code class="literal"><backward-char></code></td><td>move back one char</td></tr><tr><td>Esc B</td><td><code class="literal"><backward-word></code></td><td>move back one word</td></tr><tr><td>^D or <Delete></td><td><code class="literal"><delete-char></code></td><td>delete the char under the cursor</td></tr><tr><td>^E or <End></td><td><code class="literal"><eol></code></td><td>move to the end of the line</td></tr><tr><td>^F or <Right></td><td><code class="literal"><forward-char></code></td><td>move forward one char</td></tr><tr><td>Esc F</td><td><code class="literal"><forward-word></code></td><td>move forward one word</td></tr><tr><td><Tab></td><td><code class="literal"><complete></code></td><td>complete filename or alias</td></tr><tr><td>^T</td><td><code class="literal"><complete-query></code></td><td>complete address with query</td></tr><tr><td>^K</td><td><code class="literal"><kill-eol></code></td><td>delete to the end of the line</td></tr><tr><td>Esc d</td><td><code class="literal"><kill-eow></code></td><td>delete to the end of the word</td></tr><tr><td>^W</td><td><code class="literal"><kill-word></code></td><td>kill the word in front of the cursor</td></tr><tr><td>^U</td><td><code class="literal"><kill-line></code></td><td>delete entire line</td></tr><tr><td>^V</td><td><code class="literal"><quote-char></code></td><td>quote the next typed key</td></tr><tr><td><Up></td><td><code class="literal"><history-up></code></td><td>recall previous string from history</td></tr><tr><td><Down></td><td><code class="literal"><history-down></code></td><td>recall next string from history</td></tr><tr><td><BackSpace></td><td><code class="literal"><backspace></code></td><td>kill the char in front of the cursor</td></tr><tr><td>Esc u</td><td><code class="literal"><upcase-word></code></td><td>convert word to upper case</td></tr><tr><td>Esc l</td><td><code class="literal"><downcase-word></code></td><td>convert word to lower case</td></tr><tr><td>Esc c</td><td><code class="literal"><capitalize-word></code></td><td>capitalize the word</td></tr><tr><td>^G</td><td>n/a</td><td>abort</td></tr><tr><td><Return></td><td>n/a</td><td>finish editing</td></tr></tbody></table></div></div><br class="table-break" /><p>
-You can remap the <span class="emphasis"><em>editor</em></span> functions using the
-<a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">bind</a> command. For example, to make
-the <Delete> key delete the character in front of
-the cursor rather than under, you could use:
-</p><pre class="screen">
-bind editor <delete> backspace
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-history"></a>3.2. History</h3></div></div></div><p>
-Mutt maintains a history for the built-in editor. The number of items
-is controlled by the <a class="link" href="reference.html#history" title="3.77. history">$history</a>
-variable and can be made persistent using an external file specified
-using <a class="link" href="reference.html#history-file" title="3.78. history_file">$history_file</a>.
-You may cycle through them at an editor prompt by using the
-<code class="literal"><history-up></code> and/or
-<code class="literal"><history-down></code> commands.
-</p><p>
-Mutt maintains several distinct history lists, one for each of the
-following categories:
-</p><div class="itemizedlist"><ul type="disc"><li><p>muttrc commands</p></li><li><p>addresses and aliases</p></li><li><p>shell commands</p></li><li><p>filenames</p></li><li><p>patterns</p></li><li><p>everything else</p></li></ul></div><p>
-Mutt automatically filters out repeated items from the history. It
-also mimics the behavior of some shells by ignoring items starting
-with a space. The latter feature can be useful in macros to not clobber
-the history's valuable entries with unwanted entries.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="reading"></a>4. Reading Mail - The Index and Pager</h2></div></div></div><p>
-Similar to many other mail clients, there are two modes in which mail is
-read in Mutt. The first is the index of messages in the mailbox, which is
-called the “<span class="quote">index</span>” in Mutt. The second mode is the display of the
-message contents. This is called the “<span class="quote">pager.</span>”
-</p><p>
-The next few sections describe the functions provided in each of these
-modes.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-menu"></a>4.1. The Message Index</h3></div></div></div><p>
-Common keys used to navigate through and manage messages in the index
-are shown in <a class="xref" href="gettingstarted.html#tab-key-index" title="Table 2.3. Most common message index keys">Table 2.3, “Most common message index keys”</a>. How messages are presented
-in the index menu can be customized using the
-<a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable.
-</p><div class="table"><a id="tab-key-index"></a><p class="title"><b>Table 2.3. Most common message index keys</b></p><div class="table-contents"><table summary="Most common message index keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td>c</td><td>change to a different mailbox</td></tr><tr><td>Esc c</td><td>change to a folder in read-only mode</td></tr><tr><td>C</td><td>copy the current message to another mailbox</td></tr><tr><td>Esc C</td><td>decode a message and copy it to a folder</td></tr><tr><td>Esc s</td><td>decode a message and save it to a folder</td></tr><tr><td>D</td><td>delete messages matching a pattern</td></tr><tr><td>d</td><td>delete the current message</td></tr><tr><td>F</td><td>mark as important</td></tr><tr><td>l</td><td>show messages matching a pattern</td></tr><tr><td>N</td><td>mark message as new</td></tr><tr><td>o</td><td>change the current sort method</td></tr><tr><td>O</td><td>reverse sort the mailbox</td></tr><tr><td>q</td><td>save changes and exit</td></tr><tr><td>s</td><td>save-message</td></tr><tr><td>T</td><td>tag messages matching a pattern</td></tr><tr><td>t</td><td>toggle the tag on a message</td></tr><tr><td>Esc t</td><td>toggle tag on entire message thread</td></tr><tr><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td>u</td><td>undelete-message</td></tr><tr><td>v</td><td>view-attachments</td></tr><tr><td>x</td><td>abort changes and exit</td></tr><tr><td><Return></td><td>display-message</td></tr><tr><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td>@</td><td>show the author's full e-mail address</td></tr><tr><td>$</td><td>save changes to mailbox</td></tr><tr><td>/</td><td>search</td></tr><tr><td>Esc /</td><td>search-reverse</td></tr><tr><td>^L</td><td>clear and redraw the screen</td></tr><tr><td>^T</td><td>untag messages matching a pattern</td></tr></tbody></table></div></div><br class="table-break" /><p>
-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 “<span class="quote">flags</span>” in <a class="xref" href="gettingstarted.html#tab-msg-status-flags" title="Table 2.4. Message status flags">Table 2.4, “Message status flags”</a>
-may appear, some of which can be turned on or off using these functions:
-<code class="literal"><set-flag></code> and
-<code class="literal"><clear-flag></code>
-bound by default to “<span class="quote">w</span>” and “<span class="quote">W</span>” respectively.
-</p><p>
-Furthermore, the flags in <a class="xref" href="gettingstarted.html#tab-msg-recip-flags" title="Table 2.5. Message recipient flags">Table 2.5, “Message recipient flags”</a> reflect
-who the message is addressed to. They can be customized with the
-<a class="link" href="reference.html#to-chars" title="3.292. to_chars">$to_chars</a> variable.
-</p><div class="table"><a id="tab-msg-status-flags"></a><p class="title"><b>Table 2.4. Message status flags</b></p><div class="table-contents"><table summary="Message status flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>D</td><td>message is deleted (is marked for deletion)</td></tr><tr><td>d</td><td>message has attachments marked for deletion</td></tr><tr><td>K</td><td>contains a PGP public key</td></tr><tr><td>N</td><td>message is new</td></tr><tr><td>O</td><td>message is old</td></tr><tr><td>P</td><td>message is PGP encrypted</td></tr><tr><td>r</td><td>message has been replied to</td></tr><tr><td>S</td><td>message is signed, and the signature is successfully verified</td></tr><tr><td>s</td><td>message is signed</td></tr><tr><td>!</td><td>message is flagged</td></tr><tr><td>*</td><td>message is tagged</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-msg-recip-flags"></a><p class="title"><b>Table 2.5. Message recipient flags</b></p><div class="table-contents"><table summary="Message recipient flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>+</td><td>message is to you and you only</td></tr><tr><td>T</td><td>message is to you, but also to or cc'ed to others</td></tr><tr><td>C</td><td>message is cc'ed to you</td></tr><tr><td>F</td><td>message is from you</td></tr><tr><td>L</td><td>message is sent to a subscribed mailing list</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-menu"></a>4.2. The Pager</h3></div></div></div><p>
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program <span class="emphasis"><em>less</em></span> though not nearly as
-featureful.
-</p><div class="table"><a id="tab-key-pager"></a><p class="title"><b>Table 2.6. Most common pager keys</b></p><div class="table-contents"><table summary="Most common pager keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td><Return></td><td>go down one line</td></tr><tr><td><Space></td><td>display the next page (or next message if at the end of a message)</td></tr><tr><td>-</td><td>go back to the previous page</td></tr><tr><td>n</td><td>search for next match</td></tr><tr><td>S</td><td>skip beyond quoted text</td></tr><tr><td>T</td><td>toggle display of quoted text</td></tr><tr><td>?</td><td>show keybindings</td></tr><tr><td>/</td><td>regular expression search</td></tr><tr><td>Esc /</td><td>backward regular expression search</td></tr><tr><td>\</td><td>toggle highlighting of search matches</td></tr><tr><td>^</td><td>jump to the top of the message</td></tr></tbody></table></div></div><br class="table-break" /><p>
-In addition to key bindings in <a class="xref" href="gettingstarted.html#tab-key-pager" title="Table 2.6. Most common pager keys">Table 2.6, “Most common pager keys”</a>,
-many of the functions from the index menu are also available in
-the pager, such as <code class="literal"><delete-message></code> or <code class="literal"><copy-message></code>
-(this is one advantage over using an external pager to view messages).
-</p><p>
-Also, the internal pager supports a couple other advanced features. For
-one, it will accept and translate the “<span class="quote">standard</span>” nroff sequences for
-bold and underline. These sequences are a series of either the letter,
-backspace (^H), the letter again for bold or the letter, backspace,
-“<span class="quote">_</span>” for denoting underline. Mutt will attempt to display these
-in bold and underline respectively if your terminal supports them. If
-not, you can use the bold and underline <a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">color</a>
-objects to specify a color or mono attribute for them.
-</p><p>
-Additionally, the internal pager supports the ANSI escape sequences for
-character attributes. Mutt translates them into the correct color and
-character settings. The sequences Mutt supports are:
-</p><pre class="screen">
-\e[<span class="emphasis"><em>Ps</em></span>;<span class="emphasis"><em>Ps</em></span>;..<span class="emphasis"><em>Ps</em></span>;m
-</pre><p>
-where <span class="emphasis"><em>Ps</em></span> can be one of the codes shown in
-<a class="xref" href="gettingstarted.html#tab-ansi-esc" title="Table 2.7. ANSI escape sequences">Table 2.7, “ANSI escape sequences”</a>.
-</p><div class="table"><a id="tab-ansi-esc"></a><p class="title"><b>Table 2.7. ANSI escape sequences</b></p><div class="table-contents"><table summary="ANSI escape sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Escape code</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>All attributes off</td></tr><tr><td>1</td><td>Bold on</td></tr><tr><td>4</td><td>Underline on</td></tr><tr><td>5</td><td>Blink on</td></tr><tr><td>7</td><td>Reverse video on</td></tr><tr><td>3<span class="emphasis"><em><color></em></span></td><td>Foreground color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="gettingstarted.html#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr><tr><td>4<span class="emphasis"><em><color></em></span></td><td>Background color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="gettingstarted.html#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-color"></a><p class="title"><b>Table 2.8. Color sequences</b></p><div class="table-contents"><table summary="Color sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Color code</th><th>Color</th></tr></thead><tbody><tr><td>0</td><td>Black</td></tr><tr><td>1</td><td>Red</td></tr><tr><td>2</td><td>Green</td></tr><tr><td>3</td><td>Yellow</td></tr><tr><td>4</td><td>Blue</td></tr><tr><td>5</td><td>Magenta</td></tr><tr><td>6</td><td>Cyan</td></tr><tr><td>7</td><td>White</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Mutt uses these attributes for handling <code class="literal">text/enriched</code>
-messages, and they can also be used by an external
-<a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">autoview</a> script for highlighting
-purposes.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-Note that the search commands in the pager take regular expressions,
-which are not quite the same as the more
-complex <a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> used by the search
-command in the index. This is because the pager only performs simple
-text search, whereas the index provides boolean filtering on several
-aspects of messages.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="threads"></a>4.3. Threaded Mode</h3></div></div></div><p>
-When the mailbox is <a class="link" href="reference.html#sort" title="3.273. sort">sorted</a> by <span class="emphasis"><em>threads</em></span>, there are
-a few additional functions available in the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> modes
-as shown in <a class="xref" href="gettingstarted.html#tab-key-threads" title="Table 2.9. Most common thread mode keys">Table 2.9, “Most common thread mode keys”</a>.
-</p><div class="table"><a id="tab-key-threads"></a><p class="title"><b>Table 2.9. Most common thread mode keys</b></p><div class="table-contents"><table summary="Most common thread mode keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^D</td><td><code class="literal"><delete-thread></code></td><td>delete all messages in the current thread</td></tr><tr><td>^U</td><td><code class="literal"><undelete-thread></code></td><td>undelete all messages in the current thread</td></tr><tr><td>^N</td><td><code class="literal"><next-thread></code></td><td>jump to the start of the next thread</td></tr><tr><td>^P</td><td><code class="literal"><previous-thread></code></td><td>jump to the start of the previous thread</td></tr><tr><td>^R</td><td><code class="literal"><read-thread></code></td><td>mark the current thread as read</td></tr><tr><td>Esc d</td><td><code class="literal"><delete-subthread></code></td><td>delete all messages in the current subthread</td></tr><tr><td>Esc u</td><td><code class="literal"><undelete-subthread></code></td><td>undelete all messages in the current subthread</td></tr><tr><td>Esc n</td><td><code class="literal"><next-subthread></code></td><td>jump to the start of the next subthread</td></tr><tr><td>Esc p</td><td><code class="literal"><previous-subthread></code></td><td>jump to the start of the previous subthread</td></tr><tr><td>Esc r</td><td><code class="literal"><read-subthread></code></td><td>mark the current subthread as read</td></tr><tr><td>Esc t</td><td><code class="literal"><tag-thread></code></td><td>toggle the tag on the current thread</td></tr><tr><td>Esc v</td><td><code class="literal"><collapse-thread></code></td><td>toggle collapse for the current thread</td></tr><tr><td>Esc V</td><td><code class="literal"><collapse-all></code></td><td>toggle collapse for all threads</td></tr><tr><td>P</td><td><code class="literal"><parent-message></code></td><td>jump to parent message in thread</td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><h3 class="title">Note</h3><p>
-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 on
-the screen. See %M in <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>.
-For example, you could use "%?M?(#%03M)&(%4l)?" in <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> to optionally
-display the number of hidden messages if the thread is collapsed.
-</p></div><p>
-See also: <a class="link" href="reference.html#strict-threads" title="3.283. strict_threads">$strict_threads</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reading-misc"></a>4.4. Miscellaneous Functions</h3></div></div></div><p>
-In addition, the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span>
-menus have these interesting functions:
-</p><div class="variablelist"><dl><dt><span class="term">
-<code class="literal"><create-alias></code><a id="create-alias"></a> (default: a)
-</span></dt><dd><p>
-Creates a new alias based upon the current message (or prompts for a
-new one). Once editing is complete, an <a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">alias</a>
-command is added to the file specified by
-the <a class="link" href="reference.html#alias-file" title="3.3. alias_file">$alias_file</a> variable
-for future use
-</p><div class="note"><h3 class="title">Note</h3><p>
-Mutt does not read the <a class="link" href="reference.html#alias-file" title="3.3. alias_file">$alias_file</a>
-upon startup so you must explicitly <a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a> the file.
-</p></div></dd><dt><span class="term">
-<code class="literal"><check-traditional-pgp></code><a id="check-traditional-pgp"></a> (default: Esc P)
-</span></dt><dd><p>
-This function will search the current message for content signed or
-encrypted with PGP the “<span class="quote">traditional</span>” 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 <a class="link" href="gettingstarted.html#edit-type"><code class="literal"><edit-type></code></a> function's
-effect.
-</p></dd><dt><span class="term">
-<code class="literal"><edit></code><a id="edit"></a> (default: e)
-</span></dt><dd><p>
-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; if the message is unchanged it won't be replaced.
-</p></dd><dt><span class="term">
-<code class="literal"><edit-type></code><a id="edit-type"></a> (default:
-^E on the attachment menu, and in the pager and index menus;
-^T on the compose menu)
-</span></dt><dd><p>
-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 class="link" href="mimesupport.html#attach-menu" title="1.2. The Attachment Menu">attachment menu</a>, you can change any
-attachment's content type. These changes are not persistent, and get
-lost upon changing folders.
-</p><p>
-Note that this command is also available on the <a class="link" href="mimesupport.html#compose-menu" title="1.3. The Compose Menu">compose
-menu</a>. There, it's used to fine-tune the properties of attachments you are going
-to send.
-</p></dd><dt><span class="term">
-<code class="literal"><enter-command></code><a id="enter-command"></a> (default: “<span class="quote">:</span>”)
-</span></dt><dd><p>
-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 <a class="link" href="configuration.html#macro" title="8. Keyboard macros">macros</a> to change settings on the
-fly.
-</p></dd><dt><span class="term">
-<code class="literal"><extract-keys></code><a id="extract-keys"></a> (default: ^K)
-</span></dt><dd><p>
-This command extracts PGP public keys from the current or tagged
-message(s) and adds them to your PGP public key ring.
-</p></dd><dt><span class="term">
-<code class="literal"><forget-passphrase></code><a id="forget-passphrase"></a> (default:
-^F)
-</span></dt><dd><p>
-This command wipes the passphrase(s) from memory. It is useful, if
-you misspelled the passphrase.
-</p></dd><dt><span class="term">
-<code class="literal"><list-reply></code><a id="list-reply"></a> (default: L)
-</span></dt><dd><p>
-Reply to the current or tagged message(s) by extracting any addresses which
-match the regular expressions given by the <a class="link" href="configuration.html#lists" title="12. Mailing lists">lists or subscribe</a>
-commands, but also honor any <code class="literal">Mail-Followup-To</code> header(s) if the
-<a class="link" href="reference.html#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a>
-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.
-</p></dd><dt><span class="term">
-<code class="literal"><pipe-message></code><a id="pipe-message"></a> (default: |)
-</span></dt><dd><p>
-Asks for an external Unix command and pipes the current or
-tagged message(s) to it. The variables <a class="link" href="reference.html#pipe-decode" title="3.214. pipe_decode">$pipe_decode</a>, <a class="link" href="reference.html#pipe-split" title="3.213. pipe_split">$pipe_split</a>,
-<a class="link" href="reference.html#pipe-sep" title="3.215. pipe_sep">$pipe_sep</a> and <a class="link" href="reference.html#wait-key" title="3.303. wait_key">$wait_key</a> control the exact behavior of this function.
-</p></dd><dt><span class="term">
-<code class="literal"><resend-message></code><a id="resend-message"></a> (default: Esc e)
-</span></dt><dd><p>
-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 <a class="link" href="reference.html#weed" title="3.304. weed">$weed</a>
-variable.
-</p><p>
-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 <code class="literal">message/rfc822</code> body part.
-</p></dd><dt><span class="term">
-<code class="literal"><shell-escape></code><a id="shell-escape"></a> (default: !)
-</span></dt><dd><p>
-Asks for an external Unix command and executes it. The <a class="link" href="reference.html#wait-key" title="3.303. wait_key">$wait_key</a> can be used to control
-whether Mutt 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. If no command is given, an
-interactive shell is executed.
-</p></dd><dt><span class="term">
-<code class="literal"><toggle-quoted></code><a id="toggle-quoted"></a> (default: T)
-</span></dt><dd><p>
-The pager uses the <a class="link" href="reference.html#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a> variable to detect quoted text when
-displaying the body of the message. This function toggles the display
-of the quoted material in the message. It is particularly useful when
-being interested in just the response and there is a large amount of
-quoted text in the way.
-</p></dd><dt><span class="term">
-<code class="literal"><skip-quoted></code><a id="skip-quoted"></a> (default: S)
-</span></dt><dd><p>
-This function will go to the next line of non-quoted text which comes
-after a line of quoted text in the internal pager.
-</p></dd></dl></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="sending"></a>5. Sending Mail</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-intro"></a>5.1. Introduction</h3></div></div></div><p>
-The bindings shown in <a class="xref" href="gettingstarted.html#tab-key-send" title="Table 2.10. Most common mail sending keys">Table 2.10, “Most common mail sending keys”</a> are available in the
-<span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> to start a new message.
-</p><div class="table"><a id="tab-key-send"></a><p class="title"><b>Table 2.10. Most common mail sending keys</b></p><div class="table-contents"><table summary="Most common mail sending keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>m</td><td><code class="literal"><compose></code></td><td>compose a new message</td></tr><tr><td>r</td><td><code class="literal"><reply></code></td><td>reply to sender</td></tr><tr><td>g</td><td><code class="literal"><group-reply></code></td><td>reply to all recipients</td></tr><tr><td>L</td><td><code class="literal"><list-reply></code></td><td>reply to mailing list address</td></tr><tr><td>f</td><td><code class="literal"><forward></code></td><td>forward message</td></tr><tr><td>b</td><td><code class="literal"><bounce></code></td><td>bounce (remail) message</td></tr><tr><td>Esc k</td><td><code class="literal"><mail-key></code></td><td>mail a PGP public key to someone</td></tr></tbody></table></div></div><br class="table-break" /><p>
-<span class="emphasis"><em>Bouncing</em></span> a message sends the message as-is to the recipient you
-specify. <span class="emphasis"><em>Forwarding</em></span> 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 “<span class="quote"><a class="link" href="gettingstarted.html#forwarding-mail" title="6. Forwarding and Bouncing Mail">Forwarding
-and Bouncing Mail</a>.</span>”
-</p><p>
-Mutt will then enter the <span class="emphasis"><em>compose</em></span> menu and prompt you for the
-recipients to place on the “<span class="quote">To:</span>” header field. Next, it will ask
-you for the “<span class="quote">Subject:</span>” field for the message, providing a default if
-you are replying to or forwarding a message. See also
-<a class="link" href="reference.html#askcc" title="3.10. askcc">$askcc</a>,
-<a class="link" href="reference.html#askbcc" title="3.9. askbcc">$askbcc</a>,
-<a class="link" href="reference.html#autoedit" title="3.17. autoedit">$autoedit</a>,
-<a class="link" href="reference.html#bounce" title="3.21. bounce">$bounce</a>,
-<a class="link" href="reference.html#fast-reply" title="3.55. fast_reply">$fast_reply</a>,
-and <a class="link" href="reference.html#include" title="3.98. include">$include</a>
-for changing how Mutt asks these questions.
-</p><p>
-Mutt will then automatically start your <a class="link" href="reference.html#editor" title="3.51. editor">$editor</a>
-on the message body. If the <a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a>
-variable is set, the headers will be at the top of the message in your editor.
-Any messages you are replying to will be added in sort order to the message,
-with appropriate <a class="link" href="reference.html#attribution" title="3.16. attribution">$attribution</a>,
-<a class="link" href="reference.html#indent-string" title="3.100. indent_string">$indent_string</a> and
-<a class="link" href="reference.html#post-indent-string" title="3.225. post_indent_string">$post_indent_string</a>.
-When forwarding a message, if the <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a>
-variable is unset, a copy of the forwarded message will be included. If
-you have specified a <a class="link" href="reference.html#signature" title="3.265. signature">$signature</a>, it
-will be appended to the message.
-</p><p>
-Once you have finished editing the body of your mail message, you are
-returned to the <span class="emphasis"><em>compose</em></span> menu providing the functions
-shown in <a class="xref" href="gettingstarted.html#tab-func-compose" title="Table 2.11. Most common compose menu keys">Table 2.11, “Most common compose menu keys”</a> to modify, send or postpone the
-message.
-</p><div class="table"><a id="tab-func-compose"></a><p class="title"><b>Table 2.11. Most common compose menu keys</b></p><div class="table-contents"><table summary="Most common compose menu keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>a</td><td><code class="literal"><attach-file></code></td><td>attach a file</td></tr><tr><td>A</td><td><code class="literal"><attach-message></code></td><td>attach message(s) to the message</td></tr><tr><td>Esc k</td><td><code class="literal"><attach-key></code></td><td>attach a PGP public key</td></tr><tr><td>d</td><td><code class="literal"><edit-description></code></td><td>edit description on attachment</td></tr><tr><td>D</td><td><code class="literal"><detach-file></code></td><td>detach a file</td></tr><tr><td>t</td><td><code class="literal"><edit-to></code></td><td>edit the To field</td></tr><tr><td>Esc f</td><td><code class="literal"><edit-from></code></td><td>edit the From field</td></tr><tr><td>r</td><td><code class="literal"><edit-reply-to></code></td><td>edit the Reply-To field</td></tr><tr><td>c</td><td><code class="literal"><edit-cc></code></td><td>edit the Cc field</td></tr><tr><td>b</td><td><code class="literal"><edit-bcc></code></td><td>edit the Bcc field</td></tr><tr><td>y</td><td><code class="literal"><send-message></code></td><td>send the message</td></tr><tr><td>s</td><td><code class="literal"><edit-subject></code></td><td>edit the Subject</td></tr><tr><td>S</td><td><code class="literal"><smime-menu></code></td><td>select S/MIME options</td></tr><tr><td>f</td><td><code class="literal"><edit-fcc></code></td><td>specify an “<span class="quote">Fcc</span>” mailbox</td></tr><tr><td>p</td><td><code class="literal"><pgp-menu></code></td><td>select PGP options</td></tr><tr><td>P</td><td><code class="literal"><postpone-message></code></td><td>postpone this message until later</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>quit (abort) sending the message</td></tr><tr><td>w</td><td><code class="literal"><write-fcc></code></td><td>write the message to a folder</td></tr><tr><td>i</td><td><code class="literal"><ispell></code></td><td>check spelling (if available on your system)</td></tr><tr><td>^F</td><td><code class="literal"><forget-passphrase></code></td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The compose menu is also used to edit the attachments for a message which can be either files
-or other messages. The <code class="literal"><attach-message></code> function to will prompt you for a folder to
-attach messages from. You can now tag messages in that folder and they
-will be attached to the message you are sending.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that certain
-operations like composing a new mail, replying, forwarding, etc. are
-not permitted when you are in that folder. The %r in
-<a class="link" href="reference.html#status-format" title="3.281. status_format">$status_format</a> will change to
-a “<span class="quote">A</span>” to indicate that you are in attach-message mode.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-header"></a>5.2. Editing the message header</h3></div></div></div><p>
-When editing the header because of <a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a>
-being set, there are a several pseudo headers available which
-will not be included in sent messages.
-</p><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="fcc-header"></a>5.2.1. Fcc: pseudo header</h4></div></div></div><p>
-If you specify
-
-<code class="literal">Fcc:</code> <span class="emphasis"><em>filename</em></span>
-
-as a header, Mutt will pick up <span class="emphasis"><em>filename</em></span>
-just as if you had used the <code class="literal"><edit-fcc></code> function in the <span class="emphasis"><em>compose</em></span> menu.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="attach-header"></a>5.2.2. Attach: pseudo header</h4></div></div></div><p>
-You can also attach files to your message by specifying
-
-<code class="literal">Attach:</code> <span class="emphasis"><em>filename</em></span> [ <span class="emphasis"><em>description</em></span> ]
-
-where <span class="emphasis"><em>filename</em></span> is the file to attach and <span class="emphasis"><em>description</em></span> is an
-optional string to use as the description of the attached file.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="pgp-header"></a>5.2.3. Pgp: pseudo header</h4></div></div></div><p>
-If you want to use PGP, you can specify
-</p><p>
-<code class="literal">Pgp:</code> [ <code class="literal">E</code> | <code class="literal">S</code> | <code class="literal">S</code><span class="emphasis"><em><id></em></span> ]
-
-</p><p>
-“<span class="quote">E</span>” selects encryption, “<span class="quote">S</span>” selects signing and
-“<span class="quote">S<id></span>” selects signing with the given key, setting
-<a class="link" href="reference.html#pgp-sign-as" title="3.166. pgp_sign_as">$pgp_sign_as</a>
-permanently.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="in-reply-to-header"></a>5.2.4. In-Reply-To: header</h4></div></div></div><p>
-When replying to messages, the <span class="emphasis"><em>In-Reply-To:</em></span> header contains the
-Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
-<span class="emphasis"><em>References:</em></span> field, which allows you to create a new message thread, for example
-to create a new message to a mailing list without having to enter the mailing list's address.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-crypto"></a>5.3. Sending cryptographically signed/encrypted messages</h3></div></div></div><p>
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
-through a key selection process when you try to send the message.
-Mutt 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.
-</p><p>
-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 <code class="literal">^G</code>. When you do so, mutt will
-return to the compose screen.
-</p><p>
-Once you have successfully finished the key selection, the message
-will be encrypted using the selected public keys when sent out.
-</p><p>
-Most fields of the entries in the key selection menu (see also <a class="link" href="reference.html#pgp-entry-format" title="3.158. pgp_entry_format">$pgp_entry_format</a>)
-have obvious meanings. But some explanations on the capabilities, flags,
-and validity fields are in order.
-</p><p>
-The flags sequence (%f) will expand to one of the flags in
-<a class="xref" href="gettingstarted.html#tab-pgp-menuflags" title="Table 2.12. PGP key menu flags">Table 2.12, “PGP key menu flags”</a>.
-</p><div class="table"><a id="tab-pgp-menuflags"></a><p class="title"><b>Table 2.12. PGP key menu flags</b></p><div class="table-contents"><table summary="PGP key menu flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>R</td><td>The key has been revoked and can't be used.</td></tr><tr><td>X</td><td>The key is expired and can't be used.</td></tr><tr><td>d</td><td>You have marked the key as disabled.</td></tr><tr><td>c</td><td>There are unknown critical self-signature packets.</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The capabilities field (%c) expands to a two-character sequence
-representing a key's capabilities. The first character gives
-the key's encryption capabilities: A minus sign (“<span class="quote">-</span>”) means
-that the key cannot be used for encryption. A dot (“<span class="quote">.</span>”) means that
-it's marked as a signature key in one of the user IDs, but may
-also be used for encryption. The letter “<span class="quote">e</span>” indicates that
-this key can be used for encryption.
-</p><p>
-The second character indicates the key's signing capabilities. Once
-again, a “<span class="quote">-</span>” implies “<span class="quote">not for signing</span>”, “<span class="quote">.</span>” implies
-that the key is marked as an encryption key in one of the user-ids, and
-“<span class="quote">s</span>” denotes a key which can be used for signing.
-</p><p>
-Finally, the validity field (%t) indicates how well-certified a user-id
-is. A question mark (“<span class="quote">?</span>”) indicates undefined validity, a minus
-character (“<span class="quote">-</span>”) marks an untrusted association, a space character
-means a partially trusted association, and a plus character (“<span class="quote">+</span>”)
-indicates complete validity.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-mixmaster"></a>5.4. Sending anonymous messages via mixmaster</h3></div></div></div><p>
-You may also have compiled 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.
-</p><p>
-To use it, you'll have to obey certain restrictions. Most
-important, you cannot use the <code class="literal">Cc</code> and <code class="literal">Bcc</code> headers. To tell
-Mutt to use mixmaster, you have to select a remailer chain, using
-the mix function on the compose menu.
-</p><p>
-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.
-</p><p>
-You can navigate in the chain using the <code class="literal"><chain-prev></code> and
-<code class="literal"><chain-next></code> functions, which are by default bound to the left
-and right arrows and to the <code class="literal">h</code> and <code class="literal">l</code> keys (think vi
-keyboard bindings). To insert a remailer at the current chain
-position, use the <code class="literal"><insert></code> function. To append a remailer behind
-the current chain position, use <code class="literal"><select-entry></code> or <code class="literal"><append></code>.
-You can also delete entries from the chain, using the corresponding
-function. Finally, to abandon your changes, leave the menu, or
-<code class="literal"><accept></code> them pressing (by default) the <code class="literal">Return</code> key.
-</p><p>
-Note that different remailers do have different capabilities,
-indicated in the %c entry of the remailer menu lines (see
-<a class="link" href="reference.html#mix-entry-format" title="3.130. mix_entry_format">$mix_entry_format</a>). Most important is
-the “<span class="quote">middleman</span>” capability, indicated by a capital “<span class="quote">M</span>”: 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ff"></a>5.5. Sending format=flowed messages</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-concept"></a>5.5.1. Concept</h4></div></div></div><p>
-<code class="literal">format=flowed</code>-style messages (or <code class="literal">f=f</code>
-for short) are <code class="literal">text/plain</code> messages that consist of paragraphs which a receiver's
-mail client may reformat to its own needs which mostly means to
-customize line lengths regardless of what the sender sent. Technically this is
-achieved by letting lines of a “<span class="quote">flowable</span>” paragraph end in spaces
-except for the last line.
-</p><p>
-While for text-mode clients like mutt it's the best way to assume only a
-standard 80x25 character cell terminal, it may be desired to let the
-receiver decide completely how to view a message.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-support"></a>5.5.2. Mutt support</h4></div></div></div><p>
-Mutt only supports setting the required <code class="literal">format=flowed</code>
-MIME parameter on outgoing messages if the <a class="link" href="reference.html#text-flowed" title="3.285. text_flowed">$text_flowed</a>
-variable is set, specifically it does not add the
-trailing spaces.
-</p><p>
-After editing the initial message text and before entering
-the compose menu, mutt properly space-stuffes the message.
-<span class="emphasis"><em>Space-stuffing</em></span> is required by RfC3676 defining
-<code class="literal">format=flowed</code> and means to prepend a space to:
-</p><div class="itemizedlist"><ul type="disc"><li><p>all lines starting with a space</p></li><li><p>lines starting with the word “<span class="quote"><code class="literal">From</code></span>”
-followed by space</p></li><li><p>all lines starting with “<span class="quote"><code class="literal">></code></span>” which
-is not intended to be a quote character</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
-Mutt only supports space-stuffing
-for the first two types of lines but not for the third: It is impossible to
-safely detect whether a leading <code class="literal">></code> character starts a
-quote or not. Furthermore, Mutt only applies space-stuffing
-<span class="emphasis"><em>once</em></span> after the initial edit is finished.
-</p></div><p>
-All leading spaces are to be removed by receiving clients to restore
-the original message prior to further processing.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-editor"></a>5.5.3. Editor considerations</h4></div></div></div><p>
-As mutt provides no additional features to compose <code class="literal">f=f</code>
-messages, it's completely up to the user and his editor to produce
-proper messages. Please consider your editor's documentation if you
-intend to send <code class="literal">f=f</code> messages.
-</p><p>
-Please note that when editing messages from the compose menu several
-times before really sending a mail, it's up to the user to ensure that
-the message is properly space-stuffed.
-</p><p>
-For example, <span class="emphasis"><em>vim</em></span> provides the <code class="literal">w</code>
-flag for its <code class="literal">formatoptions</code> setting to assist in
-creating <code class="literal">f=f</code> messages, see <code class="literal">:help
-fo-table</code> for details.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="forwarding-mail"></a>6. Forwarding and Bouncing Mail</h2></div></div></div><p>
-Bouncing and forwarding let you send an existing message to recipients
-that you specify. Bouncing a message sends a verbatim copy of a message
-to alternative addresses as if they were the message's original
-recipients specified in the Bcc header.
-Forwarding a message, on the other hand, allows you to modify the message
-before it is resent (for example, by adding your own comments). Bouncing
-is done using the <code class="literal"><bounce></code> function and forwarding
-using the <code class="literal"><forward></code> function bound to “<span class="quote">b</span>” and “<span class="quote">f</span>”
-respectively.
-</p><p>
-Forwarding can be done by including the original message in the new
-message's body (surrounded by indicating lines) or including it as a MIME
-attachment, depending on the value of the <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> variable. Decoding of attachments,
-like in the pager, can be controlled by the <a class="link" href="reference.html#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="reference.html#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> variables,
-respectively. The desired forwarding format may depend on the content,
-therefore <span class="emphasis"><em>$mime_forward</em></span> is a quadoption which, for
-example, can be set to “<span class="quote">ask-no</span>”.
-</p><p>
-The inclusion of headers is controlled by the current setting of the
-<a class="link" href="reference.html#weed" title="3.304. weed">$weed</a> variable, unless <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is set.
-</p><p>
-Editing the message to forward follows the same procedure as sending or
-replying to a message does.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="postponing-mail"></a>7. Postponing Mail</h2></div></div></div><p>
-At times it is desirable to delay sending a message that you have
-already begun to compose. When the <code class="literal"><postpone-message></code> function is
-used in the <span class="emphasis"><em>compose</em></span> menu, the body of your message and attachments
-are stored in the mailbox specified by the <a class="link" href="reference.html#postponed" title="3.227. postponed">$postponed</a> variable. This means that you can recall the
-message even if you exit Mutt and then restart it at a later time.
-</p><p>
-Once a message is postponed, there are several ways to resume it. From the
-command line you can use the “<span class="quote">-p</span>” option, or if you compose a new
-message from the <span class="emphasis"><em>index</em></span> or <span class="emphasis"><em>pager</em></span> you will be prompted if postponed
-messages exist. If multiple messages are currently postponed, the
-<span class="emphasis"><em>postponed</em></span> menu will pop up and you can select which message you would
-like to resume.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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.
-</p></div><p>
-See also the <a class="link" href="reference.html#postpone" title="3.226. postpone">$postpone</a> quad-option.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="intro.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="configuration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. Introduction </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Configuration</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Mutt E-Mail Client</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><meta name="description" content="All mail clients suck. This one just sucks less. -me, circa 1995" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="next" href="intro.html" title="Chapter 1. Introduction" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The Mutt E-Mail Client</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="intro.html">Next</a></td></tr></table><hr /></div><div class="book" lang="en" xml:lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="id2820016"></a>The Mutt E-Mail Client</h1></div><div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Elkins</span></h3><code class="email"><<a class="email" href="mailto:me@cs.hmc.edu">me@cs.hmc.edu</a>></code></div></div><div><p class="releaseinfo">version 1.5.19 (2009-01-05)</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
-“<span class="quote">All mail clients suck. This one just sucks less.</span>” -me, circa 1995
-</p></div></div></div><hr /></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="intro.html">1. Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="intro.html#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="intro.html#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="intro.html#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="intro.html#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="intro.html#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="intro.html#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="intro.html#copyright">7. Copyright</a></span></dt></dl></dd><dt><span class="chapter"><a href="gettingstarted.html">2. Getting Started</a></span></dt><dd><dl><dt><span class="sect1"><a href="gettingstarted.html#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#postponing-mail">7. Postponing Mail</a></span></dt></dl></dd><dt><span class="chapter"><a href="configuration.html">3. Configuration</a></span></dt><dd><dl><dt><span class="sect1"><a href="configuration.html#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="configuration.html#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="configuration.html#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="configuration.html#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="configuration.html#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="configuration.html#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="configuration.html#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="configuration.html#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="configuration.html#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="configuration.html#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="configuration.html#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="configuration.html#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="configuration.html#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="configuration.html#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="configuration.html#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="configuration.html#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="configuration.html#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="configuration.html#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="configuration.html#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="configuration.html#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="configuration.html#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="configuration.html#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="configuration.html#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="configuration.html#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="configuration.html#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="configuration.html#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="configuration.html#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="configuration.html#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="configuration.html#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="configuration.html#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="configuration.html#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="configuration.html#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="configuration.html#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="configuration.html#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="advancedusage.html">4. Advanced Usage</a></span></dt><dd><dl><dt><span class="sect1"><a href="advancedusage.html#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></dd><dt><span class="chapter"><a href="mimesupport.html">5. Mutt's MIME Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="mimesupport.html#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="mimesupport.html#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="mimesupport.html#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="mimesupport.html#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="mimesupport.html#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="mimesupport.html#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#mime-lookup">7. MIME Lookup</a></span></dt></dl></dd><dt><span class="chapter"><a href="optionalfeatures.html">6. Optional features</a></span></dt><dd><dl><dt><span class="sect1"><a href="optionalfeatures.html#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#exact-address">8. Exact address generation</a></span></dt></dl></dd><dt><span class="chapter"><a href="tuning.html">7. Performance tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="tuning.html#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="tuning.html#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="tuning.html#tuning-search">3. Searching and limiting</a></span></dt></dl></dd><dt><span class="chapter"><a href="reference.html">8. Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="reference.html#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="reference.html#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="reference.html#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="reference.html#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="reference.html#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="reference.html#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="reference.html#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="reference.html#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="reference.html#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="reference.html#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="reference.html#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="reference.html#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="reference.html#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="reference.html#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="reference.html#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="reference.html#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="reference.html#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="reference.html#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="reference.html#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="reference.html#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="reference.html#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="reference.html#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="reference.html#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="reference.html#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="reference.html#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="reference.html#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="reference.html#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="reference.html#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="reference.html#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="reference.html#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="reference.html#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="reference.html#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="reference.html#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="reference.html#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="reference.html#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="reference.html#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="reference.html#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="reference.html#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="reference.html#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="reference.html#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="reference.html#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="reference.html#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="reference.html#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="reference.html#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="reference.html#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="reference.html#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="reference.html#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="reference.html#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="reference.html#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="reference.html#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="reference.html#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="reference.html#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="reference.html#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="reference.html#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="reference.html#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="reference.html#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="reference.html#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="reference.html#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="reference.html#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="reference.html#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="reference.html#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="reference.html#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="reference.html#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="reference.html#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="reference.html#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="reference.html#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="reference.html#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="reference.html#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="reference.html#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="reference.html#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="reference.html#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="reference.html#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="reference.html#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="reference.html#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="reference.html#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="reference.html#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="reference.html#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="reference.html#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="reference.html#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="reference.html#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="reference.html#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="reference.html#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="reference.html#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="reference.html#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="reference.html#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="reference.html#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="reference.html#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="reference.html#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="reference.html#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="reference.html#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="reference.html#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="reference.html#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="reference.html#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="reference.html#sidebar-delim">3.150. sidebar_delim</a></span></dt><dt><span class="sect2"><a href="reference.html#sidebar-visible">3.151. sidebar_visible</a></span></dt><dt><span class="sect2"><a href="reference.html#sidebar-width">3.152. sidebar_width</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-use-gpg-agent">3.153. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-verify-sig">3.154. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-is-default">3.155. smime_is_default</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-ask-cert-label">3.156. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-decrypt-use-default-key">3.157. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-entry-format">3.158. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-good-sign">3.159. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-check-exit">3.160. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-long-ids">3.161. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-retainable-sigs">3.162. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-autoinline">3.163. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-replyinline">3.164. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-show-unusable">3.165. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sign-as">3.166. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-strict-enc">3.167. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-timeout">3.168. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sort-keys">3.169. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-auto">3.170. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-auto-decode">3.171. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-signature-filename">3.172. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-signature-description">3.173. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-decode-command">3.174. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-getkeys-command">3.175. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-verify-command">3.176. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-decrypt-command">3.177. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-clearsign-command">3.178. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sign-command">3.179. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-encrypt-sign-command">3.180. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-encrypt-only-command">3.181. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-import-command">3.182. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-export-command">3.183. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-verify-key-command">3.184. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-list-secring-command">3.185. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-list-pubring-command">3.186. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-decrypt">3.187. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-timeout">3.188. smime_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-encrypt-with">3.189. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-keys">3.190. smime_keys</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-ca-location">3.191. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-certificates">3.192. smime_certificates</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-decrypt-command">3.193. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-verify-command">3.194. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-verify-opaque-command">3.195. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-sign-command">3.196. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-sign-opaque-command">3.197. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-encrypt-command">3.198. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-pk7out-command">3.199. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-cert-command">3.200. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-signer-cert-command">3.201. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-import-cert-command">3.202. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-cert-email-command">3.203. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-default-key">3.204. smime_default_key</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-client-cert">3.205. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-force-tls">3.206. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-starttls">3.207. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="reference.html#certificate-file">3.208. certificate_file</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-use-sslv3">3.209. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-use-tlsv1">3.210. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-min-dh-prime-bits">3.211. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-ca-certificates-file">3.212. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-split">3.213. pipe_split</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-decode">3.214. pipe_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-sep">3.215. pipe_sep</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-authenticators">3.216. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-auth-try-all">3.217. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-checkinterval">3.218. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-delete">3.219. pop_delete</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-host">3.220. pop_host</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-last">3.221. pop_last</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-reconnect">3.222. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-user">3.223. pop_user</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-pass">3.224. pop_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#post-indent-string">3.225. post_indent_string</a></span></dt><dt><span class="sect2"><a href="reference.html#postpone">3.226. postpone</a></span></dt><dt><span class="sect2"><a href="reference.html#postponed">3.227. postponed</a></span></dt><dt><span class="sect2"><a href="reference.html#preconnect">3.228. preconnect</a></span></dt><dt><span class="sect2"><a href="reference.html#print">3.229. print</a></span></dt><dt><span class="sect2"><a href="reference.html#print-command">3.230. print_command</a></span></dt><dt><span class="sect2"><a href="reference.html#print-decode">3.231. print_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#print-split">3.232. print_split</a></span></dt><dt><span class="sect2"><a href="reference.html#prompt-after">3.233. prompt_after</a></span></dt><dt><span class="sect2"><a href="reference.html#query-command">3.234. query_command</a></span></dt><dt><span class="sect2"><a href="reference.html#query-format">3.235. query_format</a></span></dt><dt><span class="sect2"><a href="reference.html#quit">3.236. quit</a></span></dt><dt><span class="sect2"><a href="reference.html#quote-regexp">3.237. quote_regexp</a></span></dt><dt><span class="sect2"><a href="reference.html#read-inc">3.238. read_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#read-only">3.239. read_only</a></span></dt><dt><span class="sect2"><a href="reference.html#realname">3.240. realname</a></span></dt><dt><span class="sect2"><a href="reference.html#recall">3.241. recall</a></span></dt><dt><span class="sect2"><a href="reference.html#record">3.242. record</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-regexp">3.243. reply_regexp</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-self">3.244. reply_self</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-to">3.245. reply_to</a></span></dt><dt><span class="sect2"><a href="reference.html#resolve">3.246. resolve</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-alias">3.247. reverse_alias</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-name">3.248. reverse_name</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-realname">3.249. reverse_realname</a></span></dt><dt><span class="sect2"><a href="reference.html#rfc2047-parameters">3.250. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="reference.html#save-address">3.251. save_address</a></span></dt><dt><span class="sect2"><a href="reference.html#save-empty">3.252. save_empty</a></span></dt><dt><span class="sect2"><a href="reference.html#save-history">3.253. save_history</a></span></dt><dt><span class="sect2"><a href="reference.html#save-name">3.254. save_name</a></span></dt><dt><span class="sect2"><a href="reference.html#score">3.255. score</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-delete">3.256. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-flag">3.257. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-read">3.258. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="reference.html#send-charset">3.259. send_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#sendmail">3.260. sendmail</a></span></dt><dt><span class="sect2"><a href="reference.html#sendmail-wait">3.261. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="reference.html#shell">3.262. shell</a></span></dt><dt><span class="sect2"><a href="reference.html#sig-dashes">3.263. sig_dashes</a></span></dt><dt><span class="sect2"><a href="reference.html#sig-on-top">3.264. sig_on_top</a></span></dt><dt><span class="sect2"><a href="reference.html#signature">3.265. signature</a></span></dt><dt><span class="sect2"><a href="reference.html#simple-search">3.266. simple_search</a></span></dt><dt><span class="sect2"><a href="reference.html#smart-wrap">3.267. smart_wrap</a></span></dt><dt><span class="sect2"><a href="reference.html#smileys">3.268. smileys</a></span></dt><dt><span class="sect2"><a href="reference.html#sleep-time">3.269. sleep_time</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-authenticators">3.270. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-pass">3.271. smtp_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-url">3.272. smtp_url</a></span></dt><dt><span class="sect2"><a href="reference.html#sort">3.273. sort</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-alias">3.274. sort_alias</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-aux">3.275. sort_aux</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-browser">3.276. sort_browser</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-re">3.277. sort_re</a></span></dt><dt><span class="sect2"><a href="reference.html#spam-separator">3.278. spam_separator</a></span></dt><dt><span class="sect2"><a href="reference.html#spoolfile">3.279. spoolfile</a></span></dt><dt><span class="sect2"><a href="reference.html#status-chars">3.280. status_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#status-format">3.281. status_format</a></span></dt><dt><span class="sect2"><a href="reference.html#status-on-top">3.282. status_on_top</a></span></dt><dt><span class="sect2"><a href="reference.html#strict-threads">3.283. strict_threads</a></span></dt><dt><span class="sect2"><a href="reference.html#suspend">3.284. suspend</a></span></dt><dt><span class="sect2"><a href="reference.html#text-flowed">3.285. text_flowed</a></span></dt><dt><span class="sect2"><a href="reference.html#thread-received">3.286. thread_received</a></span></dt><dt><span class="sect2"><a href="reference.html#thorough-search">3.287. thorough_search</a></span></dt><dt><span class="sect2"><a href="reference.html#tilde">3.288. tilde</a></span></dt><dt><span class="sect2"><a href="reference.html#time-inc">3.289. time_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#timeout">3.290. timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#tmpdir">3.291. tmpdir</a></span></dt><dt><span class="sect2"><a href="reference.html#to-chars">3.292. to_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#trash">3.293. trash</a></span></dt><dt><span class="sect2"><a href="reference.html#tunnel">3.294. tunnel</a></span></dt><dt><span class="sect2"><a href="reference.html#use-8bitmime">3.295. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="reference.html#use-domain">3.296. use_domain</a></span></dt><dt><span class="sect2"><a href="reference.html#use-envelope-from">3.297. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="reference.html#use-from">3.298. use_from</a></span></dt><dt><span class="sect2"><a href="reference.html#use-idn">3.299. use_idn</a></span></dt><dt><span class="sect2"><a href="reference.html#use-ipv6">3.300. use_ipv6</a></span></dt><dt><span class="sect2"><a href="reference.html#user-agent">3.301. user_agent</a></span></dt><dt><span class="sect2"><a href="reference.html#visual">3.302. visual</a></span></dt><dt><span class="sect2"><a href="reference.html#wait-key">3.303. wait_key</a></span></dt><dt><span class="sect2"><a href="reference.html#weed">3.304. weed</a></span></dt><dt><span class="sect2"><a href="reference.html#wrap">3.305. wrap</a></span></dt><dt><span class="sect2"><a href="reference.html#wrap-search">3.306. wrap_search</a></span></dt><dt><span class="sect2"><a href="reference.html#wrapmargin">3.307. wrapmargin</a></span></dt><dt><span class="sect2"><a href="reference.html#write-inc">3.308. write_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#write-bcc">3.309. write_bcc</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-icon">3.310. xterm_icon</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-set-titles">3.311. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-title">3.312. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="reference.html#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="reference.html#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="reference.html#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="reference.html#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="reference.html#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="reference.html#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="reference.html#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="reference.html#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="reference.html#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="reference.html#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="reference.html#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="reference.html#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="reference.html#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="miscellany.html">9. Miscellany</a></span></dt><dd><dl><dt><span class="sect1"><a href="miscellany.html#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="miscellany.html#about">2. About this document</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1.1. <a href="intro.html#tab-typo">Typographical conventions for special terms</a></dt><dt>2.1. <a href="gettingstarted.html#tab-keys-nav">Most common navigation keys</a></dt><dt>2.2. <a href="gettingstarted.html#tab-keys-editor">Most common line editor keys</a></dt><dt>2.3. <a href="gettingstarted.html#tab-key-index">Most common message index keys</a></dt><dt>2.4. <a href="gettingstarted.html#tab-msg-status-flags">Message status flags</a></dt><dt>2.5. <a href="gettingstarted.html#tab-msg-recip-flags">Message recipient flags</a></dt><dt>2.6. <a href="gettingstarted.html#tab-key-pager">Most common pager keys</a></dt><dt>2.7. <a href="gettingstarted.html#tab-ansi-esc">ANSI escape sequences</a></dt><dt>2.8. <a href="gettingstarted.html#tab-color">Color sequences</a></dt><dt>2.9. <a href="gettingstarted.html#tab-key-threads">Most common thread mode keys</a></dt><dt>2.10. <a href="gettingstarted.html#tab-key-send">Most common mail sending keys</a></dt><dt>2.11. <a href="gettingstarted.html#tab-func-compose">Most common compose menu keys</a></dt><dt>2.12. <a href="gettingstarted.html#tab-pgp-menuflags">PGP key menu flags</a></dt><dt>3.1. <a href="configuration.html#tab-key-names">Symbolic key names</a></dt><dt>4.1. <a href="advancedusage.html#posix-regex-char-classes">POSIX regular expression character classes</a></dt><dt>4.2. <a href="advancedusage.html#regex-repeat">Regular expression repetition operators</a></dt><dt>4.3. <a href="advancedusage.html#regex-gnu-ext">GNU regular expression extensions</a></dt><dt>4.4. <a href="advancedusage.html#tab-patterns">Pattern modifiers</a></dt><dt>4.5. <a href="advancedusage.html#tab-simplesearch-keywords">Simple search keywords</a></dt><dt>4.6. <a href="advancedusage.html#tab-date-units">Date units</a></dt><dt>8.1. <a href="reference.html#tab-commandline-options">Command line options</a></dt><dt>8.2. <a href="reference.html#generic_table">Default generic function bindings</a></dt><dt>8.3. <a href="reference.html#index_table">Default index function bindings</a></dt><dt>8.4. <a href="reference.html#pager_table">Default pager function bindings</a></dt><dt>8.5. <a href="reference.html#alias_table">Default alias function bindings</a></dt><dt>8.6. <a href="reference.html#query_table">Default query function bindings</a></dt><dt>8.7. <a href="reference.html#attach_table">Default attach function bindings</a></dt><dt>8.8. <a href="reference.html#compose_table">Default compose function bindings</a></dt><dt>8.9. <a href="reference.html#postpone_table">Default postpone function bindings</a></dt><dt>8.10. <a href="reference.html#browser_table">Default browser function bindings</a></dt><dt>8.11. <a href="reference.html#pgp_table">Default pgp function bindings</a></dt><dt>8.12. <a href="reference.html#smime_table">Default smime function bindings</a></dt><dt>8.13. <a href="reference.html#mix_table">Default mix function bindings</a></dt><dt>8.14. <a href="reference.html#editor_table">Default editor function bindings</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>3.1. <a href="configuration.html#ex-rc-multiple-cmds">Multiple configuration commands per line</a></dt><dt>3.2. <a href="configuration.html#ex-ec-comment">Commenting configuration files</a></dt><dt>3.3. <a href="configuration.html#ex-rc-quote">Escaping quotes in congfiguration files</a></dt><dt>3.4. <a href="configuration.html#ex-rc-backtick">Using external command's output in configuration files</a></dt><dt>3.5. <a href="configuration.html#ex-rc-env">Using environment variables in configuration files</a></dt><dt>3.6. <a href="configuration.html#ex-alias-external">Configuring external alias files</a></dt><dt>3.7. <a href="configuration.html#ex-folder-sorting">Setting sort method based on mailbox name</a></dt><dt>3.8. <a href="configuration.html#ex-header-weeding">Header weeding</a></dt><dt>3.9. <a href="configuration.html#ex-hdr-order">Configuring header display order</a></dt><dt>3.10. <a href="configuration.html#ex-my-hdr">Defining custom headers</a></dt><dt>3.11. <a href="configuration.html#ex-save-hook-exando">Using %-expandos in <code class="literal">save-hook</code></a></dt><dt>3.12. <a href="configuration.html#ex-folder-hook-push">Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></a></dt><dt>3.13. <a href="configuration.html#ex-spam">Configuring spam detection</a></dt><dt>3.14. <a href="configuration.html#ex-myvar1">Using user-defined variables for config file readability</a></dt><dt>3.15. <a href="configuration.html#ex-myvar2">Using user-defined variables for backing up other config option values</a></dt><dt>3.16. <a href="configuration.html#ex-myvar3">Deferring user-defined variable expansion to runtime</a></dt><dt>3.17. <a href="configuration.html#ex-fmtpipe">Using external filters in format strings</a></dt><dt>4.1. <a href="advancedusage.html#ex-pattern-bool">Using boolean operators in patterns</a></dt><dt>4.2. <a href="advancedusage.html#ex-send-hook-my-hdr">Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></a></dt><dt>5.1. <a href="mimesupport.html#ex-attach-count">Attachment counting</a></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="compressedfolders"></a>1. Compressed folders Support (OPTIONAL)</h2></div></div></div><p>
-If Mutt was compiled with compressed folders support (by running the
-<span class="emphasis"><em>configure</em></span> script with the
-<span class="emphasis"><em>--enable-compressed</em></span> flag), Mutt can open folders
-stored in an arbitrary format, provided that the user has a script to
-convert from/to this format to one of the accepted.
-
-The most common use is to open compressed archived folders e.g. with
-gzip.
-
-In addition, the user can provide a script that gets a folder in an
-accepted format and appends its context to the folder in the
-user-defined format, which may be faster than converting the entire
-folder to the accepted format, appending to it and converting back to
-the user-defined format.
-
-There are three hooks defined (<a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a>, <a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> and <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>) which define commands to
-uncompress and compress a folder and to append messages to an existing
-compressed folder respectively.
-
-For example:
-
-</p><pre class="screen">
-open-hook \\.gz$ "gzip -cd %f > %t"
-close-hook \\.gz$ "gzip -c %t > %f"
-append-hook \\.gz$ "gzip -c %t >> %f"
-</pre><p>
-
-You do not have to specify all of the commands. If you omit <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>, the folder will be open and
-closed again each time you will add to it. If you omit <a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> (or give empty command) , the
-folder will be open in the mode. If you specify <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> though you'll be able to
-append to the folder.
-
-Note that Mutt 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
-<a class="link" href="reference.html#save-empty" title="3.252. save_empty">$save_empty</a>, so that
-the compressed file will be removed if you delete all of the messages.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="open-hook"></a>1.1. Open a compressed mailbox for reading</h3></div></div></div><p>
-Usage: <code class="literal">open-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-The <span class="emphasis"><em>command</em></span> is the command that can be used for
-opening the folders whose names match <span class="emphasis"><em>regexp</em></span>.
-
-The <span class="emphasis"><em>command</em></span> string is the printf-like format
-string, and it should accept two parameters: %f, which is
-replaced with the (compressed) folder name, and %t which is
-replaced with the name of the temporary folder to which to write.
-
-%f and %t can be repeated any number of times in the
-command string, and all of the entries are replaced with the
-appropriate folder name. In addition, %% is replaced by
-%, as in printf, and any other %anything is left as is.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the original compressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-open-hook \\.gz$ "gzip -cd %f > %t"
-</pre><p>
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="close-hook"></a>1.2. Write a compressed mailbox</h3></div></div></div><p>
-Usage: <code class="literal">close-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-This is used to close the folder that was open with the <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command after some changes were
-made to it.
-
-The <span class="emphasis"><em>command</em></span> string is the command that can be
-used for closing the folders whose names match
-<span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. Temporary folder in this
-case is the folder previously produced by the <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-close-hook \\.gz$ "gzip -c %t > %f"
-</pre><p>
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type, and the file can only be open in the
-read-only mode.
-
-<a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is not called when you
-exit from the folder if the folder was not changed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="append-hook"></a>1.3. Append a message to a compressed mailbox</h3></div></div></div><p>
-Usage: <code class="literal">append-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-This command is used for saving to an existing compressed folder. The
-<span class="emphasis"><em>command</em></span> is the command that can be used for
-appending to the folders whose names match
-<span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. The temporary folder in
-this case contains the messages that are being appended.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-append-hook \\.gz$ "gzip -c %t >> %f"
-</pre><p>
-
-When <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> 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 (<a class="link" href="reference.html#mbox-type" title="3.117. mbox_type">$mbox_type</a>) type is always
-supposed (i.e. this is the format used for the temporary folder).
-
-If the file does not exist when you save to it, <a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is called, and not <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>. <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> is only for appending to
-existing folders.
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type. In this case, the folder will be open and
-closed again (using <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> and
-<a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a>respectively) each time you
-will add to it.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id2954137"></a>1.4. Encrypted folders</h3></div></div></div><p>
-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 use
-the following hooks:
-
-</p><pre class="screen">
-open-hook \\.pgp$ "pgp -f < %f > %t"
-close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-</pre><p>
-
-Please note, that PGP does not support appending to an encrypted
-folder, so there is no append-hook defined.
-
-If you are using GnuPG instead of PGP, you may use the following hooks
-instead:
-
-</p><pre class="screen">
-open-hook \\.gpg$ "gpg --decrypt < %f > %t"
-close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
-</pre><p>
-
-<span class="bold"><strong>Note:</strong></span> the folder is temporary stored
-decrypted in the /tmp directory, where it can be read by your system
-administrator. So think about the security aspects of this.
-</p></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="intro.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html>
+++ /dev/null
-#!/bin/sh --
-
-prefix=/usr
-exec_prefix=${prefix}
-bindir=${exec_prefix}/bin
-libdir=${exec_prefix}/lib
-mandir=/usr/share/man
-srcdir=../../doc
-datarootdir=${prefix}/share
-docdir=/usr/share/doc
-includedir=${prefix}/include
-top_srcdir=../..
-top_builddir=..
-
-SOURCE="$1"
-TARGET="$2"
-
-
-rm -f "$TARGET"
-
-sed -e "s;/usr/local/bin/;$bindir/;g" \
- -e "s;/usr/local/doc/mutt/;$docdir/;g" \
- "$SOURCE" > $TARGET
-
-chmod 644 "$TARGET"
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Introduction</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="index.html" title="The Mutt E-Mail Client" /><link rel="next" href="gettingstarted.html" title="Chapter 2. Getting Started" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. Introduction</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="gettingstarted.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="intro.html#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="intro.html#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="intro.html#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="intro.html#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="intro.html#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="intro.html#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="intro.html#copyright">7. Copyright</a></span></dt></dl></div><p>
-<span class="bold"><strong>Mutt</strong></span> is a small but very powerful text-based MIME mail client. Mutt 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.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="homepage"></a>1. Mutt Home Page</h2></div></div></div><p>
-The official homepage can be found at
-<a class="ulink" href="http://www.mutt.org/" target="_top">http://www.mutt.org/</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttlists"></a>2. Mailing Lists</h2></div></div></div><p>
-To subscribe to one of the following mailing lists, send a message with the
-word <span class="emphasis"><em>subscribe</em></span> in the body to
-<code class="literal">list-name</code><span class="emphasis"><em>-request</em></span><code class="literal">@mutt.org</code>.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-announce-request@mutt.org">mutt-announce-request@mutt.org</a>></code> -- low traffic list for announcements
-</p></li><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-users-request@mutt.org">mutt-users-request@mutt.org</a>></code> -- help, bug reports and feature requests
-</p></li><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-dev-request@mutt.org">mutt-dev-request@mutt.org</a>></code> -- development mailing list
-</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
-All messages posted to
-<span class="emphasis"><em>mutt-announce</em></span> are automatically forwarded to
-<span class="emphasis"><em>mutt-users</em></span>, so you do not need to be subscribed to
-both lists.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="distribution"></a>3. Software Distribution Sites</h2></div></div></div><p>
-Mutt releases can be downloaded from
-<a class="ulink" href="ftp://ftp.mutt.org/mutt/" target="_top">ftp://ftp.mutt.org/mutt/</a>.
-For a list of mirror sites, please refer to
-<a class="ulink" href="http://www.mutt.org/download.html" target="_top">http://www.mutt.org/download.html</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="irc"></a>4. Mutt online resources</h2></div></div></div><div class="variablelist"><dl><dt><span class="term">Bug Tracking System</span></dt><dd><p>
-The official mutt bug tracking system can be found at
-<a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a>
-</p></dd><dt><span class="term">Wiki</span></dt><dd><p>
-An (unofficial) wiki can be found
-at <a class="ulink" href="http://wiki.mutt.org/" target="_top">http://wiki.mutt.org/</a>.
-</p></dd><dt><span class="term">IRC</span></dt><dd><p>
-For the IRC user community, visit channel <span class="emphasis"><em>#mutt</em></span> on
-<a class="ulink" href="http://www.freenode.net/" target="_top">irc.freenode.net</a>.
-</p></dd><dt><span class="term">USENET</span></dt><dd><p>
-For USENET, see the newsgroup <a class="ulink" href="news:comp.mail.mutt" target="_top">comp.mail.mutt</a>.
-</p></dd></dl></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="contrib"></a>5. Contributing to Mutt</h2></div></div></div><p>
-There are various ways to contribute to the Mutt project.
-</p><p>
-Especially for new users it may be helpful to meet other new and
-experienced users to chat about Mutt, talk about problems and share
-tricks.
-</p><p>
-Since translations of Mutt into other languages are highly appreciated,
-the mutt developers always look for skilled translators that help
-improve and continue to maintain stale translations.
-</p><p>
-For contributing code patches for new features and bug fixes, please
-refer to the developer pages at
-<a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a> for more details.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="typo"></a>6. Typograhical conventions</h2></div></div></div><p>
-This section lists typographical conventions followed throughout this
-manual. See table <a class="xref" href="intro.html#tab-typo" title="Table 1.1. Typographical conventions for special terms">Table 1.1, “Typographical conventions for special terms”</a> for typographical
-conventions for special terms.
-</p><div class="table"><a id="tab-typo"></a><p class="title"><b>Table 1.1. Typographical conventions for special terms</b></p><div class="table-contents"><table summary="Typographical conventions for special terms" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Item</th><th>Refers to...</th></tr></thead><tbody><tr><td><code class="literal">printf(3)</code></td><td>UNIX manual pages, execute <code class="literal">man 3 printf</code></td></tr><tr><td><code class="literal"><PageUp></code></td><td>named keys</td></tr><tr><td><code class="literal"><create-alias></code></td><td>named Mutt function</td></tr><tr><td><code class="literal">^G</code></td><td>Control+G key combination</td></tr><tr><td><code class="literal">$mail_check</code></td><td>Mutt configuration option</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Examples are presented as:
-</p><pre class="screen">
-mutt -v
-</pre><p>
-Within command synopsis, curly brackets (“<span class="quote">{}</span>”) denote a set
-of options of which one is mandatory, square brackets
-(“<span class="quote">[]</span>”) denote optional arguments, three dots
-denote that the argument may be repeated arbitrary times.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="copyright"></a>7. Copyright</h2></div></div></div><p>
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins
-<code class="email"><<a class="email" href="mailto:me@mutt.org">me@mutt.org</a>></code> and others.
-</p><p>
-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.
-</p><p>
-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.
-</p><p>
-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.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="gettingstarted.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">The Mutt E-Mail Client </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Getting Started</td></tr></table></div></body></html>
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Mutt E-Mail Client</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><meta name="description" content="All mail clients suck. This one just sucks less. -me, circa 1995" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="book" lang="en" xml:lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="id2473523"></a>The Mutt E-Mail Client</h1></div><div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Elkins</span></h3><code class="email"><<a class="email" href="mailto:me@cs.hmc.edu">me@cs.hmc.edu</a>></code></div></div><div><p class="releaseinfo">version 1.5.19 (2009-01-05)</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
-“<span class="quote">All mail clients suck. This one just sucks less.</span>” -me, circa 1995
-</p></div></div></div><hr /></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1. Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="#copyright">7. Copyright</a></span></dt></dl></dd><dt><span class="chapter"><a href="#gettingstarted">2. Getting Started</a></span></dt><dd><dl><dt><span class="sect1"><a href="#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="#postponing-mail">7. Postponing Mail</a></span></dt></dl></dd><dt><span class="chapter"><a href="#configuration">3. Configuration</a></span></dt><dd><dl><dt><span class="sect1"><a href="#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#advancedusage">4. Advanced Usage</a></span></dt><dd><dl><dt><span class="sect1"><a href="#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#mimesupport">5. Mutt's MIME Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="#mime-lookup">7. MIME Lookup</a></span></dt></dl></dd><dt><span class="chapter"><a href="#optionalfeatures">6. Optional features</a></span></dt><dd><dl><dt><span class="sect1"><a href="#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="#exact-address">8. Exact address generation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#tuning">7. Performance tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="#tuning-search">3. Searching and limiting</a></span></dt></dl></dd><dt><span class="chapter"><a href="#reference">8. Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="#sidebar-delim">3.150. sidebar_delim</a></span></dt><dt><span class="sect2"><a href="#sidebar-visible">3.151. sidebar_visible</a></span></dt><dt><span class="sect2"><a href="#sidebar-width">3.152. sidebar_width</a></span></dt><dt><span class="sect2"><a href="#pgp-use-gpg-agent">3.153. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="#crypt-verify-sig">3.154. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="#smime-is-default">3.155. smime_is_default</a></span></dt><dt><span class="sect2"><a href="#smime-ask-cert-label">3.156. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-use-default-key">3.157. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="#pgp-entry-format">3.158. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="#pgp-good-sign">3.159. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="#pgp-check-exit">3.160. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="#pgp-long-ids">3.161. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="#pgp-retainable-sigs">3.162. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="#pgp-autoinline">3.163. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="#pgp-replyinline">3.164. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="#pgp-show-unusable">3.165. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-as">3.166. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="#pgp-strict-enc">3.167. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="#pgp-timeout">3.168. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="#pgp-sort-keys">3.169. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-auto">3.170. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="#pgp-auto-decode">3.171. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-filename">3.172. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-description">3.173. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="#pgp-decode-command">3.174. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="#pgp-getkeys-command">3.175. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-command">3.176. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="#pgp-decrypt-command">3.177. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#pgp-clearsign-command">3.178. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-command">3.179. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-sign-command">3.180. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-only-command">3.181. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="#pgp-import-command">3.182. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="#pgp-export-command">3.183. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-key-command">3.184. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-secring-command">3.185. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-pubring-command">3.186. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="#forward-decrypt">3.187. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="#smime-timeout">3.188. smime_timeout</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-with">3.189. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="#smime-keys">3.190. smime_keys</a></span></dt><dt><span class="sect2"><a href="#smime-ca-location">3.191. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="#smime-certificates">3.192. smime_certificates</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-command">3.193. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-command">3.194. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-opaque-command">3.195. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-command">3.196. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-opaque-command">3.197. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-command">3.198. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-pk7out-command">3.199. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-command">3.200. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-signer-cert-command">3.201. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-import-cert-command">3.202. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-email-command">3.203. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="#smime-default-key">3.204. smime_default_key</a></span></dt><dt><span class="sect2"><a href="#ssl-client-cert">3.205. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="#ssl-force-tls">3.206. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="#ssl-starttls">3.207. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="#certificate-file">3.208. certificate_file</a></span></dt><dt><span class="sect2"><a href="#ssl-use-sslv3">3.209. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="#ssl-use-tlsv1">3.210. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="#ssl-min-dh-prime-bits">3.211. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="#ssl-ca-certificates-file">3.212. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="#pipe-split">3.213. pipe_split</a></span></dt><dt><span class="sect2"><a href="#pipe-decode">3.214. pipe_decode</a></span></dt><dt><span class="sect2"><a href="#pipe-sep">3.215. pipe_sep</a></span></dt><dt><span class="sect2"><a href="#pop-authenticators">3.216. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="#pop-auth-try-all">3.217. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="#pop-checkinterval">3.218. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="#pop-delete">3.219. pop_delete</a></span></dt><dt><span class="sect2"><a href="#pop-host">3.220. pop_host</a></span></dt><dt><span class="sect2"><a href="#pop-last">3.221. pop_last</a></span></dt><dt><span class="sect2"><a href="#pop-reconnect">3.222. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="#pop-user">3.223. pop_user</a></span></dt><dt><span class="sect2"><a href="#pop-pass">3.224. pop_pass</a></span></dt><dt><span class="sect2"><a href="#post-indent-string">3.225. post_indent_string</a></span></dt><dt><span class="sect2"><a href="#postpone">3.226. postpone</a></span></dt><dt><span class="sect2"><a href="#postponed">3.227. postponed</a></span></dt><dt><span class="sect2"><a href="#preconnect">3.228. preconnect</a></span></dt><dt><span class="sect2"><a href="#print">3.229. print</a></span></dt><dt><span class="sect2"><a href="#print-command">3.230. print_command</a></span></dt><dt><span class="sect2"><a href="#print-decode">3.231. print_decode</a></span></dt><dt><span class="sect2"><a href="#print-split">3.232. print_split</a></span></dt><dt><span class="sect2"><a href="#prompt-after">3.233. prompt_after</a></span></dt><dt><span class="sect2"><a href="#query-command">3.234. query_command</a></span></dt><dt><span class="sect2"><a href="#query-format">3.235. query_format</a></span></dt><dt><span class="sect2"><a href="#quit">3.236. quit</a></span></dt><dt><span class="sect2"><a href="#quote-regexp">3.237. quote_regexp</a></span></dt><dt><span class="sect2"><a href="#read-inc">3.238. read_inc</a></span></dt><dt><span class="sect2"><a href="#read-only">3.239. read_only</a></span></dt><dt><span class="sect2"><a href="#realname">3.240. realname</a></span></dt><dt><span class="sect2"><a href="#recall">3.241. recall</a></span></dt><dt><span class="sect2"><a href="#record">3.242. record</a></span></dt><dt><span class="sect2"><a href="#reply-regexp">3.243. reply_regexp</a></span></dt><dt><span class="sect2"><a href="#reply-self">3.244. reply_self</a></span></dt><dt><span class="sect2"><a href="#reply-to">3.245. reply_to</a></span></dt><dt><span class="sect2"><a href="#resolve">3.246. resolve</a></span></dt><dt><span class="sect2"><a href="#reverse-alias">3.247. reverse_alias</a></span></dt><dt><span class="sect2"><a href="#reverse-name">3.248. reverse_name</a></span></dt><dt><span class="sect2"><a href="#reverse-realname">3.249. reverse_realname</a></span></dt><dt><span class="sect2"><a href="#rfc2047-parameters">3.250. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="#save-address">3.251. save_address</a></span></dt><dt><span class="sect2"><a href="#save-empty">3.252. save_empty</a></span></dt><dt><span class="sect2"><a href="#save-history">3.253. save_history</a></span></dt><dt><span class="sect2"><a href="#save-name">3.254. save_name</a></span></dt><dt><span class="sect2"><a href="#score">3.255. score</a></span></dt><dt><span class="sect2"><a href="#score-threshold-delete">3.256. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="#score-threshold-flag">3.257. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="#score-threshold-read">3.258. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="#send-charset">3.259. send_charset</a></span></dt><dt><span class="sect2"><a href="#sendmail">3.260. sendmail</a></span></dt><dt><span class="sect2"><a href="#sendmail-wait">3.261. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="#shell">3.262. shell</a></span></dt><dt><span class="sect2"><a href="#sig-dashes">3.263. sig_dashes</a></span></dt><dt><span class="sect2"><a href="#sig-on-top">3.264. sig_on_top</a></span></dt><dt><span class="sect2"><a href="#signature">3.265. signature</a></span></dt><dt><span class="sect2"><a href="#simple-search">3.266. simple_search</a></span></dt><dt><span class="sect2"><a href="#smart-wrap">3.267. smart_wrap</a></span></dt><dt><span class="sect2"><a href="#smileys">3.268. smileys</a></span></dt><dt><span class="sect2"><a href="#sleep-time">3.269. sleep_time</a></span></dt><dt><span class="sect2"><a href="#smtp-authenticators">3.270. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="#smtp-pass">3.271. smtp_pass</a></span></dt><dt><span class="sect2"><a href="#smtp-url">3.272. smtp_url</a></span></dt><dt><span class="sect2"><a href="#sort">3.273. sort</a></span></dt><dt><span class="sect2"><a href="#sort-alias">3.274. sort_alias</a></span></dt><dt><span class="sect2"><a href="#sort-aux">3.275. sort_aux</a></span></dt><dt><span class="sect2"><a href="#sort-browser">3.276. sort_browser</a></span></dt><dt><span class="sect2"><a href="#sort-re">3.277. sort_re</a></span></dt><dt><span class="sect2"><a href="#spam-separator">3.278. spam_separator</a></span></dt><dt><span class="sect2"><a href="#spoolfile">3.279. spoolfile</a></span></dt><dt><span class="sect2"><a href="#status-chars">3.280. status_chars</a></span></dt><dt><span class="sect2"><a href="#status-format">3.281. status_format</a></span></dt><dt><span class="sect2"><a href="#status-on-top">3.282. status_on_top</a></span></dt><dt><span class="sect2"><a href="#strict-threads">3.283. strict_threads</a></span></dt><dt><span class="sect2"><a href="#suspend">3.284. suspend</a></span></dt><dt><span class="sect2"><a href="#text-flowed">3.285. text_flowed</a></span></dt><dt><span class="sect2"><a href="#thread-received">3.286. thread_received</a></span></dt><dt><span class="sect2"><a href="#thorough-search">3.287. thorough_search</a></span></dt><dt><span class="sect2"><a href="#tilde">3.288. tilde</a></span></dt><dt><span class="sect2"><a href="#time-inc">3.289. time_inc</a></span></dt><dt><span class="sect2"><a href="#timeout">3.290. timeout</a></span></dt><dt><span class="sect2"><a href="#tmpdir">3.291. tmpdir</a></span></dt><dt><span class="sect2"><a href="#to-chars">3.292. to_chars</a></span></dt><dt><span class="sect2"><a href="#trash">3.293. trash</a></span></dt><dt><span class="sect2"><a href="#tunnel">3.294. tunnel</a></span></dt><dt><span class="sect2"><a href="#use-8bitmime">3.295. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="#use-domain">3.296. use_domain</a></span></dt><dt><span class="sect2"><a href="#use-envelope-from">3.297. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="#use-from">3.298. use_from</a></span></dt><dt><span class="sect2"><a href="#use-idn">3.299. use_idn</a></span></dt><dt><span class="sect2"><a href="#use-ipv6">3.300. use_ipv6</a></span></dt><dt><span class="sect2"><a href="#user-agent">3.301. user_agent</a></span></dt><dt><span class="sect2"><a href="#visual">3.302. visual</a></span></dt><dt><span class="sect2"><a href="#wait-key">3.303. wait_key</a></span></dt><dt><span class="sect2"><a href="#weed">3.304. weed</a></span></dt><dt><span class="sect2"><a href="#wrap">3.305. wrap</a></span></dt><dt><span class="sect2"><a href="#wrap-search">3.306. wrap_search</a></span></dt><dt><span class="sect2"><a href="#wrapmargin">3.307. wrapmargin</a></span></dt><dt><span class="sect2"><a href="#write-inc">3.308. write_inc</a></span></dt><dt><span class="sect2"><a href="#write-bcc">3.309. write_bcc</a></span></dt><dt><span class="sect2"><a href="#xterm-icon">3.310. xterm_icon</a></span></dt><dt><span class="sect2"><a href="#xterm-set-titles">3.311. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="#xterm-title">3.312. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#miscellany">9. Miscellany</a></span></dt><dd><dl><dt><span class="sect1"><a href="#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="#about">2. About this document</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1.1. <a href="#tab-typo">Typographical conventions for special terms</a></dt><dt>2.1. <a href="#tab-keys-nav">Most common navigation keys</a></dt><dt>2.2. <a href="#tab-keys-editor">Most common line editor keys</a></dt><dt>2.3. <a href="#tab-key-index">Most common message index keys</a></dt><dt>2.4. <a href="#tab-msg-status-flags">Message status flags</a></dt><dt>2.5. <a href="#tab-msg-recip-flags">Message recipient flags</a></dt><dt>2.6. <a href="#tab-key-pager">Most common pager keys</a></dt><dt>2.7. <a href="#tab-ansi-esc">ANSI escape sequences</a></dt><dt>2.8. <a href="#tab-color">Color sequences</a></dt><dt>2.9. <a href="#tab-key-threads">Most common thread mode keys</a></dt><dt>2.10. <a href="#tab-key-send">Most common mail sending keys</a></dt><dt>2.11. <a href="#tab-func-compose">Most common compose menu keys</a></dt><dt>2.12. <a href="#tab-pgp-menuflags">PGP key menu flags</a></dt><dt>3.1. <a href="#tab-key-names">Symbolic key names</a></dt><dt>4.1. <a href="#posix-regex-char-classes">POSIX regular expression character classes</a></dt><dt>4.2. <a href="#regex-repeat">Regular expression repetition operators</a></dt><dt>4.3. <a href="#regex-gnu-ext">GNU regular expression extensions</a></dt><dt>4.4. <a href="#tab-patterns">Pattern modifiers</a></dt><dt>4.5. <a href="#tab-simplesearch-keywords">Simple search keywords</a></dt><dt>4.6. <a href="#tab-date-units">Date units</a></dt><dt>8.1. <a href="#tab-commandline-options">Command line options</a></dt><dt>8.2. <a href="#generic_table">Default generic function bindings</a></dt><dt>8.3. <a href="#index_table">Default index function bindings</a></dt><dt>8.4. <a href="#pager_table">Default pager function bindings</a></dt><dt>8.5. <a href="#alias_table">Default alias function bindings</a></dt><dt>8.6. <a href="#query_table">Default query function bindings</a></dt><dt>8.7. <a href="#attach_table">Default attach function bindings</a></dt><dt>8.8. <a href="#compose_table">Default compose function bindings</a></dt><dt>8.9. <a href="#postpone_table">Default postpone function bindings</a></dt><dt>8.10. <a href="#browser_table">Default browser function bindings</a></dt><dt>8.11. <a href="#pgp_table">Default pgp function bindings</a></dt><dt>8.12. <a href="#smime_table">Default smime function bindings</a></dt><dt>8.13. <a href="#mix_table">Default mix function bindings</a></dt><dt>8.14. <a href="#editor_table">Default editor function bindings</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>3.1. <a href="#ex-rc-multiple-cmds">Multiple configuration commands per line</a></dt><dt>3.2. <a href="#ex-ec-comment">Commenting configuration files</a></dt><dt>3.3. <a href="#ex-rc-quote">Escaping quotes in congfiguration files</a></dt><dt>3.4. <a href="#ex-rc-backtick">Using external command's output in configuration files</a></dt><dt>3.5. <a href="#ex-rc-env">Using environment variables in configuration files</a></dt><dt>3.6. <a href="#ex-alias-external">Configuring external alias files</a></dt><dt>3.7. <a href="#ex-folder-sorting">Setting sort method based on mailbox name</a></dt><dt>3.8. <a href="#ex-header-weeding">Header weeding</a></dt><dt>3.9. <a href="#ex-hdr-order">Configuring header display order</a></dt><dt>3.10. <a href="#ex-my-hdr">Defining custom headers</a></dt><dt>3.11. <a href="#ex-save-hook-exando">Using %-expandos in <code class="literal">save-hook</code></a></dt><dt>3.12. <a href="#ex-folder-hook-push">Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></a></dt><dt>3.13. <a href="#ex-spam">Configuring spam detection</a></dt><dt>3.14. <a href="#ex-myvar1">Using user-defined variables for config file readability</a></dt><dt>3.15. <a href="#ex-myvar2">Using user-defined variables for backing up other config option values</a></dt><dt>3.16. <a href="#ex-myvar3">Deferring user-defined variable expansion to runtime</a></dt><dt>3.17. <a href="#ex-fmtpipe">Using external filters in format strings</a></dt><dt>4.1. <a href="#ex-pattern-bool">Using boolean operators in patterns</a></dt><dt>4.2. <a href="#ex-send-hook-my-hdr">Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></a></dt><dt>5.1. <a href="#ex-attach-count">Attachment counting</a></dt></dl></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="#copyright">7. Copyright</a></span></dt></dl></div><p>
-<span class="bold"><strong>Mutt</strong></span> is a small but very powerful text-based MIME mail client. Mutt 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.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="homepage"></a>1. Mutt Home Page</h2></div></div></div><p>
-The official homepage can be found at
-<a class="ulink" href="http://www.mutt.org/" target="_top">http://www.mutt.org/</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttlists"></a>2. Mailing Lists</h2></div></div></div><p>
-To subscribe to one of the following mailing lists, send a message with the
-word <span class="emphasis"><em>subscribe</em></span> in the body to
-<code class="literal">list-name</code><span class="emphasis"><em>-request</em></span><code class="literal">@mutt.org</code>.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-announce-request@mutt.org">mutt-announce-request@mutt.org</a>></code> -- low traffic list for announcements
-</p></li><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-users-request@mutt.org">mutt-users-request@mutt.org</a>></code> -- help, bug reports and feature requests
-</p></li><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-dev-request@mutt.org">mutt-dev-request@mutt.org</a>></code> -- development mailing list
-</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
-All messages posted to
-<span class="emphasis"><em>mutt-announce</em></span> are automatically forwarded to
-<span class="emphasis"><em>mutt-users</em></span>, so you do not need to be subscribed to
-both lists.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="distribution"></a>3. Software Distribution Sites</h2></div></div></div><p>
-Mutt releases can be downloaded from
-<a class="ulink" href="ftp://ftp.mutt.org/mutt/" target="_top">ftp://ftp.mutt.org/mutt/</a>.
-For a list of mirror sites, please refer to
-<a class="ulink" href="http://www.mutt.org/download.html" target="_top">http://www.mutt.org/download.html</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="irc"></a>4. Mutt online resources</h2></div></div></div><div class="variablelist"><dl><dt><span class="term">Bug Tracking System</span></dt><dd><p>
-The official mutt bug tracking system can be found at
-<a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a>
-</p></dd><dt><span class="term">Wiki</span></dt><dd><p>
-An (unofficial) wiki can be found
-at <a class="ulink" href="http://wiki.mutt.org/" target="_top">http://wiki.mutt.org/</a>.
-</p></dd><dt><span class="term">IRC</span></dt><dd><p>
-For the IRC user community, visit channel <span class="emphasis"><em>#mutt</em></span> on
-<a class="ulink" href="http://www.freenode.net/" target="_top">irc.freenode.net</a>.
-</p></dd><dt><span class="term">USENET</span></dt><dd><p>
-For USENET, see the newsgroup <a class="ulink" href="news:comp.mail.mutt" target="_top">comp.mail.mutt</a>.
-</p></dd></dl></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="contrib"></a>5. Contributing to Mutt</h2></div></div></div><p>
-There are various ways to contribute to the Mutt project.
-</p><p>
-Especially for new users it may be helpful to meet other new and
-experienced users to chat about Mutt, talk about problems and share
-tricks.
-</p><p>
-Since translations of Mutt into other languages are highly appreciated,
-the mutt developers always look for skilled translators that help
-improve and continue to maintain stale translations.
-</p><p>
-For contributing code patches for new features and bug fixes, please
-refer to the developer pages at
-<a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a> for more details.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="typo"></a>6. Typograhical conventions</h2></div></div></div><p>
-This section lists typographical conventions followed throughout this
-manual. See table <a class="xref" href="#tab-typo" title="Table 1.1. Typographical conventions for special terms">Table 1.1, “Typographical conventions for special terms”</a> for typographical
-conventions for special terms.
-</p><div class="table"><a id="tab-typo"></a><p class="title"><b>Table 1.1. Typographical conventions for special terms</b></p><div class="table-contents"><table summary="Typographical conventions for special terms" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Item</th><th>Refers to...</th></tr></thead><tbody><tr><td><code class="literal">printf(3)</code></td><td>UNIX manual pages, execute <code class="literal">man 3 printf</code></td></tr><tr><td><code class="literal"><PageUp></code></td><td>named keys</td></tr><tr><td><code class="literal"><create-alias></code></td><td>named Mutt function</td></tr><tr><td><code class="literal">^G</code></td><td>Control+G key combination</td></tr><tr><td><code class="literal">$mail_check</code></td><td>Mutt configuration option</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Examples are presented as:
-</p><pre class="screen">
-mutt -v
-</pre><p>
-Within command synopsis, curly brackets (“<span class="quote">{}</span>”) denote a set
-of options of which one is mandatory, square brackets
-(“<span class="quote">[]</span>”) denote optional arguments, three dots
-denote that the argument may be repeated arbitrary times.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="copyright"></a>7. Copyright</h2></div></div></div><p>
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins
-<code class="email"><<a class="email" href="mailto:me@mutt.org">me@mutt.org</a>></code> and others.
-</p><p>
-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.
-</p><p>
-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.
-</p><p>
-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.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="gettingstarted"></a>Chapter 2. Getting Started</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="#postponing-mail">7. Postponing Mail</a></span></dt></dl></div><p>
-This section is intended as a brief overview of how to use Mutt. There are
-many other features which are described elsewhere in the manual. There
-is even more information available in the Mutt FAQ and various web
-pages. See the <a class="ulink" href="http://www.mutt.org/" target="_top">Mutt homepage</a> for more details.
-</p><p>
-The keybindings described in this section are the defaults as distributed.
-Your local system administrator may have altered the defaults for your site.
-You can always type “<span class="quote">?</span>” in any menu to display the current bindings.
-</p><p>
-The first thing you need to do is invoke mutt, simply by typing <code class="literal">mutt</code>
-at the command line. There are various command-line options, see
-either the mutt man page or the <a class="link" href="#commandline" title="1. Command line options">reference</a>.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="core-concepts"></a>1. Core concepts</h2></div></div></div><p>
-Mutt is a text-based application which interacts with users through
-different menus which are mostly line-/entry-based or page-based. A
-line-based menu is the so-called “<span class="quote">index</span>” menu (listing all messages of
-the currently opened folder) or the “<span class="quote">alias</span>” menu (allowing you to
-select recipients from a list). Examples for page-based menus are the
-“<span class="quote">pager</span>” (showing one message at a time) or the “<span class="quote">help</span>” menu listing
-all available key bindings.
-</p><p>
-The user interface consists of a context sensitive help line at the top,
-the menu's contents followed by a context sensitive status line and
-finally the command line. The command line is used to display
-informational and error messages as well as for prompts and for entering
-interactive commands.
-</p><p>
-Because Mutt allows for customizing almost all key bindings, there are
-so-called “<span class="quote">functions</span>” which can be executed manually (using the
-command line) or in macros. Macros allow the user to bind a sequence of
-commands to a single key or a short key sequence instead of repeating a
-sequence of actions over and over.
-</p><p>
-Many commands (such as saving or copying a message to another folder)
-can be applied to a single message or a set of messages (so-called
-“<span class="quote">tagged</span>” messages). To help selecting messages, Mutt provides a rich
-set of message patterns (such as recipients, sender, body contents, date
-sent/received, etc.) which can be combined into complex expressions
-using the boolean <span class="emphasis"><em>and</em></span> and <span class="emphasis"><em>or</em></span>
-operations as well as negating. These patterns can also be used to (for
-example) search for messages or to limit the index to show only matching
-messages.
-</p><p>
-Mutt supports a “<span class="quote">hook</span>” concept which allows the user to execute
-arbitrary configuration commands and functions in certain situations
-such as entering a folder, starting a new message or replying to an
-existing one. These hooks can be used to highly customize Mutt's
-behaviour including managing multiple identities, customizing the
-display for a folder or even implementing auto-archiving based on a
-per-folder basis and much more.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="menus"></a>2. Moving Around in Menus</h2></div></div></div><p>
-The most important navigation keys common to all menus are shown in
-<a class="xref" href="#tab-keys-nav" title="Table 2.1. Most common navigation keys">Table 2.1, “Most common navigation keys”</a>.
-</p><div class="table"><a id="tab-keys-nav"></a><p class="title"><b>Table 2.1. Most common navigation keys</b></p><div class="table-contents"><table summary="Most common navigation keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>j or <Down></td><td><code class="literal"><next-entry></code></td><td>move to the next entry</td></tr><tr><td>k or <Up></td><td><code class="literal"><previous-entry></code></td><td>move to the previous entry</td></tr><tr><td>z or <PageDn></td><td><code class="literal"><page-down></code></td><td>go to the next page</td></tr><tr><td>Z or <PageUp></td><td><code class="literal"><page-up></code></td><td>go to the previous page</td></tr><tr><td>= or <Home></td><td><code class="literal"><first-entry></code></td><td>jump to the first entry</td></tr><tr><td>* or <End></td><td><code class="literal"><last-entry></code></td><td>jump to the last entry</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>exit the current menu</td></tr><tr><td>?</td><td><code class="literal"><help></code></td><td>list all keybindings for the current menu</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing"></a>3. Editing Input Fields</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-intro"></a>3.1. Introduction</h3></div></div></div><p>
-Mutt has a built-in line editor for inputting text, e.g. email
-addresses or filenames. The keys used to manipulate text input are
-very similar to those of Emacs. See <a class="xref" href="#tab-keys-editor" title="Table 2.2. Most common line editor keys">Table 2.2, “Most common line editor keys”</a> for a full
-reference of available functions, their default key bindings, and
-short descriptions.
-</p><div class="table"><a id="tab-keys-editor"></a><p class="title"><b>Table 2.2. Most common line editor keys</b></p><div class="table-contents"><table summary="Most common line editor keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^A or <Home></td><td><code class="literal"><bol></code></td><td>move to the start of the line</td></tr><tr><td>^B or <Left></td><td><code class="literal"><backward-char></code></td><td>move back one char</td></tr><tr><td>Esc B</td><td><code class="literal"><backward-word></code></td><td>move back one word</td></tr><tr><td>^D or <Delete></td><td><code class="literal"><delete-char></code></td><td>delete the char under the cursor</td></tr><tr><td>^E or <End></td><td><code class="literal"><eol></code></td><td>move to the end of the line</td></tr><tr><td>^F or <Right></td><td><code class="literal"><forward-char></code></td><td>move forward one char</td></tr><tr><td>Esc F</td><td><code class="literal"><forward-word></code></td><td>move forward one word</td></tr><tr><td><Tab></td><td><code class="literal"><complete></code></td><td>complete filename or alias</td></tr><tr><td>^T</td><td><code class="literal"><complete-query></code></td><td>complete address with query</td></tr><tr><td>^K</td><td><code class="literal"><kill-eol></code></td><td>delete to the end of the line</td></tr><tr><td>Esc d</td><td><code class="literal"><kill-eow></code></td><td>delete to the end of the word</td></tr><tr><td>^W</td><td><code class="literal"><kill-word></code></td><td>kill the word in front of the cursor</td></tr><tr><td>^U</td><td><code class="literal"><kill-line></code></td><td>delete entire line</td></tr><tr><td>^V</td><td><code class="literal"><quote-char></code></td><td>quote the next typed key</td></tr><tr><td><Up></td><td><code class="literal"><history-up></code></td><td>recall previous string from history</td></tr><tr><td><Down></td><td><code class="literal"><history-down></code></td><td>recall next string from history</td></tr><tr><td><BackSpace></td><td><code class="literal"><backspace></code></td><td>kill the char in front of the cursor</td></tr><tr><td>Esc u</td><td><code class="literal"><upcase-word></code></td><td>convert word to upper case</td></tr><tr><td>Esc l</td><td><code class="literal"><downcase-word></code></td><td>convert word to lower case</td></tr><tr><td>Esc c</td><td><code class="literal"><capitalize-word></code></td><td>capitalize the word</td></tr><tr><td>^G</td><td>n/a</td><td>abort</td></tr><tr><td><Return></td><td>n/a</td><td>finish editing</td></tr></tbody></table></div></div><br class="table-break" /><p>
-You can remap the <span class="emphasis"><em>editor</em></span> functions using the
-<a class="link" href="#bind" title="5. Changing the default key bindings">bind</a> command. For example, to make
-the <Delete> key delete the character in front of
-the cursor rather than under, you could use:
-</p><pre class="screen">
-bind editor <delete> backspace
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-history"></a>3.2. History</h3></div></div></div><p>
-Mutt maintains a history for the built-in editor. The number of items
-is controlled by the <a class="link" href="#history" title="3.77. history">$history</a>
-variable and can be made persistent using an external file specified
-using <a class="link" href="#history-file" title="3.78. history_file">$history_file</a>.
-You may cycle through them at an editor prompt by using the
-<code class="literal"><history-up></code> and/or
-<code class="literal"><history-down></code> commands.
-</p><p>
-Mutt maintains several distinct history lists, one for each of the
-following categories:
-</p><div class="itemizedlist"><ul type="disc"><li><p>muttrc commands</p></li><li><p>addresses and aliases</p></li><li><p>shell commands</p></li><li><p>filenames</p></li><li><p>patterns</p></li><li><p>everything else</p></li></ul></div><p>
-Mutt automatically filters out repeated items from the history. It
-also mimics the behavior of some shells by ignoring items starting
-with a space. The latter feature can be useful in macros to not clobber
-the history's valuable entries with unwanted entries.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="reading"></a>4. Reading Mail - The Index and Pager</h2></div></div></div><p>
-Similar to many other mail clients, there are two modes in which mail is
-read in Mutt. The first is the index of messages in the mailbox, which is
-called the “<span class="quote">index</span>” in Mutt. The second mode is the display of the
-message contents. This is called the “<span class="quote">pager.</span>”
-</p><p>
-The next few sections describe the functions provided in each of these
-modes.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-menu"></a>4.1. The Message Index</h3></div></div></div><p>
-Common keys used to navigate through and manage messages in the index
-are shown in <a class="xref" href="#tab-key-index" title="Table 2.3. Most common message index keys">Table 2.3, “Most common message index keys”</a>. How messages are presented
-in the index menu can be customized using the
-<a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable.
-</p><div class="table"><a id="tab-key-index"></a><p class="title"><b>Table 2.3. Most common message index keys</b></p><div class="table-contents"><table summary="Most common message index keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td>c</td><td>change to a different mailbox</td></tr><tr><td>Esc c</td><td>change to a folder in read-only mode</td></tr><tr><td>C</td><td>copy the current message to another mailbox</td></tr><tr><td>Esc C</td><td>decode a message and copy it to a folder</td></tr><tr><td>Esc s</td><td>decode a message and save it to a folder</td></tr><tr><td>D</td><td>delete messages matching a pattern</td></tr><tr><td>d</td><td>delete the current message</td></tr><tr><td>F</td><td>mark as important</td></tr><tr><td>l</td><td>show messages matching a pattern</td></tr><tr><td>N</td><td>mark message as new</td></tr><tr><td>o</td><td>change the current sort method</td></tr><tr><td>O</td><td>reverse sort the mailbox</td></tr><tr><td>q</td><td>save changes and exit</td></tr><tr><td>s</td><td>save-message</td></tr><tr><td>T</td><td>tag messages matching a pattern</td></tr><tr><td>t</td><td>toggle the tag on a message</td></tr><tr><td>Esc t</td><td>toggle tag on entire message thread</td></tr><tr><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td>u</td><td>undelete-message</td></tr><tr><td>v</td><td>view-attachments</td></tr><tr><td>x</td><td>abort changes and exit</td></tr><tr><td><Return></td><td>display-message</td></tr><tr><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td>@</td><td>show the author's full e-mail address</td></tr><tr><td>$</td><td>save changes to mailbox</td></tr><tr><td>/</td><td>search</td></tr><tr><td>Esc /</td><td>search-reverse</td></tr><tr><td>^L</td><td>clear and redraw the screen</td></tr><tr><td>^T</td><td>untag messages matching a pattern</td></tr></tbody></table></div></div><br class="table-break" /><p>
-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 “<span class="quote">flags</span>” in <a class="xref" href="#tab-msg-status-flags" title="Table 2.4. Message status flags">Table 2.4, “Message status flags”</a>
-may appear, some of which can be turned on or off using these functions:
-<code class="literal"><set-flag></code> and
-<code class="literal"><clear-flag></code>
-bound by default to “<span class="quote">w</span>” and “<span class="quote">W</span>” respectively.
-</p><p>
-Furthermore, the flags in <a class="xref" href="#tab-msg-recip-flags" title="Table 2.5. Message recipient flags">Table 2.5, “Message recipient flags”</a> reflect
-who the message is addressed to. They can be customized with the
-<a class="link" href="#to-chars" title="3.292. to_chars">$to_chars</a> variable.
-</p><div class="table"><a id="tab-msg-status-flags"></a><p class="title"><b>Table 2.4. Message status flags</b></p><div class="table-contents"><table summary="Message status flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>D</td><td>message is deleted (is marked for deletion)</td></tr><tr><td>d</td><td>message has attachments marked for deletion</td></tr><tr><td>K</td><td>contains a PGP public key</td></tr><tr><td>N</td><td>message is new</td></tr><tr><td>O</td><td>message is old</td></tr><tr><td>P</td><td>message is PGP encrypted</td></tr><tr><td>r</td><td>message has been replied to</td></tr><tr><td>S</td><td>message is signed, and the signature is successfully verified</td></tr><tr><td>s</td><td>message is signed</td></tr><tr><td>!</td><td>message is flagged</td></tr><tr><td>*</td><td>message is tagged</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-msg-recip-flags"></a><p class="title"><b>Table 2.5. Message recipient flags</b></p><div class="table-contents"><table summary="Message recipient flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>+</td><td>message is to you and you only</td></tr><tr><td>T</td><td>message is to you, but also to or cc'ed to others</td></tr><tr><td>C</td><td>message is cc'ed to you</td></tr><tr><td>F</td><td>message is from you</td></tr><tr><td>L</td><td>message is sent to a subscribed mailing list</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-menu"></a>4.2. The Pager</h3></div></div></div><p>
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program <span class="emphasis"><em>less</em></span> though not nearly as
-featureful.
-</p><div class="table"><a id="tab-key-pager"></a><p class="title"><b>Table 2.6. Most common pager keys</b></p><div class="table-contents"><table summary="Most common pager keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td><Return></td><td>go down one line</td></tr><tr><td><Space></td><td>display the next page (or next message if at the end of a message)</td></tr><tr><td>-</td><td>go back to the previous page</td></tr><tr><td>n</td><td>search for next match</td></tr><tr><td>S</td><td>skip beyond quoted text</td></tr><tr><td>T</td><td>toggle display of quoted text</td></tr><tr><td>?</td><td>show keybindings</td></tr><tr><td>/</td><td>regular expression search</td></tr><tr><td>Esc /</td><td>backward regular expression search</td></tr><tr><td>\</td><td>toggle highlighting of search matches</td></tr><tr><td>^</td><td>jump to the top of the message</td></tr></tbody></table></div></div><br class="table-break" /><p>
-In addition to key bindings in <a class="xref" href="#tab-key-pager" title="Table 2.6. Most common pager keys">Table 2.6, “Most common pager keys”</a>,
-many of the functions from the index menu are also available in
-the pager, such as <code class="literal"><delete-message></code> or <code class="literal"><copy-message></code>
-(this is one advantage over using an external pager to view messages).
-</p><p>
-Also, the internal pager supports a couple other advanced features. For
-one, it will accept and translate the “<span class="quote">standard</span>” nroff sequences for
-bold and underline. These sequences are a series of either the letter,
-backspace (^H), the letter again for bold or the letter, backspace,
-“<span class="quote">_</span>” for denoting underline. Mutt will attempt to display these
-in bold and underline respectively if your terminal supports them. If
-not, you can use the bold and underline <a class="link" href="#color" title="9. Using color and mono video attributes">color</a>
-objects to specify a color or mono attribute for them.
-</p><p>
-Additionally, the internal pager supports the ANSI escape sequences for
-character attributes. Mutt translates them into the correct color and
-character settings. The sequences Mutt supports are:
-</p><pre class="screen">
-\e[<span class="emphasis"><em>Ps</em></span>;<span class="emphasis"><em>Ps</em></span>;..<span class="emphasis"><em>Ps</em></span>;m
-</pre><p>
-where <span class="emphasis"><em>Ps</em></span> can be one of the codes shown in
-<a class="xref" href="#tab-ansi-esc" title="Table 2.7. ANSI escape sequences">Table 2.7, “ANSI escape sequences”</a>.
-</p><div class="table"><a id="tab-ansi-esc"></a><p class="title"><b>Table 2.7. ANSI escape sequences</b></p><div class="table-contents"><table summary="ANSI escape sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Escape code</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>All attributes off</td></tr><tr><td>1</td><td>Bold on</td></tr><tr><td>4</td><td>Underline on</td></tr><tr><td>5</td><td>Blink on</td></tr><tr><td>7</td><td>Reverse video on</td></tr><tr><td>3<span class="emphasis"><em><color></em></span></td><td>Foreground color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr><tr><td>4<span class="emphasis"><em><color></em></span></td><td>Background color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-color"></a><p class="title"><b>Table 2.8. Color sequences</b></p><div class="table-contents"><table summary="Color sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Color code</th><th>Color</th></tr></thead><tbody><tr><td>0</td><td>Black</td></tr><tr><td>1</td><td>Red</td></tr><tr><td>2</td><td>Green</td></tr><tr><td>3</td><td>Yellow</td></tr><tr><td>4</td><td>Blue</td></tr><tr><td>5</td><td>Magenta</td></tr><tr><td>6</td><td>Cyan</td></tr><tr><td>7</td><td>White</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Mutt uses these attributes for handling <code class="literal">text/enriched</code>
-messages, and they can also be used by an external
-<a class="link" href="#auto-view" title="4. MIME Autoview">autoview</a> script for highlighting
-purposes.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-Note that the search commands in the pager take regular expressions,
-which are not quite the same as the more
-complex <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> used by the search
-command in the index. This is because the pager only performs simple
-text search, whereas the index provides boolean filtering on several
-aspects of messages.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="threads"></a>4.3. Threaded Mode</h3></div></div></div><p>
-When the mailbox is <a class="link" href="#sort" title="3.273. sort">sorted</a> by <span class="emphasis"><em>threads</em></span>, there are
-a few additional functions available in the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> modes
-as shown in <a class="xref" href="#tab-key-threads" title="Table 2.9. Most common thread mode keys">Table 2.9, “Most common thread mode keys”</a>.
-</p><div class="table"><a id="tab-key-threads"></a><p class="title"><b>Table 2.9. Most common thread mode keys</b></p><div class="table-contents"><table summary="Most common thread mode keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^D</td><td><code class="literal"><delete-thread></code></td><td>delete all messages in the current thread</td></tr><tr><td>^U</td><td><code class="literal"><undelete-thread></code></td><td>undelete all messages in the current thread</td></tr><tr><td>^N</td><td><code class="literal"><next-thread></code></td><td>jump to the start of the next thread</td></tr><tr><td>^P</td><td><code class="literal"><previous-thread></code></td><td>jump to the start of the previous thread</td></tr><tr><td>^R</td><td><code class="literal"><read-thread></code></td><td>mark the current thread as read</td></tr><tr><td>Esc d</td><td><code class="literal"><delete-subthread></code></td><td>delete all messages in the current subthread</td></tr><tr><td>Esc u</td><td><code class="literal"><undelete-subthread></code></td><td>undelete all messages in the current subthread</td></tr><tr><td>Esc n</td><td><code class="literal"><next-subthread></code></td><td>jump to the start of the next subthread</td></tr><tr><td>Esc p</td><td><code class="literal"><previous-subthread></code></td><td>jump to the start of the previous subthread</td></tr><tr><td>Esc r</td><td><code class="literal"><read-subthread></code></td><td>mark the current subthread as read</td></tr><tr><td>Esc t</td><td><code class="literal"><tag-thread></code></td><td>toggle the tag on the current thread</td></tr><tr><td>Esc v</td><td><code class="literal"><collapse-thread></code></td><td>toggle collapse for the current thread</td></tr><tr><td>Esc V</td><td><code class="literal"><collapse-all></code></td><td>toggle collapse for all threads</td></tr><tr><td>P</td><td><code class="literal"><parent-message></code></td><td>jump to parent message in thread</td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><h3 class="title">Note</h3><p>
-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 on
-the screen. See %M in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
-For example, you could use "%?M?(#%03M)&(%4l)?" in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to optionally
-display the number of hidden messages if the thread is collapsed.
-</p></div><p>
-See also: <a class="link" href="#strict-threads" title="3.283. strict_threads">$strict_threads</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reading-misc"></a>4.4. Miscellaneous Functions</h3></div></div></div><p>
-In addition, the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span>
-menus have these interesting functions:
-</p><div class="variablelist"><dl><dt><span class="term">
-<code class="literal"><create-alias></code><a id="create-alias"></a> (default: a)
-</span></dt><dd><p>
-Creates a new alias based upon the current message (or prompts for a
-new one). Once editing is complete, an <a class="link" href="#alias" title="4. Defining/Using aliases">alias</a>
-command is added to the file specified by
-the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> variable
-for future use
-</p><div class="note"><h3 class="title">Note</h3><p>
-Mutt does not read the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a>
-upon startup so you must explicitly <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> the file.
-</p></div></dd><dt><span class="term">
-<code class="literal"><check-traditional-pgp></code><a id="check-traditional-pgp"></a> (default: Esc P)
-</span></dt><dd><p>
-This function will search the current message for content signed or
-encrypted with PGP the “<span class="quote">traditional</span>” 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 <a class="link" href="#edit-type"><code class="literal"><edit-type></code></a> function's
-effect.
-</p></dd><dt><span class="term">
-<code class="literal"><edit></code><a id="edit"></a> (default: e)
-</span></dt><dd><p>
-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; if the message is unchanged it won't be replaced.
-</p></dd><dt><span class="term">
-<code class="literal"><edit-type></code><a id="edit-type"></a> (default:
-^E on the attachment menu, and in the pager and index menus;
-^T on the compose menu)
-</span></dt><dd><p>
-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 class="link" href="#attach-menu" title="1.2. The Attachment Menu">attachment menu</a>, you can change any
-attachment's content type. These changes are not persistent, and get
-lost upon changing folders.
-</p><p>
-Note that this command is also available on the <a class="link" href="#compose-menu" title="1.3. The Compose Menu">compose
-menu</a>. There, it's used to fine-tune the properties of attachments you are going
-to send.
-</p></dd><dt><span class="term">
-<code class="literal"><enter-command></code><a id="enter-command"></a> (default: “<span class="quote">:</span>”)
-</span></dt><dd><p>
-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 <a class="link" href="#macro" title="8. Keyboard macros">macros</a> to change settings on the
-fly.
-</p></dd><dt><span class="term">
-<code class="literal"><extract-keys></code><a id="extract-keys"></a> (default: ^K)
-</span></dt><dd><p>
-This command extracts PGP public keys from the current or tagged
-message(s) and adds them to your PGP public key ring.
-</p></dd><dt><span class="term">
-<code class="literal"><forget-passphrase></code><a id="forget-passphrase"></a> (default:
-^F)
-</span></dt><dd><p>
-This command wipes the passphrase(s) from memory. It is useful, if
-you misspelled the passphrase.
-</p></dd><dt><span class="term">
-<code class="literal"><list-reply></code><a id="list-reply"></a> (default: L)
-</span></dt><dd><p>
-Reply to the current or tagged message(s) by extracting any addresses which
-match the regular expressions given by the <a class="link" href="#lists" title="12. Mailing lists">lists or subscribe</a>
-commands, but also honor any <code class="literal">Mail-Followup-To</code> header(s) if the
-<a class="link" href="#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a>
-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.
-</p></dd><dt><span class="term">
-<code class="literal"><pipe-message></code><a id="pipe-message"></a> (default: |)
-</span></dt><dd><p>
-Asks for an external Unix command and pipes the current or
-tagged message(s) to it. The variables <a class="link" href="#pipe-decode" title="3.214. pipe_decode">$pipe_decode</a>, <a class="link" href="#pipe-split" title="3.213. pipe_split">$pipe_split</a>,
-<a class="link" href="#pipe-sep" title="3.215. pipe_sep">$pipe_sep</a> and <a class="link" href="#wait-key" title="3.303. wait_key">$wait_key</a> control the exact behavior of this function.
-</p></dd><dt><span class="term">
-<code class="literal"><resend-message></code><a id="resend-message"></a> (default: Esc e)
-</span></dt><dd><p>
-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 <a class="link" href="#weed" title="3.304. weed">$weed</a>
-variable.
-</p><p>
-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 <code class="literal">message/rfc822</code> body part.
-</p></dd><dt><span class="term">
-<code class="literal"><shell-escape></code><a id="shell-escape"></a> (default: !)
-</span></dt><dd><p>
-Asks for an external Unix command and executes it. The <a class="link" href="#wait-key" title="3.303. wait_key">$wait_key</a> can be used to control
-whether Mutt 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. If no command is given, an
-interactive shell is executed.
-</p></dd><dt><span class="term">
-<code class="literal"><toggle-quoted></code><a id="toggle-quoted"></a> (default: T)
-</span></dt><dd><p>
-The pager uses the <a class="link" href="#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a> variable to detect quoted text when
-displaying the body of the message. This function toggles the display
-of the quoted material in the message. It is particularly useful when
-being interested in just the response and there is a large amount of
-quoted text in the way.
-</p></dd><dt><span class="term">
-<code class="literal"><skip-quoted></code><a id="skip-quoted"></a> (default: S)
-</span></dt><dd><p>
-This function will go to the next line of non-quoted text which comes
-after a line of quoted text in the internal pager.
-</p></dd></dl></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="sending"></a>5. Sending Mail</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-intro"></a>5.1. Introduction</h3></div></div></div><p>
-The bindings shown in <a class="xref" href="#tab-key-send" title="Table 2.10. Most common mail sending keys">Table 2.10, “Most common mail sending keys”</a> are available in the
-<span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> to start a new message.
-</p><div class="table"><a id="tab-key-send"></a><p class="title"><b>Table 2.10. Most common mail sending keys</b></p><div class="table-contents"><table summary="Most common mail sending keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>m</td><td><code class="literal"><compose></code></td><td>compose a new message</td></tr><tr><td>r</td><td><code class="literal"><reply></code></td><td>reply to sender</td></tr><tr><td>g</td><td><code class="literal"><group-reply></code></td><td>reply to all recipients</td></tr><tr><td>L</td><td><code class="literal"><list-reply></code></td><td>reply to mailing list address</td></tr><tr><td>f</td><td><code class="literal"><forward></code></td><td>forward message</td></tr><tr><td>b</td><td><code class="literal"><bounce></code></td><td>bounce (remail) message</td></tr><tr><td>Esc k</td><td><code class="literal"><mail-key></code></td><td>mail a PGP public key to someone</td></tr></tbody></table></div></div><br class="table-break" /><p>
-<span class="emphasis"><em>Bouncing</em></span> a message sends the message as-is to the recipient you
-specify. <span class="emphasis"><em>Forwarding</em></span> 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 “<span class="quote"><a class="link" href="#forwarding-mail" title="6. Forwarding and Bouncing Mail">Forwarding
-and Bouncing Mail</a>.</span>”
-</p><p>
-Mutt will then enter the <span class="emphasis"><em>compose</em></span> menu and prompt you for the
-recipients to place on the “<span class="quote">To:</span>” header field. Next, it will ask
-you for the “<span class="quote">Subject:</span>” field for the message, providing a default if
-you are replying to or forwarding a message. See also
-<a class="link" href="#askcc" title="3.10. askcc">$askcc</a>,
-<a class="link" href="#askbcc" title="3.9. askbcc">$askbcc</a>,
-<a class="link" href="#autoedit" title="3.17. autoedit">$autoedit</a>,
-<a class="link" href="#bounce" title="3.21. bounce">$bounce</a>,
-<a class="link" href="#fast-reply" title="3.55. fast_reply">$fast_reply</a>,
-and <a class="link" href="#include" title="3.98. include">$include</a>
-for changing how Mutt asks these questions.
-</p><p>
-Mutt will then automatically start your <a class="link" href="#editor" title="3.51. editor">$editor</a>
-on the message body. If the <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>
-variable is set, the headers will be at the top of the message in your editor.
-Any messages you are replying to will be added in sort order to the message,
-with appropriate <a class="link" href="#attribution" title="3.16. attribution">$attribution</a>,
-<a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a> and
-<a class="link" href="#post-indent-string" title="3.225. post_indent_string">$post_indent_string</a>.
-When forwarding a message, if the <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a>
-variable is unset, a copy of the forwarded message will be included. If
-you have specified a <a class="link" href="#signature" title="3.265. signature">$signature</a>, it
-will be appended to the message.
-</p><p>
-Once you have finished editing the body of your mail message, you are
-returned to the <span class="emphasis"><em>compose</em></span> menu providing the functions
-shown in <a class="xref" href="#tab-func-compose" title="Table 2.11. Most common compose menu keys">Table 2.11, “Most common compose menu keys”</a> to modify, send or postpone the
-message.
-</p><div class="table"><a id="tab-func-compose"></a><p class="title"><b>Table 2.11. Most common compose menu keys</b></p><div class="table-contents"><table summary="Most common compose menu keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>a</td><td><code class="literal"><attach-file></code></td><td>attach a file</td></tr><tr><td>A</td><td><code class="literal"><attach-message></code></td><td>attach message(s) to the message</td></tr><tr><td>Esc k</td><td><code class="literal"><attach-key></code></td><td>attach a PGP public key</td></tr><tr><td>d</td><td><code class="literal"><edit-description></code></td><td>edit description on attachment</td></tr><tr><td>D</td><td><code class="literal"><detach-file></code></td><td>detach a file</td></tr><tr><td>t</td><td><code class="literal"><edit-to></code></td><td>edit the To field</td></tr><tr><td>Esc f</td><td><code class="literal"><edit-from></code></td><td>edit the From field</td></tr><tr><td>r</td><td><code class="literal"><edit-reply-to></code></td><td>edit the Reply-To field</td></tr><tr><td>c</td><td><code class="literal"><edit-cc></code></td><td>edit the Cc field</td></tr><tr><td>b</td><td><code class="literal"><edit-bcc></code></td><td>edit the Bcc field</td></tr><tr><td>y</td><td><code class="literal"><send-message></code></td><td>send the message</td></tr><tr><td>s</td><td><code class="literal"><edit-subject></code></td><td>edit the Subject</td></tr><tr><td>S</td><td><code class="literal"><smime-menu></code></td><td>select S/MIME options</td></tr><tr><td>f</td><td><code class="literal"><edit-fcc></code></td><td>specify an “<span class="quote">Fcc</span>” mailbox</td></tr><tr><td>p</td><td><code class="literal"><pgp-menu></code></td><td>select PGP options</td></tr><tr><td>P</td><td><code class="literal"><postpone-message></code></td><td>postpone this message until later</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>quit (abort) sending the message</td></tr><tr><td>w</td><td><code class="literal"><write-fcc></code></td><td>write the message to a folder</td></tr><tr><td>i</td><td><code class="literal"><ispell></code></td><td>check spelling (if available on your system)</td></tr><tr><td>^F</td><td><code class="literal"><forget-passphrase></code></td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The compose menu is also used to edit the attachments for a message which can be either files
-or other messages. The <code class="literal"><attach-message></code> function to will prompt you for a folder to
-attach messages from. You can now tag messages in that folder and they
-will be attached to the message you are sending.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that certain
-operations like composing a new mail, replying, forwarding, etc. are
-not permitted when you are in that folder. The %r in
-<a class="link" href="#status-format" title="3.281. status_format">$status_format</a> will change to
-a “<span class="quote">A</span>” to indicate that you are in attach-message mode.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-header"></a>5.2. Editing the message header</h3></div></div></div><p>
-When editing the header because of <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>
-being set, there are a several pseudo headers available which
-will not be included in sent messages.
-</p><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="fcc-header"></a>5.2.1. Fcc: pseudo header</h4></div></div></div><p>
-If you specify
-
-<code class="literal">Fcc:</code> <span class="emphasis"><em>filename</em></span>
-
-as a header, Mutt will pick up <span class="emphasis"><em>filename</em></span>
-just as if you had used the <code class="literal"><edit-fcc></code> function in the <span class="emphasis"><em>compose</em></span> menu.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="attach-header"></a>5.2.2. Attach: pseudo header</h4></div></div></div><p>
-You can also attach files to your message by specifying
-
-<code class="literal">Attach:</code> <span class="emphasis"><em>filename</em></span> [ <span class="emphasis"><em>description</em></span> ]
-
-where <span class="emphasis"><em>filename</em></span> is the file to attach and <span class="emphasis"><em>description</em></span> is an
-optional string to use as the description of the attached file.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="pgp-header"></a>5.2.3. Pgp: pseudo header</h4></div></div></div><p>
-If you want to use PGP, you can specify
-</p><p>
-<code class="literal">Pgp:</code> [ <code class="literal">E</code> | <code class="literal">S</code> | <code class="literal">S</code><span class="emphasis"><em><id></em></span> ]
-
-</p><p>
-“<span class="quote">E</span>” selects encryption, “<span class="quote">S</span>” selects signing and
-“<span class="quote">S<id></span>” selects signing with the given key, setting
-<a class="link" href="#pgp-sign-as" title="3.166. pgp_sign_as">$pgp_sign_as</a>
-permanently.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="in-reply-to-header"></a>5.2.4. In-Reply-To: header</h4></div></div></div><p>
-When replying to messages, the <span class="emphasis"><em>In-Reply-To:</em></span> header contains the
-Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
-<span class="emphasis"><em>References:</em></span> field, which allows you to create a new message thread, for example
-to create a new message to a mailing list without having to enter the mailing list's address.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-crypto"></a>5.3. Sending cryptographically signed/encrypted messages</h3></div></div></div><p>
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
-through a key selection process when you try to send the message.
-Mutt 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.
-</p><p>
-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 <code class="literal">^G</code>. When you do so, mutt will
-return to the compose screen.
-</p><p>
-Once you have successfully finished the key selection, the message
-will be encrypted using the selected public keys when sent out.
-</p><p>
-Most fields of the entries in the key selection menu (see also <a class="link" href="#pgp-entry-format" title="3.158. pgp_entry_format">$pgp_entry_format</a>)
-have obvious meanings. But some explanations on the capabilities, flags,
-and validity fields are in order.
-</p><p>
-The flags sequence (%f) will expand to one of the flags in
-<a class="xref" href="#tab-pgp-menuflags" title="Table 2.12. PGP key menu flags">Table 2.12, “PGP key menu flags”</a>.
-</p><div class="table"><a id="tab-pgp-menuflags"></a><p class="title"><b>Table 2.12. PGP key menu flags</b></p><div class="table-contents"><table summary="PGP key menu flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>R</td><td>The key has been revoked and can't be used.</td></tr><tr><td>X</td><td>The key is expired and can't be used.</td></tr><tr><td>d</td><td>You have marked the key as disabled.</td></tr><tr><td>c</td><td>There are unknown critical self-signature packets.</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The capabilities field (%c) expands to a two-character sequence
-representing a key's capabilities. The first character gives
-the key's encryption capabilities: A minus sign (“<span class="quote">-</span>”) means
-that the key cannot be used for encryption. A dot (“<span class="quote">.</span>”) means that
-it's marked as a signature key in one of the user IDs, but may
-also be used for encryption. The letter “<span class="quote">e</span>” indicates that
-this key can be used for encryption.
-</p><p>
-The second character indicates the key's signing capabilities. Once
-again, a “<span class="quote">-</span>” implies “<span class="quote">not for signing</span>”, “<span class="quote">.</span>” implies
-that the key is marked as an encryption key in one of the user-ids, and
-“<span class="quote">s</span>” denotes a key which can be used for signing.
-</p><p>
-Finally, the validity field (%t) indicates how well-certified a user-id
-is. A question mark (“<span class="quote">?</span>”) indicates undefined validity, a minus
-character (“<span class="quote">-</span>”) marks an untrusted association, a space character
-means a partially trusted association, and a plus character (“<span class="quote">+</span>”)
-indicates complete validity.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-mixmaster"></a>5.4. Sending anonymous messages via mixmaster</h3></div></div></div><p>
-You may also have compiled 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.
-</p><p>
-To use it, you'll have to obey certain restrictions. Most
-important, you cannot use the <code class="literal">Cc</code> and <code class="literal">Bcc</code> headers. To tell
-Mutt to use mixmaster, you have to select a remailer chain, using
-the mix function on the compose menu.
-</p><p>
-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.
-</p><p>
-You can navigate in the chain using the <code class="literal"><chain-prev></code> and
-<code class="literal"><chain-next></code> functions, which are by default bound to the left
-and right arrows and to the <code class="literal">h</code> and <code class="literal">l</code> keys (think vi
-keyboard bindings). To insert a remailer at the current chain
-position, use the <code class="literal"><insert></code> function. To append a remailer behind
-the current chain position, use <code class="literal"><select-entry></code> or <code class="literal"><append></code>.
-You can also delete entries from the chain, using the corresponding
-function. Finally, to abandon your changes, leave the menu, or
-<code class="literal"><accept></code> them pressing (by default) the <code class="literal">Return</code> key.
-</p><p>
-Note that different remailers do have different capabilities,
-indicated in the %c entry of the remailer menu lines (see
-<a class="link" href="#mix-entry-format" title="3.130. mix_entry_format">$mix_entry_format</a>). Most important is
-the “<span class="quote">middleman</span>” capability, indicated by a capital “<span class="quote">M</span>”: 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ff"></a>5.5. Sending format=flowed messages</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-concept"></a>5.5.1. Concept</h4></div></div></div><p>
-<code class="literal">format=flowed</code>-style messages (or <code class="literal">f=f</code>
-for short) are <code class="literal">text/plain</code> messages that consist of paragraphs which a receiver's
-mail client may reformat to its own needs which mostly means to
-customize line lengths regardless of what the sender sent. Technically this is
-achieved by letting lines of a “<span class="quote">flowable</span>” paragraph end in spaces
-except for the last line.
-</p><p>
-While for text-mode clients like mutt it's the best way to assume only a
-standard 80x25 character cell terminal, it may be desired to let the
-receiver decide completely how to view a message.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-support"></a>5.5.2. Mutt support</h4></div></div></div><p>
-Mutt only supports setting the required <code class="literal">format=flowed</code>
-MIME parameter on outgoing messages if the <a class="link" href="#text-flowed" title="3.285. text_flowed">$text_flowed</a>
-variable is set, specifically it does not add the
-trailing spaces.
-</p><p>
-After editing the initial message text and before entering
-the compose menu, mutt properly space-stuffes the message.
-<span class="emphasis"><em>Space-stuffing</em></span> is required by RfC3676 defining
-<code class="literal">format=flowed</code> and means to prepend a space to:
-</p><div class="itemizedlist"><ul type="disc"><li><p>all lines starting with a space</p></li><li><p>lines starting with the word “<span class="quote"><code class="literal">From</code></span>”
-followed by space</p></li><li><p>all lines starting with “<span class="quote"><code class="literal">></code></span>” which
-is not intended to be a quote character</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
-Mutt only supports space-stuffing
-for the first two types of lines but not for the third: It is impossible to
-safely detect whether a leading <code class="literal">></code> character starts a
-quote or not. Furthermore, Mutt only applies space-stuffing
-<span class="emphasis"><em>once</em></span> after the initial edit is finished.
-</p></div><p>
-All leading spaces are to be removed by receiving clients to restore
-the original message prior to further processing.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-editor"></a>5.5.3. Editor considerations</h4></div></div></div><p>
-As mutt provides no additional features to compose <code class="literal">f=f</code>
-messages, it's completely up to the user and his editor to produce
-proper messages. Please consider your editor's documentation if you
-intend to send <code class="literal">f=f</code> messages.
-</p><p>
-Please note that when editing messages from the compose menu several
-times before really sending a mail, it's up to the user to ensure that
-the message is properly space-stuffed.
-</p><p>
-For example, <span class="emphasis"><em>vim</em></span> provides the <code class="literal">w</code>
-flag for its <code class="literal">formatoptions</code> setting to assist in
-creating <code class="literal">f=f</code> messages, see <code class="literal">:help
-fo-table</code> for details.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="forwarding-mail"></a>6. Forwarding and Bouncing Mail</h2></div></div></div><p>
-Bouncing and forwarding let you send an existing message to recipients
-that you specify. Bouncing a message sends a verbatim copy of a message
-to alternative addresses as if they were the message's original
-recipients specified in the Bcc header.
-Forwarding a message, on the other hand, allows you to modify the message
-before it is resent (for example, by adding your own comments). Bouncing
-is done using the <code class="literal"><bounce></code> function and forwarding
-using the <code class="literal"><forward></code> function bound to “<span class="quote">b</span>” and “<span class="quote">f</span>”
-respectively.
-</p><p>
-Forwarding can be done by including the original message in the new
-message's body (surrounded by indicating lines) or including it as a MIME
-attachment, depending on the value of the <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> variable. Decoding of attachments,
-like in the pager, can be controlled by the <a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> variables,
-respectively. The desired forwarding format may depend on the content,
-therefore <span class="emphasis"><em>$mime_forward</em></span> is a quadoption which, for
-example, can be set to “<span class="quote">ask-no</span>”.
-</p><p>
-The inclusion of headers is controlled by the current setting of the
-<a class="link" href="#weed" title="3.304. weed">$weed</a> variable, unless <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is set.
-</p><p>
-Editing the message to forward follows the same procedure as sending or
-replying to a message does.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="postponing-mail"></a>7. Postponing Mail</h2></div></div></div><p>
-At times it is desirable to delay sending a message that you have
-already begun to compose. When the <code class="literal"><postpone-message></code> function is
-used in the <span class="emphasis"><em>compose</em></span> menu, the body of your message and attachments
-are stored in the mailbox specified by the <a class="link" href="#postponed" title="3.227. postponed">$postponed</a> variable. This means that you can recall the
-message even if you exit Mutt and then restart it at a later time.
-</p><p>
-Once a message is postponed, there are several ways to resume it. From the
-command line you can use the “<span class="quote">-p</span>” option, or if you compose a new
-message from the <span class="emphasis"><em>index</em></span> or <span class="emphasis"><em>pager</em></span> you will be prompted if postponed
-messages exist. If multiple messages are currently postponed, the
-<span class="emphasis"><em>postponed</em></span> menu will pop up and you can select which message you would
-like to resume.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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.
-</p></div><p>
-See also the <a class="link" href="#postpone" title="3.226. postpone">$postpone</a> quad-option.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="configuration"></a>Chapter 3. Configuration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="configuration-files"></a>1. Location of initialization files</h2></div></div></div><p>
-While the default configuration (or “<span class="quote">preferences</span>”) make Mutt
-usable right out of the box, it is often desirable to tailor Mutt to
-suit your own tastes. When Mutt is first invoked, it will attempt to
-read the “<span class="quote">system</span>” configuration file (defaults set by your local
-system administrator), unless the “<span class="quote">-n</span>” <a class="link" href="#commandline" title="1. Command line options">command line</a> option is specified. This file is typically
-<code class="literal">/usr/local/share/mutt/Muttrc</code> or <code class="literal">/etc/Muttrc</code>. Mutt
-will next look for a file named <code class="literal">.muttrc</code> in your home
-directory. If this file does not exist and your home directory has
-a subdirectory named <code class="literal">.mutt</code>, mutt try to load a file named
-<code class="literal">.mutt/muttrc</code>.
-</p><p>
-<code class="literal">.muttrc</code> is the file where you will usually place your <a class="link" href="#commands" title="2. Configuration Commands">commands</a> to configure Mutt.
-</p><p>
-In addition, mutt supports version specific configuration files that are
-parsed instead of the default files as explained above. For instance, if
-your system has a <code class="literal">Muttrc-0.88</code> file in the system configuration
-directory, and you are running version 0.88 of mutt, this file will be
-sourced instead of the <code class="literal">Muttrc</code> file. The same is true of the user
-configuration file, if you have a file <code class="literal">.muttrc-0.88.6</code> in your home
-directory, when you run mutt version 0.88.6, it will source this file
-instead of the default <code class="literal">.muttrc</code> file. The version number is the
-same which is visible using the “<span class="quote">-v</span>” <a class="link" href="#commandline" title="1. Command line options">command line</a> switch or using the <code class="literal">show-version</code> key (default:
-V) from the index menu.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttrc-syntax"></a>2. Syntax of Initialization Files</h2></div></div></div><p>
-An initialization file consists of a series of <a class="link" href="#commands" title="2. Configuration Commands">commands</a>. Each line of the file may contain one or more commands.
-When multiple commands are used, they must be separated by a semicolon
-(;).
-</p><div class="example"><a id="ex-rc-multiple-cmds"></a><p class="title"><b>Example 3.1. Multiple configuration commands per line</b></p><div class="example-contents"><pre class="screen">
-set realname='Mutt user' ; ignore x-
-</pre></div></div><br class="example-break" /><p>
-The hash mark, or pound sign
-(“<span class="quote">#</span>”), is used as a “<span class="quote">comment</span>” 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,
-</p><div class="example"><a id="ex-ec-comment"></a><p class="title"><b>Example 3.2. Commenting configuration files</b></p><div class="example-contents"><pre class="screen">
-my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
-</pre></div></div><br class="example-break" /><p>
-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, backticks are evaluated inside of double
-quotes, but <span class="bold"><strong>not</strong></span> for single quotes.
-</p><p>
-\ quotes the next character, just as in shells such as bash and zsh.
-For example, if want to put quotes “<span class="quote">"</span>” inside of a string, you can use
-“<span class="quote">\</span>” to force the next character to be a literal instead of interpreted
-character.
-</p><div class="example"><a id="ex-rc-quote"></a><p class="title"><b>Example 3.3. Escaping quotes in congfiguration files</b></p><div class="example-contents"><pre class="screen">
-set realname="Michael \"MuttDude\" Elkins"
-</pre></div></div><br class="example-break" /><p>
-“<span class="quote">\\</span>” means to insert a literal “<span class="quote">\</span>” into the line.
-“<span class="quote">\n</span>” and “<span class="quote">\r</span>” have their usual C meanings of linefeed and
-carriage-return, respectively.
-</p><p>
-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.
-</p><p>
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command in
-backticks (``). For example,
-</p><div class="example"><a id="ex-rc-backtick"></a><p class="title"><b>Example 3.4. Using external command's output in configuration files</b></p><div class="example-contents"><pre class="screen">
-my_hdr X-Operating-System: `uname -a`
-</pre></div></div><br class="example-break" /><p>
-The output of the Unix command “<span class="quote">uname -a</span>” will be substituted before the
-line is parsed.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Since initialization files are line oriented, only
-the first line of output from the Unix command will be substituted.
-</p></div><p>
-Both environment variables and mutt variables can be accessed by
-prepending “<span class="quote">$</span>” to the name of the variable. For example,
-</p><div class="example"><a id="ex-rc-env"></a><p class="title"><b>Example 3.5. Using environment variables in configuration files</b></p><div class="example-contents"><pre class="screen">
-set record=+sent_on_$HOSTNAME
-</pre></div></div><br class="example-break" /><p>
-will cause mutt to save outgoing messages to a folder named
-“<span class="quote">sent_on_kremvax</span>” if the environment variable HOSTNAME is set to
-“<span class="quote">kremvax.</span>” (See <a class="link" href="#record" title="3.242. record">$record</a> for
-details.)
-</p><p>
-Mutt expands the variable when it is assigned, not when it is used. If
-the value of a variable on the right-hand side of an assignment
-changes after the assignment, the variable on the left-hand side will
-not be affected.
-</p><p>
-The commands understood by mutt are explained in the next paragraphs.
-For a complete list, see the <a class="link" href="#commands" title="2. Configuration Commands">command reference</a>.
-</p><p>
-All configuration files are expected to be in the current locale as
-specified by the <a class="link" href="#charset" title="3.25. charset">$charset</a> variable
-which doesn't have a default value since it's determined by Mutt at startup.
-If a configuration file is not encoded in the same character set the
-<a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a>
-variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
-</p><p>
-This mechanism should be avoided if possible as it has the
-following implications:
-</p><div class="itemizedlist"><ul type="disc"><li><p>These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.</p></li><li><p>If $config_charset is set, it should be set
-in each configuration file because the value is global and <span class="emphasis"><em>not</em></span>
-per configuration file.</p></li><li><p>Because Mutt first recodes a line before it attempts to parse it,
-a conversion introducing question marks or other characters as
-part of errors (unconvertable characters, transliteration) may introduce syntax
-errors or silently change the meaning of certain tokens (e.g. inserting
-question marks into regular expressions).</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="addrgroup"></a>3. Address groups</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">group</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div><div class="cmdsynopsis"><p><code class="command">ungroup</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div><p>
-<code class="literal">group</code> is used to directly add either addresses or
-regular expressions to the specified group or groups. The different
-categories of arguments to the <code class="literal">group</code> command can be
-in any order. The flags <code class="literal">-rx</code> and
-<code class="literal">-addr</code> specify what the following strings (that cannot
-begin with a hyphen) should be interpreted as: either a regular
-expression or an email address, respectively.
-</p><p>
-These address groups can also be created implicitly by the
-<a class="link" href="#alias" title="4. Defining/Using aliases">alias</a>, <a class="link" href="#lists" title="12. Mailing lists">lists</a>,
-<a class="link" href="#lists" title="12. Mailing lists">subscribe</a> and
-<a class="link" href="#alternates" title="11. Alternative addresses">alternates</a> commands by specifying the
-optional <code class="literal">-group</code> option.
-</p><p>
-Once defined, these address groups can be used in
-<a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> to search for and limit the
-display to messages matching a group.
-</p><p>
-<code class="literal">ungroup</code> is used to remove addresses or regular
-expressions from the specified group or groups. The syntax is similar to
-the <code class="literal">group</code> command, however the special character
-<code class="literal">*</code> can be used to empty a group of all of its
-contents.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alias"></a>4. Defining/Using aliases</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alias</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>address</code></em>
- [
-<em class="replaceable"><code>address</code></em>
-...]</p></div><p>
-It's usually very cumbersome to remember or type out the address of someone
-you are communicating with. Mutt allows you to create “<span class="quote">aliases</span>” which map
-a short string to a full address.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you want to create an alias for more than
-one address, you <span class="bold"><strong>must</strong></span> separate the addresses with a comma (“<span class="quote">,</span>”).
-</p></div><p>
-The optional <code class="literal">-group</code> argument to
-<code class="literal">alias</code> causes the aliased address(es) to be added to
-the named <span class="emphasis"><em>group</em></span>.
-</p><p>
-To remove an alias or aliases (“<span class="quote">*</span>” means all aliases):
-</p><div class="cmdsynopsis"><p><code class="command">unalias</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>key</code></em>
-... }</p></div><pre class="screen">
-alias muttdude me@cs.hmc.edu (Michael Elkins)
-alias theguys manny, moe, jack
-</pre><p>
-Unlike other mailers, Mutt doesn't require aliases to be defined
-in a special file. The <code class="literal">alias</code> command can appear anywhere in
-a configuration file, as long as this file is <a class="link" href="#source" title="27. Reading initialization commands from another file">sourced</a>. Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
-</p><p>
-On the other hand, the <a class="link" href="#create-alias"><code class="literal"><create-alias></code></a>
-function can use only one file, the one pointed to by the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> variable (which is
-<code class="literal">˜/.muttrc</code> by default). This file is not special either,
-in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> this file too.
-</p><p>
-For example:
-</p><div class="example"><a id="ex-alias-external"></a><p class="title"><b>Example 3.6. Configuring external alias files</b></p><div class="example-contents"><pre class="screen">
-source /usr/local/share/Mutt.aliases
-source ~/.mail_aliases
-set alias_file=~/.mail_aliases
-</pre></div></div><br class="example-break" /><p>
-To use aliases, you merely use the alias at any place in mutt where mutt
-prompts for addresses, such as the <span class="emphasis"><em>To:</em></span> or <span class="emphasis"><em>Cc:</em></span> prompt. You can
-also enter aliases in your editor at the appropriate headers if you have the
-<a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable set.
-</p><p>
-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.
-</p><p>
-In the alias menu, you can select as many aliases as you want with the
-<code class="literal">select-entry</code> key (default: <Return>), and use the
-<span class="emphasis"><em>exit</em></span> key (default: q) to return to the address prompt.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="bind"></a>5. Changing the default key bindings</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">bind</code>
-<em class="replaceable"><code>map</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>function</code></em>
- </p></div><p>
-This command allows you to change the default key bindings (operation
-invoked when pressing a key).
-</p><p>
-<span class="emphasis"><em>map</em></span> specifies in which menu the binding belongs. Multiple maps may
-be specified by separating them with commas (no additional whitespace is
-allowed). The currently defined maps are:
-</p><a id="maps"></a><div class="variablelist"><dl><dt><span class="term">generic</span></dt><dd><p>
-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 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.
-</p></dd><dt><span class="term">alias</span></dt><dd><p>
-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).
-</p></dd><dt><span class="term">attach</span></dt><dd><p>
-The attachment menu is used to access the attachments on received messages.
-</p></dd><dt><span class="term">browser</span></dt><dd><p>
-The browser is used for both browsing the local directory structure, and for
-listing all of your incoming mailboxes.
-</p></dd><dt><span class="term">editor</span></dt><dd><p>
-The editor is the line-based editor the user enters text data.
-</p></dd><dt><span class="term">index</span></dt><dd><p>
-The index is the list of messages contained in a mailbox.
-</p></dd><dt><span class="term">compose</span></dt><dd><p>
-The compose menu is the screen used when sending a new message.
-</p></dd><dt><span class="term">pager</span></dt><dd><p>
-The pager is the mode used to display message/attachment data, and help
-listings.
-</p></dd><dt><span class="term">pgp</span></dt><dd><p>
-The pgp menu is used to select the OpenPGP keys used to encrypt outgoing
-messages.
-</p></dd><dt><span class="term">smime</span></dt><dd><p>
-The smime menu is used to select the OpenSSL certificates used to encrypt outgoing
-messages.
-</p></dd><dt><span class="term">postpone</span></dt><dd><p>
-The postpone menu is similar to the index menu, except is used when
-recalling a message the user was composing, but saved until later.
-</p></dd><dt><span class="term">query</span></dt><dd><p>
-The query menu is the browser for results returned by
-<a class="link" href="#query-command" title="3.234. query_command">$query_command</a>.
-</p></dd><dt><span class="term">mix</span></dt><dd><p>
-The mixmaster screen is used to select remailer options for outgoing
-messages (if Mutt is compiled with Mixmaster support).
-</p></dd></dl></div><p>
-<span class="emphasis"><em>key</em></span> is the key (or key sequence) you wish to bind. To specify a
-control character, use the sequence <span class="emphasis"><em>\Cx</em></span>, where <span class="emphasis"><em>x</em></span> is the
-letter of the control character (for example, to specify control-A use
-“<span class="quote">\Ca</span>”). Note that the case of <span class="emphasis"><em>x</em></span> as well as <span class="emphasis"><em>\C</em></span> is
-ignored, so that <span class="emphasis"><em>\CA</em></span>, <span class="emphasis"><em>\Ca</em></span>, <span class="emphasis"><em>\cA</em></span> and <span class="emphasis"><em>\ca</em></span> are all
-equivalent. An alternative form is to specify the key as a three digit
-octal number prefixed with a “<span class="quote">\</span>” (for example <span class="emphasis"><em>\177</em></span> is
-equivalent to <span class="emphasis"><em>\c?</em></span>). In addition, <span class="emphasis"><em>key</em></span> may
-be a symbolic name as shown in <a class="xref" href="#tab-key-names" title="Table 3.1. Symbolic key names">Table 3.1, “Symbolic key names”</a>.
-</p><div class="table"><a id="tab-key-names"></a><p class="title"><b>Table 3.1. Symbolic key names</b></p><div class="table-contents"><table summary="Symbolic key names" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Symbolic name</th><th>Meaning</th></tr></thead><tbody><tr><td>\t</td><td>tab</td></tr><tr><td><tab></td><td>tab</td></tr><tr><td><backtab></td><td>backtab / shift-tab</td></tr><tr><td>\r</td><td>carriage return</td></tr><tr><td>\n</td><td>newline</td></tr><tr><td>\e</td><td>escape</td></tr><tr><td><esc></td><td>escape</td></tr><tr><td><up></td><td>up arrow</td></tr><tr><td><down></td><td>down arrow</td></tr><tr><td><left></td><td>left arrow</td></tr><tr><td><right></td><td>right arrow</td></tr><tr><td><pageup></td><td>Page Up</td></tr><tr><td><pagedown></td><td>Page Down</td></tr><tr><td><backspace></td><td>Backspace</td></tr><tr><td><delete></td><td>Delete</td></tr><tr><td><insert></td><td>Insert</td></tr><tr><td><enter></td><td>Enter</td></tr><tr><td><return></td><td>Return</td></tr><tr><td><home></td><td>Home</td></tr><tr><td><end></td><td>End</td></tr><tr><td><space></td><td>Space bar</td></tr><tr><td><f1></td><td>function key 1</td></tr><tr><td><f10></td><td>function key 10</td></tr></tbody></table></div></div><br class="table-break" /><p>
-<span class="emphasis"><em>key</em></span> does not need to be enclosed in quotes unless it contains a
-space (“<span class="quote"> </span>”) or semi-colon (“<span class="quote">;</span>”).
-</p><p>
-<span class="emphasis"><em>function</em></span> specifies which action to take when <span class="emphasis"><em>key</em></span> is pressed.
-For a complete list of functions, see the <a class="link" href="#functions" title="4. Functions">reference</a>. The special function <code class="literal"><noop></code> unbinds the specified key
-sequence.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="charset-hook"></a>6. Defining aliases for character sets </h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">charset-hook</code>
-<em class="replaceable"><code>alias</code></em>
-
-<em class="replaceable"><code>charset</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">iconv-hook</code>
-<em class="replaceable"><code>charset</code></em>
-
-<em class="replaceable"><code>local-charset</code></em>
- </p></div><p>
-The <code class="literal">charset-hook</code> 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.
-</p><p>
-The <code class="literal">iconv-hook</code> 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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="folder-hook"></a>7. Setting variables based upon mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">folder-hook</code>
-<em class="replaceable"><code>[!]regexp</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-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. <span class="emphasis"><em>regexp</em></span> is a regular expression specifying
-in which mailboxes to execute <span class="emphasis"><em>command</em></span> before loading. If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you use the “<span class="quote">!</span>” shortcut for <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a> at the beginning of the pattern, you must place it
-inside of double or single quotes in order to distinguish it from the
-logical <span class="emphasis"><em>not</em></span> operator for the expression.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-Settings are <span class="emphasis"><em>not</em></span> restored when you leave the mailbox.
-For example, a command action to perform is to change the sorting method
-based upon the mailbox being read:
-</p></div><pre class="screen">
-folder-hook mutt set sort=threads
-</pre><p>
-However, the sorting method is not restored to its previous value when
-reading a different mailbox. To specify a <span class="emphasis"><em>default</em></span> command, use the
-pattern “<span class="quote">.</span>” before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
-The following example will set the <a class="link" href="#sort" title="3.273. sort">sort</a> variable
-to <code class="literal">date-sent</code> for all folders but to <code class="literal">threads</code>
-for all folders containing “<span class="quote">mutt</span>” in their name.
-</p><div class="example"><a id="ex-folder-sorting"></a><p class="title"><b>Example 3.7. Setting sort method based on mailbox name</b></p><div class="example-contents"><pre class="screen">
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="macro"></a>8. Keyboard macros</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">macro</code>
-<em class="replaceable"><code>menu</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>sequence</code></em>
- [
-<em class="replaceable"><code>description</code></em>
-]</p></div><p>
-Macros are useful when you would like a single key to perform a series of
-actions. When you press <span class="emphasis"><em>key</em></span> in menu <span class="emphasis"><em>menu</em></span>, Mutt will behave as if
-you had typed <span class="emphasis"><em>sequence</em></span>. So if you have a common sequence of commands
-you type, you can create a macro to execute those commands with a single
-key or fewer keys.
-</p><p>
-<span class="emphasis"><em>menu</em></span> is the <a class="link" href="#maps">map</a> which the macro will be bound in.
-Multiple maps may be specified by separating multiple menu arguments by
-commas. Whitespace may not be used in between the menu arguments and the
-commas separating them.
-</p><p>
-<span class="emphasis"><em>key</em></span> and <span class="emphasis"><em>sequence</em></span> are expanded by the same rules as the
-<a class="link" href="#bind" title="5. Changing the default key bindings">key bindings</a> with some additions. The
-first is that control characters in <span class="emphasis"><em>sequence</em></span> can also be specified
-as <span class="emphasis"><em>^x</em></span>. In order to get a caret (“<span class="quote">^</span>”) you need to use
-<span class="emphasis"><em>^^</em></span>. Secondly, to specify a certain key such as <span class="emphasis"><em>up</em></span>
-or to invoke a function directly, you can use the format
-<span class="emphasis"><em><key name></em></span> and <span class="emphasis"><em><function name></em></span>. For a listing of key
-names see the section on <a class="link" href="#bind" title="5. Changing the default key bindings">key bindings</a>. Functions
-are listed in the <a class="link" href="#functions" title="4. Functions">reference</a>.
-</p><p>
-The advantage with using function names directly is that the macros will
-work regardless of the current key bindings, so they are not dependent on
-the user having particular key definitions. This makes them more robust
-and portable, and also facilitates defining of macros in files used by more
-than one user (e.g., the system Muttrc).
-</p><p>
-Optionally you can specify a descriptive text after <span class="emphasis"><em>sequence</em></span>,
-which is shown in the help screens.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Macro definitions (if any) listed in the help screen(s), are
-silently truncated at the screen width, and are not wrapped.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="color"></a>9. Using color and mono video attributes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">color</code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">color</code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">color</code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">uncolor</code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-If your terminal supports color, you can spice up Mutt by creating your own
-color scheme. To define the color of an object (type of information), you
-must specify both a foreground color <span class="bold"><strong>and</strong></span> a background color (it is not
-possible to only specify one or the other).
-</p><p>
-<span class="emphasis"><em>header</em></span> and <span class="emphasis"><em>body</em></span> match <span class="emphasis"><em>regexp</em></span>
-in the header/body of a message, <span class="emphasis"><em>index</em></span> matches <span class="emphasis"><em>pattern</em></span>
-(see <a class="xref" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">Section 2, “Patterns: Searching, Limiting and Tagging”</a>) in the message index.
-</p><p>
-<span class="emphasis"><em>object</em></span> can be one of:
-</p><div class="itemizedlist"><ul type="disc"><li><p>attachment</p></li><li><p>bold (hiliting bold patterns in the body of messages)</p></li><li><p>error (error messages printed by Mutt)</p></li><li><p>hdrdefault (default color of the message header in the pager)</p></li><li><p>indicator (arrow or bar used to indicate the current item in a menu)</p></li><li><p>markers (the “<span class="quote">+</span>” markers at the beginning of wrapped lines in the pager)</p></li><li><p>message (informational messages)</p></li><li><p>normal</p></li><li><p>quoted (text matching <a class="link" href="#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a> in the body of a message)</p></li><li><p>quoted1, quoted2, ..., quoted<span class="bold"><strong>N</strong></span> (higher levels of quoting)</p></li><li><p>search (hiliting of words in the pager)</p></li><li><p>signature</p></li><li><p>status (mode lines used to display info about the mailbox or message)</p></li><li><p>tilde (the “<span class="quote">˜</span>” used to pad blank lines in the pager)</p></li><li><p>tree (thread tree drawn in the message index and attachment menu)</p></li><li><p>underline (hiliting underlined patterns in the body of messages)</p></li></ul></div><p>
-<span class="emphasis"><em>foreground</em></span> and <span class="emphasis"><em>background</em></span> can be one of the following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>white</p></li><li><p>black</p></li><li><p>green</p></li><li><p>magenta</p></li><li><p>blue</p></li><li><p>cyan</p></li><li><p>yellow</p></li><li><p>red</p></li><li><p>default</p></li><li><p>color<span class="emphasis"><em>x</em></span></p></li></ul></div><p>
-<span class="emphasis"><em>foreground</em></span> can optionally be prefixed with the keyword <code class="literal">bright</code> to make
-the foreground color boldfaced (e.g., <code class="literal">brightred</code>).
-</p><p>
-If your terminal supports it, the special keyword <span class="emphasis"><em>default</em></span> can be
-used as a transparent color. The value <span class="emphasis"><em>brightdefault</em></span> is also valid.
-If Mutt is linked against the <span class="emphasis"><em>S-Lang</em></span> library, you also need to set
-the <span class="emphasis"><em>COLORFGBG</em></span> environment variable to the default colors of your
-terminal for this to work; for example (for Bourne-like shells):
-</p><pre class="screen">
-set COLORFGBG="green;black"
-export COLORFGBG
-</pre><div class="note"><h3 class="title">Note</h3><p>
-The <span class="emphasis"><em>S-Lang</em></span> library requires you to use the <span class="emphasis"><em>lightgray</em></span>
-and <span class="emphasis"><em>brown</em></span> keywords instead of <span class="emphasis"><em>white</em></span> and <span class="emphasis"><em>yellow</em></span> when
-setting this variable.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-The uncolor command can be applied to the index object only. It
-removes entries from the list. You <span class="bold"><strong>must</strong></span> specify the same pattern
-specified in the color command for it to be removed. The pattern “<span class="quote">*</span>” is
-a special token which means to clear the color index list of all entries.
-</p></div><p>
-Mutt also recognizes the keywords <span class="emphasis"><em>color0</em></span>, <span class="emphasis"><em>color1</em></span>, …,
-<span class="emphasis"><em>color</em></span><span class="bold"><strong>N-1</strong></span> (<span class="bold"><strong>N</strong></span> 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 <span class="emphasis"><em>color2</em></span>
-for your xterm), since color names may then lose their normal meaning.
-</p><p>
-If your terminal does not support color, it is still possible change the video
-attributes through the use of the “<span class="quote">mono</span>” command:
-</p><a id="mono"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mono</code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>attribute</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">mono</code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">mono</code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unmono</code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-For <span class="emphasis"><em>object</em></span>, see the color command. <span class="emphasis"><em>attribute</em></span>
-can be one of the following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>none</p></li><li><p>bold</p></li><li><p>underline</p></li><li><p>reverse</p></li><li><p>standout</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ignore"></a>10. Message header display</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">ignore</code>
-<em class="replaceable"><code>pattern</code></em>
- [
-<em class="replaceable"><code>pattern</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unignore</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-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 in the pager.
-</p><p>
-You do not need to specify the full header field name. For example,
-“<span class="quote">ignore content-</span>” will ignore all header fields that begin with the pattern
-“<span class="quote">content-</span>”. “<span class="quote">ignore *</span>” will ignore all headers.
-</p><p>
-To remove a previously added token from the list, use the “<span class="quote">unignore</span>” command.
-The “<span class="quote">unignore</span>” command will make Mutt display headers with the given pattern.
-For example, if you do “<span class="quote">ignore x-</span>” it is possible to “<span class="quote">unignore x-mailer</span>”.
-</p><p>
-“<span class="quote">unignore *</span>” will remove all tokens from the ignore list.
-</p><p>
-For example:
-</p><div class="example"><a id="ex-header-weeding"></a><p class="title"><b>Example 3.8. Header weeding</b></p><div class="example-contents"><pre class="screen">
-# 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:
-</pre></div></div><br class="example-break" /><a id="hdr-order"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">hdr_order</code>
-<em class="replaceable"><code>header</code></em>
- [
-<em class="replaceable"><code>header</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unhdr_order</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>header</code></em>
-... }</p></div><p>
-With the <code class="literal">hdr_order</code> command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
-</p><p>
-“<span class="quote">unhdr_order *</span>” will clear all previous headers from the order list,
-thus removing the header order effects set by the system-wide startup file.
-</p><div class="example"><a id="ex-hdr-order"></a><p class="title"><b>Example 3.9. Configuring header display order</b></p><div class="example-contents"><pre class="screen">
-hdr_order From Date: From: To: Cc: Subject:
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternates"></a>11. Alternative addresses</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alternates</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unalternates</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><p>
-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 <a class="link" href="#reply-to" title="3.245. reply_to">$reply_to</a>.)
-</p><p>
-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 <code class="literal">alternates</code> command: It takes a list of regular
-expressions, each of which can identify an address under which you
-receive e-mail.
-</p><p>
-As addresses are matched using regular expressions and not exact strict
-comparisons, you should make sure you specify your addresses as precise
-as possible to avoid mismatches. For example, if you specify:
-</p><pre class="screen">
-alternates user@example
-</pre><p>
-mutt will consider “<span class="quote"><code class="literal">some-user@example</code></span>” as
-being your address, too which may not be desired. As a solution, in such
-cases addresses should be specified as:
-</p><pre class="screen">
-alternates '^user@example$'
-</pre><p>
-The <code class="literal">-group</code> flag causes all of the subsequent regular expressions
-to be added to the named group.
-</p><p>
-The <code class="literal">unalternates</code> command can be used to write exceptions to
-<code class="literal">alternates</code> patterns. If an address matches something in an
-<code class="literal">alternates</code> command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an <code class="literal">unalternates</code>
-command.
-</p><p>
-To remove a regular expression from the <code class="literal">alternates</code> list, use the
-<code class="literal">unalternates</code> command with exactly the same <span class="emphasis"><em>regexp</em></span>.
-Likewise, if the <span class="emphasis"><em>regexp</em></span> for an <code class="literal">alternates</code> command matches
-an entry on the <code class="literal">unalternates</code> list, that <code class="literal">unalternates</code>
-entry will be removed. If the <span class="emphasis"><em>regexp</em></span> for <code class="literal">unalternates</code>
-is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries</em></span> on <code class="literal">alternates</code> will be removed.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="lists"></a>12. Mailing lists</h2></div></div></div><a id="subscribe"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">lists</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unlists</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><div class="cmdsynopsis"><p><code class="command">subscribe</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unsubscribe</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><p>
-Mutt has a few nice features for <a class="link" href="#using-lists" title="8. Handling Mailing Lists">handling mailing lists</a>. 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 <a class="link" href="#list-reply"><code class="literal"><list-reply></code></a> 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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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
-<a class="link" href="#followup-to" title="3.60. followup_to">$followup_to</a>
-configuration variable.
-</p></div><p>
-More precisely, Mutt 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 “<span class="quote">lists</span>”
-command. To mark it as subscribed, use “<span class="quote">subscribe</span>”.
-</p><p>
-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
-“<span class="quote">subscribe [0-9]*@bugs.guug.de</span>”. Often, it's sufficient to just
-give a portion of the list's e-mail address.
-</p><p>
-Specify as much of the address as you need to to remove ambiguity. For
-example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed to <span class="emphasis"><em>mutt-users@mutt.org</em></span>. So, to tell Mutt
-that this is a mailing list, you could add “<span class="quote">lists mutt-users@</span>” to your
-initialization file. To tell mutt that you are subscribed to it,
-add “<span class="quote">subscribe mutt-users</span>” to your initialization file instead.
-If you also happen to get mail from someone whose address is
-<span class="emphasis"><em>mutt-users@example.com</em></span>, you could use
-“<span class="quote">lists ^mutt-users@mutt\\.org$</span>”
-or “<span class="quote">subscribe ^mutt-users@mutt\\.org$</span>” to
-match only mail from the actual list.
-</p><p>
-The <code class="literal">-group</code> flag adds all of the subsequent regular expressions
-to the named group.
-</p><p>
-The “<span class="quote">unlists</span>” command is used to remove a token from the list of
-known and subscribed mailing-lists. Use “<span class="quote">unlists *</span>” to remove all
-tokens.
-</p><p>
-To remove a mailing list from the list of subscribed mailing lists,
-but keep it on the list of known mailing lists, use “<span class="quote">unsubscribe</span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mbox-hook"></a>13. Using Multiple spool mailboxes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mbox-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to move read messages from a specified mailbox to a
-different mailbox automatically when you quit or change folders.
-<span class="emphasis"><em>pattern</em></span> is a regular expression specifying the mailbox to treat as a
-“<span class="quote">spool</span>” mailbox and <span class="emphasis"><em>mailbox</em></span> specifies where mail should be saved when
-read.
-</p><p>
-Unlike some of the other <span class="emphasis"><em>hook</em></span> commands, only the <span class="emphasis"><em>first</em></span> matching
-pattern is used (it is not possible to save read mail in more than a single
-mailbox).
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailboxes"></a>14. Monitoring incoming mail</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mailboxes</code>
-<em class="replaceable"><code>mailbox</code></em>
- [
-<em class="replaceable"><code>mailbox</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unmailboxes</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mailbox</code></em>
-... }</p></div><p>
-This command specifies folders which can receive mail and
-which will be checked for new messages periodically.
-</p><p>
-<span class="emphasis"><em>folder</em></span> can either be a local file or directory
-(Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP
-support, <span class="emphasis"><em>folder</em></span> can also be a POP/IMAP folder
-URL. The URL syntax is described in <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>,
-POP and IMAP are described in <a class="xref" href="#pop" title="3. POP3 Support">Section 3, “POP3 Support”</a> and <a class="xref" href="#imap" title="4. IMAP Support">Section 4, “IMAP Support”</a>
-respectively.
-</p><p>
-Mutt provides a number of advanced features for handling (possibly many)
-folders and new mail within them, please refer to
-<a class="xref" href="#handling-folders" title="9. Handling multiple folders">Section 9, “Handling multiple folders”</a> for details (including in what
-situations and how often Mutt checks for new mail).
-</p><p>
-The “<span class="quote">unmailboxes</span>” command is used to remove a token from the list
-of folders which receive mail. Use “<span class="quote">unmailboxes *</span>” to remove all
-tokens.
-</p><div class="note"><h3 class="title">Note</h3><p>
-The folders in the <code class="literal">mailboxes</code> command are resolved when
-the command is executed, so if these names contain <a class="link" href="#shortcuts" title="7. Mailbox Shortcuts">shortcut characters</a> (such as “<span class="quote">=</span>” and “<span class="quote">!</span>”), any variable
-definition that affects these characters (like <a class="link" href="#folder" title="3.58. folder">$folder</a> and <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a>)
-should be set before the <code class="literal">mailboxes</code> command. If
-none of these shorcuts are used, a local path should be absolute as
-otherwise mutt tries to find it relative to the directory
-from where mutt was started which may not always be desired.
-</p></div><p>
-For Mbox and Mmdf folders, new mail is detected by comparing access and/or
-modification times of files: Mutt assumes a folder has new mail if it wasn't
-accessed after it was last modified. Utilities like <code class="literal">biff</code> or
-<code class="literal">frm</code> or any other program which accesses the mailbox might cause
-Mutt to never detect new mail for that mailbox if they do not properly reset the
-access time. Other possible causes of Mutt not detecting new mail in these folders
-are backup tools (updating access times) or filesystems mounted without
-access time update support.
-</p><p>
-In cases where new mail detection for Mbox or Mmdf folders appears to be
-unreliable, the
-<a class="link" href="#check-mbox-size" title="3.24. check_mbox_size">$check_mbox_size</a>
-option can be used to make Mutt track and consult file sizes for new
-mail detection instead.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="my-hdr"></a>15. User defined headers</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">my_hdr</code>
-<em class="replaceable"><code>string</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unmy_hdr</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>field</code></em>
-... }</p></div><p>
-The <code class="literal">my_hdr</code> command allows you to create your own header
-fields which will be added to every message you send.
-</p><p>
-For example, if you would like to add an “<span class="quote">Organization:</span>” header field to
-all of your outgoing messages, you can put the command
-</p><div class="example"><a id="ex-my-hdr"></a><p class="title"><b>Example 3.10. Defining custom headers</b></p><div class="example-contents"><pre class="screen">
-my_hdr Organization: A Really Big Company, Anytown, USA
-</pre></div></div><br class="example-break" /><p>
-in your <code class="literal">.muttrc</code>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Space characters are <span class="emphasis"><em>not</em></span> allowed between the keyword and
-the colon (“<span class="quote">:</span>”). The standard for electronic mail (RFC2822) says that
-space is illegal there, so Mutt enforces the rule.
-</p></div><p>
-If you would like to add a header field to a single message, you should
-either set the <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable,
-or use the <code class="literal"><edit-headers></code> function (default: “<span class="quote">E</span>”) in the compose menu so
-that you can edit the header of your message along with the body.
-</p><p>
-To remove user defined header fields, use the <code class="literal">unmy_hdr</code>
-command. You may specify an asterisk (“<span class="quote">*</span>”) to remove all header
-fields, or the fields to remove. For example, to remove all “<span class="quote">To</span>” and
-“<span class="quote">Cc</span>” header fields, you could use:
-</p><pre class="screen">
-unmy_hdr to cc
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="save-hook"></a>16. Specify default save mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">save-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to override the default mailbox used when saving
-messages. <span class="emphasis"><em>mailbox</em></span> will be used as the default if the message
-matches <span class="emphasis"><em>pattern</em></span>, see <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information
-on the exact format.
-</p><p>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to
-<span class="emphasis"><em>mailbox</em></span> after it was expanded.
-</p><p>
-Examples:
-</p><div class="example"><a id="ex-save-hook-exando"></a><p class="title"><b>Example 3.11. Using %-expandos in <code class="literal">save-hook</code></b></p><div class="example-contents"><pre class="screen">
-# default: save all to ~/Mail/<author name>
-save-hook . ~/Mail/%F
-
-# save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
-save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
-# save from aol.com to $folder/spam
-save-hook aol\\.com$ +spam
-</pre></div></div><br class="example-break" /><p>
-Also see the <a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-hook"></a>17. Specify default Fcc: mailbox when composing</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to save outgoing mail in a mailbox other than
-<a class="link" href="#record" title="3.242. record">$record</a>. Mutt searches the initial list of
-message recipients for the first matching <span class="emphasis"><em>regexp</em></span> and uses <span class="emphasis"><em>mailbox</em></span>
-as the default Fcc: mailbox. If no match is found the message will be saved
-to <a class="link" href="#record" title="3.242. record">$record</a> mailbox.
-</p><p>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to
-<span class="emphasis"><em>mailbox</em></span> after it was expanded.
-</p><p>
-See <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information on the exact format of <span class="emphasis"><em>pattern</em></span>.
-</p><p>
-Example: <code class="literal">fcc-hook [@.]aol\\.com$ +spammers</code>
-</p><p>
-The above will save a copy of all messages going to the aol.com domain to
-the `+spammers' mailbox by default. Also see the <a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-save-hook"></a>18. Specify default save filename and default Fcc: mailbox at once</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-save-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is a shortcut, equivalent to doing both a <a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
-and a <a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a> with its arguments,
-including %-expansion on <span class="emphasis"><em>mailbox</em></span> according
-to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="send-hook"></a>19. Change settings based upon message recipients</h2></div></div></div><a id="reply-hook"></a><a id="send2-hook"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">reply-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">send-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">send2-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-These commands can be used to execute arbitrary configuration commands based
-upon recipients of the message. <span class="emphasis"><em>pattern</em></span> is used to match
-the message, see <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for details. <span class="emphasis"><em>command</em></span>
-is executed when <span class="emphasis"><em>pattern</em></span> matches.
-</p><p>
-<code class="literal">reply-hook</code> is matched against the message you are <span class="emphasis"><em>replying to</em></span>,
-instead of the message you are <span class="emphasis"><em>sending</em></span>. <code class="literal">send-hook</code> is
-matched against all messages, both <span class="emphasis"><em>new</em></span>
-and <span class="emphasis"><em>replies</em></span>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-<code class="literal">reply-hook</code>s are matched <span class="bold"><strong>before</strong></span> the <code class="literal">send-hook</code>, <span class="bold"><strong>regardless</strong></span>
-of the order specified in the user's configuration file.
-</p></div><p>
-<code class="literal">send2-hook</code> is matched every time a message is changed, either
-by editing it, or by using the compose menu to change its recipients
-or subject. <code class="literal">send2-hook</code> is executed after <code class="literal">send-hook</code>, and
-can, e.g., be used to set parameters such as the <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> variable depending on the message's sender
-address.
-</p><p>
-For each type of <code class="literal">send-hook</code> or <code class="literal">reply-hook</code>, when multiple matches
-occur, commands are executed in the order they are specified in the muttrc
-(for that type of hook).
-</p><p>
-Example: <code class="literal">send-hook mutt "set mime_forward signature=''"</code>
-</p><p>
-Another typical use for this command is to change the values of the
-<a class="link" href="#attribution" title="3.16. attribution">$attribution</a>, <a class="link" href="#signature" title="3.265. signature">$signature</a> and <a class="link" href="#locale" title="3.104. locale">$locale</a>
-variables in order to change the language of the attributions and
-signatures based upon the recipients.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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
-<code class="literal">my_hdr</code> 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.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="message-hook"></a>20. Change settings before formatting a message</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">message-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-This command can be used to execute arbitrary configuration commands
-before viewing or formatting a message based upon information about the message.
-<span class="emphasis"><em>command</em></span> is executed if the <span class="emphasis"><em>pattern</em></span> matches the message to be
-displayed. When multiple matches occur, commands are executed in the order
-they are specified in the muttrc.
-</p><p>
-See <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for
-information on the exact format of <span class="emphasis"><em>pattern</em></span>.
-</p><p>
-Example:
-</p><pre class="screen">
-message-hook ~A 'set pager=builtin'
-message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="crypt-hook"></a>21. Choosing the cryptographic key of the recipient</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">crypt-hook</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>keyid</code></em>
- </p></div><p>
-When encrypting messages with PGP/GnuPG 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 would
-normally use. The <code class="literal">crypt-hook</code> 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.
-</p><p>
-The meaning of <span class="emphasis"><em>keyid</em></span> 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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="push"></a>22. Adding key sequences to the keyboard buffer</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">push</code>
-<em class="replaceable"><code>string</code></em>
- </p></div><p>
-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 <a class="link" href="#macro" title="8. Keyboard macros">macro</a> 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:
-</p><div class="example"><a id="ex-folder-hook-push"></a><p class="title"><b>Example 3.12. Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></b></p><div class="example-contents"><pre class="screen">
-folder-hook . 'push <collapse-all>'
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exec"></a>23. Executing functions</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">exec</code>
-<em class="replaceable"><code>function</code></em>
- [
-<em class="replaceable"><code>function</code></em>
-...]</p></div><p>
-This command can be used to execute any function. Functions are
-listed in the <a class="link" href="#functions" title="4. Functions">function reference</a>.
-“<span class="quote">exec function</span>” is equivalent to “<span class="quote">push <function></span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="score-command"></a>24. Message Scoring</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">score</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>value</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unscore</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-The <code class="literal">score</code> commands adds <span class="emphasis"><em>value</em></span> to a message's score if <span class="emphasis"><em>pattern</em></span>
-matches it. <span class="emphasis"><em>pattern</em></span> is a string in the format described in the <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> section (note: For efficiency reasons, patterns
-which scan information not available in the index, such as <code class="literal">˜b</code>,
-<code class="literal">˜B</code> or <code class="literal">˜h</code>, may not be used). <span class="emphasis"><em>value</em></span> is a
-positive or negative integer. A message's final score is the sum total of all
-matching <code class="literal">score</code> entries. However, you may optionally prefix <span class="emphasis"><em>value</em></span> with
-an equal sign (=) to cause evaluation to stop at a particular entry if there is
-a match. Negative final scores are rounded up to 0.
-</p><p>
-The <code class="literal">unscore</code> command removes score entries from the list. You <span class="bold"><strong>must</strong></span>
-specify the same pattern specified in the <code class="literal">score</code> command for it to be
-removed. The pattern “<span class="quote">*</span>” is a special token which means to clear the list
-of all score entries.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="spam"></a>25. Spam detection</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">spam</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>format</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">nospam</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
- }</p></div><p>
-Mutt has generalized support for external spam-scoring filters.
-By defining your spam patterns with the <code class="literal">spam</code> and <code class="literal">nospam</code>
-commands, you can <span class="emphasis"><em>limit</em></span>, <span class="emphasis"><em>search</em></span>, and <span class="emphasis"><em>sort</em></span> 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 <code class="literal">%H</code> selector in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable. (Tip: try <code class="literal">%?H?[%H] ?</code>
-to display spam tags only when they are defined for a given message.)
-</p><p>
-Your first step is to define your external filter's spam patterns using
-the <code class="literal">spam</code> command. <span class="emphasis"><em>pattern</em></span> 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 “<span class="quote">spam tag</span>” or
-“<span class="quote">spam attribute</span>” (unless it also matches a <code class="literal">nospam</code> pattern -- see
-below.) The appearance of this attribute is entirely up to you, and is
-governed by the <span class="emphasis"><em>format</em></span> parameter. <span class="emphasis"><em>format</em></span> can be any static
-text, but it also can include back-references from the <span class="emphasis"><em>pattern</em></span>
-expression. (A regular expression “<span class="quote">back-reference</span>” refers to a
-sub-expression contained within parentheses.) <code class="literal">%1</code> is replaced with
-the first back-reference in the regex, <code class="literal">%2</code> with the second, etc.
-</p><p>
-If you're using multiple spam filters, a message can have more than
-one spam-related header. You can define <code class="literal">spam</code> 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 <span class="emphasis"><em>format</em></span> strings joined
-together, with the value of $spam_separator separating
-them.
-</p><p>
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-define these spam settings:
-</p><div class="example"><a id="ex-spam"></a><p class="title"><b>Example 3.13. Configuring spam detection</b></p><div class="example-contents"><pre class="screen">
-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=", "
-</pre></div></div><br class="example-break" /><p>
-If I then received a message that DCC registered with “<span class="quote">many</span>” hits
-under the “<span class="quote">Fuz2</span>” checksum, and that PureMessage registered with a
-97% probability of being spam, that message's spam tag would read
-<code class="literal">90+/DCC-Fuz2, 97/PM</code>. (The four characters before “<span class="quote">=many</span>” in a
-DCC report indicate the checksum used -- in this case, “<span class="quote">Fuz2</span>”.)
-</p><p>
-If the $spam_separator variable is unset, then each
-spam pattern match supersedes the previous one. Instead of getting
-joined <span class="emphasis"><em>format</em></span> strings, you'll get only the last one to match.
-</p><p>
-The spam tag is what will be displayed in the index when you use
-<code class="literal">%H</code> in the <code class="literal">$index_format</code> variable. It's also the
-string that the <code class="literal">˜H</code> pattern-matching expression matches against for
-<code class="literal"><search></code> and <code class="literal"><limit></code> functions. And it's what sorting by spam
-attribute will use as a sort key.
-</p><p>
-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.
-</p><p>
-Generally, when you sort by spam tag, mutt will sort <span class="emphasis"><em>lexically</em></span> --
-that is, by ordering strings alphanumerically. 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
-<code class="literal">sort -n</code>.) A message with no spam attributes at all -- that is, one
-that didn't match <span class="emphasis"><em>any</em></span> of your <code class="literal">spam</code> patterns -- is sorted at
-lowest priority. Numbers are sorted next, beginning with 0 and ranging
-upward. Finally, non-numeric strings are sorted, with “<span class="quote">a</span>” taking lower
-priority than “<span class="quote">z</span>”. 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.
-</p><p>
-The <code class="literal">nospam</code> command can be used to write exceptions to <code class="literal">spam</code>
-patterns. If a header pattern matches something in a <code class="literal">spam</code> command,
-but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a <code class="literal">nospam</code> command.
-</p><p>
-If the <span class="emphasis"><em>pattern</em></span> given to <code class="literal">nospam</code> is exactly the same as the
-<span class="emphasis"><em>pattern</em></span> on an existing <code class="literal">spam</code> list entry, the effect will be to
-remove the entry from the spam list, instead of adding an exception.
-Likewise, if the <span class="emphasis"><em>pattern</em></span> for a <code class="literal">spam</code> command matches an entry
-on the <code class="literal">nospam</code> list, that <code class="literal">nospam</code> entry will be removed. If the
-<span class="emphasis"><em>pattern</em></span> for <code class="literal">nospam</code> is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries on both lists</em></span>
-will be removed. This might be the default action if you use <code class="literal">spam</code>
-and <code class="literal">nospam</code> in conjunction with a <code class="literal">folder-hook</code>.
-</p><p>
-You can have as many <code class="literal">spam</code> or <code class="literal">nospam</code> commands as you like.
-You can even do your own primitive spam detection within mutt -- for
-example, if you consider all mail from <code class="literal">MAILER-DAEMON</code> to be spam,
-you can use a <code class="literal">spam</code> command like this:
-</p><pre class="screen">
-spam "^From: .*MAILER-DAEMON" "999"
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="set"></a>26. Setting and Querying Variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-commands"></a>26.1. Commands</h3></div></div></div><p>
-The following commands are available to manipulate and query variables:
-</p><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">set</code> {
-[ <code class="option">no</code> | <code class="option">inv</code> ]
-<em class="replaceable"><code>variable</code></em>
- |
-<em class="replaceable"><code>variable=value</code></em>
- } [...]</p></div><div class="cmdsynopsis"><p><code class="command">toggle</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unset</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">reset</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><p>
-This command is used to set (and unset) <a class="link" href="#variables" title="3. Configuration variables">configuration variables</a>. There are four basic types of variables:
-boolean, number, string and quadoption. <span class="emphasis"><em>boolean</em></span> variables can be
-<span class="emphasis"><em>set</em></span> (true) or <span class="emphasis"><em>unset</em></span> (false). <span class="emphasis"><em>number</em></span> variables can be
-assigned a positive integer value.
-<span class="emphasis"><em>string</em></span> variables consist of any number of printable characters and
-must be enclosed in quotes if they contain spaces or tabs. You
-may also use the escape sequences “<span class="quote">\n</span>” and “<span class="quote">\t</span>” for newline and tab, respectively.
-<span class="emphasis"><em>quadoption</em></span> variables are used to control whether or not to be prompted
-for certain actions, or to specify a default action. A value of <span class="emphasis"><em>yes</em></span>
-will cause the action to be carried out automatically as if you had answered
-yes to the question. Similarly, a value of <span class="emphasis"><em>no</em></span> will cause the
-action to be carried out as if you had answered “<span class="quote">no.</span>” A value of
-<span class="emphasis"><em>ask-yes</em></span> will cause a prompt with a default answer of “<span class="quote">yes</span>” and
-<span class="emphasis"><em>ask-no</em></span> will provide a default answer of “<span class="quote">no.</span>”
-</p><p>
-Prefixing a variable with “<span class="quote">no</span>” will unset it. Example: <code class="literal">set noaskbcc</code>.
-</p><p>
-For <span class="emphasis"><em>boolean</em></span> variables, you may optionally prefix the variable name with
-<code class="literal">inv</code> to toggle the value (on or off). This is useful when writing
-macros. Example: <code class="literal">set invsmart_wrap</code>.
-</p><p>
-The <code class="literal">toggle</code> command automatically prepends the <code class="literal">inv</code> prefix to all
-specified variables.
-</p><p>
-The <code class="literal">unset</code> command automatically prepends the <code class="literal">no</code> prefix to all
-specified variables.
-</p><p>
-Using the <code class="literal"><enter-command></code> function in the <span class="emphasis"><em>index</em></span> menu, you can query the
-value of a variable by prefixing the name of the variable with a question
-mark:
-</p><pre class="screen">
-set ?allow_8bit
-</pre><p>
-The question mark is actually only required for boolean and quadoption
-variables.
-</p><p>
-The <code class="literal">reset</code> command resets all given variables to the compile time
-defaults (hopefully mentioned in this manual). If you use the command
-<code class="literal">set</code> and prefix the variable with “<span class="quote">&</span>” this has the same
-behavior as the reset command.
-</p><p>
-With the <code class="literal">reset</code> command there exists the special variable “<span class="quote">all</span>”,
-which allows you to reset all variables to their system defaults.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-myvar"></a>26.2. User-defined variables</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-intro"></a>26.2.1. Introduction</h4></div></div></div><p>
-Along with the variables listed in the
-<a class="link" href="#variables" title="3. Configuration variables">Configuration variables</a> section, mutt
-supports user-defined variables with names starting
-with <code class="literal">my_</code> as in, for
-example, <code class="literal">my_cfgdir</code>.
-</p><p>
-The <code class="literal">set</code> command either creates a
-custom <code class="literal">my_</code> variable or changes its
-value if it does exist already. The <code class="literal">unset</code> and <code class="literal">reset</code>
-commands remove the variable entirely.
-</p><p>
-Since user-defined variables are expanded in the same way that
-environment variables are (except for
-the <a class="link" href="#shell-escape">shell-escape</a> command and
-backtick expansion), this feature can be used to make configuration
-files more readable.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-examples"></a>26.2.2. Examples</h4></div></div></div><p>
-The following example defines and uses the variable <code class="literal">my_cfgdir</code>
-to abbreviate the calls of the <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> command:
-</p><div class="example"><a id="ex-myvar1"></a><p class="title"><b>Example 3.14. Using user-defined variables for config file readability</b></p><div class="example-contents"><pre class="screen">
-set my_cfgdir = $HOME/mutt/config
-
-source $my_cfgdir/hooks
-source $my_cfgdir/macros
-# more source commands...
-</pre></div></div><br class="example-break" /><p>
-A custom variable can also be used in macros to backup the current value
-of another variable. In the following example, the value of the
-<a class="link" href="#delete" title="3.42. delete">$delete</a> is changed temporarily
-while its original value is saved as <code class="literal">my_delete</code>.
-After the macro has executed all commands, the original value of <a class="link" href="#delete" title="3.42. delete">$delete</a> is restored.
-</p><div class="example"><a id="ex-myvar2"></a><p class="title"><b>Example 3.15. Using user-defined variables for backing up other config option values</b></p><div class="example-contents"><pre class="screen">
-macro pager ,x '\
-<enter-command>set my_delete=$delete<enter>\
-<enter-command>set delete=yes<enter>\
-...\
-<enter-command>set delete=$my_delete<enter>'
-</pre></div></div><br class="example-break" /><p>
-Since mutt expands such values already when parsing the configuration
-file(s), the value of <code class="literal">$my_delete</code> in the
-last example would be the value of <code class="literal">$delete</code> exactly
-as it was at that point during parsing the configuration file. If
-another statement would change the value for <code class="literal">$delete</code>
-later in the same or another file, it would have no effect on
-<code class="literal">$my_delete</code>. However, the expansion can
-be deferred to runtime, as shown in the next example, when escaping the
-dollar sign.
-</p><div class="example"><a id="ex-myvar3"></a><p class="title"><b>Example 3.16. Deferring user-defined variable expansion to runtime</b></p><div class="example-contents"><pre class="screen">
-macro pager <PageDown> "\
-<enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
-<next-page>\
-<enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
-<enter-command> unset my_old_pager_stop<Enter>"
-</pre></div></div><br class="example-break" /><p>
-Note that there is a space
-between <code class="literal"><enter-command></code> and
-the <code class="literal">set</code> configuration command, preventing mutt from
-recording the macro's commands into its history.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="source"></a>27. Reading initialization commands from another file</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">source</code>
-<em class="replaceable"><code>filename</code></em>
- </p></div><p>
-This command allows the inclusion of initialization commands
-from other files. For example, I place all of my aliases in
-<code class="literal">˜/.mail_aliases</code> so that I can make my
-<code class="literal">˜/.muttrc</code> readable and keep my aliases private.
-</p><p>
-If the filename begins with a tilde (“<span class="quote">˜</span>”), it will be expanded to the
-path of your home directory.
-</p><p>
-If the filename ends with a vertical bar (|), then <span class="emphasis"><em>filename</em></span> is
-considered to be an executable program from which to read input (eg.
-<code class="literal">source ˜/bin/myscript|</code>).
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ifdef"></a>28. Configuring features conditionnaly</h2></div></div></div><p>
-Usage: <code class="literal">ifdef</code> <span class="emphasis"><em>item</em></span> <span class="emphasis"><em>command</em></span>
-</p><p>
-This command allows to test if a feature has been compiled in, before
-actually executing the command. Item can be either the name of a
-function, variable, or command. Example:
-</p><p>
-</p><pre class="screen">
-ifdef imap_keepalive 'source ~/.mutt/imap_setup'
-</pre><p>
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="unhook"></a>29. Removing hooks</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">unhook</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>hook-type</code></em>
- }</p></div><p>
-This command permits you to flush hooks you have previously defined.
-You can either remove all hooks by giving the “<span class="quote">*</span>” character as an
-argument, or you can remove all hooks of a specific type by saying
-something like <code class="literal">unhook send-hook</code>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="formatstrings"></a>30. Format Strings</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-basics"></a>30.1. Basic usage</h3></div></div></div><p>
-Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
-<a class="link" href="#index-format" title="3.101. index_format">$index_format</a>,
-<a class="link" href="#pager-format" title="3.140. pager_format">$pager_format</a>,
-<a class="link" href="#status-format" title="3.281. status_format">$status_format</a>,
-and other “<span class="quote">*_format</span>” variables. These can be very straightforward,
-and it's quite possible you already know how to use them.
-</p><p>
-The most basic format string element is a percent symbol followed
-by another character. For example, <code class="literal">%s</code>
-represents a message's Subject: header in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable. The
-“<span class="quote">expandos</span>” available are documented with each format variable, but
-there are general modifiers available with all formatting expandos,
-too. Those are our concern here.
-</p><p>
-Some of the modifiers are borrowed right out of C (though you might
-know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in <code class="literal">%-12.12s</code>. As with
-such programming languages, these modifiers allow you to specify the
-minimum and maximum size of the resulting string, as well as its
-justification. If the “<span class="quote">-</span>” sign follows the percent, the string will
-be left-justified instead of right-justified. If there's a number
-immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
-will be padded out with spaces. If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
-permitted to exceed that width, no matter its natural size. Each of
-these three elements is optional, so that all these are legal format
-strings:
-<code class="literal">%-12s</code>
-<code class="literal">%4c</code>
-<code class="literal">%.15F</code>
-<code class="literal">%-12.15L</code>
-</p><p>
-Mutt adds some other modifiers to format strings. If you use an equals
-symbol (<code class="literal">=</code>) as a numeric prefix (like the minus
-above), it will force the string to be centered within its minimum
-space range. For example, <code class="literal">%=14y</code> will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-<code class="literal">$index_format</code>. If the expansion
-results in a string less than 14 characters, it will be centered in a
-14-character space. If the X-Label for a message were "test", that
-expansion would look like “<span class="quote"> test </span>”.
-</p><p>
-There are two very little-known modifiers that affect the way that an
-expando is replaced. If there is an underline (“<span class="quote">_</span>”) character
-between any format modifiers (as above) and the expando letter, it will
-expands in all lower case. And if you use a colon (“<span class="quote">:</span>”), it will
-replace all decimal points with underlines.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-filters"></a>30.2. Filters</h3></div></div></div><p>
-Any format string ending in a vertical bar (“<span class="quote">|</span>”) will be
-expanded and piped through the first word in the string, using spaces
-as separator. The string returned will be used for display.
-If the returned string ends in %, it will be passed through
-the formatter a second time. This allows the filter to generate a
-replacement format string including % expandos.
-</p><p>
-All % expandos in a format string are expanded before the script
-is called so that:
-</p><div class="example"><a id="ex-fmtpipe"></a><p class="title"><b>Example 3.17. Using external filters in format strings</b></p><div class="example-contents"><pre class="screen">
-set status_format="script.sh '%r %f (%L)'|"
-</pre></div></div><br class="example-break" /><p>
-will make mutt expand <code class="literal">%r</code>,
-<code class="literal">%f</code> and <code class="literal">%L</code>
-before calling the script. The example also shows that arguments can be
-quoted: the script will receive the expanded string between the single quotes
-as the only argument.
-</p><p>
-A practical example is the <code class="literal">mutt_xtitle</code>
-script installed in the <code class="literal">samples</code>
-subdirectory of the mutt documentation: it can be used as filter for
-<code class="literal">$status_format</code> to set the current
-terminal's title, if supported.
-</p></div></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="advancedusage"></a>Chapter 4. Advanced Usage</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="regexp"></a>1. Regular Expressions</h2></div></div></div><p>
-All string patterns in Mutt including those in more complex
-<a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> must be specified
-using regular expressions (regexp) in the “<span class="quote">POSIX extended</span>” 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.
-</p><p>
-The search is case sensitive if the pattern contains at least one upper
-case letter, and case insensitive otherwise.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that “<span class="quote">\</span>”
-must be quoted if used for a regular expression in an initialization
-command: “<span class="quote">\\</span>”.
-</p></div><p>
-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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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 <a class="xref" href="#muttrc-syntax" title="2. Syntax of Initialization Files">Syntax of Initialization Files</a>
-for more information on " and ' delimiter processing. To match a
-literal " or ' you must preface it with \ (backslash).
-</p></div><p>
-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.
-</p><p>
-The period “<span class="quote">.</span>” matches any single character. The caret “<span class="quote">^</span>” and
-the dollar sign “<span class="quote">$</span>” are metacharacters that respectively match
-the empty string at the beginning and end of a line.
-</p><p>
-A list of characters enclosed by “<span class="quote">[</span>” and “<span class="quote">]</span>” matches any
-single character in that list; if the first character of the list
-is a caret “<span class="quote">^</span>” then it matches any character <span class="bold"><strong>not</strong></span> in the
-list. For example, the regular expression <span class="bold"><strong>[0123456789]</strong></span>
-matches any single digit. A range of ASCII characters may be specified
-by giving the first and last characters, separated by a hyphen
-“<span class="quote">-</span>”. Most metacharacters lose their special meaning inside
-lists. To include a literal “<span class="quote">]</span>” place it first in the list.
-Similarly, to include a literal “<span class="quote">^</span>” place it anywhere but first.
-Finally, to include a literal hyphen “<span class="quote">-</span>” place it last.
-</p><p>
-Certain named classes of characters are predefined. Character classes
-consist of “<span class="quote">[:</span>”, a keyword denoting the class, and “<span class="quote">:]</span>”.
-The following classes are defined by the POSIX standard in
-<a class="xref" href="#posix-regex-char-classes" title="Table 4.1. POSIX regular expression character classes">Table 4.1, “POSIX regular expression character classes”</a>
-</p><div class="table"><a id="posix-regex-char-classes"></a><p class="title"><b>Table 4.1. POSIX regular expression character classes</b></p><div class="table-contents"><table summary="POSIX regular expression character classes" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Character class</th><th>Description</th></tr></thead><tbody><tr><td>[:alnum:]</td><td>Alphanumeric characters</td></tr><tr><td>[:alpha:]</td><td>Alphabetic characters</td></tr><tr><td>[:blank:]</td><td>Space or tab characters</td></tr><tr><td>[:cntrl:]</td><td>Control characters</td></tr><tr><td>[:digit:]</td><td>Numeric characters</td></tr><tr><td>[:graph:]</td><td>Characters that are both printable and visible. (A space is printable, but not visible, while an “<span class="quote">a</span>” is both)</td></tr><tr><td>[:lower:]</td><td>Lower-case alphabetic characters</td></tr><tr><td>[:print:]</td><td>Printable characters (characters that are not control characters)</td></tr><tr><td>[:punct:]</td><td>Punctuation characters (characters that are not letter, digits, control characters, or space characters)</td></tr><tr><td>[:space:]</td><td>Space characters (such as space, tab and formfeed, to name a few)</td></tr><tr><td>[:upper:]</td><td>Upper-case alphabetic characters</td></tr><tr><td>[:xdigit:]</td><td>Characters that are hexadecimal digits</td></tr></tbody></table></div></div><br class="table-break" /><p>
-A character class is only valid in a regular expression inside the
-brackets of a character list.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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, <span class="bold"><strong>[[:digit:]]</strong></span> is equivalent to
-<span class="bold"><strong>[0-9]</strong></span>.
-</p></div><p>
-Two additional special sequences can appear in character lists. These
-apply to non-ASCII character sets, which can have single symbols (called
-collating elements) that are represented with more than one character,
-as well as several characters that are equivalent for collating or
-sorting purposes:
-</p><div class="variablelist"><dl><dt><span class="term">Collating Symbols</span></dt><dd><p>
-A collating symbol is a multi-character collating element enclosed in
-“<span class="quote">[.</span>” and “<span class="quote">.]</span>”. For example, if “<span class="quote">ch</span>” is a collating
-element, then <span class="bold"><strong>[[.ch.]]</strong></span> is a regexp that matches
-this collating element, while <span class="bold"><strong>[ch]</strong></span> is a regexp that
-matches either “<span class="quote">c</span>” or “<span class="quote">h</span>”.
-</p></dd><dt><span class="term">Equivalence Classes</span></dt><dd><p>
-An equivalence class is a locale-specific name for a list of
-characters that are equivalent. The name is enclosed in “<span class="quote">[=</span>”
-and “<span class="quote">=]</span>”. For example, the name “<span class="quote">e</span>” might be used to
-represent all of “<span class="quote">è</span>” “<span class="quote">é</span>” and “<span class="quote">e</span>”. In this case,
-<span class="bold"><strong>[[=e=]]</strong></span> is a regexp that matches any of
-“<span class="quote">è</span>”, “<span class="quote">é</span>” and “<span class="quote">e</span>”.
-</p></dd></dl></div><p>
-A regular expression matching a single character may be followed by one
-of several repetition operators described in <a class="xref" href="#regex-repeat" title="Table 4.2. Regular expression repetition operators">Table 4.2, “Regular expression repetition operators”</a>.
-</p><div class="table"><a id="regex-repeat"></a><p class="title"><b>Table 4.2. Regular expression repetition operators</b></p><div class="table-contents"><table summary="Regular expression repetition operators" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Operator</th><th>Description</th></tr></thead><tbody><tr><td>?</td><td>The preceding item is optional and matched at most once</td></tr><tr><td>*</td><td>The preceding item will be matched zero or more times</td></tr><tr><td>+</td><td>The preceding item will be matched one or more times</td></tr><tr><td>{n}</td><td>The preceding item is matched exactly <span class="emphasis"><em>n</em></span> times</td></tr><tr><td>{n,}</td><td>The preceding item is matched <span class="emphasis"><em>n</em></span> or more times</td></tr><tr><td>{,m}</td><td>The preceding item is matched at most <span class="emphasis"><em>m</em></span> times</td></tr><tr><td>{n,m}</td><td>The preceding item is matched at least <span class="emphasis"><em>n</em></span> times, but no more than <span class="emphasis"><em>m</em></span> times</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Two regular expressions may be concatenated; the resulting regular
-expression matches any string formed by concatenating two substrings
-that respectively match the concatenated subexpressions.
-</p><p>
-Two regular expressions may be joined by the infix operator “<span class="quote">|</span>”;
-the resulting regular expression matches any string matching either
-subexpression.
-</p><p>
-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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you compile Mutt with the GNU <span class="emphasis"><em>rx</em></span> package, the
-following operators may also be used in regular expressions as described in <a class="xref" href="#regex-gnu-ext" title="Table 4.3. GNU regular expression extensions">Table 4.3, “GNU regular expression extensions”</a>.
-</p></div><div class="table"><a id="regex-gnu-ext"></a><p class="title"><b>Table 4.3. GNU regular expression extensions</b></p><div class="table-contents"><table summary="GNU regular expression extensions" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Expression</th><th>Description</th></tr></thead><tbody><tr><td>\\y</td><td>Matches the empty string at either the beginning or the end of a word</td></tr><tr><td>\\B</td><td>Matches the empty string within a word</td></tr><tr><td>\\<</td><td>Matches the empty string at the beginning of a word</td></tr><tr><td>\\></td><td>Matches the empty string at the end of a word</td></tr><tr><td>\\w</td><td>Matches any word-constituent character (letter, digit, or underscore)</td></tr><tr><td>\\W</td><td>Matches any character that is not word-constituent</td></tr><tr><td>\\`</td><td>Matches the empty string at the beginning of a buffer (string)</td></tr><tr><td>\\'</td><td>Matches the empty string at the end of a buffer</td></tr></tbody></table></div></div><br class="table-break" /><p>
-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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="patterns"></a>2. Patterns: Searching, Limiting and Tagging</h2></div></div></div><p>
-Many of Mutt's commands allow you to specify a pattern to match
-(<code class="literal">limit</code>, <code class="literal">tag-pattern</code>,
-<code class="literal">delete-pattern</code>, etc.). <a class="xref" href="#tab-patterns" title="Table 4.4. Pattern modifiers">Table 4.4, “Pattern modifiers”</a>
-shows several ways to select messages.
-</p><div class="table"><a id="tab-patterns"></a><p class="title"><b>Table 4.4. Pattern modifiers</b></p><div class="table-contents"><table summary="Pattern modifiers" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Pattern modifier</th><th>Description</th></tr></thead><tbody><tr><td>~A</td><td>all messages</td></tr><tr><td>~b <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message body</td></tr><tr><td>=b <span class="emphasis"><em>STRING</em></span></td><td>messages which contain <span class="emphasis"><em>STRING</em></span> in the message body. If IMAP is enabled, searches for <span class="emphasis"><em>STRING</em></span> on the server, rather than downloading each message and searching it locally.</td></tr><tr><td>~B <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the whole message</td></tr><tr><td>~c <span class="emphasis"><em>EXPR</em></span></td><td>messages carbon-copied to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%c <span class="emphasis"><em>GROUP</em></span></td><td>messages carbon-copied to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~C <span class="emphasis"><em>EXPR</em></span></td><td>messages either to: or cc: <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%C <span class="emphasis"><em>GROUP</em></span></td><td>messages either to: or cc: to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~d [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-sent</span>” in a Date range</td></tr><tr><td>~D</td><td>deleted messages</td></tr><tr><td>~e <span class="emphasis"><em>EXPR</em></span></td><td>messages which contains <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>%e <span class="emphasis"><em>GROUP</em></span></td><td>messages which contain a member of <span class="emphasis"><em>GROUP</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>~E</td><td>expired messages</td></tr><tr><td>~F</td><td>flagged messages</td></tr><tr><td>~f <span class="emphasis"><em>EXPR</em></span></td><td>messages originating from <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%f <span class="emphasis"><em>GROUP</em></span></td><td>messages originating from any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~g</td><td>cryptographically signed messages</td></tr><tr><td>~G</td><td>cryptographically encrypted messages</td></tr><tr><td>~h <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message header</td></tr><tr><td>~H <span class="emphasis"><em>EXPR</em></span></td><td>messages with a spam attribute matching <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~i <span class="emphasis"><em>EXPR</em></span></td><td>messages which match <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Message-ID</span>” field</td></tr><tr><td>~k</td><td>messages which contain PGP key material</td></tr><tr><td>~L <span class="emphasis"><em>EXPR</em></span></td><td>messages either originated or received by <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%L <span class="emphasis"><em>GROUP</em></span></td><td>message either originated or received by any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~l</td><td>messages addressed to a known mailing list</td></tr><tr><td>~m [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~n [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a score in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~N</td><td>new messages</td></tr><tr><td>~O</td><td>old messages</td></tr><tr><td>~p</td><td>messages addressed to you (consults alternates)</td></tr><tr><td>~P</td><td>messages from you (consults alternates)</td></tr><tr><td>~Q</td><td>messages which have been replied to</td></tr><tr><td>~r [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-received</span>” in a Date range</td></tr><tr><td>~R</td><td>read messages</td></tr><tr><td>~s <span class="emphasis"><em>EXPR</em></span></td><td>messages having <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Subject</span>” field.</td></tr><tr><td>~S</td><td>superseded messages</td></tr><tr><td>~t <span class="emphasis"><em>EXPR</em></span></td><td>messages addressed to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~T</td><td>tagged messages</td></tr><tr><td>~u</td><td>messages addressed to a subscribed mailing list</td></tr><tr><td>~U</td><td>unread messages</td></tr><tr><td>~v</td><td>messages part of a collapsed thread.</td></tr><tr><td>~V</td><td>cryptographically verified messages</td></tr><tr><td>~x <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">References</span>” field</td></tr><tr><td>~X [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> attachments *)</td></tr><tr><td>~y <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">X-Label</span>” field</td></tr><tr><td>~z [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a size in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~=</td><td>duplicated messages (see <a class="link" href="#duplicate-threads" title="3.49. duplicate_threads">$duplicate_threads</a>)</td></tr><tr><td>~$</td><td>unreferenced messages (requires threaded view)</td></tr><tr><td>~(<span class="emphasis"><em>PATTERN</em></span>)</td><td>messages in threads
-containing messages matching <span class="emphasis"><em>PATTERN</em></span>, e.g. all
-threads containing messages from you: ~(~P)</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Where <span class="emphasis"><em>EXPR</em></span> is a
-<a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a>. Special attention has to be
-made when using regular expressions inside of patterns. Specifically,
-Mutt's parser for these patterns will strip one level of backslash (“<span class="quote">\</span>”),
-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 (“<span class="quote">\\</span>”). You can force mutt to treat <span class="emphasis"><em>EXPR</em></span> as a simple string
-instead of a regular expression by using = instead of ˜ in the
-pattern name. For example, <code class="literal">=b *.*</code> will find all messages that contain
-the literal string “<span class="quote">*.*</span>”. Simple string matches are less powerful than
-regular expressions but can be considerably faster. This is especially
-true for IMAP folders, because string matches can be performed on the
-server instead of by fetching every message. IMAP treats <code class="literal">=h</code> specially:
-it must be of the form "header: substring" and will not partially
-match header names. The substring part may be omitted if you simply
-wish to find messages containing a particular header without regard to
-its value.
-</p><p>
-*) The forms “<span class="quote"><[<span class="emphasis"><em>MAX</em></span>]</span>”, “<span class="quote">>[<span class="emphasis"><em>MIN</em></span>]</span>”,
-“<span class="quote">[<span class="emphasis"><em>MIN</em></span>]-</span>” and “<span class="quote">-[<span class="emphasis"><em>MAX</em></span>]</span>”
-are allowed, too.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="patterns-modifier"></a>2.1. Pattern Modifier</h3></div></div></div><div class="note"><h3 class="title">Note</h3><p>
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
-match if there is at least one match in the whole list. If you want to
-make sure that all elements of that list match, you need to prefix your
-pattern with “<span class="quote">^</span>”.
-This example matches all mails which only has recipients from Germany.
-</p></div><pre class="screen">
-^~C \.de$
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-patterns"></a>2.2. Simple Patterns</h3></div></div></div><p>
-Mutt supports two versions of so called “<span class="quote">simple searches</span>” which are
-issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
-one of these characters: “<span class="quote">˜</span>”, “<span class="quote">=</span>” or “<span class="quote">%</span>”). If the query is
-supposed to contain one of these special characters, they must be escaped
-by prepending a backslash (“<span class="quote">\</span>”).
-</p><p>
-The first type is by checking whether the query string equals
-a keyword case-insensitively from <a class="xref" href="#tab-simplesearch-keywords" title="Table 4.5. Simple search keywords">Table 4.5, “Simple search keywords”</a>:
-If that is the case, Mutt will use the shown pattern modifier instead.
-If a keyword would conflict with your search keyword, you need to turn
-it into a regular expression to avoid matching the keyword table. For
-example, if you want to find all messages matching “<span class="quote">flag</span>”
-(using <a class="link" href="#simple-search" title="3.266. simple_search">$simple_search</a>)
-but don't want to match flagged messages, simply search for
-“<span class="quote"><code class="literal">[f]lag</code></span>”.
-</p><div class="table"><a id="tab-simplesearch-keywords"></a><p class="title"><b>Table 4.5. Simple search keywords</b></p><div class="table-contents"><table summary="Simple search keywords" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Keyword</th><th>Pattern modifier</th></tr></thead><tbody><tr><td>all</td><td>~A</td></tr><tr><td>.</td><td>~A</td></tr><tr><td>^</td><td>~A</td></tr><tr><td>del</td><td>~D</td></tr><tr><td>flag</td><td>~F</td></tr><tr><td>new</td><td>~N</td></tr><tr><td>old</td><td>~O</td></tr><tr><td>repl</td><td>~Q</td></tr><tr><td>read</td><td>~R</td></tr><tr><td>tag</td><td>~T</td></tr><tr><td>unread</td><td>~U</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The second type of simple search is to build a complex search
-pattern using <a class="link" href="#simple-search" title="3.266. simple_search">$simple_search</a>
-as a template. Mutt will insert your query properly quoted and search
-for the composed complex query.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="complex-patterns"></a>2.3. Complex Patterns</h3></div></div></div><p>
-Logical AND is performed by specifying more than one criterion. For
-example:
-</p><pre class="screen">
-~t mutt ~f elkins
-</pre><p>
-would select messages which contain the word “<span class="quote">mutt</span>” in the list of
-recipients <span class="bold"><strong>and</strong></span> that have the word “<span class="quote">elkins</span>” in the “<span class="quote">From</span>” header
-field.
-</p><p>
-Mutt also recognizes the following operators to create more complex search
-patterns:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-! -- logical NOT operator
-</p></li><li><p>
-| -- logical OR operator
-</p></li><li><p>
-() -- logical grouping operator
-</p></li></ul></div><p>
-Here is an example illustrating a complex search pattern. This pattern will
-select all messages which do not contain “<span class="quote">mutt</span>” in the “<span class="quote">To</span>” or “<span class="quote">Cc</span>”
-field and which are from “<span class="quote">elkins</span>”.
-</p><div class="example"><a id="ex-pattern-bool"></a><p class="title"><b>Example 4.1. Using boolean operators in patterns</b></p><div class="example-contents"><pre class="screen">
-!(~t mutt|~c mutt) ~f elkins
-</pre></div></div><br class="example-break" /><p>
-Here is an example using white space in the regular expression (note
-the ' and " delimiters). For this to match, the mail's subject must
-match the “<span class="quote">^Junk +From +Me$</span>” and it must be from either “<span class="quote">Jim +Somebody</span>”
-or “<span class="quote">Ed +SomeoneElse</span>”:
-</p><pre class="screen">
- '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
-</pre><div class="note"><h3 class="title">Note</h3><p>
-If a regular expression contains parenthesis, or a vertical bar
-("|"), you <span class="bold"><strong>must</strong></span> enclose the expression in double or single quotes since
-those characters are also used to separate different parts of Mutt's
-pattern language. For example: <code class="literal">~f "me@(mutt\.org|cs\.hmc\.edu)"</code>
-</p></div><p>
-Without the quotes, the parenthesis wouldn't end.
-This would be separated to two OR'd patterns: <span class="emphasis"><em>˜f me@(mutt\.org</em></span>
-and <span class="emphasis"><em>cs\.hmc\.edu)</em></span>. They are never what you want.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-patterns"></a>2.4. Searching by Date</h3></div></div></div><p>
-Mutt supports two types of dates, <span class="emphasis"><em>absolute</em></span> and <span class="emphasis"><em>relative</em></span>.
-</p><p>
-<span class="bold"><strong>Absolute</strong></span>. Dates <span class="bold"><strong>must</strong></span> be in DD/MM/YY format (month and year are
-optional, defaulting to the current month and year). An example of a valid
-range of dates is:
-</p><pre class="screen">
-Limit to messages matching: ~d 20/1/95-31/10
-</pre><p>
-If you omit the minimum (first) date, and just specify “<span class="quote">-DD/MM/YY</span>”, all
-messages <span class="emphasis"><em>before</em></span> the given date will be selected. If you omit the maximum
-(second) date, and specify “<span class="quote">DD/MM/YY-</span>”, all messages <span class="emphasis"><em>after</em></span> the given
-date will be selected. If you specify a single date with no dash (“<span class="quote">-</span>”),
-only messages sent on the given date will be selected.
-</p><p>
-<span class="bold"><strong>Error Margins</strong></span>. You can add error margins to absolute dates.
-An error margin is a sign (+ or -), followed by a digit, followed by
-one of the units in <a class="xref" href="#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>. As a special case, you can replace the
-sign by a “<span class="quote">*</span>” character, which is equivalent to giving identical plus and minus error margins.
-</p><div class="table"><a id="tab-date-units"></a><p class="title"><b>Table 4.6. Date units</b></p><div class="table-contents"><table summary="Date units" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Unit</th><th>Description</th></tr></thead><tbody><tr><td>y</td><td>Years</td></tr><tr><td>m</td><td>Months</td></tr><tr><td>w</td><td>Weeks</td></tr><tr><td>d</td><td>Days</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Example: To select any messages two weeks around January 15, 2001,
-you'd use the following pattern:
-</p><pre class="screen">
-Limit to messages matching: ~d 15/1/2001*2w
-</pre><p>
-<span class="bold"><strong>Relative</strong></span>. This type of date is relative to the current date, and may
-be specified as:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-><span class="emphasis"><em>offset</em></span> (messages older than <span class="emphasis"><em>offset</em></span> units)
-</p></li><li><p>
-<<span class="emphasis"><em>offset</em></span> (messages newer than <span class="emphasis"><em>offset</em></span> units)
-</p></li><li><p>
-=<span class="emphasis"><em>offset</em></span> (messages exactly <span class="emphasis"><em>offset</em></span> units old)
-</p></li></ul></div><p>
-<span class="emphasis"><em>offset</em></span> is specified as a positive number with one of the units from <a class="xref" href="#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>.
-</p><p>
-Example: to select messages less than 1 month old, you would use
-</p><pre class="screen">
-Limit to messages matching: ~d <1m
-</pre><div class="note"><h3 class="title">Note</h3><p>
-All dates used when searching are relative to the
-<span class="bold"><strong>local</strong></span> time zone, so unless you change the setting of your <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to include a
-<code class="literal">%[...]</code> format, these are <span class="bold"><strong>not</strong></span> the dates shown
-in the main index.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tags"></a>3. Using Tags</h2></div></div></div><p>
-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 <code class="literal"><tag-pattern></code> function, which is bound to
-“<span class="quote">shift-T</span>” by default. Or you can select individual messages by
-hand using the <code class="literal"><tag-message></code> function, which is bound to “<span class="quote">t</span>” by
-default. See <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> for Mutt's pattern
-matching syntax.
-</p><p>
-Once you have tagged the desired messages, you can use the
-“<span class="quote">tag-prefix</span>” operator, which is the “<span class="quote">;</span>” (semicolon) key by default.
-When the “<span class="quote">tag-prefix</span>” operator is used, the <span class="bold"><strong>next</strong></span> operation will
-be applied to all tagged messages if that operation can be used in that
-manner. If the <a class="link" href="#auto-tag" title="3.18. auto_tag">$auto_tag</a>
-variable is set, the next operation applies to the tagged messages
-automatically, without requiring the “<span class="quote">tag-prefix</span>”.
-</p><p>
-In <a class="link" href="#macro" title="8. Keyboard macros">macros</a> or <a class="link" href="#push" title="22. Adding key sequences to the keyboard buffer">push</a> commands,
-you can use the “<span class="quote">tag-prefix-cond</span>” operator. If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the “<span class="quote">end-cond</span>”
-operator; after this operator the rest of the macro will be executed as
-normal.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="hooks"></a>4. Using Hooks</h2></div></div></div><p>
-A <span class="emphasis"><em>hook</em></span> is a concept found in many other programs 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 world, a <span class="emphasis"><em>hook</em></span>
-consists of a <a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a> or
-<a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">pattern</a> along with a
-configuration option/command. See
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a>
-</p></li><li><p>
-<a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a>
-</p></li><li><p>
-<a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a>
-</p></li><li><p>
-<a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a>
-</p></li><li><p>
-<a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a>
-</p></li><li><p>
-<a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
-</p></li><li><p>
-<a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a>
-</p></li></ul></div><p>
-
-for specific details on each type of <span class="emphasis"><em>hook</em></span> available.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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:
-</p></div><div class="example"><a id="ex-send-hook-my-hdr"></a><p class="title"><b>Example 4.2. Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></b></p><div class="example-contents"><pre class="screen">
-send-hook . 'unmy_hdr From:'
-send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-</pre></div></div><br class="example-break" /><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pattern-hook"></a>4.1. Message Matching in Hooks</h3></div></div></div><p>
-Hooks that act upon messages (<code class="literal">message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook</code>) are evaluated in a
-slightly different manner. For the other
-types of hooks, a <a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a> 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.
-</p><p>
-Mutt allows the use of the <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">search pattern</a>
-language for matching messages in hook commands. This works in
-exactly the same way as it would when <span class="emphasis"><em>limiting</em></span> or
-<span class="emphasis"><em>searching</em></span> 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.).
-</p><p>
-For example, if you wanted to set your return address based upon sending
-mail to a specific address, you could do something like:
-</p><pre class="screen">
-send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
-</pre><p>
-which would execute the given command when sending mail to
-<span class="emphasis"><em>me@cs.hmc.edu</em></span>.
-</p><p>
-However, it is not required that you write the pattern to match using the
-full searching language. You can still specify a simple <span class="emphasis"><em>regular
-expression</em></span> like the other hooks, in which case Mutt will translate your
-pattern into the full language, using the translation specified by the
-<a class="link" href="#default-hook" title="3.41. default_hook">$default_hook</a> variable. The
-pattern is translated at the time the hook is declared, so the value of
-<a class="link" href="#default-hook" title="3.41. default_hook">$default_hook</a> that is in effect
-at that time will be used.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="query"></a>5. External Address Queries</h2></div></div></div><p>
-Mutt 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 <a class="link" href="#query-command" title="3.234. query_command">$query_command</a> variable, you specify the wrapper
-command to use. For example:
-</p><pre class="screen">
-set query_command = "mutt_ldap_query.pl '%s'"
-</pre><p>
-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 then
-some other optional information. On error, or if there are no matching
-addresses, return a non-zero exit code and a one line error message.
-</p><p>
-An example multiple response output:
-</p><pre class="screen">
-Searching database ... 20 entries ... 3 matching:
-me@cs.hmc.edu Michael Elkins mutt dude
-blong@fiction.net Brandon Long mutt and more
-roessler@does-not-exist.org Thomas Roessler mutt pgp
-</pre><p>
-There are two mechanisms for accessing the query function of mutt. One
-is to do a query from the index menu using the <code class="literal"><query></code> 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 addresses
-to mail, start a new query, or have a new query appended to the current
-responses.
-</p><p>
-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 <code class="literal"><complete-query></code> 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 query
-menu. At the query menu, you can select one or more addresses to be
-added to the prompt.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailbox-formats"></a>6. Mailbox Formats</h2></div></div></div><p>
-Mutt 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 new
-mailboxes, Mutt uses the default specified with the <a class="link" href="#mbox-type" title="3.117. mbox_type">$mbox_type</a> variable.
-</p><p>
-<span class="bold"><strong>mbox</strong></span>. 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:
-</p><pre class="screen">
-From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-</pre><p>
-to denote the start of a new message (this is often referred to as the
-“<span class="quote">From_</span>” line).
-</p><p>
-<span class="bold"><strong>MMDF</strong></span>. This is a variant of the <span class="emphasis"><em>mbox</em></span> format. Each message is
-surrounded by lines containing “<span class="quote">^A^A^A^A</span>” (four control-A's).
-</p><p>
-<span class="bold"><strong>MH</strong></span>. A radical departure from <span class="emphasis"><em>mbox</em></span> and <span class="emphasis"><em>MMDF</em></span>, 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 displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
-detects this type of mailbox by looking for either <code class="literal">.mh_sequences</code>
-or <code class="literal">.xmhcache</code> (needed to distinguish normal directories from MH
-mailboxes).
-</p><p>
-<span class="bold"><strong>Maildir</strong></span>. The newest of the mailbox formats, used by the Qmail MTA (a
-replacement for sendmail). Similar to <span class="emphasis"><em>MH</em></span>, except that it adds three
-subdirectories of the mailbox: <span class="emphasis"><em>tmp</em></span>, <span class="emphasis"><em>new</em></span> and <span class="emphasis"><em>cur</em></span>. Filenames
-for the messages are chosen in such a way they are unique, even when two
-programs are writing the mailbox over NFS, which means that no file locking
-is needed.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="shortcuts"></a>7. Mailbox Shortcuts</h2></div></div></div><p>
-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.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-! -- refers to your <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a> (incoming) mailbox
-</p></li><li><p>
-> -- refers to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> file
-</p></li><li><p>
-< -- refers to your <a class="link" href="#record" title="3.242. record">$record</a> file
-</p></li><li><p>
-^ -- refers to the current mailbox
-</p></li><li><p>
-- or !! -- refers to the file you've last visited
-</p></li><li><p>
-˜ -- refers to your home directory
-</p></li><li><p>
-= or + -- refers to your <a class="link" href="#folder" title="3.58. folder">$folder</a> directory
-</p></li><li><p>
-@<span class="emphasis"><em>alias</em></span> -- refers to the <a class="link" href="#save-hook" title="16. Specify default save mailbox">default save folder</a> as determined by the address of the alias
-</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-lists"></a>8. Handling Mailing Lists</h2></div></div></div><p>
-Mutt 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 <a class="link" href="#lists" title="12. Mailing lists">lists and subscribe</a> commands in your muttrc.
-</p><p>
-Now that Mutt 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 <span class="emphasis"><em>index</em></span> menu display. This is useful to distinguish between
-personal and list mail in the same mailbox. In the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable, the escape “<span class="quote">%L</span>”
-will return the string “<span class="quote">To <list></span>” when “<span class="quote">list</span>” appears in the
-“<span class="quote">To</span>” field, and “<span class="quote">Cc <list></span>” when it appears in the “<span class="quote">Cc</span>”
-field (otherwise it returns the name of the author).
-</p><p>
-Often times the “<span class="quote">To</span>” and “<span class="quote">Cc</span>” fields in mailing list messages
-tend to get quite large. Most people do not bother to remove the
-author of the message they reply to from the list, resulting in
-two or more copies being sent to that person. The <code class="literal"><list-reply></code>
-function, which by default is bound to “<span class="quote">L</span>” in the <span class="emphasis"><em>index</em></span> menu
-and <span class="emphasis"><em>pager</em></span>, helps reduce the clutter by only replying to the
-known mailing list addresses instead of all recipients (except as
-specified by <code class="literal">Mail-Followup-To</code>, see below).
-</p><p>
-Mutt also supports the <code class="literal">Mail-Followup-To</code> header. When you send
-a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the <a class="link" href="#followup-to" title="3.60. followup_to">$followup_to</a> 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 “<span class="quote">followups</span>”) 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.
-</p><p>
-Conversely, when group-replying or list-replying to a message which
-has a <code class="literal">Mail-Followup-To</code> header, mutt will respect this header if
-the <a class="link" href="#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a> 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 <code class="literal">Mail-Followup-To</code>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-When header editing is enabled, you can create a
-<code class="literal">Mail-Followup-To</code> header manually. Mutt will only auto-generate
-this header if it doesn't exist when you send the message.
-</p></div><p>
-The other method some mailing list admins use is to generate a
-“<span class="quote">Reply-To</span>” 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 “<span class="quote">Reply-To</span>”
-field. Mutt uses the <a class="link" href="#reply-to" title="3.245. reply_to">$reply_to</a>
-variable to help decide which address to use. If set to <span class="emphasis"><em>ask-yes</em></span> or
-<span class="emphasis"><em>ask-no</em></span>, you will be
-prompted as to whether or not you would like to use the address given in
-the “<span class="quote">Reply-To</span>” field, or reply directly to the address given in the
-“<span class="quote">From</span>” field. When set to <span class="emphasis"><em>yes</em></span>, the “<span class="quote">Reply-To</span>” field will be used when
-present.
-</p><p>
-The “<span class="quote">X-Label:</span>” header field can be used to further identify mailing
-lists or list subject matter (or just to annotate messages
-individually). The <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable's “<span class="quote">%y</span>” and
-“<span class="quote">%Y</span>” escapes can be used to expand “<span class="quote">X-Label:</span>” fields in the
-index, and Mutt's pattern-matcher can match regular expressions to
-“<span class="quote">X-Label:</span>” fields with the “<span class="quote">˜y</span>” selector. “<span class="quote">X-Label:</span>” is not a
-standard message header field, but it can easily be inserted by procmail
-and other mail filtering agents.
-</p><p>
-Lastly, Mutt has the ability to <a class="link" href="#sort" title="3.273. sort">sort</a> the mailbox into
-<a class="link" href="#threads" title="4.3. Threaded Mode">threads</a>. 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 dealing
-with large volume mailing lists easier because you can easily delete
-uninteresting threads and quickly find topics of value.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="handling-folders"></a>9. Handling multiple folders</h2></div></div></div><p>
-Mutt supports setups with multiple folders, allowing all of them to
-be monitored for new mail (see <a class="xref" href="#mailboxes" title="14. Monitoring incoming mail">Section 14, “Monitoring incoming mail”</a> for details).
-</p><p>
-When in the index menu and being idle (also see
-<a class="link" href="#timeout" title="3.290. timeout">$timeout</a>), Mutt periodically checks
-for new mail in all folders which have been configured via the
-<code class="literal">mailboxes</code> command. The interval depends on the folder
-type: for local/IMAP folders it consults
-<a class="link" href="#mail-check" title="3.105. mail_check">$mail_check</a> and
-<a class="link" href="#pop-checkinterval" title="3.218. pop_checkinterval">$pop_checkinterval</a>
-for POP folders.
-</p><p>
-Outside the index menu the directory browser supports checking
-for new mail using the <code class="literal"><check-new></code> function which is
-unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the <code class="literal">mailboxes</code> command,
-and indicate which contain new messages. Mutt will automatically enter this
-mode when invoked from the command line with the <code class="literal">-y</code> option.
-</p><p>
-For the pager, index and directory browser menus, Mutt contains the
-<code class="literal"><buffy-list></code> function (bound to “<span class="quote">.</span>” by default)
-which will print a list of folders with new mail in the command line at
-the bottom of the screen.
-</p><p>
-For the index, by default Mutt displays the number of mailboxes with new
-mail in the status bar, please refer to the
-<a class="link" href="#index-format" title="3.101. index_format">$index_format</a>
-variable for details.
-</p><p>
-When changing folders, Mutt fills the prompt with the first folder from
-the mailboxes list containing new mail (if any), pressing
-<span class="emphasis"><em>space</em></span> will cycle through folders with new mail.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing-threads"></a>10. Editing threads</h2></div></div></div><p>
-Mutt 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.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="link-threads"></a>10.1. Linking threads</h3></div></div></div><p>
-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 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 <code class="literal"><link-threads></code> function (bound to & by default). The
-reply will then be connected to this "parent" message.
-</p><p>
-You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="break-threads"></a>10.2. Breaking threads</h3></div></div></div><p>
-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 <code class="literal"><break-thread></code> function (bound
-by default to #), which will turn the subthread starting from the
-current message into a whole different thread.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="dsn"></a>11. Delivery Status Notification (DSN) Support</h2></div></div></div><p>
-RFC1894 defines a set of MIME content types for relaying information
-about the status of electronic mail messages. These can be thought of as
-“<span class="quote">return receipts.</span>”
-</p><p>
-To support DSN, there are two variables. <a class="link" href="#dsn-notify" title="3.47. dsn_notify">$dsn_notify</a> is used to request receipts for
-different results (such as failed message, message delivered, etc.).
-<a class="link" href="#dsn-return" title="3.48. dsn_return">$dsn_return</a> requests how much
-of your message should be returned with the receipt (headers or full
-message).
-</p><p>
-When using <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> for mail
-delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA
-supporting DSN command line options compatible to Sendmail: The -N and -R
-options can be used by the mail client to make requests as to what type of
-status messages should be returned. Please consider your MTA documentation
-whether DSN is supported.
-</p><p>
-For SMTP delivery using <a class="link" href="#smtp-url" title="3.272. smtp_url">$smtp_url</a>, it depends on the
-capabilities announced by the server whether mutt will attempt to
-request DSN or not.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="urlview"></a>12. Start a WWW Browser on URLs</h2></div></div></div><p>
-If a message contains URLs, 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
-<a class="ulink" href="ftp://ftp.mutt.org/mutt/contrib/" target="_top">ftp://ftp.mutt.org/mutt/contrib/</a>
-and the configuration commands:
-</p><pre class="screen">
-macro index \cb |urlview\n
-macro pager \cb |urlview\n
-</pre></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="compressedfolders"></a>1. Compressed folders Support (OPTIONAL)</h2></div></div></div><p>
-If Mutt was compiled with compressed folders support (by running the
-<span class="emphasis"><em>configure</em></span> script with the
-<span class="emphasis"><em>--enable-compressed</em></span> flag), Mutt can open folders
-stored in an arbitrary format, provided that the user has a script to
-convert from/to this format to one of the accepted.
-
-The most common use is to open compressed archived folders e.g. with
-gzip.
-
-In addition, the user can provide a script that gets a folder in an
-accepted format and appends its context to the folder in the
-user-defined format, which may be faster than converting the entire
-folder to the accepted format, appending to it and converting back to
-the user-defined format.
-
-There are three hooks defined (<a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a>, <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> and <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>) which define commands to
-uncompress and compress a folder and to append messages to an existing
-compressed folder respectively.
-
-For example:
-
-</p><pre class="screen">
-open-hook \\.gz$ "gzip -cd %f > %t"
-close-hook \\.gz$ "gzip -c %t > %f"
-append-hook \\.gz$ "gzip -c %t >> %f"
-</pre><p>
-
-You do not have to specify all of the commands. If you omit <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>, the folder will be open and
-closed again each time you will add to it. If you omit <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> (or give empty command) , the
-folder will be open in the mode. If you specify <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> though you'll be able to
-append to the folder.
-
-Note that Mutt 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
-<a class="link" href="#save-empty" title="3.252. save_empty">$save_empty</a>, so that
-the compressed file will be removed if you delete all of the messages.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="open-hook"></a>1.1. Open a compressed mailbox for reading</h3></div></div></div><p>
-Usage: <code class="literal">open-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-The <span class="emphasis"><em>command</em></span> is the command that can be used for
-opening the folders whose names match <span class="emphasis"><em>regexp</em></span>.
-
-The <span class="emphasis"><em>command</em></span> string is the printf-like format
-string, and it should accept two parameters: %f, which is
-replaced with the (compressed) folder name, and %t which is
-replaced with the name of the temporary folder to which to write.
-
-%f and %t can be repeated any number of times in the
-command string, and all of the entries are replaced with the
-appropriate folder name. In addition, %% is replaced by
-%, as in printf, and any other %anything is left as is.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the original compressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-open-hook \\.gz$ "gzip -cd %f > %t"
-</pre><p>
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="close-hook"></a>1.2. Write a compressed mailbox</h3></div></div></div><p>
-Usage: <code class="literal">close-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-This is used to close the folder that was open with the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command after some changes were
-made to it.
-
-The <span class="emphasis"><em>command</em></span> string is the command that can be
-used for closing the folders whose names match
-<span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. Temporary folder in this
-case is the folder previously produced by the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-close-hook \\.gz$ "gzip -c %t > %f"
-</pre><p>
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type, and the file can only be open in the
-read-only mode.
-
-<a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is not called when you
-exit from the folder if the folder was not changed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="append-hook"></a>1.3. Append a message to a compressed mailbox</h3></div></div></div><p>
-Usage: <code class="literal">append-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-This command is used for saving to an existing compressed folder. The
-<span class="emphasis"><em>command</em></span> is the command that can be used for
-appending to the folders whose names match
-<span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. The temporary folder in
-this case contains the messages that are being appended.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-append-hook \\.gz$ "gzip -c %t >> %f"
-</pre><p>
-
-When <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> 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 (<a class="link" href="#mbox-type" title="3.117. mbox_type">$mbox_type</a>) type is always
-supposed (i.e. this is the format used for the temporary folder).
-
-If the file does not exist when you save to it, <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is called, and not <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>. <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> is only for appending to
-existing folders.
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type. In this case, the folder will be open and
-closed again (using <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> and
-<a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a>respectively) each time you
-will add to it.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id2592001"></a>1.4. Encrypted folders</h3></div></div></div><p>
-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 use
-the following hooks:
-
-</p><pre class="screen">
-open-hook \\.pgp$ "pgp -f < %f > %t"
-close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-</pre><p>
-
-Please note, that PGP does not support appending to an encrypted
-folder, so there is no append-hook defined.
-
-If you are using GnuPG instead of PGP, you may use the following hooks
-instead:
-
-</p><pre class="screen">
-open-hook \\.gpg$ "gpg --decrypt < %f > %t"
-close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
-</pre><p>
-
-<span class="bold"><strong>Note:</strong></span> the folder is temporary stored
-decrypted in the /tmp directory, where it can be read by your system
-administrator. So think about the security aspects of this.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="mimesupport"></a>Chapter 5. Mutt's MIME Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="#mime-lookup">7. MIME Lookup</a></span></dt></dl></div><p>
-Quite a bit of effort has been made to make Mutt 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 for MIME, there are two extra
-types of configuration files which Mutt uses. One is the
-<code class="literal">mime.types</code> file, which contains the mapping of file extensions to
-IANA MIME types. The other is the <code class="literal">mailcap</code> file, which specifies
-the external commands to use for handling specific MIME types.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-mime"></a>1. Using MIME in Mutt</h2></div></div></div><p>
-There are three areas/menus in Mutt which deal with MIME, they are the
-pager (while viewing a message), the attachment menu and the compose
-menu.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-pager"></a>1.1. Viewing MIME messages in the pager</h3></div></div></div><p>
-When you select a message from the index and view it in the pager, Mutt
-decodes the message to a text representation. Mutt internally supports
-a number of MIME types, including <code class="literal">text/plain, text/enriched,
-message/rfc822, and message/news</code>. In addition, the export
-controlled version of Mutt recognizes a variety of PGP MIME types,
-including PGP/MIME and application/pgp.
-</p><p>
-Mutt will denote attachments with a couple lines describing them.
-These lines are of the form:
-</p><pre class="screen">
-[-- Attachment #1: Description --]
-[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-</pre><p>
-Where the <code class="literal">Description</code> is the description or filename given for the
-attachment, and the <code class="literal">Encoding</code> is one of
-<code class="literal">7bit/8bit/quoted-printable/base64/binary</code>.
-</p><p>
-If Mutt cannot deal with a MIME type, it will display a message like:
-</p><pre class="screen">
-[-- image/gif is unsupported (use 'v' to view this part) --]
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-menu"></a>1.2. The Attachment Menu</h3></div></div></div><p>
-The default binding for <code class="literal">view-attachments</code> is `v', which displays the
-attachment menu for a message. The attachment menu displays a list of
-the 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 “<span class="quote">tag-prefix</span>” 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.
-</p><p>
-Finally, you can apply the usual message-related functions (like
-<a class="link" href="#resend-message"><code class="literal"><resend-message></code></a>, and the
-<code class="literal"><reply></code> and <code class="literal"><forward></code>
-functions) to attachments of type <code class="literal">message/rfc822</code>.
-</p><p>
-See the help on the attachment menu for more information.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-menu"></a>1.3. The Compose Menu</h3></div></div></div><p>
-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.
-</p><p>
-Attachments appear as follows:
-</p><pre class="screen">
-- 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>
-</pre><p>
-The '-' denotes that Mutt will delete the file after sending (or
-postponing, or canceling) the message. It can be toggled with the
-<code class="literal">toggle-unlink</code> command (default: u). The next field is the MIME
-content-type, and can be changed with the <code class="literal">edit-type</code> 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 <code class="literal">edit-encoding</code> 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 <code class="literal">rename-file</code> command (default: R).
-The final field is the description of the attachment, and can be
-changed with the <code class="literal">edit-description</code> command (default: d).
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-types"></a>2. MIME Type configuration with <code class="literal">mime.types</code></h2></div></div></div><p>
-When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at <code class="literal">${HOME}/.mime.types</code>, and then
-the system mime.types file at <code class="literal">/usr/local/share/mutt/mime.types</code> or
-<code class="literal">/etc/mime.types</code>
-</p><p>
-The mime.types file consist of lines containing a MIME type and a space
-separated list of extensions. For example:
-</p><pre class="screen">
-application/postscript ps eps
-application/pgp pgp
-audio/x-aiff aif aifc aiff
-</pre><p>
-A sample <code class="literal">mime.types</code> file comes with the Mutt distribution, and
-should contain most of the MIME types you are likely to use.
-</p><p>
-If Mutt 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 will assume that the file is plain text, and mark it
-as <code class="literal">text/plain</code>. If the file contains binary information, then Mutt will
-mark it as <code class="literal">application/octet-stream</code>. You can change the MIME
-type that Mutt assigns to an attachment by using the <code class="literal">edit-type</code>
-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 recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
-major mime types, such as the chemical type that is widely used in the
-molecular modeling community to pass molecular data in various forms to
-various molecular viewers. Non-recognized mime types should only be used
-if the recipient of the message is likely to be expecting such attachments.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailcap"></a>3. MIME Viewer configuration with <code class="literal">mailcap</code></h2></div></div></div><p>
-Mutt supports RFC 1524 MIME Configuration, in particular the Unix
-specific format specified in Appendix A of RFC 1524. 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.
-</p><p>
-In order to handle various MIME types that Mutt can not handle
-internally, Mutt parses a series of external configuration files to
-find an external handler. The default search string for these files
-is a colon delimited list containing the following files:
-</p><div class="orderedlist"><ol type="1"><li><p><code class="literal">$HOME/.mailcap</code></p></li><li><p><code class="literal">$PKGDATADIR/mailcap</code></p></li><li><p><code class="literal">$SYSCONFDIR/mailcap</code></p></li><li><p><code class="literal">/etc/mailcap</code></p></li><li><p><code class="literal">/usr/etc/mailcap</code></p></li><li><p><code class="literal">/usr/local/etc/mailcap</code></p></li></ol></div><p>
-where <code class="literal">$HOME</code> is your home directory. The
-<code class="literal">$PKGDATADIR</code> and the
-<code class="literal">$SYSCONFDIR</code> directories depend on where mutt
-is installed: the former is the default for shared data, the
-latter for system configuration files.
-</p><p>
-The default search path can be obtained by running the following
-command:
-</p><pre class="screen">
-mutt -nF /dev/null -Q mailcap_path
-</pre><p>
-In particular, the metamail distribution will install a mailcap file,
-usually as <code class="literal">/usr/local/etc/mailcap</code>, which contains some baseline
-entries.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-basics"></a>3.1. The Basics of the mailcap file</h3></div></div></div><p>
-A mailcap file consists of a series of lines which are comments, blank,
-or definitions.
-</p><p>
-A comment line consists of a # character followed by anything you want.
-</p><p>
-A blank line is blank.
-</p><p>
-A definition line consists of a content type, a view command, and any
-number of optional fields. Each field of a definition line is divided
-by a semicolon ';' character.
-</p><p>
-The content type is specified in the MIME standard type/subtype method.
-For example,
-<code class="literal">text/plain, text/html, image/gif, </code>
-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, <code class="literal">image/*</code>, or
-<code class="literal">video,</code> will match all image types and video types,
-respectively.
-</p><p>
-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 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 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.
-</p><p>
-So, in the simplest form, you can send a text/plain message to the
-external pager more on stdin:
-</p><pre class="screen">
-text/plain; more
-</pre><p>
-Or, you could send the message as a file:
-</p><pre class="screen">
-text/plain; more %s
-</pre><p>
-Perhaps you would like to use lynx to interactively view a text/html
-message:
-</p><pre class="screen">
-text/html; lynx %s
-</pre><p>
-In this case, lynx does not support viewing a file from stdin, so you
-must use the %s syntax.
-</p><div class="note"><h3 class="title">Note</h3><p>
-<span class="emphasis"><em>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.</em></span>
-</p></div><p>
-On the other hand, maybe you don't want to use lynx interactively, you
-just want to have it convert the text/html to text/plain, then you can
-use:
-</p><pre class="screen">
-text/html; lynx -dump %s | more
-</pre><p>
-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:
-</p><pre class="screen">
-text/html; lynx %s
-text/*; more
-</pre><p>
-This is the simplest form of a mailcap file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="secure-mailcap"></a>3.2. Secure use of mailcap</h3></div></div></div><p>
-The interpretation of shell meta-characters embedded in MIME parameters
-can lead to security problems in general. Mutt tries to quote parameters
-in expansion of %s syntaxes properly, and avoids risky characters by
-substituting them, see the <a class="link" href="#mailcap-sanitize" title="3.107. mailcap_sanitize">$mailcap_sanitize</a> variable.
-</p><p>
-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:
-</p><p>
-<span class="emphasis"><em>Keep the %-expandos away from shell quoting.</em></span>
-Don't quote them with single or double quotes. Mutt 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 behavior with quotes introduces new leaks - there is no
-alternative to correct quoting in the first place.
-</p><p>
-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 <code class="literal">$charset</code> inside the backtick expansion is safe,
-since it is not itself subject to any further expansion):
-</p><pre class="screen">
-text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="advanced-mailcap"></a>3.3. Advanced mailcap Usage</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="optional-mailcap-fields"></a>3.3.1. Optional Fields</h4></div></div></div><p>
-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 recognizes the following optional fields:
-</p><div class="variablelist"><dl><dt><span class="term">copiousoutput</span></dt><dd><p>
-This flag tells Mutt that the command passes possibly large amounts of
-text on stdout. This causes Mutt 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 assumes that the command
-is interactive. One could use this to replace the pipe to <code class="literal">more</code>
-in the <code class="literal">lynx -dump</code> example in the Basic section:
-</p><pre class="screen">
-text/html; lynx -dump %s ; copiousoutput
-</pre><p>
-This will cause lynx to format the text/html output as text/plain
-and Mutt will use your standard pager to display the results.
-</p></dd><dt><span class="term">needsterminal</span></dt><dd><p>
-Mutt uses this flag when viewing attachments with <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, in order to decide whether it should honor the setting
-of the <a class="link" href="#wait-key" title="3.303. wait_key">$wait_key</a> variable or
-not. When an attachment is viewed using an interactive program, and the
-corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag, Mutt will use
-<a class="link" href="#wait-key" title="3.303. wait_key">$wait_key</a> and the exit status
-of 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.
-</p></dd><dt><span class="term">compose=<command></span></dt><dd><p>
-This flag specifies the command to use to create a new attachment of a
-specific MIME type. Mutt supports this from the compose menu.
-</p></dd><dt><span class="term">composetyped=<command></span></dt><dd><p>
-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 supports this from the compose menu.
-</p></dd><dt><span class="term">print=<command></span></dt><dd><p>
-This flag specifies the command to use to print a specific MIME type.
-Mutt supports this from the attachment and compose menus.
-</p></dd><dt><span class="term">edit=<command></span></dt><dd><p>
-This flag specifies the command to use to edit a specific MIME type.
-Mutt supports this from the compose menu, and also uses it to compose
-new attachments. Mutt will default to the defined editor for text
-attachments.
-</p></dd><dt><span class="term">nametemplate=<template></span></dt><dd><p>
-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 <code class="literal">text/html</code> if the file ends in <code class="literal">.html</code>.
-So, you would specify lynx as a <code class="literal">text/html</code> viewer with a line in
-the mailcap file like:
-</p><pre class="screen">
-text/html; lynx %s; nametemplate=%s.html
-</pre></dd><dt><span class="term">test=<command></span></dt><dd><p>
-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 uses this entry. If the command returns non-zero,
-then the test failed, and Mutt continues searching for the right entry.
-Note that the content-type must match before Mutt performs the test.
-For example:
-</p><pre class="screen">
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s
-</pre><p>
-In this example, Mutt 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 will call netscape to display the
-text/html object. If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
-</p></dd></dl></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-search-order"></a>3.3.2. Search Order</h4></div></div></div><p>
-When searching for an entry in the mailcap file, Mutt will search for
-the most useful entry for its purpose. For instance, if you are
-attempting to print an <code class="literal">image/gif</code>, and you have the following
-entries in your mailcap file, Mutt will search for an entry with the
-print command:
-</p><pre class="screen">
-image/*; xv %s
-image/gif; ; print= anytopnm %s | pnmtops | lpr; \
- nametemplate=%s.gif
-</pre><p>
-Mutt will skip the <code class="literal">image/*</code> entry and use the <code class="literal">image/gif</code>
-entry with the print command.
-</p><p>
-In addition, you can use this with <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>
-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.
-</p><pre class="screen">
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s; nametemplate=%s.html
-text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
-</pre><p>
-For <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, Mutt 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 will use the second entry
-for interactive viewing.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-command-expansion"></a>3.3.3. Command Expansion</h4></div></div></div><p>
-The various commands defined in the mailcap files are passed to the
-<code class="literal">/bin/sh</code> shell using the system() function. Before the
-command is passed to <code class="literal">/bin/sh -c</code>, it is parsed to expand
-various special parameters with information from Mutt. The keywords
-Mutt expands are:
-</p><div class="variablelist"><dl><dt><span class="term">%s</span></dt><dd><p>
-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 to not pass the body of the message
-to the view/print/edit program on stdin.
-</p></dd><dt><span class="term">%t</span></dt><dd><p>
-Mutt 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 <code class="literal">text/html</code> or
-<code class="literal">image/gif</code>.
-</p></dd><dt><span class="term">%{<parameter>}</span></dt><dd><p>
-Mutt 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:
-</p><pre class="screen">
-Content-Type: text/plain; charset=iso-8859-1
-</pre><p>
-then Mutt 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.
-</p></dd><dt><span class="term">\%</span></dt><dd><p>
-This will be replaced by a %
-</p></dd></dl></div><p>
-Mutt 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.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-example"></a>3.4. Example mailcap files</h3></div></div></div><p>
-This mailcap file is fairly simple and standard:
-</p><pre class="screen">
-# I'm always running X :)
-video/*; xanim %s > /dev/null
-image/*; xv %s > /dev/null
-
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html; netscape -remote 'openURL(%s)'
-</pre><p>
-This mailcap file shows quite a number of examples:
-</p><pre class="screen">
-# Use xanim to view all videos Xanim produces a header on startup,
-# send that to /dev/null so I don't see it
-video/*; xanim %s > /dev/null
-
-# Send html to a running netscape by remote
-text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
-
-# If I'm not running netscape but I am running X, start netscape on the
-# object
-text/html; netscape %s; test=RunningX
-
-# Else use lynx to view it as text
-text/html; lynx %s
-
-# This version would convert the text/html to text/plain
-text/html; lynx -dump %s; copiousoutput
-
-# I use enscript to print text in two columns to a page
-text/*; more %s; print=enscript -2Gr %s
-
-# Netscape adds a flag to tell itself to view jpegs internally
-image/jpeg;xv %s; x-mozilla-flags=internal
-
-# Use xv to view images if I'm running X
-# In addition, this uses the \ to extend the line and set my editor
-# for images
-image/*;xv %s; test=RunningX; \
- edit=xpaint %s
-
-# Convert images to text using the netpbm tools
-image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
-pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
-# Send excel spreadsheets to my NT box
-application/ms-excel; open.pl %s
-</pre></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="auto-view"></a>4. MIME Autoview</h2></div></div></div><p>
-In addition to explicitly telling Mutt to view an attachment with the
-MIME viewer defined in the mailcap file, Mutt has support for
-automatically viewing MIME attachments while in the pager.
-</p><p>
-To work, you must define a viewer in the mailcap file which uses the
-<code class="literal">copiousoutput</code> 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.
-</p><p>
-You then use the <code class="literal">auto_view</code> muttrc command to list the
-content-types that you wish to view automatically.
-</p><p>
-For instance, if you set auto_view to:
-</p><pre class="screen">
-auto_view text/html application/x-gunzip \
- application/postscript image/gif application/x-tar-gz
-</pre><p>
-Mutt could use the following mailcap entries to automatically view
-attachments of these types.
-</p><pre class="screen">
-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
-</pre><p>
-“<span class="quote">unauto_view</span>” 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.
-“<span class="quote">unauto_view *</span>” will remove all previous entries.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternative-order"></a>5. MIME Multipart/Alternative</h2></div></div></div><p>
-Mutt 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 types
-is preferred. The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
-</p><pre class="screen">
-alternative_order text/enriched text/plain text application/postscript image/*
-</pre><p>
-Next, mutt will check if any of the types have a defined
-<a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, and use that. Failing
-that, Mutt will look for any text type. As a last attempt, mutt will
-look for any type it knows how to handle.
-</p><p>
-To remove a MIME type from the <code class="literal">alternative_order</code> list, use the
-<code class="literal">unalternative_order</code> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="attachments"></a>6. Attachment Searching and Counting</h2></div></div></div><p>
-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.
-</p><p>
-In order to provide this information, mutt needs to fully MIME-parse
-all messages affected first. This can slow down operation especially for
-remote mail folders such as IMAP because all messages have to be
-downloaded first regardless whether the user really wants to view them
-or not.
-</p><p>
-The syntax is:
-</p><pre class="screen">
-attachments {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments ?
-</pre><p>
-Disposition is the attachment's Content-disposition type -- either
-<code class="literal">inline</code> or <code class="literal">attachment</code>.
-You can abbreviate this to <code class="literal">I</code> or <code class="literal">A</code>.
-</p><p>
-Disposition is prefixed by either a + symbol or 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.
-</p><p>
-Mime-type is, unsurprisingly, the MIME type of the attachment you want
-to affect. A MIME type is always of the format <code class="literal">major/minor</code>, where
-<code class="literal">major</code> describes the broad category of document you're looking at, and
-<code class="literal">minor</code> describes the specific type within that category. The major
-part of mime-type must be literal text (or the special token “<span class="quote"><code class="literal">*</code></span>”), but
-the minor part may be a regular expression. (Therefore, “<span class="quote"><code class="literal">*/.*</code></span>” matches
-any MIME type.)
-</p><p>
-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.
-</p><p>
-Some examples might help to illustrate. The examples that are not
-commented out define the default configuration of the lists.
-</p><div class="example"><a id="ex-attach-count"></a><p class="title"><b>Example 5.1. Attachment counting</b></p><div class="example-contents"><pre class="screen">
-## 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
-</pre></div></div><br class="example-break" /><p>
-Entering the command “<span class="quote"><code class="literal">attachments ?</code></span>”
-as a command will list your current settings in Muttrc format, so that
-it can be pasted elsewhere.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-lookup"></a>7. MIME Lookup</h2></div></div></div><p>
-Mutt's mime_lookup list specifies a list of mime-types that should not
-be treated according to their mailcap entry. This option is designed to
-deal 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:
-</p><pre class="screen">
-mime_lookup application/octet-stream application/X-Lotus-Manuscript
-</pre><p>
-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.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="optionalfeatures"></a>Chapter 6. Optional features</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="#exact-address">8. Exact address generation</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="optionalfeatures-notes"></a>1. General notes</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compile-time-features"></a>1.1. Enabling/disabling features</h3></div></div></div><p>
-Mutt supports several of optional features which can be enabled or
-disabled at compile-time by giving the <span class="emphasis"><em>configure</em></span> script
-certain arguments. These are listed in the “<span class="quote">Optional features</span>” section of
-the <span class="emphasis"><em>configure --help</em></span> output.
-</p><p>
-Which features are enabled or disabled can later be determined from the
-output of <code class="literal">mutt -v</code>. If a compile option starts with
-“<span class="quote">+</span>” it is enabled and disabled if prefixed with “<span class="quote">-</span>”. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
-OpenSSL, <code class="literal">mutt -v</code> would contain:
-</p><pre class="screen">
--USE_SSL_OPENSSL +USE_SSL_GNUTLS</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="url-syntax"></a>1.2. URL syntax</h3></div></div></div><p>
-Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
-to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in <code class="literal">[]</code> means it is optional and
-may be omitted):
-</p><pre class="screen">
-proto[s]://[username[:password]@]server[:port]/[path]
-</pre><p>
-<code class="literal">proto</code> is the communication protocol:
-<code class="literal">imap</code> for IMAP, <code class="literal">pop</code> for POP3 and
-<code class="literal">smtp</code> for SMTP. If “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”
-is appended, mutt will attempt to establish an encrypted communication
-using SSL or TLS. If no explicit port is given, mutt will use the
-system's default for the given protocol.
-</p><p>
-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the <code class="literal">pop_user</code> or
-<code class="literal">imap_user</code> variables. It may contain the “<span class="quote">@</span>” symbol
-being used by many mail systems as part of the login name. A password can be
-given, too but is not recommended if the URL is specified in a configuration
-file on disk.
-</p><p>
-The optional path is only relevant for IMAP.
-</p><p>
-For IMAP for example, you can select an alternative port by specifying it with the
-server: <code class="literal">imap://imapserver:port/INBOX</code>. You can also specify different
-username for each folder: <code class="literal">imap://username@imapserver[:port]/INBOX</code>
-or <code class="literal">imap://username2@imapserver[:port]/path/to/folder</code>.
-Replacing <code class="literal">imap://</code> by <code class="literal">imaps://</code>
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ssl"></a>2. SSL/TLS Support</h2></div></div></div><p>
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
-compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
-by running the <span class="emphasis"><em>configure</em></span> script with the
-<span class="emphasis"><em>--enable-ssl=...</em></span> option for OpenSSL or
-<span class="emphasis"><em>--enable-gnutls=...</em></span> for GnuTLS). Mutt can then
-attempt to encrypt communication with remote servers if these protocols
-are suffixed with “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="pop"></a>3. POP3 Support</h2></div></div></div><p>
-If Mutt was compiled with POP3 support (by running the <span class="emphasis"><em>configure</em></span>
-script with the <span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work
-with mailboxes located on a remote POP3 server and fetch mail for local
-browsing.
-</p><p>
-Remote POP3 servers can be accessed using URLs with the <code class="literal">pop</code> protocol
-for unencrypted and <code class="literal">pops</code> for encrypted
-communication, see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details.
-</p><p>
-Polling for new mail is more expensive over POP3 than locally. For this
-reason the frequency at which Mutt will check for mail remotely can be
-controlled by the
-<a class="link" href="#pop-checkinterval" title="3.218. pop_checkinterval">$pop_checkinterval</a>
-variable, which defaults to every 60 seconds.
-</p><a id="fetch-mail"></a><p>
-Another way to access your POP3 mail is the <code class="literal"><fetch-mail$</code> function
-(default: G). It allows to connect to <a class="link" href="#pop-host" title="3.220. pop_host">$pop_host</a>, fetch all your new mail and place it in the
-local <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a>. After this
-point, Mutt runs exactly as if the mail had always been local.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you only need to fetch all messages to a
-local mailbox you should consider using a specialized program, such as
-<code class="literal">fetchmail</code>, <code class="literal">getmail</code> or similar.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="imap"></a>4. IMAP Support</h2></div></div></div><p>
-If Mutt was compiled with IMAP support (by running the <span class="emphasis"><em>configure</em></span>
-script with the <span class="emphasis"><em>--enable-imap</em></span> flag), it has the ability to work
-with folders located on a remote IMAP server.
-</p><p>
-You can access the remote inbox by selecting the folder by its URL
-(see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details) using the
-<code class="literal">imap</code> or <code class="literal">imaps</code> protocol.
-Alternatively, a pine-compatible notation is also supported, ie
-<code class="literal">{[username@]imapserver[:port][/ssl]}path/to/folder</code>
-</p><p>
-Note that not all servers use “<span class="quote">/</span>” as the hierarchy separator. Mutt should
-correctly notice which separator is being used by the server and convert
-paths accordingly.
-</p><p>
-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
-<span class="emphasis"><em>toggle-subscribed</em></span> command. See also the
-<a class="link" href="#imap-list-subscribed" title="3.89. imap_list_subscribed">$imap_list_subscribed</a> variable.
-</p><p>
-Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
-want to carefully tune the
-<a class="link" href="#mail-check" title="3.105. mail_check">$mail_check</a>
-and
-<a class="link" href="#timeout" title="3.290. timeout">$timeout</a>
-variables. Personally I use
-</p><pre class="screen">
-set mail_check=90
-set timeout=15
-</pre><p>
-with relatively good results over my slow modem line.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that if you are using mbox as the mail store on UW servers prior to
-v12.250, the server has been reported to disconnect a client if another client
-selects the same folder.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-browser"></a>4.1. The Folder Browser</h3></div></div></div><p>
-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:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-In lieu 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.
-</p></li><li><p>
-For the case where an entry can contain both messages and
-subfolders, the selection key (bound to <code class="literal">enter</code> by default)
-will choose to descend into the subfolder view. If you wish to view
-the messages in that folder, you must use <code class="literal">view-file</code> instead
-(bound to <code class="literal">space</code> by default).
-</p></li><li><p>
-You can create, delete and rename mailboxes with the
-<code class="literal">create-mailbox</code>, <code class="literal">delete-mailbox</code>, and
-<code class="literal">rename-mailbox</code> commands (default bindings: <code class="literal">C</code>,
-<code class="literal">d</code> and <code class="literal">r</code>, respectively). You may also
-<code class="literal">subscribe</code> and <code class="literal">unsubscribe</code> to mailboxes (normally
-these are bound to <code class="literal">s</code> and <code class="literal">u</code>, respectively).
-</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authentication"></a>4.2. Authentication</h3></div></div></div><p>
-Mutt 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".
-</p><p>
-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 library
-installed on your system and compile mutt with the <span class="emphasis"><em>--with-sasl</em></span> flag.
-</p><p>
-Mutt will try whichever methods are compiled in and available on the server,
-in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-</p><p>
-There are a few variables which control authentication:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="link" href="#imap-user" title="3.96. imap_user">$imap_user</a> - 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 (ie by using a mailbox name of the form
-<code class="literal">{user@host}</code>).
-</p></li><li><p>
-<a class="link" href="#imap-pass" title="3.91. imap_pass">$imap_pass</a> - a
-password which you may preset, used by all authentication methods where
-a password is needed.
-</p></li><li><p>
-<a class="link" href="#imap-authenticators" title="3.83. imap_authenticators">$imap_authenticators</a> - 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).
-</p></li></ul></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="smtp"></a>5. SMTP Support</h2></div></div></div><p>
-Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
-was configured and built with <code class="literal">--enable-smtp</code>.
-</p><p>
-If the configuration variable
-<a class="link" href="#smtp-url" title="3.272. smtp_url">$smtp_url</a> is set, mutt
-will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a>.
-</p><p>
-For details on the URL syntax, please see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>.
-</p><p>
-The built-in SMTP support supports encryption (the <code class="literal">smtps</code> protocol
-using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
-for SASL are specified in <a class="link" href="#smtp-authenticators" title="3.270. smtp_authenticators">$smtp_authenticators</a>
-defaulting to an empty list which makes mutt try all available methods
-from most-secure to least-secure.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="account-hook"></a>6. Managing multiple accounts</h2></div></div></div><p>
-If you happen to have accounts on multiple IMAP, POP and/or SMTP 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 which includes (for example) polling for new mail, storing Fcc
-messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
-as passwords or tunnel commands but not settings such as sender
-address or name (because in general it should be considered unpredictable
-which account-hook was last used).
-</p><p>
-Some examples:
-</p><pre class="screen">
-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"'
-account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="caching"></a>7. Local caching</h2></div></div></div><p>
-Mutt contains two types of local caching: <span class="emphasis"><em>(1)</em></span>
-the so-called “<span class="quote">header caching</span>” and <span class="emphasis"><em>(2)</em></span> the
-so-called “<span class="quote">body caching</span>” which are both described in this section.
-</p><p>
-Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
-support as these use it (body caching requires no external library).
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-caching"></a>7.1. Header caching</h3></div></div></div><p>
-Mutt provides optional support for caching message headers for the
-following types of folders: IMAP, POP, Maildir and MH. Header caching
-greatly improves speed because for remote folders, headers
-usually only need to be downloaded once. For Maildir and MH, reading the
-headers from a single file is much faster than looking at possibly
-thousands of single files (since Maildir and MH use one file per message.)
-</p><p>
-Header caching can be enabled via the configure script and the
-<span class="emphasis"><em>--enable-hcache</em></span> option. It's not turned on
-by default because external database libraries are required: one
-of tokyocabinet, qdbm, gdbm or bdb must be present.
-</p><p>
-If enabled, <a class="link" href="#header-cache" title="3.109. header_cache">$header_cache</a> can be
-used to either point to a file or a directory. If set to point to
-a file, one database file for all folders will be used (which may
-result in lower performance), but one file per folder if it points
-to a directory.
-</p><p>
-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-</p><pre class="screen">
-$ printf '%s' '/path/to/folder' | md5sum
-</pre><p>
-The <code class="literal">md5sum</code> command may also be
-named <code class="literal">md5</code>, depending on your operating system.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="body-caching"></a>7.2. Body caching</h3></div></div></div><p>
-Both cache methods can be combined using the same directory for storage
-(and for IMAP/POP even provide meaningful file names) which simplifies
-manual maintenance tasks.
-</p><p>
-In addition to caching message headers only, mutt can also cache
-whole message bodies. This results in faster display of messages
-for POP and IMAP folders because messages usually have to be
-downloaded only once.
-</p><p>
-For configuration, the variable <a class="link" href="#message-cachedir" title="3.133. message_cachedir">$message_cachedir</a> must point to a
-directory. There, mutt will create a hierarchy of subdirectories
-named like: <code class="literal">proto:user@hostname</code> where
-<code class="literal">proto</code> is either “<span class="quote">pop</span>” or “<span class="quote">imap.</span>” Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-</p><p>
-All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maint-cache"></a>7.3. Maintenance</h3></div></div></div><p>
-Mutt does not (yet) support maintenance features for header cache
-database files so that files have to be removed in case they grow too
-big. It depends on the database library used for header caching whether
-disk space freed by removing messages is re-used.
-</p><p>
-For body caches, mutt can keep the local cache in sync with the
-remote mailbox if the
-<a class="link" href="#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a>
-variable is set. Cleaning means to remove messages from the cache which
-are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
-delete messages (Mutt itself removes deleted messages from the cache
-when syncing a mailbox). As cleaning can take a noticeable amount of time,
-it should not be set in general but only occasionally.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exact-address"></a>8. Exact address generation</h2></div></div></div><p>
-Mutt supports the “<span class="quote">Name <user@host></span>” address syntax for reading and
-writing messages, the older “<span class="quote">user@host (Name)</span>” syntax is only supported when
-reading messages. The <span class="emphasis"><em>--enable-exact-address</em></span>
-switch can be given to configure to build it with write-support
-for the latter syntax. <code class="literal">EXACT_ADDRESS</code> in the output of
-<code class="literal">mutt -v</code> indicates whether it's supported.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="tuning"></a>Chapter 7. Performance tuning</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="#tuning-search">3. Searching and limiting</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-mailboxes"></a>1. Reading and writing mailboxes</h2></div></div></div><p>
-Mutt's performance when reading mailboxes can be improved in two ways:
-</p><div class="orderedlist"><ol type="1"><li><p>
-For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
-performance can be greatly improved using
-<a class="link" href="#header-caching" title="7.1. Header caching">header caching</a>.
-Using a single database per folder may further increase
-performance.
-</p></li><li><p>
-Mutt provides the <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>
-and <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a>
-variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
-time on updating the progress counter than it spends on
-actually reading/writing folders.
-</p><p>
-For example, when opening a maildir folder with a few
-thousand messages, the default value for
-<a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>
-may be too low. It can be tuned on on a folder-basis using
-<a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hooks</a>:
-</p><pre class="screen">
-# use very high $read_inc to speed up reading hcache'd maildirs
-folder-hook . 'set read_inc=1000'
-# use lower value for reading slower remote IMAP folders
-folder-hook ^imap 'set read_inc=100'
-# use even lower value for reading even slower remote POP folders
-folder-hook ^pop 'set read_inc=1'</pre></li></ol></div><p>These settings work on a per-message basis. However, as messages may
-greatly differ in size and certain operations are much faster than others,
-even per-folder settings of the increment variables may not be
-desirable as they produce either too few or too much progress updates.
-Thus, Mutt allows to limit the number of progress updates per second it'll
-actually send to the terminal using the
-<a class="link" href="#time-inc" title="3.289. time_inc">$time_inc</a> variable.</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-messages"></a>2. Reading messages from remote folders</h2></div></div></div><p>
-Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
-limited number of recently viewed messages (usually 10) per
-session (so that it will be gone for the next session.)
-</p><p>
-To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
-<a class="link" href="#body-caching" title="7.2. Body caching">body caching</a> for details.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-search"></a>3. Searching and limiting</h2></div></div></div><p>
-When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
-searches. For regular expressions, patterns are prefixed with
-“<span class="quote">˜</span>” and with “<span class="quote">=</span>” for string searches.
-</p><p>
-Even though a regular expression search is fast, it's several times
-slower than a pure string search which is noticeable especially on large
-folders. As a consequence, a string search should be used instead of a
-regular expression search if the user already knows enough about the
-search pattern.
-</p><p>
-For example, when limiting a large folder to all messages sent to or by
-an author, it's much faster to search for the initial part of an e-mail
-address via <code class="literal">=Luser@</code> instead of
-<code class="literal">˜Luser@</code>. This is especially true for searching
-message bodies since a larger amount of input has to be searched.
-</p><p>
-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="reference"></a>Chapter 8. Reference</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="#sidebar-delim">3.150. sidebar_delim</a></span></dt><dt><span class="sect2"><a href="#sidebar-visible">3.151. sidebar_visible</a></span></dt><dt><span class="sect2"><a href="#sidebar-width">3.152. sidebar_width</a></span></dt><dt><span class="sect2"><a href="#pgp-use-gpg-agent">3.153. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="#crypt-verify-sig">3.154. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="#smime-is-default">3.155. smime_is_default</a></span></dt><dt><span class="sect2"><a href="#smime-ask-cert-label">3.156. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-use-default-key">3.157. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="#pgp-entry-format">3.158. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="#pgp-good-sign">3.159. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="#pgp-check-exit">3.160. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="#pgp-long-ids">3.161. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="#pgp-retainable-sigs">3.162. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="#pgp-autoinline">3.163. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="#pgp-replyinline">3.164. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="#pgp-show-unusable">3.165. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-as">3.166. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="#pgp-strict-enc">3.167. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="#pgp-timeout">3.168. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="#pgp-sort-keys">3.169. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-auto">3.170. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="#pgp-auto-decode">3.171. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-filename">3.172. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-description">3.173. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="#pgp-decode-command">3.174. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="#pgp-getkeys-command">3.175. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-command">3.176. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="#pgp-decrypt-command">3.177. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#pgp-clearsign-command">3.178. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-command">3.179. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-sign-command">3.180. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-only-command">3.181. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="#pgp-import-command">3.182. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="#pgp-export-command">3.183. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-key-command">3.184. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-secring-command">3.185. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-pubring-command">3.186. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="#forward-decrypt">3.187. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="#smime-timeout">3.188. smime_timeout</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-with">3.189. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="#smime-keys">3.190. smime_keys</a></span></dt><dt><span class="sect2"><a href="#smime-ca-location">3.191. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="#smime-certificates">3.192. smime_certificates</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-command">3.193. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-command">3.194. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-opaque-command">3.195. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-command">3.196. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-opaque-command">3.197. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-command">3.198. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-pk7out-command">3.199. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-command">3.200. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-signer-cert-command">3.201. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-import-cert-command">3.202. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-email-command">3.203. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="#smime-default-key">3.204. smime_default_key</a></span></dt><dt><span class="sect2"><a href="#ssl-client-cert">3.205. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="#ssl-force-tls">3.206. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="#ssl-starttls">3.207. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="#certificate-file">3.208. certificate_file</a></span></dt><dt><span class="sect2"><a href="#ssl-use-sslv3">3.209. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="#ssl-use-tlsv1">3.210. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="#ssl-min-dh-prime-bits">3.211. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="#ssl-ca-certificates-file">3.212. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="#pipe-split">3.213. pipe_split</a></span></dt><dt><span class="sect2"><a href="#pipe-decode">3.214. pipe_decode</a></span></dt><dt><span class="sect2"><a href="#pipe-sep">3.215. pipe_sep</a></span></dt><dt><span class="sect2"><a href="#pop-authenticators">3.216. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="#pop-auth-try-all">3.217. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="#pop-checkinterval">3.218. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="#pop-delete">3.219. pop_delete</a></span></dt><dt><span class="sect2"><a href="#pop-host">3.220. pop_host</a></span></dt><dt><span class="sect2"><a href="#pop-last">3.221. pop_last</a></span></dt><dt><span class="sect2"><a href="#pop-reconnect">3.222. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="#pop-user">3.223. pop_user</a></span></dt><dt><span class="sect2"><a href="#pop-pass">3.224. pop_pass</a></span></dt><dt><span class="sect2"><a href="#post-indent-string">3.225. post_indent_string</a></span></dt><dt><span class="sect2"><a href="#postpone">3.226. postpone</a></span></dt><dt><span class="sect2"><a href="#postponed">3.227. postponed</a></span></dt><dt><span class="sect2"><a href="#preconnect">3.228. preconnect</a></span></dt><dt><span class="sect2"><a href="#print">3.229. print</a></span></dt><dt><span class="sect2"><a href="#print-command">3.230. print_command</a></span></dt><dt><span class="sect2"><a href="#print-decode">3.231. print_decode</a></span></dt><dt><span class="sect2"><a href="#print-split">3.232. print_split</a></span></dt><dt><span class="sect2"><a href="#prompt-after">3.233. prompt_after</a></span></dt><dt><span class="sect2"><a href="#query-command">3.234. query_command</a></span></dt><dt><span class="sect2"><a href="#query-format">3.235. query_format</a></span></dt><dt><span class="sect2"><a href="#quit">3.236. quit</a></span></dt><dt><span class="sect2"><a href="#quote-regexp">3.237. quote_regexp</a></span></dt><dt><span class="sect2"><a href="#read-inc">3.238. read_inc</a></span></dt><dt><span class="sect2"><a href="#read-only">3.239. read_only</a></span></dt><dt><span class="sect2"><a href="#realname">3.240. realname</a></span></dt><dt><span class="sect2"><a href="#recall">3.241. recall</a></span></dt><dt><span class="sect2"><a href="#record">3.242. record</a></span></dt><dt><span class="sect2"><a href="#reply-regexp">3.243. reply_regexp</a></span></dt><dt><span class="sect2"><a href="#reply-self">3.244. reply_self</a></span></dt><dt><span class="sect2"><a href="#reply-to">3.245. reply_to</a></span></dt><dt><span class="sect2"><a href="#resolve">3.246. resolve</a></span></dt><dt><span class="sect2"><a href="#reverse-alias">3.247. reverse_alias</a></span></dt><dt><span class="sect2"><a href="#reverse-name">3.248. reverse_name</a></span></dt><dt><span class="sect2"><a href="#reverse-realname">3.249. reverse_realname</a></span></dt><dt><span class="sect2"><a href="#rfc2047-parameters">3.250. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="#save-address">3.251. save_address</a></span></dt><dt><span class="sect2"><a href="#save-empty">3.252. save_empty</a></span></dt><dt><span class="sect2"><a href="#save-history">3.253. save_history</a></span></dt><dt><span class="sect2"><a href="#save-name">3.254. save_name</a></span></dt><dt><span class="sect2"><a href="#score">3.255. score</a></span></dt><dt><span class="sect2"><a href="#score-threshold-delete">3.256. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="#score-threshold-flag">3.257. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="#score-threshold-read">3.258. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="#send-charset">3.259. send_charset</a></span></dt><dt><span class="sect2"><a href="#sendmail">3.260. sendmail</a></span></dt><dt><span class="sect2"><a href="#sendmail-wait">3.261. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="#shell">3.262. shell</a></span></dt><dt><span class="sect2"><a href="#sig-dashes">3.263. sig_dashes</a></span></dt><dt><span class="sect2"><a href="#sig-on-top">3.264. sig_on_top</a></span></dt><dt><span class="sect2"><a href="#signature">3.265. signature</a></span></dt><dt><span class="sect2"><a href="#simple-search">3.266. simple_search</a></span></dt><dt><span class="sect2"><a href="#smart-wrap">3.267. smart_wrap</a></span></dt><dt><span class="sect2"><a href="#smileys">3.268. smileys</a></span></dt><dt><span class="sect2"><a href="#sleep-time">3.269. sleep_time</a></span></dt><dt><span class="sect2"><a href="#smtp-authenticators">3.270. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="#smtp-pass">3.271. smtp_pass</a></span></dt><dt><span class="sect2"><a href="#smtp-url">3.272. smtp_url</a></span></dt><dt><span class="sect2"><a href="#sort">3.273. sort</a></span></dt><dt><span class="sect2"><a href="#sort-alias">3.274. sort_alias</a></span></dt><dt><span class="sect2"><a href="#sort-aux">3.275. sort_aux</a></span></dt><dt><span class="sect2"><a href="#sort-browser">3.276. sort_browser</a></span></dt><dt><span class="sect2"><a href="#sort-re">3.277. sort_re</a></span></dt><dt><span class="sect2"><a href="#spam-separator">3.278. spam_separator</a></span></dt><dt><span class="sect2"><a href="#spoolfile">3.279. spoolfile</a></span></dt><dt><span class="sect2"><a href="#status-chars">3.280. status_chars</a></span></dt><dt><span class="sect2"><a href="#status-format">3.281. status_format</a></span></dt><dt><span class="sect2"><a href="#status-on-top">3.282. status_on_top</a></span></dt><dt><span class="sect2"><a href="#strict-threads">3.283. strict_threads</a></span></dt><dt><span class="sect2"><a href="#suspend">3.284. suspend</a></span></dt><dt><span class="sect2"><a href="#text-flowed">3.285. text_flowed</a></span></dt><dt><span class="sect2"><a href="#thread-received">3.286. thread_received</a></span></dt><dt><span class="sect2"><a href="#thorough-search">3.287. thorough_search</a></span></dt><dt><span class="sect2"><a href="#tilde">3.288. tilde</a></span></dt><dt><span class="sect2"><a href="#time-inc">3.289. time_inc</a></span></dt><dt><span class="sect2"><a href="#timeout">3.290. timeout</a></span></dt><dt><span class="sect2"><a href="#tmpdir">3.291. tmpdir</a></span></dt><dt><span class="sect2"><a href="#to-chars">3.292. to_chars</a></span></dt><dt><span class="sect2"><a href="#trash">3.293. trash</a></span></dt><dt><span class="sect2"><a href="#tunnel">3.294. tunnel</a></span></dt><dt><span class="sect2"><a href="#use-8bitmime">3.295. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="#use-domain">3.296. use_domain</a></span></dt><dt><span class="sect2"><a href="#use-envelope-from">3.297. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="#use-from">3.298. use_from</a></span></dt><dt><span class="sect2"><a href="#use-idn">3.299. use_idn</a></span></dt><dt><span class="sect2"><a href="#use-ipv6">3.300. use_ipv6</a></span></dt><dt><span class="sect2"><a href="#user-agent">3.301. user_agent</a></span></dt><dt><span class="sect2"><a href="#visual">3.302. visual</a></span></dt><dt><span class="sect2"><a href="#wait-key">3.303. wait_key</a></span></dt><dt><span class="sect2"><a href="#weed">3.304. weed</a></span></dt><dt><span class="sect2"><a href="#wrap">3.305. wrap</a></span></dt><dt><span class="sect2"><a href="#wrap-search">3.306. wrap_search</a></span></dt><dt><span class="sect2"><a href="#wrapmargin">3.307. wrapmargin</a></span></dt><dt><span class="sect2"><a href="#write-inc">3.308. write_inc</a></span></dt><dt><span class="sect2"><a href="#write-bcc">3.309. write_bcc</a></span></dt><dt><span class="sect2"><a href="#xterm-icon">3.310. xterm_icon</a></span></dt><dt><span class="sect2"><a href="#xterm-set-titles">3.311. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="#xterm-title">3.312. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commandline"></a>1. Command line options</h2></div></div></div><p>
-Running <code class="literal">mutt</code> with no arguments will make Mutt attempt to read your spool
-mailbox. However, it is possible to read other mailboxes and
-to send messages from the command line as well.
-</p><div class="table"><a id="tab-commandline-options"></a><p class="title"><b>Table 8.1. Command line options</b></p><div class="table-contents"><table summary="Command line options" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td>-A</td><td>expand an alias</td></tr><tr><td>-a</td><td>attach a file to a message</td></tr><tr><td>-b</td><td>specify a blind carbon-copy (BCC) address</td></tr><tr><td>-c</td><td>specify a carbon-copy (Cc) address</td></tr><tr><td>-D</td><td>print the value of all mutt variables to stdout</td></tr><tr><td>-e</td><td>specify a config command to be run after initialization files are read</td></tr><tr><td>-f</td><td>specify a mailbox to load</td></tr><tr><td>-F</td><td>specify an alternate file to read initialization commands</td></tr><tr><td>-h</td><td>print help on command line options</td></tr><tr><td>-H</td><td>specify a draft file from which to read a header and body</td></tr><tr><td>-i</td><td>specify a file to include in a message composition</td></tr><tr><td>-m</td><td>specify a default mailbox type</td></tr><tr><td>-n</td><td>do not read the system Muttrc</td></tr><tr><td>-p</td><td>recall a postponed message</td></tr><tr><td>-Q</td><td>query a configuration variable</td></tr><tr><td>-R</td><td>open mailbox in read-only mode</td></tr><tr><td>-s</td><td>specify a subject (enclose in quotes if it contains spaces)</td></tr><tr><td>-v</td><td>show version number and compile-time definitions</td></tr><tr><td>-x</td><td>simulate the mailx(1) compose mode</td></tr><tr><td>-y</td><td>show a menu containing the files specified by the mailboxes command</td></tr><tr><td>-z</td><td>exit immediately if there are no messages in the mailbox</td></tr><tr><td>-Z</td><td>open the first folder with new message,exit immediately if none</td></tr></tbody></table></div></div><br class="table-break" /><p>
-To read messages in a mailbox
-</p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-nz</code>] [<code class="option">-F</code>
-<em class="replaceable"><code>muttrc</code></em>
-] [<code class="option">-m</code>
-<em class="replaceable"><code>type</code></em>
-] [<code class="option">-f</code>
-<em class="replaceable"><code>mailbox</code></em>
-]</p></div><p>
-To compose a new message
-</p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-n</code>] [<code class="option">-F</code>
-<em class="replaceable"><code>muttrc</code></em>
-] [<code class="option">-c</code>
-<em class="replaceable"><code>address</code></em>
-] [<code class="option">-i</code>
-<em class="replaceable"><code>filename</code></em>
-] [<code class="option">-s</code>
-<em class="replaceable"><code>subject</code></em>
-] [
-<code class="option">-a</code>
-<em class="replaceable"><code>file</code></em>
- [...]
---
-]
-<em class="replaceable"><code>address</code></em>
-... </p></div><p>
-Mutt also supports a “<span class="quote">batch</span>” mode to send prepared messages. Simply redirect
-input from the file you wish to send. For example,
-</p><p>
-<code class="literal">mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat</code>
-</p><p>
-This command will send a message to “<span class="quote">professor@bigschool.edu</span>” with a subject
-of “<span class="quote">data set for run #2</span>”. In the body of the message will be the contents
-of the file “<span class="quote">˜/run2.dat</span>”.
-</p><p>
-All files passed with -a <span class="emphasis"><em>file</em></span> will be attached as a MIME
-part to the message. To attach several files, use “<span class="quote">--</span>” to separate files and
-recipient addresses: <code class="literal">mutt -a *.png -- some@one.org</code>
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commands"></a>2. Configuration Commands</h2></div></div></div><p>
-The following are the commands understood by mutt.
-</p><div class="itemizedlist"><ul type="disc"><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#account-hook" title="6. Managing multiple accounts">account-hook</a></code>
-<em class="replaceable"><code>pattern</code></em>
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alias" title="4. Defining/Using aliases">alias</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>address</code></em>
- [
-<em class="replaceable"><code>address</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alias" title="4. Defining/Using aliases">unalias</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>key</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternates" title="11. Alternative addresses">unalternates</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternative-order" title="5. MIME Multipart/Alternative">alternative-order</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternative-order" title="5. MIME Multipart/Alternative">unalternative-order</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#auto-view" title="4. MIME Autoview">auto-view</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#auto-view" title="4. MIME Autoview">unauto-view</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#bind" title="5. Changing the default key bindings">bind</a></code>
-<em class="replaceable"><code>map</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>function</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#charset-hook" title="6. Defining aliases for character sets">charset-hook</a></code>
-<em class="replaceable"><code>alias</code></em>
-
-<em class="replaceable"><code>charset</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#charset-hook" title="6. Defining aliases for character sets">iconv-hook</a></code>
-<em class="replaceable"><code>charset</code></em>
-
-<em class="replaceable"><code>local-charset</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">uncolor</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>pattern</code></em>
-... </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#exec" title="23. Executing functions">exec</a></code>
-<em class="replaceable"><code>function</code></em>
- [
-<em class="replaceable"><code>function</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a></code>
-<em class="replaceable"><code>[!]regexp</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#addrgroup" title="3. Address groups">group</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#addrgroup" title="3. Address groups">ungroup</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#hdr-order">hdr_order</a></code>
-<em class="replaceable"><code>header</code></em>
- [
-<em class="replaceable"><code>header</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#hdr-order">unhdr_order</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>header</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#ignore" title="10. Message header display">ignore</a></code>
-<em class="replaceable"><code>pattern</code></em>
- [
-<em class="replaceable"><code>pattern</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#ignore" title="10. Message header display">unignore</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#lists" title="12. Mailing lists">lists</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#lists" title="12. Mailing lists">unlists</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#macro" title="8. Keyboard macros">macro</a></code>
-<em class="replaceable"><code>menu</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>sequence</code></em>
- [
-<em class="replaceable"><code>description</code></em>
-]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></code>
-<em class="replaceable"><code>mailbox</code></em>
- [
-<em class="replaceable"><code>mailbox</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">unmailboxes</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mailbox</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mime-lookup" title="7. MIME Lookup">mime-lookup</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mime-lookup" title="7. MIME Lookup">unmime-lookup</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>attribute</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">unmono</a></code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></code>
-<em class="replaceable"><code>string</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#my-hdr" title="15. User defined headers">unmy_hdr</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>field</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#crypt-hook" title="21. Choosing the cryptographic key of the recipient">crypt-hook</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>keyid</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#push" title="22. Adding key sequences to the keyboard buffer">push</a></code>
-<em class="replaceable"><code>string</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">reset</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#score" title="3.255. score">score</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>value</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#score" title="3.255. score">unscore</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#reply-hook">reply-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#send2-hook">send2-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">set</a></code> {
-[ <code class="option">no</code> | <code class="option">inv</code> ]
-<em class="replaceable"><code>variable</code></em>
- |
-<em class="replaceable"><code>variable=value</code></em>
- } [...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">unset</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#source" title="27. Reading initialization commands from another file">source</a></code>
-<em class="replaceable"><code>filename</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#spam" title="25. Spam detection">spam</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>format</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#spam" title="25. Spam detection">nospam</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
- }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#subscribe">subscribe</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#subscribe">unsubscribe</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">toggle</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#unhook" title="29. Removing hooks">unhook</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>hook-type</code></em>
- }</p></div></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="variables"></a>3. Configuration variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-nosubject"></a>3.1. abort_nosubject</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-If set to <span class="emphasis"><em>yes</em></span>, when composing messages and no subject is given
-at the subject prompt, composition will be aborted. If set to
-<span class="emphasis"><em>no</em></span>, composing messages with no subject given at the subject
-prompt will never be aborted.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-unmodified"></a>3.2. abort_unmodified</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If set to <span class="emphasis"><em>yes</em></span>, composition will automatically abort after
-editing the message body if no changes are made to the file (this
-check only happens after the <span class="emphasis"><em>first</em></span> edit of the file). When set
-to <span class="emphasis"><em>no</em></span>, composition will never be aborted.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-file"></a>3.3. alias_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.muttrc</code></span>”</p></div><p>
-The default file in which to save aliases created by the
-<code class="literal"><a class="link" href="#create-alias"><create-alias></a></code> function. Entries added to this file are
-encoded in the character set specified by <a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a> if it
-is <span class="emphasis"><em>set</em></span> or the current character set otherwise.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> Mutt will not automatically source this file; you must
-explicitly use the “<span class="quote"><a class="link" href="#source" title="27. Reading initialization commands from another file">source</a></span>” command for it to be executed in case
-this option points to a dedicated alias file.
-</p><p>
-The default for this option is the currently used muttrc file, or
-“<span class="quote">˜/.muttrc</span>” if no user muttrc was found.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-format"></a>3.4. alias_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %2f %t %-10a %r</code></span>”</p></div><p>
-Specifies the format of the data displayed for the “<span class="quote"><a class="link" href="#alias" title="4. Defining/Using aliases">alias</a></span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are available:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>alias name
-</p></dd><dt><span class="term">%f </span></dt><dd><p>flags - currently, a “<span class="quote">d</span>” for an alias marked for deletion
-</p></dd><dt><span class="term">%n </span></dt><dd><p>index number
-</p></dd><dt><span class="term">%r </span></dt><dd><p>address which alias expands to
-</p></dd><dt><span class="term">%t </span></dt><dd><p>character which indicates if the alias is tagged for inclusion
-</p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-8bit"></a>3.5. allow_8bit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether 8-bit data is converted to 7-bit using either Quoted-
-Printable or Base64 encoding when sending mail.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-ansi"></a>3.6. allow_ansi</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <span class="emphasis"><em>set</em></span>,
-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
-
-</p><pre class="screen">
-[-- PGP output follows ...
-
-</pre><p>
-and give it the same color as your attachment color (see also
-<a class="link" href="#crypt-timestamp" title="3.149. crypt_timestamp">$crypt_timestamp</a>).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="arrow-cursor"></a>3.7. arrow_cursor</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, an arrow (“<span class="quote">-></span>”) 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ascii-chars"></a>3.8. ascii_chars</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will use plain ASCII characters when displaying thread
-and attachment trees, instead of the default <span class="emphasis"><em>ACS</em></span> characters.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askbcc"></a>3.9. askbcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
-before editing an outgoing message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askcc"></a>3.10. askcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for carbon-copy (Cc) recipients before
-editing the body of an outgoing message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="assumed-charset"></a>3.11. assumed_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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 “<span class="quote">us-ascii</span>”.
-</p><p>
-For example, Japanese users might prefer this:
-
-</p><pre class="screen">
-set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</pre><p>
-However, only the first content is valid for the message body.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-charset"></a>3.12. attach_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable is a colon-separated list of character encoding
-schemes for text file attachments. Mutt uses this setting to guess
-which encoding files being attached are encoded in to convert them to
-a proper character set given in <a class="link" href="#send-charset" title="3.259. send_charset">$send_charset</a>.
-</p><p>
-If <span class="emphasis"><em>unset</em></span>, the value of <a class="link" href="#charset" title="3.25. charset">$charset</a> will be used instead.
-For example, the following configuration would work for Japanese
-text handling:
-
-</p><pre class="screen">
-set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</pre><p>
-Note: for Japanese users, “<span class="quote">iso-2022-*</span>” must be put at the head
-of the value as shown above if included.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-format"></a>3.13. attach_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] </code></span>”</p></div><p>
-This variable describes the format of the “<span class="quote">attachment</span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are understood:
-
-</p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>charset
-</p></dd><dt><span class="term">%c </span></dt><dd><p>requires charset conversion (“<span class="quote">n</span>” or “<span class="quote">c</span>”)
-</p></dd><dt><span class="term">%D </span></dt><dd><p>deleted flag
-</p></dd><dt><span class="term">%d </span></dt><dd><p>description
-</p></dd><dt><span class="term">%e </span></dt><dd><p>MIME content-transfer-encoding
-</p></dd><dt><span class="term">%f </span></dt><dd><p>filename
-</p></dd><dt><span class="term">%I </span></dt><dd><p>disposition (“<span class="quote">I</span>” for inline, “<span class="quote">A</span>” for attachment)
-</p></dd><dt><span class="term">%m </span></dt><dd><p>major MIME type
-</p></dd><dt><span class="term">%M </span></dt><dd><p>MIME subtype
-</p></dd><dt><span class="term">%n </span></dt><dd><p>attachment number
-</p></dd><dt><span class="term">%Q </span></dt><dd><p>“<span class="quote">Q</span>”, if MIME part qualifies for attachment counting
-</p></dd><dt><span class="term">%s </span></dt><dd><p>size
-</p></dd><dt><span class="term">%t </span></dt><dd><p>tagged flag
-</p></dd><dt><span class="term">%T </span></dt><dd><p>graphic tree characters
-</p></dd><dt><span class="term">%u </span></dt><dd><p>unlink (=to delete) flag
-</p></dd><dt><span class="term">%X </span></dt><dd><p>number of qualifying MIME parts in this part and its children
-(please see the “<span class="quote"><a class="link" href="#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-sep"></a>3.14. attach_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
-The separator to add between attachments when operating (saving,
-printing, piping, etc) on a list of tagged attachments.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-split"></a>3.15. attach_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this variable is <span class="emphasis"><em>unset</em></span>, when operating (saving, printing, piping,
-etc) on a list of tagged attachments, Mutt will concatenate the
-attachments and will operate on them as a single attachment. The
-<a class="link" href="#attach-sep" title="3.14. attach_sep">$attach_sep</a> separator is added after each attachment. When <span class="emphasis"><em>set</em></span>,
-Mutt will operate on the attachments one by one.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attribution"></a>3.16. attribution</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">On %d, %n wrote:</code></span>”</p></div><p>
-This is the string that will precede a message which has been included
-in a reply. For a full listing of defined <code class="literal">printf(3)</code>-like sequences see
-the section on <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="autoedit"></a>3.17. autoedit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span> along with <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>, Mutt will skip the initial
-send-menu (prompting for subject and recipients) 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.
-</p><p>
-Also see <a class="link" href="#fast-reply" title="3.55. fast_reply">$fast_reply</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="auto-tag"></a>3.18. auto_tag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, functions in the <span class="emphasis"><em>index</em></span> menu which affect a message
-will be applied to all tagged messages (if there are any). When
-unset, you must first use the <code class="literal"><tag-prefix></code> function (bound to “<span class="quote">;</span>”
-by default) to make the next function apply to all tagged messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep"></a>3.19. beep</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep when an error occurs.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep-new"></a>3.20. beep_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep whenever it prints a message
-notifying you of new mail. This is independent of the setting of the
-<a class="link" href="#beep" title="3.19. beep">$beep</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce"></a>3.21. bounce</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether you will be asked to confirm bouncing messages.
-If set to <span class="emphasis"><em>yes</em></span> you don't get asked if you want to bounce a
-message. Setting this variable to <span class="emphasis"><em>no</em></span> is not generally useful,
-and thus not recommended, because you are unable to bounce messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce-delivered"></a>3.22. bounce_delivered</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will include Delivered-To headers when
-bouncing messages. Postfix users may wish to <span class="emphasis"><em>unset</em></span> this variable.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is unset by default in
-/etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="braille-friendly"></a>3.23. braille_friendly</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will place the cursor at the beginning
-of the current line in menus, even when the <a class="link" href="#arrow-cursor" title="3.7. arrow_cursor">$arrow_cursor</a> variable
-is <span class="emphasis"><em>unset</em></span>, making it easier for blind persons using Braille displays to
-follow these menus. The option is <span class="emphasis"><em>unset</em></span> by default because many
-visual terminals don't permit making the cursor invisible.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-mbox-size"></a>3.24. check_mbox_size</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
-</p><p>
-This variable is <span class="emphasis"><em>unset</em></span> by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
-</p><p>
-Note that enabling this variable should happen before any “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="charset"></a>3.25. charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Character set your terminal uses to display and enter textual data.
-It is also the fallback for <a class="link" href="#send-charset" title="3.259. send_charset">$send_charset</a>.
-</p><p>
-Upon startup Mutt tries to derive this value from environment variables
-such as <code class="literal">$LC_CTYPE</code> or <code class="literal">$LANG</code>.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> It should only be set in case Mutt isn't abled to determine the
-character set used correctly.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-new"></a>3.26. check_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-<span class="bold"><strong>Note:</strong></span> this option only affects <span class="emphasis"><em>maildir</em></span> and <span class="emphasis"><em>MH</em></span> style
-mailboxes.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt 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
-this variable is <span class="emphasis"><em>unset</em></span>, no check for new mail is performed
-while the mailbox is open.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="collapse-unread"></a>3.27. collapse_unread</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, Mutt will not collapse a thread if it contains any
-unread messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="uncollapse-jump"></a>3.28. uncollapse_jump</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will jump to the next unread message, if any,
-when the current thread is <span class="emphasis"><em>un</em></span>collapsed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-format"></a>3.29. compose_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-</code></span>”</p></div><p>
-Controls the format of the status line displayed in the “<span class="quote">compose</span>”
-menu. This string is similar to <a class="link" href="#status-format" title="3.281. status_format">$status_format</a>, but has its own
-set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>total number of attachments
-</p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
-</p></dd><dt><span class="term">%l </span></dt><dd><p>approximate size (in bytes) of the current message
-</p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
-</p></dd></dl></div><p>
-See the text describing the <a class="link" href="#status-format" title="3.281. status_format">$status_format</a> option for more
-information on how to set <a class="link" href="#compose-format" title="3.29. compose_format">$compose_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="config-charset"></a>3.30. config_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-When defined, Mutt will recode commands in rc files from this
-encoding to the current character set as specified by <a class="link" href="#charset" title="3.25. charset">$charset</a>
-and aliases written to <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> from the current character set.
-</p><p>
-Please note that if setting <a class="link" href="#charset" title="3.25. charset">$charset</a> it must be done before
-setting <a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a>.
-</p><p>
-Recoding should be avoided as it may render unconvertable
-characters as question marks which can lead to undesired
-side effects (for example in regular expressions).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmappend"></a>3.31. confirmappend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when appending messages to
-an existing mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmcreate"></a>3.32. confirmcreate</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when saving messages to a
-mailbox which does not yet exist before creating it.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="connect-timeout"></a>3.33. connect_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 30</p></div><p>
-Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-many seconds if the connection is not able to be established. A negative
-value causes Mutt to wait indefinitely for the connection attempt to succeed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="content-type"></a>3.34. content_type</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">text/plain</code></span>”</p></div><p>
-Sets the default Content-Type for the body of newly composed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="copy"></a>3.35. copy</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether or not copies of your outgoing messages
-will be saved for later references. Also see <a class="link" href="#record" title="3.242. record">$record</a>,
-<a class="link" href="#save-name" title="3.254. save_name">$save_name</a>, <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> and “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-gpgme"></a>3.36. crypt_use_gpgme</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls the use of the GPGME-enabled crypto backends.
-If it is <span class="emphasis"><em>set</em></span> and Mutt was built with gpgme support, the gpgme code for
-S/MIME and PGP will be used instead of the classic code. Note that
-you need to set this option in .muttrc; it won't have any effect when
-used interactively.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-pka"></a>3.37. crypt_use_pka</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether mutt uses PKA
-(see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
-verification (only supported by the GPGME backend).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autopgp"></a>3.38. crypt_autopgp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages. See also <a class="link" href="#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
-<a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
-<a class="link" href="#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosmime"></a>3.39. crypt_autosmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also <a class="link" href="#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
-<a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
-<a class="link" href="#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-format"></a>3.40. date_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">!%a, %b %d, %Y at %I:%M:%S%p %Z</code></span>”</p></div><p>
-This variable controls the format of the date printed by the “<span class="quote">%d</span>”
-sequence in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>. This is passed to the <code class="literal">strftime(3)</code>
-function to process the date, see the man page for the proper syntax.
-</p><p>
-Unless the first character in the string is a bang (“<span class="quote">!</span>”), the month
-and week day names are expanded according to the locale specified in
-the variable <a class="link" href="#locale" title="3.104. locale">$locale</a>. 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 <span class="emphasis"><em>C</em></span> locale (that is in US
-English).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="default-hook"></a>3.41. default_hook</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜f %s !˜P | (˜P ˜C %s)</code></span>”</p></div><p>
-This variable controls how “<span class="quote"><a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a></span>”, “<span class="quote"><a class="link" href="#reply-hook">reply-hook</a></span>”, “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”,
-“<span class="quote"><a class="link" href="#send2-hook">send2-hook</a></span>”, “<span class="quote"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, and “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” 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.
-</p><p>
-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
-“<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”) and is to or cc'ed to a user matching the given
-regular expression.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete"></a>3.42. delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not messages are really deleted when closing or
-synchronizing a mailbox. If set to <span class="emphasis"><em>yes</em></span>, messages marked for
-deleting will automatically be purged without prompting. If set to
-<span class="emphasis"><em>no</em></span>, messages marked for deletion will be kept in the mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete-untag"></a>3.43. delete_untag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this option is <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="digest-collapse"></a>3.44. digest_collapse</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this option is <span class="emphasis"><em>set</em></span>, mutt's received-attachments menu will not show the subparts of
-individual messages in a multipart/digest. To see these subparts, press “<span class="quote">v</span>” on that menu.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="display-filter"></a>3.45. display_filter</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-When set, specifies a command used to filter messages. When a message
-is viewed it is passed as standard input to <a class="link" href="#display-filter" title="3.45. display_filter">$display_filter</a>, and the
-filtered message is read from the standard output.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dotlock-program"></a>3.46. dotlock_program</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">/usr/bin/mutt_dotlock</code></span>”</p></div><p>
-Contains the path of the <code class="literal">mutt_dotlock(8)</code> binary to be used by
-mutt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-notify"></a>3.47. dsn_notify</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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: <span class="emphasis"><em>never</em></span>, to never request notification,
-<span class="emphasis"><em>failure</em></span>, to request notification on transmission failure,
-<span class="emphasis"><em>delay</em></span>, to be notified of message delays, <span class="emphasis"><em>success</em></span>, to be
-notified of successful transmission.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set dsn_notify="failure,delay"
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> when using <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-N</code> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-return"></a>3.48. dsn_return</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable controls how much of your message is returned in DSN
-messages. It may be set to either <span class="emphasis"><em>hdrs</em></span> to return just the
-message header, or <span class="emphasis"><em>full</em></span> to return the full message.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set dsn_return=hdrs
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> when using <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-R</code> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="duplicate-threads"></a>3.49. duplicate_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether mutt, when <a class="link" href="#sort" title="3.273. sort">$sort</a> is set to <span class="emphasis"><em>threads</em></span>, threads
-messages with the same Message-Id together. If it is <span class="emphasis"><em>set</em></span>, it will indicate
-that it thinks they are duplicates of each other with an equals sign
-in the thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-headers"></a>3.50. edit_headers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option allows you to edit the header of your outgoing messages
-along with the body of your message.
-</p><p>
-<span class="bold"><strong>Note</strong></span> that changes made to the References: and Date: headers are
-ignored for interoperability reasons.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor"></a>3.51. editor</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable specifies which editor is used by mutt.
-It defaults to the value of the <code class="literal">$VISUAL</code>, or <code class="literal">$EDITOR</code>, environment
-variable, or to the string “<span class="quote">/usr/bin/editor</span>” if neither of those are set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="encode-from"></a>3.52. encode_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will quoted-printable encode messages when
-they contain the string “<span class="quote">From </span>” (note the trailing space) in the beginning of a line.
-This is useful to avoid the tampering certain mail delivery and transport
-agents tend to do with messages (in order to prevent tools from
-misinterpreting the line as a mbox message separator).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="envelope-from-address"></a>3.53. envelope_from_address</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
-Default: (empty)</p></div><p>
-Manually sets the <span class="emphasis"><em>envelope</em></span> sender for outgoing messages.
-This value is ignored if <a class="link" href="#use-envelope-from" title="3.297. use_envelope_from">$use_envelope_from</a> is <span class="emphasis"><em>unset</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="escape"></a>3.54. escape</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜</code></span>”</p></div><p>
-Escape character to use for functions in the builtin editor.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fast-reply"></a>3.55. fast_reply</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, 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><p>
-<span class="bold"><strong>Note:</strong></span> this variable has no effect when the <a class="link" href="#autoedit" title="3.17. autoedit">$autoedit</a>
-variable is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-attach"></a>3.56. fcc_attach</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not attachments on outgoing messages
-are saved along with the main body of your message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-clear"></a>3.57. fcc_clear</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, FCCs will be stored unencrypted and
-unsigned, even when the actual message is encrypted and/or
-signed.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder"></a>3.58. folder</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/Mail</code></span>”</p></div><p>
-Specifies the default location of your mailboxes. A “<span class="quote">+</span>” or “<span class="quote">=</span>” 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 <span class="emphasis"><em>before</em></span>
-you use “<span class="quote">+</span>” or “<span class="quote">=</span>” for any other variables since expansion takes place
-when handling the “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder-format"></a>3.59. folder_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f</code></span>”</p></div><p>
-This variable allows you to customize the file browser display to your
-personal taste. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but has
-its own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>current file number
-</p></dd><dt><span class="term">%d </span></dt><dd><p>date/time folder was last modified
-</p></dd><dt><span class="term">%f </span></dt><dd><p>filename
-</p></dd><dt><span class="term">%F </span></dt><dd><p>file permissions
-</p></dd><dt><span class="term">%g </span></dt><dd><p>group name (or numeric gid, if missing)
-</p></dd><dt><span class="term">%l </span></dt><dd><p>number of hard links
-</p></dd><dt><span class="term">%N </span></dt><dd><p>N if folder has new mail, blank otherwise
-</p></dd><dt><span class="term">%s </span></dt><dd><p>size in bytes
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if the file is tagged, blank otherwise
-</p></dd><dt><span class="term">%u </span></dt><dd><p>owner name (or numeric uid, if missing)
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="followup-to"></a>3.60. followup_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether or not the “<span class="quote">Mail-Followup-To:</span>” header field is
-generated when sending mail. When <span class="emphasis"><em>set</em></span>, Mutt will generate this
-field when you are replying to a known mailing list, specified with
-the “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” or “<span class="quote"><a class="link" href="#lists" title="12. Mailing lists">lists</a></span>” commands.
-</p><p>
-This field has two purposes. First, preventing you from
-receiving duplicate copies of replies to messages which you send
-to mailing lists, and second, ensuring that you do get a reply
-separately for any messages sent to known lists to which you are
-not subscribed.
-</p><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="force-name"></a>3.61. force_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable is similar to <a class="link" href="#save-name" title="3.254. save_name">$save_name</a>, except that Mutt 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.
-</p><p>
-Also see the <a class="link" href="#record" title="3.242. record">$record</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decode"></a>3.62. forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
-forwarding a message. The message header is also RFC2047 decoded.
-This variable is only used, if <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>,
-otherwise <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is used instead.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-edit"></a>3.63. forward_edit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-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 “<span class="quote">no</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-format"></a>3.64. forward_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">[%a: %s]</code></span>”</p></div><p>
-This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-quote"></a>3.65. forward_quote</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, forwarded messages included in the main body of the
-message (when <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>) will be quoted using
-<a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="from"></a>3.66. from</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
-Default: (empty)</p></div><p>
-When <span class="emphasis"><em>set</em></span>, this variable contains a default from address. It
-can be overridden using “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>” (including from a “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”) and
-<a class="link" href="#reverse-name" title="3.248. reverse_name">$reverse_name</a>. This variable is ignored if <a class="link" href="#use-from" title="3.298. use_from">$use_from</a> is <span class="emphasis"><em>unset</em></span>.
-</p><p>
-This setting defaults to the contents of the environment variable <code class="literal">$EMAIL</code>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="gecos-mask"></a>3.67. gecos_mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^[^,]*</code></span>”</p></div><p>
-A regular expression used by mutt to parse the GECOS field of a password
-entry when expanding the alias. The default value
-will return the string up to the first “<span class="quote">,</span>” encountered.
-If the GECOS field contains a string like “<span class="quote">lastname, firstname</span>” then you
-should set it to “<span class="quote"><code class="literal">.*</code></span>”.
-</p><p>
-This can be useful if you see the following behavior: you address an e-mail
-to user ID “<span class="quote">stevef</span>” whose full name is “<span class="quote">Steve Franklin</span>”. If mutt expands
-“<span class="quote">stevef</span>” to “<span class="quote">"Franklin" stevef@foo.bar</span>” then you should set the <a class="link" href="#gecos-mask" title="3.67. gecos_mask">$gecos_mask</a> to
-a regular expression that will match the whole name so mutt will expand
-“<span class="quote">Franklin</span>” to “<span class="quote">Franklin, Steve</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hdrs"></a>3.68. hdrs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, the header fields normally added by the “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command are not created. This variable <span class="emphasis"><em>must</em></span> be unset before
-composing a new message or replying in order to take effect. If <span class="emphasis"><em>set</em></span>,
-the user defined header fields are added to every new message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header"></a>3.69. header</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, this variable causes Mutt to include the header
-of the message you are replying to into the edit buffer.
-The <a class="link" href="#weed" title="3.304. weed">$weed</a> setting applies.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="help"></a>3.70. help</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, help lines describing the bindings for the major functions
-provided by each menu are displayed on the first line of the screen.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> 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 is
-running. Since this variable is primarily aimed at new users, neither
-of these should present a major problem.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hidden-host"></a>3.71. hidden_host</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will skip the host name part of <a class="link" href="#hostname" title="3.80. hostname">$hostname</a> variable
-when adding the domain part to addresses. This variable does not
-affect the generation of Message-IDs, and it will not lead to the
-cut-off of first-level domains.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-limited"></a>3.72. hide_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
-by limiting, in the thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-missing"></a>3.73. hide_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages in the
-thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-thread-subject"></a>3.74. hide_thread_subject</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the subject of messages in the thread
-tree that have the same subject as their parent or closest previously
-displayed sibling.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-limited"></a>3.75. hide_top_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
-by limiting, at the top of threads in the thread tree. Note that when
-<a class="link" href="#hide-limited" title="3.72. hide_limited">$hide_limited</a> is <span class="emphasis"><em>set</em></span>, this option will have no effect.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-missing"></a>3.76. hide_top_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages at the
-top of threads in the thread tree. Note that when <a class="link" href="#hide-missing" title="3.73. hide_missing">$hide_missing</a> is
-<span class="emphasis"><em>set</em></span>, this option will have no effect.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history"></a>3.77. history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-This variable controls the size (in number of strings remembered) of
-the string history buffer per category. The buffer is cleared each time the
-variable is set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history-file"></a>3.78. history_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.mutthistory</code></span>”</p></div><p>
-The file in which Mutt will save its history.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="honor-followup-to"></a>3.79. honor_followup_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether or not a Mail-Followup-To header is
-honored when group-replying to a message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hostname"></a>3.80. hostname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the fully-qualified hostname of the system mutt is running on
-containing the host's name and the DNS domain it belongs to. It is used
-as the domain part (after “<span class="quote">@</span>”) for local email addresses as well as
-Message-Id headers.
-</p><p>
-Its value is determined at startup as follows: If the node's name
-as returned by the <code class="literal">uname(3)</code> function contains the hostname and the
-domain, these are used to construct <a class="link" href="#hostname" title="3.80. hostname">$hostname</a>. If there is no
-domain part returned, Mutt will look for a “<span class="quote">domain</span>” or “<span class="quote">search</span>”
-line in <code class="literal">/etc/resolv.conf</code> to determine the domain. Optionally, Mutt
-can be compiled with a fixed domain name in which case a detected
-one is not used.
-</p><p>
-Also see <a class="link" href="#use-domain" title="3.296. use_domain">$use_domain</a> and <a class="link" href="#hidden-host" title="3.71. hidden_host">$hidden_host</a>.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, the default for this variable is obtained
-from /etc/mailname when Mutt starts.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-linear-white-space"></a>3.81. ignore_linear_white_space</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option replaces linear-white-space between encoded-word
-and text to a single space to prevent the display of MIME-encoded
-“<span class="quote">Subject:</span>” field from being divided into multiple lines.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-list-reply-to"></a>3.82. ignore_list_reply_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Affects the behaviour of the <code class="literal"><reply></code> function when replying to
-messages from mailing lists (as defined by the “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” or
-“<span class="quote"><a class="link" href="#lists" title="12. Mailing lists">lists</a></span>” commands). When <span class="emphasis"><em>set</em></span>, if the “<span class="quote">Reply-To:</span>” field is
-set to the same value as the “<span class="quote">To:</span>” field, Mutt assumes that the
-“<span class="quote">Reply-To:</span>” 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 <span class="emphasis"><em>set</em></span>, use the <code class="literal"><a class="link" href="#list-reply"><list-reply></a></code>
-function; <code class="literal"><group-reply></code> will reply to both the sender and the
-list.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authenticators"></a>3.83. imap_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an IMAP server, in the order mutt should
-try them. Authentication methods are either “<span class="quote">login</span>” or the right
-side of an IMAP “<span class="quote">AUTH=xxx</span>” capability string, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>”
-or “<span class="quote">cram-md5</span>”. This option is case-insensitive. If it's
-<span class="emphasis"><em>unset</em></span> (the default) mutt will try all available methods,
-in order from most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set imap_authenticators="gssapi:cram-md5:login"
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> Mutt will only fall back to other authentication methods if
-the previous methods are unavailable. If a method is available but
-authentication fails, mutt will not connect to the IMAP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-check-subscribed"></a>3.84. imap_check_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, 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 just as if you had issued individual “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
-commands.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-delim-chars"></a>3.85. imap_delim_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">/.</code></span>”</p></div><p>
-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 “<span class="quote">=</span>” shortcut for your <span class="emphasis"><em>folder</em></span> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-headers"></a>3.86. imap_headers</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Mutt requests these header fields in addition to the default headers
-(“<span class="quote">Date:</span>”, “<span class="quote">From:</span>”, “<span class="quote">Subject:</span>”, “<span class="quote">To:</span>”, “<span class="quote">Cc:</span>”, “<span class="quote">Message-Id:</span>”,
-“<span class="quote">References:</span>”, “<span class="quote">Content-Type:</span>”, “<span class="quote">Content-Description:</span>”, “<span class="quote">In-Reply-To:</span>”,
-“<span class="quote">Reply-To:</span>”, “<span class="quote">Lines:</span>”, “<span class="quote">List-Post:</span>”, “<span class="quote">X-Label:</span>”) from IMAP
-servers before displaying the index menu. You may want to add more
-headers for spam detection.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> This is a space separated list, items should be uppercase
-and not contain the colon, e.g. “<span class="quote">X-BOGOSITY X-SPAM-STATUS</span>” for the
-“<span class="quote">X-Bogosity:</span>” and “<span class="quote">X-Spam-Status:</span>” header fields.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-idle"></a>3.87. imap_idle</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will attempt to use the IMAP IDLE extension
-to check for new mail in the current mailbox. Some servers
-(dovecot was the inspiration for this option) react badly
-to mutt's implementation. If your connection seems to freeze
-up periodically, try unsetting this.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-keepalive"></a>3.88. imap_keepalive</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 900</p></div><p>
-This variable specifies the maximum amount of time in seconds that mutt
-will wait before polling open IMAP connections, to prevent the server
-from closing them before mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-list-subscribed"></a>3.89. imap_list_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <code class="literal"><toggle-subscribed></code> function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-login"></a>3.90. imap_login</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Your login name on the IMAP server.
-</p><p>
-This variable defaults to the value of <a class="link" href="#imap-user" title="3.96. imap_user">$imap_user</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pass"></a>3.91. imap_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your IMAP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you invoke the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function
-or try to open an IMAP folder.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-passive"></a>3.92. imap_passive</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not open new IMAP connections to check for new
-mail. Mutt 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 invocation, or if opening the connection
-is slow.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-peek"></a>3.93. imap_peek</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pipeline-depth"></a>3.94. imap_pipeline_depth</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 15</p></div><p>
-Controls the number of IMAP commands that may be queued up before they
-are sent to the server. A deeper pipeline reduces the amount of time
-mutt must wait for the server, and can make IMAP servers feel much
-more responsive. But not all servers correctly handle pipelined commands,
-so if you have problems you might want to try setting this variable to 0.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> Changes to this variable have no effect on open connections.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-servernoise"></a>3.95. imap_servernoise</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-user"></a>3.96. imap_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-The name of the user whose mail you intend to access on the IMAP
-server.
-</p><p>
-This variable defaults to your user name on the local machine.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="implicit-autoview"></a>3.97. implicit_autoview</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If set to “<span class="quote">yes</span>”, mutt will look for a mailcap entry with the
-“<span class="quote"><code class="literal">copiousoutput</code></span>” flag set for <span class="emphasis"><em>every</em></span> MIME attachment it doesn't have
-an internal viewer defined for. If such an entry is found, mutt will
-use the viewer defined in that entry to convert the body part to text
-form.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include"></a>3.98. include</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not a copy of the message(s) you are replying to
-is included in your reply.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include-onlyfirst"></a>3.99. include_onlyfirst</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether or not Mutt includes only the first attachment
-of the message you are replying.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="indent-string"></a>3.100. indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">> </code></span>”</p></div><p>
-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.
-</p><p>
-This option is a format string, please see the description of
-<a class="link" href="#index-format" title="3.101. index_format">$index_format</a> for supported <code class="literal">printf(3)</code>-style sequences.
-</p><p>
-Because for <code class="literal">format=lowed</code> style messages the quoting mechanism
-is strictly defined, this setting is ignored if <a class="link" href="#text-flowed" title="3.285. text_flowed">$text_flowed</a> is
-<span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-format"></a>3.101. index_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s</code></span>”</p></div><p>
-This variable allows you to customize the message index display to
-your personal taste.
-</p><p>
-“<span class="quote">Format strings</span>” are similar to the strings used in the C
-function <code class="literal">printf(3)</code> to format output (see the man page for more details).
-The following sequences are defined in Mutt:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>address of the author
-</p></dd><dt><span class="term">%A </span></dt><dd><p>reply-to address (if present; otherwise: address of author)
-</p></dd><dt><span class="term">%b </span></dt><dd><p>filename of the original message folder (think mailbox)
-</p></dd><dt><span class="term">%B </span></dt><dd><p>the list to which the letter was sent, or else the folder name (%b).
-</p></dd><dt><span class="term">%c </span></dt><dd><p>number of characters (bytes) in the message
-</p></dd><dt><span class="term">%C </span></dt><dd><p>current message number
-</p></dd><dt><span class="term">%d </span></dt><dd><p>date and time of the message in the format specified by
-<a class="link" href="#date-format" title="3.40. date_format">$date_format</a> converted to sender's time zone
-</p></dd><dt><span class="term">%D </span></dt><dd><p>date and time of the message in the format specified by
-<a class="link" href="#date-format" title="3.40. date_format">$date_format</a> converted to the local time zone
-</p></dd><dt><span class="term">%e </span></dt><dd><p>current message number in thread
-</p></dd><dt><span class="term">%E </span></dt><dd><p>number of messages in current thread
-</p></dd><dt><span class="term">%f </span></dt><dd><p>sender (address + real name), either From: or Return-Path:
-</p></dd><dt><span class="term">%F </span></dt><dd><p>author name, or recipient name if the message is from you
-</p></dd><dt><span class="term">%H </span></dt><dd><p>spam attribute(s) of this message
-</p></dd><dt><span class="term">%i </span></dt><dd><p>message-id of the current message
-</p></dd><dt><span class="term">%l </span></dt><dd><p>number of lines in the message (does not work with maildir,
-mh, and possibly IMAP folders)
-</p></dd><dt><span class="term">%L </span></dt><dd><p>If an address in the “<span class="quote">To:</span>” or “<span class="quote">Cc:</span>” header field matches an address
-defined by the users “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” command, this displays
-"To <list-name>", otherwise the same as %F.
-</p></dd><dt><span class="term">%m </span></dt><dd><p>total number of message in the mailbox
-</p></dd><dt><span class="term">%M </span></dt><dd><p>number of hidden messages if the thread is collapsed.
-</p></dd><dt><span class="term">%N </span></dt><dd><p>message score
-</p></dd><dt><span class="term">%n </span></dt><dd><p>author's real name (or address if missing)
-</p></dd><dt><span class="term">%O </span></dt><dd><p>original save folder where mutt would formerly have
-stashed the message: list name or recipient name
-if not sent to a list
-</p></dd><dt><span class="term">%P </span></dt><dd><p>progress indicator for the builtin pager (how much of the file has been displayed)
-</p></dd><dt><span class="term">%s </span></dt><dd><p>subject of the message
-</p></dd><dt><span class="term">%S </span></dt><dd><p>status of the message (“<span class="quote">N</span>”/“<span class="quote">D</span>”/“<span class="quote">d</span>”/“<span class="quote">!</span>”/“<span class="quote">r</span>”/*)
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">To:</span>” field (recipients)
-</p></dd><dt><span class="term">%T </span></dt><dd><p>the appropriate character from the <a class="link" href="#to-chars" title="3.292. to_chars">$to_chars</a> string
-</p></dd><dt><span class="term">%u </span></dt><dd><p>user (login) name of the author
-</p></dd><dt><span class="term">%v </span></dt><dd><p>first name of the author, or the recipient if the message is from you
-</p></dd><dt><span class="term">%X </span></dt><dd><p>number of attachments
-(please see the “<span class="quote"><a class="link" href="#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
-</p></dd><dt><span class="term">%y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present
-</p></dd><dt><span class="term">%Y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present, and <span class="emphasis"><em>(1)</em></span> not at part of a thread tree,
-<span class="emphasis"><em>(2)</em></span> at the top of a thread, or <span class="emphasis"><em>(3)</em></span> “<span class="quote">X-Label:</span>” is different from
-preceding message's “<span class="quote">X-Label:</span>”.
-</p></dd><dt><span class="term">%Z </span></dt><dd><p>message status flags
-</p></dd><dt><span class="term">%{fmt} </span></dt><dd><p>the date and time of the message is converted to sender's
-time zone, and “<span class="quote">fmt</span>” is expanded by the library function
-<code class="literal">strftime(3)</code>; a leading bang disables locales
-</p></dd><dt><span class="term">%[fmt] </span></dt><dd><p>the date and time of the message is converted to the local
-time zone, and “<span class="quote">fmt</span>” is expanded by the library function
-<code class="literal">strftime(3)</code>; a leading bang disables locales
-</p></dd><dt><span class="term">%(fmt) </span></dt><dd><p>the local date and time when the message was received.
-“<span class="quote">fmt</span>” is expanded by the library function <code class="literal">strftime(3)</code>;
-a leading bang disables locales
-</p></dd><dt><span class="term">%<fmt> </span></dt><dd><p>the current local time. “<span class="quote">fmt</span>” is expanded by the library
-function <code class="literal">strftime(3)</code>; a leading bang disables locales.
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-“<span class="quote">Soft-fill</span>” deserves some explanation: Normal right-justification
-will print everything to the left of the “<span class="quote">%></span>”, displaying padding and
-whatever lies to the right only if there's room. By contrast,
-soft-fill gives priority to the right-hand side, guaranteeing space
-to display it and showing padding only if there's still room. If
-necessary, soft-fill will eat text leftwards to make room for
-rightward text.
-</p><p>
-Note that these expandos are supported in
-“<span class="quote"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” and “<span class="quote"><a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></span>”, too.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ispell"></a>3.102. ispell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">ispell</code></span>”</p></div><p>
-How to invoke ispell (GNU's spell-checking software).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="keep-flagged"></a>3.103. keep_flagged</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, read messages marked as flagged will not be moved
-from your spool mailbox to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
-a “<span class="quote"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="locale"></a>3.104. locale</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">C</code></span>”</p></div><p>
-The locale used by <code class="literal">strftime(3)</code> to format dates. Legal values are
-the strings your system accepts for the locale environment variable <code class="literal">$LC_TIME</code>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mail-check"></a>3.105. mail_check</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 5</p></div><p>
-This variable configures how often (in seconds) mutt should look for
-new mail. Also see the <a class="link" href="#timeout" title="3.290. timeout">$timeout</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-path"></a>3.106. mailcap_path</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable specifies which files to consult when attempting to
-display MIME bodies not directly supported by Mutt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-sanitize"></a>3.107. mailcap_sanitize</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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.
-</p><p>
-<span class="bold"><strong>DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
-DOING!</strong></span>
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-mtime"></a>3.108. maildir_mtime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If set, the sort-by-date option in the browser will sort maildirs
-smartly, not using the mtime of the maildir itself but that of the
-newest message in the new subdirectory, making the sorting by
-reverse date much more useful. People with maildirs over NFS may
-wish to leave this option unset.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache"></a>3.109. header_cache</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is <span class="emphasis"><em>unset</em></span> so no header
-caching will be used.
-</p><p>
-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see “<span class="quote"><a class="link" href="#caching" title="7. Local caching">caching</a></span>” for details.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-header-cache-verify"></a>3.110. maildir_header_cache_verify</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Check for Maildir unaware programs other than mutt having modified maildir
-files when the header cache is in use. This incurs one <code class="literal">stat(2)</code> per
-message every time the folder is opened (which can be very slow for NFS
-folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache-pagesize"></a>3.111. header_cache_pagesize</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">16384</code></span>”</p></div><p>
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-trash"></a>3.112. maildir_trash</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, messages marked as deleted will be saved with the maildir
-trashed flag instead of unlinked. <span class="bold"><strong>Note:</strong></span> this only applies
-to maildir-style mailboxes. Setting it will have no effect on other
-mailbox types.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mark-old"></a>3.113. mark_old</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether or not mutt marks <span class="emphasis"><em>new</em></span> <span class="bold"><strong>unread</strong></span>
-messages as <span class="emphasis"><em>old</em></span> if you exit a mailbox without reading them.
-With this option <span class="emphasis"><em>set</em></span>, the next time you start mutt, the messages
-will show up with an “<span class="quote">O</span>” next to them in the index menu,
-indicating that they are old.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="markers"></a>3.114. markers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the display of wrapped lines in the internal pager. If set, a
-“<span class="quote">+</span>” marker is displayed at the beginning of wrapped lines.
-</p><p>
-Also see the <a class="link" href="#smart-wrap" title="3.267. smart_wrap">$smart_wrap</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mask"></a>3.115. mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">!^\.[^.]</code></span>”</p></div><p>
-A regular expression used in the file browser, optionally preceded by
-the <span class="emphasis"><em>not</em></span> operator “<span class="quote">!</span>”. Only files whose names match this mask
-will be shown. The match is always case-sensitive.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox"></a>3.116. mbox</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/mbox</code></span>”</p></div><p>
-This specifies the folder into which read mail in your <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a>
-folder will be appended.
-</p><p>
-Also see the <a class="link" href="#move" title="3.132. move">$move</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox-type"></a>3.117. mbox_type</h3></div></div></div><div class="literallayout"><p>Type: folder magic<br />
-Default: mbox</p></div><p>
-The default mailbox type used when creating new folders. May be any of
-“<span class="quote">mbox</span>”, “<span class="quote">MMDF</span>”, “<span class="quote">MH</span>” and “<span class="quote">Maildir</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="metoo"></a>3.118. metoo</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>unset</em></span>, Mutt will remove your address (see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”
-command) from the list of recipients when replying to a message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-context"></a>3.119. menu_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to <a class="link" href="#pager-context" title="3.139. pager_context">$pager_context</a>.)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-move-off"></a>3.120. menu_move_off</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, the bottom entry of menus will never scroll up past
-the bottom of the screen, unless there are less entries than lines.
-When <span class="emphasis"><em>set</em></span>, the bottom entry may move off the bottom.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-scroll"></a>3.121. menu_scroll</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, menus will be scrolled up or down one line when you
-attempt to move across a screen boundary. If <span class="emphasis"><em>unset</em></span>, the screen
-is cleared and the next or previous page of the menu is displayed
-(useful for slow links to avoid many redraws).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="meta-key"></a>3.122. meta_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, forces Mutt 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 <code class="literal">0xf8</code>, then this is treated as if the user had
-pressed Esc then “<span class="quote">x</span>”. This is because the result of removing the
-high bit from <code class="literal">0xf8</code> is <code class="literal">0x78</code>, which is the ASCII character
-“<span class="quote">x</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-purge"></a>3.123. mh_purge</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mutt will mimic mh's behaviour and rename deleted messages
-to <span class="emphasis"><em>,<old file name></em></span> in mh folders instead of really deleting
-them. This leaves the message on disk but makes programs reading the folder
-ignore it. If the variable is <span class="emphasis"><em>set</em></span>, the message files will simply be
-deleted.
-</p><p>
-This option is similar to <a class="link" href="#maildir-trash" title="3.112. maildir_trash">$maildir_trash</a> for Maildir folders.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-flagged"></a>3.124. mh_seq_flagged</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">flagged</code></span>”</p></div><p>
-The name of the MH sequence used for flagged messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-replied"></a>3.125. mh_seq_replied</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">replied</code></span>”</p></div><p>
-The name of the MH sequence used to tag replied messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-unseen"></a>3.126. mh_seq_unseen</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">unseen</code></span>”</p></div><p>
-The name of the MH sequence used for unseen messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward"></a>3.127. mime_forward</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the message you are forwarding will be attached as a
-separate <code class="literal">message/rfc822</code> 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 “<span class="quote">ask-no</span>” or “<span class="quote">ask-yes</span>”.
-</p><p>
-Also see <a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-decode"></a>3.128. mime_forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
-forwarding a message while <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span>. Otherwise
-<a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> is used instead.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-rest"></a>3.129. mime_forward_rest</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-When forwarding multiple attachments of a MIME message from the attachment
-menu, attachments which cannot be decoded in a reasonable manner will
-be attached to the newly composed message if this option is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix-entry-format"></a>3.130. mix_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %c %-16s %a</code></span>”</p></div><p>
-This variable describes the format of a remailer line on the mixmaster
-chain selection screen. The following <code class="literal">printf(3)</code>-like sequences are
-supported:
-
-</p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>The running number on the menu.
-</p></dd><dt><span class="term">%c </span></dt><dd><p>Remailer capabilities.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>The remailer's short name.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The remailer's e-mail address.
-</p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mixmaster"></a>3.131. mixmaster</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">mixmaster</code></span>”</p></div><p>
-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.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
-“<span class="quote">mixmaster-filter</span>” in /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="move"></a>3.132. move</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: no</p></div><p>
-Controls whether or not Mutt will move read messages
-from your spool mailbox to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
-a “<span class="quote"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cachedir"></a>3.133. message_cachedir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-</p><p>
-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-</p><p>
-Also see the <a class="link" href="#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cache-clean"></a>3.134. message_cache_clean</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-format"></a>3.135. message_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%s</code></span>”</p></div><p>
-This is the string displayed in the “<span class="quote">attachment</span>” menu for
-attachments of type <code class="literal">message/rfc822</code>. For a full listing of defined
-<code class="literal">printf(3)</code>-like sequences see the section on <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="narrow-tree"></a>3.136. narrow_tree</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable, when <span class="emphasis"><em>set</em></span>, makes the thread tree narrower, allowing
-deeper threads to fit on the screen.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="net-inc"></a>3.137. net_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-Operations that expect to transfer a large amount of data over the
-network will update their progress every <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> kilobytes.
-If set to 0, no progress messages will be displayed.
-</p><p>
-See also <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a> and <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager"></a>3.138. pager</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">builtin</code></span>”</p></div><p>
-This variable specifies which pager you would like to use to view
-messages. The value “<span class="quote">builtin</span>” means to use the builtin pager, otherwise this
-variable should specify the pathname of the external pager you would
-like to use.
-</p><p>
-Using an external pager may have some disadvantages: Additional
-keystrokes are necessary because you can't call mutt functions
-directly from the pager, and screen resizes cause lines longer than
-the screen width to be badly formatted in the help menu.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-context"></a>3.139. pager_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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 will display the line after the last one on the screen
-at the top of the next page (0 lines of context).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-format"></a>3.140. pager_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-%Z- %C/%m: %-20.20n %s%* -- (%P)</code></span>”</p></div><p>
-This variable controls the format of the one-line message “<span class="quote">status</span>”
-displayed before each message in either the internal or an external
-pager. The valid sequences are listed in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>
-section.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-index-lines"></a>3.141. pager_index_lines</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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 setting 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 <a class="link" href="#pager-index-lines" title="3.141. pager_index_lines">$pager_index_lines</a>, then the index will only use as
-many lines as it needs.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-stop"></a>3.142. pager_stop</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the internal-pager will <span class="bold"><strong>not</strong></span> move to the next message
-when you are at the end of a message and invoke the <code class="literal"><next-page></code>
-function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosign"></a>3.143. crypt_autosign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt 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 <a class="link" href="#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autoencrypt"></a>3.144. crypt_autoencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages. This is probably only useful in
-connection to the “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>” command. It can be overridden
-by use of the pgp menu, when encryption is not required or
-signing is requested as well. If <a class="link" href="#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-ignore-subkeys"></a>3.145. pgp_ignore_subkeys</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities. <span class="emphasis"><em>Unset</em></span> this
-if you want to play interesting key selection games.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replyencrypt"></a>3.146. crypt_replyencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysign"></a>3.147. crypt_replysign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages which are
-signed.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> this does not work on messages that are encrypted
-<span class="emphasis"><em>and</em></span> signed!
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysignencrypted"></a>3.148. crypt_replysignencrypted</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages
-which are encrypted. This makes sense in combination with
-<a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>, because it allows you to sign all
-messages which are automatically encrypted. This works around
-the problem noted in <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a>, that mutt is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-timestamp"></a>3.149. crypt_timestamp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 <span class="emphasis"><em>unset</em></span> this setting.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-delim"></a>3.150. sidebar_delim</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">|</code></span>”</p></div><p>
-This specifies the delimiter between the sidebar (if visible) and
-other screens.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-visible"></a>3.151. sidebar_visible</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This specifies whether or not to show sidebar (left-side list of folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-width"></a>3.152. sidebar_width</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-The width of the sidebar.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-use-gpg-agent"></a>3.153. pgp_use_gpg_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will use a possibly-running <code class="literal">gpg-agent(1)</code> process.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-verify-sig"></a>3.154. crypt_verify_sig</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>“<span class="quote">yes</span>”</em></span>, always attempt to verify PGP or S/MIME signatures.
-If <span class="emphasis"><em>“<span class="quote">ask-*</span>”</em></span>, ask whether or not to verify the signature.
-If \Fi“<span class="quote">no</span>”, never attempt to verify cryptographic signatures.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-is-default"></a>3.155. smime_is_default</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-The default behaviour of mutt is to use PGP on all auto-sign/encryption
-operations. To override and to use OpenSSL instead this must be <span class="emphasis"><em>set</em></span>.
-However, this has no effect while replying, since mutt will automatically
-select the same application that was used to sign/encrypt the original
-message. (Note that this variable can be overridden by unsetting <a class="link" href="#crypt-autosmime" title="3.39. crypt_autosmime">$crypt_autosmime</a>.)
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ask-cert-label"></a>3.156. smime_ask_cert_label</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-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
-<span class="emphasis"><em>set</em></span> by default.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-use-default-key"></a>3.157. smime_decrypt_use_default_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span> (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate-key-pairs, mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-entry-format"></a>3.158. pgp_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %t%f %4l/0x%k %-4a %2c %u</code></span>”</p></div><p>
-This variable allows you to customize the PGP key selection menu to
-your personal taste. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but
-has its own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>number
-</p></dd><dt><span class="term">%k </span></dt><dd><p>key id
-</p></dd><dt><span class="term">%u </span></dt><dd><p>user id
-</p></dd><dt><span class="term">%a </span></dt><dd><p>algorithm
-</p></dd><dt><span class="term">%l </span></dt><dd><p>key length
-</p></dd><dt><span class="term">%f </span></dt><dd><p>flags
-</p></dd><dt><span class="term">%c </span></dt><dd><p>capabilities
-</p></dd><dt><span class="term">%t </span></dt><dd><p>trust/validity of the key-uid association
-</p></dd><dt><span class="term">%[<s>] </span></dt><dd><p>date of the key where <s> is an <code class="literal">strftime(3)</code> expression
-</p></dd></dl></div><p>
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-good-sign"></a>3.159. pgp_good_sign</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: (empty)</p></div><p>
-If you assign a text to this variable, then a PGP signature is only
-considered verified if the output from <a class="link" href="#pgp-verify-command" title="3.176. pgp_verify_command">$pgp_verify_command</a> contains
-the text. Use this variable if the exit code from the command is 0
-even for bad signatures.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-check-exit"></a>3.160. pgp_check_exit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-long-ids"></a>3.161. pgp_long_ids</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, use 64 bit PGP key IDs, if <span class="emphasis"><em>unset</em></span> use the normal 32 bit key IDs.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-retainable-sigs"></a>3.162. pgp_retainable_sigs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, signed and encrypted messages will consist of nested
-<code class="literal">multipart/signed</code> and <code class="literal">multipart/encrypted</code> body parts.
-</p><p>
-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (<code class="literal">multipart/encrypted</code>) can be easily
-removed, while the inner <code class="literal">multipart/signed</code> part is retained.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-autoinline"></a>3.163. pgp_autoinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option controls whether Mutt 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.
-</p><p>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</p><p>
-Also see the <a class="link" href="#pgp-mime-auto" title="3.170. pgp_mime_auto">$pgp_mime_auto</a> variable.
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-replyinline"></a>3.164. pgp_replyinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt 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
-internals for previously checked/flagged messages.
-</p><p>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</p><p>
-Also see the <a class="link" href="#pgp-mime-auto" title="3.170. pgp_mime_auto">$pgp_mime_auto</a> variable.
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-show-unusable"></a>3.165. pgp_show_unusable</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 “<span class="quote">disabled</span>” by the user.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-as"></a>3.166. pgp_sign_as</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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. <code class="literal">0x00112233</code>).
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-strict-enc"></a>3.167. pgp_strict_enc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-timeout"></a>3.168. pgp_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 300</p></div><p>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sort-keys"></a>3.169. pgp_sort_keys</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: address</p></div><p>
-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-
-</p><div class="variablelist"><dl><dt><span class="term">address </span></dt><dd><p>sort alphabetically by user id
-</p></dd><dt><span class="term">keyid </span></dt><dd><p>sort alphabetically by key id
-</p></dd><dt><span class="term">date </span></dt><dd><p>sort by key creation date
-</p></dd><dt><span class="term">trust </span></dt><dd><p>sort by the trust of the key
-</p></dd></dl></div><p>
-If you prefer reverse order of the above values, prefix it with
-“<span class="quote">reverse-</span>”.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-auto"></a>3.170. pgp_mime_auto</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-auto-decode"></a>3.171. pgp_auto_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 <code class="literal"><a class="link" href="#check-traditional-pgp"><check-traditional-pgp></a></code> function, mutt will automatically
-check the message for traditional pgp.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-filename"></a>3.172. pgp_mime_signature_filename</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">signature.asc</code></span>”</p></div><p>
-This option sets the filename used for signature parts in PGP/MIME
-signed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-description"></a>3.173. pgp_mime_signature_description</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">Digital signature</code></span>”</p></div><p>
-This option sets the Content-Description used for signature parts in
-PGP/MIME signed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decode-command"></a>3.174. pgp_decode_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format strings specifies a command which is used to decode
-application/pgp attachments.
-</p><p>
-The PGP command formats have their own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%p </span></dt><dd><p>Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-string otherwise. Note: This may be used with a %? construct.
-</p></dd><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
- of a <code class="literal">multipart/signed</code> attachment when verifying it.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The value of <a class="link" href="#pgp-sign-as" title="3.166. pgp_sign_as">$pgp_sign_as</a>.
-</p></dd><dt><span class="term">%r </span></dt><dd><p>One or more key IDs.
-</p></dd></dl></div><p>
-For examples on how to configure these formats for the various versions
-of PGP which are floating around, see the pgp and gpg sample configuration files in
-the <code class="literal">samples/</code> subdirectory which has been installed on your system
-alongside the documentation.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-getkeys-command"></a>3.175. pgp_getkeys_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a>, %r is the only
-<code class="literal">printf(3)</code>-like sequence used with this format.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-command"></a>3.176. pgp_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify PGP signatures.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decrypt-command"></a>3.177. pgp_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to decrypt a PGP encrypted message.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-clearsign-command"></a>3.178. pgp_clearsign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format is used to create an old-style “<span class="quote">clearsigned</span>” PGP
-message. Note that the use of this format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-command"></a>3.179. pgp_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to create the detached PGP signature for a
-<code class="literal">multipart/signed</code> PGP/MIME body part.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-sign-command"></a>3.180. pgp_encrypt_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to both sign and encrypt a body part.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-only-command"></a>3.181. pgp_encrypt_only_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to encrypt a body part without signing it.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-import-command"></a>3.182. pgp_import_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to import a key from a message into
-the user's public key ring.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-export-command"></a>3.183. pgp_export_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to export a public key from the user's
-key ring.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-key-command"></a>3.184. pgp_verify_key_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify key information from the key selection
-menu.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-secring-command"></a>3.185. pgp_list_secring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to list the secret key ring's contents. The
-output format must be analogous to the one used by:
-
-</p><pre class="screen">
-gpg --list-keys --with-colons.
-
-</pre><p>
-This format is also generated by the <code class="literal">pgpring</code> utility which comes
-with mutt.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-pubring-command"></a>3.186. pgp_list_pubring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to list the public key ring's contents. The
-output format must be analogous to the one used by
-
-</p><pre class="screen">
-gpg --list-keys --with-colons.
-
-</pre><p>
-This format is also generated by the <code class="literal">pgpring</code> utility which comes
-with mutt.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decrypt"></a>3.187. forward_decrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the handling of encrypted messages when forwarding a message.
-When <span class="emphasis"><em>set</em></span>, the outer layer of encryption is stripped off. This
-variable is only used if <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span> and
-<a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is <span class="emphasis"><em>unset</em></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-timeout"></a>3.188. smime_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 300</p></div><p>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-with"></a>3.189. smime_encrypt_with</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This sets the algorithm that should be used for encryption.
-Valid choices are “<span class="quote">des</span>”, “<span class="quote">des3</span>”, “<span class="quote">rc2-40</span>”, “<span class="quote">rc2-64</span>”, “<span class="quote">rc2-128</span>”.
-If <span class="emphasis"><em>unset</em></span>, “<span class="quote">3des</span>” (TripleDES) is used.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-keys"></a>3.190. smime_keys</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and 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 option points to the location of the private keys.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ca-location"></a>3.191. smime_ca_location</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this defaults to the first existing file in
-the following list: ˜/.smime/ca-certificates.crt ˜/.smime/ca-bundle.crt
-/etc/ssl/certs/ca-certificates.crt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-certificates"></a>3.192. smime_certificates</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-the location of the certificates.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-command"></a>3.193. smime_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format string specifies a command which is used to decrypt
-<code class="literal">application/x-pkcs7-mime</code> attachments.
-</p><p>
-The OpenSSL command formats have their own set of <code class="literal">printf(3)</code>-like sequences
-similar to PGP's:
-
-</p><div class="variablelist"><dl><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
- of a <code class="literal">multipart/signed</code> attachment when verifying it.
-</p></dd><dt><span class="term">%k </span></dt><dd><p>The key-pair specified with <a class="link" href="#smime-default-key" title="3.204. smime_default_key">$smime_default_key</a>
-</p></dd><dt><span class="term">%c </span></dt><dd><p>One or more certificate IDs.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The algorithm used for encryption.
-</p></dd><dt><span class="term">%C </span></dt><dd><p>CA location: Depending on whether <a class="link" href="#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a>
- points to a directory or file, this expands to
- “<span class="quote">-CApath <a class="link" href="#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a></span>” or “<span class="quote">-CAfile <a class="link" href="#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a></span>”.
-</p></dd></dl></div><p>
-For examples on how to configure these formats, see the <code class="literal">smime.rc</code> in
-the <code class="literal">samples/</code> subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-command"></a>3.194. smime_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify S/MIME signatures of type <code class="literal">multipart/signed</code>.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-opaque-command"></a>3.195. smime_verify_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify S/MIME signatures of type
-<code class="literal">application/x-pkcs7-mime</code>.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-command"></a>3.196. smime_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to created S/MIME signatures of type
-<code class="literal">multipart/signed</code>, which can be read by all mail clients.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-opaque-command"></a>3.197. smime_sign_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to created S/MIME signatures of type
-<code class="literal">application/x-pkcs7-signature</code>, which can only be handled by mail
-clients supporting the S/MIME extension.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-command"></a>3.198. smime_encrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to create encrypted S/MIME messages.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-pk7out-command"></a>3.199. smime_pk7out_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-command"></a>3.200. smime_get_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to extract X509 certificates from a PKCS7 structure.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-signer-cert-command"></a>3.201. smime_get_signer_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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 “<span class="quote">From:</span>” field.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-import-cert-command"></a>3.202. smime_import_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to import a certificate via smime_keys.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-email-command"></a>3.203. smime_get_cert_email_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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).
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-default-key"></a>3.204. smime_default_key</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-client-cert"></a>3.205. ssl_client_cert</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-The file containing a client certificate and its associated private
-key.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-force-tls"></a>3.206. ssl_force_tls</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If this variable is <span class="emphasis"><em>set</em></span>, Mutt 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 <a class="link" href="#ssl-starttls" title="3.207. ssl_starttls">$ssl_starttls</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-starttls"></a>3.207. ssl_starttls</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span> (the default), mutt will attempt to use <code class="literal">STARTTLS</code> on servers
-advertising the capability. When <span class="emphasis"><em>unset</em></span>, mutt will not attempt to
-use <code class="literal">STARTTLS</code> regardless of the server's capabilities.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="certificate-file"></a>3.208. certificate_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.mutt_certificates</code></span>”</p></div><p>
-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.
-</p><p>
-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set certificate_file=~/.mutt/certificates
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-sslv3"></a>3.209. ssl_use_sslv3</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-tlsv1"></a>3.210. ssl_use_tlsv1</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-min-dh-prime-bits"></a>3.211. ssl_min_dh_prime_bits</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-ca-certificates-file"></a>3.212. ssl_ca_certificates_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this variable defaults to the example
-mentioned. This file is managed by the “<span class="quote">ca-certificates</span>” package.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-split"></a>3.213. pipe_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><pipe-message></code> function following
-<code class="literal"><tag-prefix></code>. If this variable is <span class="emphasis"><em>unset</em></span>, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated. When <span class="emphasis"><em>set</em></span>, Mutt will pipe the messages one by one.
-In both cases the messages are piped in the current sorted order,
-and the <a class="link" href="#pipe-sep" title="3.215. pipe_sep">$pipe_sep</a> separator is added after each message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-decode"></a>3.214. pipe_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><pipe-message></code> command. When <span class="emphasis"><em>unset</em></span>,
-Mutt will pipe the messages without any preprocessing. When <span class="emphasis"><em>set</em></span>, Mutt
-will weed headers and will attempt to decode the messages
-first.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-sep"></a>3.215. pipe_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
-The separator to add between messages when piping a list of tagged
-messages to an external Unix command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-authenticators"></a>3.216. pop_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an POP server, in the order mutt should
-try them. Authentication methods are either “<span class="quote">user</span>”, “<span class="quote">apop</span>” or any
-SASL mechanism, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
-This option is case-insensitive. If this option is <span class="emphasis"><em>unset</em></span>
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set pop_authenticators="digest-md5:apop:user"
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-auth-try-all"></a>3.217. pop_auth_try_all</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will try all available authentication methods.
-When <span class="emphasis"><em>unset</em></span>, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-checkinterval"></a>3.218. pop_checkinterval</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 60</p></div><p>
-This variable configures how often (in seconds) mutt should look for
-new mail in the currently selected mailbox if it is a POP mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-delete"></a>3.219. pop_delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will delete successfully downloaded messages from the POP
-server when using the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function. When <span class="emphasis"><em>unset</em></span>, Mutt will
-download messages but also leave them on the POP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-host"></a>3.220. pop_host</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-The name of your POP server for the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function. You
-can also specify an alternative port, username and password, ie:
-
-</p><pre class="screen">
-[pop[s]://][username[:password]@]popserver[:port]
-
-</pre><p>
-where “<span class="quote">[...]</span>” denotes an optional part.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-last"></a>3.221. pop_last</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If this variable is <span class="emphasis"><em>set</em></span>, mutt will try to use the “<span class="quote"><code class="literal">LAST</code></span>” POP command
-for retrieving only unread messages from the POP server when using
-the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-reconnect"></a>3.222. pop_reconnect</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-user"></a>3.223. pop_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Your login name on the POP server.
-</p><p>
-This variable defaults to your user name on the local machine.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-pass"></a>3.224. pop_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your POP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you open a POP mailbox.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc
-even if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="post-indent-string"></a>3.225. post_indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Similar to the <a class="link" href="#attribution" title="3.16. attribution">$attribution</a> variable, Mutt will append this
-string after the inclusion of a message which is being replied to.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone"></a>3.226. postpone</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not messages are saved in the <a class="link" href="#postponed" title="3.227. postponed">$postponed</a>
-mailbox when you elect not to send immediately.
-</p><p>
-Also see the <a class="link" href="#recall" title="3.241. recall">$recall</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postponed"></a>3.227. postponed</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/postponed</code></span>”</p></div><p>
-Mutt allows you to indefinitely “<span class="quote"><a class="link" href="#postpone" title="3.226. postpone">postpone</a> sending a message</span>” which
-you are editing. When you choose to postpone a message, Mutt saves it
-in the mailbox specified by this variable.
-</p><p>
-Also see the <a class="link" href="#postpone" title="3.226. postpone">$postpone</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="preconnect"></a>3.228. preconnect</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-If <span class="emphasis"><em>set</em></span>, a shell command to be executed if mutt fails to establish
-a connection to the server. This is useful for setting up secure
-connections, e.g. with <code class="literal">ssh(1)</code>. If the command returns a nonzero
-status, mutt gives up opening the server. Example:
-
-</p><pre class="screen">
-set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
-sleep 20 < /dev/null > /dev/null"
-
-</pre><p>
-Mailbox “<span class="quote">foo</span>” on “<span class="quote">mailhost.net</span>” can now be reached
-as “<span class="quote">{localhost:1234}foo</span>”.
-</p><p>
-Note: For this example to work, you must be able to log in to the
-remote machine without having to enter a password.
-</p><p>
-When set, Mutt uses the tunnel for all remote connections.
-Please see “<span class="quote"><a class="link" href="#account-hook" title="6. Managing multiple accounts">account-hook</a></span>” in the manual for how to use different
-tunnel commands per connection.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print"></a>3.229. print</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-no</p></div><p>
-Controls whether or not Mutt really prints messages.
-This is set to “<span class="quote">ask-no</span>” by default, because some people
-accidentally hit “<span class="quote">p</span>” often.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-command"></a>3.230. print_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">lpr</code></span>”</p></div><p>
-This specifies the command pipe that should be used to print messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-decode"></a>3.231. print_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Used in connection with the <code class="literal"><print-message></code> command. If this
-option is <span class="emphasis"><em>set</em></span>, the message is decoded before it is passed to the
-external command specified by <a class="link" href="#print-command" title="3.230. print_command">$print_command</a>. If this option
-is <span class="emphasis"><em>unset</em></span>, 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-split"></a>3.232. print_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><print-message></code> command. If this option
-is <span class="emphasis"><em>set</em></span>, the command specified by <a class="link" href="#print-command" title="3.230. print_command">$print_command</a> is executed once for
-each message which is to be printed. If this option is <span class="emphasis"><em>unset</em></span>,
-the command specified by <a class="link" href="#print-command" title="3.230. print_command">$print_command</a> is executed only once, and
-all the messages are concatenated, with a form feed as the message
-separator.
-</p><p>
-Those who use the <code class="literal">enscript</code>(1) program's mail-printing mode will
-most likely want to <span class="emphasis"><em>set</em></span> this option.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="prompt-after"></a>3.233. prompt_after</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If you use an <span class="emphasis"><em>external</em></span> <a class="link" href="#pager" title="3.138. pager">$pager</a>, setting this variable will
-cause Mutt to prompt you for a command when the pager exits rather
-than returning to the index menu. If <span class="emphasis"><em>unset</em></span>, Mutt will return to the
-index menu when the external pager exits.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-command"></a>3.234. query_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This specifies the command that mutt will use to make external address
-queries. The string should contain a “<span class="quote">%s</span>”, which will be substituted
-with the query string the user types. See “<span class="quote"><a class="link" href="#query" title="5. External Address Queries">query</a></span>” for more
-information.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-format"></a>3.235. query_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4c %t %-25.25a %-25.25n %?e?(%e)?</code></span>”</p></div><p>
-This variable describes the format of the “<span class="quote">query</span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are understood:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>destination address
-</p></dd><dt><span class="term">%c </span></dt><dd><p>current entry number
-</p></dd><dt><span class="term">%e </span></dt><dd><p>extra information *
-</p></dd><dt><span class="term">%n </span></dt><dd><p>destination name
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if current entry is tagged, a space otherwise
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p><p>
-* = can be optionally printed if nonzero, see the <a class="link" href="#status-format" title="3.281. status_format">$status_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quit"></a>3.236. quit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether “<span class="quote">quit</span>” and “<span class="quote">exit</span>” actually quit
-from mutt. If this option is <span class="emphasis"><em>set</em></span>, they do quit, if it is <span class="emphasis"><em>unset</em></span>, they
-have no effect, and if it is set to <span class="emphasis"><em>ask-yes</em></span> or <span class="emphasis"><em>ask-no</em></span>, you are
-prompted for confirmation when you try to quit.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quote-regexp"></a>3.237. quote_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^([ \t]*[|>:}#])+</code></span>”</p></div><p>
-A regular expression used in the internal pager to determine quoted
-sections of text in the body of a message. Quoted text may be filtered
-out using the <code class="literal"><toggle-quoted></code> command, or colored according to the
-“<span class="quote">color quoted</span>” family of directives.
-</p><p>
-Higher levels of quoting may be colored differently (“<span class="quote">color quoted1</span>”,
-“<span class="quote">color quoted2</span>”, etc.). The quoting level is determined by removing
-the last character from the matched text and recursively reapplying
-the regular expression until it fails to produce a match.
-</p><p>
-Match detection may be overridden by the <a class="link" href="#smileys" title="3.268. smileys">$smileys</a> regular expression.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-inc"></a>3.238. read_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-If set to a value greater than 0, Mutt will display which message it
-is currently on when reading a mailbox or when performing search actions
-such as search and limit. The message is printed after
-this many messages have been read or searched (e.g., if set to 25, Mutt will
-print a message when it is at message 25, and then again when it gets
-to message 50). This variable is meant to indicate progress when
-reading or searching large mailboxes which may take some time.
-When set to 0, only a single message will appear before the reading
-the mailbox.
-</p><p>
-Also see the <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a>, <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="#time-inc" title="3.289. time_inc">$time_inc</a> variables and the
-“<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-only"></a>3.239. read_only</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, all folders are opened in read-only mode.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="realname"></a>3.240. realname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable specifies what “<span class="quote">real</span>” or “<span class="quote">personal</span>” name should be used
-when sending messages.
-</p><p>
-By default, this is the GECOS field from <code class="literal">/etc/passwd</code>. Note that this
-variable will <span class="emphasis"><em>not</em></span> be used when the user has set a real name
-in the <a class="link" href="#from" title="3.66. from">$from</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="recall"></a>3.241. recall</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not Mutt recalls postponed messages
-when composing a new message.
-</p><p>
-<span class="emphasis"><em>Setting</em></span> this variable to is not generally useful, and thus not
-recommended.
-</p><p>
-Also see <a class="link" href="#postponed" title="3.227. postponed">$postponed</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="record"></a>3.242. record</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/sent</code></span>”</p></div><p>
-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 “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command to create a “<span class="quote">Bcc:</span>” field with your email address in it.)
-</p><p>
-The value of <span class="emphasis"><em><a class="link" href="#record" title="3.242. record">$record</a></em></span> is overridden by the <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> and
-<a class="link" href="#save-name" title="3.254. save_name">$save_name</a> variables, and the “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-regexp"></a>3.243. reply_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^(re([\[0-9\]+])*|aw):[ \t]*</code></span>”</p></div><p>
-A regular expression used to recognize reply messages when threading
-and replying. The default value corresponds to the English "Re:" and
-the German "Aw:".
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-self"></a>3.244. reply_self</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>unset</em></span> and you are replying to a message sent by you, Mutt will
-assume that you want to reply to the recipients of that message rather
-than to yourself.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-to"></a>3.245. reply_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, when replying to a message, Mutt will use the address listed
-in the Reply-to: header as the recipient of the reply. If <span class="emphasis"><em>unset</em></span>,
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="resolve"></a>3.246. resolve</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the cursor will be automatically advanced to the next
-(possibly undeleted) message whenever a command that modifies the
-current message is executed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-alias"></a>3.247. reverse_alias</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls whether or not Mutt will display the “<span class="quote">personal</span>”
-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:
-
-</p><pre class="screen">
-alias juser abd30425@somewhere.net (Joe User)
-
-</pre><p>
-and then you receive mail which contains the following header:
-
-</p><pre class="screen">
-From: abd30425@somewhere.net
-
-</pre><p>
-It would be displayed in the index menu as “<span class="quote">Joe User</span>” instead of
-“<span class="quote">abd30425@somewhere.net.</span>” This is useful when the person's e-mail
-address is not human friendly.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-name"></a>3.248. reverse_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <span class="emphasis"><em>set</em></span>, the default <span class="emphasis"><em>From:</em></span> line of
-the reply messages is built using the address where you received the
-messages you are replying to <span class="bold"><strong>if</strong></span> that address matches your
-“<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”. If the variable is <span class="emphasis"><em>unset</em></span>, or the address that would be
-used doesn't match your “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”, the <span class="emphasis"><em>From:</em></span> line will use
-your address on the current machine.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-realname"></a>3.249. reverse_realname</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable fine-tunes the behaviour of the <a class="link" href="#reverse-name" title="3.248. reverse_name">$reverse_name</a> feature.
-When it is <span class="emphasis"><em>set</em></span>, mutt will use the address from incoming messages as-is,
-possibly including eventual real names. When it is <span class="emphasis"><em>unset</em></span>, mutt will
-override any such real names with the setting of the <a class="link" href="#realname" title="3.240. realname">$realname</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="rfc2047-parameters"></a>3.250. rfc2047_parameters</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, Mutt will decode RFC2047-encoded MIME
-parameters. You want to set this variable when mutt suggests you
-to save attachments to files named like:
-
-</p><pre class="screen">
-=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-</pre><p>
-When this variable is <span class="emphasis"><em>set</em></span> interactively, the change won't be
-active until you change folders.
-</p><p>
-Note that this use of RFC2047's encoding is explicitly
-prohibited by the standard, but nevertheless encountered in the
-wild.
-</p><p>
-Also note that setting this parameter will <span class="emphasis"><em>not</em></span> have the effect
-that mutt <span class="emphasis"><em>generates</em></span> this kind of encoding. Instead, mutt will
-unconditionally use the encoding specified in RFC2231.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-address"></a>3.251. save_address</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If <a class="link" href="#save-name" title="3.254. save_name">$save_name</a> or <a class="link" href="#force-name" title="3.61. force_name">$force_name</a>
-is <span class="emphasis"><em>set</em></span> too, the selection of the Fcc folder will be changed as well.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-empty"></a>3.252. save_empty</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mailboxes which contain no saved messages will be removed
-when closed (the exception is <a class="link" href="#spoolfile" title="3.279. spoolfile">$spoolfile</a> which is never removed).
-If <span class="emphasis"><em>set</em></span>, mailboxes are never removed.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> This only applies to mbox and MMDF folders, Mutt does not
-delete MH and Maildir directories.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-history"></a>3.253. save_history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-This variable controls the size of the history (per category) saved in the
-<a class="link" href="#history-file" title="3.78. history_file">$history_file</a> file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-name"></a>3.254. save_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls how copies of outgoing messages are saved.
-When <span class="emphasis"><em>set</em></span>, 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 <a class="link" href="#folder" title="3.58. folder">$folder</a> directory with the <span class="emphasis"><em>username</em></span> 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
-<a class="link" href="#record" title="3.242. record">$record</a> mailbox.
-</p><p>
-Also see the <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score"></a>3.255. score</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>unset</em></span>, scoring is turned off. This can
-be useful to selectively disable scoring for certain folders when the
-<a class="link" href="#score-threshold-delete" title="3.256. score_threshold_delete">$score_threshold_delete</a> variable and related are used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-delete"></a>3.256. score_threshold_delete</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: -1</p></div><p>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked for deletion by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message for deletion.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-flag"></a>3.257. score_threshold_flag</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 9999</p></div><p>
-Messages which have been assigned a score greater than or equal to this
-variable's value are automatically marked "flagged".
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-read"></a>3.258. score_threshold_read</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: -1</p></div><p>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked as read by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message read.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="send-charset"></a>3.259. send_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">us-ascii:iso-8859-1:utf-8</code></span>”</p></div><p>
-A colon-delimited list of character sets for outgoing messages. Mutt will use the
-first character set into which the text can be converted exactly.
-If your <a class="link" href="#charset" title="3.25. charset">$charset</a> is not “<span class="quote">iso-8859-1</span>” and recipients may not
-understand “<span class="quote">UTF-8</span>”, it is advisable to include in the list an
-appropriate widely used standard character set (such as
-“<span class="quote">iso-8859-2</span>”, “<span class="quote">koi8-r</span>” or “<span class="quote">iso-2022-jp</span>”) either instead of or after
-“<span class="quote">iso-8859-1</span>”.
-</p><p>
-In case the text cannot be converted into one of these exactly,
-mutt uses <a class="link" href="#charset" title="3.25. charset">$charset</a> as a fallback.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail"></a>3.260. sendmail</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">/usr/sbin/sendmail -oem -oi</code></span>”</p></div><p>
-Specifies the program and arguments used to deliver mail sent by Mutt.
-Mutt expects that the specified program interprets additional
-arguments as recipient addresses.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail-wait"></a>3.261. sendmail_wait</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-Specifies the number of seconds to wait for the <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> process
-to finish before giving up and putting delivery in the background.
-</p><p>
-Mutt interprets the value of this variable as follows:
-
-</p><div class="variablelist"><dl><dt><span class="term">>0 </span></dt><dd><p>number of seconds to wait for sendmail to finish before continuing
-</p></dd><dt><span class="term">0 </span></dt><dd><p>wait forever for sendmail to finish
-</p></dd><dt><span class="term"><0 </span></dt><dd><p>always put sendmail in the background without waiting
-</p></dd></dl></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="shell"></a>3.262. shell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Command to use when spawning a subshell. By default, the user's login
-shell from <code class="literal">/etc/passwd</code> is used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-dashes"></a>3.263. sig_dashes</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, a line containing “<span class="quote">-- </span>” (note the trailing space) will be inserted before your
-<a class="link" href="#signature" title="3.265. signature">$signature</a>. It is <span class="bold"><strong>strongly</strong></span> recommended that you not <span class="emphasis"><em>unset</em></span>
-this variable unless your signature contains just your name. The
-reason for this is because many software packages use “<span class="quote">-- \n</span>” to
-detect your signature. For example, Mutt has the ability to highlight
-the signature in a different color in the builtin pager.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-on-top"></a>3.264. sig_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, the signature will be included before any quoted or forwarded
-text. It is <span class="bold"><strong>strongly</strong></span> 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="signature"></a>3.265. signature</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.signature</code></span>”</p></div><p>
-Specifies the filename of your signature, which is appended to all
-outgoing messages. If the filename ends with a pipe (“<span class="quote">|</span>”), it is
-assumed that filename is a shell command and input should be read from
-its standard output.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-search"></a>3.266. simple_search</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜f %s | ˜s %s</code></span>”</p></div><p>
-Specifies how Mutt should expand a simple search into a real search
-pattern. A simple search is one that does not contain any of the “<span class="quote">˜</span>” pattern
-operators. See “<span class="quote"><a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>” for more information on search patterns.
-</p><p>
-For example, if you simply type “<span class="quote">joe</span>” at a search or limit prompt, Mutt
-will automatically expand it to the value specified by this variable by
-replacing “<span class="quote">%s</span>” with the supplied string.
-For the default value, “<span class="quote">joe</span>” would be expanded to: “<span class="quote">˜f joe | ˜s joe</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smart-wrap"></a>3.267. smart_wrap</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the display of lines longer than the screen width in the
-internal pager. If <span class="emphasis"><em>set</em></span>, long lines are wrapped at a word boundary. If
-<span class="emphasis"><em>unset</em></span>, lines are simply wrapped at the screen edge. Also see the
-<a class="link" href="#markers" title="3.114. markers">$markers</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smileys"></a>3.268. smileys</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">(>From )|(:[-^]?[][)(><}{|/DP])</code></span>”</p></div><p>
-The <span class="emphasis"><em>pager</em></span> uses this variable to catch some common false
-positives of <a class="link" href="#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a>, most notably smileys and not consider
-a line quoted text if it also matches <a class="link" href="#smileys" title="3.268. smileys">$smileys</a>. This mostly
-happens at the beginning of a line.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sleep-time"></a>3.269. sleep_time</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 1</p></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-authenticators"></a>3.270. smtp_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an SMTP server, in the order mutt should
-try them. Authentication methods are any SASL mechanism, eg
-“<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
-This option is case-insensitive. If it is “<span class="quote">unset</span>”
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set smtp_authenticators="digest-md5:cram-md5"
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-pass"></a>3.271. smtp_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your SMTP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you first send mail via SMTP.
-See <a class="link" href="#smtp-url" title="3.272. smtp_url">$smtp_url</a> to configure mutt to send mail via SMTP.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-url"></a>3.272. smtp_url</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Defines the SMTP smarthost where sent messages should relayed for
-delivery. This should take the form of an SMTP URL, eg:
-
-</p><pre class="screen">
-smtp[s]://[user[:pass]@]host[:port]/
-
-</pre><p>
-\.\.\. where “<span class="quote">[...]</span>” denotes an optional part.
-Setting this variable overrides the value of the <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a>
-variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort"></a>3.273. sort</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: date</p></div><p>
-Specifies how to sort messages in the “<span class="quote">index</span>” menu. Valid values
-are:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>date or date-sent
-</p></li><li><p>date-received
-</p></li><li><p>from
-</p></li><li><p>mailbox-order (unsorted)
-</p></li><li><p>score
-</p></li><li><p>size
-</p></li><li><p>spam
-</p></li><li><p>subject
-</p></li><li><p>threads
-</p></li><li><p>to
-</p></li></ul></div><p>
-You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
-order (example: “<span class="quote"><code class="literal">set sort=reverse-date-sent</code></span>”).
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
-“<span class="quote">threads</span>” in /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-alias"></a>3.274. sort_alias</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: alias</p></div><p>
-Specifies how the entries in the “<span class="quote">alias</span>” menu are sorted. The
-following are legal values:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>address (sort alphabetically by email address)
-</p></li><li><p>alias (sort alphabetically by alias name)
-</p></li><li><p>unsorted (leave in order specified in .muttrc)
-</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-aux"></a>3.275. sort_aux</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: date</p></div><p>
-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 <a class="link" href="#sort" title="3.273. sort">$sort</a> can, except
-“<span class="quote">threads</span>” (in that case, mutt will just use “<span class="quote">date-sent</span>”). You can also
-specify the “<span class="quote">last-</span>” prefix in addition to the “<span class="quote">reverse-</span>” prefix, but “<span class="quote">last-</span>”
-must come after “<span class="quote">reverse-</span>”. The “<span class="quote">last-</span>” prefix causes messages to be
-sorted against its siblings by which has the last descendant, using
-the rest of <a class="link" href="#sort-aux" title="3.275. sort_aux">$sort_aux</a> as an ordering. For instance,
-
-</p><pre class="screen">
-set sort_aux=last-date-received
-
-</pre><p>
-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 “<span class="quote"><code class="literal">set sort=reverse-threads</code></span>”.)
-</p><p>
-Note: For reversed <a class="link" href="#sort" title="3.273. sort">$sort</a>
-order <a class="link" href="#sort-aux" title="3.275. sort_aux">$sort_aux</a> is reversed again (which is not the right thing to do,
-but kept to not break any existing configuration setting).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-browser"></a>3.276. sort_browser</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: alpha</p></div><p>
-Specifies how to sort entries in the file browser. By default, the
-entries are sorted alphabetically. Valid values:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>alpha (alphabetically)
-</p></li><li><p>date
-</p></li><li><p>size
-</p></li><li><p>unsorted
-</p></li></ul></div><p>
-You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
-order (example: “<span class="quote"><code class="literal">set sort_browser=reverse-date</code></span>”).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-re"></a>3.277. sort_re</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable is only useful when sorting by threads with
-<a class="link" href="#strict-threads" title="3.283. strict_threads">$strict_threads</a> <span class="emphasis"><em>unset</em></span>. In that case, it changes the heuristic
-mutt uses to thread messages by subject. With <a class="link" href="#sort-re" title="3.277. sort_re">$sort_re</a> <span class="emphasis"><em>set</em></span>, mutt 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 <a class="link" href="#reply-regexp" title="3.243. reply_regexp">$reply_regexp</a>. With <a class="link" href="#sort-re" title="3.277. sort_re">$sort_re</a> <span class="emphasis"><em>unset</em></span>, mutt will attach
-the message whether or not this is the case, as long as the
-non-<a class="link" href="#reply-regexp" title="3.243. reply_regexp">$reply_regexp</a> parts of both messages are identical.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spam-separator"></a>3.278. spam_separator</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">,</code></span>”</p></div><p>
-This variable controls what happens when multiple spam headers
-are matched: if <span class="emphasis"><em>unset</em></span>, each successive header will overwrite any
-previous matches value for the spam label. If <span class="emphasis"><em>set</em></span>, each successive
-match will append to the previous, using this variable's value as a
-separator.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spoolfile"></a>3.279. spoolfile</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-If your spool mailbox is in a non-default place where Mutt cannot find
-it, you can specify its location with this variable. Mutt will
-automatically set this variable to the value of the environment
-variable <code class="literal">$MAIL</code> if it is not set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-chars"></a>3.280. status_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-*%A</code></span>”</p></div><p>
-Controls the characters used by the “<span class="quote">%r</span>” indicator in
-<a class="link" href="#status-format" title="3.281. status_format">$status_format</a>. 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 <code class="literal"><toggle-write></code> operation, bound by default to “<span class="quote">%</span>”). 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).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-format"></a>3.281. status_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-%r-Mutt: %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)---</code></span>”</p></div><p>
-Controls the format of the status line displayed in the “<span class="quote">index</span>”
-menu. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but has its own
-set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%b </span></dt><dd><p>number of mailboxes with new mail *
-</p></dd><dt><span class="term">%d </span></dt><dd><p>number of deleted messages *
-</p></dd><dt><span class="term">%f </span></dt><dd><p>the full pathname of the current mailbox
-</p></dd><dt><span class="term">%F </span></dt><dd><p>number of flagged messages *
-</p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
-</p></dd><dt><span class="term">%l </span></dt><dd><p>size (in bytes) of the current mailbox *
-</p></dd><dt><span class="term">%L </span></dt><dd><p>size (in bytes) of the messages shown
-(i.e., which match the current limit) *
-</p></dd><dt><span class="term">%m </span></dt><dd><p>the number of messages in the mailbox *
-</p></dd><dt><span class="term">%M </span></dt><dd><p>the number of messages shown (i.e., which match the current limit) *
-</p></dd><dt><span class="term">%n </span></dt><dd><p>number of new messages in the mailbox *
-</p></dd><dt><span class="term">%o </span></dt><dd><p>number of old unread messages *
-</p></dd><dt><span class="term">%p </span></dt><dd><p>number of postponed messages *
-</p></dd><dt><span class="term">%P </span></dt><dd><p>percentage of the way through the index
-</p></dd><dt><span class="term">%r </span></dt><dd><p>modified/read-only/won't-write/attach-message indicator,
-according to <a class="link" href="#status-chars" title="3.280. status_chars">$status_chars</a>
-</p></dd><dt><span class="term">%s </span></dt><dd><p>current sorting mode (<a class="link" href="#sort" title="3.273. sort">$sort</a>)
-</p></dd><dt><span class="term">%S </span></dt><dd><p>current aux sorting method (<a class="link" href="#sort-aux" title="3.275. sort_aux">$sort_aux</a>)
-</p></dd><dt><span class="term">%t </span></dt><dd><p>number of tagged messages *
-</p></dd><dt><span class="term">%u </span></dt><dd><p>number of unread messages *
-</p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
-</p></dd><dt><span class="term">%V </span></dt><dd><p>currently active limit pattern, if any *
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p><p>
-* = can be optionally printed if nonzero
-</p><p>
-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:
-</p><p>
-<code class="literal">%?<sequence_char>?<optional_string>?</code>
-</p><p>
-where <span class="emphasis"><em>sequence_char</em></span> is a character from the table above, and
-<span class="emphasis"><em>optional_string</em></span> is the string you would like printed if
-<span class="emphasis"><em>sequence_char</em></span> is nonzero. <span class="emphasis"><em>optional_string</em></span> <span class="bold"><strong>may</strong></span> contain
-other sequences as well as normal text, but you may <span class="bold"><strong>not</strong></span> nest
-optional strings.
-</p><p>
-Here is an example illustrating how to optionally print the number of
-new messages in a mailbox:
-</p><p>
-<code class="literal">%?n?%n new messages.?</code>
-</p><p>
-You can also switch between two strings using the following construct:
-</p><p>
-<code class="literal">%?<sequence_char>?<if_string>&<else_string>?</code>
-</p><p>
-If the value of <span class="emphasis"><em>sequence_char</em></span> is non-zero, <span class="emphasis"><em>if_string</em></span> will
-be expanded, otherwise <span class="emphasis"><em>else_string</em></span> will be expanded.
-</p><p>
-You can force the result of any <code class="literal">printf(3)</code>-like sequence to be lowercase
-by prefixing the sequence character with an underscore (“<span class="quote">_</span>”) sign.
-For example, if you want to display the local hostname in lowercase,
-you would use: “<span class="quote"><code class="literal">%_h</code></span>”.
-</p><p>
-If you prefix the sequence character with a colon (“<span class="quote">:</span>”) character, mutt
-will replace any dots in the expansion by underscores. This might be helpful
-with IMAP folders that don't like dots in folder names.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-on-top"></a>3.282. status_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable causes the “<span class="quote">status bar</span>” to be displayed on
-the first line of the screen rather than near the bottom. If <a class="link" href="#help" title="3.70. help">$help</a>
-is <span class="emphasis"><em>set</em></span>, too it'll be placed at the bottom.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="strict-threads"></a>3.283. strict_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, threading will only make use of the “<span class="quote">In-Reply-To</span>” and
-“<span class="quote">References:</span>” fields when you <a class="link" href="#sort" title="3.273. sort">$sort</a> by message threads. By
-default, messages with the same subject are grouped together in
-“<span class="quote">pseudo threads.</span>”. This may not always be desirable, such as in a
-personal mailbox where you might have several unrelated messages with
-the subjects like “<span class="quote">hi</span>” which will get grouped together. See also
-<a class="link" href="#sort-re" title="3.277. sort_re">$sort_re</a> for a less drastic way of controlling this
-behaviour.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="suspend"></a>3.284. suspend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mutt won't stop when the user presses the terminal's
-<span class="emphasis"><em>susp</em></span> key, usually “<span class="quote">^Z</span>”. This is useful if you run mutt
-inside an xterm using a command like “<span class="quote"><code class="literal">xterm -e mutt</code></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="text-flowed"></a>3.285. text_flowed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will generate “<span class="quote">format=flowed</span>” bodies with a content type
-of “<span class="quote"><code class="literal">text/plain; format=flowed</code></span>”.
-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.
-</p><p>
-Note that <a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a> is ignored when this option is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thread-received"></a>3.286. thread_received</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt uses the date received rather than the date sent
-to thread messages by subject.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thorough-search"></a>3.287. thorough_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Affects the <code class="literal">˜b</code> and <code class="literal">˜h</code> search operations described in
-section “<span class="quote"><a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>”. If <span class="emphasis"><em>set</em></span>, the headers and body/attachments of
-messages to be searched are decoded before searching. If <span class="emphasis"><em>unset</em></span>,
-messages are searched as they appear in the folder.
-</p><p>
-Users searching attachments or for non-ASCII characters should <span class="emphasis"><em>set</em></span>
-this value because decoding also includes MIME parsing/decoding and possible
-character set conversions. Otherwise mutt will attempt to match against the
-raw message received (for example quoted-printable encoded or with encoded
-headers) which may lead to incorrect search results.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tilde"></a>3.288. tilde</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the internal-pager will pad blank lines to the bottom of the
-screen with a tilde (“<span class="quote">˜</span>”).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="time-inc"></a>3.289. time_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-Along with <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a>, and <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a>, this
-variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than <a class="link" href="#time-inc" title="3.289. time_inc">$time_inc</a> milliseconds
-apart. This can improve throughput on systems with slow terminals,
-or when running mutt on a remote system.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="timeout"></a>3.290. timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 600</p></div><p>
-When Mutt is waiting for user input either idleing in menus or
-in an interactive prompt, Mutt would block until input is
-present. Depending on the context, this would prevent certain
-operations from working, like checking for new mail or keeping
-an IMAP connection alive.
-</p><p>
-This variable controls how many seconds Mutt will at most wait
-until it aborts waiting for input, performs these operations and
-continues to wait for input.
-</p><p>
-A value of zero or less will cause Mutt to never time out.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tmpdir"></a>3.291. tmpdir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable allows you to specify where Mutt will place its
-temporary files needed for displaying and composing messages. If
-this variable is not set, the environment variable <code class="literal">$TMPDIR</code> is
-used. If <code class="literal">$TMPDIR</code> is not set then “<span class="quote"><code class="literal">/tmp</code></span>” is used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="to-chars"></a>3.292. to_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal"> +TCFL</code></span>”</p></div><p>
-Controls the character used to indicate mail addressed to you. The
-first character is the one used when the mail is <span class="emphasis"><em>not</em></span> addressed to your
-address. The second is used when you are the only
-recipient of the message. The third is when your address
-appears in the “<span class="quote">To:</span>” header field, but you are not the only recipient of
-the message. The fourth character is used when your
-address is specified in the “<span class="quote">Cc:</span>” header field, but you are not the only
-recipient. The fifth character is used to indicate mail that was sent
-by <span class="emphasis"><em>you</em></span>. The sixth character is used to indicate when a mail
-was sent to a mailing-list you subscribe to.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="trash"></a>3.293. trash</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-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.
-</p><p>
-NOTE: When you delete a message in the trash folder, it is really
-deleted, so that you have a way to clean the trash.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tunnel"></a>3.294. tunnel</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Setting this variable will cause mutt 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/SMTP server. Example:
-
-</p><pre class="screen">
-set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-
-</pre><p>
-Note: For this example to work you must be able to log in to the remote
-machine without having to enter a password.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-8bitmime"></a>3.295. use_8bitmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-<span class="bold"><strong>Warning:</strong></span> do not set this variable unless you are using a version
-of sendmail which supports the <code class="literal">-B8BITMIME</code> flag (such as sendmail
-8.8.x) or you may not be able to send mail.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will invoke <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> with the <code class="literal">-B8BITMIME</code>
-flag when sending 8-bit messages to enable ESMTP negotiation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-domain"></a>3.296. use_domain</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will qualify all local addresses (ones without the
-“<span class="quote">@host</span>” portion) with the value of <a class="link" href="#hostname" title="3.80. hostname">$hostname</a>. If <span class="emphasis"><em>unset</em></span>, no
-addresses will be qualified.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-envelope-from"></a>3.297. use_envelope_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will set the <span class="emphasis"><em>envelope</em></span> sender of the message.
-If <a class="link" href="#envelope-from-address" title="3.53. envelope_from_address">$envelope_from_address</a> is <span class="emphasis"><em>set</em></span>, it will be used as the sender
-address. If <span class="emphasis"><em>unset</em></span>, mutt will attempt to derive the sender from the
-“<span class="quote">From:</span>” header.
-</p><p>
-Note that this information is passed to sendmail command using the
-<code class="literal">-f</code> command line switch. Therefore setting this option is not useful
-if the <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> variable already contains <code class="literal">-f</code> or if the
-executable pointed to by <a class="link" href="#sendmail" title="3.260. sendmail">$sendmail</a> doesn't support the <code class="literal">-f</code> switch.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-from"></a>3.298. use_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will generate the “<span class="quote">From:</span>” header field when
-sending messages. If <span class="emphasis"><em>unset</em></span>, no “<span class="quote">From:</span>” header field will be
-generated unless the user explicitly sets one using the “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-idn"></a>3.299. use_idn</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will show you international domain names decoded.
-Note: You can use IDNs for addresses even if this is <span class="emphasis"><em>unset</em></span>.
-This variable only affects decoding.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-ipv6"></a>3.300. use_ipv6</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will look for IPv6 addresses of hosts it tries to
-contact. If this option is <span class="emphasis"><em>unset</em></span>, Mutt will restrict itself to IPv4 addresses.
-Normally, the default should work.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="user-agent"></a>3.301. user_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will add a “<span class="quote">User-Agent:</span>” header to outgoing
-messages, indicating which version of mutt was used for composing
-them.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="visual"></a>3.302. visual</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Specifies the visual editor to invoke when the “<span class="quote"><code class="literal">˜v</code></span>” command is
-given in the builtin editor.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wait-key"></a>3.303. wait_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether Mutt will ask you to press a key after an external command
-has been invoked by these functions: <code class="literal"><shell-escape></code>,
-<code class="literal"><pipe-message></code>, <code class="literal"><pipe-entry></code>, <code class="literal"><print-message></code>,
-and <code class="literal"><print-entry></code> commands.
-</p><p>
-It is also used when viewing attachments with “<span class="quote"><a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a></span>”, provided
-that the corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag,
-and the external program is interactive.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will always ask for a key. When <span class="emphasis"><em>unset</em></span>, Mutt will wait
-for a key only if the external command returned a non-zero status.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="weed"></a>3.304. weed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will weed headers when displaying, forwarding,
-printing, or replying to messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap"></a>3.305. wrap</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-When set to a positive value, mutt will wrap text at <a class="link" href="#wrap" title="3.305. wrap">$wrap</a> characters.
-When set to a negative value, mutt will wrap text so that there are <a class="link" href="#wrap" title="3.305. wrap">$wrap</a>
-characters of empty space on the right side of the terminal.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap-search"></a>3.306. wrap_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether searches wrap around the end.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, searches will wrap around the first (or last) item. When
-<span class="emphasis"><em>unset</em></span>, incremental searches will not wrap.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrapmargin"></a>3.307. wrapmargin</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-(DEPRECATED) Equivalent to setting <a class="link" href="#wrap" title="3.305. wrap">$wrap</a> with a negative value.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-inc"></a>3.308. write_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-When writing a mailbox, a message will be printed every
-<a class="link" href="#write-inc" title="3.308. write_inc">$write_inc</a> messages to indicate progress. If set to 0, only a
-single message will be displayed before writing a mailbox.
-</p><p>
-Also see the <a class="link" href="#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="#time-inc" title="3.289. time_inc">$time_inc</a> variables and the
-“<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-bcc"></a>3.309. write_bcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether mutt writes out the “<span class="quote">Bcc:</span>” header when preparing
-messages to be sent. Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see <a class="link" href="#smtp-url" title="3.272. smtp_url">$smtp_url</a>), this
-option does nothing: mutt will never write out the “<span class="quote">Bcc:</span>” header
-in this case.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, exim4 and postfix strip BCC headers by
-default. The above warning applies to exim3 users, see /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-icon"></a>3.310. xterm_icon</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">M%?n?AIL&ail?</code></span>”</p></div><p>
-Controls the format of the icon title, as long as xterm_set_titles
-is enabled. This string is identical in formatting to the one used by
-“<span class="quote"><a class="link" href="#status-format" title="3.281. status_format">$status_format</a></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-set-titles"></a>3.311. xterm_set_titles</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether mutt sets the xterm title bar and icon name
-(as long as you are in an appropriate terminal).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-title"></a>3.312. xterm_title</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?</code></span>”</p></div><p>
-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 “<span class="quote"><a class="link" href="#status-format" title="3.281. status_format">$status_format</a></span>”.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="functions"></a>4. Functions</h2></div></div></div><p>
-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 <a class="link" href="#bind" title="5. Changing the default key bindings">bind</a>
-command.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="generic_map"></a>4.1. generic menu</h3></div></div></div><p>
-The <span class="emphasis"><em>generic</em></span> menu is not a real menu, but specifies common functions
-(such as movement) available in all menus except for <span class="emphasis"><em>pager</em></span> and
-<span class="emphasis"><em>editor</em></span>. Changing settings for this menu will affect the default
-bindings for all menus (except as noted).
-</p><div class="table"><a id="generic_table"></a><p class="title"><b>Table 8.2. Default generic function bindings</b></p><div class="table-contents"><table summary="Default generic function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><top-page></code></td><td>H</td><td>move to the top of the page</td></tr><tr><td><code class="literal"><next-entry></code></td><td>j</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>k</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><bottom-page></code></td><td>L</td><td>move to the bottom of the page</td></tr><tr><td><code class="literal"><refresh></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><middle-page></code></td><td>M</td><td>move to the middle of the page</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><tag-entry></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><next-page></code></td><td>z</td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>Z</td><td>move to the previous page</td></tr><tr><td><code class="literal"><last-entry></code></td><td>*</td><td>move to the last entry</td></tr><tr><td><code class="literal"><first-entry></code></td><td>=</td><td>move to the first entry</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><next-line></code></td><td>></td><td>scroll down one line</td></tr><tr><td><code class="literal"><previous-line></code></td><td><</td><td>scroll up one line</td></tr><tr><td><code class="literal"><half-up></code></td><td>[</td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td>]</td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><tag-prefix></code></td><td>;</td><td>apply next function to tagged messages</td></tr><tr><td><code class="literal"><tag-prefix-cond></code></td><td> </td><td>apply next function ONLY to tagged messages</td></tr><tr><td><code class="literal"><end-cond></code></td><td> </td><td>end of conditional execution (noop)</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><select-entry></code></td><td><Return></td><td>select the current entry</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><current-top></code></td><td> </td><td>move entry to top of screen</td></tr><tr><td><code class="literal"><current-middle></code></td><td> </td><td>move entry to middle of screen</td></tr><tr><td><code class="literal"><current-bottom></code></td><td> </td><td>move entry to bottom of screen</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index_map"></a>4.2. index menu</h3></div></div></div><div class="table"><a id="index_table"></a><p class="title"><b>Table 8.3. Default index function bindings</b></p><div class="table-contents"><table summary="Default index function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><collapse-thread></code></td><td>Esc v</td><td>collapse/uncollapse current thread</td></tr><tr><td><code class="literal"><collapse-all></code></td><td>Esc V</td><td>collapse/uncollapse all threads</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-pattern></code></td><td>D</td><td>delete messages matching a pattern</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><fetch-mail></code></td><td>G</td><td>retrieve mail from POP server</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><limit></code></td><td>l</td><td>show only messages matching a pattern</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><toggle-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><toggle-write></code></td><td>%</td><td>toggle whether the mailbox will be rewritten</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><quit></code></td><td>q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><show-limit></code></td><td>Esc l</td><td>show currently active limit pattern</td></tr><tr><td><code class="literal"><sort-mailbox></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><tag-pattern></code></td><td>T</td><td>tag messages matching a pattern</td></tr><tr><td><code class="literal"><tag-subthread></code></td><td> </td><td>tag the current subthread</td></tr><tr><td><code class="literal"><tag-thread></code></td><td>Esc t</td><td>tag the current thread</td></tr><tr><td><code class="literal"><untag-pattern></code></td><td>^T</td><td>untag messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-pattern></code></td><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><set-flag></code></td><td>w</td><td>set a status flag on a message</td></tr><tr><td><code class="literal"><clear-flag></code></td><td>W</td><td>clear a status flag from a message</td></tr><tr><td><code class="literal"><display-message></code></td><td><Return></td><td>display a message</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><next-new-then-unread></code></td><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-new-then-unread></code></td><td>Esc <Tab></td><td>jump to the previous new or unread message</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr><tr><td><code class="literal"><sidebar-scroll-up></code></td><td> </td><td>scroll the mailbox pane up 1 page</td></tr><tr><td><code class="literal"><sidebar-scroll-down></code></td><td> </td><td>scroll the mailbox pane down 1 page</td></tr><tr><td><code class="literal"><sidebar-next></code></td><td> </td><td>go down to next mailbox</td></tr><tr><td><code class="literal"><sidebar-prev></code></td><td> </td><td>go to previous mailbox</td></tr><tr><td><code class="literal"><sidebar-open></code></td><td> </td><td>open hilighted mailbox</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager_map"></a>4.3. pager menu</h3></div></div></div><div class="table"><a id="pager_table"></a><p class="title"><b>Table 8.4. Default pager function bindings</b></p><div class="table-contents"><table summary="Default pager function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><next-entry></code></td><td>J</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>K</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><redraw-screen></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><mark-as-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><quit></code></td><td>Q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><skip-quoted></code></td><td>S</td><td>skip beyond quoted text</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><tag-message></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><toggle-quoted></code></td><td>T</td><td>toggle display of quoted text</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><search-toggle></code></td><td>\\</td><td>toggle search pattern coloring</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><next-page></code></td><td><Space></td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>-</td><td>move to the previous page</td></tr><tr><td><code class="literal"><top></code></td><td>^</td><td>jump to the top of the message</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><next-line></code></td><td><Return></td><td>scroll down one line</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><half-up></code></td><td> </td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td> </td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><previous-line></code></td><td> </td><td>scroll up one line</td></tr><tr><td><code class="literal"><bottom></code></td><td> </td><td>jump to the bottom of the message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr><tr><td><code class="literal"><sidebar-scroll-up></code></td><td> </td><td>scroll the mailbox pane up 1 page</td></tr><tr><td><code class="literal"><sidebar-scroll-down></code></td><td> </td><td>scroll the mailbox pane down 1 page</td></tr><tr><td><code class="literal"><sidebar-next></code></td><td> </td><td>go down to next mailbox</td></tr><tr><td><code class="literal"><sidebar-prev></code></td><td> </td><td>go to previous mailbox</td></tr><tr><td><code class="literal"><sidebar-open></code></td><td> </td><td>open hilighted mailbox</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias_map"></a>4.4. alias menu</h3></div></div></div><div class="table"><a id="alias_table"></a><p class="title"><b>Table 8.5. Default alias function bindings</b></p><div class="table-contents"><table summary="Default alias function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query_map"></a>4.5. query menu</h3></div></div></div><div class="table"><a id="query_table"></a><p class="title"><b>Table 8.6. Default query function bindings</b></p><div class="table-contents"><table summary="Default query function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><query-append></code></td><td>A</td><td>append new query results to current results</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach_map"></a>4.6. attach menu</h3></div></div></div><div class="table"><a id="attach_table"></a><p class="title"><b>Table 8.7. Default attach function bindings</b></p><div class="table-contents"><table summary="Default attach function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><print-entry></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><save-entry></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><view-mailcap></code></td><td>m</td><td>force viewing of attachment using mailcap</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><view-text></code></td><td>T</td><td>view attachment as text</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><collapse-parts></code></td><td>v</td><td>Toggle display of subparts</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose_map"></a>4.7. compose menu</h3></div></div></div><div class="table"><a id="compose_table"></a><p class="title"><b>Table 8.8. Default compose function bindings</b></p><div class="table-contents"><table summary="Default compose function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><attach-file></code></td><td>a</td><td>attach file(s) to this message</td></tr><tr><td><code class="literal"><attach-message></code></td><td>A</td><td>attach message(s) to this message</td></tr><tr><td><code class="literal"><edit-bcc></code></td><td>b</td><td>edit the BCC list</td></tr><tr><td><code class="literal"><edit-cc></code></td><td>c</td><td>edit the CC list</td></tr><tr><td><code class="literal"><copy-file></code></td><td>C</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><detach-file></code></td><td>D</td><td>delete the current entry</td></tr><tr><td><code class="literal"><toggle-disposition></code></td><td>^D</td><td>toggle disposition between inline/attachment</td></tr><tr><td><code class="literal"><edit-description></code></td><td>d</td><td>edit attachment description</td></tr><tr><td><code class="literal"><edit-message></code></td><td>e</td><td>edit the message</td></tr><tr><td><code class="literal"><edit-headers></code></td><td>E</td><td>edit the message with headers</td></tr><tr><td><code class="literal"><edit-file></code></td><td>^X e</td><td>edit the file to be attached</td></tr><tr><td><code class="literal"><edit-encoding></code></td><td>^E</td><td>edit attachment transfer-encoding</td></tr><tr><td><code class="literal"><edit-from></code></td><td>Esc f</td><td>edit the from field</td></tr><tr><td><code class="literal"><edit-fcc></code></td><td>f</td><td>enter a file to save a copy of this message in</td></tr><tr><td><code class="literal"><filter-entry></code></td><td>F</td><td>filter attachment through a shell command</td></tr><tr><td><code class="literal"><get-attachment></code></td><td>G</td><td>get a temporary copy of an attachment</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><ispell></code></td><td>i</td><td>run ispell on the message</td></tr><tr><td><code class="literal"><print-entry></code></td><td>l</td><td>print the current entry</td></tr><tr><td><code class="literal"><edit-mime></code></td><td>m</td><td>edit attachment using mailcap entry</td></tr><tr><td><code class="literal"><new-mime></code></td><td>n</td><td>compose new attachment using mailcap entry</td></tr><tr><td><code class="literal"><postpone-message></code></td><td>P</td><td>save this message to send later</td></tr><tr><td><code class="literal"><edit-reply-to></code></td><td>r</td><td>edit the Reply-To field</td></tr><tr><td><code class="literal"><rename-file></code></td><td>R</td><td>rename/move an attached file</td></tr><tr><td><code class="literal"><edit-subject></code></td><td>s</td><td>edit the subject of this message</td></tr><tr><td><code class="literal"><edit-to></code></td><td>t</td><td>edit the TO list</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^T</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><write-fcc></code></td><td>w</td><td>write the message to a folder</td></tr><tr><td><code class="literal"><toggle-unlink></code></td><td>u</td><td>toggle whether to delete file after sending it</td></tr><tr><td><code class="literal"><toggle-recode></code></td><td> </td><td>toggle recoding of this attachment</td></tr><tr><td><code class="literal"><update-encoding></code></td><td>U</td><td>update an attachment's encoding info</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><send-message></code></td><td>y</td><td>send the message</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><attach-key></code></td><td>Esc k</td><td>attach a PGP public key</td></tr><tr><td><code class="literal"><pgp-menu></code></td><td>p</td><td>show PGP options</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><smime-menu></code></td><td>S</td><td>show S/MIME options</td></tr><tr><td><code class="literal"><mix></code></td><td>M</td><td>send the message through a mixmaster remailer chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone_map"></a>4.8. postpone menu</h3></div></div></div><div class="table"><a id="postpone_table"></a><p class="title"><b>Table 8.9. Default postpone function bindings</b></p><div class="table-contents"><table summary="Default postpone function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="browser_map"></a>4.9. browser menu</h3></div></div></div><div class="table"><a id="browser_table"></a><p class="title"><b>Table 8.10. Default browser function bindings</b></p><div class="table-contents"><table summary="Default browser function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><change-dir></code></td><td>c</td><td>change directories</td></tr><tr><td><code class="literal"><display-filename></code></td><td>@</td><td>display the currently selected file's name</td></tr><tr><td><code class="literal"><enter-mask></code></td><td>m</td><td>enter a file mask</td></tr><tr><td><code class="literal"><sort></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><select-new></code></td><td>N</td><td>select a new file in this directory</td></tr><tr><td><code class="literal"><check-new></code></td><td> </td><td>check mailboxes for new mail</td></tr><tr><td><code class="literal"><toggle-mailboxes></code></td><td><Tab></td><td>toggle whether to browse mailboxes or all files</td></tr><tr><td><code class="literal"><view-file></code></td><td><Space></td><td>view file</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><create-mailbox></code></td><td>C</td><td>create a new mailbox (IMAP only)</td></tr><tr><td><code class="literal"><delete-mailbox></code></td><td>d</td><td>delete the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><rename-mailbox></code></td><td>r</td><td>rename the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><subscribe></code></td><td>s</td><td>subscribe to current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><unsubscribe></code></td><td>u</td><td>unsubscribe from current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><toggle-subscribed></code></td><td>T</td><td>toggle view all/subscribed mailboxes (IMAP only)</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp_map"></a>4.10. pgp menu</h3></div></div></div><div class="table"><a id="pgp_table"></a><p class="title"><b>Table 8.11. Default pgp function bindings</b></p><div class="table-contents"><table summary="Default pgp function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime_map"></a>4.11. smime menu</h3></div></div></div><div class="table"><a id="smime_table"></a><p class="title"><b>Table 8.12. Default smime function bindings</b></p><div class="table-contents"><table summary="Default smime function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix_map"></a>4.12. mix menu</h3></div></div></div><div class="table"><a id="mix_table"></a><p class="title"><b>Table 8.13. Default mix function bindings</b></p><div class="table-contents"><table summary="Default mix function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><accept></code></td><td><Return></td><td>Accept the chain constructed</td></tr><tr><td><code class="literal"><append></code></td><td>a</td><td>Append a remailer to the chain</td></tr><tr><td><code class="literal"><insert></code></td><td>i</td><td>Insert a remailer into the chain</td></tr><tr><td><code class="literal"><delete></code></td><td>d</td><td>Delete a remailer from the chain</td></tr><tr><td><code class="literal"><chain-prev></code></td><td><Left></td><td>Select the previous element of the chain</td></tr><tr><td><code class="literal"><chain-next></code></td><td><Right></td><td>Select the next element of the chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor_map"></a>4.13. editor menu</h3></div></div></div><div class="table"><a id="editor_table"></a><p class="title"><b>Table 8.14. Default editor function bindings</b></p><div class="table-contents"><table summary="Default editor function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bol></code></td><td>^A</td><td>jump to the beginning of the line</td></tr><tr><td><code class="literal"><backward-char></code></td><td>^B</td><td>move the cursor one character to the left</td></tr><tr><td><code class="literal"><backward-word></code></td><td>Esc b</td><td>move the cursor to the beginning of the word</td></tr><tr><td><code class="literal"><capitalize-word></code></td><td>Esc c</td><td>capitalize the word</td></tr><tr><td><code class="literal"><downcase-word></code></td><td>Esc l</td><td>convert the word to lower case</td></tr><tr><td><code class="literal"><upcase-word></code></td><td>Esc u</td><td>convert the word to upper case</td></tr><tr><td><code class="literal"><delete-char></code></td><td>^D</td><td>delete the char under the cursor</td></tr><tr><td><code class="literal"><eol></code></td><td>^E</td><td>jump to the end of the line</td></tr><tr><td><code class="literal"><forward-char></code></td><td>^F</td><td>move the cursor one character to the right</td></tr><tr><td><code class="literal"><forward-word></code></td><td>Esc f</td><td>move the cursor to the end of the word</td></tr><tr><td><code class="literal"><backspace></code></td><td><Backspace></td><td>delete the char in front of the cursor</td></tr><tr><td><code class="literal"><kill-eol></code></td><td>^K</td><td>delete chars from cursor to end of line</td></tr><tr><td><code class="literal"><kill-eow></code></td><td>Esc d</td><td>delete chars from the cursor to the end of the word</td></tr><tr><td><code class="literal"><kill-line></code></td><td>^U</td><td>delete all chars on the line</td></tr><tr><td><code class="literal"><quote-char></code></td><td>^V</td><td>quote the next typed key</td></tr><tr><td><code class="literal"><kill-word></code></td><td>^W</td><td>delete the word in front of the cursor</td></tr><tr><td><code class="literal"><complete></code></td><td><Tab></td><td>complete filename or alias</td></tr><tr><td><code class="literal"><complete-query></code></td><td>^T</td><td>complete address with query</td></tr><tr><td><code class="literal"><buffy-cycle></code></td><td><Space></td><td>cycle among incoming mailboxes</td></tr><tr><td><code class="literal"><history-up></code></td><td> </td><td>scroll up through the history list</td></tr><tr><td><code class="literal"><history-down></code></td><td> </td><td>scroll down through the history list</td></tr><tr><td><code class="literal"><transpose-chars></code></td><td> </td><td>transpose character under cursor with previous</td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="miscellany"></a>Chapter 9. Miscellany</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="#about">2. About this document</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="acknowledgements"></a>1. Acknowledgements</h2></div></div></div><p>
-Kari Hurtta <code class="email"><<a class="email" href="mailto:kari.hurtta@fmi.fi">kari.hurtta@fmi.fi</a>></code>
-co-developed the original MIME parsing code back in the ELM-ME days.
-</p><p>
-The following people have been very helpful to the development of Mutt:
-</p><div class="itemizedlist"><ul type="disc"><li><p>Vikas Agnihotri <code class="email"><<a class="email" href="mailto:vikasa@writeme.com">vikasa@writeme.com</a>></code></p></li><li><p>Francois Berjon <code class="email"><<a class="email" href="mailto:Francois.Berjon@aar.alcatel-alsthom.fr">Francois.Berjon@aar.alcatel-alsthom.fr</a>></code></p></li><li><p>Aric Blumer <code class="email"><<a class="email" href="mailto:aric@fore.com">aric@fore.com</a>></code></p></li><li><p>John Capo <code class="email"><<a class="email" href="mailto:jc@irbs.com">jc@irbs.com</a>></code></p></li><li><p>David Champion <code class="email"><<a class="email" href="mailto:dgc@uchicago.edu">dgc@uchicago.edu</a>></code></p></li><li><p>Brendan Cully <code class="email"><<a class="email" href="mailto:brendan@kublai.com">brendan@kublai.com</a>></code></p></li><li><p>Liviu Daia <code class="email"><<a class="email" href="mailto:daia@stoilow.imar.ro">daia@stoilow.imar.ro</a>></code></p></li><li><p>Thomas E. Dickey <code class="email"><<a class="email" href="mailto:dickey@herndon4.his.com">dickey@herndon4.his.com</a>></code></p></li><li><p>David DeSimone <code class="email"><<a class="email" href="mailto:fox@convex.hp.com">fox@convex.hp.com</a>></code></p></li><li><p>Nickolay N. Dudorov <code class="email"><<a class="email" href="mailto:nnd@wint.itfs.nsk.su">nnd@wint.itfs.nsk.su</a>></code></p></li><li><p>Ruslan Ermilov <code class="email"><<a class="email" href="mailto:ru@freebsd.org">ru@freebsd.org</a>></code></p></li><li><p>Edmund Grimley Evans <code class="email"><<a class="email" href="mailto:edmundo@rano.org">edmundo@rano.org</a>></code></p></li><li><p>Michael Finken <code class="email"><<a class="email" href="mailto:finken@conware.de">finken@conware.de</a>></code></p></li><li><p>Sven Guckes <code class="email"><<a class="email" href="mailto:guckes@math.fu-berlin.de">guckes@math.fu-berlin.de</a>></code></p></li><li><p>Lars Hecking <code class="email"><<a class="email" href="mailto:lhecking@nmrc.ie">lhecking@nmrc.ie</a>></code></p></li><li><p>Mark Holloman <code class="email"><<a class="email" href="mailto:holloman@nando.net">holloman@nando.net</a>></code></p></li><li><p>Andreas Holzmann <code class="email"><<a class="email" href="mailto:holzmann@fmi.uni-passau.de">holzmann@fmi.uni-passau.de</a>></code></p></li><li><p>Marco d'Itri <code class="email"><<a class="email" href="mailto:md@linux.it">md@linux.it</a>></code></p></li><li><p>Björn Jacke <code class="email"><<a class="email" href="mailto:bjacke@suse.com">bjacke@suse.com</a>></code></p></li><li><p>Byrial Jensen <code class="email"><<a class="email" href="mailto:byrial@image.dk">byrial@image.dk</a>></code></p></li><li><p>David Jeske <code class="email"><<a class="email" href="mailto:jeske@igcom.net">jeske@igcom.net</a>></code></p></li><li><p>Christophe Kalt <code class="email"><<a class="email" href="mailto:kalt@hugo.int-evry.fr">kalt@hugo.int-evry.fr</a>></code></p></li><li><p>Tommi Komulainen <code class="email"><<a class="email" href="mailto:Tommi.Komulainen@iki.fi">Tommi.Komulainen@iki.fi</a>></code></p></li><li><p>Felix von Leitner (a.k.a “<span class="quote">Fefe</span>”) <code class="email"><<a class="email" href="mailto:leitner@math.fu-berlin.de">leitner@math.fu-berlin.de</a>></code></p></li><li><p>Brandon Long <code class="email"><<a class="email" href="mailto:blong@fiction.net">blong@fiction.net</a>></code></p></li><li><p>Jimmy Mäkelä <code class="email"><<a class="email" href="mailto:jmy@flashback.net">jmy@flashback.net</a>></code></p></li><li><p>Lars Marowsky-Bree <code class="email"><<a class="email" href="mailto:lmb@pointer.in-minden.de">lmb@pointer.in-minden.de</a>></code></p></li><li><p>Thomas “<span class="quote">Mike</span>” Michlmayr <code class="email"><<a class="email" href="mailto:mike@cosy.sbg.ac.at">mike@cosy.sbg.ac.at</a>></code></p></li><li><p>Andrew W. Nosenko <code class="email"><<a class="email" href="mailto:awn@bcs.zp.ua">awn@bcs.zp.ua</a>></code></p></li><li><p>David O'Brien <code class="email"><<a class="email" href="mailto:obrien@Nuxi.cs.ucdavis.edu">obrien@Nuxi.cs.ucdavis.edu</a>></code></p></li><li><p>Clint Olsen <code class="email"><<a class="email" href="mailto:olsenc@ichips.intel.com">olsenc@ichips.intel.com</a>></code></p></li><li><p>Park Myeong Seok <code class="email"><<a class="email" href="mailto:pms@romance.kaist.ac.kr">pms@romance.kaist.ac.kr</a>></code></p></li><li><p>Thomas Parmelan <code class="email"><<a class="email" href="mailto:tom@ankh.fr.eu.org">tom@ankh.fr.eu.org</a>></code></p></li><li><p>Ollivier Robert <code class="email"><<a class="email" href="mailto:roberto@keltia.freenix.fr">roberto@keltia.freenix.fr</a>></code></p></li><li><p>Thomas Roessler <code class="email"><<a class="email" href="mailto:roessler@does-not-exist.org">roessler@does-not-exist.org</a>></code></p></li><li><p>Roland Rosenfeld <code class="email"><<a class="email" href="mailto:roland@spinnaker.de">roland@spinnaker.de</a>></code></p></li><li><p>Rocco Rutte <code class="email"><<a class="email" href="mailto:pdmef@gmx.net">pdmef@gmx.net</a>></code></p></li><li><p>TAKIZAWA Takashi <code class="email"><<a class="email" href="mailto:taki@luna.email.ne.jp">taki@luna.email.ne.jp</a>></code></p></li><li><p>Allain Thivillon <code class="email"><<a class="email" href="mailto:Allain.Thivillon@alma.fr">Allain.Thivillon@alma.fr</a>></code></p></li><li><p>Gero Treuner <code class="email"><<a class="email" href="mailto:gero@70t.de">gero@70t.de</a>></code></p></li><li><p>Vsevolod Volkov <code class="email"><<a class="email" href="mailto:vvv@lucky.net">vvv@lucky.net</a>></code></p></li><li><p>Ken Weinert <code class="email"><<a class="email" href="mailto:kenw@ihs.com">kenw@ihs.com</a>></code></p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="about"></a>2. About this document</h2></div></div></div><p>
-This document was written in <a class="ulink" href="http://docbook.sourceforge.net" target="_top">DocBook</a>,
-and then rendered using the <a class="ulink" href="http://xmlsoft.org/XSLT/" target="_top">Gnome XSLT toolkit</a>.
-</p></div></div></div></body></html>
+++ /dev/null
- The Mutt E-Mail Client
-
- Michael Elkins
-
- <me@cs.hmc.edu>
-
- version 1.5.19 (2009-01-05)
-
- Abstract
-
- "All mail clients suck. This one just sucks less." -me, circa 1995
-
- ----------------------------------------------------------------------
-
- Table of Contents
-
- 1. Introduction
-
- 1. Mutt Home Page
-
- 2. Mailing Lists
-
- 3. Software Distribution Sites
-
- 4. Mutt online resources
-
- 5. Contributing to Mutt
-
- 6. Typograhical conventions
-
- 7. Copyright
-
- 2. Getting Started
-
- 1. Core concepts
-
- 2. Moving Around in Menus
-
- 3. Editing Input Fields
-
- 3.1. Introduction
-
- 3.2. History
-
- 4. Reading Mail - The Index and Pager
-
- 4.1. The Message Index
-
- 4.2. The Pager
-
- 4.3. Threaded Mode
-
- 4.4. Miscellaneous Functions
-
- 5. Sending Mail
-
- 5.1. Introduction
-
- 5.2. Editing the message header
-
- 5.3. Sending cryptographically signed/encrypted
- messages
-
- 5.4. Sending anonymous messages via mixmaster
-
- 5.5. Sending format=flowed messages
-
- 6. Forwarding and Bouncing Mail
-
- 7. Postponing Mail
-
- 3. Configuration
-
- 1. Location of initialization files
-
- 2. Syntax of Initialization Files
-
- 3. Address groups
-
- 4. Defining/Using aliases
-
- 5. Changing the default key bindings
-
- 6. Defining aliases for character sets
-
- 7. Setting variables based upon mailbox
-
- 8. Keyboard macros
-
- 9. Using color and mono video attributes
-
- 10. Message header display
-
- 11. Alternative addresses
-
- 12. Mailing lists
-
- 13. Using Multiple spool mailboxes
-
- 14. Monitoring incoming mail
-
- 15. User defined headers
-
- 16. Specify default save mailbox
-
- 17. Specify default Fcc: mailbox when composing
-
- 18. Specify default save filename and default Fcc: mailbox at
- once
-
- 19. Change settings based upon message recipients
-
- 20. Change settings before formatting a message
-
- 21. Choosing the cryptographic key of the recipient
-
- 22. Adding key sequences to the keyboard buffer
-
- 23. Executing functions
-
- 24. Message Scoring
-
- 25. Spam detection
-
- 26. Setting and Querying Variables
-
- 26.1. Commands
-
- 26.2. User-defined variables
-
- 27. Reading initialization commands from another file
-
- 28. Configuring features conditionnaly
-
- 29. Removing hooks
-
- 30. Format Strings
-
- 30.1. Basic usage
-
- 30.2. Filters
-
- 4. Advanced Usage
-
- 1. Regular Expressions
-
- 2. Patterns: Searching, Limiting and Tagging
-
- 2.1. Pattern Modifier
-
- 2.2. Simple Patterns
-
- 2.3. Complex Patterns
-
- 2.4. Searching by Date
-
- 3. Using Tags
-
- 4. Using Hooks
-
- 4.1. Message Matching in Hooks
-
- 5. External Address Queries
-
- 6. Mailbox Formats
-
- 7. Mailbox Shortcuts
-
- 8. Handling Mailing Lists
-
- 9. Handling multiple folders
-
- 10. Editing threads
-
- 10.1. Linking threads
-
- 10.2. Breaking threads
-
- 11. Delivery Status Notification (DSN) Support
-
- 12. Start a WWW Browser on URLs
-
- 5. Mutt's MIME Support
-
- 1. Using MIME in Mutt
-
- 1.1. Viewing MIME messages in the pager
-
- 1.2. The Attachment Menu
-
- 1.3. The Compose Menu
-
- 2. MIME Type configuration with mime.types
-
- 3. MIME Viewer configuration with mailcap
-
- 3.1. The Basics of the mailcap file
-
- 3.2. Secure use of mailcap
-
- 3.3. Advanced mailcap Usage
-
- 3.4. Example mailcap files
-
- 4. MIME Autoview
-
- 5. MIME Multipart/Alternative
-
- 6. Attachment Searching and Counting
-
- 7. MIME Lookup
-
- 6. Optional features
-
- 1. General notes
-
- 1.1. Enabling/disabling features
-
- 1.2. URL syntax
-
- 2. SSL/TLS Support
-
- 3. POP3 Support
-
- 4. IMAP Support
-
- 4.1. The Folder Browser
-
- 4.2. Authentication
-
- 5. SMTP Support
-
- 6. Managing multiple accounts
-
- 7. Local caching
-
- 7.1. Header caching
-
- 7.2. Body caching
-
- 7.3. Maintenance
-
- 8. Exact address generation
-
- 7. Performance tuning
-
- 1. Reading and writing mailboxes
-
- 2. Reading messages from remote folders
-
- 3. Searching and limiting
-
- 8. Reference
-
- 1. Command line options
-
- 2. Configuration Commands
-
- 3. Configuration variables
-
- 3.1. abort_nosubject
-
- 3.2. abort_unmodified
-
- 3.3. alias_file
-
- 3.4. alias_format
-
- 3.5. allow_8bit
-
- 3.6. allow_ansi
-
- 3.7. arrow_cursor
-
- 3.8. ascii_chars
-
- 3.9. askbcc
-
- 3.10. askcc
-
- 3.11. assumed_charset
-
- 3.12. attach_charset
-
- 3.13. attach_format
-
- 3.14. attach_sep
-
- 3.15. attach_split
-
- 3.16. attribution
-
- 3.17. autoedit
-
- 3.18. auto_tag
-
- 3.19. beep
-
- 3.20. beep_new
-
- 3.21. bounce
-
- 3.22. bounce_delivered
-
- 3.23. braille_friendly
-
- 3.24. check_mbox_size
-
- 3.25. charset
-
- 3.26. check_new
-
- 3.27. collapse_unread
-
- 3.28. uncollapse_jump
-
- 3.29. compose_format
-
- 3.30. config_charset
-
- 3.31. confirmappend
-
- 3.32. confirmcreate
-
- 3.33. connect_timeout
-
- 3.34. content_type
-
- 3.35. copy
-
- 3.36. crypt_use_gpgme
-
- 3.37. crypt_use_pka
-
- 3.38. crypt_autopgp
-
- 3.39. crypt_autosmime
-
- 3.40. date_format
-
- 3.41. default_hook
-
- 3.42. delete
-
- 3.43. delete_untag
-
- 3.44. digest_collapse
-
- 3.45. display_filter
-
- 3.46. dotlock_program
-
- 3.47. dsn_notify
-
- 3.48. dsn_return
-
- 3.49. duplicate_threads
-
- 3.50. edit_headers
-
- 3.51. editor
-
- 3.52. encode_from
-
- 3.53. envelope_from_address
-
- 3.54. escape
-
- 3.55. fast_reply
-
- 3.56. fcc_attach
-
- 3.57. fcc_clear
-
- 3.58. folder
-
- 3.59. folder_format
-
- 3.60. followup_to
-
- 3.61. force_name
-
- 3.62. forward_decode
-
- 3.63. forward_edit
-
- 3.64. forward_format
-
- 3.65. forward_quote
-
- 3.66. from
-
- 3.67. gecos_mask
-
- 3.68. hdrs
-
- 3.69. header
-
- 3.70. help
-
- 3.71. hidden_host
-
- 3.72. hide_limited
-
- 3.73. hide_missing
-
- 3.74. hide_thread_subject
-
- 3.75. hide_top_limited
-
- 3.76. hide_top_missing
-
- 3.77. history
-
- 3.78. history_file
-
- 3.79. honor_followup_to
-
- 3.80. hostname
-
- 3.81. ignore_linear_white_space
-
- 3.82. ignore_list_reply_to
-
- 3.83. imap_authenticators
-
- 3.84. imap_check_subscribed
-
- 3.85. imap_delim_chars
-
- 3.86. imap_headers
-
- 3.87. imap_idle
-
- 3.88. imap_keepalive
-
- 3.89. imap_list_subscribed
-
- 3.90. imap_login
-
- 3.91. imap_pass
-
- 3.92. imap_passive
-
- 3.93. imap_peek
-
- 3.94. imap_pipeline_depth
-
- 3.95. imap_servernoise
-
- 3.96. imap_user
-
- 3.97. implicit_autoview
-
- 3.98. include
-
- 3.99. include_onlyfirst
-
- 3.100. indent_string
-
- 3.101. index_format
-
- 3.102. ispell
-
- 3.103. keep_flagged
-
- 3.104. locale
-
- 3.105. mail_check
-
- 3.106. mailcap_path
-
- 3.107. mailcap_sanitize
-
- 3.108. maildir_mtime
-
- 3.109. header_cache
-
- 3.110. maildir_header_cache_verify
-
- 3.111. header_cache_pagesize
-
- 3.112. maildir_trash
-
- 3.113. mark_old
-
- 3.114. markers
-
- 3.115. mask
-
- 3.116. mbox
-
- 3.117. mbox_type
-
- 3.118. metoo
-
- 3.119. menu_context
-
- 3.120. menu_move_off
-
- 3.121. menu_scroll
-
- 3.122. meta_key
-
- 3.123. mh_purge
-
- 3.124. mh_seq_flagged
-
- 3.125. mh_seq_replied
-
- 3.126. mh_seq_unseen
-
- 3.127. mime_forward
-
- 3.128. mime_forward_decode
-
- 3.129. mime_forward_rest
-
- 3.130. mix_entry_format
-
- 3.131. mixmaster
-
- 3.132. move
-
- 3.133. message_cachedir
-
- 3.134. message_cache_clean
-
- 3.135. message_format
-
- 3.136. narrow_tree
-
- 3.137. net_inc
-
- 3.138. pager
-
- 3.139. pager_context
-
- 3.140. pager_format
-
- 3.141. pager_index_lines
-
- 3.142. pager_stop
-
- 3.143. crypt_autosign
-
- 3.144. crypt_autoencrypt
-
- 3.145. pgp_ignore_subkeys
-
- 3.146. crypt_replyencrypt
-
- 3.147. crypt_replysign
-
- 3.148. crypt_replysignencrypted
-
- 3.149. crypt_timestamp
-
- 3.150. sidebar_delim
-
- 3.151. sidebar_visible
-
- 3.152. sidebar_width
-
- 3.153. pgp_use_gpg_agent
-
- 3.154. crypt_verify_sig
-
- 3.155. smime_is_default
-
- 3.156. smime_ask_cert_label
-
- 3.157. smime_decrypt_use_default_key
-
- 3.158. pgp_entry_format
-
- 3.159. pgp_good_sign
-
- 3.160. pgp_check_exit
-
- 3.161. pgp_long_ids
-
- 3.162. pgp_retainable_sigs
-
- 3.163. pgp_autoinline
-
- 3.164. pgp_replyinline
-
- 3.165. pgp_show_unusable
-
- 3.166. pgp_sign_as
-
- 3.167. pgp_strict_enc
-
- 3.168. pgp_timeout
-
- 3.169. pgp_sort_keys
-
- 3.170. pgp_mime_auto
-
- 3.171. pgp_auto_decode
-
- 3.172. pgp_mime_signature_filename
-
- 3.173. pgp_mime_signature_description
-
- 3.174. pgp_decode_command
-
- 3.175. pgp_getkeys_command
-
- 3.176. pgp_verify_command
-
- 3.177. pgp_decrypt_command
-
- 3.178. pgp_clearsign_command
-
- 3.179. pgp_sign_command
-
- 3.180. pgp_encrypt_sign_command
-
- 3.181. pgp_encrypt_only_command
-
- 3.182. pgp_import_command
-
- 3.183. pgp_export_command
-
- 3.184. pgp_verify_key_command
-
- 3.185. pgp_list_secring_command
-
- 3.186. pgp_list_pubring_command
-
- 3.187. forward_decrypt
-
- 3.188. smime_timeout
-
- 3.189. smime_encrypt_with
-
- 3.190. smime_keys
-
- 3.191. smime_ca_location
-
- 3.192. smime_certificates
-
- 3.193. smime_decrypt_command
-
- 3.194. smime_verify_command
-
- 3.195. smime_verify_opaque_command
-
- 3.196. smime_sign_command
-
- 3.197. smime_sign_opaque_command
-
- 3.198. smime_encrypt_command
-
- 3.199. smime_pk7out_command
-
- 3.200. smime_get_cert_command
-
- 3.201. smime_get_signer_cert_command
-
- 3.202. smime_import_cert_command
-
- 3.203. smime_get_cert_email_command
-
- 3.204. smime_default_key
-
- 3.205. ssl_client_cert
-
- 3.206. ssl_force_tls
-
- 3.207. ssl_starttls
-
- 3.208. certificate_file
-
- 3.209. ssl_use_sslv3
-
- 3.210. ssl_use_tlsv1
-
- 3.211. ssl_min_dh_prime_bits
-
- 3.212. ssl_ca_certificates_file
-
- 3.213. pipe_split
-
- 3.214. pipe_decode
-
- 3.215. pipe_sep
-
- 3.216. pop_authenticators
-
- 3.217. pop_auth_try_all
-
- 3.218. pop_checkinterval
-
- 3.219. pop_delete
-
- 3.220. pop_host
-
- 3.221. pop_last
-
- 3.222. pop_reconnect
-
- 3.223. pop_user
-
- 3.224. pop_pass
-
- 3.225. post_indent_string
-
- 3.226. postpone
-
- 3.227. postponed
-
- 3.228. preconnect
-
- 3.229. print
-
- 3.230. print_command
-
- 3.231. print_decode
-
- 3.232. print_split
-
- 3.233. prompt_after
-
- 3.234. query_command
-
- 3.235. query_format
-
- 3.236. quit
-
- 3.237. quote_regexp
-
- 3.238. read_inc
-
- 3.239. read_only
-
- 3.240. realname
-
- 3.241. recall
-
- 3.242. record
-
- 3.243. reply_regexp
-
- 3.244. reply_self
-
- 3.245. reply_to
-
- 3.246. resolve
-
- 3.247. reverse_alias
-
- 3.248. reverse_name
-
- 3.249. reverse_realname
-
- 3.250. rfc2047_parameters
-
- 3.251. save_address
-
- 3.252. save_empty
-
- 3.253. save_history
-
- 3.254. save_name
-
- 3.255. score
-
- 3.256. score_threshold_delete
-
- 3.257. score_threshold_flag
-
- 3.258. score_threshold_read
-
- 3.259. send_charset
-
- 3.260. sendmail
-
- 3.261. sendmail_wait
-
- 3.262. shell
-
- 3.263. sig_dashes
-
- 3.264. sig_on_top
-
- 3.265. signature
-
- 3.266. simple_search
-
- 3.267. smart_wrap
-
- 3.268. smileys
-
- 3.269. sleep_time
-
- 3.270. smtp_authenticators
-
- 3.271. smtp_pass
-
- 3.272. smtp_url
-
- 3.273. sort
-
- 3.274. sort_alias
-
- 3.275. sort_aux
-
- 3.276. sort_browser
-
- 3.277. sort_re
-
- 3.278. spam_separator
-
- 3.279. spoolfile
-
- 3.280. status_chars
-
- 3.281. status_format
-
- 3.282. status_on_top
-
- 3.283. strict_threads
-
- 3.284. suspend
-
- 3.285. text_flowed
-
- 3.286. thread_received
-
- 3.287. thorough_search
-
- 3.288. tilde
-
- 3.289. time_inc
-
- 3.290. timeout
-
- 3.291. tmpdir
-
- 3.292. to_chars
-
- 3.293. trash
-
- 3.294. tunnel
-
- 3.295. use_8bitmime
-
- 3.296. use_domain
-
- 3.297. use_envelope_from
-
- 3.298. use_from
-
- 3.299. use_idn
-
- 3.300. use_ipv6
-
- 3.301. user_agent
-
- 3.302. visual
-
- 3.303. wait_key
-
- 3.304. weed
-
- 3.305. wrap
-
- 3.306. wrap_search
-
- 3.307. wrapmargin
-
- 3.308. write_inc
-
- 3.309. write_bcc
-
- 3.310. xterm_icon
-
- 3.311. xterm_set_titles
-
- 3.312. xterm_title
-
- 4. Functions
-
- 4.1. generic menu
-
- 4.2. index menu
-
- 4.3. pager menu
-
- 4.4. alias menu
-
- 4.5. query menu
-
- 4.6. attach menu
-
- 4.7. compose menu
-
- 4.8. postpone menu
-
- 4.9. browser menu
-
- 4.10. pgp menu
-
- 4.11. smime menu
-
- 4.12. mix menu
-
- 4.13. editor menu
-
- 9. Miscellany
-
- 1. Acknowledgements
-
- 2. About this document
-
- List of Tables
-
- 1.1. Typographical conventions for special terms
-
- 2.1. Most common navigation keys
-
- 2.2. Most common line editor keys
-
- 2.3. Most common message index keys
-
- 2.4. Message status flags
-
- 2.5. Message recipient flags
-
- 2.6. Most common pager keys
-
- 2.7. ANSI escape sequences
-
- 2.8. Color sequences
-
- 2.9. Most common thread mode keys
-
- 2.10. Most common mail sending keys
-
- 2.11. Most common compose menu keys
-
- 2.12. PGP key menu flags
-
- 3.1. Symbolic key names
-
- 4.1. POSIX regular expression character classes
-
- 4.2. Regular expression repetition operators
-
- 4.3. GNU regular expression extensions
-
- 4.4. Pattern modifiers
-
- 4.5. Simple search keywords
-
- 4.6. Date units
-
- 8.1. Command line options
-
- 8.2. Default generic function bindings
-
- 8.3. Default index function bindings
-
- 8.4. Default pager function bindings
-
- 8.5. Default alias function bindings
-
- 8.6. Default query function bindings
-
- 8.7. Default attach function bindings
-
- 8.8. Default compose function bindings
-
- 8.9. Default postpone function bindings
-
- 8.10. Default browser function bindings
-
- 8.11. Default pgp function bindings
-
- 8.12. Default smime function bindings
-
- 8.13. Default mix function bindings
-
- 8.14. Default editor function bindings
-
- List of Examples
-
- 3.1. Multiple configuration commands per line
-
- 3.2. Commenting configuration files
-
- 3.3. Escaping quotes in congfiguration files
-
- 3.4. Using external command's output in configuration files
-
- 3.5. Using environment variables in configuration files
-
- 3.6. Configuring external alias files
-
- 3.7. Setting sort method based on mailbox name
-
- 3.8. Header weeding
-
- 3.9. Configuring header display order
-
- 3.10. Defining custom headers
-
- 3.11. Using %-expandos in save-hook
-
- 3.12. Embedding push in folder-hook
-
- 3.13. Configuring spam detection
-
- 3.14. Using user-defined variables for config file readability
-
- 3.15. Using user-defined variables for backing up other config option
- values
-
- 3.16. Deferring user-defined variable expansion to runtime
-
- 3.17. Using external filters in format strings
-
- 4.1. Using boolean operators in patterns
-
- 4.2. Combining send-hook and my_hdr
-
- 5.1. Attachment counting
-
-Chapter 1. Introduction
-
- Table of Contents
-
- 1. Mutt Home Page
-
- 2. Mailing Lists
-
- 3. Software Distribution Sites
-
- 4. Mutt online resources
-
- 5. Contributing to Mutt
-
- 6. Typograhical conventions
-
- 7. Copyright
-
- Mutt is a small but very powerful text-based MIME mail client. Mutt 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.
-
-1. Mutt Home Page
-
- The official homepage can be found at http://www.mutt.org/.
-
-2. Mailing Lists
-
- To subscribe to one of the following mailing lists, send a message with
- the word subscribe in the body to list-name-request@mutt.org.
-
- o <mutt-announce-request@mutt.org> -- low traffic list for announcements
-
- o <mutt-users-request@mutt.org> -- help, bug reports and feature
- requests
-
- o <mutt-dev-request@mutt.org> -- development mailing list
-
- Note
-
- All messages posted to mutt-announce are automatically forwarded to
- mutt-users, so you do not need to be subscribed to both lists.
-
-3. Software Distribution Sites
-
- Mutt releases can be downloaded from ftp://ftp.mutt.org/mutt/. For a list
- of mirror sites, please refer to http://www.mutt.org/download.html.
-
-4. Mutt online resources
-
- Bug Tracking System
-
- The official mutt bug tracking system can be found at
- http://dev.mutt.org/
-
- Wiki
-
- An (unofficial) wiki can be found at http://wiki.mutt.org/.
-
- IRC
-
- For the IRC user community, visit channel #mutt on
- irc.freenode.net.
-
- USENET
-
- For USENET, see the newsgroup comp.mail.mutt.
-
-5. Contributing to Mutt
-
- There are various ways to contribute to the Mutt project.
-
- Especially for new users it may be helpful to meet other new and
- experienced users to chat about Mutt, talk about problems and share
- tricks.
-
- Since translations of Mutt into other languages are highly appreciated,
- the mutt developers always look for skilled translators that help improve
- and continue to maintain stale translations.
-
- For contributing code patches for new features and bug fixes, please refer
- to the developer pages at http://dev.mutt.org/ for more details.
-
-6. Typograhical conventions
-
- This section lists typographical conventions followed throughout this
- manual. See table Table 1.1, "Typographical conventions for special terms"
- for typographical conventions for special terms.
-
- Table 1.1. Typographical conventions for special terms
-
- +----------------------------------------------------------+
- | Item | Refers to... |
- |----------------+-----------------------------------------|
- | printf(3) | UNIX manual pages, execute man 3 printf |
- |----------------+-----------------------------------------|
- | <PageUp> | named keys |
- |----------------+-----------------------------------------|
- | <create-alias> | named Mutt function |
- |----------------+-----------------------------------------|
- | ^G | Control+G key combination |
- |----------------+-----------------------------------------|
- | $mail_check | Mutt configuration option |
- +----------------------------------------------------------+
-
- Examples are presented as:
-
- mutt -v
-
- Within command synopsis, curly brackets ("{}") denote a set of options of
- which one is mandatory, square brackets ("[]") denote optional arguments,
- three dots denote that the argument may be repeated arbitrary times.
-
-7. Copyright
-
- Mutt is Copyright (C) 1996-2009 Michael R. Elkins <me@mutt.org> and
- others.
-
- This program is free software; you can redistribute it and/or modify it
- under the terms of the GNU General Public License as published by the Free
- Software Foundation; either version 2 of the License, or (at your option)
- any later version.
-
- This program is distributed in the hope that it will be useful, but
- WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
- for more details.
-
- You should have received a copy of the GNU General Public License along
- with this program; if not, write to the Free Software Foundation, Inc., 51
- Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-
-Chapter 2. Getting Started
-
- Table of Contents
-
- 1. Core concepts
-
- 2. Moving Around in Menus
-
- 3. Editing Input Fields
-
- 3.1. Introduction
-
- 3.2. History
-
- 4. Reading Mail - The Index and Pager
-
- 4.1. The Message Index
-
- 4.2. The Pager
-
- 4.3. Threaded Mode
-
- 4.4. Miscellaneous Functions
-
- 5. Sending Mail
-
- 5.1. Introduction
-
- 5.2. Editing the message header
-
- 5.3. Sending cryptographically signed/encrypted messages
-
- 5.4. Sending anonymous messages via mixmaster
-
- 5.5. Sending format=flowed messages
-
- 6. Forwarding and Bouncing Mail
-
- 7. Postponing Mail
-
- This section is intended as a brief overview of how to use Mutt. There are
- many other features which are described elsewhere in the manual. There is
- even more information available in the Mutt FAQ and various web pages. See
- the Mutt homepage for more details.
-
- The keybindings described in this section are the defaults as distributed.
- Your local system administrator may have altered the defaults for your
- site. You can always type "?" in any menu to display the current bindings.
-
- The first thing you need to do is invoke mutt, simply by typing mutt at
- the command line. There are various command-line options, see either the
- mutt man page or the reference.
-
-1. Core concepts
-
- Mutt is a text-based application which interacts with users through
- different menus which are mostly line-/entry-based or page-based. A
- line-based menu is the so-called "index" menu (listing all messages of the
- currently opened folder) or the "alias" menu (allowing you to select
- recipients from a list). Examples for page-based menus are the "pager"
- (showing one message at a time) or the "help" menu listing all available
- key bindings.
-
- The user interface consists of a context sensitive help line at the top,
- the menu's contents followed by a context sensitive status line and
- finally the command line. The command line is used to display
- informational and error messages as well as for prompts and for entering
- interactive commands.
-
- Because Mutt allows for customizing almost all key bindings, there are
- so-called "functions" which can be executed manually (using the command
- line) or in macros. Macros allow the user to bind a sequence of commands
- to a single key or a short key sequence instead of repeating a sequence of
- actions over and over.
-
- Many commands (such as saving or copying a message to another folder) can
- be applied to a single message or a set of messages (so-called "tagged"
- messages). To help selecting messages, Mutt provides a rich set of message
- patterns (such as recipients, sender, body contents, date sent/received,
- etc.) which can be combined into complex expressions using the boolean and
- and or operations as well as negating. These patterns can also be used to
- (for example) search for messages or to limit the index to show only
- matching messages.
-
- Mutt supports a "hook" concept which allows the user to execute arbitrary
- configuration commands and functions in certain situations such as
- entering a folder, starting a new message or replying to an existing one.
- These hooks can be used to highly customize Mutt's behaviour including
- managing multiple identities, customizing the display for a folder or even
- implementing auto-archiving based on a per-folder basis and much more.
-
-2. Moving Around in Menus
-
- The most important navigation keys common to all menus are shown in
- Table 2.1, "Most common navigation keys".
-
- Table 2.1. Most common navigation keys
-
- +------------------------------------------------------------------------+
- | 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 keybindings for the |
- | | | current menu |
- +------------------------------------------------------------------------+
-
-3. Editing Input Fields
-
- 3.1. Introduction
-
- Mutt has a built-in line editor for inputting text, e.g. email addresses
- or filenames. The keys used to manipulate text input are very similar to
- those of Emacs. See Table 2.2, "Most common line editor keys" for a full
- reference of available functions, their default key bindings, and short
- descriptions.
-
- Table 2.2. Most common line editor keys
-
- +------------------------------------------------------------------------+
- | Key | Function | Description |
- |----------------+-------------------+-----------------------------------|
- | ^A or <Home> | <bol> | move to the start of the line |
- |----------------+-------------------+-----------------------------------|
- | ^B or <Left> | <backward-char> | move back one char |
- |----------------+-------------------+-----------------------------------|
- | Esc B | <backward-word> | move back one word |
- |----------------+-------------------+-----------------------------------|
- | ^D or <Delete> | <delete-char> | delete the char under the cursor |
- |----------------+-------------------+-----------------------------------|
- | ^E or <End> | <eol> | move to the end of the line |
- |----------------+-------------------+-----------------------------------|
- | ^F or <Right> | <forward-char> | move forward one char |
- |----------------+-------------------+-----------------------------------|
- | Esc F | <forward-word> | move forward one word |
- |----------------+-------------------+-----------------------------------|
- | <Tab> | <complete> | complete filename or alias |
- |----------------+-------------------+-----------------------------------|
- | ^T | <complete-query> | complete address with query |
- |----------------+-------------------+-----------------------------------|
- | ^K | <kill-eol> | delete to the end of the line |
- |----------------+-------------------+-----------------------------------|
- | Esc d | <kill-eow> | delete to the end of the word |
- |----------------+-------------------+-----------------------------------|
- | ^W | <kill-word> | kill the word in front of the |
- | | | cursor |
- |----------------+-------------------+-----------------------------------|
- | ^U | <kill-line> | delete entire line |
- |----------------+-------------------+-----------------------------------|
- | ^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 |
- |----------------+-------------------+-----------------------------------|
- | Esc u | <upcase-word> | convert word to upper case |
- |----------------+-------------------+-----------------------------------|
- | Esc l | <downcase-word> | convert word to lower case |
- |----------------+-------------------+-----------------------------------|
- | Esc c | <capitalize-word> | capitalize the word |
- |----------------+-------------------+-----------------------------------|
- | ^G | n/a | abort |
- |----------------+-------------------+-----------------------------------|
- | <Return> | n/a | finish editing |
- +------------------------------------------------------------------------+
-
- You can remap the editor functions using the bind command. For example, to
- make the <Delete> key delete the character in front of the cursor rather
- than under, you could use:
-
- bind editor <delete> backspace
-
- 3.2. History
-
- Mutt maintains a history for the built-in editor. The number of items is
- controlled by the $history variable and can be made persistent using an
- external file specified using $history_file. You may cycle through them at
- an editor prompt by using the <history-up> and/or <history-down> commands.
-
- Mutt maintains several distinct history lists, one for each of the
- following categories:
-
- o muttrc commands
-
- o addresses and aliases
-
- o shell commands
-
- o filenames
-
- o patterns
-
- o everything else
-
- Mutt automatically filters out repeated items from the history. It also
- mimics the behavior of some shells by ignoring items starting with a
- space. The latter feature can be useful in macros to not clobber the
- history's valuable entries with unwanted entries.
-
-4. Reading Mail - The Index and Pager
-
- Similar to many other mail clients, there are two modes in which mail is
- read in Mutt. The first is the index of messages in the mailbox, which is
- called the "index" in Mutt. The second mode is the display of the message
- contents. This is called the "pager."
-
- The next few sections describe the functions provided in each of these
- modes.
-
- 4.1. The Message Index
-
- Common keys used to navigate through and manage messages in the index are
- shown in Table 2.3, "Most common message index keys". How messages are
- presented in the index menu can be customized using the $index_format
- variable.
-
- Table 2.3. Most common message index keys
-
- +--------------------------------------------------------+
- | Key | Description |
- |----------+---------------------------------------------|
- | c | change to a different mailbox |
- |----------+---------------------------------------------|
- | Esc c | change to a folder in read-only mode |
- |----------+---------------------------------------------|
- | C | copy the current message to another mailbox |
- |----------+---------------------------------------------|
- | Esc C | decode a message and copy it to a folder |
- |----------+---------------------------------------------|
- | Esc 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 |
- |----------+---------------------------------------------|
- | Esc 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 |
- |----------+---------------------------------------------|
- | Esc / | search-reverse |
- |----------+---------------------------------------------|
- | ^L | clear and redraw the screen |
- |----------+---------------------------------------------|
- | ^T | untag messages matching a pattern |
- +--------------------------------------------------------+
-
- 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 "flags" in Table 2.4, "Message status flags" may appear,
- some of which can be turned on or off using these functions: <set-flag>
- and <clear-flag> bound by default to "w" and "W" respectively.
-
- Furthermore, the flags in Table 2.5, "Message recipient flags" reflect who
- the message is addressed to. They can be customized with the $to_chars
- variable.
-
- Table 2.4. Message status flags
-
- +----------------------------------------------------------------------+
- | Flag | Description |
- |------+---------------------------------------------------------------|
- | D | message is deleted (is marked for deletion) |
- |------+---------------------------------------------------------------|
- | d | message has attachments marked for deletion |
- |------+---------------------------------------------------------------|
- | K | contains a PGP public key |
- |------+---------------------------------------------------------------|
- | N | message is new |
- |------+---------------------------------------------------------------|
- | O | message is old |
- |------+---------------------------------------------------------------|
- | P | message is PGP encrypted |
- |------+---------------------------------------------------------------|
- | r | message has been replied to |
- |------+---------------------------------------------------------------|
- | S | message is signed, and the signature is successfully verified |
- |------+---------------------------------------------------------------|
- | s | message is signed |
- |------+---------------------------------------------------------------|
- | ! | message is flagged |
- |------+---------------------------------------------------------------|
- | * | message is tagged |
- +----------------------------------------------------------------------+
-
- Table 2.5. Message recipient flags
-
- +----------------------------------------------------------+
- | Flag | Description |
- |------+---------------------------------------------------|
- | + | message is to you and you only |
- |------+---------------------------------------------------|
- | T | message is to you, but also to or cc'ed to others |
- |------+---------------------------------------------------|
- | C | message is cc'ed to you |
- |------+---------------------------------------------------|
- | F | message is from you |
- |------+---------------------------------------------------|
- | L | message is sent to a subscribed mailing list |
- +----------------------------------------------------------+
-
- 4.2. The Pager
-
- By default, Mutt uses its builtin pager to display the contents of
- messages. The pager is very similar to the Unix program less though not
- nearly as featureful.
-
- Table 2.6. Most common pager keys
-
- +------------------------------------------------------------------------+
- | Key | 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 keybindings |
- |----------+-------------------------------------------------------------|
- | / | regular expression search |
- |----------+-------------------------------------------------------------|
- | Esc / | backward regular expression search |
- |----------+-------------------------------------------------------------|
- | \ | toggle highlighting of search matches |
- |----------+-------------------------------------------------------------|
- | ^ | jump to the top of the message |
- +------------------------------------------------------------------------+
-
- In addition to key bindings in Table 2.6, "Most common pager keys", many
- of the functions from the index menu are also 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 for bold
- and underline. These sequences are a series of either the letter,
- backspace (^H), the letter again for bold or the letter, backspace, "_"
- for denoting underline. Mutt 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 translates them into the correct color and
- character settings. The sequences Mutt supports are:
-
- \e[Ps;Ps;..Ps;m
-
- where Ps can be one of the codes shown in Table 2.7, "ANSI escape
- sequences".
-
- Table 2.7. ANSI escape sequences
-
- +------------------------------------------------------------------------+
- | Escape code | Description |
- |-------------+----------------------------------------------------------|
- | 0 | All attributes off |
- |-------------+----------------------------------------------------------|
- | 1 | Bold on |
- |-------------+----------------------------------------------------------|
- | 4 | Underline on |
- |-------------+----------------------------------------------------------|
- | 5 | Blink on |
- |-------------+----------------------------------------------------------|
- | 7 | Reverse video on |
- |-------------+----------------------------------------------------------|
- | 3<color> | Foreground color is <color> (see Table 2.8, "Color |
- | | sequences") |
- |-------------+----------------------------------------------------------|
- | 4<color> | Background color is <color> (see Table 2.8, "Color |
- | | sequences") |
- +------------------------------------------------------------------------+
-
- Table 2.8. Color sequences
-
- +----------------------+
- | Color code | Color |
- |------------+---------|
- | 0 | Black |
- |------------+---------|
- | 1 | Red |
- |------------+---------|
- | 2 | Green |
- |------------+---------|
- | 3 | Yellow |
- |------------+---------|
- | 4 | Blue |
- |------------+---------|
- | 5 | Magenta |
- |------------+---------|
- | 6 | Cyan |
- |------------+---------|
- | 7 | White |
- +----------------------+
-
- Mutt uses these attributes for handling text/enriched messages, and they
- can also be used by an external autoview 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.
-
- Note
-
- Note that the search commands in the pager take regular expressions, which
- are not quite the same as the more complex patterns used by the search
- command in the index. This is because the pager only performs simple text
- search, whereas the index provides boolean filtering on several aspects of
- messages.
-
- 4.3. Threaded Mode
-
- When the mailbox is sorted by threads, there are a few additional
- functions available in the index and pager modes as shown in Table 2.9,
- "Most common thread mode keys".
-
- Table 2.9. Most common thread mode keys
-
- +------------------------------------------------------------------------+
- | Key | Function | Description |
- |-------+----------------------+-----------------------------------------|
- | ^D | <delete-thread> | delete all messages in the current |
- | | | thread |
- |-------+----------------------+-----------------------------------------|
- | ^U | <undelete-thread> | undelete all messages in the current |
- | | | thread |
- |-------+----------------------+-----------------------------------------|
- | ^N | <next-thread> | jump to the start of the next thread |
- |-------+----------------------+-----------------------------------------|
- | ^P | <previous-thread> | jump to the start of the previous |
- | | | thread |
- |-------+----------------------+-----------------------------------------|
- | ^R | <read-thread> | mark the current thread as read |
- |-------+----------------------+-----------------------------------------|
- | Esc d | <delete-subthread> | delete all messages in the current |
- | | | subthread |
- |-------+----------------------+-----------------------------------------|
- | Esc u | <undelete-subthread> | undelete all messages in the current |
- | | | subthread |
- |-------+----------------------+-----------------------------------------|
- | Esc n | <next-subthread> | jump to the start of the next subthread |
- |-------+----------------------+-----------------------------------------|
- | Esc p | <previous-subthread> | jump to the start of the previous |
- | | | subthread |
- |-------+----------------------+-----------------------------------------|
- | Esc r | <read-subthread> | mark the current subthread as read |
- |-------+----------------------+-----------------------------------------|
- | Esc t | <tag-thread> | toggle the tag on the current thread |
- |-------+----------------------+-----------------------------------------|
- | Esc v | <collapse-thread> | toggle collapse for the current thread |
- |-------+----------------------+-----------------------------------------|
- | Esc 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 on the screen. See %M in
- $index_format. For example, you could use "%?M?(#%03M)&(%4l)?" in
- $index_format to optionally display the number of hidden messages if the
- thread is collapsed.
-
- See also: $strict_threads.
-
- 4.4. Miscellaneous Functions
-
- In addition, the index and pager menus have these interesting functions:
-
- <create-alias> (default: a)
-
- Creates a new alias based upon the current message (or prompts for
- a new one). Once editing is complete, an alias command is added to
- the file specified by the $alias_file variable for future use
-
- Note
-
- Mutt does not read the $alias_file upon startup so you must
- explicitly source the file.
-
- <check-traditional-pgp> (default: Esc P)
-
- This function will search the current message for content signed
- or encrypted with PGP the "traditional" way, that is, without
- proper MIME tagging. Technically, this function will temporarily
- change the MIME content types of the body parts containing PGP
- data; this is similar to the <edit-type> function's effect.
-
- <edit> (default: e)
-
- This command (available in the index and pager) allows you to edit
- the raw current message as it's present in the mail folder. After
- you have finished editing, the changed message will be appended to
- the current folder, and the original message will be marked for
- deletion; if the message is unchanged it won't be replaced.
-
- <edit-type> (default: ^E on the attachment menu, and in the pager and
- index menus; ^T on the compose menu)
-
- This command is used to temporarily edit an attachment's content
- type to fix, for instance, bogus character set parameters. When
- invoked from the index or from the pager, you'll have the
- opportunity to edit the top-level attachment's content type. On
- the attachment menu, you can change any attachment's content type.
- These changes are not persistent, and get lost upon changing
- folders.
-
- Note that this command is also available on the compose menu.
- There, it's used to fine-tune the properties of attachments you
- are going to send.
-
- <enter-command> (default: ":")
-
- This command is used to execute any command you would normally put
- in a configuration file. A common use is to check the settings of
- variables, or in conjunction with macros to change settings on the
- fly.
-
- <extract-keys> (default: ^K)
-
- This command extracts PGP public keys from the current or tagged
- message(s) and adds them to your PGP public key ring.
-
- <forget-passphrase> (default: ^F)
-
- This command wipes the passphrase(s) from memory. It is useful, if
- you misspelled the passphrase.
-
- <list-reply> (default: L)
-
- Reply to the current or tagged message(s) by extracting any
- addresses which match the regular expressions given by the lists
- or subscribe commands, but also honor any Mail-Followup-To
- header(s) if the $honor_followup_to configuration variable is set.
- Using this when replying to messages posted to mailing lists helps
- avoid duplicate copies being sent to the author of the message you
- are replying to.
-
- <pipe-message> (default: |)
-
- Asks for an external Unix command and pipes the current or tagged
- message(s) to it. The variables $pipe_decode, $pipe_split,
- $pipe_sep and $wait_key control the exact behavior of this
- function.
-
- <resend-message> (default: Esc e)
-
- Mutt takes the current message as a template for a new message.
- This function is best described as "recall from arbitrary
- folders". It can conveniently be used to forward MIME messages
- while preserving the original mail structure. Note that the amount
- of headers included here depends on the value of the $weed
- variable.
-
- This function is also available from the attachment menu. You can
- use this to easily resend a message which was included with a
- bounce message as a message/rfc822 body part.
-
- <shell-escape> (default: !)
-
- Asks for an external Unix command and executes it. The $wait_key
- can be used to control whether Mutt 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. If no command is given, an interactive shell is
- executed.
-
- <toggle-quoted> (default: T)
-
- The pager uses the $quote_regexp variable to detect quoted text
- when displaying the body of the message. This function toggles the
- display of the quoted material in the message. It is particularly
- useful when being interested in just the response and there is a
- large amount of quoted text in the way.
-
- <skip-quoted> (default: S)
-
- This function will go to the next line of non-quoted text which
- comes after a line of quoted text in the internal pager.
-
-5. Sending Mail
-
- 5.1. Introduction
-
- The bindings shown in Table 2.10, "Most common mail sending keys" are
- available in the index and pager to start a new message.
-
- Table 2.10. Most common mail sending keys
-
- +----------------------------------------------------------+
- | 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 |
- |-------+---------------+----------------------------------|
- | Esc k | <mail-key> | mail a PGP public key to someone |
- +----------------------------------------------------------+
-
- Bouncing a message sends the message as-is to the recipient you specify.
- Forwarding a message allows you to add comments or modify the message you
- are forwarding. These items are discussed in greater detail in the next
- chapter "Forwarding and Bouncing Mail."
-
- Mutt will then enter the compose menu and prompt you for the recipients to
- place on the "To:" header field. Next, it will ask you for the "Subject:"
- field for the message, providing a default if you are replying to or
- forwarding a message. See also $askcc, $askbcc, $autoedit, $bounce,
- $fast_reply, and $include for changing how Mutt asks these questions.
-
- Mutt will then automatically start your $editor on the message body. If
- the $edit_headers variable is set, the headers will be at the top of the
- message in your editor. Any messages you are replying to will be added in
- sort order to the message, with appropriate $attribution, $indent_string
- and $post_indent_string. When forwarding a message, if the $mime_forward
- variable is unset, a copy of the forwarded message will be included. If
- you have specified a $signature, it will be appended to the message.
-
- Once you have finished editing the body of your mail message, you are
- returned to the compose menu providing the functions shown in Table 2.11,
- "Most common compose menu keys" to modify, send or postpone the message.
-
- Table 2.11. Most common compose menu keys
-
- +------------------------------------------------------------------------+
- | Key | Function | Description |
- |-------+---------------------+------------------------------------------|
- | a | <attach-file> | attach a file |
- |-------+---------------------+------------------------------------------|
- | A | <attach-message> | attach message(s) to the message |
- |-------+---------------------+------------------------------------------|
- | Esc 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 |
- |-------+---------------------+------------------------------------------|
- | Esc 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) |
- |-------+---------------------+------------------------------------------|
- | ^F | <forget-passphrase> | wipe passphrase(s) from memory |
- +------------------------------------------------------------------------+
-
- The compose menu is also used to edit the attachments for a message which
- can be either files or other messages. The <attach-message> function to
- will prompt you for a folder to attach messages from. You can now tag
- messages in that folder and they will be attached to the message you are
- sending.
-
- Note
-
- Note that certain operations 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.
-
- 5.2. Editing the message header
-
- When editing the header because of $edit_headers being set, there are a
- several pseudo headers available which will not be included in sent
- messages.
-
- 5.2.1. Fcc: pseudo header
-
- If you specify Fcc: filename as a header, Mutt will pick up filename just
- as if you had used the <edit-fcc> function in the compose menu.
-
- 5.2.2. Attach: pseudo header
-
- You can also attach files to your message by specifying Attach: filename [
- description ] where filename is the file to attach and description is an
- optional string to use as the description of the attached file.
-
- 5.2.3. Pgp: pseudo header
-
- If you want to use PGP, you can specify
-
- Pgp: [ E | S | S<id> ]
-
- "E" selects encryption, "S" selects signing and "S<id>" selects signing
- with the given key, setting $pgp_sign_as permanently.
-
- 5.2.4. In-Reply-To: header
-
- When replying to messages, the In-Reply-To: header contains the Message-Id
- of the message(s) you reply to. If you remove its value, Mutt will not
- generate a References: field, which allows you to create a new message
- thread, for example to create a new message to a mailing list without
- having to enter the mailing list's address.
-
- 5.3. Sending cryptographically signed/encrypted messages
-
- If you have told mutt to PGP or S/MIME encrypt a message, it will guide
- you through a key selection process when you try to send the message. Mutt
- will not ask you any questions about keys which have a certified user ID
- matching one of the message recipients' mail addresses. However, there may
- be situations in which there are several keys, weakly certified user ID
- fields, or where no matching keys can be found.
-
- In these cases, you are dropped into a menu with a list of keys from which
- you can select one. When you quit this menu, or mutt can't find any
- matching keys, you are prompted for a user ID. You can, as usually, abort
- this prompt using ^G. When you do so, mutt will return to the compose
- screen.
-
- Once you have successfully finished the key selection, the message will be
- encrypted using the selected public keys when sent out.
-
- Most fields of the entries in the key selection menu (see also
- $pgp_entry_format) have obvious meanings. But some explanations on the
- capabilities, flags, and validity fields are in order.
-
- The flags sequence (%f) will expand to one of the flags in Table 2.12,
- "PGP key menu flags".
-
- Table 2.12. PGP key menu flags
-
- +-----------------------------------------------------------+
- | Flag | Description |
- |------+----------------------------------------------------|
- | R | The key has been revoked and can't be used. |
- |------+----------------------------------------------------|
- | X | The key is expired and can't be used. |
- |------+----------------------------------------------------|
- | d | You have marked the key as disabled. |
- |------+----------------------------------------------------|
- | c | There are unknown critical self-signature packets. |
- +-----------------------------------------------------------+
-
- The capabilities field (%c) expands to a two-character sequence
- representing a key's capabilities. The first character gives the key's
- encryption capabilities: A minus sign ("-") means that the key cannot be
- used for encryption. A dot (".") means that it's marked as a signature key
- in one of the user IDs, but may also be used for encryption. The letter
- "e" indicates that this key can be used for encryption.
-
- The second character indicates the key's signing capabilities. Once again,
- a "-" implies "not for signing", "." implies that the key is marked as an
- encryption key in one of the user-ids, and "s" denotes a key which can be
- used for signing.
-
- Finally, the validity field (%t) indicates how well-certified a user-id
- is. A question mark ("?") indicates undefined validity, a minus character
- ("-") marks an untrusted association, a space character means a partially
- trusted association, and a plus character ("+") indicates complete
- validity.
-
- 5.4. Sending anonymous messages via mixmaster
-
- You may also have compiled mutt to co-operate with Mixmaster, an anonymous
- remailer. Mixmaster permits you to send your messages anonymously using a
- chain of remailers. Mixmaster support in mutt is for mixmaster version
- 2.04 (beta 45 appears to be the latest) and 2.03. It does not support
- earlier versions or the later so-called version 3 betas, of which the
- latest appears to be called 2.9b23.
-
- To use it, you'll have to obey certain restrictions. Most important, you
- cannot use the Cc and Bcc headers. To tell Mutt to use mixmaster, you have
- to select a remailer chain, using the mix function on the compose menu.
-
- The chain selection screen is divided into two parts. In the (larger)
- upper part, you get a list of remailers you may use. In the lower part,
- you see the currently selected chain of remailers.
-
- You can navigate in the chain using the <chain-prev> and <chain-next>
- functions, which are by default bound to the left and right arrows and to
- the h and l keys (think vi keyboard bindings). To insert a remailer at the
- current chain position, use the <insert> function. To append a remailer
- behind the current chain position, use <select-entry> or <append>. You can
- also delete entries from the chain, using the corresponding function.
- Finally, to abandon your changes, leave the menu, or <accept> them
- pressing (by default) the Return key.
-
- Note that different remailers do have different capabilities, indicated in
- the %c entry of the remailer menu lines (see $mix_entry_format). Most
- important is the "middleman" capability, indicated by a capital "M": This
- means that the remailer in question cannot be used as the final element of
- a chain, but will only forward messages to other mixmaster remailers. For
- details on the other capabilities, please have a look at the mixmaster
- documentation.
-
- 5.5. Sending format=flowed messages
-
- 5.5.1. Concept
-
- format=flowed-style messages (or f=f for short) are text/plain messages
- that consist of paragraphs which a receiver's mail client may reformat to
- its own needs which mostly means to customize line lengths regardless of
- what the sender sent. Technically this is achieved by letting lines of a
- "flowable" paragraph end in spaces except for the last line.
-
- While for text-mode clients like mutt it's the best way to assume only a
- standard 80x25 character cell terminal, it may be desired to let the
- receiver decide completely how to view a message.
-
- 5.5.2. Mutt support
-
- Mutt only supports setting the required format=flowed MIME parameter on
- outgoing messages if the $text_flowed variable is set, specifically it
- does not add the trailing spaces.
-
- After editing the initial message text and before entering the compose
- menu, mutt properly space-stuffes the message. Space-stuffing is required
- by RfC3676 defining format=flowed and means to prepend a space to:
-
- o all lines starting with a space
-
- o lines starting with the word "From" followed by space
-
- o all lines starting with ">" which is not intended to be a quote
- character
-
- Note
-
- Mutt only supports space-stuffing for the first two types of lines but not
- for the third: It is impossible to safely detect whether a leading >
- character starts a quote or not. Furthermore, Mutt only applies
- space-stuffing once after the initial edit is finished.
-
- All leading spaces are to be removed by receiving clients to restore the
- original message prior to further processing.
-
- 5.5.3. Editor considerations
-
- As mutt provides no additional features to compose f=f messages, it's
- completely up to the user and his editor to produce proper messages.
- Please consider your editor's documentation if you intend to send f=f
- messages.
-
- Please note that when editing messages from the compose menu several times
- before really sending a mail, it's up to the user to ensure that the
- message is properly space-stuffed.
-
- For example, vim provides the w flag for its formatoptions setting to
- assist in creating f=f messages, see :help fo-table for details.
-
-6. Forwarding and Bouncing Mail
-
- Bouncing and forwarding let you send an existing message to recipients
- that you specify. Bouncing a message sends a verbatim copy of a message to
- alternative addresses as if they were the message's original recipients
- specified in the Bcc header. Forwarding a message, on the other hand,
- allows you to modify the message before it is resent (for example, by
- adding your own comments). Bouncing is done using the <bounce> function
- and forwarding using the <forward> function bound to "b" and "f"
- respectively.
-
- Forwarding can be done by including the original message in the new
- message's body (surrounded by indicating lines) or including it as a MIME
- attachment, depending on the value of the $mime_forward variable. Decoding
- of attachments, like in the pager, can be controlled by the
- $forward_decode and $mime_forward_decode variables, respectively. The
- desired forwarding format may depend on the content, therefore
- $mime_forward is a quadoption which, for example, can be set to "ask-no".
-
- The inclusion of headers is controlled by the current setting of the $weed
- variable, unless $mime_forward is set.
-
- Editing the message to forward follows the same procedure as sending or
- replying to a message does.
-
-7. Postponing Mail
-
- At times it is desirable to delay sending a message that you have already
- begun to compose. When the <postpone-message> function is used in the
- compose menu, the body of your message and attachments are stored in the
- mailbox specified by the $postponed variable. This means that you can
- recall the message even if you exit Mutt and then restart it at a later
- time.
-
- Once a message is postponed, there are several ways to resume it. From the
- command line you can use the "-p" option, or if you compose a new message
- from the index or pager you will be prompted if postponed messages exist.
- If multiple messages are currently postponed, the postponed menu will pop
- up and you can select which message you would like to resume.
-
- Note
-
- If you postpone a reply to a message, the reply setting of the message is
- only updated when you actually finish the message and send it. Also, you
- must be in the same folder with the message you replied to for the status
- of the message to be updated.
-
- See also the $postpone quad-option.
-
-Chapter 3. Configuration
-
- Table of Contents
-
- 1. Location of initialization files
-
- 2. Syntax of Initialization Files
-
- 3. Address groups
-
- 4. Defining/Using aliases
-
- 5. Changing the default key bindings
-
- 6. Defining aliases for character sets
-
- 7. Setting variables based upon mailbox
-
- 8. Keyboard macros
-
- 9. Using color and mono video attributes
-
- 10. Message header display
-
- 11. Alternative addresses
-
- 12. Mailing lists
-
- 13. Using Multiple spool mailboxes
-
- 14. Monitoring incoming mail
-
- 15. User defined headers
-
- 16. Specify default save mailbox
-
- 17. Specify default Fcc: mailbox when composing
-
- 18. Specify default save filename and default Fcc: mailbox at once
-
- 19. Change settings based upon message recipients
-
- 20. Change settings before formatting a message
-
- 21. Choosing the cryptographic key of the recipient
-
- 22. Adding key sequences to the keyboard buffer
-
- 23. Executing functions
-
- 24. Message Scoring
-
- 25. Spam detection
-
- 26. Setting and Querying Variables
-
- 26.1. Commands
-
- 26.2. User-defined variables
-
- 27. Reading initialization commands from another file
-
- 28. Configuring features conditionnaly
-
- 29. Removing hooks
-
- 30. Format Strings
-
- 30.1. Basic usage
-
- 30.2. Filters
-
-1. Location of initialization files
-
- While the default configuration (or "preferences") make Mutt usable right
- out of the box, it is often desirable to tailor Mutt to suit your own
- tastes. When Mutt is first invoked, it will attempt to read the "system"
- configuration file (defaults set by your local system administrator),
- unless the "-n" command line option is specified. This file is typically
- /usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt will next look for a
- file named .muttrc in your home directory. If this file does not exist and
- your home directory has a subdirectory named .mutt, mutt try to load a
- file named .mutt/muttrc.
-
- .muttrc is the file where you will usually place your commands to
- configure Mutt.
-
- In addition, mutt supports version specific configuration files that are
- parsed instead of the default files as explained above. For instance, if
- your system has a Muttrc-0.88 file in the system configuration directory,
- and you are running version 0.88 of mutt, this file will be sourced
- instead of the Muttrc file. The same is true of the user configuration
- file, if you have a file .muttrc-0.88.6 in your home directory, when you
- run mutt version 0.88.6, it will source this file instead of the default
- .muttrc file. The version number is the same which is visible using the
- "-v" command line switch or using the show-version key (default: V) from
- the index menu.
-
-2. Syntax of Initialization Files
-
- An initialization file consists of a series of commands. Each line of the
- file may contain one or more commands. When multiple commands are used,
- they must be separated by a semicolon (;).
-
- Example 3.1. Multiple configuration commands per line
-
- set realname='Mutt 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,
-
- Example 3.2. Commenting configuration files
-
- 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, backticks are evaluated inside of double quotes,
- but not for single quotes.
-
- \ quotes the next character, just as in shells such as bash and zsh. For
- example, if want to put quotes """ inside of a string, you can use "\" to
- force the next character to be a literal instead of interpreted character.
-
- Example 3.3. Escaping quotes in congfiguration files
-
- set realname="Michael \"MuttDude\" Elkins"
-
- "\\" means to insert a literal "\" into the line. "\n" and "\r" have their
- usual C meanings of linefeed and carriage-return, respectively.
-
- A \ at the end of a line can be used to split commands over multiple
- lines, provided that the split points don't appear in the middle of
- command names.
-
- It is also possible to substitute the output of a Unix command in an
- initialization file. This is accomplished by enclosing the command in
- backticks (``). For example,
-
- Example 3.4. Using external command's output in configuration files
-
- my_hdr X-Operating-System: `uname -a`
-
- The output of the Unix command "uname -a" will be substituted before the
- line is parsed.
-
- Note
-
- Since initialization files are line oriented, only the first line of
- output from the Unix command will be substituted.
-
- Both environment variables and mutt variables can be accessed by
- prepending "$" to the name of the variable. For example,
-
- Example 3.5. Using environment variables in configuration files
-
- set record=+sent_on_$HOSTNAME
-
- will cause mutt to save outgoing messages to a folder named
- "sent_on_kremvax" if the environment variable HOSTNAME is set to
- "kremvax." (See $record for details.)
-
- Mutt expands the variable when it is assigned, not when it is used. If the
- value of a variable on the right-hand side of an assignment changes after
- the assignment, the variable on the left-hand side will not be affected.
-
- The commands understood by mutt are explained in the next paragraphs. For
- a complete list, see the command reference.
-
- All configuration files are expected to be in the current locale as
- specified by the $charset variable which doesn't have a default value
- since it's determined by Mutt at startup. If a configuration file is not
- encoded in the same character set the $config_charset variable should be
- used: all lines starting with the next are recoded from $config_charset to
- $charset.
-
- This mechanism should be avoided if possible as it has the following
- implications:
-
- o These variables should be set early in a configuration file with
- $charset preceding $config_charset so Mutt know what character set to
- convert to.
-
- o If $config_charset is set, it should be set in each configuration file
- because the value is global and not per configuration file.
-
- o Because Mutt first recodes a line before it attempts to parse it, a
- conversion introducing question marks or other characters as part of
- errors (unconvertable characters, transliteration) may introduce
- syntax errors or silently change the meaning of certain tokens (e.g.
- inserting question marks into regular expressions).
-
-3. Address groups
-
- Usage:
-
- group [ -group name ...] { -rx expr ... | -addr expr ... }
-
- ungroup [ -group name ...] { * | -rx expr ... | -addr expr ... }
-
- group is used to directly add either addresses or regular expressions to
- the specified group or groups. The different categories of arguments to
- the group command can be in any order. The flags -rx and -addr specify
- what the following strings (that cannot begin with a hyphen) should be
- interpreted as: either a regular expression or an email address,
- respectively.
-
- These address groups can also be created implicitly by the alias, lists,
- subscribe and alternates commands by specifying the optional -group
- option.
-
- Once defined, these address groups can be used in patterns to search for
- and limit the display to messages matching a group.
-
- ungroup is used to remove addresses or regular expressions from the
- specified group or groups. The syntax is similar to the group command,
- however the special character * can be used to empty a group of all of its
- contents.
-
-4. Defining/Using aliases
-
- Usage:
-
- alias [ -group name ...] key address [ address ...]
-
- It's usually very cumbersome to remember or type out the address of
- someone you are communicating with. Mutt allows you to create "aliases"
- which map a short string to a full address.
-
- Note
-
- If you want to create an alias for more than one address, you must
- separate the addresses with a comma (",").
-
- The optional -group argument to alias causes the aliased address(es) to be
- added to the named group.
-
- To remove an alias or aliases ("*" means all aliases):
-
- unalias [ -group name ...] { * | key ... }
-
- alias muttdude me@cs.hmc.edu (Michael Elkins)
- alias theguys manny, moe, jack
-
- Unlike other mailers, Mutt 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 sourced. Consequently, you can have multiple
- alias files, or you can have all aliases defined in your muttrc.
-
- On the other hand, the <create-alias> function can use only one file, the
- one pointed to by the $alias_file variable (which is ~/.muttrc by
- default). This file is not special either, in the sense that Mutt 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:
-
- Example 3.6. Configuring external alias files
-
- source /usr/local/share/Mutt.aliases
- source ~/.mail_aliases
- set alias_file=~/.mail_aliases
-
- To use aliases, you merely use the alias at any place in mutt where mutt
- prompts 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
- $edit_headers variable set.
-
- In addition, at the various address prompts, you can use the tab character
- to expand a partial alias to the full alias. If there are multiple
- matches, mutt will bring up a menu with the matching aliases. In order to
- be presented with the full list of aliases, you must hit tab with out a
- partial alias, such as at the beginning of the prompt or after a comma
- denoting multiple addresses.
-
- In the alias menu, you can select as many aliases as you want with the
- select-entry key (default: <Return>), and use the exit key (default: q) to
- return to the address prompt.
-
-5. Changing the default key bindings
-
- Usage:
-
- bind map key function
-
- This command allows you to change the default key bindings (operation
- invoked when pressing a key).
-
- map specifies in which menu the binding belongs. Multiple maps may be
- specified by separating them with commas (no additional whitespace is
- allowed). The currently defined maps are:
-
- generic
-
- This is not a real menu, but is used as a fallback for all of the
- other menus except for the pager and editor modes. If a key is not
- defined in another menu, Mutt will look for a binding to use in
- this menu. This allows you to bind a key to a certain function in
- multiple menus instead of having multiple bind statements to
- accomplish the same task.
-
- alias
-
- The alias menu is the list of your personal aliases as defined in
- your muttrc. It is the mapping from a short alias name to the full
- email address(es) of the recipient(s).
-
- attach
-
- The attachment menu is used to access the attachments on received
- messages.
-
- browser
-
- The browser is used for both browsing the local directory
- structure, and for listing all of your incoming mailboxes.
-
- editor
-
- The editor is the line-based editor the user enters text data.
-
- index
-
- The index is the list of messages contained in a mailbox.
-
- compose
-
- The compose menu is the screen used when sending a new message.
-
- pager
-
- The pager is the mode used to display message/attachment data, and
- help listings.
-
- pgp
-
- The pgp menu is used to select the OpenPGP keys used to encrypt
- outgoing messages.
-
- smime
-
- The smime menu is used to select the OpenSSL certificates used to
- encrypt outgoing messages.
-
- postpone
-
- The postpone menu is similar to the index menu, except is used
- when recalling a message the user was composing, but saved until
- later.
-
- query
-
- The query menu is the browser for results returned by
- $query_command.
-
- mix
-
- The mixmaster screen is used to select remailer options for
- outgoing messages (if Mutt is compiled with Mixmaster support).
-
- key is the key (or key sequence) you wish to bind. To specify a control
- character, use the sequence \Cx, where x is the letter of the control
- character (for example, to specify control-A use "\Ca"). Note that the
- case of x as well as \C is ignored, so that \CA, \Ca, \cA and \ca are all
- equivalent. An alternative form is to specify the key as a three digit
- octal number prefixed with a "\" (for example \177 is equivalent to \c?).
- In addition, key may be a symbolic name as shown in Table 3.1, "Symbolic
- key names".
-
- Table 3.1. Symbolic key names
-
- +-------------------------------------+
- | Symbolic name | Meaning |
- |---------------+---------------------|
- | \t | tab |
- |---------------+---------------------|
- | <tab> | tab |
- |---------------+---------------------|
- | <backtab> | backtab / shift-tab |
- |---------------+---------------------|
- | \r | carriage return |
- |---------------+---------------------|
- | \n | newline |
- |---------------+---------------------|
- | \e | escape |
- |---------------+---------------------|
- | <esc> | escape |
- |---------------+---------------------|
- | <up> | up arrow |
- |---------------+---------------------|
- | <down> | down arrow |
- |---------------+---------------------|
- | <left> | left arrow |
- |---------------+---------------------|
- | <right> | right arrow |
- |---------------+---------------------|
- | <pageup> | Page Up |
- |---------------+---------------------|
- | <pagedown> | Page Down |
- |---------------+---------------------|
- | <backspace> | Backspace |
- |---------------+---------------------|
- | <delete> | Delete |
- |---------------+---------------------|
- | <insert> | Insert |
- |---------------+---------------------|
- | <enter> | Enter |
- |---------------+---------------------|
- | <return> | Return |
- |---------------+---------------------|
- | <home> | Home |
- |---------------+---------------------|
- | <end> | End |
- |---------------+---------------------|
- | <space> | Space bar |
- |---------------+---------------------|
- | <f1> | function key 1 |
- |---------------+---------------------|
- | <f10> | function key 10 |
- +-------------------------------------+
-
- key does not need to be enclosed in quotes unless it contains a space ("
- ") or semi-colon (";").
-
- function specifies which action to take when key is pressed. For a
- complete list of functions, see the reference. The special function <noop>
- unbinds the specified key sequence.
-
-6. Defining aliases for character sets
-
- Usage:
-
- charset-hook alias charset
-
- iconv-hook charset local-charset
-
- The charset-hook command defines an alias for a character set. This is
- useful to properly display messages which are tagged with a character set
- name not known to mutt.
-
- The iconv-hook command defines a system-specific name for a character set.
- This is helpful when your systems character conversion library insists on
- using strange, system-specific names for character sets.
-
-7. Setting variables based upon mailbox
-
- Usage:
-
- folder-hook [!]regexp command
-
- It is often desirable to change settings based on which mailbox you are
- reading. The folder-hook command provides a method by which you can
- execute any configuration command. regexp is a regular expression
- specifying in which mailboxes to execute command before loading. If a
- mailbox matches multiple folder-hook's, they are executed in the order
- given in the muttrc.
-
- Note
-
- If you use the "!" shortcut for $spoolfile at the beginning of the
- pattern, you must place it inside of double or single quotes in order to
- distinguish it from the logical not operator for the expression.
-
- Note
-
- Settings are not restored when you leave the mailbox. For example, a
- command action to perform is to change the sorting method based upon the
- mailbox being read:
-
- folder-hook mutt set sort=threads
-
- However, the sorting method is not restored to its previous value when
- reading a different mailbox. To specify a default command, use the pattern
- "." before other folder-hooks adjusting a value on a per-folder basis
- because folder-hooks are evaluated in the order given in the configuration
- file. The following example will set the sort variable to date-sent for
- all folders but to threads for all folders containing "mutt" in their
- name.
-
- Example 3.7. Setting sort method based on mailbox name
-
- folder-hook . set sort=date-sent
- folder-hook mutt set sort=threads
-
-8. Keyboard macros
-
- Usage:
-
- macro menu key sequence [ description ]
-
- Macros are useful when you would like a single key to perform a series of
- actions. When you press key in menu menu, Mutt 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 single key or fewer
- keys.
-
- menu is the map which the macro will be bound in. Multiple maps may be
- specified by separating multiple menu arguments by commas. Whitespace may
- not be used in between the menu arguments and the commas separating them.
-
- key and sequence are expanded by the same rules as the key bindings with
- some additions. The first is that control characters in sequence can also
- be specified as ^x. In order to get a caret ("^") you need to use ^^.
- 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 key bindings. Functions are listed
- in the reference.
-
- The advantage with using function names directly is that the macros will
- work regardless of the current key bindings, so they are not dependent on
- the user having particular key definitions. This makes them more robust
- and portable, and also facilitates defining of macros in files used by
- more than one user (e.g., the system Muttrc).
-
- Optionally you can specify a descriptive text after sequence, which is
- shown in the help screens.
-
- Note
-
- Macro definitions (if any) listed in the help screen(s), are silently
- truncated at the screen width, and are not wrapped.
-
-9. Using color and mono video attributes
-
- Usage:
-
- color object foreground background
-
- color { header | body } foreground background regexp
-
- color index foreground background pattern
-
- uncolor index { * | pattern ... }
-
- If your terminal supports color, you can spice up Mutt 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).
-
- header and body match regexp in the header/body of a message, index
- matches pattern (see Section 2, "Patterns: Searching, Limiting and
- Tagging") in the message index.
-
- object can be one of:
-
- o attachment
-
- o bold (hiliting bold patterns in the body of messages)
-
- o error (error messages printed by Mutt)
-
- o hdrdefault (default color of the message header in the pager)
-
- o indicator (arrow or bar used to indicate the current item in a menu)
-
- o markers (the "+" markers at the beginning of wrapped lines in the
- pager)
-
- o message (informational messages)
-
- o normal
-
- o quoted (text matching $quote_regexp in the body of a message)
-
- o quoted1, quoted2, ..., quotedN (higher levels of quoting)
-
- o search (hiliting of words in the pager)
-
- o signature
-
- o status (mode lines used to display info about the mailbox or message)
-
- o tilde (the "~" used to pad blank lines in the pager)
-
- o tree (thread tree drawn in the message index and attachment menu)
-
- o underline (hiliting underlined patterns in the body of messages)
-
- foreground and background can be one of the following:
-
- o white
-
- o black
-
- o green
-
- o magenta
-
- o blue
-
- o cyan
-
- o yellow
-
- o red
-
- o default
-
- o colorx
-
- foreground can optionally be prefixed with the keyword bright to make the
- foreground color boldfaced (e.g., brightred).
-
- If your terminal supports it, the special keyword default can be used as a
- transparent color. The value brightdefault is also valid. If Mutt is
- linked against the S-Lang library, you also need to set the COLORFGBG
- environment variable to the default colors of your terminal for this to
- work; for example (for Bourne-like shells):
-
- set COLORFGBG="green;black"
- export COLORFGBG
-
- Note
-
- The S-Lang library requires you to use the lightgray and brown keywords
- instead of white and yellow when setting this variable.
-
- Note
-
- The uncolor command can be applied to the index object only. It removes
- entries from the list. You must specify the same pattern specified in the
- color command for it to be removed. The pattern "*" is a special token
- which means to clear the color index list of all entries.
-
- Mutt also recognizes the keywords color0, color1, ..., colorN-1 (N being
- the number of colors supported by your terminal). This is useful when you
- remap the colors for your display (for example by changing the color
- associated with color2 for your xterm), since color names may then lose
- their normal meaning.
-
- If your terminal does not support color, it is still possible change the
- video attributes through the use of the "mono" command:
-
- Usage:
-
- mono object attribute
-
- mono { header | body } attribute regexp
-
- mono index attribute pattern
-
- unmono index { * | pattern ... }
-
- For object, see the color command. attribute can be one of the following:
-
- o none
-
- o bold
-
- o underline
-
- o reverse
-
- o standout
-
-10. Message header display
-
- Usage:
-
- ignore pattern [ pattern ...]
-
- unignore { * | pattern ... }
-
- Messages often have many header fields added by automatic processing
- systems, or which may not seem useful to display on the screen. This
- command allows you to specify header fields which you don't normally want
- to see in the pager.
-
- You do not need to specify the full header field name. For example,
- "ignore content-" will ignore all header fields that begin with the
- pattern "content-". "ignore *" will ignore all headers.
-
- To remove a previously added token from the list, use the "unignore"
- command. The "unignore" command will make Mutt display headers with the
- given pattern. For example, if you do "ignore x-" it is possible to
- "unignore x-mailer".
-
- "unignore *" will remove all tokens from the ignore list.
-
- For example:
-
- Example 3.8. Header weeding
-
- # 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:
-
- Usage:
-
- hdr_order header [ header ...]
-
- unhdr_order { * | header ... }
-
- With the hdr_order command you can specify an order in which mutt will
- attempt to present these headers to you when viewing messages.
-
- "unhdr_order *" will clear all previous headers from the order list, thus
- removing the header order effects set by the system-wide startup file.
-
- Example 3.9. Configuring header display order
-
- hdr_order From Date: From: To: Cc: Subject:
-
-11. Alternative addresses
-
- Usage:
-
- alternates [ -group name ...] regexp [ regexp ...]
-
- unalternates [ -group name ...] { * | regexp ... }
-
- With various functions, mutt will treat messages differently, depending on
- whether you sent them or whether you received them from someone else. For
- instance, when replying to a message that you sent to a different party,
- mutt will automatically suggest to send the response to the original
- message's recipients -- responding to yourself won't make much sense in
- many cases. (See $reply_to.)
-
- Many users receive e-mail under a number of different addresses. To fully
- use mutt's features here, the program must be able to recognize what
- e-mail addresses you receive mail under. That's the purpose of the
- alternates command: It takes a list of regular expressions, each of which
- can identify an address under which you receive e-mail.
-
- As addresses are matched using regular expressions and not exact strict
- comparisons, you should make sure you specify your addresses as precise as
- possible to avoid mismatches. For example, if you specify:
-
- alternates user@example
-
- mutt will consider "some-user@example" as being your address, too which
- may not be desired. As a solution, in such cases addresses should be
- specified as:
-
- alternates '^user@example$'
-
- The -group flag causes all of the subsequent regular expressions to be
- added to the named group.
-
- The unalternates command can be used to write exceptions to alternates
- patterns. If an address matches something in an alternates command, but
- you nonetheless do not think it is from you, you can list a more precise
- pattern under an unalternates command.
-
- To remove a regular expression from the alternates list, use the
- unalternates command with exactly the same regexp. Likewise, if the regexp
- for an alternates command matches an entry on the unalternates list, that
- unalternates entry will be removed. If the regexp for unalternates is "*",
- all entries on alternates will be removed.
-
-12. Mailing lists
-
- Usage:
-
- lists [ -group name ...] regexp [ regexp ...]
-
- unlists [ -group name ...] { * | regexp ... }
-
- subscribe [ -group name ...] regexp [ regexp ...]
-
- unsubscribe [ -group name ...] { * | regexp ... }
-
- Mutt has a few nice features for handling mailing 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
-
- 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 maintains lists of patterns for the addresses of
- known and subscribed mailing lists. Every subscribed mailing list is
- known. To mark a mailing list as known, use the "lists" command. To mark
- it as subscribed, use "subscribe".
-
- You can use regular expressions with both commands. To mark all messages
- sent to a specific bug report's address on mutt's bug tracking system as
- list mail, for instance, you could say "subscribe [0-9]*@bugs.guug.de".
- Often, it's sufficient to just give a portion of the list's e-mail
- address.
-
- Specify as much of the address as you need to to remove ambiguity. For
- example, if you've subscribed to the Mutt mailing list, you will receive
- mail addressed to mutt-users@mutt.org. So, to tell Mutt that this is a
- mailing list, you could add "lists mutt-users@" to your initialization
- file. To tell mutt that you are subscribed to it, add "subscribe
- mutt-users" to your initialization file instead. If you also happen to get
- mail from someone whose address is mutt-users@example.com, you could use
- "lists ^mutt-users@mutt\\.org$" or "subscribe ^mutt-users@mutt\\.org$" to
- match only mail from the actual list.
-
- The -group flag adds all of the subsequent regular expressions to the
- named group.
-
- 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".
-
-13. Using Multiple spool mailboxes
-
- Usage:
-
- mbox-hook [!]pattern mailbox
-
- This command is used to move read messages from a specified mailbox to a
- different mailbox automatically when you quit or change folders. pattern
- is a regular expression specifying the mailbox to treat as a "spool"
- mailbox and mailbox specifies where mail should be saved when read.
-
- Unlike some of the other hook commands, only the first matching pattern is
- used (it is not possible to save read mail in more than a single mailbox).
-
-14. Monitoring incoming mail
-
- Usage:
-
- mailboxes mailbox [ mailbox ...]
-
- unmailboxes { * | mailbox ... }
-
- This command specifies folders which can receive mail and which will be
- checked for new messages periodically.
-
- folder can either be a local file or directory (Mbox/Mmdf or Maildir/Mh).
- If Mutt was built with POP and/or IMAP support, folder can also be a
- POP/IMAP folder URL. The URL syntax is described in Section 1.2, "URL
- syntax", POP and IMAP are described in Section 3, "POP3 Support" and
- Section 4, "IMAP Support" respectively.
-
- Mutt provides a number of advanced features for handling (possibly many)
- folders and new mail within them, please refer to Section 9, "Handling
- multiple folders" for details (including in what situations and how often
- Mutt checks for new mail).
-
- The "unmailboxes" command is used to remove a token from the list of
- folders which receive mail. Use "unmailboxes *" to remove all tokens.
-
- Note
-
- The folders in the mailboxes command are resolved when the command is
- executed, so if these names contain shortcut characters (such as "=" and
- "!"), any variable definition that affects these characters (like $folder
- and $spoolfile) should be set before the mailboxes command. If none of
- these shorcuts are used, a local path should be absolute as otherwise mutt
- tries to find it relative to the directory from where mutt was started
- which may not always be desired.
-
- For Mbox and Mmdf folders, new mail is detected by comparing access and/or
- modification times of files: Mutt assumes a folder has new mail if it
- wasn't accessed after it was last modified. Utilities like biff or frm or
- any other program which accesses the mailbox might cause Mutt to never
- detect new mail for that mailbox if they do not properly reset the access
- time. Other possible causes of Mutt not detecting new mail in these
- folders are backup tools (updating access times) or filesystems mounted
- without access time update support.
-
- In cases where new mail detection for Mbox or Mmdf folders appears to be
- unreliable, the $check_mbox_size option can be used to make Mutt track and
- consult file sizes for new mail detection instead.
-
-15. User defined headers
-
- Usage:
-
- my_hdr string
-
- unmy_hdr { * | field ... }
-
- The my_hdr command allows you to create your own header fields which will
- be added to every message you send.
-
- For example, if you would like to add an "Organization:" header field to
- all of your outgoing messages, you can put the command
-
- Example 3.10. Defining custom headers
-
- my_hdr Organization: A Really Big Company, Anytown, USA
-
- in your .muttrc.
-
- Note
-
- Space characters are not allowed between the keyword and the colon (":").
- The standard for electronic mail (RFC2822) says that space is illegal
- there, so Mutt enforces the rule.
-
- If you would like to add a header field to a single message, you should
- either set the $edit_headers variable, or use the <edit-headers> function
- (default: "E") in the compose menu so that you can edit the header of your
- message along with the body.
-
- To remove user defined header fields, use the unmy_hdr command. You may
- specify an asterisk ("*") to remove all header fields, or the fields to
- remove. For example, to remove all "To" and "Cc" header fields, you could
- use:
-
- unmy_hdr to cc
-
-16. Specify default save mailbox
-
- Usage:
-
- save-hook [!]pattern mailbox
-
- This command is used to override the default mailbox used when saving
- messages. mailbox will be used as the default if the message matches
- pattern, see Message Matching in Hooks for information on the exact
- format.
-
- To provide more flexibility and good defaults, Mutt applies the expandos
- of $index_format to mailbox after it was expanded.
-
- Examples:
-
- Example 3.11. Using %-expandos in save-hook
-
- # default: save all to ~/Mail/<author name>
- save-hook . ~/Mail/%F
-
- # save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
- save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
- # save from aol.com to $folder/spam
- save-hook aol\\.com$ +spam
-
- Also see the fcc-save-hook command.
-
-17. Specify default Fcc: mailbox when composing
-
- Usage:
-
- fcc-hook [!]pattern mailbox
-
- This command is used to save outgoing mail in a mailbox other than
- $record. Mutt 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.
-
- To provide more flexibility and good defaults, Mutt applies the expandos
- of $index_format to mailbox after it was expanded.
-
- See Message Matching in Hooks for information on the exact format of
- pattern.
-
- Example: fcc-hook [@.]aol\\.com$ +spammers
-
- The above will save a copy of all messages going to the aol.com domain to
- the `+spammers' mailbox by default. Also see the fcc-save-hook command.
-
-18. Specify default save filename and default Fcc: mailbox at once
-
- Usage:
-
- fcc-save-hook [!]pattern mailbox
-
- This command is a shortcut, equivalent to doing both a fcc-hook and a
- save-hook with its arguments, including %-expansion on mailbox according
- to $index_format.
-
-19. Change settings based upon message recipients
-
- Usage:
-
- reply-hook [!]pattern command
-
- send-hook [!]pattern command
-
- send2-hook [!]pattern command
-
- These commands can be used to execute arbitrary configuration commands
- based upon recipients of the message. pattern is used to match the
- message, see Message Matching in Hooks for details. command is executed
- when pattern matches.
-
- 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 user's configuration file.
-
- send2-hook is matched every time a message is changed, either by editing
- it, or by using the compose menu to change its recipients or subject.
- send2-hook is executed after send-hook, and can, e.g., be used to set
- parameters such as the $sendmail variable depending on the message's
- sender address.
-
- For each type of send-hook or reply-hook, when multiple matches occur,
- commands are executed in the order they are specified in the muttrc (for
- that type of hook).
-
- Example: send-hook mutt "set mime_forward signature=''"
-
- Another typical use for this command is to change the values of the
- $attribution, $signature and $locale variables in order to change the
- language of the attributions and signatures based upon the recipients.
-
- Note
-
- 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.
-
-20. Change settings before formatting a message
-
- Usage:
-
- message-hook [!]pattern command
-
- This command can be used to execute arbitrary configuration commands
- before viewing or formatting a message based upon information about the
- message. command is executed if the pattern matches the message to be
- displayed. When multiple matches occur, commands are executed in the order
- they are specified in the muttrc.
-
- See Message Matching in Hooks for information on the exact format of
- pattern.
-
- Example:
-
- message-hook ~A 'set pager=builtin'
- message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
-
-21. Choosing the cryptographic key of the recipient
-
- Usage:
-
- crypt-hook pattern keyid
-
- When encrypting messages with PGP/GnuPG 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
- would normally use. The crypt-hook command provides a method by which you
- can specify the ID of the public key to be used when encrypting messages
- to a certain recipient.
-
- The meaning of keyid 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.
-
-22. Adding key sequences to the keyboard buffer
-
- Usage:
-
- push string
-
- This command adds the named string to the keyboard buffer. The string may
- contain control characters, key names and function names like the sequence
- string in the macro command. You may use it to automatically run a
- sequence of commands at startup, or when entering certain folders. For
- example, the following command will automatically collapse all threads
- when entering a folder:
-
- Example 3.12. Embedding push in folder-hook
-
- folder-hook . 'push <collapse-all>'
-
-23. Executing functions
-
- Usage:
-
- exec function [ function ...]
-
- This command can be used to execute any function. Functions are listed in
- the function reference. "exec function" is equivalent to "push
- <function>".
-
-24. Message Scoring
-
- Usage:
-
- score pattern value
-
- unscore { * | pattern ... }
-
- The score commands adds value to a message's score if pattern matches it.
- pattern is a string in the format described in the patterns section (note:
- For efficiency reasons, patterns which scan information not available in
- the index, such as ~b, ~B or ~h, may not be used). value is a positive or
- negative integer. A message's final score is the sum total of all matching
- score entries. However, you may optionally prefix value with an equal sign
- (=) to cause evaluation to stop at a particular entry if there is a match.
- Negative final scores are rounded up to 0.
-
- The unscore command removes score entries from the list. You must specify
- the same pattern specified in the score command for it to be removed. The
- pattern "*" is a special token which means to clear the list of all score
- entries.
-
-25. Spam detection
-
- Usage:
-
- spam pattern format
-
- nospam { * | pattern }
-
- Mutt has generalized support for external spam-scoring filters. By
- defining your spam patterns with the spam and nospam commands, you can
- limit, search, and sort your mail based on its spam attributes, as
- determined by the external filter. You also can display the spam
- attributes in your index display using the %H selector in the
- $index_format variable. (Tip: try %?H?[%H] ? to display spam tags only
- when they are defined for a given message.)
-
- Your first step is to define your external filter's spam patterns using
- the spam command. pattern should be a regular expression that matches a
- header in a mail message. If any message in the mailbox matches this
- regular expression, it will receive a "spam tag" or "spam attribute"
- (unless it also matches a nospam pattern -- see below.) The appearance of
- this attribute is entirely up to you, and is governed by the format
- parameter. format can be any static text, but it also can include
- back-references from the pattern expression. (A regular expression
- "back-reference" refers to a sub-expression contained within parentheses.)
- %1 is replaced with the first back-reference in the regex, %2 with the
- second, etc.
-
- If you're using multiple spam filters, a message can have more than one
- spam-related header. You can define spam patterns for each filter you use.
- If a message matches two or more of these patterns, and the
- $spam_separator variable is set to a string, then the message's spam tag
- will consist of all the format strings joined together, with the value of
- $spam_separator separating them.
-
- For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
- define these spam settings:
-
- Example 3.13. Configuring spam detection
-
- spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
- spam "X-Spam-Status: Yes" "90+/SA"
- spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
- set spam_separator=", "
-
- If I then received a message that DCC registered with "many" hits under
- the "Fuz2" checksum, and that PureMessage registered with a 97%
- probability of being spam, that message's spam tag would read
- 90+/DCC-Fuz2, 97/PM. (The four characters before "=many" in a DCC report
- indicate the checksum used -- in this case, "Fuz2".)
-
- If the $spam_separator variable is unset, then each spam pattern match
- supersedes the previous one. Instead of getting joined format strings,
- you'll get only the last one to match.
-
- The spam tag is what will be displayed in the index when you use %H in the
- $index_format variable. It's also the string that the ~H pattern-matching
- expression matches against for <search> and <limit> functions. And it's
- what sorting by spam attribute will use as a sort key.
-
- That's a pretty complicated example, and most people's actual environments
- will have only one spam filter. The simpler your configuration, the more
- effective mutt can be, especially when it comes to sorting.
-
- Generally, when you sort by spam tag, mutt will sort lexically -- that is,
- by ordering strings alphanumerically. 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 lower priority 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 a more 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"
-
-26. Setting and Querying Variables
-
- 26.1. Commands
-
- The following commands are available to manipulate and query variables:
-
- Usage:
-
- set { [ no | inv ] variable | variable=value } [...]
-
- toggle variable [ variable ...]
-
- unset variable [ variable ...]
-
- reset variable [ variable ...]
-
- This command is used to set (and unset) configuration variables. There are
- four basic types of variables: boolean, number, string and quadoption.
- boolean variables can be set (true) or unset (false). number variables can
- be assigned a positive integer value. string variables consist of any
- number of printable characters and must be enclosed in quotes if they
- contain spaces or tabs. You may also use the escape sequences "\n" and
- "\t" for newline and tab, respectively. quadoption variables are used to
- control whether or not to be prompted for certain actions, or to specify a
- default action. A value of yes will cause the action to be carried out
- automatically as if you had answered yes to the question. Similarly, a
- value of no will cause the action to be carried out as if you had answered
- "no." A value of ask-yes will cause a prompt with a default answer of
- "yes" and ask-no will provide a default answer of "no."
-
- Prefixing a variable with "no" will unset it. Example: set noaskbcc.
-
- For boolean variables, you may optionally prefix the variable name with
- inv to toggle the value (on or off). This is useful when writing macros.
- Example: set invsmart_wrap.
-
- The toggle command automatically prepends the inv prefix to all specified
- variables.
-
- The unset command automatically prepends the no prefix to all specified
- variables.
-
- Using the <enter-command> function in the index menu, you can query the
- value of a variable by prefixing the name of the variable with a question
- mark:
-
- set ?allow_8bit
-
- The question mark is actually only required for boolean and quadoption
- variables.
-
- The reset command resets all given variables to the compile time defaults
- (hopefully mentioned in this manual). If you use the command set and
- prefix the variable with "&" this has the same behavior as the reset
- command.
-
- With the reset command there exists the special variable "all", which
- allows you to reset all variables to their system defaults.
-
- 26.2. User-defined variables
-
- 26.2.1. Introduction
-
- Along with the variables listed in the Configuration variables section,
- mutt supports user-defined variables with names starting with my_ as in,
- for example, my_cfgdir.
-
- The set command either creates a custom my_ variable or changes its value
- if it does exist already. The unset and reset commands remove the variable
- entirely.
-
- Since user-defined variables are expanded in the same way that environment
- variables are (except for the shell-escape command and backtick
- expansion), this feature can be used to make configuration files more
- readable.
-
- 26.2.2. Examples
-
- The following example defines and uses the variable my_cfgdir to
- abbreviate the calls of the source command:
-
- Example 3.14. Using user-defined variables for config file readability
-
- set my_cfgdir = $HOME/mutt/config
-
- source $my_cfgdir/hooks
- source $my_cfgdir/macros
- # more source commands...
-
- A custom variable can also be used in macros to backup the current value
- of another variable. In the following example, the value of the $delete is
- changed temporarily while its original value is saved as my_delete. After
- the macro has executed all commands, the original value of $delete is
- restored.
-
- Example 3.15. Using user-defined variables for backing up other config
- option values
-
- macro pager ,x '\
- <enter-command>set my_delete=$delete<enter>\
- <enter-command>set delete=yes<enter>\
- ...\
- <enter-command>set delete=$my_delete<enter>'
-
- Since mutt expands such values already when parsing the configuration
- file(s), the value of $my_delete in the last example would be the value of
- $delete exactly as it was at that point during parsing the configuration
- file. If another statement would change the value for $delete later in the
- same or another file, it would have no effect on $my_delete. However, the
- expansion can be deferred to runtime, as shown in the next example, when
- escaping the dollar sign.
-
- Example 3.16. Deferring user-defined variable expansion to runtime
-
- macro pager <PageDown> "\
- <enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
- <next-page>\
- <enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
- <enter-command> unset my_old_pager_stop<Enter>"
-
- Note that there is a space between <enter-command> and the set
- configuration command, preventing mutt from recording the macro's commands
- into its history.
-
-27. Reading initialization commands from another file
-
- Usage:
-
- source filename
-
- This command allows the inclusion of initialization commands from other
- files. For example, I place all of my aliases in ~/.mail_aliases so that I
- can make my ~/.muttrc readable and keep my aliases private.
-
- If the filename begins with a tilde ("~"), it will be expanded to the path
- of your home directory.
-
- If the filename ends with a vertical bar (|), then filename is considered
- to be an executable program from which to read input (eg. source
- ~/bin/myscript|).
-
-28. Configuring features conditionnaly
-
- Usage: ifdef item command
-
- This command allows to test if a feature has been compiled in, before
- actually executing the command. Item can be either the name of a function,
- variable, or command. Example:
-
- ifdef imap_keepalive 'source ~/.mutt/imap_setup'
-
-29. Removing hooks
-
- Usage:
-
- unhook { * | hook-type }
-
- This command permits you to flush hooks you have previously defined. You
- can either remove all hooks by giving the "*" character as an argument, or
- you can remove all hooks of a specific type by saying something like
- unhook send-hook.
-
-30. Format Strings
-
- 30.1. Basic usage
-
- Format strings are a general concept you'll find in several locations
- through the mutt configuration, especially in the $index_format,
- $pager_format, $status_format, and other "*_format" variables. These can
- be very straightforward, and it's quite possible you already know how to
- use them.
-
- The most basic format string element is a percent symbol followed by
- another character. For example, %s represents a message's Subject: header
- in the $index_format variable. The "expandos" available are documented
- with each format variable, but there are general modifiers available with
- all formatting expandos, too. Those are our concern here.
-
- Some of the modifiers are borrowed right out of C (though you might know
- them from Perl, Python, shell, or another language). These are the [-]m.n
- modifiers, as in %-12.12s. As with such programming languages, these
- modifiers allow you to specify the minimum and maximum size of the
- resulting string, as well as its justification. If the "-" sign follows
- the percent, the string will be left-justified instead of right-justified.
- If there's a number immediately following that, it's the minimum amount of
- space the formatted string will occupy -- if it's naturally smaller than
- that, it will be padded out with spaces. If a decimal point and another
- number follow, that's the maximum space allowable -- the string will not
- be permitted to exceed that width, no matter its natural size. Each of
- these three elements is optional, so that all these are legal format
- strings: %-12s %4c %.15F %-12.15L
-
- Mutt adds some other modifiers to format strings. If you use an equals
- symbol (=) as a numeric prefix (like the minus above), it will force the
- string to be centered within its minimum space range. For example, %=14y
- will reserve 14 characters for the %y expansion -- that's the X-Label:
- header, in $index_format. If the expansion results in a string less than
- 14 characters, it will be centered in a 14-character space. If the X-Label
- for a message were "test", that expansion would look like " test ".
-
- There are two very little-known modifiers that affect the way that an
- expando is replaced. If there is an underline ("_") character between any
- format modifiers (as above) and the expando letter, it will expands in all
- lower case. And if you use a colon (":"), it will replace all decimal
- points with underlines.
-
- 30.2. Filters
-
- Any format string ending in a vertical bar ("|") will be expanded and
- piped through the first word in the string, using spaces as separator. The
- string returned will be used for display. If the returned string ends in
- %, it will be passed through the formatter a second time. This allows the
- filter to generate a replacement format string including % expandos.
-
- All % expandos in a format string are expanded before the script is called
- so that:
-
- Example 3.17. Using external filters in format strings
-
- set status_format="script.sh '%r %f (%L)'|"
-
- will make mutt expand %r, %f and %L before calling the script. The example
- also shows that arguments can be quoted: the script will receive the
- expanded string between the single quotes as the only argument.
-
- A practical example is the mutt_xtitle script installed in the samples
- subdirectory of the mutt documentation: it can be used as filter for
- $status_format to set the current terminal's title, if supported.
-
-Chapter 4. Advanced Usage
-
- Table of Contents
-
- 1. Regular Expressions
-
- 2. Patterns: Searching, Limiting and Tagging
-
- 2.1. Pattern Modifier
-
- 2.2. Simple Patterns
-
- 2.3. Complex Patterns
-
- 2.4. Searching by Date
-
- 3. Using Tags
-
- 4. Using Hooks
-
- 4.1. Message Matching in Hooks
-
- 5. External Address Queries
-
- 6. Mailbox Formats
-
- 7. Mailbox Shortcuts
-
- 8. Handling Mailing Lists
-
- 9. Handling multiple folders
-
- 10. Editing threads
-
- 10.1. Linking threads
-
- 10.2. Breaking threads
-
- 11. Delivery Status Notification (DSN) Support
-
- 12. Start a WWW Browser on URLs
-
-1. Regular Expressions
-
- All string patterns in Mutt including those in more complex patterns must
- be specified using regular expressions (regexp) in the "POSIX extended"
- syntax (which is more or less the syntax used by egrep and GNU awk). For
- your convenience, we have included below a brief description of this
- syntax.
-
- The search is case sensitive if the pattern contains at least one upper
- case letter, and case insensitive otherwise.
-
- Note
-
- 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
-
- 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 Syntax of Initialization Files for more information on "
- and ' delimiter processing. To match a literal " or ' you must preface it
- with \ (backslash).
-
- The fundamental building blocks are the regular expressions that match a
- single character. Most characters, including all letters and digits, are
- regular expressions that match themselves. Any metacharacter with special
- meaning may be quoted by preceding it with a backslash.
-
- The period "." matches any single character. The caret "^" and the dollar
- sign "$" are metacharacters that respectively match the empty string at
- the beginning and end of a line.
-
- A list of characters enclosed by "[" and "]" matches any single character
- in that list; if the first character of the list is a caret "^" then it
- matches any character not in the list. For example, the regular expression
- [0123456789] matches any single digit. A range of ASCII characters may be
- specified by giving the first and last characters, separated by a hyphen
- "-". Most metacharacters lose their special meaning inside lists. To
- include a literal "]" place it first in the list. Similarly, to include a
- literal "^" place it anywhere but first. Finally, to include a literal
- hyphen "-" place it last.
-
- Certain named classes of characters are predefined. Character classes
- consist of "[:", a keyword denoting the class, and ":]". The following
- classes are defined by the POSIX standard in Table 4.1, "POSIX regular
- expression character classes"
-
- Table 4.1. POSIX regular expression character classes
-
- +------------------------------------------------------------------------+
- | Character class | Description |
- |-----------------+------------------------------------------------------|
- | [:alnum:] | Alphanumeric characters |
- |-----------------+------------------------------------------------------|
- | [:alpha:] | Alphabetic characters |
- |-----------------+------------------------------------------------------|
- | [:blank:] | Space or tab characters |
- |-----------------+------------------------------------------------------|
- | [:cntrl:] | Control characters |
- |-----------------+------------------------------------------------------|
- | [:digit:] | Numeric characters |
- |-----------------+------------------------------------------------------|
- | | Characters that are both printable and visible. (A |
- | [:graph:] | space is printable, but not visible, while an "a" is |
- | | both) |
- |-----------------+------------------------------------------------------|
- | [:lower:] | Lower-case alphabetic characters |
- |-----------------+------------------------------------------------------|
- | [:print:] | Printable characters (characters that are not |
- | | control characters) |
- |-----------------+------------------------------------------------------|
- | | Punctuation characters (characters that are not |
- | [:punct:] | letter, digits, control characters, or space |
- | | characters) |
- |-----------------+------------------------------------------------------|
- | [:space:] | Space characters (such as space, tab and formfeed, |
- | | to name a few) |
- |-----------------+------------------------------------------------------|
- | [:upper:] | Upper-case alphabetic characters |
- |-----------------+------------------------------------------------------|
- | [:xdigit:] | Characters that are hexadecimal digits |
- +------------------------------------------------------------------------+
-
- A character class is only valid in a regular expression inside the
- brackets of a character list.
-
- Note
-
- Note that the brackets in these class names are part of the symbolic
- names, and must be included in addition to the brackets delimiting the
- bracket list. For example, [[:digit:]] is equivalent to [0-9].
-
- Two additional special sequences can appear in character lists. These
- apply to non-ASCII character sets, which can have single symbols (called
- collating elements) that are represented with more than one character, as
- well as several characters that are equivalent for collating or sorting
- purposes:
-
- Collating Symbols
-
- A collating symbol is a multi-character collating element enclosed
- in "[." and ".]". For example, if "ch" is a collating element,
- then [[.ch.]] is a regexp that matches this collating element,
- while [ch] is a regexp that matches either "c" or "h".
-
- Equivalence Classes
-
- An equivalence class is a locale-specific name for a list of
- characters that are equivalent. The name is enclosed in "[=" and
- "=]". For example, the name "e" might be used to represent all of
- "e" "e" and "e". In this case, [[=e=]] is a regexp that matches
- any of "e", "e" and "e".
-
- A regular expression matching a single character may be followed by one of
- several repetition operators described in Table 4.2, "Regular expression
- repetition operators".
-
- Table 4.2. Regular expression repetition operators
-
- +------------------------------------------------------------------------+
- | Operator | Description |
- |----------+-------------------------------------------------------------|
- | ? | The preceding item is optional and matched at most once |
- |----------+-------------------------------------------------------------|
- | * | The preceding item will be matched zero or more times |
- |----------+-------------------------------------------------------------|
- | + | The preceding item will be matched one or more times |
- |----------+-------------------------------------------------------------|
- | {n} | The preceding item is matched exactly n times |
- |----------+-------------------------------------------------------------|
- | {n,} | The preceding item is matched n or more times |
- |----------+-------------------------------------------------------------|
- | {,m} | The preceding item is matched at most m times |
- |----------+-------------------------------------------------------------|
- | {n,m} | The preceding item is matched at least n times, but no more |
- | | than m times |
- +------------------------------------------------------------------------+
-
- Two regular expressions may be concatenated; the resulting regular
- expression matches any string formed by concatenating two substrings that
- respectively match the concatenated subexpressions.
-
- Two regular expressions may be joined by the infix operator "|"; the
- resulting regular expression matches any string matching either
- subexpression.
-
- Repetition takes precedence over concatenation, which in turn takes
- precedence over alternation. A whole subexpression may be enclosed in
- parentheses to override these precedence rules.
-
- Note
-
- If you compile Mutt with the GNU rx package, the following operators may
- also be used in regular expressions as described in Table 4.3, "GNU
- regular expression extensions".
-
- Table 4.3. GNU regular expression extensions
-
- +------------------------------------------------------------------------+
- | Expression | Description |
- |------------+-----------------------------------------------------------|
- | \\y | Matches the empty string at either the beginning or the |
- | | end of a word |
- |------------+-----------------------------------------------------------|
- | \\B | Matches the empty string within a word |
- |------------+-----------------------------------------------------------|
- | \\< | Matches the empty string at the beginning of a word |
- |------------+-----------------------------------------------------------|
- | \\> | Matches the empty string at the end of a word |
- |------------+-----------------------------------------------------------|
- | \\w | Matches any word-constituent character (letter, digit, or |
- | | underscore) |
- |------------+-----------------------------------------------------------|
- | \\W | Matches any character that is not word-constituent |
- |------------+-----------------------------------------------------------|
- | \\` | Matches the empty string at the beginning of a buffer |
- | | (string) |
- |------------+-----------------------------------------------------------|
- | \\' | Matches the empty string at the end of a buffer |
- +------------------------------------------------------------------------+
-
- Please note however that these operators are not defined by POSIX, so they
- may or may not be available in stock libraries on various systems.
-
-2. Patterns: Searching, Limiting and Tagging
-
- Many of Mutt's commands allow you to specify a pattern to match (limit,
- tag-pattern, delete-pattern, etc.). Table 4.4, "Pattern modifiers" shows
- several ways to select messages.
-
- Table 4.4. Pattern modifiers
-
- +------------------------------------------------------------------------+
- | Pattern modifier | Description |
- |------------------+-----------------------------------------------------|
- | ~A | all messages |
- |------------------+-----------------------------------------------------|
- | ~b EXPR | messages which contain EXPR in the message body |
- |------------------+-----------------------------------------------------|
- | | messages which contain STRING in the message body. |
- | =b STRING | If IMAP is enabled, searches for STRING on the |
- | | server, rather than downloading each message and |
- | | searching it locally. |
- |------------------+-----------------------------------------------------|
- | ~B EXPR | messages which contain EXPR in the whole message |
- |------------------+-----------------------------------------------------|
- | ~c EXPR | messages carbon-copied to EXPR |
- |------------------+-----------------------------------------------------|
- | %c GROUP | messages carbon-copied to any member of GROUP |
- |------------------+-----------------------------------------------------|
- | ~C EXPR | messages either to: or cc: EXPR |
- |------------------+-----------------------------------------------------|
- | %C GROUP | messages either to: or cc: to any member of GROUP |
- |------------------+-----------------------------------------------------|
- | ~d [MIN]-[MAX] | messages with "date-sent" in a Date range |
- |------------------+-----------------------------------------------------|
- | ~D | deleted messages |
- |------------------+-----------------------------------------------------|
- | ~e EXPR | messages which contains EXPR in the "Sender" field |
- |------------------+-----------------------------------------------------|
- | %e GROUP | messages which contain a member of GROUP in the |
- | | "Sender" field |
- |------------------+-----------------------------------------------------|
- | ~E | expired messages |
- |------------------+-----------------------------------------------------|
- | ~F | flagged messages |
- |------------------+-----------------------------------------------------|
- | ~f EXPR | messages originating from EXPR |
- |------------------+-----------------------------------------------------|
- | %f GROUP | messages originating from any member of GROUP |
- |------------------+-----------------------------------------------------|
- | ~g | cryptographically signed messages |
- |------------------+-----------------------------------------------------|
- | ~G | cryptographically encrypted messages |
- |------------------+-----------------------------------------------------|
- | ~h EXPR | messages which contain EXPR in the message header |
- |------------------+-----------------------------------------------------|
- | ~H EXPR | messages with a spam attribute matching EXPR |
- |------------------+-----------------------------------------------------|
- | ~i EXPR | messages which match EXPR in the "Message-ID" field |
- |------------------+-----------------------------------------------------|
- | ~k | messages which contain PGP key material |
- |------------------+-----------------------------------------------------|
- | ~L EXPR | messages either originated or received by EXPR |
- |------------------+-----------------------------------------------------|
- | %L GROUP | message either originated or received by any member |
- | | of GROUP |
- |------------------+-----------------------------------------------------|
- | ~l | messages addressed to a known mailing list |
- |------------------+-----------------------------------------------------|
- | ~m [MIN]-[MAX] | messages in the range MIN to MAX *) |
- |------------------+-----------------------------------------------------|
- | ~n [MIN]-[MAX] | messages with a score in the range MIN to MAX *) |
- |------------------+-----------------------------------------------------|
- | ~N | new messages |
- |------------------+-----------------------------------------------------|
- | ~O | old messages |
- |------------------+-----------------------------------------------------|
- | ~p | messages addressed to you (consults alternates) |
- |------------------+-----------------------------------------------------|
- | ~P | messages from you (consults alternates) |
- |------------------+-----------------------------------------------------|
- | ~Q | messages which have been replied to |
- |------------------+-----------------------------------------------------|
- | ~r [MIN]-[MAX] | messages with "date-received" in a Date range |
- |------------------+-----------------------------------------------------|
- | ~R | read messages |
- |------------------+-----------------------------------------------------|
- | ~s EXPR | messages having EXPR in the "Subject" field. |
- |------------------+-----------------------------------------------------|
- | ~S | superseded messages |
- |------------------+-----------------------------------------------------|
- | ~t EXPR | messages addressed to EXPR |
- |------------------+-----------------------------------------------------|
- | ~T | tagged messages |
- |------------------+-----------------------------------------------------|
- | ~u | messages addressed to a subscribed mailing list |
- |------------------+-----------------------------------------------------|
- | ~U | unread messages |
- |------------------+-----------------------------------------------------|
- | ~v | messages part of a collapsed thread. |
- |------------------+-----------------------------------------------------|
- | ~V | cryptographically verified messages |
- |------------------+-----------------------------------------------------|
- | ~x EXPR | messages which contain EXPR in the "References" |
- | | field |
- |------------------+-----------------------------------------------------|
- | ~X [MIN]-[MAX] | messages with MIN to MAX attachments *) |
- |------------------+-----------------------------------------------------|
- | ~y EXPR | messages which contain EXPR in the "X-Label" field |
- |------------------+-----------------------------------------------------|
- | ~z [MIN]-[MAX] | messages with a size in the range MIN to MAX *) |
- |------------------+-----------------------------------------------------|
- | ~= | duplicated messages (see $duplicate_threads) |
- |------------------+-----------------------------------------------------|
- | ~$ | unreferenced messages (requires threaded view) |
- |------------------+-----------------------------------------------------|
- | | messages in threads containing messages matching |
- | ~(PATTERN) | PATTERN, e.g. all threads containing messages from |
- | | you: ~(~P) |
- +------------------------------------------------------------------------+
-
- Where EXPR is a regular expression. Special attention has to be made when
- using regular expressions inside of patterns. Specifically, Mutt'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
- ("\\"). You can force mutt to treat EXPR as a simple string instead of a
- regular expression by using = instead of ~ in the pattern name. For
- example, =b *.* will find all messages that contain the literal string
- "*.*". Simple string matches are less powerful than regular expressions
- but can be considerably faster. This is especially true for IMAP folders,
- because string matches can be performed on the server instead of by
- fetching every message. IMAP treats =h specially: it must be of the form
- "header: substring" and will not partially match header names. The
- substring part may be omitted if you simply wish to find messages
- containing a particular header without regard to its value.
-
- *) The forms "<[MAX]", ">[MIN]", "[MIN]-" and "-[MAX]" are allowed, too.
-
- 2.1. Pattern Modifier
-
- Note
-
- Note that patterns matching 'lists' of addresses (notably c, C, p, P and
- t) match if there is at least one match in the whole list. If you want to
- make sure that all elements of that list match, you need to prefix your
- pattern with "^". This example matches all mails which only has recipients
- from Germany.
-
- ^~C \.de$
-
- 2.2. Simple Patterns
-
- Mutt supports two versions of so called "simple searches" which are issued
- if the query entered for searching, limiting and similar operations does
- not seem to be a valid pattern (i.e. it does not contain one of these
- characters: "~", "=" or "%"). If the query is supposed to contain one of
- these special characters, they must be escaped by prepending a backslash
- ("\").
-
- The first type is by checking whether the query string equals a keyword
- case-insensitively from Table 4.5, "Simple search keywords": If that is
- the case, Mutt will use the shown pattern modifier instead. If a keyword
- would conflict with your search keyword, you need to turn it into a
- regular expression to avoid matching the keyword table. For example, if
- you want to find all messages matching "flag" (using $simple_search) but
- don't want to match flagged messages, simply search for "[f]lag".
-
- Table 4.5. Simple search keywords
-
- +----------------------------+
- | Keyword | Pattern modifier |
- |---------+------------------|
- | all | ~A |
- |---------+------------------|
- | . | ~A |
- |---------+------------------|
- | ^ | ~A |
- |---------+------------------|
- | del | ~D |
- |---------+------------------|
- | flag | ~F |
- |---------+------------------|
- | new | ~N |
- |---------+------------------|
- | old | ~O |
- |---------+------------------|
- | repl | ~Q |
- |---------+------------------|
- | read | ~R |
- |---------+------------------|
- | tag | ~T |
- |---------+------------------|
- | unread | ~U |
- +----------------------------+
-
- The second type of simple search is to build a complex search pattern
- using $simple_search as a template. Mutt will insert your query properly
- quoted and search for the composed complex query.
-
- 2.3. Complex Patterns
-
- Logical AND is performed by specifying more than one criterion. For
- example:
-
- ~t mutt ~f elkins
-
- would select messages which contain the word "mutt" in the list of
- recipients and that have the word "elkins" in the "From" header field.
-
- Mutt also recognizes the following operators to create more complex search
- patterns:
-
- o ! -- logical NOT operator
-
- o | -- logical OR operator
-
- o () -- logical grouping operator
-
- Here is an example illustrating a complex search pattern. This pattern
- will select all messages which do not contain "mutt" in the "To" or "Cc"
- field and which are from "elkins".
-
- Example 4.1. Using boolean operators in patterns
-
- !(~t mutt|~c mutt) ~f elkins
-
- Here is an example using white space in the regular expression (note the '
- and " delimiters). For this to match, the mail's subject must match the
- "^Junk +From +Me$" and it must be from either "Jim +Somebody" or "Ed
- +SomeoneElse":
-
- '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
-
- Note
-
- If a regular expression contains parenthesis, or a vertical bar ("|"), you
- must enclose the expression in double or single quotes since those
- characters are also used to separate different parts of Mutt's pattern
- language. For example: ~f "me@(mutt\.org|cs\.hmc\.edu)"
-
- Without the quotes, the parenthesis wouldn't end. This would be separated
- to two OR'd patterns: ~f me@(mutt\.org and cs\.hmc\.edu). They are never
- what you want.
-
- 2.4. Searching by Date
-
- Mutt supports two types of dates, absolute and relative.
-
- Absolute. Dates must be in DD/MM/YY format (month and year are optional,
- defaulting to the current month and year). An example of a valid range of
- dates is:
-
- Limit to messages matching: ~d 20/1/95-31/10
-
- If you omit the minimum (first) date, and just specify "-DD/MM/YY", all
- messages before the given date will be selected. If you omit the maximum
- (second) date, and specify "DD/MM/YY-", all messages after the given date
- will be selected. If you specify a single date with no dash ("-"), only
- messages sent on the given date will be selected.
-
- Error Margins. You can add error margins to absolute dates. An error
- margin is a sign (+ or -), followed by a digit, followed by one of the
- units in Table 4.6, "Date units". As a special case, you can replace the
- sign by a "*" character, which is equivalent to giving identical plus and
- minus error margins.
-
- Table 4.6. Date units
-
- +--------------------+
- | Unit | Description |
- |------+-------------|
- | y | Years |
- |------+-------------|
- | m | Months |
- |------+-------------|
- | w | Weeks |
- |------+-------------|
- | d | Days |
- +--------------------+
-
- Example: To select any messages two weeks around January 15, 2001, you'd
- use the following pattern:
-
- Limit to messages matching: ~d 15/1/2001*2w
-
- Relative. This type of date is relative to the current date, and may be
- specified as:
-
- o >offset (messages older than offset units)
-
- o <offset (messages newer than offset units)
-
- o =offset (messages exactly offset units old)
-
- offset is specified as a positive number with one of the units from
- Table 4.6, "Date units".
-
- Example: to select messages less than 1 month old, you would use
-
- Limit to messages matching: ~d <1m
-
- Note
-
- All dates used when searching are relative to the local time zone, so
- unless you change the setting of your $index_format to include a %[...]
- format, these are not the dates shown in the main index.
-
-3. Using Tags
-
- Sometimes it is desirable to perform an operation on a group of messages
- all at once rather than one at a time. An example might be to save
- messages to a mailing list to a separate folder, or to delete all messages
- with a given subject. To tag all messages matching a pattern, use the
- <tag-pattern> function, which is bound to "shift-T" by default. Or you can
- select individual messages by hand using the <tag-message> function, which
- is bound to "t" by default. See patterns for Mutt'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 macros 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 will stop "eating" the macro when it encounters
- the "end-cond" operator; after this operator the rest of the macro will be
- executed as normal.
-
-4. Using Hooks
-
- A hook is a concept found in many other programs 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 world, a hook
- consists of a regular expression or pattern along with a configuration
- option/command. See
-
- o folder-hook
-
- o send-hook
-
- o message-hook
-
- o save-hook
-
- o mbox-hook
-
- o fcc-hook
-
- o fcc-save-hook
-
- for specific details on each type of hook available.
-
- Note
-
- If a hook changes configuration settings, these changes remain effective
- until the end of the current mutt session. As this is generally not
- desired, a default hook needs to be added before all other hooks to
- restore configuration defaults. Here is an example with send-hook and the
- my_hdr directive:
-
- Example 4.2. Combining send-hook and my_hdr
-
- send-hook . 'unmy_hdr From:'
- send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-
- 4.1. Message Matching in Hooks
-
- Hooks that act upon messages (message-hook, reply-hook, send-hook,
- send2-hook, save-hook, fcc-hook) are evaluated in a slightly different
- manner. For the other types of hooks, a regular expression 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 allows the use of the search pattern language for matching messages
- in hook commands. This works in exactly the same way as it would when
- limiting or searching 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 User <user@host>'
-
- which would execute the given command when sending mail to me@cs.hmc.edu.
-
- However, it is not required that you write the pattern to match using the
- full searching language. You can still specify a simple regular expression
- like the other hooks, in which case Mutt 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.
-
-5. External Address Queries
-
- Mutt supports connecting to external directory databases such as LDAP,
- ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using
- a simple interface. Using the $query_command variable, you specify the
- wrapper command to use. For example:
-
- set query_command = "mutt_ldap_query.pl '%s'"
-
- The wrapper script should accept the query on the command-line. It should
- return a one line message, then each matching response on a single line,
- each line containing a tab separated address then name then some other
- optional information. On error, or if there are no matching addresses,
- return a non-zero exit code and a one line error message.
-
- An example multiple response output:
-
- Searching database ... 20 entries ... 3 matching:
- me@cs.hmc.edu Michael Elkins mutt dude
- blong@fiction.net Brandon Long mutt and more
- roessler@does-not-exist.org 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 addresses to mail, start
- a new query, or have a new query appended to the current responses.
-
- The other mechanism for accessing the query function is for address
- completion, similar to the alias completion. In any prompt for address
- entry, you can use the <complete-query> function (default: ^T) to run a
- query based on the current address you have typed. Like aliases, mutt will
- look for what you have typed back to the last space or comma. If there is
- a single response for that query, mutt will expand the address in place.
- If there are multiple responses, mutt will activate the query menu. At the
- query menu, you can select one or more addresses to be added to the
- prompt.
-
-6. Mailbox Formats
-
- Mutt 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 new
- mailboxes, Mutt uses the default specified with the $mbox_type variable.
-
- mbox. This is the most widely used mailbox format for UNIX. All messages
- are stored in a single file. Each message has a line of the form:
-
- From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-
- to denote the start of a new message (this is often referred to as the
- "From_" line).
-
- MMDF. This is a variant of the mbox format. Each message is surrounded by
- lines containing "^A^A^A^A" (four control-A's).
-
- MH. A radical departure from mbox and MMDF, a mailbox consists of a
- directory and each message is stored in a separate file. The filename
- indicates the message number (however, this is may not correspond to the
- message number Mutt displays). Deleted messages are renamed with a comma
- (,) prepended to the filename. 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 two programs
- are writing the mailbox over NFS, which means that no file locking is
- needed.
-
-7. Mailbox Shortcuts
-
- There are a number of built in shortcuts which refer to specific
- mailboxes. These shortcuts can be used anywhere you are prompted for a
- file or mailbox path.
-
- o ! -- refers to your $spoolfile (incoming) mailbox
-
- o > -- refers to your $mbox file
-
- o < -- refers to your $record file
-
- o ^ -- refers to the current mailbox
-
- o - or !! -- refers to the file you've last visited
-
- o ~ -- refers to your home directory
-
- o = or + -- refers to your $folder directory
-
- o @alias -- refers to the default save folder as determined by the
- address of the alias
-
-8. Handling Mailing Lists
-
- Mutt 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 and subscribe commands in your muttrc.
-
- Now that Mutt 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 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 also supports the Mail-Followup-To header. When you send a message to
- a list of recipients which includes one or several subscribed mailing
- lists, and if the $followup_to option is set, mutt will generate a
- Mail-Followup-To header which contains all the recipients to whom you send
- this message, but not your address. This indicates that group-replies or
- list-replies (also known as "followups") to this message should only be
- sent to the original recipients of the message, and not separately to you
- - you'll receive your copy through one of the mailing lists you are
- subscribed to.
-
- Conversely, when group-replying or list-replying to a message which has a
- Mail-Followup-To header, mutt will respect this header if the
- $honor_followup_to configuration variable is set. Using list-reply will in
- this case also make sure that the reply goes to the mailing list, even if
- it's not specified in the list of recipients in the Mail-Followup-To.
-
- Note
-
- When header editing is enabled, you can create a Mail-Followup-To header
- manually. Mutt will only auto-generate this header if it doesn't exist
- when you send the message.
-
- The other method some mailing list admins use is to generate a "Reply-To"
- field which points back to the mailing list address rather than the author
- of the message. This can create problems when trying to reply directly to
- the author in private, since most mail clients will automatically reply to
- the address given in the "Reply-To" field. Mutt 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 in the "Reply-To" field, or reply directly to the address
- given in the "From" field. When set to yes, the "Reply-To" field will be
- used when present.
-
- The "X-Label:" header field can be used to further identify mailing lists
- or list subject matter (or just to annotate messages individually). The
- $index_format variable's "%y" and "%Y" escapes can be used to expand
- "X-Label:" fields in the index, and Mutt'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 procmail and other mail filtering agents.
-
- Lastly, Mutt 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 dealing with large volume
- mailing lists easier because you can easily delete uninteresting threads
- and quickly find topics of value.
-
-9. Handling multiple folders
-
- Mutt supports setups with multiple folders, allowing all of them to be
- monitored for new mail (see Section 14, "Monitoring incoming mail" for
- details).
-
- When in the index menu and being idle (also see $timeout), Mutt
- periodically checks for new mail in all folders which have been configured
- via the mailboxes command. The interval depends on the folder type: for
- local/IMAP folders it consults $mail_check and $pop_checkinterval for POP
- folders.
-
- Outside the index menu the directory browser supports checking for new
- mail using the <check-new> function which is unbound by default. Pressing
- TAB will bring up a menu showing the files specified by the mailboxes
- command, and indicate which contain new messages. Mutt will automatically
- enter this mode when invoked from the command line with the -y option.
-
- For the pager, index and directory browser menus, Mutt contains the
- <buffy-list> function (bound to "." by default) which will print a list of
- folders with new mail in the command line at the bottom of the screen.
-
- For the index, by default Mutt displays the number of mailboxes with new
- mail in the status bar, please refer to the $index_format variable for
- details.
-
- When changing folders, Mutt fills the prompt with the first folder from
- the mailboxes list containing new mail (if any), pressing space will cycle
- through folders with new mail.
-
-10. Editing threads
-
- Mutt 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.
-
- 10.1. Linking threads
-
- Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
- "References:" headers when replying to a message. This results in broken
- discussions because Mutt has not enough information to guess the correct
- threading. You can fix this by tagging the reply, then moving to the
- parent message and using the <link-threads> function (bound to & by
- default). The reply will then be connected to this "parent" message.
-
- You can also connect multiple children at once, tagging them and using the
- tag-prefix command (';') or the auto_tag option.
-
- 10.2. Breaking threads
-
- On mailing lists, some people are in the bad habit of starting a new
- discussion by hitting "reply" to any message from the list and changing
- the subject to a totally unrelated one. You can fix such threads by using
- the <break-thread> function (bound by default to #), which will turn the
- subthread starting from the current message into a whole different thread.
-
-11. Delivery Status Notification (DSN) Support
-
- RFC1894 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."
-
- To support DSN, there are two variables. $dsn_notify is used to request
- receipts for different results (such as failed message, message delivered,
- etc.). $dsn_return requests how much of your message should be returned
- with the receipt (headers or full message).
-
- When using $sendmail for mail delivery, you need to use either Berkeley
- sendmail 8.8.x (or greater) a MTA supporting DSN command line options
- compatible to Sendmail: The -N and -R options can be used by the mail
- client to make requests as to what type of status messages should be
- returned. Please consider your MTA documentation whether DSN is supported.
-
- For SMTP delivery using $smtp_url, it depends on the capabilities
- announced by the server whether mutt will attempt to request DSN or not.
-
-12. Start a WWW Browser on URLs
-
- If a message contains URLs, it is efficient to get a menu with all the
- URLs and start a WWW browser on one of them. This functionality is
- provided by the external urlview program which can be retrieved at
- ftp://ftp.mutt.org/mutt/contrib/ and the configuration commands:
-
- macro index \cb |urlview\n
- macro pager \cb |urlview\n
-
-1. Compressed folders Support (OPTIONAL)
-
- If Mutt was compiled with compressed folders support (by running the
- configure script with the --enable-compressed flag), Mutt can open folders
- stored in an arbitrary format, provided that the user has a script to
- convert from/to this format to one of the accepted. The most common use is
- to open compressed archived folders e.g. with gzip. In addition, the user
- can provide a script that gets a folder in an accepted format and appends
- its context to the folder in the user-defined format, which may be faster
- than converting the entire folder to the accepted format, appending to it
- and converting back to the user-defined format. There are three hooks
- defined (open-hook, close-hook and append-hook) which define commands to
- uncompress and compress a folder and to append messages to an existing
- compressed folder respectively. For example:
-
- open-hook \\.gz$ "gzip -cd %f > %t"
- close-hook \\.gz$ "gzip -c %t > %f"
- append-hook \\.gz$ "gzip -c %t >> %f"
-
- You do not have to specify all of the commands. If you omit append-hook,
- the folder will be open and closed again each time you will add to it. If
- you omit close-hook (or give empty command) , the folder will be open in
- the mode. If you specify append-hook though you'll be able to append to
- the folder. Note that Mutt 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.
-
- 1.1. Open a compressed mailbox for reading
-
- Usage: open-hook regexp "command" The command is the command that can be
- used for opening the folders whose names match regexp. The command string
- is the printf-like format string, and it should accept two parameters: %f,
- which is replaced with the (compressed) folder name, and %t which is
- replaced with the name of the temporary folder to which to write. %f and
- %t can be repeated any number of times in the command string, and all of
- the entries are replaced with the appropriate folder name. In addition, %%
- is replaced by %, as in printf, and any other %anything is left as is. The
- command should not remove the original compressed file. The command should
- return non-zero exit status if it fails, so mutt knows something's wrong.
- Example:
-
- open-hook \\.gz$ "gzip -cd %f > %t"
-
- If the command is empty, this operation is disabled for this file type.
-
- 1.2. Write a compressed mailbox
-
- Usage: close-hook regexp "command" This is used to close the folder that
- was open with the open-hook command after some changes were made to it.
- The command string is the command that can be used for closing the folders
- whose names match regexp. It has the same format as in the open-hook
- command. Temporary folder in this case is the folder previously produced
- by the open-hook command. The command should not remove the decompressed
- file. The command should return non-zero exit status if it fails, so mutt
- knows something's wrong. Example:
-
- close-hook \\.gz$ "gzip -c %t > %f"
-
- If the command is empty, this operation is disabled for this file type,
- and the file can only be open in the read-only mode. close-hook is not
- called when you exit from the folder if the folder was not changed.
-
- 1.3. Append a message to a compressed mailbox
-
- Usage: append-hook regexp "command" This command is used for saving to an
- existing compressed folder. The command is the command that can be used
- for appending to the folders whose 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 being appended. The command should not
- remove the decompressed file. The command should return non-zero exit
- status if it fails, so mutt knows something's wrong. Example:
-
- append-hook \\.gz$ "gzip -c %t >> %f"
-
- When append-hook is used, the folder is not opened, which saves time, but
- this means that we can not find out what the folder type is. Thus the
- default ($mbox_type) type is always supposed (i.e. this is the format used
- for the temporary folder). If the file does not exist when you save to it,
- close-hook is called, and not append-hook. append-hook is only for
- appending to existing folders. If the command is empty, this operation is
- disabled for this file type. In this case, the folder will be open and
- closed again (using open-hook and close-hookrespectively) each time you
- will add to it.
-
- 1.4. Encrypted folders
-
- The compressed folders support can also be used to handle encrypted
- folders. If you want to encrypt a folder with PGP, you may want to use the
- following hooks:
-
- open-hook \\.pgp$ "pgp -f < %f > %t"
- close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-
- Please note, that PGP does not support appending to an encrypted folder,
- so there is no append-hook defined. If you are using GnuPG instead of PGP,
- you may use the following hooks instead:
-
- open-hook \\.gpg$ "gpg --decrypt < %f > %t"
- close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
-
- Note: the folder is temporary stored decrypted in the /tmp directory,
- where it can be read by your system administrator. So think about the
- security aspects of this.
-
-Chapter 5. Mutt's MIME Support
-
- Table of Contents
-
- 1. Using MIME in Mutt
-
- 1.1. Viewing MIME messages in the pager
-
- 1.2. The Attachment Menu
-
- 1.3. The Compose Menu
-
- 2. MIME Type configuration with mime.types
-
- 3. MIME Viewer configuration with mailcap
-
- 3.1. The Basics of the mailcap file
-
- 3.2. Secure use of mailcap
-
- 3.3. Advanced mailcap Usage
-
- 3.4. Example mailcap files
-
- 4. MIME Autoview
-
- 5. MIME Multipart/Alternative
-
- 6. Attachment Searching and Counting
-
- 7. MIME Lookup
-
- Quite a bit of effort has been made to make Mutt 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 for MIME, there are two extra
- types of configuration files which Mutt uses. One is the mime.types file,
- which contains the mapping of file extensions to IANA MIME types. The
- other is the mailcap file, which specifies the external commands to use
- for handling specific MIME types.
-
-1. Using MIME in Mutt
-
- There are three areas/menus in Mutt which deal with MIME, they are the
- pager (while viewing a message), the attachment menu and the compose menu.
-
- 1.1. Viewing MIME messages in the pager
-
- When you select a message from the index and view it in the pager, Mutt
- decodes the message to a text representation. Mutt 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
- recognizes a variety of PGP MIME types, including PGP/MIME and
- application/pgp.
-
- Mutt will denote attachments with a couple lines describing them. These
- lines are of the form:
-
- [-- Attachment #1: Description --]
- [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-
- Where the Description is the description or filename given for the
- attachment, and the Encoding is one of
- 7bit/8bit/quoted-printable/base64/binary.
-
- If Mutt cannot deal with a MIME type, it will display a message like:
-
- [-- image/gif is unsupported (use 'v' to view this part) --]
-
- 1.2. The Attachment Menu
-
- The default binding for view-attachments is `v', which displays the
- attachment menu for a message. The attachment menu displays a list of the
- attachments in a message. From the attachment menu, you can save, print,
- pipe, delete, and view attachments. You can apply these operations to a
- group of attachments at once, by tagging the attachments and by using the
- "tag-prefix" operator. You can also reply to the current message from this
- menu, and only the current attachment (or the attachments tagged) will be
- quoted in your reply. You can view attachments as text, or view them using
- the mailcap viewer definition.
-
- Finally, you can apply the usual message-related functions (like
- <resend-message>, and the <reply> and <forward> functions) to attachments
- of type message/rfc822.
-
- See the help on the attachment menu for more information.
-
- 1.3. The Compose Menu
-
- The compose menu is the menu you see before you send a message. It allows
- you to edit the recipient list, the subject, and other aspects of your
- message. It also contains a list of the attachments of your message,
- including the main body. From this menu, you can print, copy, filter,
- pipe, edit, compose, review, and rename an attachment or a list of tagged
- attachments. You can also modifying the attachment information, notably
- the type, encoding and description.
-
- Attachments appear as follows:
-
- - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
- 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
-
- The '-' denotes that Mutt will delete the file after sending (or
- postponing, or canceling) the message. It can be toggled with the
- toggle-unlink command (default: u). The next field is the MIME
- content-type, and can be changed with the edit-type command (default: ^T).
- The next field is the encoding for the attachment, which allows a binary
- message to be encoded for transmission on 7bit links. It can be changed
- with the edit-encoding command (default: ^E). The next field is the size
- of the attachment, rounded to kilobytes or megabytes. The next field is
- the filename, which can be changed with the rename-file command (default:
- R). The final field is the description of the attachment, and can be
- changed with the edit-description command (default: d).
-
-2. MIME Type configuration with mime.types
-
- When you add an attachment to your mail message, Mutt searches your
- personal mime.types file at ${HOME}/.mime.types, 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 distribution, and should
- contain most of the MIME types you are likely to use.
-
- If Mutt 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 will assume that the file is plain text, and mark it as
- text/plain. If the file contains binary information, then Mutt will mark
- it as application/octet-stream. You can change the MIME type that Mutt
- 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 recognizes all of these if the appropriate entry is
- found in the mime.types file. It also recognizes other major mime types,
- such as the chemical type that is widely used in the molecular modeling
- community to pass molecular data in various forms to various molecular
- viewers. Non-recognized mime types should only be used if the recipient of
- the message is likely to be expecting such attachments.
-
-3. MIME Viewer configuration with mailcap
-
- Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific
- format specified in Appendix A of RFC 1524. This file format is commonly
- referred to as the mailcap format. Many MIME compliant programs utilize
- the mailcap format, allowing you to specify handling for all MIME types in
- one place for all programs. Programs known to use this format include
- Netscape, XMosaic, lynx and metamail.
-
- In order to handle various MIME types that Mutt can not handle internally,
- Mutt parses a series of external configuration files to find an external
- handler. The default search string for these files is a colon delimited
- list containing the following files:
-
- 1. $HOME/.mailcap
-
- 2. $PKGDATADIR/mailcap
-
- 3. $SYSCONFDIR/mailcap
-
- 4. /etc/mailcap
-
- 5. /usr/etc/mailcap
-
- 6. /usr/local/etc/mailcap
-
- where $HOME is your home directory. The $PKGDATADIR and the $SYSCONFDIR
- directories depend on where mutt is installed: the former is the default
- for shared data, the latter for system configuration files.
-
- The default search path can be obtained by running the following command:
-
- mutt -nF /dev/null -Q mailcap_path
-
- In particular, the metamail distribution will install a mailcap file,
- usually as /usr/local/etc/mailcap, which contains some baseline entries.
-
- 3.1. The Basics of the mailcap file
-
- A mailcap file consists of a series of lines which are comments, blank, or
- definitions.
-
- A comment line consists of a # character followed by anything you want.
-
- A blank line is blank.
-
- A definition line consists of a content type, a view command, and any
- number of optional fields. Each field of a definition line is divided by 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 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 will turn over the terminal to the view program
- until the program quits, at which time Mutt will remove the temporary file
- if it exists.
-
- So, in the simplest form, you can send a text/plain message to the
- external pager more on stdin:
-
- text/plain; more
-
- Or, you could send the message as a file:
-
- text/plain; more %s
-
- Perhaps you would like to use lynx to interactively view a text/html
- message:
-
- text/html; lynx %s
-
- In this case, lynx does not support viewing a file from stdin, so you must
- use the %s syntax.
-
- Note
-
- Some older versions of lynx contain a bug where they will check the
- mailcap file for a viewer for text/html. They will find the line which
- calls lynx, and run it. This causes lynx to continuously spawn itself to
- view the object.
-
- On the other hand, maybe you don't want to use lynx interactively, you
- just want to have it convert the text/html to text/plain, then you can
- use:
-
- text/html; lynx -dump %s | more
-
- Perhaps you wish to use lynx to view text/html files, and a pager on all
- other text formats, then you would use the following:
-
- text/html; lynx %s
- text/*; more
-
- This is the simplest form of a mailcap file.
-
- 3.2. Secure use of mailcap
-
- The interpretation of shell meta-characters embedded in MIME parameters
- can lead to security problems in general. Mutt tries to quote parameters
- in expansion of %s syntaxes properly, and avoids risky characters by
- substituting them, see the $mailcap_sanitize variable.
-
- Although mutt's procedures to invoke programs with mailcap seem to be
- safe, there are other applications parsing mailcap, maybe taking less care
- of it. Therefore you should pay attention to the following rules:
-
- Keep the %-expandos away from shell quoting. Don't quote them with single
- or double quotes. Mutt 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 behavior with quotes introduces new
- leaks - there is no alternative to correct quoting in the first place.
-
- If you have to use the %-expandos' values in context where you need
- quoting or backtick expansions, put that value into a shell variable and
- reference the shell variable where necessary, as in the following example
- (using $charset inside the backtick expansion is safe, since it is not
- itself subject to any further expansion):
-
- text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-
- 3.3. Advanced mailcap Usage
-
- 3.3.1. Optional Fields
-
- In addition to the required content-type and view command fields, you can
- add semi-colon ';' separated fields to set flags and other options. Mutt
- recognizes the following optional fields:
-
- copiousoutput
-
- This flag tells Mutt that the command passes possibly large
- amounts of text on stdout. This causes Mutt 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 assumes that the command is interactive. One could use
- this to replace the pipe to more in the lynx -dump example in the
- Basic section:
-
- text/html; lynx -dump %s ; copiousoutput
-
- This will cause lynx to format the text/html output as text/plain
- and Mutt will use your standard pager to display the results.
-
- needsterminal
-
- Mutt 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 will use $wait_key and the exit status of
- the program to decide if it will ask you to press a key after the
- external program has exited. In all other situations it will not
- prompt you for a key.
-
- compose=<command>
-
- This flag specifies the command to use to create a new attachment
- of a specific MIME type. Mutt supports this from the compose menu.
-
- composetyped=<command>
-
- This flag specifies the command to use to create a new attachment
- of a specific MIME type. This command differs from the compose
- command in that mutt will expect standard MIME headers on the
- data. This can be used to specify parameters, filename,
- description, etc. for a new attachment. Mutt supports this from
- the compose menu.
-
- print=<command>
-
- This flag specifies the command to use to print a specific MIME
- type. Mutt supports this from the attachment and compose menus.
-
- edit=<command>
-
- This flag specifies the command to use to edit a specific MIME
- type. Mutt supports this from the compose menu, and also uses it
- to compose new attachments. Mutt will default to the defined
- editor for text attachments.
-
- nametemplate=<template>
-
- This field specifies the format for the file denoted by %s in the
- command fields. Certain programs will require a certain file
- extension, for instance, to correctly view a file. For instance,
- lynx will only interpret a file as text/html if the file ends in
- .html. So, you would specify lynx as a text/html viewer with a
- line in the mailcap file like:
-
- text/html; lynx %s; nametemplate=%s.html
-
- test=<command>
-
- This field specifies a command to run to test whether this mailcap
- entry should be used. The command is defined with the command
- expansion rules defined in the next section. If the command
- returns 0, then the test passed, and Mutt uses this entry. If the
- command returns non-zero, then the test failed, and Mutt continues
- searching for the right entry. Note that the content-type must
- match before Mutt performs the test. For example:
-
- text/html; netscape -remote 'openURL(%s)' ; test=RunningX
- text/html; lynx %s
-
- In this example, Mutt 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 will call netscape to
- display the text/html object. If RunningX doesn't return 0, then
- Mutt 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 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 will search for an entry with the print command:
-
- image/*; xv %s
- image/gif; ; print= anytopnm %s | pnmtops | lpr; \
- nametemplate=%s.gif
-
- Mutt 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 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 will use the second entry for interactive viewing.
-
- 3.3.3. Command Expansion
-
- The various commands defined in the mailcap files are passed to the
- /bin/sh shell using the system() function. Before the command is passed to
- /bin/sh -c, it is parsed to expand various special parameters with
- information from Mutt. The keywords Mutt expands are:
-
- %s
-
- As seen in the basic mailcap section, this variable is expanded to
- a filename specified by the calling program. This file contains
- the body of the message to view/print/edit or where the composing
- program should place the results of composition. In addition, the
- use of this keyword causes Mutt to not pass the body of the
- message to the view/print/edit program on stdin.
-
- %t
-
- Mutt will expand %t to the text representation of the content type
- of the message in the same form as the first parameter of the
- mailcap definition line, ie text/html or image/gif.
-
- %{<parameter>}
-
- Mutt will expand this to the value of the specified parameter from
- the Content-Type: line of the mail message. For instance, if Your
- mail message contains:
-
- Content-Type: text/plain; charset=iso-8859-1
-
- then Mutt will expand %{charset} to iso-8859-1. The default
- metamail mailcap file uses this feature to test the charset to
- spawn an xterm using the right charset to view the message.
-
- \%
-
- This will be replaced by a %
-
- Mutt 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.
-
- 3.4. Example mailcap files
-
- This mailcap file is fairly simple and standard:
-
- # I'm always running X :)
- video/*; xanim %s > /dev/null
- image/*; xv %s > /dev/null
-
- # I'm always running netscape (if my computer had more memory, maybe)
- text/html; netscape -remote 'openURL(%s)'
-
- This mailcap file shows quite a number of examples:
-
- # Use xanim to view all videos Xanim produces a header on startup,
- # send that to /dev/null so I don't see it
- video/*; xanim %s > /dev/null
-
- # Send html to a running netscape by remote
- text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
-
- # If I'm not running netscape but I am running X, start netscape on the
- # object
- text/html; netscape %s; test=RunningX
-
- # Else use lynx to view it as text
- text/html; lynx %s
-
- # This version would convert the text/html to text/plain
- text/html; lynx -dump %s; copiousoutput
-
- # I use enscript to print text in two columns to a page
- text/*; more %s; print=enscript -2Gr %s
-
- # Netscape adds a flag to tell itself to view jpegs internally
- image/jpeg;xv %s; x-mozilla-flags=internal
-
- # Use xv to view images if I'm running X
- # In addition, this uses the \ to extend the line and set my editor
- # for images
- image/*;xv %s; test=RunningX; \
- edit=xpaint %s
-
- # Convert images to text using the netpbm tools
- image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
- pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
- # Send excel spreadsheets to my NT box
- application/ms-excel; open.pl %s
-
-4. MIME Autoview
-
- In addition to explicitly telling Mutt to view an attachment with the MIME
- viewer defined in the mailcap file, Mutt has support for automatically
- viewing MIME attachments while in the pager.
-
- To work, you must define a viewer in the mailcap file which uses the
- copiousoutput option to denote that it is non-interactive. Usually, you
- also use the entry to convert the attachment to a text representation
- which you can view in the pager.
-
- You then use the auto_view muttrc command to list the content-types that
- you wish to view automatically.
-
- For instance, if you set auto_view to:
-
- auto_view text/html application/x-gunzip \
- application/postscript image/gif application/x-tar-gz
-
- Mutt could use the following mailcap entries to automatically view
- attachments of these types.
-
- text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
- image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | \
- pgmtopbm | pbmtoascii ; copiousoutput
- application/x-gunzip; gzcat; copiousoutput
- application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
- application/postscript; ps2ascii %s; copiousoutput
-
- "unauto_view" can be used to remove previous entries from the autoview
- list. This can be used with message-hook to autoview messages based on
- size, etc. "unauto_view *" will remove all previous entries.
-
-5. MIME Multipart/Alternative
-
- Mutt 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 types is
- preferred. The alternative_order list consists of a number of mimetypes in
- order, including support for implicit and explicit wildcards, for example:
-
- alternative_order text/enriched text/plain text application/postscript image/*
-
- Next, mutt will check if any of the types have a defined auto_view, and
- use that. Failing that, Mutt will look for any text type. As a last
- attempt, mutt will look for any type it knows how to handle.
-
- To remove a MIME type from the alternative_order list, use the
- unalternative_order command.
-
-6. Attachment Searching and Counting
-
- If you ever lose track of attachments in your mailboxes, Mutt's
- attachment-counting and -searching support might be for you. You can make
- your message index display the number of qualifying attachments in each
- message, or search for messages by attachment count. You also can
- configure what kinds of attachments qualify for this feature with the
- attachments and unattachments commands.
-
- In order to provide this information, mutt needs to fully MIME-parse all
- messages affected first. This can slow down operation especially for
- remote mail folders such as IMAP because all messages have to be
- downloaded first regardless whether the user really wants to view them or
- not.
-
- The syntax is:
-
- attachments {+|-}disposition mime-type
- unattachments {+|-}disposition mime-type
- attachments ?
-
- Disposition is the attachment's Content-disposition type -- either inline
- or attachment. You can abbreviate this to I or A.
-
- Disposition is prefixed by either a + symbol or a - symbol. If it's a +,
- you're saying that you want to allow this disposition and MIME type to
- qualify. If it's a -, you're saying that this disposition and MIME type is
- an exception to previous + rules. There are examples below of how this is
- useful.
-
- Mime-type is, unsurprisingly, the MIME type of the attachment you want to
- affect. A MIME type is always of the format major/minor, where major
- describes the broad category of document you're looking at, and minor
- describes the specific type within that category. The major part of
- mime-type must be literal text (or the special token "*"), but the minor
- part may be a regular expression. (Therefore, "*/.*" matches any MIME
- type.)
-
- The MIME types you give to the attachments directive are a kind of
- pattern. When you use the attachments directive, the patterns you specify
- are added to a list. When you use unattachments, the pattern is removed
- from the list. The patterns are not expanded and matched to specific MIME
- types at this time -- they're just text in a list. They're only matched
- when actually evaluating a message.
-
- Some examples might help to illustrate. The examples that are not
- commented out define the default configuration of the lists.
-
- Example 5.1. Attachment counting
-
- ## 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
-
- Entering the command "attachments ?" as a command will list your current
- settings in Muttrc format, so that it can be pasted elsewhere.
-
-7. MIME Lookup
-
- Mutt's mime_lookup list specifies a list of mime-types that should not be
- treated according to their mailcap entry. This option is designed to deal
- with binary types such as application/octet-stream. When an attachment's
- mime-type is listed in mime_lookup, then the extension of the filename
- will be compared to the list of extensions in the mime.types file. The
- mime-type associated with this extension will then be used to process the
- attachment according to the rules in the mailcap file and according to any
- other configuration options (such as auto_view) specified. Common usage
- would be:
-
- mime_lookup application/octet-stream application/X-Lotus-Manuscript
-
- In addition, the unmime_lookup command may be used to disable this feature
- for any particular mime-type if it had been set, for example, in a global
- muttrc.
-
-Chapter 6. Optional features
-
- Table of Contents
-
- 1. General notes
-
- 1.1. Enabling/disabling features
-
- 1.2. URL syntax
-
- 2. SSL/TLS Support
-
- 3. POP3 Support
-
- 4. IMAP Support
-
- 4.1. The Folder Browser
-
- 4.2. Authentication
-
- 5. SMTP Support
-
- 6. Managing multiple accounts
-
- 7. Local caching
-
- 7.1. Header caching
-
- 7.2. Body caching
-
- 7.3. Maintenance
-
- 8. Exact address generation
-
-1. General notes
-
- 1.1. Enabling/disabling features
-
- Mutt supports several of optional features which can be enabled or
- disabled at compile-time by giving the configure script certain arguments.
- These are listed in the "Optional features" section of the configure
- --help output.
-
- Which features are enabled or disabled can later be determined from the
- output of mutt -v. If a compile option starts with "+" it is enabled and
- disabled if prefixed with "-". For example, if mutt was compiled using
- GnuTLS for encrypted communication instead of OpenSSL, mutt -v would
- contain:
-
- -USE_SSL_OPENSSL +USE_SSL_GNUTLS
-
- 1.2. URL syntax
-
- Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
- to access servers using URLs. The canonical syntax for specifying URLs in
- mutt is (an item enclosed in [] means it is optional and may be omitted):
-
- proto[s]://[username[:password]@]server[:port]/[path]
-
- proto is the communication protocol: imap for IMAP, pop for POP3 and smtp
- for SMTP. If "s" for "secure communication" is appended, mutt will attempt
- to establish an encrypted communication using SSL or TLS. If no explicit
- port is given, mutt will use the system's default for the given protocol.
-
- Since all protocols by mutt support authentication, the username may be
- given directly in the URL instead of using the pop_user or imap_user
- variables. It may contain the "@" symbol being used by many mail systems
- as part of the login name. A password can be given, too but is not
- recommended if the URL is specified in a configuration file on disk.
-
- The optional path is only relevant for IMAP.
-
- For IMAP for example, you can select an alternative port by specifying it
- with the server: imap://imapserver:port/INBOX. You can also specify
- different username for each folder:
- imap://username@imapserver[:port]/INBOX or
- imap://username2@imapserver[:port]/path/to/folder. Replacing imap:// by
- imaps:// would make mutt attempt to connect using SSL or TLS on a
- different port to encrypt the communication.
-
-2. SSL/TLS Support
-
- If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
- compiled with support for SSL or TLS using either OpenSSL or GnuTLS ( by
- running the configure script with the --enable-ssl=... option for OpenSSL
- or --enable-gnutls=... for GnuTLS). Mutt can then attempt to encrypt
- communication with remote servers if these protocols are suffixed with "s"
- for "secure communication".
-
-3. POP3 Support
-
- If Mutt 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.
-
- Remote POP3 servers can be accessed using URLs with the pop protocol for
- unencrypted and pops for encrypted communication, see Section 1.2, "URL
- syntax" for details.
-
- Polling for new mail is more expensive over POP3 than locally. For this
- reason the frequency at which Mutt will check for mail remotely can be
- controlled by the $pop_checkinterval variable, which defaults to every 60
- seconds.
-
- 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 runs exactly
- as if the mail had always been local.
-
- Note
-
- If you only need to fetch all messages to a local mailbox you should
- consider using a specialized program, such as fetchmail, getmail or
- similar.
-
-4. IMAP Support
-
- If Mutt was compiled with IMAP support (by running the configure script
- with the --enable-imap flag), it has the ability to work with folders
- located on a remote IMAP server.
-
- You can access the remote inbox by selecting the folder by its URL (see
- Section 1.2, "URL syntax" for details) using the imap or imaps protocol.
- Alternatively, a pine-compatible notation is also supported, ie
- {[username@]imapserver[:port][/ssl]}path/to/folder
-
- Note that not all servers use "/" as the hierarchy separator. Mutt should
- correctly notice which separator is being used by the server and convert
- paths accordingly.
-
- When browsing folders on an IMAP server, you can toggle whether to look at
- only the folders you are subscribed to, or all folders with the
- toggle-subscribed command. See also the $imap_list_subscribed variable.
-
- Polling for new mail on an IMAP server can cause noticeable delays. So,
- you'll want to carefully tune the $mail_check and $timeout variables.
- Personally I use
-
- set mail_check=90
- set timeout=15
-
- with relatively good results over my slow modem line.
-
- Note
-
- Note that if you are using mbox as the mail store on UW servers prior to
- v12.250, the server has been reported to disconnect a client if another
- client selects the same folder.
-
- 4.1. The Folder Browser
-
- As of version 1.2, mutt supports browsing mailboxes on an IMAP server.
- This is mostly the same as the local file browser, with the following
- differences:
-
- o In lieu of file permissions, mutt displays the string "IMAP", possibly
- followed by the symbol "+", indicating that the entry contains both
- messages and subfolders. On Cyrus-like servers folders will often
- contain both messages and subfolders.
-
- o For the case where an entry can contain both messages and subfolders,
- the selection key (bound to enter by default) will choose to descend
- into the subfolder view. If you wish to view the messages in that
- folder, you must use view-file instead (bound to space by default).
-
- o You can create, delete and rename mailboxes with the create-mailbox,
- delete-mailbox, and rename-mailbox commands (default bindings: C, d
- and r, respectively). You may also subscribe and unsubscribe to
- mailboxes (normally these are bound to s and u, respectively).
-
- 4.2. Authentication
-
- Mutt supports four authentication methods with IMAP servers: SASL, GSSAPI,
- CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM
- authentication for you poor exchange users out there, but it has yet to be
- integrated into the main tree). There is also support for the
- pseudo-protocol ANONYMOUS, which allows you to log in to a public IMAP
- server without having an account. To use ANONYMOUS, simply make your
- username blank or "anonymous".
-
- SASL is a special super-authenticator, which selects among several
- protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most
- secure method available on your host and the server. Using some of these
- methods (including DIGEST-MD5 and possibly GSSAPI), your entire session
- will be encrypted and invisible to those teeming network snoops. It is the
- best option if you have it. To use it, you must have the Cyrus SASL
- library installed on your system and compile mutt with the --with-sasl
- flag.
-
- Mutt will try whichever methods are compiled in and available on the
- server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-
- There are a few variables which control authentication:
-
- o $imap_user - controls the username under which you request
- authentication on the IMAP server, for all authenticators. This is
- overridden by an explicit username in the mailbox path (ie by using a
- mailbox name of the form {user@host}).
-
- o $imap_pass - a password which you may preset, used by all
- authentication methods where a password is needed.
-
- o $imap_authenticators - a colon-delimited list of IMAP authentication
- methods to try, in the order you wish to try them. If specified, this
- overrides mutt's default (attempt everything, in the order listed
- above).
-
-5. SMTP Support
-
- Besides supporting traditional mail delivery through a sendmail-compatible
- program, mutt supports delivery through SMTP if it was configured and
- built with --enable-smtp.
-
- If the configuration variable $smtp_url is set, mutt will contact the
- given SMTP server to deliver messages; if it is unset, mutt will use the
- program specified by $sendmail.
-
- For details on the URL syntax, please see Section 1.2, "URL syntax".
-
- The built-in SMTP support supports encryption (the smtps protocol using
- SSL or TLS) as well as SMTP authentication using SASL. The authentication
- mechanisms for SASL are specified in $smtp_authenticators defaulting to an
- empty list which makes mutt try all available methods from most-secure to
- least-secure.
-
-6. Managing multiple accounts
-
- If you happen to have accounts on multiple IMAP, POP and/or SMTP 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 which
- includes (for example) polling for new mail, storing Fcc messages and
- saving messages to a folder. As a consequence, account-hook should only be
- used to set connection-related settings such as passwords or tunnel
- commands but not settings such as sender address or name (because in
- general it should be considered unpredictable which account-hook was last
- used).
-
- Some examples:
-
- account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
- account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
- account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
- account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-
-7. Local caching
-
- Mutt contains two types of local caching: (1) the so-called "header
- caching" and (2) the so-called "body caching" which are both described in
- this section.
-
- Header caching is optional as it depends on external libraries, body
- caching is always enabled if mutt is compiled with POP and/or IMAP support
- as these use it (body caching requires no external library).
-
- 7.1. Header caching
-
- Mutt provides optional support for caching message headers for the
- following types of folders: IMAP, POP, Maildir and MH. Header caching
- greatly improves speed because for remote folders, headers usually only
- need to be downloaded once. For Maildir and MH, reading the headers from a
- single file is much faster than looking at possibly thousands of single
- files (since Maildir and MH use one file per message.)
-
- Header caching can be enabled via the configure script and the
- --enable-hcache option. It's not turned on by default because external
- database libraries are required: one of tokyocabinet, qdbm, gdbm or bdb
- must be present.
-
- If enabled, $header_cache can be used to either point to a file or a
- directory. If set to point to a file, one database file for all folders
- will be used (which may result in lower performance), but one file per
- folder if it points to a directory.
-
- For the one-file-per-folder case, database files for remote folders will
- be named according to their URL while database files for local folders
- will be named by the MD5 checksums of their path. These database files may
- be safely removed if a system is short on space. You can compute the name
- of the header cache file for a particular local folder through a command
- like the following:
-
- $ printf '%s' '/path/to/folder' | md5sum
-
- The md5sum command may also be named md5, depending on your operating
- system.
-
- 7.2. Body caching
-
- Both cache methods can be combined using the same directory for storage
- (and for IMAP/POP even provide meaningful file names) which simplifies
- manual maintenance tasks.
-
- In addition to caching message headers only, mutt can also cache whole
- message bodies. This results in faster display of messages for POP and
- IMAP folders because messages usually have to be downloaded only once.
-
- For configuration, the variable $message_cachedir must point to a
- directory. There, mutt will create a hierarchy of subdirectories named
- like: proto:user@hostname where proto is either "pop" or "imap." Within
- there for each folder, mutt stores messages in single files (just like
- Maildir) so that with manual symlink creation these cache directories can
- be examined with mutt as read-only Maildir folders.
-
- All files can be removed as needed if the consumed disk space becomes an
- issue as mutt will silently fetch missing items again.
-
- 7.3. Maintenance
-
- Mutt does not (yet) support maintenance features for header cache database
- files so that files have to be removed in case they grow too big. It
- depends on the database library used for header caching whether disk space
- freed by removing messages is re-used.
-
- For body caches, mutt can keep the local cache in sync with the remote
- mailbox if the $message_cache_clean variable is set. Cleaning means to
- remove messages from the cache which are no longer present in the mailbox
- which only happens when other mail clients or instances of mutt using a
- different body cache location delete messages (Mutt itself removes deleted
- messages from the cache when syncing a mailbox). As cleaning can take a
- noticeable amount of time, it should not be set in general but only
- occasionally.
-
-8. Exact address generation
-
- Mutt supports the "Name <user@host>" address syntax for reading and
- writing messages, the older "user@host (Name)" syntax is only supported
- when reading messages. The --enable-exact-address switch can be given to
- configure to build it with write-support for the latter syntax.
- EXACT_ADDRESS in the output of mutt -v indicates whether it's supported.
-
-Chapter 7. Performance tuning
-
- Table of Contents
-
- 1. Reading and writing mailboxes
-
- 2. Reading messages from remote folders
-
- 3. Searching and limiting
-
-1. Reading and writing mailboxes
-
- Mutt's performance when reading mailboxes can be improved in two ways:
-
- 1. For remote folders (IMAP and POP) as well as folders using
- one-file-per message storage (Maildir and MH), mutt's performance can
- be greatly improved using header caching. Using a single database per
- folder may further increase performance.
-
- 2. Mutt provides the $read_inc and $write_inc variables to specify at
- which rate to update progress counters. If these values are too low,
- mutt may spend more time on updating the progress counter than it
- spends on actually reading/writing folders.
-
- For example, when opening a maildir folder with a few thousand
- messages, the default value for $read_inc may be too low. It can be
- tuned on on a folder-basis using folder-hooks:
-
- # use very high $read_inc to speed up reading hcache'd maildirs
- folder-hook . 'set read_inc=1000'
- # use lower value for reading slower remote IMAP folders
- folder-hook ^imap 'set read_inc=100'
- # use even lower value for reading even slower remote POP folders
- folder-hook ^pop 'set read_inc=1'
-
- These settings work on a per-message basis. However, as messages may
- greatly differ in size and certain operations are much faster than others,
- even per-folder settings of the increment variables may not be desirable
- as they produce either too few or too much progress updates. Thus, Mutt
- allows to limit the number of progress updates per second it'll actually
- send to the terminal using the $time_inc variable.
-
-2. Reading messages from remote folders
-
- Reading messages from remote folders such as IMAP an POP can be slow
- especially for large mailboxes since mutt only caches a very limited
- number of recently viewed messages (usually 10) per session (so that it
- will be gone for the next session.)
-
- To improve performance and permanently cache whole messages, please refer
- to mutt's so-called body caching for details.
-
-3. Searching and limiting
-
- When searching mailboxes either via a search or a limit action, for some
- patterns mutt distinguishes between regular expression and string
- searches. For regular expressions, patterns are prefixed with "~" and with
- "=" for string searches.
-
- Even though a regular expression search is fast, it's several times slower
- than a pure string search which is noticeable especially on large folders.
- As a consequence, a string search should be used instead of a regular
- expression search if the user already knows enough about the search
- pattern.
-
- For example, when limiting a large folder to all messages sent to or by an
- author, it's much faster to search for the initial part of an e-mail
- address via =Luser@ instead of ~Luser@. This is especially true for
- searching message bodies since a larger amount of input has to be
- searched.
-
- Please note that string search is an exact case-sensitive search while a
- regular expression search with only lower-case letters performs a
- case-insensitive search.
-
-Chapter 8. Reference
-
- Table of Contents
-
- 1. Command line options
-
- 2. Configuration Commands
-
- 3. Configuration variables
-
- 3.1. abort_nosubject
-
- 3.2. abort_unmodified
-
- 3.3. alias_file
-
- 3.4. alias_format
-
- 3.5. allow_8bit
-
- 3.6. allow_ansi
-
- 3.7. arrow_cursor
-
- 3.8. ascii_chars
-
- 3.9. askbcc
-
- 3.10. askcc
-
- 3.11. assumed_charset
-
- 3.12. attach_charset
-
- 3.13. attach_format
-
- 3.14. attach_sep
-
- 3.15. attach_split
-
- 3.16. attribution
-
- 3.17. autoedit
-
- 3.18. auto_tag
-
- 3.19. beep
-
- 3.20. beep_new
-
- 3.21. bounce
-
- 3.22. bounce_delivered
-
- 3.23. braille_friendly
-
- 3.24. check_mbox_size
-
- 3.25. charset
-
- 3.26. check_new
-
- 3.27. collapse_unread
-
- 3.28. uncollapse_jump
-
- 3.29. compose_format
-
- 3.30. config_charset
-
- 3.31. confirmappend
-
- 3.32. confirmcreate
-
- 3.33. connect_timeout
-
- 3.34. content_type
-
- 3.35. copy
-
- 3.36. crypt_use_gpgme
-
- 3.37. crypt_use_pka
-
- 3.38. crypt_autopgp
-
- 3.39. crypt_autosmime
-
- 3.40. date_format
-
- 3.41. default_hook
-
- 3.42. delete
-
- 3.43. delete_untag
-
- 3.44. digest_collapse
-
- 3.45. display_filter
-
- 3.46. dotlock_program
-
- 3.47. dsn_notify
-
- 3.48. dsn_return
-
- 3.49. duplicate_threads
-
- 3.50. edit_headers
-
- 3.51. editor
-
- 3.52. encode_from
-
- 3.53. envelope_from_address
-
- 3.54. escape
-
- 3.55. fast_reply
-
- 3.56. fcc_attach
-
- 3.57. fcc_clear
-
- 3.58. folder
-
- 3.59. folder_format
-
- 3.60. followup_to
-
- 3.61. force_name
-
- 3.62. forward_decode
-
- 3.63. forward_edit
-
- 3.64. forward_format
-
- 3.65. forward_quote
-
- 3.66. from
-
- 3.67. gecos_mask
-
- 3.68. hdrs
-
- 3.69. header
-
- 3.70. help
-
- 3.71. hidden_host
-
- 3.72. hide_limited
-
- 3.73. hide_missing
-
- 3.74. hide_thread_subject
-
- 3.75. hide_top_limited
-
- 3.76. hide_top_missing
-
- 3.77. history
-
- 3.78. history_file
-
- 3.79. honor_followup_to
-
- 3.80. hostname
-
- 3.81. ignore_linear_white_space
-
- 3.82. ignore_list_reply_to
-
- 3.83. imap_authenticators
-
- 3.84. imap_check_subscribed
-
- 3.85. imap_delim_chars
-
- 3.86. imap_headers
-
- 3.87. imap_idle
-
- 3.88. imap_keepalive
-
- 3.89. imap_list_subscribed
-
- 3.90. imap_login
-
- 3.91. imap_pass
-
- 3.92. imap_passive
-
- 3.93. imap_peek
-
- 3.94. imap_pipeline_depth
-
- 3.95. imap_servernoise
-
- 3.96. imap_user
-
- 3.97. implicit_autoview
-
- 3.98. include
-
- 3.99. include_onlyfirst
-
- 3.100. indent_string
-
- 3.101. index_format
-
- 3.102. ispell
-
- 3.103. keep_flagged
-
- 3.104. locale
-
- 3.105. mail_check
-
- 3.106. mailcap_path
-
- 3.107. mailcap_sanitize
-
- 3.108. maildir_mtime
-
- 3.109. header_cache
-
- 3.110. maildir_header_cache_verify
-
- 3.111. header_cache_pagesize
-
- 3.112. maildir_trash
-
- 3.113. mark_old
-
- 3.114. markers
-
- 3.115. mask
-
- 3.116. mbox
-
- 3.117. mbox_type
-
- 3.118. metoo
-
- 3.119. menu_context
-
- 3.120. menu_move_off
-
- 3.121. menu_scroll
-
- 3.122. meta_key
-
- 3.123. mh_purge
-
- 3.124. mh_seq_flagged
-
- 3.125. mh_seq_replied
-
- 3.126. mh_seq_unseen
-
- 3.127. mime_forward
-
- 3.128. mime_forward_decode
-
- 3.129. mime_forward_rest
-
- 3.130. mix_entry_format
-
- 3.131. mixmaster
-
- 3.132. move
-
- 3.133. message_cachedir
-
- 3.134. message_cache_clean
-
- 3.135. message_format
-
- 3.136. narrow_tree
-
- 3.137. net_inc
-
- 3.138. pager
-
- 3.139. pager_context
-
- 3.140. pager_format
-
- 3.141. pager_index_lines
-
- 3.142. pager_stop
-
- 3.143. crypt_autosign
-
- 3.144. crypt_autoencrypt
-
- 3.145. pgp_ignore_subkeys
-
- 3.146. crypt_replyencrypt
-
- 3.147. crypt_replysign
-
- 3.148. crypt_replysignencrypted
-
- 3.149. crypt_timestamp
-
- 3.150. sidebar_delim
-
- 3.151. sidebar_visible
-
- 3.152. sidebar_width
-
- 3.153. pgp_use_gpg_agent
-
- 3.154. crypt_verify_sig
-
- 3.155. smime_is_default
-
- 3.156. smime_ask_cert_label
-
- 3.157. smime_decrypt_use_default_key
-
- 3.158. pgp_entry_format
-
- 3.159. pgp_good_sign
-
- 3.160. pgp_check_exit
-
- 3.161. pgp_long_ids
-
- 3.162. pgp_retainable_sigs
-
- 3.163. pgp_autoinline
-
- 3.164. pgp_replyinline
-
- 3.165. pgp_show_unusable
-
- 3.166. pgp_sign_as
-
- 3.167. pgp_strict_enc
-
- 3.168. pgp_timeout
-
- 3.169. pgp_sort_keys
-
- 3.170. pgp_mime_auto
-
- 3.171. pgp_auto_decode
-
- 3.172. pgp_mime_signature_filename
-
- 3.173. pgp_mime_signature_description
-
- 3.174. pgp_decode_command
-
- 3.175. pgp_getkeys_command
-
- 3.176. pgp_verify_command
-
- 3.177. pgp_decrypt_command
-
- 3.178. pgp_clearsign_command
-
- 3.179. pgp_sign_command
-
- 3.180. pgp_encrypt_sign_command
-
- 3.181. pgp_encrypt_only_command
-
- 3.182. pgp_import_command
-
- 3.183. pgp_export_command
-
- 3.184. pgp_verify_key_command
-
- 3.185. pgp_list_secring_command
-
- 3.186. pgp_list_pubring_command
-
- 3.187. forward_decrypt
-
- 3.188. smime_timeout
-
- 3.189. smime_encrypt_with
-
- 3.190. smime_keys
-
- 3.191. smime_ca_location
-
- 3.192. smime_certificates
-
- 3.193. smime_decrypt_command
-
- 3.194. smime_verify_command
-
- 3.195. smime_verify_opaque_command
-
- 3.196. smime_sign_command
-
- 3.197. smime_sign_opaque_command
-
- 3.198. smime_encrypt_command
-
- 3.199. smime_pk7out_command
-
- 3.200. smime_get_cert_command
-
- 3.201. smime_get_signer_cert_command
-
- 3.202. smime_import_cert_command
-
- 3.203. smime_get_cert_email_command
-
- 3.204. smime_default_key
-
- 3.205. ssl_client_cert
-
- 3.206. ssl_force_tls
-
- 3.207. ssl_starttls
-
- 3.208. certificate_file
-
- 3.209. ssl_use_sslv3
-
- 3.210. ssl_use_tlsv1
-
- 3.211. ssl_min_dh_prime_bits
-
- 3.212. ssl_ca_certificates_file
-
- 3.213. pipe_split
-
- 3.214. pipe_decode
-
- 3.215. pipe_sep
-
- 3.216. pop_authenticators
-
- 3.217. pop_auth_try_all
-
- 3.218. pop_checkinterval
-
- 3.219. pop_delete
-
- 3.220. pop_host
-
- 3.221. pop_last
-
- 3.222. pop_reconnect
-
- 3.223. pop_user
-
- 3.224. pop_pass
-
- 3.225. post_indent_string
-
- 3.226. postpone
-
- 3.227. postponed
-
- 3.228. preconnect
-
- 3.229. print
-
- 3.230. print_command
-
- 3.231. print_decode
-
- 3.232. print_split
-
- 3.233. prompt_after
-
- 3.234. query_command
-
- 3.235. query_format
-
- 3.236. quit
-
- 3.237. quote_regexp
-
- 3.238. read_inc
-
- 3.239. read_only
-
- 3.240. realname
-
- 3.241. recall
-
- 3.242. record
-
- 3.243. reply_regexp
-
- 3.244. reply_self
-
- 3.245. reply_to
-
- 3.246. resolve
-
- 3.247. reverse_alias
-
- 3.248. reverse_name
-
- 3.249. reverse_realname
-
- 3.250. rfc2047_parameters
-
- 3.251. save_address
-
- 3.252. save_empty
-
- 3.253. save_history
-
- 3.254. save_name
-
- 3.255. score
-
- 3.256. score_threshold_delete
-
- 3.257. score_threshold_flag
-
- 3.258. score_threshold_read
-
- 3.259. send_charset
-
- 3.260. sendmail
-
- 3.261. sendmail_wait
-
- 3.262. shell
-
- 3.263. sig_dashes
-
- 3.264. sig_on_top
-
- 3.265. signature
-
- 3.266. simple_search
-
- 3.267. smart_wrap
-
- 3.268. smileys
-
- 3.269. sleep_time
-
- 3.270. smtp_authenticators
-
- 3.271. smtp_pass
-
- 3.272. smtp_url
-
- 3.273. sort
-
- 3.274. sort_alias
-
- 3.275. sort_aux
-
- 3.276. sort_browser
-
- 3.277. sort_re
-
- 3.278. spam_separator
-
- 3.279. spoolfile
-
- 3.280. status_chars
-
- 3.281. status_format
-
- 3.282. status_on_top
-
- 3.283. strict_threads
-
- 3.284. suspend
-
- 3.285. text_flowed
-
- 3.286. thread_received
-
- 3.287. thorough_search
-
- 3.288. tilde
-
- 3.289. time_inc
-
- 3.290. timeout
-
- 3.291. tmpdir
-
- 3.292. to_chars
-
- 3.293. trash
-
- 3.294. tunnel
-
- 3.295. use_8bitmime
-
- 3.296. use_domain
-
- 3.297. use_envelope_from
-
- 3.298. use_from
-
- 3.299. use_idn
-
- 3.300. use_ipv6
-
- 3.301. user_agent
-
- 3.302. visual
-
- 3.303. wait_key
-
- 3.304. weed
-
- 3.305. wrap
-
- 3.306. wrap_search
-
- 3.307. wrapmargin
-
- 3.308. write_inc
-
- 3.309. write_bcc
-
- 3.310. xterm_icon
-
- 3.311. xterm_set_titles
-
- 3.312. xterm_title
-
- 4. Functions
-
- 4.1. generic menu
-
- 4.2. index menu
-
- 4.3. pager menu
-
- 4.4. alias menu
-
- 4.5. query menu
-
- 4.6. attach menu
-
- 4.7. compose menu
-
- 4.8. postpone menu
-
- 4.9. browser menu
-
- 4.10. pgp menu
-
- 4.11. smime menu
-
- 4.12. mix menu
-
- 4.13. editor menu
-
-1. Command line options
-
- Running mutt with no arguments will make Mutt attempt to read your spool
- mailbox. However, it is possible to read other mailboxes and to send
- messages from the command line as well.
-
- Table 8.1. Command line options
-
- +------------------------------------------------------------------------+
- | Option | Description |
- |--------+---------------------------------------------------------------|
- | -A | expand an alias |
- |--------+---------------------------------------------------------------|
- | -a | attach a file to a message |
- |--------+---------------------------------------------------------------|
- | -b | specify a blind carbon-copy (BCC) address |
- |--------+---------------------------------------------------------------|
- | -c | specify a carbon-copy (Cc) address |
- |--------+---------------------------------------------------------------|
- | -D | print the value of all mutt variables to stdout |
- |--------+---------------------------------------------------------------|
- | -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 Muttrc |
- |--------+---------------------------------------------------------------|
- | -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) |
- |--------+---------------------------------------------------------------|
- | -v | show version number and compile-time definitions |
- |--------+---------------------------------------------------------------|
- | -x | simulate the mailx(1) compose mode |
- |--------+---------------------------------------------------------------|
- | -y | show a menu containing the files specified by the mailboxes |
- | | command |
- |--------+---------------------------------------------------------------|
- | -z | exit immediately if there are no messages in the mailbox |
- |--------+---------------------------------------------------------------|
- | -Z | open the first folder with new message,exit immediately if |
- | | none |
- +------------------------------------------------------------------------+
-
- To read messages in a mailbox
-
- mutt [-nz] [-F muttrc ] [-m type ] [-f mailbox ]
-
- To compose a new message
-
- mutt [-n] [-F muttrc ] [-c address ] [-i filename ] [-s subject ] [ -a
- file [...] -- ] address ...
-
- Mutt also supports a "batch" mode to send prepared messages. Simply
- redirect input from the file you wish to send. For example,
-
- mutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat
-
- This command will send a message to "professor@bigschool.edu" with a
- subject of "data set for run #2". In the body of the message will be the
- contents of the file "~/run2.dat".
-
- All files passed with -a file will be attached as a MIME part to the
- message. To attach several files, use "--" to separate files and recipient
- addresses: mutt -a *.png -- some@one.org
-
-2. Configuration Commands
-
- The following are the commands understood by mutt.
-
- o account-hook pattern command
-
- o alias [ -group name ...] key address [ address ...]
-
- o unalias [ -group name ...] { * | key ... }
-
- o alternates [ -group name ...] regexp [ regexp ...]
-
- o unalternates [ -group name ...] { * | regexp ... }
-
- o alternative-order mimetype [ mimetype ...]
-
- o unalternative-order { * | mimetype ... }
-
- o auto-view mimetype [ mimetype ...]
-
- o unauto-view { * | mimetype ... }
-
- o bind map key function
-
- o charset-hook alias charset
-
- o iconv-hook charset local-charset
-
- o color object foreground background
-
- color { header | body } foreground background regexp
-
- color index foreground background pattern
-
- o uncolor index pattern ...
-
- o exec function [ function ...]
-
- o fcc-hook [!]pattern mailbox
-
- o fcc-save-hook [!]pattern mailbox
-
- o folder-hook [!]regexp command
-
- o group [ -group name ...] { -rx expr ... | -addr expr ... }
-
- o ungroup [ -group name ...] { * | -rx expr ... | -addr expr ... }
-
- o hdr_order header [ header ...]
-
- o unhdr_order { * | header ... }
-
- o ignore pattern [ pattern ...]
-
- o unignore { * | pattern ... }
-
- o lists [ -group name ] regexp [ regexp ...]
-
- o unlists [ -group name ...] { * | regexp ... }
-
- o macro menu key sequence [ description ]
-
- o mailboxes mailbox [ mailbox ...]
-
- o unmailboxes { * | mailbox ... }
-
- o mbox-hook [!]pattern mailbox
-
- o message-hook [!]pattern command
-
- o mime-lookup mimetype [ mimetype ...]
-
- o unmime-lookup { * | mimetype ... }
-
- o mono object attribute
-
- mono { header | body } attribute regexp
-
- mono index attribute pattern
-
- o unmono index { * | pattern ... }
-
- o my_hdr string
-
- o unmy_hdr { * | field ... }
-
- o crypt-hook pattern keyid
-
- o push string
-
- o reset variable [ variable ...]
-
- o save-hook [!]pattern mailbox
-
- o score pattern value
-
- o unscore { * | pattern ... }
-
- o reply-hook [!]pattern command
-
- o send-hook [!]pattern command
-
- o send2-hook [!]pattern command
-
- o set { [ no | inv ] variable | variable=value } [...]
-
- o unset variable [ variable ...]
-
- o source filename
-
- o spam pattern format
-
- o nospam { * | pattern }
-
- o subscribe [ -group name ...] regexp [ regexp ...]
-
- o unsubscribe [ -group name ...] { * | regexp ... }
-
- o toggle variable [ variable ...]
-
- o unhook { * | hook-type }
-
-3. Configuration variables
-
- 3.1. abort_nosubject
-
- Type: quadoption
- Default: ask-yes
-
- If set to yes, when composing messages and no subject is given at the
- subject prompt, composition will be aborted. If set to no, composing
- messages with no subject given at the subject prompt will never be
- aborted.
-
- 3.2. abort_unmodified
-
- Type: quadoption
- Default: yes
-
- If set to yes, composition will automatically abort after editing the
- message body if no changes are made to the file (this check only happens
- after the first edit of the file). When set to no, composition will never
- be aborted.
-
- 3.3. alias_file
-
- Type: path
- Default: "~/.muttrc"
-
- The default file in which to save aliases created by the <create-alias>
- function. Entries added to this file are encoded in the character set
- specified by $config_charset if it is set or the current character set
- otherwise.
-
- Note: Mutt will not automatically source this file; you must explicitly
- use the "source" command for it to be executed in case this option points
- to a dedicated alias file.
-
- The default for this option is the currently used muttrc file, or
- "~/.muttrc" if no user muttrc was found.
-
- 3.4. alias_format
-
- Type: string
- Default: "%4n %2f %t %-10a %r"
-
- Specifies the format of the data displayed for the "alias" menu. The
- following printf(3)-style sequences are available:
-
- %a
-
- alias name
-
- %f
-
- flags - currently, a "d" for an alias marked for deletion
-
- %n
-
- index number
-
- %r
-
- address which alias expands to
-
- %t
-
- character which indicates if the alias is tagged for inclusion
-
- 3.5. allow_8bit
-
- Type: boolean
- Default: yes
-
- Controls whether 8-bit data is converted to 7-bit using either Quoted-
- Printable or Base64 encoding when sending mail.
-
- 3.6. allow_ansi
-
- Type: boolean
- Default: no
-
- Controls whether ANSI color codes in messages (and color tags in rich text
- messages) are to be interpreted. Messages containing these codes are rare,
- but if this option is set, their text will be colored accordingly. Note
- that this may override your color choices, and even present a security
- problem, since a message could include a line like
-
- [-- PGP output follows ...
-
-
- and give it the same color as your attachment color (see also
- $crypt_timestamp).
-
- 3.7. arrow_cursor
-
- Type: boolean
- Default: no
-
- When set, an arrow ("->") will be used to indicate the current entry in
- menus instead of highlighting the whole line. On slow network or modem
- links this will make response faster because there is less that has to be
- redrawn on the screen when moving to the next or previous entries in the
- menu.
-
- 3.8. ascii_chars
-
- Type: boolean
- Default: no
-
- If set, Mutt will use plain ASCII characters when displaying thread and
- attachment trees, instead of the default ACS characters.
-
- 3.9. askbcc
-
- Type: boolean
- Default: no
-
- If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before
- editing an outgoing message.
-
- 3.10. askcc
-
- Type: boolean
- Default: no
-
- If set, Mutt will prompt you for carbon-copy (Cc) recipients before
- editing the body of an outgoing message.
-
- 3.11. assumed_charset
-
- Type: string
- Default: (empty)
-
- This variable is a colon-separated list of character encoding schemes for
- messages without character encoding indication. Header field values and
- message body content without character encoding indication would be
- assumed that they are written in one of this list. By default, all the
- header fields and message body without any charset indication are assumed
- to be in "us-ascii".
-
- For example, Japanese users might prefer this:
-
- set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-
- However, only the first content is valid for the message body.
-
- 3.12. attach_charset
-
- Type: string
- Default: (empty)
-
- This variable is a colon-separated list of character encoding schemes for
- text file attachments. Mutt uses this setting to guess which encoding
- files being attached are encoded in to convert them to a proper character
- set given in $send_charset.
-
- If unset, the value of $charset will be used instead. For example, the
- following configuration would work for Japanese text handling:
-
- set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-
- Note: for Japanese users, "iso-2022-*" must be put at the head of the
- value as shown above if included.
-
- 3.13. attach_format
-
- Type: string
- Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
-
- This variable describes the format of the "attachment" menu. The following
- printf(3)-style sequences are understood:
-
- %C
-
- charset
-
- %c
-
- requires charset conversion ("n" or "c")
-
- %D
-
- deleted flag
-
- %d
-
- description
-
- %e
-
- MIME content-transfer-encoding
-
- %f
-
- filename
-
- %I
-
- disposition ("I" for inline, "A" for attachment)
-
- %m
-
- major MIME type
-
- %M
-
- MIME subtype
-
- %n
-
- attachment number
-
- %Q
-
- "Q", if MIME part qualifies for attachment counting
-
- %s
-
- size
-
- %t
-
- tagged flag
-
- %T
-
- graphic tree characters
-
- %u
-
- unlink (=to delete) flag
-
- %X
-
- number of qualifying MIME parts in this part and its children
- (please see the "attachments" section for possible speed effects)
-
- %>X
-
- right justify the rest of the string and pad with character "X"
-
- %|X
-
- pad to the end of the line with character "X"
-
- %*X
-
- soft-fill with character "X" as pad
-
- For an explanation of "soft-fill", see the $index_format documentation.
-
- 3.14. attach_sep
-
- Type: string
- Default: "\n"
-
- The separator to add between attachments when operating (saving, printing,
- piping, etc) on a list of tagged attachments.
-
- 3.15. attach_split
-
- Type: boolean
- Default: yes
-
- If this variable is unset, when operating (saving, printing, piping, etc)
- on a list of tagged attachments, Mutt 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 will operate on the
- attachments one by one.
-
- 3.16. attribution
-
- Type: string
- Default: "On %d, %n wrote:"
-
- This is the string that will precede a message which has been included in
- a reply. For a full listing of defined printf(3)-like sequences see the
- section on $index_format.
-
- 3.17. autoedit
-
- Type: boolean
- Default: no
-
- When set along with $edit_headers, Mutt will skip the initial send-menu
- (prompting for subject and recipients) and allow you to immediately begin
- editing the body of your message. The send-menu may still be accessed once
- you have finished editing the body of your message.
-
- Also see $fast_reply.
-
- 3.18. auto_tag
-
- Type: boolean
- Default: no
-
- When set, functions in the index menu which affect a message will be
- applied to all tagged messages (if there are any). When unset, you must
- first use the <tag-prefix> function (bound to ";" by default) to make the
- next function apply to all tagged messages.
-
- 3.19. beep
-
- Type: boolean
- Default: yes
-
- When this variable is set, mutt will beep when an error occurs.
-
- 3.20. beep_new
-
- Type: boolean
- Default: no
-
- When this variable is set, mutt will beep whenever it prints a message
- notifying you of new mail. This is independent of the setting of the $beep
- variable.
-
- 3.21. bounce
-
- Type: quadoption
- Default: ask-yes
-
- Controls whether you will be asked to confirm bouncing messages. If set to
- yes you don't get asked if you want to bounce a message. Setting this
- variable to no is not generally useful, and thus not recommended, because
- you are unable to bounce messages.
-
- 3.22. bounce_delivered
-
- Type: boolean
- Default: yes
-
- When this variable is set, mutt will include Delivered-To headers when
- bouncing messages. Postfix users may wish to unset this variable.
-
- Note: On Debian systems, this option is unset by default in /etc/Muttrc.
-
- 3.23. braille_friendly
-
- Type: boolean
- Default: no
-
- When this variable is set, mutt will place the cursor at the beginning of
- the current line in menus, even when the $arrow_cursor variable is unset,
- making it easier for blind persons using Braille displays to follow these
- menus. The option is unset by default because many visual terminals don't
- permit making the cursor invisible.
-
- 3.24. check_mbox_size
-
- Type: boolean
- Default: no
-
- When this variable is set, mutt will use file size attribute instead of
- access time when checking for new mail in mbox and mmdf folders.
-
- This variable is unset by default and should only be enabled when new mail
- detection for these folder types is unreliable or doesn't work.
-
- Note that enabling this variable should happen before any "mailboxes"
- directives occur in configuration files regarding mbox or mmdf folders
- because mutt needs to determine the initial new mail status of such a
- mailbox by performing a fast mailbox scan when it is defined. Afterwards
- the new mail status is tracked by file size changes.
-
- 3.25. charset
-
- Type: string
- Default: (empty)
-
- Character set your terminal uses to display and enter textual data. It is
- also the fallback for $send_charset.
-
- Upon startup Mutt tries to derive this value from environment variables
- such as $LC_CTYPE or $LANG.
-
- Note: It should only be set in case Mutt isn't abled to determine the
- character set used correctly.
-
- 3.26. check_new
-
- Type: boolean
- Default: yes
-
- Note: this option only affects maildir and MH style mailboxes.
-
- When set, Mutt 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 this variable is unset, no check
- for new mail is performed while the mailbox is open.
-
- 3.27. collapse_unread
-
- Type: boolean
- Default: yes
-
- When unset, Mutt will not collapse a thread if it contains any unread
- messages.
-
- 3.28. uncollapse_jump
-
- Type: boolean
- Default: no
-
- When set, Mutt will jump to the next unread message, if any, when the
- current thread is uncollapsed.
-
- 3.29. compose_format
-
- Type: string
- Default: "-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-"
-
- Controls the format of the status line displayed in the "compose" menu.
- This string is similar to $status_format, but has its own set of
- printf(3)-like sequences:
-
- %a
-
- total number of attachments
-
- %h
-
- local hostname
-
- %l
-
- approximate size (in bytes) of the current message
-
- %v
-
- Mutt version string
-
- See the text describing the $status_format option for more information on
- how to set $compose_format.
-
- 3.30. config_charset
-
- Type: string
- Default: (empty)
-
- When defined, Mutt will recode commands in rc files from this encoding to
- the current character set as specified by $charset and aliases written to
- $alias_file from the current character set.
-
- Please note that if setting $charset it must be done before setting
- $config_charset.
-
- Recoding should be avoided as it may render unconvertable characters as
- question marks which can lead to undesired side effects (for example in
- regular expressions).
-
- 3.31. confirmappend
-
- Type: boolean
- Default: yes
-
- When set, Mutt will prompt for confirmation when appending messages to an
- existing mailbox.
-
- 3.32. confirmcreate
-
- Type: boolean
- Default: yes
-
- When set, Mutt will prompt for confirmation when saving messages to a
- mailbox which does not yet exist before creating it.
-
- 3.33. connect_timeout
-
- Type: number
- Default: 30
-
- Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after
- this many seconds if the connection is not able to be established. A
- negative value causes Mutt to wait indefinitely for the connection attempt
- to succeed.
-
- 3.34. content_type
-
- Type: string
- Default: "text/plain"
-
- Sets the default Content-Type for the body of newly composed messages.
-
- 3.35. copy
-
- Type: quadoption
- Default: yes
-
- 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".
-
- 3.36. crypt_use_gpgme
-
- Type: boolean
- Default: no
-
- This variable controls the use of the GPGME-enabled crypto backends. If it
- is set and Mutt was built with gpgme support, the gpgme code for S/MIME
- and PGP will be used instead of the classic code. Note that you need to
- set this option in .muttrc; it won't have any effect when used
- interactively.
-
- 3.37. crypt_use_pka
-
- Type: boolean
- Default: no
-
- Controls whether mutt uses PKA (see
- http://www.g10code.de/docs/pka-intro.de.pdf) during signature verification
- (only supported by the GPGME backend).
-
- 3.38. crypt_autopgp
-
- Type: boolean
- Default: yes
-
- This variable controls whether or not mutt may automatically enable PGP
- encryption/signing for messages. See also $crypt_autoencrypt,
- $crypt_replyencrypt, $crypt_autosign, $crypt_replysign and
- $smime_is_default.
-
- 3.39. crypt_autosmime
-
- Type: boolean
- Default: yes
-
- This variable controls whether or not mutt may automatically enable S/MIME
- encryption/signing for messages. See also $crypt_autoencrypt,
- $crypt_replyencrypt, $crypt_autosign, $crypt_replysign and
- $smime_is_default.
-
- 3.40. date_format
-
- Type: string
- Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
-
- This variable controls the format of the date printed by the "%d" sequence
- in $index_format. This is passed to the strftime(3) function to process
- the date, see the man page for the proper syntax.
-
- 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).
-
- 3.41. default_hook
-
- Type: string
- Default: "~f %s !~P | (~P ~C %s)"
-
- This variable controls how "message-hook", "reply-hook", "send-hook",
- "send2-hook", "save-hook", and "fcc-hook" 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.
-
- 3.42. delete
-
- 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.
-
- 3.43. delete_untag
-
- Type: boolean
- Default: yes
-
- If this option is set, mutt 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.
-
- 3.44. digest_collapse
-
- Type: boolean
- Default: yes
-
- If this option is set, mutt'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.
-
- 3.45. display_filter
-
- Type: path
- Default: (empty)
-
- 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.
-
- 3.46. dotlock_program
-
- Type: path
- Default: "/usr/bin/mutt_dotlock"
-
- Contains the path of the mutt_dotlock(8) binary to be used by mutt.
-
- 3.47. dsn_notify
-
- Type: string
- Default: (empty)
-
- 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.
-
- Example:
-
- set dsn_notify="failure,delay"
-
-
- Note: when using $sendmail for delivery, you should not enable this unless
- you are either using Sendmail 8.8.x or greater or a MTA providing a
- sendmail(1)-compatible interface supporting the -N option for DSN. For
- SMTP delivery, DSN support is autodetected so that it depends on the
- server whether DSN will be used or not.
-
- 3.48. dsn_return
-
- Type: string
- Default: (empty)
-
- 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.
-
- Example:
-
- set dsn_return=hdrs
-
-
- Note: when using $sendmail for delivery, you should not enable this unless
- you are either using Sendmail 8.8.x or greater or a MTA providing a
- sendmail(1)-compatible interface supporting the -R option for DSN. For
- SMTP delivery, DSN support is autodetected so that it depends on the
- server whether DSN will be used or not.
-
- 3.49. duplicate_threads
-
- Type: boolean
- Default: yes
-
- This variable controls whether mutt, when $sort is set to threads, threads
- messages with the same Message-Id together. If it is set, it will indicate
- that it thinks they are duplicates of each other with an equals sign in
- the thread tree.
-
- 3.50. edit_headers
-
- Type: boolean
- Default: no
-
- This option allows you to edit the header of your outgoing messages along
- with the body of your message.
-
- Note that changes made to the References: and Date: headers are ignored
- for interoperability reasons.
-
- 3.51. editor
-
- Type: path
- Default: (empty)
-
- This variable specifies which editor is used by mutt. It defaults to the
- value of the $VISUAL, or $EDITOR, environment variable, or to the string
- "/usr/bin/editor" if neither of those are set.
-
- 3.52. encode_from
-
- Type: boolean
- Default: no
-
- When set, mutt will quoted-printable encode messages when they contain the
- string "From " (note the trailing space) in the beginning of a line. This
- is useful to avoid the tampering certain mail delivery and transport
- agents tend to do with messages (in order to prevent tools from
- misinterpreting the line as a mbox message separator).
-
- 3.53. envelope_from_address
-
- Type: e-mail address
- Default: (empty)
-
- Manually sets the envelope sender for outgoing messages. This value is
- ignored if $use_envelope_from is unset.
-
- 3.54. escape
-
- Type: string
- Default: "~"
-
- Escape character to use for functions in the builtin editor.
-
- 3.55. fast_reply
-
- Type: boolean
- Default: no
-
- 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.
-
- Note: this variable has no effect when the $autoedit variable is set.
-
- 3.56. fcc_attach
-
- Type: boolean
- Default: yes
-
- This variable controls whether or not attachments on outgoing messages are
- saved along with the main body of your message.
-
- 3.57. fcc_clear
-
- Type: boolean
- Default: no
-
- When this variable is set, FCCs will be stored unencrypted and unsigned,
- even when the actual message is encrypted and/or signed. (PGP only)
-
- 3.58. folder
-
- Type: path
- Default: "~/Mail"
-
- 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 when handling the "mailboxes"
- command.
-
- 3.59. folder_format
-
- Type: string
- Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
-
- 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:
-
- %C
-
- current file number
-
- %d
-
- date/time folder was last modified
-
- %f
-
- filename
-
- %F
-
- file permissions
-
- %g
-
- group name (or numeric gid, if missing)
-
- %l
-
- number of hard links
-
- %N
-
- N if folder has new mail, blank otherwise
-
- %s
-
- size in bytes
-
- %t
-
- "*" 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"
-
- %*X
-
- soft-fill with character "X" as pad
-
- For an explanation of "soft-fill", see the $index_format documentation.
-
- 3.60. followup_to
-
- Type: boolean
- Default: yes
-
- Controls whether or not the "Mail-Followup-To:" header field is generated
- when sending mail. When set, Mutt will generate this field when you are
- replying to a known mailing list, specified with the "subscribe" or
- "lists" commands.
-
- This field has two purposes. First, preventing you from receiving
- duplicate copies of replies to messages which you send to mailing lists,
- and 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.
-
- 3.61. force_name
-
- Type: boolean
- Default: no
-
- This variable is similar to $save_name, except that Mutt 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.
-
- 3.62. forward_decode
-
- Type: boolean
- Default: yes
-
- 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.
-
- 3.63. 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".
-
- 3.64. forward_format
-
- 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.
-
- 3.65. 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.
-
- 3.66. from
-
- Type: e-mail address
- Default: (empty)
-
- When set, this variable contains a default from address. It can be
- overridden using "my_hdr" (including from a "send-hook") and
- $reverse_name. This variable is ignored if $use_from is unset.
-
- This setting defaults to the contents of the environment variable $EMAIL.
-
- 3.67. gecos_mask
-
- Type: regular expression
- Default: "^[^,]*"
-
- A regular expression used by mutt to parse the GECOS field of a password
- entry when expanding the alias. The default value will return the string
- up to the first "," encountered. If the GECOS field contains a string like
- "lastname, firstname" then you should set it to ".*".
-
- This can be useful if you see the following behavior: you address an
- e-mail to user ID "stevef" whose full name is "Steve Franklin". If mutt
- 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
- will expand "Franklin" to "Franklin, Steve".
-
- 3.68. 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.
-
- 3.69. header
-
- Type: boolean
- Default: no
-
- When set, this variable causes Mutt to include the header of the message
- you are replying to into the edit buffer. The $weed setting applies.
-
- 3.70. 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 is running. Since this
- variable is primarily aimed at new users, neither of these should present
- a major problem.
-
- 3.71. hidden_host
-
- Type: boolean
- Default: no
-
- When set, mutt 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-IDs, and it will not lead to the cut-off of
- first-level domains.
-
- 3.72. hide_limited
-
- Type: boolean
- Default: no
-
- When set, mutt will not show the presence of messages that are hidden by
- limiting, in the thread tree.
-
- 3.73. hide_missing
-
- Type: boolean
- Default: yes
-
- When set, mutt will not show the presence of missing messages in the
- thread tree.
-
- 3.74. hide_thread_subject
-
- Type: boolean
- Default: yes
-
- When set, mutt will not show the subject of messages in the thread tree
- that have the same subject as their parent or closest previously displayed
- sibling.
-
- 3.75. hide_top_limited
-
- Type: boolean
- Default: no
-
- When set, mutt 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_limited is set, this option will have no effect.
-
- 3.76. hide_top_missing
-
- Type: boolean
- Default: yes
-
- When set, mutt will not show the presence of missing messages at the top
- of threads in the thread tree. Note that when $hide_missing is set, this
- option will have no effect.
-
- 3.77. history
-
- Type: number
- Default: 10
-
- This variable controls the size (in number of strings remembered) of the
- string history buffer per category. The buffer is cleared each time the
- variable is set.
-
- 3.78. history_file
-
- Type: path
- Default: "~/.mutthistory"
-
- The file in which Mutt will save its history.
-
- 3.79. honor_followup_to
-
- Type: quadoption
- Default: yes
-
- This variable controls whether or not a Mail-Followup-To header is honored
- when group-replying to a message.
-
- 3.80. hostname
-
- Type: string
- Default: (empty)
-
- Specifies the fully-qualified hostname of the system mutt is running on
- containing the host's name and the DNS domain it belongs to. It is used as
- the domain part (after "@") for local email addresses as well as
- Message-Id headers.
-
- Its value is determined at startup as follows: If the node's name as
- returned by the uname(3) function contains the hostname and the domain,
- these are used to construct $hostname. If there is no domain part
- returned, Mutt will look for a "domain" or "search" line in
- /etc/resolv.conf to determine the domain. Optionally, Mutt can be compiled
- with a fixed domain name in which case a detected one is not used.
-
- Also see $use_domain and $hidden_host.
-
- Note: On Debian systems, the default for this variable is obtained from
- /etc/mailname when Mutt starts.
-
- 3.81. ignore_linear_white_space
-
- Type: boolean
- Default: no
-
- This option replaces linear-white-space between encoded-word and text to a
- single space to prevent the display of MIME-encoded "Subject:" field from
- being divided into multiple lines.
-
- 3.82. ignore_list_reply_to
-
- Type: boolean
- Default: no
-
- Affects the behaviour of the <reply> function when replying to messages
- from mailing lists (as defined by the "subscribe" or "lists" commands).
- When set, if the "Reply-To:" field is set to the same value as the "To:"
- field, Mutt assumes that the "Reply-To:" 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.
-
- 3.83. imap_authenticators
-
- Type: string
- Default: (empty)
-
- This is a colon-delimited list of authentication methods mutt may attempt
- to use to log in to an IMAP server, in the order mutt should try them.
- Authentication methods are either "login" or the right side of an IMAP
- "AUTH=xxx" capability string, eg "digest-md5", "gssapi" or "cram-md5".
- This option is case-insensitive. If it's unset (the default) mutt will try
- all available methods, in order from most-secure to least-secure.
-
- Example:
-
- set imap_authenticators="gssapi:cram-md5:login"
-
-
- Note: Mutt will only fall back to other authentication methods if the
- previous methods are unavailable. If a method is available but
- authentication fails, mutt will not connect to the IMAP server.
-
- 3.84. imap_check_subscribed
-
- 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
- just as if you had issued individual "mailboxes" commands.
-
- 3.85. imap_delim_chars
-
- Type: string
- Default: "/."
-
- 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.
-
- 3.86. imap_headers
-
- Type: string
- Default: (empty)
-
- Mutt 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:", "List-Post:", "X-Label:") from IMAP servers before displaying
- the index menu. You may want to add more headers for spam detection.
-
- Note: This is a space separated list, items should be uppercase and not
- contain the colon, e.g. "X-BOGOSITY X-SPAM-STATUS" for the "X-Bogosity:"
- and "X-Spam-Status:" header fields.
-
- 3.87. imap_idle
-
- Type: boolean
- Default: no
-
- When set, mutt will attempt to use the IMAP IDLE extension to check for
- new mail in the current mailbox. Some servers (dovecot was the inspiration
- for this option) react badly to mutt's implementation. If your connection
- seems to freeze up periodically, try unsetting this.
-
- 3.88. imap_keepalive
-
- Type: number
- Default: 900
-
- This variable specifies the maximum amount of time in seconds that mutt
- will wait before polling open IMAP connections, to prevent the server from
- closing them before mutt 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.
-
- 3.89. imap_list_subscribed
-
- Type: boolean
- Default: no
-
- 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.
-
- 3.90. imap_login
-
- Type: string
- Default: (empty)
-
- Your login name on the IMAP server.
-
- This variable defaults to the value of $imap_user.
-
- 3.91. imap_pass
-
- Type: string
- Default: (empty)
-
- Specifies the password for your IMAP account. If unset, Mutt will prompt
- you for your password when you invoke the <fetch-mail> function or try to
- open an IMAP folder.
-
- Warning: you should only use this option when you are on a fairly secure
- machine, because the superuser can read your muttrc even if you are the
- only one who can read the file.
-
- 3.92. imap_passive
-
- Type: boolean
- Default: yes
-
- When set, mutt will not open new IMAP connections to check for new mail.
- Mutt 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
- invocation, or if opening the connection is slow.
-
- 3.93. imap_peek
-
- Type: boolean
- Default: yes
-
- When set, mutt 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.
-
- 3.94. imap_pipeline_depth
-
- Type: number
- Default: 15
-
- Controls the number of IMAP commands that may be queued up before they are
- sent to the server. A deeper pipeline reduces the amount of time mutt must
- wait for the server, and can make IMAP servers feel much more responsive.
- But not all servers correctly handle pipelined commands, so if you have
- problems you might want to try setting this variable to 0.
-
- Note: Changes to this variable have no effect on open connections.
-
- 3.95. imap_servernoise
-
- Type: boolean
- Default: yes
-
- When set, mutt 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.
-
- 3.96. imap_user
-
- Type: string
- Default: (empty)
-
- 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.
-
- 3.97. implicit_autoview
-
- Type: boolean
- Default: no
-
- If set to "yes", mutt 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 will use the
- viewer defined in that entry to convert the body part to text form.
-
- 3.98. 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.
-
- 3.99. include_onlyfirst
-
- Type: boolean
- Default: no
-
- Controls whether or not Mutt includes only the first attachment of the
- message you are replying.
-
- 3.100. 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.
-
- This option is a format string, please see the description of
- $index_format for supported printf(3)-style sequences.
-
- Because for format=lowed style messages the quoting mechanism is strictly
- defined, this setting is ignored if $text_flowed is set.
-
- 3.101. 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 details). The
- following sequences are defined in Mutt:
-
- %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
-
- sender (address + real name), either From: or Return-Path:
-
- %F
-
- author name, or recipient name if the message is from you
-
- %H
-
- spam attribute(s) of this message
-
- %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
-
- original save folder where mutt would formerly have stashed the
- message: list name or recipient name if not sent to a list
-
- %P
-
- progress indicator for the builtin pager (how much of the file has
- been displayed)
-
- %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
-
- %X
-
- number of attachments (please see the "attachments" section for
- possible speed effects)
-
- %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(3); 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(3); a
- leading bang disables locales
-
- %(fmt)
-
- the local date and time when the message was received. "fmt" is
- expanded by the library function strftime(3); a leading bang
- disables locales
-
- %<fmt>
-
- the current local time. "fmt" is expanded by the library function
- strftime(3); 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"
-
- %*X
-
- soft-fill with character "X" as pad
-
- "Soft-fill" deserves some explanation: Normal right-justification will
- print everything to the left of the "%>", displaying padding and whatever
- lies to the right only if there's room. By contrast, soft-fill gives
- priority to the right-hand side, guaranteeing space to display it and
- showing padding only if there's still room. If necessary, soft-fill will
- eat text leftwards to make room for rightward text.
-
- Note that these expandos are supported in "save-hook", "fcc-hook" and
- "fcc-save-hook", too.
-
- 3.102. ispell
-
- Type: path
- Default: "ispell"
-
- How to invoke ispell (GNU's spell-checking software).
-
- 3.103. 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.
-
- 3.104. 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 environment variable $LC_TIME.
-
- 3.105. mail_check
-
- Type: number
- Default: 5
-
- This variable configures how often (in seconds) mutt should look for new
- mail. Also see the $timeout variable.
-
- 3.106. mailcap_path
-
- Type: string
- Default: (empty)
-
- This variable specifies which files to consult when attempting to display
- MIME bodies not directly supported by Mutt.
-
- 3.107. mailcap_sanitize
-
- Type: boolean
- Default: yes
-
- If set, mutt 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!
-
- 3.108. maildir_mtime
-
- Type: boolean
- Default: no
-
- If set, the sort-by-date option in the browser will sort maildirs smartly,
- not using the mtime of the maildir itself but that of the newest message
- in the new subdirectory, making the sorting by reverse date much more
- useful. People with maildirs over NFS may wish to leave this option unset.
-
- 3.109. header_cache
-
- Type: path
- Default: (empty)
-
- This variable points to the header cache database. If pointing to a
- directory Mutt will contain a header cache database file per folder, if
- pointing to a file that file will be a single global header cache. By
- default it is unset so no header caching will be used.
-
- Header caching can greatly improve speed when opening POP, IMAP MH or
- Maildir folders, see "caching" for details.
-
- 3.110. maildir_header_cache_verify
-
- Type: boolean
- Default: yes
-
- Check for Maildir unaware programs other than mutt having modified maildir
- files when the header cache is in use. This incurs one stat(2) per message
- every time the folder is opened (which can be very slow for NFS folders).
-
- 3.111. header_cache_pagesize
-
- Type: string
- Default: "16384"
-
- When mutt is compiled with either gdbm or bdb4 as the header cache
- backend, this option changes the database page size. Too large or too
- small values can waste space, memory, or CPU time. The default should be
- more or less optimal for most use cases.
-
- 3.112. maildir_trash
-
- Type: boolean
- Default: no
-
- If set, messages marked as deleted will be saved with the maildir trashed
- flag instead of unlinked. Note: this only applies to maildir-style
- mailboxes. Setting it will have no effect on other mailbox types.
-
- 3.113. mark_old
-
- Type: boolean
- Default: yes
-
- Controls whether or not mutt marks new unread messages as old if you exit
- a mailbox without reading them. With this option set, the next time you
- start mutt, the messages will show up with an "O" next to them in the
- index menu, indicating that they are old.
-
- 3.114. 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.
-
- 3.115. 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.
-
- 3.116. mbox
-
- Type: path
- Default: "~/mbox"
-
- This specifies the folder into which read mail in your $spoolfile folder
- will be appended.
-
- Also see the $move variable.
-
- 3.117. 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".
-
- 3.118. metoo
-
- Type: boolean
- Default: no
-
- If unset, Mutt will remove your address (see the "alternates" command)
- from the list of recipients when replying to a message.
-
- 3.119. 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.)
-
- 3.120. 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.
-
- 3.121. 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).
-
- 3.122. meta_key
-
- Type: boolean
- Default: no
-
- If set, forces Mutt 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".
-
- 3.123. mh_purge
-
- Type: boolean
- Default: no
-
- When unset, mutt will mimic mh's behaviour and rename deleted messages to
- ,<old file name> in mh folders instead of really deleting them. This
- leaves the message on disk but makes programs reading the folder ignore
- it. If the variable is set, the message files will simply be deleted.
-
- This option is similar to $maildir_trash for Maildir folders.
-
- 3.124. mh_seq_flagged
-
- Type: string
- Default: "flagged"
-
- The name of the MH sequence used for flagged messages.
-
- 3.125. mh_seq_replied
-
- Type: string
- Default: "replied"
-
- The name of the MH sequence used to tag replied messages.
-
- 3.126. mh_seq_unseen
-
- Type: string
- Default: "unseen"
-
- The name of the MH sequence used for unseen messages.
-
- 3.127. mime_forward
-
- Type: quadoption
- Default: no
-
- When set, the message you are forwarding will be attached as a separate
- message/rfc822 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.
-
- 3.128. 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.
-
- 3.129. mime_forward_rest
-
- Type: quadoption
- Default: yes
-
- When forwarding multiple attachments of a MIME message from the attachment
- menu, attachments which cannot be decoded in a reasonable manner will be
- attached to the newly composed message if this option is set.
-
- 3.130. mix_entry_format
-
- Type: string
- Default: "%4n %c %-16s %a"
-
- 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.
-
- 3.131. mixmaster
-
- Type: path
- Default: "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.
-
- Note: On Debian systems, this option is set by default to
- "mixmaster-filter" in /etc/Muttrc.
-
- 3.132. move
-
- Type: quadoption
- Default: no
-
- Controls whether or not Mutt will move read messages from your spool
- mailbox to your $mbox mailbox, or as a result of a "mbox-hook" command.
-
- 3.133. message_cachedir
-
- Type: path
- Default: (empty)
-
- Set this to a directory and mutt will cache copies of messages from your
- IMAP and POP servers here. You are free to remove entries at any time.
-
- When setting this variable to a directory, mutt needs to fetch every
- remote message only once and can perform regular expression searches as
- fast as for local folders.
-
- Also see the $message_cache_clean variable.
-
- 3.134. message_cache_clean
-
- Type: boolean
- Default: no
-
- If set, mutt will clean out obsolete entries from the message cache when
- the mailbox is synchronized. You probably only want to set it every once
- in a while, since it can be a little slow (especially for large folders).
-
- 3.135. 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.
-
- 3.136. narrow_tree
-
- Type: boolean
- Default: no
-
- This variable, when set, makes the thread tree narrower, allowing deeper
- threads to fit on the screen.
-
- 3.137. 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, $write_inc and $net_inc.
-
- 3.138. pager
-
- Type: path
- Default: "builtin"
-
- This variable specifies which pager you would like to use to view
- messages. The value "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 functions directly from the
- pager, and screen resizes cause lines longer than the screen width to be
- badly formatted in the help menu.
-
- 3.139. 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 will display the line after the last one on the screen at the top of
- the next page (0 lines of context).
-
- 3.140. pager_format
-
- Type: string
- Default: "-%Z- %C/%m: %-20.20n %s%* -- (%P)"
-
- 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.
-
- 3.141. 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 setting 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.
-
- 3.142. 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.
-
- 3.143. crypt_autosign
-
- Type: boolean
- Default: no
-
- Setting this variable will cause Mutt 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
- instead of the pgp menu. (Crypto only)
-
- 3.144. crypt_autoencrypt
-
- Type: boolean
- Default: no
-
- Setting this variable will cause Mutt 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 instead.
- (Crypto only)
-
- 3.145. pgp_ignore_subkeys
-
- Type: boolean
- Default: yes
-
- Setting this variable will cause Mutt 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)
-
- 3.146. crypt_replyencrypt
-
- Type: boolean
- Default: yes
-
- If set, automatically PGP or OpenSSL encrypt replies to messages which are
- encrypted. (Crypto only)
-
- 3.147. crypt_replysign
-
- Type: boolean
- Default: no
-
- If set, automatically PGP or OpenSSL sign replies to messages which are
- signed.
-
- Note: this does not work on messages that are encrypted and signed!
- (Crypto only)
-
- 3.148. crypt_replysignencrypted
-
- Type: boolean
- Default: no
-
- 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 is not able to find out whether an encrypted message is also signed.
- (Crypto only)
-
- 3.149. crypt_timestamp
-
- Type: boolean
- Default: yes
-
- If set, mutt 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)
-
- 3.150. sidebar_delim
-
- Type: string
- Default: "|"
-
- This specifies the delimiter between the sidebar (if visible) and other
- screens.
-
- 3.151. sidebar_visible
-
- Type: boolean
- Default: no
-
- This specifies whether or not to show sidebar (left-side list of folders).
-
- 3.152. sidebar_width
-
- Type: number
- Default: 0
-
- The width of the sidebar.
-
- 3.153. pgp_use_gpg_agent
-
- Type: boolean
- Default: no
-
- If set, mutt will use a possibly-running gpg-agent(1) process. (PGP only)
-
- 3.154. crypt_verify_sig
-
- Type: quadoption
- Default: yes
-
- If "yes", always attempt to verify PGP or S/MIME signatures. If "ask-*",
- ask whether or not to verify the signature. If \Fi"no", never attempt to
- verify cryptographic signatures. (Crypto only)
-
- 3.155. smime_is_default
-
- Type: boolean
- Default: no
-
- The default behaviour of mutt 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 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)
-
- 3.156. 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)
-
- 3.157. smime_decrypt_use_default_key
-
- Type: boolean
- Default: yes
-
- If set (default) this tells mutt to use the default key for decryption.
- Otherwise, if managing multiple certificate-key-pairs, mutt 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)
-
- 3.158. 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)
-
- 3.159. pgp_good_sign
-
- Type: regular expression
- Default: (empty)
-
- 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)
-
- 3.160. pgp_check_exit
-
- Type: boolean
- Default: yes
-
- If set, mutt 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)
-
- 3.161. pgp_long_ids
-
- Type: boolean
- Default: no
-
- If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs.
- (PGP only)
-
- 3.162. 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)
-
- 3.163. pgp_autoinline
-
- Type: boolean
- Default: no
-
- This option controls whether Mutt 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 might automatically use PGP/MIME for messages which consist
- of more than a single MIME part. Mutt can be configured to ask before
- sending PGP/MIME messages when inline (traditional) would not work.
-
- Also see the $pgp_mime_auto variable.
-
- Also note that using the old-style PGP message format is strongly
- deprecated. (PGP only)
-
- 3.164. pgp_replyinline
-
- Type: boolean
- Default: no
-
- Setting this variable will cause Mutt 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 internals
- for previously checked/flagged messages.
-
- Note that Mutt might automatically use PGP/MIME for messages which consist
- of more than a single MIME part. Mutt can be configured to ask before
- sending PGP/MIME messages when inline (traditional) would not work.
-
- Also see the $pgp_mime_auto variable.
-
- Also note that using the old-style PGP message format is strongly
- deprecated. (PGP only)
-
- 3.165. pgp_show_unusable
-
- Type: boolean
- Default: yes
-
- If set, mutt 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)
-
- 3.166. pgp_sign_as
-
- Type: string
- Default: (empty)
-
- 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)
-
- 3.167. pgp_strict_enc
-
- Type: boolean
- Default: yes
-
- If set, Mutt 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)
-
- 3.168. pgp_timeout
-
- Type: number
- Default: 300
-
- The number of seconds after which a cached passphrase will expire if not
- used. (PGP only)
-
- 3.169. pgp_sort_keys
-
- Type: sort order
- Default: address
-
- Specifies how the entries in the pgp 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)
-
- 3.170. pgp_mime_auto
-
- Type: quadoption
- Default: ask-yes
-
- This option controls whether Mutt 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 strongly
- deprecated. (PGP only)
-
- 3.171. pgp_auto_decode
-
- Type: boolean
- Default: no
-
- If set, mutt 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 will automatically
- check the message for traditional pgp.
-
- 3.172. pgp_mime_signature_filename
-
- Type: string
- Default: "signature.asc"
-
- This option sets the filename used for signature parts in PGP/MIME signed
- messages.
-
- 3.173. pgp_mime_signature_description
-
- Type: string
- Default: "Digital signature"
-
- This option sets the Content-Description used for signature parts in
- PGP/MIME signed messages.
-
- 3.174. pgp_decode_command
-
- Type: string
- Default: (empty)
-
- 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 and gpg sample configuration
- files in the samples/ subdirectory which has been installed on your system
- alongside the documentation. (PGP only)
-
- 3.175. pgp_getkeys_command
-
- Type: string
- Default: (empty)
-
- This command is invoked whenever mutt will need public key information. Of
- the sequences supported by $pgp_decode_command, %r is the only
- printf(3)-like sequence used with this format. (PGP only)
-
- 3.176. pgp_verify_command
-
- Type: string
- Default: (empty)
-
- This command is used to verify PGP signatures.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.177. pgp_decrypt_command
-
- Type: string
- Default: (empty)
-
- This command is used to decrypt a PGP encrypted message.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.178. pgp_clearsign_command
-
- Type: string
- Default: (empty)
-
- This format is used to create an old-style "clearsigned" PGP message. Note
- that the use of this format is strongly deprecated.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.179. pgp_sign_command
-
- Type: string
- Default: (empty)
-
- This command is used to create the detached PGP signature for a
- multipart/signed PGP/MIME body part.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.180. pgp_encrypt_sign_command
-
- Type: string
- Default: (empty)
-
- This command is used to both sign and encrypt a body part.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.181. pgp_encrypt_only_command
-
- Type: string
- Default: (empty)
-
- This command is used to encrypt a body part without signing it.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.182. pgp_import_command
-
- Type: string
- Default: (empty)
-
- This command is used to import a key from a message into the user's public
- key ring.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.183. pgp_export_command
-
- Type: string
- Default: (empty)
-
- This command is used to export a public key from the user's key ring.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.184. pgp_verify_key_command
-
- Type: string
- Default: (empty)
-
- This command is used to verify key information from the key selection
- menu.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.185. pgp_list_secring_command
-
- Type: string
- Default: (empty)
-
- 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.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.186. pgp_list_pubring_command
-
- Type: string
- Default: (empty)
-
- 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.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.187. forward_decrypt
-
- 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)
-
- 3.188. smime_timeout
-
- Type: number
- Default: 300
-
- The number of seconds after which a cached passphrase will expire if not
- used. (S/MIME only)
-
- 3.189. smime_encrypt_with
-
- Type: string
- Default: (empty)
-
- This sets the algorithm that should be used for encryption. Valid choices
- are "des", "des3", "rc2-40", "rc2-64", "rc2-128". If unset, "3des"
- (TripleDES) is used. (S/MIME only)
-
- 3.190. smime_keys
-
- Type: path
- Default: (empty)
-
- Since for S/MIME there is no pubring/secring as with PGP, mutt has to
- handle storage and 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 option points to the location of the private keys. (S/MIME
- only)
-
- 3.191. smime_ca_location
-
- Type: path
- Default: (empty)
-
- This variable contains the name of either a directory, or a file which
- contains trusted certificates for use with OpenSSL. (S/MIME only)
-
- Note: On Debian systems, this defaults to the first existing file in the
- following list: ~/.smime/ca-certificates.crt ~/.smime/ca-bundle.crt
- /etc/ssl/certs/ca-certificates.crt.
-
- 3.192. smime_certificates
-
- Type: path
- Default: (empty)
-
- Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to the location of the certificates. (S/MIME
- only)
-
- 3.193. smime_decrypt_command
-
- Type: string
- Default: (empty)
-
- 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)
-
- 3.194. smime_verify_command
-
- Type: string
- Default: (empty)
-
- This command is used to verify S/MIME signatures of type multipart/signed.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.195. smime_verify_opaque_command
-
- Type: string
- Default: (empty)
-
- This command is used to verify S/MIME signatures of type
- application/x-pkcs7-mime.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.196. smime_sign_command
-
- Type: string
- Default: (empty)
-
- This command is used to created S/MIME signatures of type
- multipart/signed, which can be read by all mail clients.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.197. smime_sign_opaque_command
-
- Type: string
- Default: (empty)
-
- 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.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.198. smime_encrypt_command
-
- Type: string
- Default: (empty)
-
- This command is used to create encrypted S/MIME messages.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.199. smime_pk7out_command
-
- Type: string
- Default: (empty)
-
- This command is used to extract PKCS7 structures of S/MIME signatures, in
- order to extract the public X509 certificate(s).
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.200. smime_get_cert_command
-
- Type: string
- Default: (empty)
-
- This command is used to extract X509 certificates from a PKCS7 structure.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.201. smime_get_signer_cert_command
-
- Type: string
- Default: (empty)
-
- 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:" field.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.202. smime_import_cert_command
-
- Type: string
- Default: (empty)
-
- This command is used to import a certificate via smime_keys.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.203. smime_get_cert_email_command
-
- Type: string
- Default: (empty)
-
- 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).
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.204. smime_default_key
-
- Type: string
- Default: (empty)
-
- 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)
-
- 3.205. ssl_client_cert
-
- Type: path
- Default: (empty)
-
- The file containing a client certificate and its associated private key.
-
- 3.206. ssl_force_tls
-
- Type: boolean
- Default: no
-
- If this variable is set, Mutt 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.
-
- 3.207. ssl_starttls
-
- Type: quadoption
- Default: yes
-
- If set (the default), mutt will attempt to use STARTTLS on servers
- advertising the capability. When unset, mutt will not attempt to use
- STARTTLS regardless of the server's capabilities.
-
- 3.208. certificate_file
-
- Type: path
- Default: "~/.mutt_certificates"
-
- This variable specifies the file where the certificates you trust are
- saved. When an unknown certificate is encountered, you are asked if you
- accept it or not. If you accept it, the certificate can also be saved in
- this file and further connections are automatically accepted.
-
- You can also manually add CA certificates in this file. Any server
- certificate that is signed with one of these CA certificates is also
- automatically accepted.
-
- Example:
-
- set certificate_file=~/.mutt/certificates
-
-
- 3.209. ssl_use_sslv3
-
- Type: boolean
- Default: yes
-
- This variable specifies whether to attempt to use SSLv3 in the SSL
- authentication process.
-
- 3.210. ssl_use_tlsv1
-
- Type: boolean
- Default: yes
-
- This variable specifies whether to attempt to use TLSv1 in the SSL
- authentication process.
-
- 3.211. ssl_min_dh_prime_bits
-
- Type: number
- Default: 0
-
- 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.
-
- 3.212. ssl_ca_certificates_file
-
- Type: path
- Default: (empty)
-
- This variable specifies a file containing trusted CA certificates. Any
- server certificate that is signed with one of these CA certificates is
- also automatically accepted.
-
- Example:
-
- set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-
- Note: On Debian systems, this variable defaults to the example mentioned.
- This file is managed by the "ca-certificates" package.
-
- 3.213. pipe_split
-
- Type: boolean
- Default: no
-
- Used in connection with the <pipe-message> function following
- <tag-prefix>. If this variable is unset, when piping a list of tagged
- messages Mutt will concatenate the messages and will pipe them all
- concatenated. When set, Mutt 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.
-
- 3.214. pipe_decode
-
- Type: boolean
- Default: no
-
- Used in connection with the <pipe-message> command. When unset, Mutt will
- pipe the messages without any preprocessing. When set, Mutt will weed
- headers and will attempt to decode the messages first.
-
- 3.215. pipe_sep
-
- Type: string
- Default: "\n"
-
- The separator to add between messages when piping a list of tagged
- messages to an external Unix command.
-
- 3.216. pop_authenticators
-
- Type: string
- Default: (empty)
-
- This is a colon-delimited list of authentication methods mutt may attempt
- to use to log in to an POP server, in the order mutt should try them.
- Authentication methods are either "user", "apop" or any SASL mechanism, eg
- "digest-md5", "gssapi" or "cram-md5". This option is case-insensitive. If
- this option is unset (the default) mutt will try all available methods, in
- order from most-secure to least-secure.
-
- Example:
-
- set pop_authenticators="digest-md5:apop:user"
-
-
- 3.217. pop_auth_try_all
-
- Type: boolean
- Default: yes
-
- If set, Mutt will try all available authentication methods. When unset,
- Mutt will only fall back to other authentication methods if the previous
- methods are unavailable. If a method is available but authentication
- fails, Mutt will not connect to the POP server.
-
- 3.218. pop_checkinterval
-
- Type: number
- Default: 60
-
- This variable configures how often (in seconds) mutt should look for new
- mail in the currently selected mailbox if it is a POP mailbox.
-
- 3.219. pop_delete
-
- Type: quadoption
- Default: ask-no
-
- If set, Mutt will delete successfully downloaded messages from the POP
- server when using the <fetch-mail> function. When unset, Mutt will
- download messages but also leave them on the POP server.
-
- 3.220. pop_host
-
- Type: string
- Default: (empty)
-
- The name of your POP server for the <fetch-mail> function. You can also
- specify an alternative port, username and password, ie:
-
- [pop[s]://][username[:password]@]popserver[:port]
-
-
- where "[...]" denotes an optional part.
-
- 3.221. pop_last
-
- Type: boolean
- Default: no
-
- If this variable is set, mutt will try to use the "LAST" POP command for
- retrieving only unread messages from the POP server when using the
- <fetch-mail> function.
-
- 3.222. pop_reconnect
-
- Type: quadoption
- Default: ask-yes
-
- Controls whether or not Mutt will try to reconnect to the POP server if
- the connection is lost.
-
- 3.223. pop_user
-
- Type: string
- Default: (empty)
-
- Your login name on the POP server.
-
- This variable defaults to your user name on the local machine.
-
- 3.224. pop_pass
-
- Type: string
- Default: (empty)
-
- Specifies the password for your POP account. If unset, Mutt will prompt
- you for your password when you open a POP mailbox.
-
- Warning: you should only use this option when you are on a fairly secure
- machine, because the superuser can read your muttrc even if you are the
- only one who can read the file.
-
- 3.225. post_indent_string
-
- Type: string
- Default: (empty)
-
- Similar to the $attribution variable, Mutt will append this string after
- the inclusion of a message which is being replied to.
-
- 3.226. postpone
-
- Type: quadoption
- Default: ask-yes
-
- Controls whether or not messages are saved in the $postponed mailbox when
- you elect not to send immediately.
-
- Also see the $recall variable.
-
- 3.227. postponed
-
- Type: path
- Default: "~/postponed"
-
- Mutt allows you to indefinitely "postpone sending a message" which you are
- editing. When you choose to postpone a message, Mutt saves it in the
- mailbox specified by this variable.
-
- Also see the $postpone variable.
-
- 3.228. preconnect
-
- Type: string
- Default: (empty)
-
- If set, a shell command to be executed if mutt 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 gives up opening the server. Example:
-
- set 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.
-
- When set, Mutt uses the tunnel for all remote connections. Please see
- "account-hook" in the manual for how to use different tunnel commands per
- connection.
-
- 3.229. print
-
- Type: quadoption
- Default: ask-no
-
- Controls whether or not Mutt really prints messages. This is set to
- "ask-no" by default, because some people accidentally hit "p" often.
-
- 3.230. print_command
-
- Type: path
- Default: "lpr"
-
- This specifies the command pipe that should be used to print messages.
-
- 3.231. 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.
-
- 3.232. 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.
-
- 3.233. prompt_after
-
- Type: boolean
- Default: yes
-
- If you use an external $pager, setting this variable will cause Mutt to
- prompt you for a command when the pager exits rather than returning to the
- index menu. If unset, Mutt will return to the index menu when the external
- pager exits.
-
- 3.234. query_command
-
- Type: path
- Default: (empty)
-
- This specifies the command that mutt 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.
-
- 3.235. query_format
-
- Type: string
- Default: "%4c %t %-25.25a %-25.25n %?e?(%e)?"
-
- This variable describes the format of the "query" menu. The following
- printf(3)-style sequences are understood:
-
- %a
-
- destination address
-
- %c
-
- current entry number
-
- %e
-
- extra information *
-
- %n
-
- destination name
-
- %t
-
- "*" if current entry is tagged, a space otherwise
-
- %>X
-
- right justify the rest of the string and pad with "X"
-
- %|X
-
- pad to the end of the line with "X"
-
- %*X
-
- soft-fill with character "X" as pad
-
- For an explanation of "soft-fill", see the $index_format documentation.
-
- * = can be optionally printed if nonzero, see the $status_format
- documentation.
-
- 3.236. quit
-
- Type: quadoption
- Default: yes
-
- This variable controls whether "quit" and "exit" actually quit from mutt.
- If this option is set, they do quit, if it is unset, 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.
-
- 3.237. 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. Quoted text may be filtered out
- using the <toggle-quoted> command, or colored according to the "color
- quoted" family of directives.
-
- Higher levels of quoting may be colored differently ("color quoted1",
- "color quoted2", etc.). The quoting level is determined by removing the
- last character from the matched text and recursively reapplying the
- regular expression until it fails to produce a match.
-
- Match detection may be overridden by the $smileys regular expression.
-
- 3.238. read_inc
-
- Type: number
- Default: 10
-
- If set to a value greater than 0, Mutt will display which message it is
- currently on when reading a mailbox or when performing search actions such
- as search and limit. The message is printed after this many messages have
- been read or searched (e.g., if set to 25, Mutt will print a message when
- it is at message 25, and then again when it gets to message 50). This
- variable is meant to indicate progress when reading or searching 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, $net_inc and $time_inc variables and the "tuning"
- section of the manual for performance considerations.
-
- 3.239. read_only
-
- Type: boolean
- Default: no
-
- If set, all folders are opened in read-only mode.
-
- 3.240. realname
-
- Type: string
- Default: (empty)
-
- 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 that this
- variable will not be used when the user has set a real name in the $from
- variable.
-
- 3.241. recall
-
- Type: quadoption
- Default: ask-yes
-
- Controls whether or not Mutt recalls postponed messages when composing a
- new message.
-
- Setting this variable to is not generally useful, and thus not
- recommended.
-
- Also see $postponed variable.
-
- 3.242. record
-
- Type: path
- Default: "~/sent"
-
- 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:" 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.
-
- 3.243. 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:".
-
- 3.244. reply_self
-
- Type: boolean
- Default: no
-
- If unset and you are replying to a message sent by you, Mutt will assume
- that you want to reply to the recipients of that message rather than to
- yourself.
-
- Also see the "alternates" command.
-
- 3.245. reply_to
-
- Type: quadoption
- Default: ask-yes
-
- If set, when replying to a message, Mutt will use the address listed in
- the Reply-to: header 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.
-
- 3.246. 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.
-
- 3.247. reverse_alias
-
- Type: boolean
- Default: no
-
- This variable controls whether or not Mutt 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.
-
- 3.248. 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.
-
- Also see the "alternates" command.
-
- 3.249. reverse_realname
-
- Type: boolean
- Default: yes
-
- This variable fine-tunes the behaviour of the $reverse_name feature. When
- it is set, mutt will use the address from incoming messages as-is,
- possibly including eventual real names. When it is unset, mutt will
- override any such real names with the setting of the $realname variable.
-
- 3.250. rfc2047_parameters
-
- Type: boolean
- Default: no
-
- When this variable is set, Mutt will decode RFC2047-encoded MIME
- parameters. You want to set this variable when mutt suggests you to save
- attachments to files named like:
-
- =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-
- When this variable is set interactively, the change won't be active until
- you change folders.
-
- Note that this use of RFC2047'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
- generates this kind of encoding. Instead, mutt will unconditionally use
- the encoding specified in RFC2231.
-
- 3.251. save_address
-
- Type: boolean
- Default: no
-
- If set, mutt 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.
-
- 3.252. 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 does not delete MH
- and Maildir directories.
-
- 3.253. save_history
-
- Type: number
- Default: 0
-
- This variable controls the size of the history (per category) saved in the
- $history_file file.
-
- 3.254. 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.
-
- 3.255. 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 related are used.
-
- 3.256. 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. Since mutt
- scores are always greater than or equal to zero, the default setting of
- this variable will never mark a message for deletion.
-
- 3.257. 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".
-
- 3.258. 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. Since mutt
- scores are always greater than or equal to zero, the default setting of
- this variable will never mark a message read.
-
- 3.259. send_charset
-
- Type: string
- Default: "us-ascii:iso-8859-1:utf-8"
-
- A colon-delimited list of character sets for outgoing messages. Mutt 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".
-
- In case the text cannot be converted into one of these exactly, mutt uses
- $charset as a fallback.
-
- 3.260. sendmail
-
- Type: path
- Default: "/usr/sbin/sendmail -oem -oi"
-
- Specifies the program and arguments used to deliver mail sent by Mutt.
- Mutt expects that the specified program interprets additional arguments as
- recipient addresses.
-
- 3.261. 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 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.
-
- 3.262. shell
-
- Type: path
- Default: (empty)
-
- Command to use when spawning a subshell. By default, the user's login
- shell from /etc/passwd is used.
-
- 3.263. sig_dashes
-
- Type: boolean
- Default: yes
-
- If set, a line containing "-- " (note the trailing 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 has the ability to highlight the signature in
- a different color in the builtin pager.
-
- 3.264. 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.
-
- 3.265. 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
- standard output.
-
- 3.266. simple_search
-
- Type: string
- Default: "~f %s | ~s %s"
-
- Specifies how Mutt should expand a simple search into a real search
- pattern. A simple search is one that does not contain any of the "~"
- pattern operators. See "patterns" for more information on search patterns.
-
- For example, if you simply type "joe" at a search or limit prompt, Mutt
- will automatically expand it to the value specified by this variable by
- replacing "%s" with the supplied string. For the default value, "joe"
- would be expanded to: "~f joe | ~s joe".
-
- 3.267. 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.
-
- 3.268. smileys
-
- Type: regular expression
- Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
-
- The pager uses this variable to catch some common false positives of
- $quote_regexp, most notably smileys and not consider a line quoted text if
- it also matches $smileys. This mostly happens at the beginning of a line.
-
- 3.269. 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.
-
- 3.270. smtp_authenticators
-
- Type: string
- Default: (empty)
-
- This is a colon-delimited list of authentication methods mutt may attempt
- to use to log in to an SMTP server, in the order mutt should try them.
- Authentication methods are any SASL mechanism, eg "digest-md5", "gssapi"
- or "cram-md5". This option is case-insensitive. If it is "unset" (the
- default) mutt will try all available methods, in order from most-secure to
- least-secure.
-
- Example:
-
- set smtp_authenticators="digest-md5:cram-md5"
-
-
- 3.271. smtp_pass
-
- Type: string
- Default: (empty)
-
- Specifies the password for your SMTP account. If unset, Mutt will prompt
- you for your password when you first send mail via SMTP. See $smtp_url to
- configure mutt to send mail via SMTP.
-
- Warning: you should only use this option when you are on a fairly secure
- machine, because the superuser can read your muttrc even if you are the
- only one who can read the file.
-
- 3.272. smtp_url
-
- Type: string
- Default: (empty)
-
- Defines the SMTP smarthost where sent messages should relayed for
- delivery. This should take the form of an SMTP URL, eg:
-
- smtp[s]://[user[:pass]@]host[:port]/
-
-
- \.\.\. where "[...]" denotes an optional part. Setting this variable
- overrides the value of the $sendmail variable.
-
- 3.273. sort
-
- Type: sort order
- Default: date
-
- Specifies how to sort messages in the "index" menu. Valid values are:
-
- o date or date-sent
-
- o date-received
-
- o from
-
- o mailbox-order (unsorted)
-
- o score
-
- o size
-
- o spam
-
- o subject
-
- o threads
-
- o to
-
- You may optionally use the "reverse-" prefix to specify reverse sorting
- order (example: "set sort=reverse-date-sent").
-
- Note: On Debian systems, this option is set by default to "threads" in
- /etc/Muttrc.
-
- 3.274. sort_alias
-
- Type: sort order
- Default: alias
-
- Specifies how the entries in the "alias" menu are sorted. The following
- are legal values:
-
- o address (sort alphabetically by email address)
-
- o alias (sort alphabetically by alias name)
-
- o unsorted (leave in order specified in .muttrc)
-
- 3.275. 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 will just use "date-sent"). You can also specify the
- "last-" prefix in addition to the "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).
-
- 3.276. 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:
-
- o alpha (alphabetically)
-
- o date
-
- o size
-
- o unsorted
-
- You may optionally use the "reverse-" prefix to specify reverse sorting
- order (example: "set sort_browser=reverse-date").
-
- 3.277. 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 uses to thread messages
- by subject. With $sort_re set, mutt 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_re unset, mutt will attach the message whether or not this is the
- case, as long as the non-$reply_regexp parts of both messages are
- identical.
-
- 3.278. spam_separator
-
- Type: string
- Default: ","
-
- This variable 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 this variable's value as a separator.
-
- 3.279. spoolfile
-
- Type: path
- Default: (empty)
-
- If your spool mailbox is in a non-default place where Mutt cannot find it,
- you can specify its location with this variable. Mutt will automatically
- set this variable to the value of the environment variable $MAIL if it is
- not set.
-
- 3.280. 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).
-
- 3.281. status_format
-
- Type: string
- Default: "-%r-Mutt: %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 *
-
- %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 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"
-
- %*X
-
- soft-fill with character "X" as pad
-
- For an explanation of "soft-fill", see the $index_format documentation.
-
- * = 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_string may 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.?
-
- You can also switch between two strings using the following construct:
-
- %?<sequence_char>?<if_string>&<else_string>?
-
- If the value of sequence_char is non-zero, if_string will be expanded,
- otherwise else_string will be expanded.
-
- You can 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
- will replace any dots in the expansion by underscores. This might be
- helpful with IMAP folders that don't like dots in folder names.
-
- 3.282. 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. If $help is set, too it'll
- be placed at the bottom.
-
- 3.283. strict_threads
-
- Type: boolean
- Default: no
-
- If set, threading will only make use of the "In-Reply-To" and
- "References:" 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 subjects like "hi" which
- will get grouped together. See also $sort_re for a less drastic way of
- controlling this behaviour.
-
- 3.284. suspend
-
- Type: boolean
- Default: yes
-
- When unset, mutt won't stop when the user presses the terminal's susp key,
- usually "^Z". This is useful if you run mutt inside an xterm using a
- command like "xterm -e mutt".
-
- 3.285. text_flowed
-
- Type: boolean
- Default: no
-
- When set, mutt will generate "format=flowed" bodies with a content type of
- "text/plain; format=flowed". 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.
-
- 3.286. thread_received
-
- Type: boolean
- Default: no
-
- When set, mutt uses the date received rather than the date sent to thread
- messages by subject.
-
- 3.287. thorough_search
-
- Type: boolean
- Default: no
-
- Affects the ~b and ~h search operations described in section "patterns".
- If set, the headers and body/attachments of messages to be searched are
- decoded before searching. If unset, messages are searched as they appear
- in the folder.
-
- Users searching attachments or for non-ASCII characters should set this
- value because decoding also includes MIME parsing/decoding and possible
- character set conversions. Otherwise mutt will attempt to match against
- the raw message received (for example quoted-printable encoded or with
- encoded headers) which may lead to incorrect search results.
-
- 3.288. tilde
-
- Type: boolean
- Default: no
-
- When set, the internal-pager will pad blank lines to the bottom of the
- screen with a tilde ("~").
-
- 3.289. time_inc
-
- Type: number
- Default: 0
-
- Along with $read_inc, $write_inc, and $net_inc, this variable controls the
- frequency with which progress updates are displayed. It suppresses updates
- less than $time_inc milliseconds apart. This can improve throughput on
- systems with slow terminals, or when running mutt on a remote system.
-
- Also see the "tuning" section of the manual for performance
- considerations.
-
- 3.290. timeout
-
- Type: number
- Default: 600
-
- When Mutt is waiting for user input either idleing in menus or in an
- interactive prompt, Mutt would block until input is present. Depending on
- the context, this would prevent certain operations from working, like
- checking for new mail or keeping an IMAP connection alive.
-
- This variable controls how many seconds Mutt will at most wait until it
- aborts waiting for input, performs these operations and continues to wait
- for input.
-
- A value of zero or less will cause Mutt to never time out.
-
- 3.291. tmpdir
-
- Type: path
- Default: (empty)
-
- This variable allows you to specify where Mutt 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.
-
- 3.292. 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.
- The second is used when you are the only recipient of the message. The
- third is when your address appears in the "To:" header field, but you are
- not the only recipient of the message. 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 subscribe to.
-
- 3.293. trash
-
- Type: path
- Default: (empty)
-
- 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 you have a way to clean the trash.
-
- 3.294. tunnel
-
- Type: string
- Default: (empty)
-
- Setting this variable will cause mutt 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/SMTP server. Example:
-
- set 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.
-
- 3.295. 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
- you may not be able to send mail.
-
- When set, Mutt will invoke $sendmail with the -B8BITMIME flag when sending
- 8-bit messages to enable ESMTP negotiation.
-
- 3.296. use_domain
-
- Type: boolean
- Default: yes
-
- When set, Mutt will qualify all local addresses (ones without the "@host"
- portion) with the value of $hostname. If unset, no addresses will be
- qualified.
-
- 3.297. use_envelope_from
-
- Type: boolean
- Default: no
-
- When set, mutt will set the envelope sender of the message. If
- $envelope_from_address is set, it will be used as the sender address. If
- unset, mutt will attempt to derive the sender from the "From:" header.
-
- Note that this information is passed to sendmail command using the -f
- command line switch. Therefore setting this option is not useful if the
- $sendmail variable already contains -f or if the executable pointed to by
- $sendmail doesn't support the -f switch.
-
- 3.298. use_from
-
- Type: boolean
- Default: yes
-
- When set, Mutt 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.
-
- 3.299. use_idn
-
- Type: boolean
- Default: yes
-
- When set, Mutt will show you international domain names decoded. Note: You
- can use IDNs for addresses even if this is unset. This variable only
- affects decoding.
-
- 3.300. use_ipv6
-
- Type: boolean
- Default: yes
-
- When set, Mutt will look for IPv6 addresses of hosts it tries to contact.
- If this option is unset, Mutt will restrict itself to IPv4 addresses.
- Normally, the default should work.
-
- 3.301. user_agent
-
- Type: boolean
- Default: yes
-
- When set, mutt will add a "User-Agent:" header to outgoing messages,
- indicating which version of mutt was used for composing them.
-
- 3.302. visual
-
- Type: path
- Default: (empty)
-
- Specifies the visual editor to invoke when the "~v" command is given in
- the builtin editor.
-
- 3.303. wait_key
-
- Type: boolean
- Default: yes
-
- Controls whether Mutt will ask you to press a key after an external
- command has been invoked by these functions: <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 will always ask for a key. When unset, Mutt will wait for a
- key only if the external command returned a non-zero status.
-
- 3.304. weed
-
- Type: boolean
- Default: yes
-
- When set, mutt will weed headers when displaying, forwarding, printing, or
- replying to messages.
-
- 3.305. wrap
-
- Type: number
- Default: 0
-
- When set to a positive value, mutt will wrap text at $wrap characters.
- When set to a negative value, mutt will wrap text so that there are $wrap
- characters of empty space on the right side of the terminal.
-
- 3.306. wrap_search
-
- Type: boolean
- Default: yes
-
- Controls whether searches wrap around the end.
-
- When set, searches will wrap around the first (or last) item. When unset,
- incremental searches will not wrap.
-
- 3.307. wrapmargin
-
- Type: number
- Default: 0
-
- (DEPRECATED) Equivalent to setting $wrap with a negative value.
-
- 3.308. 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, $net_inc and $time_inc variables and the "tuning"
- section of the manual for performance considerations.
-
- 3.309. write_bcc
-
- Type: boolean
- Default: yes
-
- Controls whether mutt writes out the "Bcc:" header when preparing messages
- to be sent. Exim users may wish to unset this. If mutt is set to deliver
- directly via SMTP (see $smtp_url), this option does nothing: mutt will
- never write out the "Bcc:" header in this case.
-
- Note: On Debian systems, exim4 and postfix strip BCC headers by default.
- The above warning applies to exim3 users, see /etc/Muttrc.
-
- 3.310. xterm_icon
-
- Type: string
- Default: "M%?n?AIL&ail?"
-
- Controls the format of the icon title, as long as xterm_set_titles is
- enabled. This string is identical in formatting to the one used by
- "$status_format".
-
- 3.311. xterm_set_titles
-
- Type: boolean
- Default: no
-
- Controls whether mutt sets the xterm title bar and icon name (as long as
- you are in an appropriate terminal).
-
- 3.312. xterm_title
-
- Type: string
- Default: "Mutt 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".
-
-4. 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.
-
- 4.1. generic menu
-
- 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 8.2. Default generic function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |-------------------+-------------+--------------------------------------|
- | <top-page> | H | move to the top of the page |
- |-------------------+-------------+--------------------------------------|
- | <next-entry> | j | move to the next entry |
- |-------------------+-------------+--------------------------------------|
- | <previous-entry> | k | move to the previous entry |
- |-------------------+-------------+--------------------------------------|
- | <bottom-page> | L | move to the bottom of the page |
- |-------------------+-------------+--------------------------------------|
- | <refresh> | ^L | clear and redraw the screen |
- |-------------------+-------------+--------------------------------------|
- | <middle-page> | M | move to the middle of the page |
- |-------------------+-------------+--------------------------------------|
- | <search-next> | n | search for next match |
- |-------------------+-------------+--------------------------------------|
- | <exit> | q | exit this menu |
- |-------------------+-------------+--------------------------------------|
- | <tag-entry> | t | tag the current entry |
- |-------------------+-------------+--------------------------------------|
- | <next-page> | z | move to the next page |
- |-------------------+-------------+--------------------------------------|
- | <previous-page> | Z | move to the previous page |
- |-------------------+-------------+--------------------------------------|
- | <last-entry> | * | move to the last entry |
- |-------------------+-------------+--------------------------------------|
- | <first-entry> | = | move to the first entry |
- |-------------------+-------------+--------------------------------------|
- | <enter-command> | : | enter a muttrc command |
- |-------------------+-------------+--------------------------------------|
- | <next-line> | > | scroll down one line |
- |-------------------+-------------+--------------------------------------|
- | <previous-line> | < | scroll up one line |
- |-------------------+-------------+--------------------------------------|
- | <half-up> | [ | scroll up 1/2 page |
- |-------------------+-------------+--------------------------------------|
- | <half-down> | ] | scroll down 1/2 page |
- |-------------------+-------------+--------------------------------------|
- | <help> | ? | this screen |
- |-------------------+-------------+--------------------------------------|
- | <tag-prefix> | ; | apply next function to tagged |
- | | | messages |
- |-------------------+-------------+--------------------------------------|
- | <tag-prefix-cond> | | apply next function ONLY to tagged |
- | | | messages |
- |-------------------+-------------+--------------------------------------|
- | <end-cond> | | end of conditional execution (noop) |
- |-------------------+-------------+--------------------------------------|
- | <shell-escape> | ! | invoke a command in a subshell |
- |-------------------+-------------+--------------------------------------|
- | <select-entry> | <Return> | select the current entry |
- |-------------------+-------------+--------------------------------------|
- | <search> | / | search for a regular expression |
- |-------------------+-------------+--------------------------------------|
- | <search-reverse> | Esc / | search backwards for a regular |
- | | | expression |
- |-------------------+-------------+--------------------------------------|
- | <search-opposite> | | search for next match in opposite |
- | | | direction |
- |-------------------+-------------+--------------------------------------|
- | <jump> | | jump to an index number |
- |-------------------+-------------+--------------------------------------|
- | <current-top> | | move entry to top of screen |
- |-------------------+-------------+--------------------------------------|
- | <current-middle> | | move entry to middle of screen |
- |-------------------+-------------+--------------------------------------|
- | <current-bottom> | | move entry to bottom of screen |
- |-------------------+-------------+--------------------------------------|
- | <what-key> | | display the keycode for a key press |
- +------------------------------------------------------------------------+
-
- 4.2. index menu
-
- Table 8.3. Default index function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |----------------------------+-------------+-----------------------------|
- | <create-alias> | a | create an alias from a |
- | | | message sender |
- |----------------------------+-------------+-----------------------------|
- | <bounce-message> | b | remail a message to another |
- | | | user |
- |----------------------------+-------------+-----------------------------|
- | <break-thread> | # | break the thread in two |
- |----------------------------+-------------+-----------------------------|
- | <change-folder> | c | open a different folder |
- |----------------------------+-------------+-----------------------------|
- | <change-folder-readonly> | Esc c | open a different folder in |
- | | | read only mode |
- |----------------------------+-------------+-----------------------------|
- | <next-unread-mailbox> | | open next mailbox with new |
- | | | mail |
- |----------------------------+-------------+-----------------------------|
- | <collapse-thread> | Esc v | collapse/uncollapse current |
- | | | thread |
- |----------------------------+-------------+-----------------------------|
- | <collapse-all> | Esc V | collapse/uncollapse all |
- | | | threads |
- |----------------------------+-------------+-----------------------------|
- | <copy-message> | C | copy a message to a |
- | | | file/mailbox |
- |----------------------------+-------------+-----------------------------|
- | <decode-copy> | Esc C | make decoded (text/plain) |
- | | | copy |
- |----------------------------+-------------+-----------------------------|
- | <decode-save> | Esc s | make decoded copy |
- | | | (text/plain) and delete |
- |----------------------------+-------------+-----------------------------|
- | <delete-message> | d | delete the current entry |
- |----------------------------+-------------+-----------------------------|
- | <delete-pattern> | D | delete messages matching a |
- | | | pattern |
- |----------------------------+-------------+-----------------------------|
- | <delete-thread> | ^D | delete all messages in |
- | | | thread |
- |----------------------------+-------------+-----------------------------|
- | <delete-subthread> | Esc d | delete all messages in |
- | | | subthread |
- |----------------------------+-------------+-----------------------------|
- | <edit> | e | edit the raw message |
- |----------------------------+-------------+-----------------------------|
- | <edit-type> | ^E | edit attachment content |
- | | | type |
- |----------------------------+-------------+-----------------------------|
- | <forward-message> | f | forward a message with |
- | | | comments |
- |----------------------------+-------------+-----------------------------|
- | <flag-message> | F | toggle a message's |
- | | | 'important' flag |
- |----------------------------+-------------+-----------------------------|
- | <group-reply> | g | reply to all recipients |
- |----------------------------+-------------+-----------------------------|
- | <fetch-mail> | G | retrieve mail from POP |
- | | | server |
- |----------------------------+-------------+-----------------------------|
- | <imap-fetch-mail> | | force retrieval of mail |
- | | | from IMAP server |
- |----------------------------+-------------+-----------------------------|
- | <display-toggle-weed> | h | display message and toggle |
- | | | header weeding |
- |----------------------------+-------------+-----------------------------|
- | <next-undeleted> | j | move to the next undeleted |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <previous-undeleted> | k | move to the previous |
- | | | undeleted message |
- |----------------------------+-------------+-----------------------------|
- | <limit> | l | show only messages matching |
- | | | a pattern |
- |----------------------------+-------------+-----------------------------|
- | <link-threads> | & | link tagged message to the |
- | | | current one |
- |----------------------------+-------------+-----------------------------|
- | <list-reply> | L | reply to specified mailing |
- | | | list |
- |----------------------------+-------------+-----------------------------|
- | <mail> | m | compose a new mail message |
- |----------------------------+-------------+-----------------------------|
- | <toggle-new> | N | toggle a message's 'new' |
- | | | flag |
- |----------------------------+-------------+-----------------------------|
- | <toggle-write> | % | toggle whether the mailbox |
- | | | will be rewritten |
- |----------------------------+-------------+-----------------------------|
- | <next-thread> | ^N | jump to the next thread |
- |----------------------------+-------------+-----------------------------|
- | <next-subthread> | Esc n | jump to the next subthread |
- |----------------------------+-------------+-----------------------------|
- | | | really delete the current |
- | <purge-message> | | entry, bypassing the trash |
- | | | folder |
- |----------------------------+-------------+-----------------------------|
- | <query> | Q | query external program for |
- | | | addresses |
- |----------------------------+-------------+-----------------------------|
- | <quit> | q | save changes to mailbox and |
- | | | quit |
- |----------------------------+-------------+-----------------------------|
- | <reply> | r | reply to a message |
- |----------------------------+-------------+-----------------------------|
- | <show-limit> | Esc l | show currently active limit |
- | | | pattern |
- |----------------------------+-------------+-----------------------------|
- | <sort-mailbox> | o | sort messages |
- |----------------------------+-------------+-----------------------------|
- | <sort-reverse> | O | sort messages in reverse |
- | | | order |
- |----------------------------+-------------+-----------------------------|
- | <print-message> | p | print the current entry |
- |----------------------------+-------------+-----------------------------|
- | <previous-thread> | ^P | jump to previous thread |
- |----------------------------+-------------+-----------------------------|
- | <previous-subthread> | Esc p | jump to previous subthread |
- |----------------------------+-------------+-----------------------------|
- | <recall-message> | R | recall a postponed message |
- |----------------------------+-------------+-----------------------------|
- | <read-thread> | ^R | mark the current thread as |
- | | | read |
- |----------------------------+-------------+-----------------------------|
- | <read-subthread> | Esc r | mark the current subthread |
- | | | as read |
- |----------------------------+-------------+-----------------------------|
- | <resend-message> | Esc e | use the current message as |
- | | | a template for a new one |
- |----------------------------+-------------+-----------------------------|
- | <save-message> | s | save message/attachment to |
- | | | a file |
- |----------------------------+-------------+-----------------------------|
- | <tag-pattern> | T | tag messages matching a |
- | | | pattern |
- |----------------------------+-------------+-----------------------------|
- | <tag-subthread> | | tag the current subthread |
- |----------------------------+-------------+-----------------------------|
- | <tag-thread> | Esc t | tag the current thread |
- |----------------------------+-------------+-----------------------------|
- | <untag-pattern> | ^T | untag messages matching a |
- | | | pattern |
- |----------------------------+-------------+-----------------------------|
- | <undelete-message> | u | undelete the current entry |
- |----------------------------+-------------+-----------------------------|
- | <undelete-pattern> | U | undelete messages matching |
- | | | a pattern |
- |----------------------------+-------------+-----------------------------|
- | <undelete-subthread> | Esc u | undelete all messages in |
- | | | subthread |
- |----------------------------+-------------+-----------------------------|
- | <undelete-thread> | ^U | undelete all messages in |
- | | | thread |
- |----------------------------+-------------+-----------------------------|
- | <view-attachments> | v | show MIME attachments |
- |----------------------------+-------------+-----------------------------|
- | <show-version> | V | show the Mutt version |
- | | | number and date |
- |----------------------------+-------------+-----------------------------|
- | <set-flag> | w | set a status flag on a |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <clear-flag> | W | clear a status flag from a |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <display-message> | <Return> | display a message |
- |----------------------------+-------------+-----------------------------|
- | <buffy-list> | . | list mailboxes with new |
- | | | mail |
- |----------------------------+-------------+-----------------------------|
- | <sync-mailbox> | $ | save changes to mailbox |
- |----------------------------+-------------+-----------------------------|
- | <display-address> | @ | display full address of |
- | | | sender |
- |----------------------------+-------------+-----------------------------|
- | <pipe-message> | | | pipe message/attachment to |
- | | | a shell command |
- |----------------------------+-------------+-----------------------------|
- | <next-new> | | jump to the next new |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <next-new-then-unread> | <Tab> | jump to the next new or |
- | | | unread message |
- |----------------------------+-------------+-----------------------------|
- | <previous-new> | | jump to the previous new |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <previous-new-then-unread> | Esc <Tab> | jump to the previous new or |
- | | | unread message |
- |----------------------------+-------------+-----------------------------|
- | <next-unread> | | jump to the next unread |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <previous-unread> | | jump to the previous unread |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <parent-message> | P | jump to parent message in |
- | | | thread |
- |----------------------------+-------------+-----------------------------|
- | <extract-keys> | ^K | extract supported public |
- | | | keys |
- |----------------------------+-------------+-----------------------------|
- | <forget-passphrase> | ^F | wipe passphrase(s) from |
- | | | memory |
- |----------------------------+-------------+-----------------------------|
- | <check-traditional-pgp> | Esc P | check for classic PGP |
- |----------------------------+-------------+-----------------------------|
- | <mail-key> | Esc k | mail a PGP public key |
- |----------------------------+-------------+-----------------------------|
- | <decrypt-copy> | | make decrypted copy |
- |----------------------------+-------------+-----------------------------|
- | <decrypt-save> | | make decrypted copy and |
- | | | delete |
- |----------------------------+-------------+-----------------------------|
- | <sidebar-scroll-up> | | scroll the mailbox pane up |
- | | | 1 page |
- |----------------------------+-------------+-----------------------------|
- | <sidebar-scroll-down> | | scroll the mailbox pane |
- | | | down 1 page |
- |----------------------------+-------------+-----------------------------|
- | <sidebar-next> | | go down to next mailbox |
- |----------------------------+-------------+-----------------------------|
- | <sidebar-prev> | | go to previous mailbox |
- |----------------------------+-------------+-----------------------------|
- | <sidebar-open> | | open hilighted mailbox |
- +------------------------------------------------------------------------+
-
- 4.3. pager menu
-
- Table 8.4. Default pager function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |--------------------------+-------------+-------------------------------|
- | <break-thread> | # | break the thread in two |
- |--------------------------+-------------+-------------------------------|
- | <create-alias> | a | create an alias from a |
- | | | message sender |
- |--------------------------+-------------+-------------------------------|
- | <bounce-message> | b | remail a message to another |
- | | | user |
- |--------------------------+-------------+-------------------------------|
- | <change-folder> | c | open a different folder |
- |--------------------------+-------------+-------------------------------|
- | <change-folder-readonly> | Esc c | open a different folder in |
- | | | read only mode |
- |--------------------------+-------------+-------------------------------|
- | <next-unread-mailbox> | | open next mailbox with new |
- | | | mail |
- |--------------------------+-------------+-------------------------------|
- | <copy-message> | C | copy a message to a |
- | | | file/mailbox |
- |--------------------------+-------------+-------------------------------|
- | <decode-copy> | Esc C | make decoded (text/plain) |
- | | | copy |
- |--------------------------+-------------+-------------------------------|
- | <delete-message> | d | delete the current entry |
- |--------------------------+-------------+-------------------------------|
- | <delete-thread> | ^D | delete all messages in thread |
- |--------------------------+-------------+-------------------------------|
- | <delete-subthread> | Esc d | delete all messages in |
- | | | subthread |
- |--------------------------+-------------+-------------------------------|
- | <edit> | e | edit the raw message |
- |--------------------------+-------------+-------------------------------|
- | <edit-type> | ^E | edit attachment content type |
- |--------------------------+-------------+-------------------------------|
- | <forward-message> | f | forward a message with |
- | | | comments |
- |--------------------------+-------------+-------------------------------|
- | <flag-message> | F | toggle a message's |
- | | | 'important' flag |
- |--------------------------+-------------+-------------------------------|
- | <group-reply> | g | reply to all recipients |
- |--------------------------+-------------+-------------------------------|
- | <imap-fetch-mail> | | force retrieval of mail from |
- | | | IMAP server |
- |--------------------------+-------------+-------------------------------|
- | <display-toggle-weed> | h | display message and toggle |
- | | | header weeding |
- |--------------------------+-------------+-------------------------------|
- | <next-undeleted> | j | move to the next undeleted |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <next-entry> | J | move to the next entry |
- |--------------------------+-------------+-------------------------------|
- | <previous-undeleted> | k | move to the previous |
- | | | undeleted message |
- |--------------------------+-------------+-------------------------------|
- | <previous-entry> | K | move to the previous entry |
- |--------------------------+-------------+-------------------------------|
- | <link-threads> | & | link tagged message to the |
- | | | current one |
- |--------------------------+-------------+-------------------------------|
- | <list-reply> | L | reply to specified mailing |
- | | | list |
- |--------------------------+-------------+-------------------------------|
- | <redraw-screen> | ^L | clear and redraw the screen |
- |--------------------------+-------------+-------------------------------|
- | <mail> | m | compose a new mail message |
- |--------------------------+-------------+-------------------------------|
- | <mark-as-new> | N | toggle a message's 'new' flag |
- |--------------------------+-------------+-------------------------------|
- | <search-next> | n | search for next match |
- |--------------------------+-------------+-------------------------------|
- | <next-thread> | ^N | jump to the next thread |
- |--------------------------+-------------+-------------------------------|
- | <next-subthread> | Esc n | jump to the next subthread |
- |--------------------------+-------------+-------------------------------|
- | <print-message> | p | print the current entry |
- |--------------------------+-------------+-------------------------------|
- | <previous-thread> | ^P | jump to previous thread |
- |--------------------------+-------------+-------------------------------|
- | <previous-subthread> | Esc p | jump to previous subthread |
- |--------------------------+-------------+-------------------------------|
- | | | really delete the current |
- | <purge-message> | | entry, bypassing the trash |
- | | | folder |
- |--------------------------+-------------+-------------------------------|
- | <quit> | Q | save changes to mailbox and |
- | | | quit |
- |--------------------------+-------------+-------------------------------|
- | <exit> | q | exit this menu |
- |--------------------------+-------------+-------------------------------|
- | <reply> | r | reply to a message |
- |--------------------------+-------------+-------------------------------|
- | <recall-message> | R | recall a postponed message |
- |--------------------------+-------------+-------------------------------|
- | <read-thread> | ^R | mark the current thread as |
- | | | read |
- |--------------------------+-------------+-------------------------------|
- | <read-subthread> | Esc r | mark the current subthread as |
- | | | read |
- |--------------------------+-------------+-------------------------------|
- | <resend-message> | Esc e | use the current message as a |
- | | | template for a new one |
- |--------------------------+-------------+-------------------------------|
- | <save-message> | s | save message/attachment to a |
- | | | file |
- |--------------------------+-------------+-------------------------------|
- | <skip-quoted> | S | skip beyond quoted text |
- |--------------------------+-------------+-------------------------------|
- | <decode-save> | Esc s | make decoded copy |
- | | | (text/plain) and delete |
- |--------------------------+-------------+-------------------------------|
- | <tag-message> | t | tag the current entry |
- |--------------------------+-------------+-------------------------------|
- | <toggle-quoted> | T | toggle display of quoted text |
- |--------------------------+-------------+-------------------------------|
- | <undelete-message> | u | undelete the current entry |
- |--------------------------+-------------+-------------------------------|
- | <undelete-subthread> | Esc u | undelete all messages in |
- | | | subthread |
- |--------------------------+-------------+-------------------------------|
- | <undelete-thread> | ^U | undelete all messages in |
- | | | thread |
- |--------------------------+-------------+-------------------------------|
- | <view-attachments> | v | show MIME attachments |
- |--------------------------+-------------+-------------------------------|
- | <show-version> | V | show the Mutt version number |
- | | | and date |
- |--------------------------+-------------+-------------------------------|
- | <search-toggle> | \\ | toggle search pattern |
- | | | coloring |
- |--------------------------+-------------+-------------------------------|
- | <display-address> | @ | display full address of |
- | | | sender |
- |--------------------------+-------------+-------------------------------|
- | <next-new> | | jump to the next new message |
- |--------------------------+-------------+-------------------------------|
- | <pipe-message> | | | pipe message/attachment to a |
- | | | shell command |
- |--------------------------+-------------+-------------------------------|
- | <help> | ? | this screen |
- |--------------------------+-------------+-------------------------------|
- | <next-page> | <Space> | move to the next page |
- |--------------------------+-------------+-------------------------------|
- | <previous-page> | - | move to the previous page |
- |--------------------------+-------------+-------------------------------|
- | <top> | ^ | jump to the top of the |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <sync-mailbox> | $ | save changes to mailbox |
- |--------------------------+-------------+-------------------------------|
- | <shell-escape> | ! | invoke a command in a |
- | | | subshell |
- |--------------------------+-------------+-------------------------------|
- | <enter-command> | : | enter a muttrc command |
- |--------------------------+-------------+-------------------------------|
- | <buffy-list> | . | list mailboxes with new mail |
- |--------------------------+-------------+-------------------------------|
- | <search> | / | search for a regular |
- | | | expression |
- |--------------------------+-------------+-------------------------------|
- | <search-reverse> | Esc / | search backwards for a |
- | | | regular expression |
- |--------------------------+-------------+-------------------------------|
- | <search-opposite> | | search for next match in |
- | | | opposite direction |
- |--------------------------+-------------+-------------------------------|
- | <next-line> | <Return> | scroll down one line |
- |--------------------------+-------------+-------------------------------|
- | <jump> | | jump to an index number |
- |--------------------------+-------------+-------------------------------|
- | <next-unread> | | jump to the next unread |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <previous-new> | | jump to the previous new |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <previous-unread> | | jump to the previous unread |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <half-up> | | scroll up 1/2 page |
- |--------------------------+-------------+-------------------------------|
- | <half-down> | | scroll down 1/2 page |
- |--------------------------+-------------+-------------------------------|
- | <previous-line> | | scroll up one line |
- |--------------------------+-------------+-------------------------------|
- | <bottom> | | jump to the bottom of the |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <parent-message> | P | jump to parent message in |
- | | | thread |
- |--------------------------+-------------+-------------------------------|
- | <check-traditional-pgp> | Esc P | check for classic PGP |
- |--------------------------+-------------+-------------------------------|
- | <mail-key> | Esc k | mail a PGP public key |
- |--------------------------+-------------+-------------------------------|
- | <extract-keys> | ^K | extract supported public keys |
- |--------------------------+-------------+-------------------------------|
- | <forget-passphrase> | ^F | wipe passphrase(s) from |
- | | | memory |
- |--------------------------+-------------+-------------------------------|
- | <decrypt-copy> | | make decrypted copy |
- |--------------------------+-------------+-------------------------------|
- | <decrypt-save> | | make decrypted copy and |
- | | | delete |
- |--------------------------+-------------+-------------------------------|
- | <what-key> | | display the keycode for a key |
- | | | press |
- |--------------------------+-------------+-------------------------------|
- | <sidebar-scroll-up> | | scroll the mailbox pane up 1 |
- | | | page |
- |--------------------------+-------------+-------------------------------|
- | <sidebar-scroll-down> | | scroll the mailbox pane down |
- | | | 1 page |
- |--------------------------+-------------+-------------------------------|
- | <sidebar-next> | | go down to next mailbox |
- |--------------------------+-------------+-------------------------------|
- | <sidebar-prev> | | go to previous mailbox |
- |--------------------------+-------------+-------------------------------|
- | <sidebar-open> | | open hilighted mailbox |
- +------------------------------------------------------------------------+
-
- 4.4. alias menu
-
- Table 8.5. Default alias function bindings
-
- +-------------------------------------------------------------+
- | Function | Default key | Description |
- |------------------+-------------+----------------------------|
- | <delete-entry> | d | delete the current entry |
- |------------------+-------------+----------------------------|
- | <undelete-entry> | u | undelete the current entry |
- +-------------------------------------------------------------+
-
- 4.5. query menu
-
- Table 8.6. Default query 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 |
- +------------------------------------------------------------------------+
-
- 4.6. attach menu
-
- Table 8.7. Default attach function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |-------------------------+-------------+--------------------------------|
- | <bounce-message> | b | remail a message to another |
- | | | user |
- |-------------------------+-------------+--------------------------------|
- | <display-toggle-weed> | h | display message and toggle |
- | | | header weeding |
- |-------------------------+-------------+--------------------------------|
- | <edit-type> | ^E | edit attachment content type |
- |-------------------------+-------------+--------------------------------|
- | <print-entry> | p | print the current entry |
- |-------------------------+-------------+--------------------------------|
- | <save-entry> | s | save message/attachment to a |
- | | | file |
- |-------------------------+-------------+--------------------------------|
- | <pipe-entry> | | | pipe message/attachment to a |
- | | | shell command |
- |-------------------------+-------------+--------------------------------|
- | <view-mailcap> | m | force viewing of attachment |
- | | | using mailcap |
- |-------------------------+-------------+--------------------------------|
- | <reply> | r | reply to a message |
- |-------------------------+-------------+--------------------------------|
- | <resend-message> | Esc e | use the current message as a |
- | | | template for a new one |
- |-------------------------+-------------+--------------------------------|
- | <group-reply> | g | reply to all recipients |
- |-------------------------+-------------+--------------------------------|
- | <list-reply> | L | reply to specified mailing |
- | | | list |
- |-------------------------+-------------+--------------------------------|
- | <forward-message> | f | forward a message with |
- | | | comments |
- |-------------------------+-------------+--------------------------------|
- | <view-text> | T | view attachment as text |
- |-------------------------+-------------+--------------------------------|
- | <view-attach> | <Return> | view attachment using mailcap |
- | | | entry if necessary |
- |-------------------------+-------------+--------------------------------|
- | <delete-entry> | d | delete the current entry |
- |-------------------------+-------------+--------------------------------|
- | <undelete-entry> | u | undelete the current entry |
- |-------------------------+-------------+--------------------------------|
- | <collapse-parts> | v | Toggle display of subparts |
- |-------------------------+-------------+--------------------------------|
- | <check-traditional-pgp> | Esc P | check for classic PGP |
- |-------------------------+-------------+--------------------------------|
- | <extract-keys> | ^K | extract supported public keys |
- |-------------------------+-------------+--------------------------------|
- | <forget-passphrase> | ^F | wipe passphrase(s) from memory |
- +------------------------------------------------------------------------+
-
- 4.7. compose menu
-
- Table 8.8. Default compose function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |-----------------------+-------------+----------------------------------|
- | <attach-file> | a | attach file(s) to this message |
- |-----------------------+-------------+----------------------------------|
- | <attach-message> | A | attach message(s) to this |
- | | | message |
- |-----------------------+-------------+----------------------------------|
- | <edit-bcc> | b | edit the BCC list |
- |-----------------------+-------------+----------------------------------|
- | <edit-cc> | c | edit the CC list |
- |-----------------------+-------------+----------------------------------|
- | <copy-file> | C | save message/attachment to a |
- | | | file |
- |-----------------------+-------------+----------------------------------|
- | <detach-file> | D | delete the current entry |
- |-----------------------+-------------+----------------------------------|
- | <toggle-disposition> | ^D | toggle disposition between |
- | | | inline/attachment |
- |-----------------------+-------------+----------------------------------|
- | <edit-description> | d | edit attachment description |
- |-----------------------+-------------+----------------------------------|
- | <edit-message> | e | edit the message |
- |-----------------------+-------------+----------------------------------|
- | <edit-headers> | E | edit the message with headers |
- |-----------------------+-------------+----------------------------------|
- | <edit-file> | ^X e | edit the file to be attached |
- |-----------------------+-------------+----------------------------------|
- | <edit-encoding> | ^E | edit attachment |
- | | | transfer-encoding |
- |-----------------------+-------------+----------------------------------|
- | <edit-from> | Esc f | edit the from field |
- |-----------------------+-------------+----------------------------------|
- | <edit-fcc> | f | enter a file to save a copy of |
- | | | this message in |
- |-----------------------+-------------+----------------------------------|
- | <filter-entry> | F | filter attachment through a |
- | | | shell command |
- |-----------------------+-------------+----------------------------------|
- | <get-attachment> | G | get a temporary copy of an |
- | | | attachment |
- |-----------------------+-------------+----------------------------------|
- | <display-toggle-weed> | h | display message and toggle |
- | | | header weeding |
- |-----------------------+-------------+----------------------------------|
- | <ispell> | i | run ispell on the message |
- |-----------------------+-------------+----------------------------------|
- | <print-entry> | l | print the current entry |
- |-----------------------+-------------+----------------------------------|
- | <edit-mime> | m | edit attachment using mailcap |
- | | | entry |
- |-----------------------+-------------+----------------------------------|
- | <new-mime> | n | compose new attachment using |
- | | | mailcap entry |
- |-----------------------+-------------+----------------------------------|
- | <postpone-message> | P | save this message to send later |
- |-----------------------+-------------+----------------------------------|
- | <edit-reply-to> | r | edit the Reply-To field |
- |-----------------------+-------------+----------------------------------|
- | <rename-file> | R | rename/move an attached file |
- |-----------------------+-------------+----------------------------------|
- | <edit-subject> | s | edit the subject of this message |
- |-----------------------+-------------+----------------------------------|
- | <edit-to> | t | edit the TO list |
- |-----------------------+-------------+----------------------------------|
- | <edit-type> | ^T | edit attachment content type |
- |-----------------------+-------------+----------------------------------|
- | <write-fcc> | w | write the message to a folder |
- |-----------------------+-------------+----------------------------------|
- | <toggle-unlink> | u | toggle whether to delete file |
- | | | after sending it |
- |-----------------------+-------------+----------------------------------|
- | <toggle-recode> | | toggle recoding of this |
- | | | attachment |
- |-----------------------+-------------+----------------------------------|
- | <update-encoding> | U | update an attachment's encoding |
- | | | info |
- |-----------------------+-------------+----------------------------------|
- | <view-attach> | <Return> | view attachment using mailcap |
- | | | entry if necessary |
- |-----------------------+-------------+----------------------------------|
- | <send-message> | y | send the message |
- |-----------------------+-------------+----------------------------------|
- | <pipe-entry> | | | pipe message/attachment to a |
- | | | shell command |
- |-----------------------+-------------+----------------------------------|
- | <attach-key> | Esc k | attach a PGP public key |
- |-----------------------+-------------+----------------------------------|
- | <pgp-menu> | p | show PGP options |
- |-----------------------+-------------+----------------------------------|
- | <forget-passphrase> | ^F | wipe passphrase(s) from memory |
- |-----------------------+-------------+----------------------------------|
- | <smime-menu> | S | show S/MIME options |
- |-----------------------+-------------+----------------------------------|
- | <mix> | M | send the message through a |
- | | | mixmaster remailer chain |
- +------------------------------------------------------------------------+
-
- 4.8. postpone menu
-
- Table 8.9. Default postpone function bindings
-
- +-------------------------------------------------------------+
- | Function | Default key | Description |
- |------------------+-------------+----------------------------|
- | <delete-entry> | d | delete the current entry |
- |------------------+-------------+----------------------------|
- | <undelete-entry> | u | undelete the current entry |
- +-------------------------------------------------------------+
-
- 4.9. browser menu
-
- Table 8.10. Default browser function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |---------------------+-------------+------------------------------------|
- | <change-dir> | c | change directories |
- |---------------------+-------------+------------------------------------|
- | <display-filename> | @ | display the currently selected |
- | | | file's name |
- |---------------------+-------------+------------------------------------|
- | <enter-mask> | m | enter a file mask |
- |---------------------+-------------+------------------------------------|
- | <sort> | o | sort messages |
- |---------------------+-------------+------------------------------------|
- | <sort-reverse> | O | sort messages in reverse order |
- |---------------------+-------------+------------------------------------|
- | <select-new> | N | select a new file in this |
- | | | directory |
- |---------------------+-------------+------------------------------------|
- | <check-new> | | check mailboxes for new mail |
- |---------------------+-------------+------------------------------------|
- | <toggle-mailboxes> | <Tab> | toggle whether to browse mailboxes |
- | | | or all files |
- |---------------------+-------------+------------------------------------|
- | <view-file> | <Space> | view file |
- |---------------------+-------------+------------------------------------|
- | <buffy-list> | . | list mailboxes with new mail |
- |---------------------+-------------+------------------------------------|
- | <create-mailbox> | C | create a new mailbox (IMAP only) |
- |---------------------+-------------+------------------------------------|
- | <delete-mailbox> | d | delete the current mailbox (IMAP |
- | | | only) |
- |---------------------+-------------+------------------------------------|
- | <rename-mailbox> | r | rename the current mailbox (IMAP |
- | | | only) |
- |---------------------+-------------+------------------------------------|
- | <subscribe> | s | subscribe to current mailbox (IMAP |
- | | | only) |
- |---------------------+-------------+------------------------------------|
- | <unsubscribe> | u | unsubscribe from current mailbox |
- | | | (IMAP only) |
- |---------------------+-------------+------------------------------------|
- | <toggle-subscribed> | T | toggle view all/subscribed |
- | | | mailboxes (IMAP only) |
- +------------------------------------------------------------------------+
-
- 4.10. pgp menu
-
- Table 8.11. Default pgp function bindings
-
- +------------------------------------------------------+
- | Function | Default key | Description |
- |--------------+-------------+-------------------------|
- | <verify-key> | c | verify a PGP public key |
- |--------------+-------------+-------------------------|
- | <view-name> | % | view the key's user id |
- +------------------------------------------------------+
-
- 4.11. smime menu
-
- Table 8.12. Default smime function bindings
-
- +------------------------------------------------------+
- | Function | Default key | Description |
- |--------------+-------------+-------------------------|
- | <verify-key> | c | verify a PGP public key |
- |--------------+-------------+-------------------------|
- | <view-name> | % | view the key's user id |
- +------------------------------------------------------+
-
- 4.12. mix menu
-
- Table 8.13. Default mix function bindings
-
- +-----------------------------------------------------------------------+
- | Function | Default key | Description |
- |--------------+-------------+------------------------------------------|
- | <accept> | <Return> | Accept the chain constructed |
- |--------------+-------------+------------------------------------------|
- | <append> | a | Append a remailer to the chain |
- |--------------+-------------+------------------------------------------|
- | <insert> | i | Insert a remailer into the chain |
- |--------------+-------------+------------------------------------------|
- | <delete> | d | Delete a remailer from the chain |
- |--------------+-------------+------------------------------------------|
- | <chain-prev> | <Left> | Select the previous element of the chain |
- |--------------+-------------+------------------------------------------|
- | <chain-next> | <Right> | Select the next element of the chain |
- +-----------------------------------------------------------------------+
-
- 4.13. editor menu
-
- Table 8.14. Default editor function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |-------------------+-------------+--------------------------------------|
- | <bol> | ^A | jump to the beginning of the line |
- |-------------------+-------------+--------------------------------------|
- | <backward-char> | ^B | move the cursor one character to the |
- | | | left |
- |-------------------+-------------+--------------------------------------|
- | <backward-word> | Esc b | move the cursor to the beginning of |
- | | | the word |
- |-------------------+-------------+--------------------------------------|
- | <capitalize-word> | Esc c | capitalize the word |
- |-------------------+-------------+--------------------------------------|
- | <downcase-word> | Esc l | convert the word to lower case |
- |-------------------+-------------+--------------------------------------|
- | <upcase-word> | Esc u | convert the word to upper case |
- |-------------------+-------------+--------------------------------------|
- | <delete-char> | ^D | delete the char under the cursor |
- |-------------------+-------------+--------------------------------------|
- | <eol> | ^E | jump to the end of the line |
- |-------------------+-------------+--------------------------------------|
- | <forward-char> | ^F | move the cursor one character to the |
- | | | right |
- |-------------------+-------------+--------------------------------------|
- | <forward-word> | Esc f | move the cursor to the end of the |
- | | | word |
- |-------------------+-------------+--------------------------------------|
- | <backspace> | <Backspace> | delete the char in front of the |
- | | | cursor |
- |-------------------+-------------+--------------------------------------|
- | <kill-eol> | ^K | delete chars from cursor to end of |
- | | | line |
- |-------------------+-------------+--------------------------------------|
- | <kill-eow> | Esc d | delete chars from the cursor to the |
- | | | end of the word |
- |-------------------+-------------+--------------------------------------|
- | <kill-line> | ^U | delete all chars on the line |
- |-------------------+-------------+--------------------------------------|
- | <quote-char> | ^V | quote the next typed key |
- |-------------------+-------------+--------------------------------------|
- | <kill-word> | ^W | delete the word in front of the |
- | | | cursor |
- |-------------------+-------------+--------------------------------------|
- | <complete> | <Tab> | complete filename or alias |
- |-------------------+-------------+--------------------------------------|
- | <complete-query> | ^T | complete address with query |
- |-------------------+-------------+--------------------------------------|
- | <buffy-cycle> | <Space> | cycle among incoming mailboxes |
- |-------------------+-------------+--------------------------------------|
- | <history-up> | | scroll up through the history list |
- |-------------------+-------------+--------------------------------------|
- | <history-down> | | scroll down through the history list |
- |-------------------+-------------+--------------------------------------|
- | <transpose-chars> | | transpose character under cursor |
- | | | with previous |
- +------------------------------------------------------------------------+
-
-Chapter 9. Miscellany
-
- Table of Contents
-
- 1. Acknowledgements
-
- 2. About this document
-
-1. Acknowledgements
-
- 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:
-
- 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 Bjo: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 Ma:kela: <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 Rocco Rutte <pdmef@gmx.net>
-
- 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>
-
-2. About this document
-
- This document was written in DocBook, and then rendered using the Gnome
- XSLT toolkit.
+++ /dev/null
-<?xml version="1.0" standalone="no"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
-<book>
-
-<bookinfo>
-<title>The Mutt E-Mail Client</title>
-<author>
-<firstname>Michael</firstname><surname>Elkins</surname>
-<email>me@cs.hmc.edu</email>
-</author>
-<releaseinfo>version 1.5.19 (2009-01-05)</releaseinfo>
-
-<abstract>
-<para>
-<quote>All mail clients suck. This one just sucks less.</quote> -me, circa 1995
-</para>
-</abstract>
-</bookinfo>
-
-<chapter id="intro">
-<title>Introduction</title>
-
-<para>
-<emphasis role="bold">Mutt</emphasis> is a small but very powerful text-based MIME mail client. Mutt 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.
-</para>
-
-<sect1 id="homepage">
-<title>Mutt Home Page</title>
-
-<para>
-The official homepage can be found at
-<ulink url="http://www.mutt.org/">http://www.mutt.org/</ulink>.
-</para>
-
-</sect1>
-
-<sect1 id="muttlists">
-<title>Mailing Lists</title>
-
-<para>
-To subscribe to one of the following mailing lists, send a message with the
-word <emphasis>subscribe</emphasis> in the body to
-<literal>list-name</literal><emphasis>-request</emphasis><literal>@mutt.org</literal>.
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-<email>mutt-announce-request@mutt.org</email> -- low traffic list for announcements
-</para>
-</listitem>
-<listitem>
-
-<para>
-<email>mutt-users-request@mutt.org</email> -- help, bug reports and feature requests
-</para>
-</listitem>
-<listitem>
-
-<para>
-<email>mutt-dev-request@mutt.org</email> -- development mailing list
-</para>
-</listitem>
-
-</itemizedlist>
-
-<note>
-<para>
-All messages posted to
-<emphasis>mutt-announce</emphasis> are automatically forwarded to
-<emphasis>mutt-users</emphasis>, so you do not need to be subscribed to
-both lists.
-</para>
-</note>
-
-</sect1>
-
-<sect1 id="distribution">
-<title>Software Distribution Sites</title>
-
-<para>
-Mutt releases can be downloaded from
-<ulink url="ftp://ftp.mutt.org/mutt/">ftp://ftp.mutt.org/mutt/</ulink>.
-For a list of mirror sites, please refer to
-<ulink url="http://www.mutt.org/download.html">http://www.mutt.org/download.html</ulink>.
-</para>
-
-</sect1>
-
-<sect1 id="irc">
-<title>Mutt online resources</title>
-
-<variablelist>
-
-<varlistentry>
-<term>Bug Tracking System</term>
-<listitem>
-<para>
-The official mutt bug tracking system can be found at
-<ulink url="http://dev.mutt.org/">http://dev.mutt.org/</ulink>
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>Wiki</term>
-<listitem>
-<para>
-An (unofficial) wiki can be found
-at <ulink url="http://wiki.mutt.org/">http://wiki.mutt.org/</ulink>.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>IRC</term>
-<listitem>
-<para>
-For the IRC user community, visit channel <emphasis>#mutt</emphasis> on
-<ulink url="http://www.freenode.net/">irc.freenode.net</ulink>.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>USENET</term>
-<listitem>
-<para>
-For USENET, see the newsgroup <ulink url="news:comp.mail.mutt">comp.mail.mutt</ulink>.
-</para>
-</listitem>
-</varlistentry>
-
-</variablelist>
-
-</sect1>
-
-<sect1 id="contrib">
-<title>Contributing to Mutt</title>
-
-<para>
-There are various ways to contribute to the Mutt project.
-</para>
-
-<para>
-Especially for new users it may be helpful to meet other new and
-experienced users to chat about Mutt, talk about problems and share
-tricks.
-</para>
-
-<para>
-Since translations of Mutt into other languages are highly appreciated,
-the mutt developers always look for skilled translators that help
-improve and continue to maintain stale translations.
-</para>
-
-<para>
-For contributing code patches for new features and bug fixes, please
-refer to the developer pages at
-<ulink url="http://dev.mutt.org/">http://dev.mutt.org/</ulink> for more details.
-</para>
-
-</sect1>
-
-<sect1 id="typo">
-<title>Typograhical conventions</title>
-
-<para>
-This section lists typographical conventions followed throughout this
-manual. See table <xref linkend="tab-typo"/> for typographical
-conventions for special terms.
-</para>
-
-<table id="tab-typo">
-<title>Typographical conventions for special terms</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Item</entry><entry>Refers to...</entry></row>
-</thead>
-<tbody>
-<row><entry><literal>printf(3)</literal></entry><entry>UNIX manual pages, execute <literal>man 3 printf</literal></entry></row>
-<row><entry><literal><PageUp></literal></entry><entry>named keys</entry></row>
-<row><entry><literal><create-alias></literal></entry><entry>named Mutt function</entry></row>
-<row><entry><literal>ˆG</literal></entry><entry>Control+G key combination</entry></row>
-<row><entry><literal>$mail_check</literal></entry><entry>Mutt configuration option</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Examples are presented as:
-</para>
-
-<screen>
-mutt -v
-</screen>
-
-<para>
-Within command synopsis, curly brackets (<quote>{}</quote>) denote a set
-of options of which one is mandatory, square brackets
-(<quote>[]</quote>) denote optional arguments, three dots
-denote that the argument may be repeated arbitrary times.
-</para>
-
-</sect1>
-
-<sect1 id="copyright">
-<title>Copyright</title>
-
-<para>
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins
-<email>me@mutt.org</email> and others.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-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.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="gettingstarted">
-<title>Getting Started</title>
-
-<para>
-This section is intended as a brief overview of how to use Mutt. There are
-many other features which are described elsewhere in the manual. There
-is even more information available in the Mutt FAQ and various web
-pages. See the <ulink url="http://www.mutt.org/">Mutt homepage</ulink> for more details.
-</para>
-
-<para>
-The keybindings described in this section are the defaults as distributed.
-Your local system administrator may have altered the defaults for your site.
-You can always type <quote>?</quote> in any menu to display the current bindings.
-</para>
-
-<para>
-The first thing you need to do is invoke mutt, simply by typing <literal>mutt</literal>
-at the command line. There are various command-line options, see
-either the mutt man page or the <link linkend="commandline">reference</link>.
-</para>
-
-<sect1 id="core-concepts">
-<title>Core concepts</title>
-
-<para>
-Mutt is a text-based application which interacts with users through
-different menus which are mostly line-/entry-based or page-based. A
-line-based menu is the so-called <quote>index</quote> menu (listing all messages of
-the currently opened folder) or the <quote>alias</quote> menu (allowing you to
-select recipients from a list). Examples for page-based menus are the
-<quote>pager</quote> (showing one message at a time) or the <quote>help</quote> menu listing
-all available key bindings.
-</para>
-
-<para>
-The user interface consists of a context sensitive help line at the top,
-the menu's contents followed by a context sensitive status line and
-finally the command line. The command line is used to display
-informational and error messages as well as for prompts and for entering
-interactive commands.
-</para>
-
-<para>
-Because Mutt allows for customizing almost all key bindings, there are
-so-called <quote>functions</quote> which can be executed manually (using the
-command line) or in macros. Macros allow the user to bind a sequence of
-commands to a single key or a short key sequence instead of repeating a
-sequence of actions over and over.
-</para>
-
-<para>
-Many commands (such as saving or copying a message to another folder)
-can be applied to a single message or a set of messages (so-called
-<quote>tagged</quote> messages). To help selecting messages, Mutt provides a rich
-set of message patterns (such as recipients, sender, body contents, date
-sent/received, etc.) which can be combined into complex expressions
-using the boolean <emphasis>and</emphasis> and <emphasis>or</emphasis>
-operations as well as negating. These patterns can also be used to (for
-example) search for messages or to limit the index to show only matching
-messages.
-</para>
-
-<para>
-Mutt supports a <quote>hook</quote> concept which allows the user to execute
-arbitrary configuration commands and functions in certain situations
-such as entering a folder, starting a new message or replying to an
-existing one. These hooks can be used to highly customize Mutt's
-behaviour including managing multiple identities, customizing the
-display for a folder or even implementing auto-archiving based on a
-per-folder basis and much more.
-</para>
-
-</sect1>
-
-<sect1 id="menus">
-<title>Moving Around in Menus</title>
-
-<para>
-The most important navigation keys common to all menus are shown in
-<xref linkend="tab-keys-nav"/>.
-</para>
-
-<table id="tab-keys-nav">
-<title>Most common navigation keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>j or <Down></entry><entry><literal><next-entry></literal></entry><entry>move to the next entry</entry></row>
-<row><entry>k or <Up></entry><entry><literal><previous-entry></literal></entry><entry>move to the previous entry</entry></row>
-<row><entry>z or <PageDn></entry><entry><literal><page-down></literal></entry><entry>go to the next page</entry></row>
-<row><entry>Z or <PageUp></entry><entry><literal><page-up></literal></entry><entry>go to the previous page</entry></row>
-<row><entry>= or <Home></entry><entry><literal><first-entry></literal></entry><entry>jump to the first entry</entry></row>
-<row><entry>* or <End></entry><entry><literal><last-entry></literal></entry><entry>jump to the last entry</entry></row>
-<row><entry>q</entry><entry><literal><quit></literal></entry><entry>exit the current menu</entry></row>
-<row><entry>?</entry><entry><literal><help></literal></entry><entry>list all keybindings for the current menu</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-</sect1>
-
-<sect1 id="editing">
-<title>Editing Input Fields</title>
-
-<sect2 id="editing-intro">
-<title>Introduction</title>
-
-<para>
-Mutt has a built-in line editor for inputting text, e.g. email
-addresses or filenames. The keys used to manipulate text input are
-very similar to those of Emacs. See <xref linkend="tab-keys-editor"/> for a full
-reference of available functions, their default key bindings, and
-short descriptions.
-</para>
-
-<table id="tab-keys-editor">
-<title>Most common line editor keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>ˆA or <Home></entry><entry><literal><bol></literal></entry><entry>move to the start of the line</entry></row>
-<row><entry>ˆB or <Left></entry><entry><literal><backward-char></literal></entry><entry>move back one char</entry></row>
-<row><entry>Esc B</entry><entry><literal><backward-word></literal></entry><entry>move back one word</entry></row>
-<row><entry>ˆD or <Delete></entry><entry><literal><delete-char></literal></entry><entry>delete the char under the cursor</entry></row>
-<row><entry>ˆE or <End></entry><entry><literal><eol></literal></entry><entry>move to the end of the line</entry></row>
-<row><entry>ˆF or <Right></entry><entry><literal><forward-char></literal></entry><entry>move forward one char</entry></row>
-<row><entry>Esc F</entry><entry><literal><forward-word></literal></entry><entry>move forward one word</entry></row>
-<row><entry><Tab></entry><entry><literal><complete></literal></entry><entry>complete filename or alias</entry></row>
-<row><entry>ˆT</entry><entry><literal><complete-query></literal></entry><entry>complete address with query</entry></row>
-<row><entry>ˆK</entry><entry><literal><kill-eol></literal></entry><entry>delete to the end of the line</entry></row>
-<row><entry>Esc d</entry><entry><literal><kill-eow></literal></entry><entry>delete to the end of the word</entry></row>
-<row><entry>ˆW</entry><entry><literal><kill-word></literal></entry><entry>kill the word in front of the cursor</entry></row>
-<row><entry>ˆU</entry><entry><literal><kill-line></literal></entry><entry>delete entire line</entry></row>
-<row><entry>ˆV</entry><entry><literal><quote-char></literal></entry><entry>quote the next typed key</entry></row>
-<row><entry><Up></entry><entry><literal><history-up></literal></entry><entry>recall previous string from history</entry></row>
-<row><entry><Down></entry><entry><literal><history-down></literal></entry><entry>recall next string from history</entry></row>
-<row><entry><BackSpace></entry><entry><literal><backspace></literal></entry><entry>kill the char in front of the cursor</entry></row>
-<row><entry>Esc u</entry><entry><literal><upcase-word></literal></entry><entry>convert word to upper case</entry></row>
-<row><entry>Esc l</entry><entry><literal><downcase-word></literal></entry><entry>convert word to lower case</entry></row>
-<row><entry>Esc c</entry><entry><literal><capitalize-word></literal></entry><entry>capitalize the word</entry></row>
-<row><entry>ˆG</entry><entry>n/a</entry><entry>abort</entry></row>
-<row><entry><Return></entry><entry>n/a</entry><entry>finish editing</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-You can remap the <emphasis>editor</emphasis> functions using the
-<link linkend="bind">bind</link> command. For example, to make
-the <Delete> key delete the character in front of
-the cursor rather than under, you could use:
-</para>
-
-<screen>
-bind editor <delete> backspace
-</screen>
-
-</sect2>
-
-<sect2 id="editing-history">
-<title>History</title>
-
-<para>
-Mutt maintains a history for the built-in editor. The number of items
-is controlled by the <link linkend="history">$history</link>
-variable and can be made persistent using an external file specified
-using <link linkend="history-file">$history_file</link>.
-You may cycle through them at an editor prompt by using the
-<literal><history-up></literal> and/or
-<literal><history-down></literal> commands.
-</para>
-
-<para>
-Mutt maintains several distinct history lists, one for each of the
-following categories:
-</para>
-
-<itemizedlist>
-<listitem><para>muttrc commands</para></listitem>
-<listitem><para>addresses and aliases</para></listitem>
-<listitem><para>shell commands</para></listitem>
-<listitem><para>filenames</para></listitem>
-<listitem><para>patterns</para></listitem>
-<listitem><para>everything else</para></listitem>
-</itemizedlist>
-
-<para>
-Mutt automatically filters out repeated items from the history. It
-also mimics the behavior of some shells by ignoring items starting
-with a space. The latter feature can be useful in macros to not clobber
-the history's valuable entries with unwanted entries.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="reading">
-<title>Reading Mail - The Index and Pager</title>
-
-<para>
-Similar to many other mail clients, there are two modes in which mail is
-read in Mutt. The first is the index of messages in the mailbox, which is
-called the <quote>index</quote> in Mutt. The second mode is the display of the
-message contents. This is called the <quote>pager.</quote>
-</para>
-
-<para>
-The next few sections describe the functions provided in each of these
-modes.
-</para>
-
-<sect2 id="index-menu">
-<title>The Message Index</title>
-
-<para>
-Common keys used to navigate through and manage messages in the index
-are shown in <xref linkend="tab-key-index"/>. How messages are presented
-in the index menu can be customized using the
-<link linkend="index-format">$index_format</link> variable.
-</para>
-
-<table id="tab-key-index">
-<title>Most common message index keys</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>c</entry><entry>change to a different mailbox</entry></row>
-<row><entry>Esc c</entry><entry>change to a folder in read-only mode</entry></row>
-<row><entry>C</entry><entry>copy the current message to another mailbox</entry></row>
-<row><entry>Esc C</entry><entry>decode a message and copy it to a folder</entry></row>
-<row><entry>Esc s</entry><entry>decode a message and save it to a folder</entry></row>
-<row><entry>D</entry><entry>delete messages matching a pattern</entry></row>
-<row><entry>d</entry><entry>delete the current message</entry></row>
-<row><entry>F</entry><entry>mark as important</entry></row>
-<row><entry>l</entry><entry>show messages matching a pattern</entry></row>
-<row><entry>N</entry><entry>mark message as new</entry></row>
-<row><entry>o</entry><entry>change the current sort method</entry></row>
-<row><entry>O</entry><entry>reverse sort the mailbox</entry></row>
-<row><entry>q</entry><entry>save changes and exit</entry></row>
-<row><entry>s</entry><entry>save-message</entry></row>
-<row><entry>T</entry><entry>tag messages matching a pattern</entry></row>
-<row><entry>t</entry><entry>toggle the tag on a message</entry></row>
-<row><entry>Esc t</entry><entry>toggle tag on entire message thread</entry></row>
-<row><entry>U</entry><entry>undelete messages matching a pattern</entry></row>
-<row><entry>u</entry><entry>undelete-message</entry></row>
-<row><entry>v</entry><entry>view-attachments</entry></row>
-<row><entry>x</entry><entry>abort changes and exit</entry></row>
-<row><entry><Return></entry><entry>display-message</entry></row>
-<row><entry><Tab></entry><entry>jump to the next new or unread message</entry></row>
-<row><entry>@</entry><entry>show the author's full e-mail address</entry></row>
-<row><entry>$</entry><entry>save changes to mailbox</entry></row>
-<row><entry>/</entry><entry>search</entry></row>
-<row><entry>Esc /</entry><entry>search-reverse</entry></row>
-<row><entry>ˆL</entry><entry>clear and redraw the screen</entry></row>
-<row><entry>ˆT</entry><entry>untag messages matching a pattern</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-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 <quote>flags</quote> in <xref linkend="tab-msg-status-flags"/>
-may appear, some of which can be turned on or off using these functions:
-<literal><set-flag></literal> and
-<literal><clear-flag></literal>
-bound by default to <quote>w</quote> and <quote>W</quote> respectively.
-</para>
-
-<para>
-Furthermore, the flags in <xref linkend="tab-msg-recip-flags"/> reflect
-who the message is addressed to. They can be customized with the
-<link linkend="to-chars">$to_chars</link> variable.
-</para>
-
-<table id="tab-msg-status-flags">
-<title>Message status flags</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Flag</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>D</entry><entry>message is deleted (is marked for deletion)</entry></row>
-<row><entry>d</entry><entry>message has attachments marked for deletion</entry></row>
-<row><entry>K</entry><entry>contains a PGP public key</entry></row>
-<row><entry>N</entry><entry>message is new</entry></row>
-<row><entry>O</entry><entry>message is old</entry></row>
-<row><entry>P</entry><entry>message is PGP encrypted</entry></row>
-<row><entry>r</entry><entry>message has been replied to</entry></row>
-<row><entry>S</entry><entry>message is signed, and the signature is successfully verified</entry></row>
-<row><entry>s</entry><entry>message is signed</entry></row>
-<row><entry>!</entry><entry>message is flagged</entry></row>
-<row><entry>*</entry><entry>message is tagged</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<table id="tab-msg-recip-flags">
-<title>Message recipient flags</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Flag</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>+</entry><entry>message is to you and you only</entry></row>
-<row><entry>T</entry><entry>message is to you, but also to or cc'ed to others</entry></row>
-<row><entry>C</entry><entry>message is cc'ed to you</entry></row>
-<row><entry>F</entry><entry>message is from you</entry></row>
-<row><entry>L</entry><entry>message is sent to a subscribed mailing list</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="pager-menu">
-<title>The Pager</title>
-
-<para>
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program <emphasis>less</emphasis> though not nearly as
-featureful.
-</para>
-
-<table id="tab-key-pager">
-<title>Most common pager keys</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><Return></entry><entry>go down one line</entry></row>
-<row><entry><Space></entry><entry>display the next page (or next message if at the end of a message)</entry></row>
-<row><entry>-</entry><entry>go back to the previous page</entry></row>
-<row><entry>n</entry><entry>search for next match</entry></row>
-<row><entry>S</entry><entry>skip beyond quoted text</entry></row>
-<row><entry>T</entry><entry>toggle display of quoted text</entry></row>
-<row><entry>?</entry><entry>show keybindings</entry></row>
-<row><entry>/</entry><entry>regular expression search</entry></row>
-<row><entry>Esc /</entry><entry>backward regular expression search</entry></row>
-<row><entry>\</entry><entry>toggle highlighting of search matches</entry></row>
-<row><entry>ˆ</entry><entry>jump to the top of the message</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-In addition to key bindings in <xref linkend="tab-key-pager"/>,
-many of the functions from the index menu are also available in
-the pager, such as <literal><delete-message></literal> or <literal><copy-message></literal>
-(this is one advantage over using an external pager to view messages).
-</para>
-
-<para>
-Also, the internal pager supports a couple other advanced features. For
-one, it will accept and translate the <quote>standard</quote> nroff sequences for
-bold and underline. These sequences are a series of either the letter,
-backspace (ˆH), the letter again for bold or the letter, backspace,
-<quote>_</quote> for denoting underline. Mutt will attempt to display these
-in bold and underline respectively if your terminal supports them. If
-not, you can use the bold and underline <link linkend="color">color</link>
-objects to specify a color or mono attribute for them.
-</para>
-
-<para>
-Additionally, the internal pager supports the ANSI escape sequences for
-character attributes. Mutt translates them into the correct color and
-character settings. The sequences Mutt supports are:
-</para>
-
-<screen>
-\e[<emphasis>Ps</emphasis>;<emphasis>Ps</emphasis>;..<emphasis>Ps</emphasis>;m
-</screen>
-
-<para>
-where <emphasis>Ps</emphasis> can be one of the codes shown in
-<xref linkend="tab-ansi-esc"/>.
-</para>
-
-<table id="tab-ansi-esc">
-<title>ANSI escape sequences</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Escape code</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>0</entry><entry>All attributes off</entry></row>
-<row><entry>1</entry><entry>Bold on</entry></row>
-<row><entry>4</entry><entry>Underline on</entry></row>
-<row><entry>5</entry><entry>Blink on</entry></row>
-<row><entry>7</entry><entry>Reverse video on</entry></row>
-<row><entry>3<emphasis><color></emphasis></entry><entry>Foreground color is <emphasis><color></emphasis> (see <xref linkend="tab-color"/>)</entry></row>
-<row><entry>4<emphasis><color></emphasis></entry><entry>Background color is <emphasis><color></emphasis> (see <xref linkend="tab-color"/>)</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<table id="tab-color">
-<title>Color sequences</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Color code</entry><entry>Color</entry></row>
-</thead>
-<tbody>
-<row><entry>0</entry><entry>Black</entry></row>
-<row><entry>1</entry><entry>Red</entry></row>
-<row><entry>2</entry><entry>Green</entry></row>
-<row><entry>3</entry><entry>Yellow</entry></row>
-<row><entry>4</entry><entry>Blue</entry></row>
-<row><entry>5</entry><entry>Magenta</entry></row>
-<row><entry>6</entry><entry>Cyan</entry></row>
-<row><entry>7</entry><entry>White</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Mutt uses these attributes for handling <literal>text/enriched</literal>
-messages, and they can also be used by an external
-<link linkend="auto-view">autoview</link> script for highlighting
-purposes.
-</para>
-
-<note>
-<para>
-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.
-</para>
-</note>
-
-<note>
-<para>
-Note that the search commands in the pager take regular expressions,
-which are not quite the same as the more
-complex <link linkend="patterns">patterns</link> used by the search
-command in the index. This is because the pager only performs simple
-text search, whereas the index provides boolean filtering on several
-aspects of messages.
-</para>
-</note>
-
-</sect2>
-
-<sect2 id="threads">
-<title>Threaded Mode</title>
-
-<para>
-When the mailbox is <link linkend="sort">sorted</link> by <emphasis>threads</emphasis>, there are
-a few additional functions available in the <emphasis>index</emphasis> and <emphasis>pager</emphasis> modes
-as shown in <xref linkend="tab-key-threads"/>.
-</para>
-
-<table id="tab-key-threads">
-<title>Most common thread mode keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>ˆD</entry><entry><literal><delete-thread></literal></entry><entry>delete all messages in the current thread</entry></row>
-<row><entry>ˆU</entry><entry><literal><undelete-thread></literal></entry><entry>undelete all messages in the current thread</entry></row>
-<row><entry>ˆN</entry><entry><literal><next-thread></literal></entry><entry>jump to the start of the next thread</entry></row>
-<row><entry>ˆP</entry><entry><literal><previous-thread></literal></entry><entry>jump to the start of the previous thread</entry></row>
-<row><entry>ˆR</entry><entry><literal><read-thread></literal></entry><entry>mark the current thread as read</entry></row>
-<row><entry>Esc d</entry><entry><literal><delete-subthread></literal></entry><entry>delete all messages in the current subthread</entry></row>
-<row><entry>Esc u</entry><entry><literal><undelete-subthread></literal></entry><entry>undelete all messages in the current subthread</entry></row>
-<row><entry>Esc n</entry><entry><literal><next-subthread></literal></entry><entry>jump to the start of the next subthread</entry></row>
-<row><entry>Esc p</entry><entry><literal><previous-subthread></literal></entry><entry>jump to the start of the previous subthread</entry></row>
-<row><entry>Esc r</entry><entry><literal><read-subthread></literal></entry><entry>mark the current subthread as read</entry></row>
-<row><entry>Esc t</entry><entry><literal><tag-thread></literal></entry><entry>toggle the tag on the current thread</entry></row>
-<row><entry>Esc v</entry><entry><literal><collapse-thread></literal></entry><entry>toggle collapse for the current thread</entry></row>
-<row><entry>Esc V</entry><entry><literal><collapse-all></literal></entry><entry>toggle collapse for all threads</entry></row>
-<row><entry>P</entry><entry><literal><parent-message></literal></entry><entry>jump to parent message in thread</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<note>
-<para>
-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 on
-the screen. See %M in <link linkend="index-format">$index_format</link>.
-For example, you could use "%?M?(#%03M)&(%4l)?" in <link linkend="index-format">$index_format</link> to optionally
-display the number of hidden messages if the thread is collapsed.
-</para>
-</note>
-
-<para>
-See also: <link linkend="strict-threads">$strict_threads</link>.
-</para>
-
-</sect2>
-
-<sect2 id="reading-misc">
-<title>Miscellaneous Functions</title>
-
-<para>
-In addition, the <emphasis>index</emphasis> and <emphasis>pager</emphasis>
-menus have these interesting functions:
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>
-<literal><create-alias></literal><anchor id="create-alias"/> (default: a)
-</term>
-<listitem>
-<para>
-Creates a new alias based upon the current message (or prompts for a
-new one). Once editing is complete, an <link linkend="alias">alias</link>
-command is added to the file specified by
-the <link linkend="alias-file">$alias_file</link> variable
-for future use
-</para>
-
-<note>
-<para>
-Mutt does not read the <link linkend="alias-file">$alias_file</link>
-upon startup so you must explicitly <link linkend="source">source</link> the file.
-</para>
-</note>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><check-traditional-pgp></literal><anchor id="check-traditional-pgp"/> (default: Esc P)
-</term>
-<listitem>
-<para>
-This function will search the current message for content signed or
-encrypted with PGP the <quote>traditional</quote> 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 <link linkend="edit-type"><literal><edit-type></literal></link> function's
-effect.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><edit></literal><anchor id="edit"/> (default: e)
-</term>
-<listitem>
-<para>
-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; if the message is unchanged it won't be replaced.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><edit-type></literal><anchor id="edit-type"/> (default:
-ˆE on the attachment menu, and in the pager and index menus;
-ˆT on the compose menu)
-</term>
-<listitem>
-<para>
-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
-<link linkend="attach-menu">attachment menu</link>, you can change any
-attachment's content type. These changes are not persistent, and get
-lost upon changing folders.
-</para>
-
-<para>
-Note that this command is also available on the <link linkend="compose-menu">compose
-menu</link>. There, it's used to fine-tune the properties of attachments you are going
-to send.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><enter-command></literal><anchor id="enter-command"/> (default: <quote>:</quote>)
-</term>
-<listitem>
-<para>
-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 <link linkend="macro">macros</link> to change settings on the
-fly.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><extract-keys></literal><anchor id="extract-keys"/> (default: ˆK)
-</term>
-<listitem>
-<para>
-This command extracts PGP public keys from the current or tagged
-message(s) and adds them to your PGP public key ring.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><forget-passphrase></literal><anchor id="forget-passphrase"/> (default:
-ˆF)
-</term>
-<listitem>
-<para>
-This command wipes the passphrase(s) from memory. It is useful, if
-you misspelled the passphrase.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><list-reply></literal><anchor id="list-reply"/> (default: L)
-</term>
-<listitem>
-<para>
-Reply to the current or tagged message(s) by extracting any addresses which
-match the regular expressions given by the <link linkend="lists">lists or subscribe</link>
-commands, but also honor any <literal>Mail-Followup-To</literal> header(s) if the
-<link linkend="honor-followup-to">$honor_followup_to</link>
-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.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><pipe-message></literal><anchor id="pipe-message"/> (default: |)
-</term>
-<listitem>
-<para>
-Asks for an external Unix command and pipes the current or
-tagged message(s) to it. The variables <link linkend="pipe-decode">$pipe_decode</link>, <link linkend="pipe-split">$pipe_split</link>,
-<link linkend="pipe-sep">$pipe_sep</link> and <link linkend="wait-key">$wait_key</link> control the exact behavior of this function.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><resend-message></literal><anchor id="resend-message"/> (default: Esc e)
-</term>
-<listitem>
-<para>
-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 <link linkend="weed">$weed</link>
-variable.
-</para>
-
-<para>
-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 <literal>message/rfc822</literal> body part.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><shell-escape></literal><anchor id="shell-escape"/> (default: !)
-</term>
-<listitem>
-<para>
-Asks for an external Unix command and executes it. The <link linkend="wait-key">$wait_key</link> can be used to control
-whether Mutt 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. If no command is given, an
-interactive shell is executed.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><toggle-quoted></literal><anchor id="toggle-quoted"/> (default: T)
-</term>
-<listitem>
-<para>
-The pager uses the <link linkend="quote-regexp">$quote_regexp</link> variable to detect quoted text when
-displaying the body of the message. This function toggles the display
-of the quoted material in the message. It is particularly useful when
-being interested in just the response and there is a large amount of
-quoted text in the way.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><skip-quoted></literal><anchor id="skip-quoted"/> (default: S)
-</term>
-<listitem>
-<para>
-This function will go to the next line of non-quoted text which comes
-after a line of quoted text in the internal pager.
-</para>
-</listitem>
-</varlistentry>
-
-</variablelist>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="sending">
-<title>Sending Mail</title>
-
-<sect2 id="sending-intro">
-<title>Introduction</title>
-
-<para>
-The bindings shown in <xref linkend="tab-key-send"/> are available in the
-<emphasis>index</emphasis> and <emphasis>pager</emphasis> to start a new message.
-</para>
-
-<table id="tab-key-send">
-<title>Most common mail sending keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>m</entry><entry><literal><compose></literal></entry><entry>compose a new message</entry></row>
-<row><entry>r</entry><entry><literal><reply></literal></entry><entry>reply to sender</entry></row>
-<row><entry>g</entry><entry><literal><group-reply></literal></entry><entry>reply to all recipients</entry></row>
-<row><entry>L</entry><entry><literal><list-reply></literal></entry><entry>reply to mailing list address</entry></row>
-<row><entry>f</entry><entry><literal><forward></literal></entry><entry>forward message</entry></row>
-<row><entry>b</entry><entry><literal><bounce></literal></entry><entry>bounce (remail) message</entry></row>
-<row><entry>Esc k</entry><entry><literal><mail-key></literal></entry><entry>mail a PGP public key to someone</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-<emphasis>Bouncing</emphasis> a message sends the message as-is to the recipient you
-specify. <emphasis>Forwarding</emphasis> 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 <quote><link linkend="forwarding-mail">Forwarding
-and Bouncing Mail</link>.</quote>
-</para>
-
-<para>
-Mutt will then enter the <emphasis>compose</emphasis> menu and prompt you for the
-recipients to place on the <quote>To:</quote> header field. Next, it will ask
-you for the <quote>Subject:</quote> field for the message, providing a default if
-you are replying to or forwarding a message. See also
-<link linkend="askcc">$askcc</link>,
-<link linkend="askbcc">$askbcc</link>,
-<link linkend="autoedit">$autoedit</link>,
-<link linkend="bounce">$bounce</link>,
-<link linkend="fast-reply">$fast_reply</link>,
-and <link linkend="include">$include</link>
-for changing how Mutt asks these questions.
-</para>
-
-<para>
-Mutt will then automatically start your <link linkend="editor">$editor</link>
-on the message body. If the <link linkend="edit-headers">$edit_headers</link>
-variable is set, the headers will be at the top of the message in your editor.
-Any messages you are replying to will be added in sort order to the message,
-with appropriate <link linkend="attribution">$attribution</link>,
-<link linkend="indent-string">$indent_string</link> and
-<link linkend="post-indent-string">$post_indent_string</link>.
-When forwarding a message, if the <link linkend="mime-forward">$mime_forward</link>
-variable is unset, a copy of the forwarded message will be included. If
-you have specified a <link linkend="signature">$signature</link>, it
-will be appended to the message.
-</para>
-
-<para>
-Once you have finished editing the body of your mail message, you are
-returned to the <emphasis>compose</emphasis> menu providing the functions
-shown in <xref linkend="tab-func-compose"/> to modify, send or postpone the
-message.
-</para>
-
-<table id="tab-func-compose">
-<title>Most common compose menu keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>a</entry><entry><literal><attach-file></literal></entry><entry>attach a file</entry></row>
-<row><entry>A</entry><entry><literal><attach-message></literal></entry><entry>attach message(s) to the message</entry></row>
-<row><entry>Esc k</entry><entry><literal><attach-key></literal></entry><entry>attach a PGP public key</entry></row>
-<row><entry>d</entry><entry><literal><edit-description></literal></entry><entry>edit description on attachment</entry></row>
-<row><entry>D</entry><entry><literal><detach-file></literal></entry><entry>detach a file</entry></row>
-<row><entry>t</entry><entry><literal><edit-to></literal></entry><entry>edit the To field</entry></row>
-<row><entry>Esc f</entry><entry><literal><edit-from></literal></entry><entry>edit the From field</entry></row>
-<row><entry>r</entry><entry><literal><edit-reply-to></literal></entry><entry>edit the Reply-To field</entry></row>
-<row><entry>c</entry><entry><literal><edit-cc></literal></entry><entry>edit the Cc field</entry></row>
-<row><entry>b</entry><entry><literal><edit-bcc></literal></entry><entry>edit the Bcc field</entry></row>
-<row><entry>y</entry><entry><literal><send-message></literal></entry><entry>send the message</entry></row>
-<row><entry>s</entry><entry><literal><edit-subject></literal></entry><entry>edit the Subject</entry></row>
-<row><entry>S</entry><entry><literal><smime-menu></literal></entry><entry>select S/MIME options</entry></row>
-<row><entry>f</entry><entry><literal><edit-fcc></literal></entry><entry>specify an <quote>Fcc</quote> mailbox</entry></row>
-<row><entry>p</entry><entry><literal><pgp-menu></literal></entry><entry>select PGP options</entry></row>
-<row><entry>P</entry><entry><literal><postpone-message></literal></entry><entry>postpone this message until later</entry></row>
-<row><entry>q</entry><entry><literal><quit></literal></entry><entry>quit (abort) sending the message</entry></row>
-<row><entry>w</entry><entry><literal><write-fcc></literal></entry><entry>write the message to a folder</entry></row>
-<row><entry>i</entry><entry><literal><ispell></literal></entry><entry>check spelling (if available on your system)</entry></row>
-<row><entry>ˆF</entry><entry><literal><forget-passphrase></literal></entry><entry>wipe passphrase(s) from memory</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-The compose menu is also used to edit the attachments for a message which can be either files
-or other messages. The <literal><attach-message></literal> function to will prompt you for a folder to
-attach messages from. You can now tag messages in that folder and they
-will be attached to the message you are sending.
-</para>
-
-<note>
-<para>
-Note that certain
-operations like composing a new mail, replying, forwarding, etc. are
-not permitted when you are in that folder. The %r in
-<link linkend="status-format">$status_format</link> will change to
-a <quote>A</quote> to indicate that you are in attach-message mode.
-</para>
-</note>
-
-</sect2>
-
-<sect2 id="edit-header">
-<title>Editing the message header</title>
-
-<para>
-When editing the header because of <link linkend="edit-headers">$edit_headers</link>
-being set, there are a several pseudo headers available which
-will not be included in sent messages.
-</para>
-
-<sect3 id="fcc-header">
-<title>Fcc: pseudo header</title>
-
-<para>
-If you specify
-
-<literal>Fcc:</literal> <emphasis>filename</emphasis>
-
-as a header, Mutt will pick up <emphasis>filename</emphasis>
-just as if you had used the <literal><edit-fcc></literal> function in the <emphasis>compose</emphasis> menu.
-</para>
-
-</sect3>
-
-<sect3 id="attach-header">
-<title>Attach: pseudo header</title>
-
-<para>
-You can also attach files to your message by specifying
-
-<literal>Attach:</literal> <emphasis>filename</emphasis> [ <emphasis>description</emphasis> ]
-
-where <emphasis>filename</emphasis> is the file to attach and <emphasis>description</emphasis> is an
-optional string to use as the description of the attached file.
-</para>
-
-</sect3>
-
-<sect3 id="pgp-header">
-<title>Pgp: pseudo header</title>
-
-<para>
-If you want to use PGP, you can specify
-</para>
-
-<para>
-<literal>Pgp:</literal> [ <literal>E</literal> | <literal>S</literal> | <literal>S</literal><emphasis><id></emphasis> ]
-
-</para>
-
-<para>
-<quote>E</quote> selects encryption, <quote>S</quote> selects signing and
-<quote>S<id></quote> selects signing with the given key, setting
-<link linkend="pgp-sign-as">$pgp_sign_as</link>
-permanently.
-</para>
-
-</sect3>
-
-<sect3 id="in-reply-to-header">
-<title>In-Reply-To: header</title>
-
-<para>
-When replying to messages, the <emphasis>In-Reply-To:</emphasis> header contains the
-Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
-<emphasis>References:</emphasis> field, which allows you to create a new message thread, for example
-to create a new message to a mailing list without having to enter the mailing list's address.
-</para>
-
-</sect3>
-
-</sect2>
-
-<sect2 id="sending-crypto">
-<title>Sending cryptographically signed/encrypted messages</title>
-
-<para>
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
-through a key selection process when you try to send the message.
-Mutt 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.
-</para>
-
-<para>
-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 <literal>ˆG</literal>. When you do so, mutt will
-return to the compose screen.
-</para>
-
-<para>
-Once you have successfully finished the key selection, the message
-will be encrypted using the selected public keys when sent out.
-</para>
-
-<para>
-Most fields of the entries in the key selection menu (see also <link linkend="pgp-entry-format">$pgp_entry_format</link>)
-have obvious meanings. But some explanations on the capabilities, flags,
-and validity fields are in order.
-</para>
-
-<para>
-The flags sequence (%f) will expand to one of the flags in
-<xref linkend="tab-pgp-menuflags"/>.
-</para>
-
-<table id="tab-pgp-menuflags">
-<title>PGP key menu flags</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Flag</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>R</entry><entry>The key has been revoked and can't be used.</entry></row>
-<row><entry>X</entry><entry>The key is expired and can't be used.</entry></row>
-<row><entry>d</entry><entry>You have marked the key as disabled.</entry></row>
-<row><entry>c</entry><entry>There are unknown critical self-signature packets.</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-The capabilities field (%c) expands to a two-character sequence
-representing a key's capabilities. The first character gives
-the key's encryption capabilities: A minus sign (<quote>-</quote>) means
-that the key cannot be used for encryption. A dot (<quote>.</quote>) means that
-it's marked as a signature key in one of the user IDs, but may
-also be used for encryption. The letter <quote>e</quote> indicates that
-this key can be used for encryption.
-</para>
-
-<para>
-The second character indicates the key's signing capabilities. Once
-again, a <quote>-</quote> implies <quote>not for signing</quote>, <quote>.</quote> implies
-that the key is marked as an encryption key in one of the user-ids, and
-<quote>s</quote> denotes a key which can be used for signing.
-</para>
-
-<para>
-Finally, the validity field (%t) indicates how well-certified a user-id
-is. A question mark (<quote>?</quote>) indicates undefined validity, a minus
-character (<quote>-</quote>) marks an untrusted association, a space character
-means a partially trusted association, and a plus character (<quote>+</quote>)
-indicates complete validity.
-</para>
-
-</sect2>
-
-<sect2 id="sending-mixmaster">
-<title>Sending anonymous messages via mixmaster</title>
-
-<para>
-You may also have compiled 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.
-</para>
-
-<para>
-To use it, you'll have to obey certain restrictions. Most
-important, you cannot use the <literal>Cc</literal> and <literal>Bcc</literal> headers. To tell
-Mutt to use mixmaster, you have to select a remailer chain, using
-the mix function on the compose menu.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-You can navigate in the chain using the <literal><chain-prev></literal> and
-<literal><chain-next></literal> functions, which are by default bound to the left
-and right arrows and to the <literal>h</literal> and <literal>l</literal> keys (think vi
-keyboard bindings). To insert a remailer at the current chain
-position, use the <literal><insert></literal> function. To append a remailer behind
-the current chain position, use <literal><select-entry></literal> or <literal><append></literal>.
-You can also delete entries from the chain, using the corresponding
-function. Finally, to abandon your changes, leave the menu, or
-<literal><accept></literal> them pressing (by default) the <literal>Return</literal> key.
-</para>
-
-<para>
-Note that different remailers do have different capabilities,
-indicated in the %c entry of the remailer menu lines (see
-<link linkend="mix-entry-format">$mix_entry_format</link>). Most important is
-the <quote>middleman</quote> capability, indicated by a capital <quote>M</quote>: 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.
-</para>
-
-</sect2>
-
-<sect2 id="ff">
-<title>Sending format=flowed messages</title>
-
-<sect3 id="ff-concept">
-<title>Concept</title>
-
-<para>
-<literal>format=flowed</literal>-style messages (or <literal>f=f</literal>
-for short) are <literal>text/plain</literal> messages that consist of paragraphs which a receiver's
-mail client may reformat to its own needs which mostly means to
-customize line lengths regardless of what the sender sent. Technically this is
-achieved by letting lines of a <quote>flowable</quote> paragraph end in spaces
-except for the last line.
-</para>
-
-<para>
-While for text-mode clients like mutt it's the best way to assume only a
-standard 80x25 character cell terminal, it may be desired to let the
-receiver decide completely how to view a message.
-</para>
-
-</sect3>
-
-<sect3 id="ff-support">
-<title>Mutt support</title>
-
-<para>
-Mutt only supports setting the required <literal>format=flowed</literal>
-MIME parameter on outgoing messages if the <link
-linkend="text-flowed">$text_flowed</link>
-variable is set, specifically it does not add the
-trailing spaces.
-</para>
-
-<para>
-After editing the initial message text and before entering
-the compose menu, mutt properly space-stuffes the message.
-<emphasis>Space-stuffing</emphasis> is required by RfC3676 defining
-<literal>format=flowed</literal> and means to prepend a space to:
-</para>
-
-<itemizedlist>
-<listitem><para>all lines starting with a space</para></listitem>
-<listitem><para>lines starting with the word <quote><literal>From</literal></quote>
-followed by space</para></listitem>
-<listitem><para>all lines starting with <quote><literal>></literal></quote> which
-is not intended to be a quote character</para></listitem>
-</itemizedlist>
-
-<note>
-<para>
-Mutt only supports space-stuffing
-for the first two types of lines but not for the third: It is impossible to
-safely detect whether a leading <literal>></literal> character starts a
-quote or not. Furthermore, Mutt only applies space-stuffing
-<emphasis>once</emphasis> after the initial edit is finished.
-</para>
-</note>
-
-<para>
-All leading spaces are to be removed by receiving clients to restore
-the original message prior to further processing.
-</para>
-
-</sect3>
-
-<sect3 id="ff-editor">
-<title>Editor considerations</title>
-
-<para>
-As mutt provides no additional features to compose <literal>f=f</literal>
-messages, it's completely up to the user and his editor to produce
-proper messages. Please consider your editor's documentation if you
-intend to send <literal>f=f</literal> messages.
-</para>
-
-<para>
-Please note that when editing messages from the compose menu several
-times before really sending a mail, it's up to the user to ensure that
-the message is properly space-stuffed.
-</para>
-
-<para>
-For example, <emphasis>vim</emphasis> provides the <literal>w</literal>
-flag for its <literal>formatoptions</literal> setting to assist in
-creating <literal>f=f</literal> messages, see <literal>:help
-fo-table</literal> for details.
-</para>
-
-</sect3>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="forwarding-mail">
-<title>Forwarding and Bouncing Mail</title>
-
-<para>
-Bouncing and forwarding let you send an existing message to recipients
-that you specify. Bouncing a message sends a verbatim copy of a message
-to alternative addresses as if they were the message's original
-recipients specified in the Bcc header.
-Forwarding a message, on the other hand, allows you to modify the message
-before it is resent (for example, by adding your own comments). Bouncing
-is done using the <literal><bounce></literal> function and forwarding
-using the <literal><forward></literal> function bound to <quote>b</quote> and <quote>f</quote>
-respectively.
-</para>
-
-<para>
-Forwarding can be done by including the original message in the new
-message's body (surrounded by indicating lines) or including it as a MIME
-attachment, depending on the value of the <link linkend="mime-forward">$mime_forward</link> variable. Decoding of attachments,
-like in the pager, can be controlled by the <link linkend="forward-decode">$forward_decode</link> and <link linkend="mime-forward-decode">$mime_forward_decode</link> variables,
-respectively. The desired forwarding format may depend on the content,
-therefore <emphasis>$mime_forward</emphasis> is a quadoption which, for
-example, can be set to <quote>ask-no</quote>.
-</para>
-
-<para>
-The inclusion of headers is controlled by the current setting of the
-<link linkend="weed">$weed</link> variable, unless <link linkend="mime-forward">$mime_forward</link> is set.
-</para>
-
-<para>
-Editing the message to forward follows the same procedure as sending or
-replying to a message does.
-</para>
-
-</sect1>
-
-<sect1 id="postponing-mail">
-<title>Postponing Mail</title>
-
-<para>
-At times it is desirable to delay sending a message that you have
-already begun to compose. When the <literal><postpone-message></literal> function is
-used in the <emphasis>compose</emphasis> menu, the body of your message and attachments
-are stored in the mailbox specified by the <link linkend="postponed">$postponed</link> variable. This means that you can recall the
-message even if you exit Mutt and then restart it at a later time.
-</para>
-
-<para>
-Once a message is postponed, there are several ways to resume it. From the
-command line you can use the <quote>-p</quote> option, or if you compose a new
-message from the <emphasis>index</emphasis> or <emphasis>pager</emphasis> you will be prompted if postponed
-messages exist. If multiple messages are currently postponed, the
-<emphasis>postponed</emphasis> menu will pop up and you can select which message you would
-like to resume.
-</para>
-
-<note>
-<para>
-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.
-</para>
-</note>
-
-<para>
-See also the <link linkend="postpone">$postpone</link> quad-option.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="configuration">
-<title>Configuration</title>
-
-<sect1 id="configuration-files">
-<title>Location of initialization files</title>
-
-<para>
-While the default configuration (or <quote>preferences</quote>) make Mutt
-usable right out of the box, it is often desirable to tailor Mutt to
-suit your own tastes. When Mutt is first invoked, it will attempt to
-read the <quote>system</quote> configuration file (defaults set by your local
-system administrator), unless the <quote>-n</quote> <link linkend="commandline">command line</link> option is specified. This file is typically
-<literal>/usr/local/share/mutt/Muttrc</literal> or <literal>/etc/Muttrc</literal>. Mutt
-will next look for a file named <literal>.muttrc</literal> in your home
-directory. If this file does not exist and your home directory has
-a subdirectory named <literal>.mutt</literal>, mutt try to load a file named
-<literal>.mutt/muttrc</literal>.
-</para>
-
-<para>
-<literal>.muttrc</literal> is the file where you will usually place your <link linkend="commands">commands</link> to configure Mutt.
-</para>
-
-<para>
-In addition, mutt supports version specific configuration files that are
-parsed instead of the default files as explained above. For instance, if
-your system has a <literal>Muttrc-0.88</literal> file in the system configuration
-directory, and you are running version 0.88 of mutt, this file will be
-sourced instead of the <literal>Muttrc</literal> file. The same is true of the user
-configuration file, if you have a file <literal>.muttrc-0.88.6</literal> in your home
-directory, when you run mutt version 0.88.6, it will source this file
-instead of the default <literal>.muttrc</literal> file. The version number is the
-same which is visible using the <quote>-v</quote> <link linkend="commandline">command line</link> switch or using the <literal>show-version</literal> key (default:
-V) from the index menu.
-</para>
-
-</sect1>
-
-<sect1 id="muttrc-syntax" xreflabel="Syntax of Initialization Files">
-<title>Syntax of Initialization Files</title>
-
-<para>
-An initialization file consists of a series of <link linkend="commands">commands</link>. Each line of the file may contain one or more commands.
-When multiple commands are used, they must be separated by a semicolon
-(;).
-</para>
-
-<example id="ex-rc-multiple-cmds">
-<title>Multiple configuration commands per line</title>
-<screen>
-set realname='Mutt user' ; ignore x-
-</screen>
-</example>
-
-<para>
-The hash mark, or pound sign
-(<quote>#</quote>), is used as a <quote>comment</quote> 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,
-</para>
-
-<example id="ex-ec-comment">
-<title>Commenting configuration files</title>
-<screen>
-my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
-</screen>
-</example>
-
-<para>
-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, backticks are evaluated inside of double
-quotes, but <emphasis role="bold">not</emphasis> for single quotes.
-</para>
-
-<para>
-\ quotes the next character, just as in shells such as bash and zsh.
-For example, if want to put quotes <quote>"</quote> inside of a string, you can use
-<quote>\</quote> to force the next character to be a literal instead of interpreted
-character.
-</para>
-
-<example id="ex-rc-quote">
-<title>Escaping quotes in congfiguration files</title>
-<screen>
-set realname="Michael \"MuttDude\" Elkins"
-</screen>
-</example>
-
-<para>
-<quote>\\</quote> means to insert a literal <quote>\</quote> into the line.
-<quote>\n</quote> and <quote>\r</quote> have their usual C meanings of linefeed and
-carriage-return, respectively.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command in
-backticks (``). For example,
-</para>
-
-<example id="ex-rc-backtick">
-<title>Using external command's output in configuration files</title>
-<screen>
-my_hdr X-Operating-System: `uname -a`
-</screen>
-</example>
-
-<para>
-The output of the Unix command <quote>uname -a</quote> will be substituted before the
-line is parsed.
-</para>
-
-<note>
-<para>
-Since initialization files are line oriented, only
-the first line of output from the Unix command will be substituted.
-</para>
-</note>
-
-<para>
-Both environment variables and mutt variables can be accessed by
-prepending <quote>$</quote> to the name of the variable. For example,
-</para>
-
-<example id="ex-rc-env">
-<title>Using environment variables in configuration files</title>
-<screen>
-set record=+sent_on_$HOSTNAME
-</screen>
-</example>
-
-<para>
-will cause mutt to save outgoing messages to a folder named
-<quote>sent_on_kremvax</quote> if the environment variable HOSTNAME is set to
-<quote>kremvax.</quote> (See <link linkend="record">$record</link> for
-details.)
-</para>
-
-<para>
-Mutt expands the variable when it is assigned, not when it is used. If
-the value of a variable on the right-hand side of an assignment
-changes after the assignment, the variable on the left-hand side will
-not be affected.
-</para>
-
-<para>
-The commands understood by mutt are explained in the next paragraphs.
-For a complete list, see the <link linkend="commands">command reference</link>.
-</para>
-
-<para>
-All configuration files are expected to be in the current locale as
-specified by the <link linkend="charset">$charset</link> variable
-which doesn't have a default value since it's determined by Mutt at startup.
-If a configuration file is not encoded in the same character set the
-<link linkend="config-charset">$config_charset</link>
-variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
-</para>
-
-<para>
-This mechanism should be avoided if possible as it has the
-following implications:
-</para>
-
-<itemizedlist>
-
-<listitem><para>These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.</para></listitem>
-
-<listitem><para>If $config_charset is set, it should be set
-in each configuration file because the value is global and <emphasis>not</emphasis>
-per configuration file.</para></listitem>
-
-<listitem><para>Because Mutt first recodes a line before it attempts to parse it,
-a conversion introducing question marks or other characters as
-part of errors (unconvertable characters, transliteration) may introduce syntax
-errors or silently change the meaning of certain tokens (e.g. inserting
-question marks into regular expressions).</para></listitem>
-
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="addrgroup">
-<title>Address groups</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>group</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain" rep="repeat">
-<option>-rx</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-addr</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>ungroup</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-rx</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-addr</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-<literal>group</literal> is used to directly add either addresses or
-regular expressions to the specified group or groups. The different
-categories of arguments to the <literal>group</literal> command can be
-in any order. The flags <literal>-rx</literal> and
-<literal>-addr</literal> specify what the following strings (that cannot
-begin with a hyphen) should be interpreted as: either a regular
-expression or an email address, respectively.
-</para>
-
-<para>
-These address groups can also be created implicitly by the
-<link linkend="alias">alias</link>, <link linkend="lists">lists</link>,
-<link linkend="lists">subscribe</link> and
-<link linkend="alternates">alternates</link> commands by specifying the
-optional <literal>-group</literal> option.
-</para>
-
-<para>
-Once defined, these address groups can be used in
-<link linkend="patterns">patterns</link> to search for and limit the
-display to messages matching a group.
-</para>
-
-<para>
-<literal>ungroup</literal> is used to remove addresses or regular
-expressions from the specified group or groups. The syntax is similar to
-the <literal>group</literal> command, however the special character
-<literal>*</literal> can be used to empty a group of all of its
-contents.
-</para>
-
-</sect1>
-
-<sect1 id="alias">
-<title>Defining/Using aliases</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>alias</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">address</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">address</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-It's usually very cumbersome to remember or type out the address of someone
-you are communicating with. Mutt allows you to create <quote>aliases</quote> which map
-a short string to a full address.
-</para>
-
-<note>
-<para>
-If you want to create an alias for more than
-one address, you <emphasis role="bold">must</emphasis> separate the addresses with a comma (<quote>,</quote>).
-</para>
-</note>
-
-<para>
-The optional <literal>-group</literal> argument to
-<literal>alias</literal> causes the aliased address(es) to be added to
-the named <emphasis>group</emphasis>.
-</para>
-
-<para>
-To remove an alias or aliases (<quote>*</quote> means all aliases):
-</para>
-
-<cmdsynopsis>
-<command>unalias</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">key</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<screen>
-alias muttdude me@cs.hmc.edu (Michael Elkins)
-alias theguys manny, moe, jack
-</screen>
-
-<para>
-Unlike other mailers, Mutt doesn't require aliases to be defined
-in a special file. The <literal>alias</literal> command can appear anywhere in
-a configuration file, as long as this file is <link linkend="source">sourced</link>. Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
-</para>
-
-<para>
-On the other hand, the <link linkend="create-alias"><literal><create-alias></literal></link>
-function can use only one file, the one pointed to by the <link linkend="alias-file">$alias_file</link> variable (which is
-<literal>˜/.muttrc</literal> by default). This file is not special either,
-in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly <link linkend="source">source</link> this file too.
-</para>
-
-<para>
-For example:
-</para>
-
-<example id="ex-alias-external">
-<title>Configuring external alias files</title>
-<screen>
-source /usr/local/share/Mutt.aliases
-source ~/.mail_aliases
-set alias_file=~/.mail_aliases
-</screen>
-</example>
-
-<para>
-To use aliases, you merely use the alias at any place in mutt where mutt
-prompts for addresses, such as the <emphasis>To:</emphasis> or <emphasis>Cc:</emphasis> prompt. You can
-also enter aliases in your editor at the appropriate headers if you have the
-<link linkend="edit-headers">$edit_headers</link> variable set.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-In the alias menu, you can select as many aliases as you want with the
-<literal>select-entry</literal> key (default: <Return>), and use the
-<emphasis>exit</emphasis> key (default: q) to return to the address prompt.
-</para>
-
-</sect1>
-
-<sect1 id="bind">
-<title>Changing the default key bindings</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>bind</command>
-<arg choice="plain">
-<replaceable class="parameter">map</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">function</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command allows you to change the default key bindings (operation
-invoked when pressing a key).
-</para>
-
-<para>
-<emphasis>map</emphasis> specifies in which menu the binding belongs. Multiple maps may
-be specified by separating them with commas (no additional whitespace is
-allowed). The currently defined maps are:
-</para>
-
-<anchor id="maps"/>
-<variablelist>
-
-<varlistentry>
-<term>generic</term>
-<listitem>
-<para>
-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 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.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>alias</term>
-<listitem>
-<para>
-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).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>attach</term>
-<listitem>
-<para>
-The attachment menu is used to access the attachments on received messages.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>browser</term>
-<listitem>
-<para>
-The browser is used for both browsing the local directory structure, and for
-listing all of your incoming mailboxes.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>editor</term>
-<listitem>
-<para>
-The editor is the line-based editor the user enters text data.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>index</term>
-<listitem>
-<para>
-The index is the list of messages contained in a mailbox.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>compose</term>
-<listitem>
-<para>
-The compose menu is the screen used when sending a new message.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>pager</term>
-<listitem>
-<para>
-The pager is the mode used to display message/attachment data, and help
-listings.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>pgp</term>
-<listitem>
-<para>
-The pgp menu is used to select the OpenPGP keys used to encrypt outgoing
-messages.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>smime</term>
-<listitem>
-<para>
-The smime menu is used to select the OpenSSL certificates used to encrypt outgoing
-messages.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>postpone</term>
-<listitem>
-<para>
-The postpone menu is similar to the index menu, except is used when
-recalling a message the user was composing, but saved until later.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>query</term>
-<listitem>
-<para>
-The query menu is the browser for results returned by
-<link linkend="query-command">$query_command</link>.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>mix</term>
-<listitem>
-<para>
-The mixmaster screen is used to select remailer options for outgoing
-messages (if Mutt is compiled with Mixmaster support).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-<para>
-<emphasis>key</emphasis> is the key (or key sequence) you wish to bind. To specify a
-control character, use the sequence <emphasis>\Cx</emphasis>, where <emphasis>x</emphasis> is the
-letter of the control character (for example, to specify control-A use
-<quote>\Ca</quote>). Note that the case of <emphasis>x</emphasis> as well as <emphasis>\C</emphasis> is
-ignored, so that <emphasis>\CA</emphasis>, <emphasis>\Ca</emphasis>, <emphasis>\cA</emphasis> and <emphasis>\ca</emphasis> are all
-equivalent. An alternative form is to specify the key as a three digit
-octal number prefixed with a <quote>\</quote> (for example <emphasis>\177</emphasis> is
-equivalent to <emphasis>\c?</emphasis>). In addition, <emphasis>key</emphasis> may
-be a symbolic name as shown in <xref linkend="tab-key-names"/>.
-</para>
-
-<table id="tab-key-names">
-<title>Symbolic key names</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Symbolic name</entry><entry>Meaning</entry></row>
-</thead>
-<tbody>
-<row><entry>\t</entry><entry>tab</entry></row>
-<row><entry><tab></entry><entry>tab</entry></row>
-<row><entry><backtab></entry><entry>backtab / shift-tab</entry></row>
-<row><entry>\r</entry><entry>carriage return</entry></row>
-<row><entry>\n</entry><entry>newline</entry></row>
-<row><entry>\e</entry><entry>escape</entry></row>
-<row><entry><esc></entry><entry>escape</entry></row>
-<row><entry><up></entry><entry>up arrow</entry></row>
-<row><entry><down></entry><entry>down arrow</entry></row>
-<row><entry><left></entry><entry>left arrow</entry></row>
-<row><entry><right></entry><entry>right arrow</entry></row>
-<row><entry><pageup></entry><entry>Page Up</entry></row>
-<row><entry><pagedown></entry><entry>Page Down</entry></row>
-<row><entry><backspace></entry><entry>Backspace</entry></row>
-<row><entry><delete></entry><entry>Delete</entry></row>
-<row><entry><insert></entry><entry>Insert</entry></row>
-<row><entry><enter></entry><entry>Enter</entry></row>
-<row><entry><return></entry><entry>Return</entry></row>
-<row><entry><home></entry><entry>Home</entry></row>
-<row><entry><end></entry><entry>End</entry></row>
-<row><entry><space></entry><entry>Space bar</entry></row>
-<row><entry><f1></entry><entry>function key 1</entry></row>
-<row><entry><f10></entry><entry>function key 10</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-<emphasis>key</emphasis> does not need to be enclosed in quotes unless it contains a
-space (<quote> </quote>) or semi-colon (<quote>;</quote>).
-</para>
-
-<para>
-<emphasis>function</emphasis> specifies which action to take when <emphasis>key</emphasis> is pressed.
-For a complete list of functions, see the <link linkend="functions">reference</link>. The special function <literal><noop></literal> unbinds the specified key
-sequence.
-</para>
-
-</sect1>
-
-<sect1 id="charset-hook">
-<title>Defining aliases for character sets </title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>charset-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">alias</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">charset</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>iconv-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">charset</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">local-charset</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-The <literal>charset-hook</literal> 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.
-</para>
-
-<para>
-The <literal>iconv-hook</literal> 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.
-</para>
-
-</sect1>
-
-<sect1 id="folder-hook">
-<title>Setting variables based upon mailbox</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>folder-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]regexp</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-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. <emphasis>regexp</emphasis> is a regular expression specifying
-in which mailboxes to execute <emphasis>command</emphasis> before loading. If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
-</para>
-
-<note>
-<para>
-If you use the <quote>!</quote> shortcut for <link linkend="spoolfile">$spoolfile</link> at the beginning of the pattern, you must place it
-inside of double or single quotes in order to distinguish it from the
-logical <emphasis>not</emphasis> operator for the expression.
-</para>
-</note>
-
-<note>
-<para>
-Settings are <emphasis>not</emphasis> restored when you leave the mailbox.
-For example, a command action to perform is to change the sorting method
-based upon the mailbox being read:
-</para>
-</note>
-
-<screen>
-folder-hook mutt set sort=threads
-</screen>
-
-<para>
-However, the sorting method is not restored to its previous value when
-reading a different mailbox. To specify a <emphasis>default</emphasis> command, use the
-pattern <quote>.</quote> before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
-The following example will set the <link linkend="sort">sort</link> variable
-to <literal>date-sent</literal> for all folders but to <literal>threads</literal>
-for all folders containing <quote>mutt</quote> in their name.
-</para>
-
-<example id="ex-folder-sorting">
-<title>Setting sort method based on mailbox name</title>
-<screen>
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
-</screen>
-</example>
-
-</sect1>
-
-<sect1 id="macro">
-<title>Keyboard macros</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>macro</command>
-<arg choice="plain">
-<replaceable class="parameter">menu</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">sequence</replaceable>
-</arg>
-<arg choice="opt">
-<replaceable class="parameter">description</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-Macros are useful when you would like a single key to perform a series of
-actions. When you press <emphasis>key</emphasis> in menu <emphasis>menu</emphasis>, Mutt will behave as if
-you had typed <emphasis>sequence</emphasis>. So if you have a common sequence of commands
-you type, you can create a macro to execute those commands with a single
-key or fewer keys.
-</para>
-
-<para>
-<emphasis>menu</emphasis> is the <link linkend="maps">map</link> which the macro will be bound in.
-Multiple maps may be specified by separating multiple menu arguments by
-commas. Whitespace may not be used in between the menu arguments and the
-commas separating them.
-</para>
-
-<para>
-<emphasis>key</emphasis> and <emphasis>sequence</emphasis> are expanded by the same rules as the
-<link linkend="bind">key bindings</link> with some additions. The
-first is that control characters in <emphasis>sequence</emphasis> can also be specified
-as <emphasis>ˆx</emphasis>. In order to get a caret (<quote>ˆ</quote>) you need to use
-<emphasis>ˆˆ</emphasis>. Secondly, to specify a certain key such as <emphasis>up</emphasis>
-or to invoke a function directly, you can use the format
-<emphasis><key name></emphasis> and <emphasis><function name></emphasis>. For a listing of key
-names see the section on <link linkend="bind">key bindings</link>. Functions
-are listed in the <link linkend="functions">reference</link>.
-</para>
-
-<para>
-The advantage with using function names directly is that the macros will
-work regardless of the current key bindings, so they are not dependent on
-the user having particular key definitions. This makes them more robust
-and portable, and also facilitates defining of macros in files used by more
-than one user (e.g., the system Muttrc).
-</para>
-
-<para>
-Optionally you can specify a descriptive text after <emphasis>sequence</emphasis>,
-which is shown in the help screens.
-</para>
-
-<note>
-<para>
-Macro definitions (if any) listed in the help screen(s), are
-silently truncated at the screen width, and are not wrapped.
-</para>
-</note>
-
-</sect1>
-
-<sect1 id="color">
-<title>Using color and mono video attributes</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>color</command>
-<arg choice="plain">
-<replaceable class="parameter">object</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>color</command>
-<group choice="req">
-<arg choice="plain">
-<option>header</option>
-</arg>
-<arg choice="plain">
-<option>body</option>
-</arg>
-</group>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>color</command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>uncolor</command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-If your terminal supports color, you can spice up Mutt by creating your own
-color scheme. To define the color of an object (type of information), you
-must specify both a foreground color <emphasis role="bold">and</emphasis> a background color (it is not
-possible to only specify one or the other).
-</para>
-
-<para>
-<emphasis>header</emphasis> and <emphasis>body</emphasis> match <emphasis>regexp</emphasis>
-in the header/body of a message, <emphasis>index</emphasis> matches <emphasis>pattern</emphasis>
-(see <xref linkend="patterns"/>) in the message index.
-</para>
-
-<para>
-<emphasis>object</emphasis> can be one of:
-</para>
-
-<itemizedlist>
-<listitem><para>attachment</para></listitem>
-<listitem><para>bold (hiliting bold patterns in the body of messages)</para></listitem>
-<listitem><para>error (error messages printed by Mutt)</para></listitem>
-<listitem><para>hdrdefault (default color of the message header in the pager)</para></listitem>
-<listitem><para>indicator (arrow or bar used to indicate the current item in a menu)</para></listitem>
-<listitem><para>markers (the <quote>+</quote> markers at the beginning of wrapped lines in the pager)</para></listitem>
-<listitem><para>message (informational messages)</para></listitem>
-<listitem><para>normal</para></listitem>
-<listitem><para>quoted (text matching <link linkend="quote-regexp">$quote_regexp</link> in the body of a message)</para></listitem>
-<listitem><para>quoted1, quoted2, ..., quoted<emphasis role="bold">N</emphasis> (higher levels of quoting)</para></listitem>
-<listitem><para>search (hiliting of words in the pager)</para></listitem>
-<listitem><para>signature</para></listitem><listitem><para>status (mode lines used to display info about the mailbox or message)</para></listitem>
-<listitem><para>tilde (the <quote>˜</quote> used to pad blank lines in the pager)</para></listitem>
-<listitem><para>tree (thread tree drawn in the message index and attachment menu)</para></listitem>
-<listitem><para>underline (hiliting underlined patterns in the body of messages)</para></listitem>
-</itemizedlist>
-
-<para>
-<emphasis>foreground</emphasis> and <emphasis>background</emphasis> can be one of the following:
-</para>
-
-<itemizedlist>
-<listitem><para>white</para></listitem>
-<listitem><para>black</para></listitem>
-<listitem><para>green</para></listitem>
-<listitem><para>magenta</para></listitem>
-<listitem><para>blue</para></listitem>
-<listitem><para>cyan</para></listitem>
-<listitem><para>yellow</para></listitem>
-<listitem><para>red</para></listitem>
-<listitem><para>default</para></listitem>
-<listitem><para>color<emphasis>x</emphasis></para>
-</listitem>
-</itemizedlist>
-
-<para>
-<emphasis>foreground</emphasis> can optionally be prefixed with the keyword <literal>bright</literal> to make
-the foreground color boldfaced (e.g., <literal>brightred</literal>).
-</para>
-
-<para>
-If your terminal supports it, the special keyword <emphasis>default</emphasis> can be
-used as a transparent color. The value <emphasis>brightdefault</emphasis> is also valid.
-If Mutt is linked against the <emphasis>S-Lang</emphasis> library, you also need to set
-the <emphasis>COLORFGBG</emphasis> environment variable to the default colors of your
-terminal for this to work; for example (for Bourne-like shells):
-</para>
-
-<screen>
-set COLORFGBG="green;black"
-export COLORFGBG
-</screen>
-
-<note>
-<para>
-The <emphasis>S-Lang</emphasis> library requires you to use the <emphasis>lightgray</emphasis>
-and <emphasis>brown</emphasis> keywords instead of <emphasis>white</emphasis> and <emphasis>yellow</emphasis> when
-setting this variable.
-</para>
-</note>
-
-<note>
-<para>
-The uncolor command can be applied to the index object only. It
-removes entries from the list. You <emphasis role="bold">must</emphasis> specify the same pattern
-specified in the color command for it to be removed. The pattern <quote>*</quote> is
-a special token which means to clear the color index list of all entries.
-</para>
-</note>
-
-<para>
-Mutt also recognizes the keywords <emphasis>color0</emphasis>, <emphasis>color1</emphasis>, …,
-<emphasis>color</emphasis><emphasis role="bold">N-1</emphasis> (<emphasis role="bold">N</emphasis> 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 <emphasis>color2</emphasis>
-for your xterm), since color names may then lose their normal meaning.
-</para>
-
-<para>
-If your terminal does not support color, it is still possible change the video
-attributes through the use of the <quote>mono</quote> command:
-</para>
-
-<anchor id="mono"/>
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>mono</command>
-<arg choice="plain">
-<replaceable class="parameter">object</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>mono</command>
-<group choice="req">
-<arg choice="plain">
-<option>header</option>
-</arg>
-<arg choice="plain">
-<option>body</option>
-</arg>
-</group>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>mono</command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unmono</command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-For <emphasis>object</emphasis>, see the color command. <emphasis>attribute</emphasis>
-can be one of the following:
-</para>
-
-<itemizedlist>
-<listitem><para>none</para></listitem>
-<listitem><para>bold</para></listitem>
-<listitem><para>underline</para></listitem>
-<listitem><para>reverse</para></listitem>
-<listitem><para>standout</para></listitem>
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="ignore">
-<title>Message header display</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>ignore</command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unignore</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-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 in the pager.
-</para>
-
-<para>
-You do not need to specify the full header field name. For example,
-<quote>ignore content-</quote> will ignore all header fields that begin with the pattern
-<quote>content-</quote>. <quote>ignore *</quote> will ignore all headers.
-</para>
-
-<para>
-To remove a previously added token from the list, use the <quote>unignore</quote> command.
-The <quote>unignore</quote> command will make Mutt display headers with the given pattern.
-For example, if you do <quote>ignore x-</quote> it is possible to <quote>unignore x-mailer</quote>.
-</para>
-
-<para>
-<quote>unignore *</quote> will remove all tokens from the ignore list.
-</para>
-
-<para>
-For example:
-</para>
-
-<example id="ex-header-weeding">
-<title>Header weeding</title>
-<screen>
-# 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:
-</screen>
-</example>
-
-<anchor id="hdr-order"/>
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>hdr_order</command>
-<arg choice="plain">
-<replaceable class="parameter">header</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">header</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unhdr_order</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>header</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-With the <literal>hdr_order</literal> command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
-</para>
-
-<para>
-<quote>unhdr_order *</quote> will clear all previous headers from the order list,
-thus removing the header order effects set by the system-wide startup file.
-</para>
-
-<example id="ex-hdr-order">
-<title>Configuring header display order</title>
-<screen>
-hdr_order From Date: From: To: Cc: Subject:
-</screen>
-</example>
-
-</sect1>
-
-<sect1 id="alternates">
-<title>Alternative addresses</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>alternates</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable>regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unalternates</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-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 <link linkend="reply-to">$reply_to</link>.)
-</para>
-
-<para>
-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 <literal>alternates</literal> command: It takes a list of regular
-expressions, each of which can identify an address under which you
-receive e-mail.
-</para>
-
-<para>
-As addresses are matched using regular expressions and not exact strict
-comparisons, you should make sure you specify your addresses as precise
-as possible to avoid mismatches. For example, if you specify:
-</para>
-
-<screen>
-alternates user@example
-</screen>
-
-<para>
-mutt will consider <quote><literal>some-user@example</literal></quote> as
-being your address, too which may not be desired. As a solution, in such
-cases addresses should be specified as:
-</para>
-
-<screen>
-alternates '^user@example$'
-</screen>
-
-<para>
-The <literal>-group</literal> flag causes all of the subsequent regular expressions
-to be added to the named group.
-</para>
-
-<para>
-The <literal>unalternates</literal> command can be used to write exceptions to
-<literal>alternates</literal> patterns. If an address matches something in an
-<literal>alternates</literal> command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an <literal>unalternates</literal>
-command.
-</para>
-
-<para>
-To remove a regular expression from the <literal>alternates</literal> list, use the
-<literal>unalternates</literal> command with exactly the same <emphasis>regexp</emphasis>.
-Likewise, if the <emphasis>regexp</emphasis> for an <literal>alternates</literal> command matches
-an entry on the <literal>unalternates</literal> list, that <literal>unalternates</literal>
-entry will be removed. If the <emphasis>regexp</emphasis> for <literal>unalternates</literal>
-is <quote>*</quote>, <emphasis>all entries</emphasis> on <literal>alternates</literal> will be removed.
-</para>
-
-</sect1>
-
-<sect1 id="lists">
-<title>Mailing lists</title>
-
-<anchor id="subscribe"/>
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>lists</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unlists</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>subscribe</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unsubscribe</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-Mutt has a few nice features for <link linkend="using-lists">handling mailing lists</link>. 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 <link linkend="list-reply"><literal><list-reply></literal></link> 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.
-</para>
-
-<note>
-<para>
-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
-<link linkend="followup-to">$followup_to</link>
-configuration variable.
-</para>
-</note>
-
-<para>
-More precisely, Mutt 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 <quote>lists</quote>
-command. To mark it as subscribed, use <quote>subscribe</quote>.
-</para>
-
-<para>
-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
-<quote>subscribe [0-9]*@bugs.guug.de</quote>. Often, it's sufficient to just
-give a portion of the list's e-mail address.
-</para>
-
-<para>
-Specify as much of the address as you need to to remove ambiguity. For
-example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed to <emphasis>mutt-users@mutt.org</emphasis>. So, to tell Mutt
-that this is a mailing list, you could add <quote>lists mutt-users@</quote> to your
-initialization file. To tell mutt that you are subscribed to it,
-add <quote>subscribe mutt-users</quote> to your initialization file instead.
-If you also happen to get mail from someone whose address is
-<emphasis>mutt-users@example.com</emphasis>, you could use
-<quote>lists ^mutt-users@mutt\\.org$</quote>
-or <quote>subscribe ^mutt-users@mutt\\.org$</quote> to
-match only mail from the actual list.
-</para>
-
-<para>
-The <literal>-group</literal> flag adds all of the subsequent regular expressions
-to the named group.
-</para>
-
-<para>
-The <quote>unlists</quote> command is used to remove a token from the list of
-known and subscribed mailing-lists. Use <quote>unlists *</quote> to remove all
-tokens.
-</para>
-
-<para>
-To remove a mailing list from the list of subscribed mailing lists,
-but keep it on the list of known mailing lists, use <quote>unsubscribe</quote>.
-</para>
-
-</sect1>
-
-<sect1 id="mbox-hook">
-<title>Using Multiple spool mailboxes</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>mbox-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is used to move read messages from a specified mailbox to a
-different mailbox automatically when you quit or change folders.
-<emphasis>pattern</emphasis> is a regular expression specifying the mailbox to treat as a
-<quote>spool</quote> mailbox and <emphasis>mailbox</emphasis> specifies where mail should be saved when
-read.
-</para>
-
-<para>
-Unlike some of the other <emphasis>hook</emphasis> commands, only the <emphasis>first</emphasis> matching
-pattern is used (it is not possible to save read mail in more than a single
-mailbox).
-</para>
-
-</sect1>
-
-<sect1 id="mailboxes">
-<title>Monitoring incoming mail</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>mailboxes</command>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unmailboxes</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-This command specifies folders which can receive mail and
-which will be checked for new messages periodically.
-</para>
-
-<para>
-<emphasis>folder</emphasis> can either be a local file or directory
-(Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP
-support, <emphasis>folder</emphasis> can also be a POP/IMAP folder
-URL. The URL syntax is described in <xref linkend="url-syntax"/>,
-POP and IMAP are described in <xref linkend="pop"/> and <xref linkend="imap"/>
-respectively.
-</para>
-
-<para>
-Mutt provides a number of advanced features for handling (possibly many)
-folders and new mail within them, please refer to
-<xref linkend="handling-folders"/> for details (including in what
-situations and how often Mutt checks for new mail).
-</para>
-
-<para>
-The <quote>unmailboxes</quote> command is used to remove a token from the list
-of folders which receive mail. Use <quote>unmailboxes *</quote> to remove all
-tokens.
-</para>
-
-<note>
-<para>
-The folders in the <literal>mailboxes</literal> command are resolved when
-the command is executed, so if these names contain <link linkend="shortcuts">shortcut characters</link> (such as <quote>=</quote> and <quote>!</quote>), any variable
-definition that affects these characters (like <link linkend="folder">$folder</link> and <link linkend="spoolfile">$spoolfile</link>)
-should be set before the <literal>mailboxes</literal> command. If
-none of these shorcuts are used, a local path should be absolute as
-otherwise mutt tries to find it relative to the directory
-from where mutt was started which may not always be desired.
-</para>
-</note>
-
-<para>
-For Mbox and Mmdf folders, new mail is detected by comparing access and/or
-modification times of files: Mutt assumes a folder has new mail if it wasn't
-accessed after it was last modified. Utilities like <literal>biff</literal> or
-<literal>frm</literal> or any other program which accesses the mailbox might cause
-Mutt to never detect new mail for that mailbox if they do not properly reset the
-access time. Other possible causes of Mutt not detecting new mail in these folders
-are backup tools (updating access times) or filesystems mounted without
-access time update support.
-</para>
-
-<para>
-In cases where new mail detection for Mbox or Mmdf folders appears to be
-unreliable, the
-<link linkend="check-mbox-size">$check_mbox_size</link>
-option can be used to make Mutt track and consult file sizes for new
-mail detection instead.
-</para>
-
-</sect1>
-
-<sect1 id="my-hdr">
-<title>User defined headers</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>my_hdr</command>
-<arg choice="plain">
-<replaceable class="parameter">string</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unmy_hdr</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">field</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-The <literal>my_hdr</literal> command allows you to create your own header
-fields which will be added to every message you send.
-</para>
-
-<para>
-For example, if you would like to add an <quote>Organization:</quote> header field to
-all of your outgoing messages, you can put the command
-</para>
-
-<example id="ex-my-hdr">
-<title>Defining custom headers</title>
-<screen>
-my_hdr Organization: A Really Big Company, Anytown, USA
-</screen>
-</example>
-
-<para>
-in your <literal>.muttrc</literal>.
-</para>
-
-<note>
-<para>
-Space characters are <emphasis>not</emphasis> allowed between the keyword and
-the colon (<quote>:</quote>). The standard for electronic mail (RFC2822) says that
-space is illegal there, so Mutt enforces the rule.
-</para>
-</note>
-
-<para>
-If you would like to add a header field to a single message, you should
-either set the <link linkend="edit-headers">$edit_headers</link> variable,
-or use the <literal><edit-headers></literal> function (default: <quote>E</quote>) in the compose menu so
-that you can edit the header of your message along with the body.
-</para>
-
-<para>
-To remove user defined header fields, use the <literal>unmy_hdr</literal>
-command. You may specify an asterisk (<quote>*</quote>) to remove all header
-fields, or the fields to remove. For example, to remove all <quote>To</quote> and
-<quote>Cc</quote> header fields, you could use:
-</para>
-
-<screen>
-unmy_hdr to cc
-</screen>
-
-</sect1>
-
-<sect1 id="save-hook">
-<title>Specify default save mailbox</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>save-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is used to override the default mailbox used when saving
-messages. <emphasis>mailbox</emphasis> will be used as the default if the message
-matches <emphasis>pattern</emphasis>, see <xref linkend="pattern-hook"/> for information
-on the exact format.
-</para>
-
-<para>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <link linkend="index-format">$index_format</link> to
-<emphasis>mailbox</emphasis> after it was expanded.
-</para>
-
-<para>
-Examples:
-</para>
-
-<example id="ex-save-hook-exando">
-<title>Using %-expandos in <literal>save-hook</literal></title>
-<screen>
-# default: save all to ~/Mail/<author name>
-save-hook . ~/Mail/%F
-
-# save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
-save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
-# save from aol.com to $folder/spam
-save-hook aol\\.com$ +spam
-</screen>
-</example>
-
-<para>
-Also see the <link linkend="fcc-save-hook">fcc-save-hook</link> command.
-</para>
-
-</sect1>
-
-<sect1 id="fcc-hook">
-<title>Specify default Fcc: mailbox when composing</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>fcc-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is used to save outgoing mail in a mailbox other than
-<link linkend="record">$record</link>. Mutt searches the initial list of
-message recipients for the first matching <emphasis>regexp</emphasis> and uses <emphasis>mailbox</emphasis>
-as the default Fcc: mailbox. If no match is found the message will be saved
-to <link linkend="record">$record</link> mailbox.
-</para>
-
-<para>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <link linkend="index-format">$index_format</link> to
-<emphasis>mailbox</emphasis> after it was expanded.
-</para>
-
-<para>
-See <xref linkend="pattern-hook"/> for information on the exact format of <emphasis>pattern</emphasis>.
-</para>
-
-<para>
-Example: <literal>fcc-hook [@.]aol\\.com$ +spammers</literal>
-</para>
-
-<para>
-The above will save a copy of all messages going to the aol.com domain to
-the `+spammers' mailbox by default. Also see the <link linkend="fcc-save-hook">fcc-save-hook</link> command.
-</para>
-
-</sect1>
-
-<sect1 id="fcc-save-hook">
-<title>Specify default save filename and default Fcc: mailbox at once</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>fcc-save-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is a shortcut, equivalent to doing both a <link linkend="fcc-hook">fcc-hook</link>
-and a <link linkend="save-hook">save-hook</link> with its arguments,
-including %-expansion on <emphasis>mailbox</emphasis> according
-to <link linkend="index-format">$index_format</link>.
-</para>
-
-</sect1>
-
-<sect1 id="send-hook">
-<title>Change settings based upon message recipients</title>
-
-<anchor id="reply-hook"/>
-<anchor id="send2-hook"/>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>reply-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>send-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>send2-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-These commands can be used to execute arbitrary configuration commands based
-upon recipients of the message. <emphasis>pattern</emphasis> is used to match
-the message, see <xref linkend="pattern-hook"/> for details. <emphasis>command</emphasis>
-is executed when <emphasis>pattern</emphasis> matches.
-</para>
-
-<para>
-<literal>reply-hook</literal> is matched against the message you are <emphasis>replying to</emphasis>,
-instead of the message you are <emphasis>sending</emphasis>. <literal>send-hook</literal> is
-matched against all messages, both <emphasis>new</emphasis>
-and <emphasis>replies</emphasis>.
-</para>
-
-<note>
-<para>
-<literal>reply-hook</literal>s are matched <emphasis role="bold">before</emphasis> the <literal>send-hook</literal>, <emphasis role="bold">regardless</emphasis>
-of the order specified in the user's configuration file.
-</para>
-</note>
-
-<para>
-<literal>send2-hook</literal> is matched every time a message is changed, either
-by editing it, or by using the compose menu to change its recipients
-or subject. <literal>send2-hook</literal> is executed after <literal>send-hook</literal>, and
-can, e.g., be used to set parameters such as the <link linkend="sendmail">$sendmail</link> variable depending on the message's sender
-address.
-</para>
-
-<para>
-For each type of <literal>send-hook</literal> or <literal>reply-hook</literal>, when multiple matches
-occur, commands are executed in the order they are specified in the muttrc
-(for that type of hook).
-</para>
-
-<para>
-Example: <literal>send-hook mutt "set mime_forward signature=''"</literal>
-</para>
-
-<para>
-Another typical use for this command is to change the values of the
-<link linkend="attribution">$attribution</link>, <link linkend="signature">$signature</link> and <link linkend="locale">$locale</link>
-variables in order to change the language of the attributions and
-signatures based upon the recipients.
-</para>
-
-<note>
-<para>
-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
-<literal>my_hdr</literal> 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.
-</para>
-</note>
-
-</sect1>
-
-<sect1 id="message-hook">
-<title>Change settings before formatting a message</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>message-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command can be used to execute arbitrary configuration commands
-before viewing or formatting a message based upon information about the message.
-<emphasis>command</emphasis> is executed if the <emphasis>pattern</emphasis> matches the message to be
-displayed. When multiple matches occur, commands are executed in the order
-they are specified in the muttrc.
-</para>
-
-<para>
-See <xref linkend="pattern-hook"/> for
-information on the exact format of <emphasis>pattern</emphasis>.
-</para>
-
-<para>
-Example:
-</para>
-
-<screen>
-message-hook ~A 'set pager=builtin'
-message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
-</screen>
-
-</sect1>
-
-<sect1 id="crypt-hook">
-<title>Choosing the cryptographic key of the recipient</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>crypt-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">keyid</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-When encrypting messages with PGP/GnuPG 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 would
-normally use. The <literal>crypt-hook</literal> 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.
-</para>
-
-<para>
-The meaning of <emphasis>keyid</emphasis> 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.
-</para>
-
-</sect1>
-
-<sect1 id="push">
-<title>Adding key sequences to the keyboard buffer</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>push</command>
-<arg choice="plain">
-<replaceable class="parameter">string</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-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 <link linkend="macro">macro</link> 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:
-</para>
-
-<example id="ex-folder-hook-push">
-<title>Embedding <literal>push</literal> in <literal>folder-hook</literal></title>
-<screen>
-folder-hook . 'push <collapse-all>'
-</screen>
-</example>
-
-</sect1>
-
-<sect1 id="exec">
-<title>Executing functions</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>exec</command>
-<arg choice="plain">
-<replaceable class="parameter">function</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">function</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command can be used to execute any function. Functions are
-listed in the <link linkend="functions">function reference</link>.
-<quote>exec function</quote> is equivalent to <quote>push <function></quote>.
-</para>
-
-</sect1>
-
-<sect1 id="score-command">
-<title>Message Scoring</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>score</command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">value</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unscore</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-The <literal>score</literal> commands adds <emphasis>value</emphasis> to a message's score if <emphasis>pattern</emphasis>
-matches it. <emphasis>pattern</emphasis> is a string in the format described in the <link linkend="patterns">patterns</link> section (note: For efficiency reasons, patterns
-which scan information not available in the index, such as <literal>˜b</literal>,
-<literal>˜B</literal> or <literal>˜h</literal>, may not be used). <emphasis>value</emphasis> is a
-positive or negative integer. A message's final score is the sum total of all
-matching <literal>score</literal> entries. However, you may optionally prefix <emphasis>value</emphasis> with
-an equal sign (=) to cause evaluation to stop at a particular entry if there is
-a match. Negative final scores are rounded up to 0.
-</para>
-
-<para>
-The <literal>unscore</literal> command removes score entries from the list. You <emphasis role="bold">must</emphasis>
-specify the same pattern specified in the <literal>score</literal> command for it to be
-removed. The pattern <quote>*</quote> is a special token which means to clear the list
-of all score entries.
-</para>
-
-</sect1>
-
-<sect1 id="spam">
-<title>Spam detection</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>spam</command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">format</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>nospam</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-Mutt has generalized support for external spam-scoring filters.
-By defining your spam patterns with the <literal>spam</literal> and <literal>nospam</literal>
-commands, you can <emphasis>limit</emphasis>, <emphasis>search</emphasis>, and <emphasis>sort</emphasis> 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 <literal>%H</literal> selector in the <link linkend="index-format">$index_format</link> variable. (Tip: try <literal>%?H?[%H] ?</literal>
-to display spam tags only when they are defined for a given message.)
-</para>
-
-<para>
-Your first step is to define your external filter's spam patterns using
-the <literal>spam</literal> command. <emphasis>pattern</emphasis> 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 <quote>spam tag</quote> or
-<quote>spam attribute</quote> (unless it also matches a <literal>nospam</literal> pattern -- see
-below.) The appearance of this attribute is entirely up to you, and is
-governed by the <emphasis>format</emphasis> parameter. <emphasis>format</emphasis> can be any static
-text, but it also can include back-references from the <emphasis>pattern</emphasis>
-expression. (A regular expression <quote>back-reference</quote> refers to a
-sub-expression contained within parentheses.) <literal>%1</literal> is replaced with
-the first back-reference in the regex, <literal>%2</literal> with the second, etc.
-</para>
-
-<para>
-If you're using multiple spam filters, a message can have more than
-one spam-related header. You can define <literal>spam</literal> 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 <emphasis>format</emphasis> strings joined
-together, with the value of $spam_separator separating
-them.
-</para>
-
-<para>
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-define these spam settings:
-</para>
-
-<example id="ex-spam">
-<title>Configuring spam detection</title>
-<screen>
-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=", "
-</screen>
-</example>
-
-<para>
-If I then received a message that DCC registered with <quote>many</quote> hits
-under the <quote>Fuz2</quote> checksum, and that PureMessage registered with a
-97% probability of being spam, that message's spam tag would read
-<literal>90+/DCC-Fuz2, 97/PM</literal>. (The four characters before <quote>=many</quote> in a
-DCC report indicate the checksum used -- in this case, <quote>Fuz2</quote>.)
-</para>
-
-<para>
-If the $spam_separator variable is unset, then each
-spam pattern match supersedes the previous one. Instead of getting
-joined <emphasis>format</emphasis> strings, you'll get only the last one to match.
-</para>
-
-<para>
-The spam tag is what will be displayed in the index when you use
-<literal>%H</literal> in the <literal>$index_format</literal> variable. It's also the
-string that the <literal>˜H</literal> pattern-matching expression matches against for
-<literal><search></literal> and <literal><limit></literal> functions. And it's what sorting by spam
-attribute will use as a sort key.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-Generally, when you sort by spam tag, mutt will sort <emphasis>lexically</emphasis> --
-that is, by ordering strings alphanumerically. 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
-<literal>sort -n</literal>.) A message with no spam attributes at all -- that is, one
-that didn't match <emphasis>any</emphasis> of your <literal>spam</literal> patterns -- is sorted at
-lowest priority. Numbers are sorted next, beginning with 0 and ranging
-upward. Finally, non-numeric strings are sorted, with <quote>a</quote> taking lower
-priority than <quote>z</quote>. 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.
-</para>
-
-<para>
-The <literal>nospam</literal> command can be used to write exceptions to <literal>spam</literal>
-patterns. If a header pattern matches something in a <literal>spam</literal> command,
-but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a <literal>nospam</literal> command.
-</para>
-
-<para>
-If the <emphasis>pattern</emphasis> given to <literal>nospam</literal> is exactly the same as the
-<emphasis>pattern</emphasis> on an existing <literal>spam</literal> list entry, the effect will be to
-remove the entry from the spam list, instead of adding an exception.
-Likewise, if the <emphasis>pattern</emphasis> for a <literal>spam</literal> command matches an entry
-on the <literal>nospam</literal> list, that <literal>nospam</literal> entry will be removed. If the
-<emphasis>pattern</emphasis> for <literal>nospam</literal> is <quote>*</quote>, <emphasis>all entries on both lists</emphasis>
-will be removed. This might be the default action if you use <literal>spam</literal>
-and <literal>nospam</literal> in conjunction with a <literal>folder-hook</literal>.
-</para>
-
-<para>
-You can have as many <literal>spam</literal> or <literal>nospam</literal> commands as you like.
-You can even do your own primitive spam detection within mutt -- for
-example, if you consider all mail from <literal>MAILER-DAEMON</literal> to be spam,
-you can use a <literal>spam</literal> command like this:
-</para>
-
-<screen>
-spam "^From: .*MAILER-DAEMON" "999"
-</screen>
-
-</sect1>
-
-<sect1 id="set">
-<title>Setting and Querying Variables</title>
-
-<sect2 id="set-commands">
-<title>Commands</title>
-
-<para>
-The following commands are available to manipulate and query variables:
-</para>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>set</command>
-<group choice="req">
-<arg choice="plain">
-<group choice="opt">
-<arg choice="plain"><option>no</option></arg>
-<arg choice="plain"><option>inv</option></arg>
-</group>
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">variable=value</replaceable>
-</arg>
-</group>
-<arg choice="opt" rep="repeat"/>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>toggle</command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unset</command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>reset</command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is used to set (and unset) <link linkend="variables">configuration variables</link>. There are four basic types of variables:
-boolean, number, string and quadoption. <emphasis>boolean</emphasis> variables can be
-<emphasis>set</emphasis> (true) or <emphasis>unset</emphasis> (false). <emphasis>number</emphasis> variables can be
-assigned a positive integer value.
-<emphasis>string</emphasis> variables consist of any number of printable characters and
-must be enclosed in quotes if they contain spaces or tabs. You
-may also use the escape sequences <quote>\n</quote> and <quote>\t</quote> for newline and tab, respectively.
-<emphasis>quadoption</emphasis> variables are used to control whether or not to be prompted
-for certain actions, or to specify a default action. A value of <emphasis>yes</emphasis>
-will cause the action to be carried out automatically as if you had answered
-yes to the question. Similarly, a value of <emphasis>no</emphasis> will cause the
-action to be carried out as if you had answered <quote>no.</quote> A value of
-<emphasis>ask-yes</emphasis> will cause a prompt with a default answer of <quote>yes</quote> and
-<emphasis>ask-no</emphasis> will provide a default answer of <quote>no.</quote>
-</para>
-
-<para>
-Prefixing a variable with <quote>no</quote> will unset it. Example: <literal>set noaskbcc</literal>.
-</para>
-
-<para>
-For <emphasis>boolean</emphasis> variables, you may optionally prefix the variable name with
-<literal>inv</literal> to toggle the value (on or off). This is useful when writing
-macros. Example: <literal>set invsmart_wrap</literal>.
-</para>
-
-<para>
-The <literal>toggle</literal> command automatically prepends the <literal>inv</literal> prefix to all
-specified variables.
-</para>
-
-<para>
-The <literal>unset</literal> command automatically prepends the <literal>no</literal> prefix to all
-specified variables.
-</para>
-
-<para>
-Using the <literal><enter-command></literal> function in the <emphasis>index</emphasis> menu, you can query the
-value of a variable by prefixing the name of the variable with a question
-mark:
-</para>
-
-<screen>
-set ?allow_8bit
-</screen>
-
-<para>
-The question mark is actually only required for boolean and quadoption
-variables.
-</para>
-
-<para>
-The <literal>reset</literal> command resets all given variables to the compile time
-defaults (hopefully mentioned in this manual). If you use the command
-<literal>set</literal> and prefix the variable with <quote>&</quote> this has the same
-behavior as the reset command.
-</para>
-
-<para>
-With the <literal>reset</literal> command there exists the special variable <quote>all</quote>,
-which allows you to reset all variables to their system defaults.
-</para>
-
-</sect2>
-
-<sect2 id="set-myvar">
-<title>User-defined variables</title>
-
-<sect3 id="set-myvar-intro">
-<title>Introduction</title>
-
-<para>
-Along with the variables listed in the
-<link linkend="variables">Configuration variables</link> section, mutt
-supports user-defined variables with names starting
-with <literal>my_</literal> as in, for
-example, <literal>my_cfgdir</literal>.
-</para>
-
-<para>
-The <literal>set</literal> command either creates a
-custom <literal>my_</literal> variable or changes its
-value if it does exist already. The <literal>unset</literal> and <literal>reset</literal>
-commands remove the variable entirely.
-</para>
-
-<para>
-Since user-defined variables are expanded in the same way that
-environment variables are (except for
-the <link linkend="shell-escape">shell-escape</link> command and
-backtick expansion), this feature can be used to make configuration
-files more readable.
-</para>
-
-</sect3>
-
-<sect3 id="set-myvar-examples">
-<title>Examples</title>
-
-<para>
-The following example defines and uses the variable <literal>my_cfgdir</literal>
-to abbreviate the calls of the <link linkend="source">source</link> command:
-</para>
-
-<example id="ex-myvar1">
-<title>Using user-defined variables for config file readability</title>
-<screen>
-set my_cfgdir = $HOME/mutt/config
-
-source $my_cfgdir/hooks
-source $my_cfgdir/macros
-# more source commands...
-</screen>
-</example>
-
-<para>
-A custom variable can also be used in macros to backup the current value
-of another variable. In the following example, the value of the
-<link linkend="delete">$delete</link> is changed temporarily
-while its original value is saved as <literal>my_delete</literal>.
-After the macro has executed all commands, the original value of <link
-linkend="delete">$delete</link> is restored.
-</para>
-
-<example id="ex-myvar2">
-<title>Using user-defined variables for backing up other config option values</title>
-<screen>
-macro pager ,x '\
-<enter-command>set my_delete=$delete<enter>\
-<enter-command>set delete=yes<enter>\
-...\
-<enter-command>set delete=$my_delete<enter>'
-</screen>
-</example>
-
-<para>
-Since mutt expands such values already when parsing the configuration
-file(s), the value of <literal>$my_delete</literal> in the
-last example would be the value of <literal>$delete</literal> exactly
-as it was at that point during parsing the configuration file. If
-another statement would change the value for <literal>$delete</literal>
-later in the same or another file, it would have no effect on
-<literal>$my_delete</literal>. However, the expansion can
-be deferred to runtime, as shown in the next example, when escaping the
-dollar sign.
-</para>
-
-<example id="ex-myvar3">
-<title>Deferring user-defined variable expansion to runtime</title>
-<screen>
-macro pager <PageDown> "\
-<enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
-<next-page>\
-<enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
-<enter-command> unset my_old_pager_stop<Enter>"
-</screen>
-</example>
-
-<para>
-Note that there is a space
-between <literal><enter-command></literal> and
-the <literal>set</literal> configuration command, preventing mutt from
-recording the macro's commands into its history.
-</para>
-
-</sect3>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="source">
-<title>Reading initialization commands from another file</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>source</command>
-<arg choice="plain">
-<replaceable class="parameter">filename</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command allows the inclusion of initialization commands
-from other files. For example, I place all of my aliases in
-<literal>˜/.mail_aliases</literal> so that I can make my
-<literal>˜/.muttrc</literal> readable and keep my aliases private.
-</para>
-
-<para>
-If the filename begins with a tilde (<quote>˜</quote>), it will be expanded to the
-path of your home directory.
-</para>
-
-<para>
-If the filename ends with a vertical bar (|), then <emphasis>filename</emphasis> is
-considered to be an executable program from which to read input (eg.
-<literal>source ˜/bin/myscript|</literal>).
-</para>
-
-</sect1>
-
-<sect1 id="ifdef">
-
-<title>Configuring features conditionnaly</title>
-
-<para>
-Usage: <literal>ifdef</literal> <emphasis>item</emphasis> <emphasis>command</emphasis>
-</para>
-
-<para>
-This command allows to test if a feature has been compiled in, before
-actually executing the command. Item can be either the name of a
-function, variable, or command. Example:
-</para>
-
-<para>
-<screen>
-ifdef imap_keepalive 'source ~/.mutt/imap_setup'
-</screen>
-</para>
-
-</sect1>
-
-<sect1 id="unhook">
-<title>Removing hooks</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>unhook</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">hook-type</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-This command permits you to flush hooks you have previously defined.
-You can either remove all hooks by giving the <quote>*</quote> character as an
-argument, or you can remove all hooks of a specific type by saying
-something like <literal>unhook send-hook</literal>.
-</para>
-
-</sect1>
-
-<sect1 id="formatstrings">
-<title>Format Strings</title>
-
-<sect2 id="formatstrings-basics">
-<title>Basic usage</title>
-
-<para>
-Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
-<link linkend="index-format">$index_format</link>,
-<link linkend="pager-format">$pager_format</link>,
-<link linkend="status-format">$status_format</link>,
-and other <quote>*_format</quote> variables. These can be very straightforward,
-and it's quite possible you already know how to use them.
-</para>
-
-<para>
-The most basic format string element is a percent symbol followed
-by another character. For example, <literal>%s</literal>
-represents a message's Subject: header in the <link
-linkend="index-format">$index_format</link> variable. The
-<quote>expandos</quote> available are documented with each format variable, but
-there are general modifiers available with all formatting expandos,
-too. Those are our concern here.
-</para>
-
-<para>
-Some of the modifiers are borrowed right out of C (though you might
-know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in <literal>%-12.12s</literal>. As with
-such programming languages, these modifiers allow you to specify the
-minimum and maximum size of the resulting string, as well as its
-justification. If the <quote>-</quote> sign follows the percent, the string will
-be left-justified instead of right-justified. If there's a number
-immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
-will be padded out with spaces. If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
-permitted to exceed that width, no matter its natural size. Each of
-these three elements is optional, so that all these are legal format
-strings:
-<literal>%-12s</literal>
-<literal>%4c</literal>
-<literal>%.15F</literal>
-<literal>%-12.15L</literal>
-</para>
-
-<para>
-Mutt adds some other modifiers to format strings. If you use an equals
-symbol (<literal>=</literal>) as a numeric prefix (like the minus
-above), it will force the string to be centered within its minimum
-space range. For example, <literal>%=14y</literal> will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-<literal>$index_format</literal>. If the expansion
-results in a string less than 14 characters, it will be centered in a
-14-character space. If the X-Label for a message were "test", that
-expansion would look like <quote> test </quote>.
-</para>
-
-<para>
-There are two very little-known modifiers that affect the way that an
-expando is replaced. If there is an underline (<quote>_</quote>) character
-between any format modifiers (as above) and the expando letter, it will
-expands in all lower case. And if you use a colon (<quote>:</quote>), it will
-replace all decimal points with underlines.
-</para>
-
-</sect2>
-
-<sect2 id="formatstrings-filters">
-<title>Filters</title>
-
-<para>
-Any format string ending in a vertical bar (<quote>|</quote>) will be
-expanded and piped through the first word in the string, using spaces
-as separator. The string returned will be used for display.
-If the returned string ends in %, it will be passed through
-the formatter a second time. This allows the filter to generate a
-replacement format string including % expandos.
-</para>
-
-<para>
-All % expandos in a format string are expanded before the script
-is called so that:
-</para>
-
-<example id="ex-fmtpipe">
-<title>Using external filters in format strings</title>
-<screen>
-set status_format="script.sh '%r %f (%L)'|"
-</screen>
-</example>
-
-<para>
-will make mutt expand <literal>%r</literal>,
-<literal>%f</literal> and <literal>%L</literal>
-before calling the script. The example also shows that arguments can be
-quoted: the script will receive the expanded string between the single quotes
-as the only argument.
-</para>
-
-<para>
-A practical example is the <literal>mutt_xtitle</literal>
-script installed in the <literal>samples</literal>
-subdirectory of the mutt documentation: it can be used as filter for
-<literal>$status_format</literal> to set the current
-terminal's title, if supported.
-</para>
-
-</sect2>
-
-</sect1>
-
-</chapter>
-
-<chapter id="advancedusage">
-<title>Advanced Usage</title>
-
-<sect1 id="regexp">
-<title>Regular Expressions</title>
-
-<para>
-All string patterns in Mutt including those in more complex
-<link linkend="patterns">patterns</link> must be specified
-using regular expressions (regexp) in the <quote>POSIX extended</quote> 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.
-</para>
-
-<para>
-The search is case sensitive if the pattern contains at least one upper
-case letter, and case insensitive otherwise.
-</para>
-
-<note>
-<para>
-Note that <quote>\</quote>
-must be quoted if used for a regular expression in an initialization
-command: <quote>\\</quote>.
-</para>
-</note>
-
-<para>
-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.
-</para>
-
-<note>
-<para>
-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 <xref linkend="muttrc-syntax"/>
-for more information on " and ' delimiter processing. To match a
-literal " or ' you must preface it with \ (backslash).
-</para>
-</note>
-
-<para>
-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.
-</para>
-
-<para>
-The period <quote>.</quote> matches any single character. The caret <quote>ˆ</quote> and
-the dollar sign <quote>$</quote> are metacharacters that respectively match
-the empty string at the beginning and end of a line.
-</para>
-
-<para>
-A list of characters enclosed by <quote>[</quote> and <quote>]</quote> matches any
-single character in that list; if the first character of the list
-is a caret <quote>ˆ</quote> then it matches any character <emphasis role="bold">not</emphasis> in the
-list. For example, the regular expression <emphasis role="bold">[0123456789]</emphasis>
-matches any single digit. A range of ASCII characters may be specified
-by giving the first and last characters, separated by a hyphen
-<quote>-</quote>. Most metacharacters lose their special meaning inside
-lists. To include a literal <quote>]</quote> place it first in the list.
-Similarly, to include a literal <quote>ˆ</quote> place it anywhere but first.
-Finally, to include a literal hyphen <quote>-</quote> place it last.
-</para>
-
-<para>
-Certain named classes of characters are predefined. Character classes
-consist of <quote>[:</quote>, a keyword denoting the class, and <quote>:]</quote>.
-The following classes are defined by the POSIX standard in
-<xref linkend="posix-regex-char-classes"/>
-</para>
-
-<table id="posix-regex-char-classes">
-<title>POSIX regular expression character classes</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Character class</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>[:alnum:]</entry><entry>Alphanumeric characters</entry></row>
-<row><entry>[:alpha:]</entry><entry>Alphabetic characters</entry></row>
-<row><entry>[:blank:]</entry><entry>Space or tab characters</entry></row>
-<row><entry>[:cntrl:]</entry><entry>Control characters</entry></row>
-<row><entry>[:digit:]</entry><entry>Numeric characters</entry></row>
-<row><entry>[:graph:]</entry><entry>Characters that are both printable and visible. (A space is printable, but not visible, while an <quote>a</quote> is both)</entry></row>
-<row><entry>[:lower:]</entry><entry>Lower-case alphabetic characters</entry></row>
-<row><entry>[:print:]</entry><entry>Printable characters (characters that are not control characters)</entry></row>
-<row><entry>[:punct:]</entry><entry>Punctuation characters (characters that are not letter, digits, control characters, or space characters)</entry></row>
-<row><entry>[:space:]</entry><entry>Space characters (such as space, tab and formfeed, to name a few)</entry></row>
-<row><entry>[:upper:]</entry><entry>Upper-case alphabetic characters</entry></row>
-<row><entry>[:xdigit:]</entry><entry>Characters that are hexadecimal digits</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-A character class is only valid in a regular expression inside the
-brackets of a character list.
-</para>
-
-<note>
-<para>
-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, <emphasis role="bold">[[:digit:]]</emphasis> is equivalent to
-<emphasis role="bold">[0-9]</emphasis>.
-</para>
-</note>
-
-<para>
-Two additional special sequences can appear in character lists. These
-apply to non-ASCII character sets, which can have single symbols (called
-collating elements) that are represented with more than one character,
-as well as several characters that are equivalent for collating or
-sorting purposes:
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>Collating Symbols</term>
-<listitem>
-<para>
-A collating symbol is a multi-character collating element enclosed in
-<quote>[.</quote> and <quote>.]</quote>. For example, if <quote>ch</quote> is a collating
-element, then <emphasis role="bold">[[.ch.]]</emphasis> is a regexp that matches
-this collating element, while <emphasis role="bold">[ch]</emphasis> is a regexp that
-matches either <quote>c</quote> or <quote>h</quote>.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>Equivalence Classes</term>
-<listitem>
-<para>
-An equivalence class is a locale-specific name for a list of
-characters that are equivalent. The name is enclosed in <quote>[=</quote>
-and <quote>=]</quote>. For example, the name <quote>e</quote> might be used to
-represent all of <quote>è</quote> <quote>é</quote> and <quote>e</quote>. In this case,
-<emphasis role="bold">[[=e=]]</emphasis> is a regexp that matches any of
-<quote>è</quote>, <quote>é</quote> and <quote>e</quote>.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-<para>
-A regular expression matching a single character may be followed by one
-of several repetition operators described in <xref linkend="regex-repeat"/>.
-</para>
-
-<table id="regex-repeat">
-<title>Regular expression repetition operators</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Operator</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>?</entry><entry>The preceding item is optional and matched at most once</entry></row>
-<row><entry>*</entry><entry>The preceding item will be matched zero or more times</entry></row>
-<row><entry>+</entry><entry>The preceding item will be matched one or more times</entry></row>
-<row><entry>{n}</entry><entry>The preceding item is matched exactly <emphasis>n</emphasis> times</entry></row>
-<row><entry>{n,}</entry><entry>The preceding item is matched <emphasis>n</emphasis> or more times</entry></row>
-<row><entry>{,m}</entry><entry>The preceding item is matched at most <emphasis>m</emphasis> times</entry></row>
-<row><entry>{n,m}</entry><entry>The preceding item is matched at least <emphasis>n</emphasis> times, but no more than <emphasis>m</emphasis> times</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Two regular expressions may be concatenated; the resulting regular
-expression matches any string formed by concatenating two substrings
-that respectively match the concatenated subexpressions.
-</para>
-
-<para>
-Two regular expressions may be joined by the infix operator <quote>|</quote>;
-the resulting regular expression matches any string matching either
-subexpression.
-</para>
-
-<para>
-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.
-</para>
-
-<note>
-<para>
-If you compile Mutt with the GNU <emphasis>rx</emphasis> package, the
-following operators may also be used in regular expressions as described in <xref linkend="regex-gnu-ext"/>.
-</para>
-</note>
-
-<table id="regex-gnu-ext">
-<title>GNU regular expression extensions</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Expression</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>\\y</entry><entry>Matches the empty string at either the beginning or the end of a word</entry></row>
-<row><entry>\\B</entry><entry>Matches the empty string within a word</entry></row>
-<row><entry>\\<</entry><entry>Matches the empty string at the beginning of a word</entry></row>
-<row><entry>\\></entry><entry>Matches the empty string at the end of a word</entry></row>
-<row><entry>\\w</entry><entry>Matches any word-constituent character (letter, digit, or underscore)</entry></row>
-<row><entry>\\W</entry><entry>Matches any character that is not word-constituent</entry></row>
-<row><entry>\\`</entry><entry>Matches the empty string at the beginning of a buffer (string)</entry></row>
-<row><entry>\\'</entry><entry>Matches the empty string at the end of a buffer</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-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.
-</para>
-
-</sect1>
-
-<sect1 id="patterns">
-<title>Patterns: Searching, Limiting and Tagging</title>
-
-<para>
-Many of Mutt's commands allow you to specify a pattern to match
-(<literal>limit</literal>, <literal>tag-pattern</literal>,
-<literal>delete-pattern</literal>, etc.). <xref linkend="tab-patterns"/>
-shows several ways to select messages.
-</para>
-
-<table id="tab-patterns">
-<title>Pattern modifiers</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Pattern modifier</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>~A</entry><entry>all messages</entry></row>
-<row><entry>~b <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the message body</entry></row>
-<row><entry>=b <emphasis>STRING</emphasis></entry><entry>messages which contain <emphasis>STRING</emphasis> in the message body. If IMAP is enabled, searches for <emphasis>STRING</emphasis> on the server, rather than downloading each message and searching it locally.</entry></row>
-<row><entry>~B <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the whole message</entry></row>
-<row><entry>~c <emphasis>EXPR</emphasis></entry><entry>messages carbon-copied to <emphasis>EXPR</emphasis></entry></row>
-<row><entry>%c <emphasis>GROUP</emphasis></entry><entry>messages carbon-copied to any member of <emphasis>GROUP</emphasis></entry></row>
-<row><entry>~C <emphasis>EXPR</emphasis></entry><entry>messages either to: or cc: <emphasis>EXPR</emphasis></entry></row>
-<row><entry>%C <emphasis>GROUP</emphasis></entry><entry>messages either to: or cc: to any member of <emphasis>GROUP</emphasis></entry></row>
-<row><entry>~d [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with <quote>date-sent</quote> in a Date range</entry></row>
-<row><entry>~D</entry><entry>deleted messages</entry></row>
-<row><entry>~e <emphasis>EXPR</emphasis></entry><entry>messages which contains <emphasis>EXPR</emphasis> in the <quote>Sender</quote> field</entry></row>
-<row><entry>%e <emphasis>GROUP</emphasis></entry><entry>messages which contain a member of <emphasis>GROUP</emphasis> in the <quote>Sender</quote> field</entry></row>
-<row><entry>~E</entry><entry>expired messages</entry></row>
-<row><entry>~F</entry><entry>flagged messages</entry></row>
-<row><entry>~f <emphasis>EXPR</emphasis></entry><entry>messages originating from <emphasis>EXPR</emphasis></entry></row>
-<row><entry>%f <emphasis>GROUP</emphasis></entry><entry>messages originating from any member of <emphasis>GROUP</emphasis></entry></row>
-<row><entry>~g</entry><entry>cryptographically signed messages</entry></row>
-<row><entry>~G</entry><entry>cryptographically encrypted messages</entry></row>
-<row><entry>~h <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the message header</entry></row>
-<row><entry>~H <emphasis>EXPR</emphasis></entry><entry>messages with a spam attribute matching <emphasis>EXPR</emphasis></entry></row>
-<row><entry>~i <emphasis>EXPR</emphasis></entry><entry>messages which match <emphasis>EXPR</emphasis> in the <quote>Message-ID</quote> field</entry></row>
-<row><entry>~k</entry><entry>messages which contain PGP key material</entry></row>
-<row><entry>~L <emphasis>EXPR</emphasis></entry><entry>messages either originated or received by <emphasis>EXPR</emphasis></entry></row>
-<row><entry>%L <emphasis>GROUP</emphasis></entry><entry>message either originated or received by any member of <emphasis>GROUP</emphasis></entry></row>
-<row><entry>~l</entry><entry>messages addressed to a known mailing list</entry></row>
-<row><entry>~m [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *)</entry></row>
-<row><entry>~n [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with a score in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *)</entry></row>
-<row><entry>~N</entry><entry>new messages</entry></row>
-<row><entry>~O</entry><entry>old messages</entry></row>
-<row><entry>~p</entry><entry>messages addressed to you (consults alternates)</entry></row>
-<row><entry>~P</entry><entry>messages from you (consults alternates)</entry></row>
-<row><entry>~Q</entry><entry>messages which have been replied to</entry></row>
-<row><entry>~r [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with <quote>date-received</quote> in a Date range</entry></row>
-<row><entry>~R</entry><entry>read messages</entry></row>
-<row><entry>~s <emphasis>EXPR</emphasis></entry><entry>messages having <emphasis>EXPR</emphasis> in the <quote>Subject</quote> field.</entry></row>
-<row><entry>~S</entry><entry>superseded messages</entry></row>
-<row><entry>~t <emphasis>EXPR</emphasis></entry><entry>messages addressed to <emphasis>EXPR</emphasis></entry></row>
-<row><entry>~T</entry><entry>tagged messages</entry></row>
-<row><entry>~u</entry><entry>messages addressed to a subscribed mailing list</entry></row>
-<row><entry>~U</entry><entry>unread messages</entry></row>
-<row><entry>~v</entry><entry>messages part of a collapsed thread.</entry></row>
-<row><entry>~V</entry><entry>cryptographically verified messages</entry></row>
-<row><entry>~x <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the <quote>References</quote> field</entry></row>
-<row><entry>~X [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> attachments *)</entry></row>
-<row><entry>~y <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the <quote>X-Label</quote> field</entry></row>
-<row><entry>~z [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with a size in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *)</entry></row>
-<row><entry>~=</entry><entry>duplicated messages (see <link linkend="duplicate-threads">$duplicate_threads</link>)</entry></row>
-<row><entry>~$</entry><entry>unreferenced messages (requires threaded view)</entry></row>
-<row><entry>~(<emphasis>PATTERN</emphasis>)</entry><entry>messages in threads
-containing messages matching <emphasis>PATTERN</emphasis>, e.g. all
-threads containing messages from you: ~(~P)</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Where <emphasis>EXPR</emphasis> is a
-<link linkend="regexp">regular expression</link>. Special attention has to be
-made when using regular expressions inside of patterns. Specifically,
-Mutt's parser for these patterns will strip one level of backslash (<quote>\</quote>),
-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 (<quote>\\</quote>). You can force mutt to treat <emphasis>EXPR</emphasis> as a simple string
-instead of a regular expression by using = instead of ˜ in the
-pattern name. For example, <literal>=b *.*</literal> will find all messages that contain
-the literal string <quote>*.*</quote>. Simple string matches are less powerful than
-regular expressions but can be considerably faster. This is especially
-true for IMAP folders, because string matches can be performed on the
-server instead of by fetching every message. IMAP treats <literal>=h</literal> specially:
-it must be of the form "header: substring" and will not partially
-match header names. The substring part may be omitted if you simply
-wish to find messages containing a particular header without regard to
-its value.
-</para>
-
-<para>
-*) The forms <quote><[<emphasis>MAX</emphasis>]</quote>, <quote>>[<emphasis>MIN</emphasis>]</quote>,
-<quote>[<emphasis>MIN</emphasis>]-</quote> and <quote>-[<emphasis>MAX</emphasis>]</quote>
-are allowed, too.
-</para>
-
-<sect2 id="patterns-modifier">
-<title>Pattern Modifier</title>
-
-<note>
-<para>
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
-match if there is at least one match in the whole list. If you want to
-make sure that all elements of that list match, you need to prefix your
-pattern with <quote>ˆ</quote>.
-This example matches all mails which only has recipients from Germany.
-</para>
-</note>
-
-<screen>
-^~C \.de$
-</screen>
-
-</sect2>
-
-<sect2 id="simple-patterns">
-<title>Simple Patterns</title>
-
-<para>
-Mutt supports two versions of so called <quote>simple searches</quote> which are
-issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
-one of these characters: <quote>˜</quote>, <quote>=</quote> or <quote>%</quote>). If the query is
-supposed to contain one of these special characters, they must be escaped
-by prepending a backslash (<quote>\</quote>).
-</para>
-
-<para>
-The first type is by checking whether the query string equals
-a keyword case-insensitively from <xref linkend="tab-simplesearch-keywords"/>:
-If that is the case, Mutt will use the shown pattern modifier instead.
-If a keyword would conflict with your search keyword, you need to turn
-it into a regular expression to avoid matching the keyword table. For
-example, if you want to find all messages matching <quote>flag</quote>
-(using <link linkend="simple-search">$simple_search</link>)
-but don't want to match flagged messages, simply search for
-<quote><literal>[f]lag</literal></quote>.
-</para>
-
-<table id="tab-simplesearch-keywords">
-<title>Simple search keywords</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Keyword</entry><entry>Pattern modifier</entry></row>
-</thead>
-<tbody>
-<row><entry>all</entry><entry>~A</entry></row>
-<row><entry>.</entry><entry>~A</entry></row>
-<row><entry>ˆ</entry><entry>~A</entry></row>
-<row><entry>del</entry><entry>~D</entry></row>
-<row><entry>flag</entry><entry>~F</entry></row>
-<row><entry>new</entry><entry>~N</entry></row>
-<row><entry>old</entry><entry>~O</entry></row>
-<row><entry>repl</entry><entry>~Q</entry></row>
-<row><entry>read</entry><entry>~R</entry></row>
-<row><entry>tag</entry><entry>~T</entry></row>
-<row><entry>unread</entry><entry>~U</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-The second type of simple search is to build a complex search
-pattern using <link linkend="simple-search">$simple_search</link>
-as a template. Mutt will insert your query properly quoted and search
-for the composed complex query.
-</para>
-
-</sect2>
-
-<sect2 id="complex-patterns">
-<title>Complex Patterns</title>
-
-<para>
-Logical AND is performed by specifying more than one criterion. For
-example:
-</para>
-
-<screen>
-~t mutt ~f elkins
-</screen>
-
-<para>
-would select messages which contain the word <quote>mutt</quote> in the list of
-recipients <emphasis role="bold">and</emphasis> that have the word <quote>elkins</quote> in the <quote>From</quote> header
-field.
-</para>
-
-<para>
-Mutt also recognizes the following operators to create more complex search
-patterns:
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-! -- logical NOT operator
-</para>
-</listitem>
-<listitem>
-
-<para>
-| -- logical OR operator
-</para>
-</listitem>
-<listitem>
-
-<para>
-() -- logical grouping operator
-</para>
-</listitem>
-
-</itemizedlist>
-
-<para>
-Here is an example illustrating a complex search pattern. This pattern will
-select all messages which do not contain <quote>mutt</quote> in the <quote>To</quote> or <quote>Cc</quote>
-field and which are from <quote>elkins</quote>.
-</para>
-
-<example id="ex-pattern-bool">
-<title>Using boolean operators in patterns</title>
-<screen>
-!(~t mutt|~c mutt) ~f elkins
-</screen>
-</example>
-
-<para>
-Here is an example using white space in the regular expression (note
-the ' and " delimiters). For this to match, the mail's subject must
-match the <quote>ˆJunk +From +Me$</quote> and it must be from either <quote>Jim +Somebody</quote>
-or <quote>Ed +SomeoneElse</quote>:
-</para>
-
-<screen>
- '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
-</screen>
-
-<note>
-<para>
-If a regular expression contains parenthesis, or a vertical bar
-("|"), you <emphasis role="bold">must</emphasis> enclose the expression in double or single quotes since
-those characters are also used to separate different parts of Mutt's
-pattern language. For example: <literal>~f "me@(mutt\.org|cs\.hmc\.edu)"</literal>
-</para>
-</note>
-
-<para>
-Without the quotes, the parenthesis wouldn't end.
-This would be separated to two OR'd patterns: <emphasis>˜f me@(mutt\.org</emphasis>
-and <emphasis>cs\.hmc\.edu)</emphasis>. They are never what you want.
-</para>
-
-</sect2>
-
-<sect2 id="date-patterns">
-<title>Searching by Date</title>
-
-<para>
-Mutt supports two types of dates, <emphasis>absolute</emphasis> and <emphasis>relative</emphasis>.
-</para>
-
-<para>
-<emphasis role="bold">Absolute</emphasis>. Dates <emphasis role="bold">must</emphasis> be in DD/MM/YY format (month and year are
-optional, defaulting to the current month and year). An example of a valid
-range of dates is:
-</para>
-
-<screen>
-Limit to messages matching: ~d 20/1/95-31/10
-</screen>
-
-<para>
-If you omit the minimum (first) date, and just specify <quote>-DD/MM/YY</quote>, all
-messages <emphasis>before</emphasis> the given date will be selected. If you omit the maximum
-(second) date, and specify <quote>DD/MM/YY-</quote>, all messages <emphasis>after</emphasis> the given
-date will be selected. If you specify a single date with no dash (<quote>-</quote>),
-only messages sent on the given date will be selected.
-</para>
-
-<para>
-<emphasis role="bold">Error Margins</emphasis>. You can add error margins to absolute dates.
-An error margin is a sign (+ or -), followed by a digit, followed by
-one of the units in <xref linkend="tab-date-units"/>. As a special case, you can replace the
-sign by a <quote>*</quote> character, which is equivalent to giving identical plus and minus error margins.
-</para>
-
-<table id="tab-date-units">
-<title>Date units</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Unit</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>y</entry><entry>Years</entry></row>
-<row><entry>m</entry><entry>Months</entry></row>
-<row><entry>w</entry><entry>Weeks</entry></row>
-<row><entry>d</entry><entry>Days</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Example: To select any messages two weeks around January 15, 2001,
-you'd use the following pattern:
-</para>
-
-<screen>
-Limit to messages matching: ~d 15/1/2001*2w
-</screen>
-
-<para>
-<emphasis role="bold">Relative</emphasis>. This type of date is relative to the current date, and may
-be specified as:
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-><emphasis>offset</emphasis> (messages older than <emphasis>offset</emphasis> units)
-</para>
-</listitem>
-<listitem>
-
-<para>
-<<emphasis>offset</emphasis> (messages newer than <emphasis>offset</emphasis> units)
-</para>
-</listitem>
-<listitem>
-
-<para>
-=<emphasis>offset</emphasis> (messages exactly <emphasis>offset</emphasis> units old)
-</para>
-</listitem>
-
-</itemizedlist>
-
-<para>
-<emphasis>offset</emphasis> is specified as a positive number with one of the units from <xref linkend="tab-date-units"/>.
-</para>
-
-<para>
-Example: to select messages less than 1 month old, you would use
-</para>
-
-<screen>
-Limit to messages matching: ~d <1m
-</screen>
-
-<note>
-<para>
-All dates used when searching are relative to the
-<emphasis role="bold">local</emphasis> time zone, so unless you change the setting of your <link linkend="index-format">$index_format</link> to include a
-<literal>%[...]</literal> format, these are <emphasis role="bold">not</emphasis> the dates shown
-in the main index.
-</para>
-</note>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="tags">
-<title>Using Tags</title>
-
-<para>
-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 <literal><tag-pattern></literal> function, which is bound to
-<quote>shift-T</quote> by default. Or you can select individual messages by
-hand using the <literal><tag-message></literal> function, which is bound to <quote>t</quote> by
-default. See <link linkend="patterns">patterns</link> for Mutt's pattern
-matching syntax.
-</para>
-
-<para>
-Once you have tagged the desired messages, you can use the
-<quote>tag-prefix</quote> operator, which is the <quote>;</quote> (semicolon) key by default.
-When the <quote>tag-prefix</quote> operator is used, the <emphasis role="bold">next</emphasis> operation will
-be applied to all tagged messages if that operation can be used in that
-manner. If the <link linkend="auto-tag">$auto_tag</link>
-variable is set, the next operation applies to the tagged messages
-automatically, without requiring the <quote>tag-prefix</quote>.
-</para>
-
-<para>
-In <link linkend="macro">macros</link> or <link linkend="push">push</link> commands,
-you can use the <quote>tag-prefix-cond</quote> operator. If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the <quote>end-cond</quote>
-operator; after this operator the rest of the macro will be executed as
-normal.
-</para>
-
-</sect1>
-
-<sect1 id="hooks">
-<title>Using Hooks</title>
-
-<para>
-A <emphasis>hook</emphasis> is a concept found in many other programs 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 world, a <emphasis>hook</emphasis>
-consists of a <link linkend="regexp">regular expression</link> or
-<link linkend="patterns">pattern</link> along with a
-configuration option/command. See
-
-<itemizedlist>
-<listitem>
-
-<para>
-<link linkend="folder-hook">folder-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="send-hook">send-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="message-hook">message-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="save-hook">save-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="mbox-hook">mbox-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="fcc-hook">fcc-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="fcc-save-hook">fcc-save-hook</link>
-</para>
-</listitem>
-
-</itemizedlist>
-
-for specific details on each type of <emphasis>hook</emphasis> available.
-</para>
-
-<note>
-<para>
-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:
-</para>
-</note>
-
-<example id="ex-send-hook-my-hdr">
-<title>Combining <literal>send-hook</literal> and <literal>my_hdr</literal></title>
-<screen>
-send-hook . 'unmy_hdr From:'
-send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-</screen>
-</example>
-
-<sect2 id="pattern-hook" xreflabel="Message Matching in Hooks">
-<title>Message Matching in Hooks</title>
-
-<para>
-Hooks that act upon messages (<literal>message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook</literal>) are evaluated in a
-slightly different manner. For the other
-types of hooks, a <link linkend="regexp">regular expression</link> 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.
-</para>
-
-<para>
-Mutt allows the use of the <link linkend="patterns">search pattern</link>
-language for matching messages in hook commands. This works in
-exactly the same way as it would when <emphasis>limiting</emphasis> or
-<emphasis>searching</emphasis> 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.).
-</para>
-
-<para>
-For example, if you wanted to set your return address based upon sending
-mail to a specific address, you could do something like:
-</para>
-
-<screen>
-send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
-</screen>
-
-<para>
-which would execute the given command when sending mail to
-<emphasis>me@cs.hmc.edu</emphasis>.
-</para>
-
-<para>
-However, it is not required that you write the pattern to match using the
-full searching language. You can still specify a simple <emphasis>regular
-expression</emphasis> like the other hooks, in which case Mutt will translate your
-pattern into the full language, using the translation specified by the
-<link linkend="default-hook">$default_hook</link> variable. The
-pattern is translated at the time the hook is declared, so the value of
-<link linkend="default-hook">$default_hook</link> that is in effect
-at that time will be used.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="query">
-<title>External Address Queries</title>
-
-<para>
-Mutt 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 <link linkend="query-command">$query_command</link> variable, you specify the wrapper
-command to use. For example:
-</para>
-
-<screen>
-set query_command = "mutt_ldap_query.pl '%s'"
-</screen>
-
-<para>
-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 then
-some other optional information. On error, or if there are no matching
-addresses, return a non-zero exit code and a one line error message.
-</para>
-
-<para>
-An example multiple response output:
-</para>
-
-<screen>
-Searching database ... 20 entries ... 3 matching:
-me@cs.hmc.edu Michael Elkins mutt dude
-blong@fiction.net Brandon Long mutt and more
-roessler@does-not-exist.org Thomas Roessler mutt pgp
-</screen>
-
-<para>
-There are two mechanisms for accessing the query function of mutt. One
-is to do a query from the index menu using the <literal><query></literal> 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 addresses
-to mail, start a new query, or have a new query appended to the current
-responses.
-</para>
-
-<para>
-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 <literal><complete-query></literal> 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 query
-menu. At the query menu, you can select one or more addresses to be
-added to the prompt.
-</para>
-
-</sect1>
-
-<sect1 id="mailbox-formats">
-<title>Mailbox Formats</title>
-
-<para>
-Mutt 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 new
-mailboxes, Mutt uses the default specified with the <link linkend="mbox-type">$mbox_type</link> variable.
-</para>
-
-<para>
-<emphasis role="bold">mbox</emphasis>. 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:
-</para>
-
-<screen>
-From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-</screen>
-
-<para>
-to denote the start of a new message (this is often referred to as the
-<quote>From_</quote> line).
-</para>
-
-<para>
-<emphasis role="bold">MMDF</emphasis>. This is a variant of the <emphasis>mbox</emphasis> format. Each message is
-surrounded by lines containing <quote>ˆAˆAˆAˆA</quote> (four control-A's).
-</para>
-
-<para>
-<emphasis role="bold">MH</emphasis>. A radical departure from <emphasis>mbox</emphasis> and <emphasis>MMDF</emphasis>, 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 displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
-detects this type of mailbox by looking for either <literal>.mh_sequences</literal>
-or <literal>.xmhcache</literal> (needed to distinguish normal directories from MH
-mailboxes).
-</para>
-
-<para>
-<emphasis role="bold">Maildir</emphasis>. The newest of the mailbox formats, used by the Qmail MTA (a
-replacement for sendmail). Similar to <emphasis>MH</emphasis>, except that it adds three
-subdirectories of the mailbox: <emphasis>tmp</emphasis>, <emphasis>new</emphasis> and <emphasis>cur</emphasis>. Filenames
-for the messages are chosen in such a way they are unique, even when two
-programs are writing the mailbox over NFS, which means that no file locking
-is needed.
-</para>
-
-</sect1>
-
-<sect1 id="shortcuts">
-<title>Mailbox Shortcuts</title>
-
-<para>
-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.
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-! -- refers to your <link linkend="spoolfile">$spoolfile</link> (incoming) mailbox
-</para>
-</listitem>
-<listitem>
-
-<para>
-> -- refers to your <link linkend="mbox">$mbox</link> file
-</para>
-</listitem>
-<listitem>
-
-<para>
-< -- refers to your <link linkend="record">$record</link> file
-</para>
-</listitem>
-<listitem>
-
-<para>
-ˆ -- refers to the current mailbox
-</para>
-</listitem>
-<listitem>
-
-<para>
-- or !! -- refers to the file you've last visited
-</para>
-</listitem>
-<listitem>
-
-<para>
-˜ -- refers to your home directory
-</para>
-</listitem>
-<listitem>
-
-<para>
-= or + -- refers to your <link linkend="folder">$folder</link> directory
-</para>
-</listitem>
-<listitem>
-
-<para>
-@<emphasis>alias</emphasis> -- refers to the <link linkend="save-hook">default save folder</link> as determined by the address of the alias
-</para>
-</listitem>
-
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="using-lists">
-<title>Handling Mailing Lists</title>
-
-<para>
-Mutt 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 <link linkend="lists">lists and subscribe</link> commands in your muttrc.
-</para>
-
-<para>
-Now that Mutt 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 <emphasis>index</emphasis> menu display. This is useful to distinguish between
-personal and list mail in the same mailbox. In the <link linkend="index-format">$index_format</link> variable, the escape <quote>%L</quote>
-will return the string <quote>To <list></quote> when <quote>list</quote> appears in the
-<quote>To</quote> field, and <quote>Cc <list></quote> when it appears in the <quote>Cc</quote>
-field (otherwise it returns the name of the author).
-</para>
-
-<para>
-Often times the <quote>To</quote> and <quote>Cc</quote> fields in mailing list messages
-tend to get quite large. Most people do not bother to remove the
-author of the message they reply to from the list, resulting in
-two or more copies being sent to that person. The <literal><list-reply></literal>
-function, which by default is bound to <quote>L</quote> in the <emphasis>index</emphasis> menu
-and <emphasis>pager</emphasis>, helps reduce the clutter by only replying to the
-known mailing list addresses instead of all recipients (except as
-specified by <literal>Mail-Followup-To</literal>, see below).
-</para>
-
-<para>
-Mutt also supports the <literal>Mail-Followup-To</literal> header. When you send
-a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the <link linkend="followup-to">$followup_to</link> 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 <quote>followups</quote>) 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.
-</para>
-
-<para>
-Conversely, when group-replying or list-replying to a message which
-has a <literal>Mail-Followup-To</literal> header, mutt will respect this header if
-the <link linkend="honor-followup-to">$honor_followup_to</link> 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 <literal>Mail-Followup-To</literal>.
-</para>
-
-<note>
-<para>
-When header editing is enabled, you can create a
-<literal>Mail-Followup-To</literal> header manually. Mutt will only auto-generate
-this header if it doesn't exist when you send the message.
-</para>
-</note>
-
-<para>
-The other method some mailing list admins use is to generate a
-<quote>Reply-To</quote> 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 <quote>Reply-To</quote>
-field. Mutt uses the <link linkend="reply-to">$reply_to</link>
-variable to help decide which address to use. If set to <emphasis>ask-yes</emphasis> or
-<emphasis>ask-no</emphasis>, you will be
-prompted as to whether or not you would like to use the address given in
-the <quote>Reply-To</quote> field, or reply directly to the address given in the
-<quote>From</quote> field. When set to <emphasis>yes</emphasis>, the <quote>Reply-To</quote> field will be used when
-present.
-</para>
-
-<para>
-The <quote>X-Label:</quote> header field can be used to further identify mailing
-lists or list subject matter (or just to annotate messages
-individually). The <link linkend="index-format">$index_format</link> variable's <quote>%y</quote> and
-<quote>%Y</quote> escapes can be used to expand <quote>X-Label:</quote> fields in the
-index, and Mutt's pattern-matcher can match regular expressions to
-<quote>X-Label:</quote> fields with the <quote>˜y</quote> selector. <quote>X-Label:</quote> is not a
-standard message header field, but it can easily be inserted by procmail
-and other mail filtering agents.
-</para>
-
-<para>
-Lastly, Mutt has the ability to <link linkend="sort">sort</link> the mailbox into
-<link linkend="threads">threads</link>. 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 dealing
-with large volume mailing lists easier because you can easily delete
-uninteresting threads and quickly find topics of value.
-</para>
-
-</sect1>
-
-<sect1 id="handling-folders">
-<title>Handling multiple folders</title>
-
-<para>
-Mutt supports setups with multiple folders, allowing all of them to
-be monitored for new mail (see <xref linkend="mailboxes"/> for details).
-</para>
-
-<para>
-When in the index menu and being idle (also see
-<link linkend="timeout">$timeout</link>), Mutt periodically checks
-for new mail in all folders which have been configured via the
-<literal>mailboxes</literal> command. The interval depends on the folder
-type: for local/IMAP folders it consults
-<link linkend="mail-check">$mail_check</link> and
-<link linkend="pop-checkinterval">$pop_checkinterval</link>
-for POP folders.
-</para>
-
-<para>
-Outside the index menu the directory browser supports checking
-for new mail using the <literal><check-new></literal> function which is
-unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the <literal>mailboxes</literal> command,
-and indicate which contain new messages. Mutt will automatically enter this
-mode when invoked from the command line with the <literal>-y</literal> option.
-</para>
-
-<para>
-For the pager, index and directory browser menus, Mutt contains the
-<literal><buffy-list></literal> function (bound to <quote>.</quote> by default)
-which will print a list of folders with new mail in the command line at
-the bottom of the screen.
-</para>
-
-<para>
-For the index, by default Mutt displays the number of mailboxes with new
-mail in the status bar, please refer to the
-<link linkend="index-format">$index_format</link>
-variable for details.
-</para>
-
-<para>
-When changing folders, Mutt fills the prompt with the first folder from
-the mailboxes list containing new mail (if any), pressing
-<emphasis>space</emphasis> will cycle through folders with new mail.
-</para>
-
-</sect1>
-
-<sect1 id="editing-threads">
-<title>Editing threads</title>
-
-<para>
-Mutt 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.
-</para>
-
-<sect2 id="link-threads">
-<title>Linking threads</title>
-
-<para>
-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 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 <literal><link-threads></literal> function (bound to & by default). The
-reply will then be connected to this "parent" message.
-</para>
-
-<para>
-You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
-</para>
-
-</sect2>
-
-<sect2 id="break-threads">
-<title>Breaking threads</title>
-
-<para>
-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 <literal><break-thread></literal> function (bound
-by default to #), which will turn the subthread starting from the
-current message into a whole different thread.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="dsn">
-<title>Delivery Status Notification (DSN) Support</title>
-
-<para>
-RFC1894 defines a set of MIME content types for relaying information
-about the status of electronic mail messages. These can be thought of as
-<quote>return receipts.</quote>
-</para>
-
-<para>
-To support DSN, there are two variables. <link linkend="dsn-notify">$dsn_notify</link> is used to request receipts for
-different results (such as failed message, message delivered, etc.).
-<link linkend="dsn-return">$dsn_return</link> requests how much
-of your message should be returned with the receipt (headers or full
-message).
-</para>
-
-<para>
-When using <link linkend="sendmail">$sendmail</link> for mail
-delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA
-supporting DSN command line options compatible to Sendmail: The -N and -R
-options can be used by the mail client to make requests as to what type of
-status messages should be returned. Please consider your MTA documentation
-whether DSN is supported.
-</para>
-
-<para>
-For SMTP delivery using <link
- linkend="smtp-url">$smtp_url</link>, it depends on the
-capabilities announced by the server whether mutt will attempt to
-request DSN or not.
-</para>
-
-</sect1>
-
-<sect1 id="urlview">
-<title>Start a WWW Browser on URLs</title>
-
-<para>
-If a message contains URLs, 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
-<ulink url="ftp://ftp.mutt.org/mutt/contrib/">ftp://ftp.mutt.org/mutt/contrib/</ulink>
-and the configuration commands:
-</para>
-
-<screen>
-macro index \cb |urlview\n
-macro pager \cb |urlview\n
-</screen>
-
-</sect1>
-
-</chapter>
-
-<sect1 id="compressedfolders">
-<title>Compressed folders Support (OPTIONAL)</title>
-
-<para>
-If Mutt was compiled with compressed folders support (by running the
-<emphasis>configure</emphasis> script with the
-<emphasis>--enable-compressed</emphasis> flag), Mutt can open folders
-stored in an arbitrary format, provided that the user has a script to
-convert from/to this format to one of the accepted.
-
-The most common use is to open compressed archived folders e.g. with
-gzip.
-
-In addition, the user can provide a script that gets a folder in an
-accepted format and appends its context to the folder in the
-user-defined format, which may be faster than converting the entire
-folder to the accepted format, appending to it and converting back to
-the user-defined format.
-
-There are three hooks defined (<link
-linkend="open-hook">open-hook</link>, <link
-linkend="close-hook">close-hook</link> and <link
-linkend="append-hook">append-hook</link>) which define commands to
-uncompress and compress a folder and to append messages to an existing
-compressed folder respectively.
-
-For example:
-
-<screen>
-open-hook \\.gz$ "gzip -cd %f > %t"
-close-hook \\.gz$ "gzip -c %t > %f"
-append-hook \\.gz$ "gzip -c %t >> %f"
-</screen>
-
-You do not have to specify all of the commands. If you omit <link
-linkend="append-hook">append-hook</link>, the folder will be open and
-closed again each time you will add to it. If you omit <link
-linkend="close-hook">close-hook</link> (or give empty command) , the
-folder will be open in the mode. If you specify <link
-linkend="append-hook">append-hook</link> though you'll be able to
-append to the folder.
-
-Note that Mutt 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
-<link linkend="save-empty">$save_empty</link>, so that
-the compressed file will be removed if you delete all of the messages.
-</para>
-
-<sect2 id="open-hook">
-<title>Open a compressed mailbox for reading</title>
-
-<para>
-Usage: <literal>open-hook</literal> <emphasis>regexp</emphasis> "<emphasis>command</emphasis>"
-
-The <emphasis>command</emphasis> is the command that can be used for
-opening the folders whose names match <emphasis>regexp</emphasis>.
-
-The <emphasis>command</emphasis> string is the printf-like format
-string, and it should accept two parameters: %f, which is
-replaced with the (compressed) folder name, and %t which is
-replaced with the name of the temporary folder to which to write.
-
-%f and %t can be repeated any number of times in the
-command string, and all of the entries are replaced with the
-appropriate folder name. In addition, %% is replaced by
-%, as in printf, and any other %anything is left as is.
-
-The <emphasis>command</emphasis> should <emphasis
-role="bold">not</emphasis> remove the original compressed file. The
-<emphasis>command</emphasis> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-<screen>
-open-hook \\.gz$ "gzip -cd %f > %t"
-</screen>
-
-If the <emphasis>command</emphasis> is empty, this operation is
-disabled for this file type.
-</para>
-</sect2>
-
-<sect2 id="close-hook">
-<title>Write a compressed mailbox</title>
-
-<para>
-Usage: <literal>close-hook</literal> <emphasis>regexp</emphasis> "<emphasis>command</emphasis>"
-
-This is used to close the folder that was open with the <link
-linkend="open-hook">open-hook</link> command after some changes were
-made to it.
-
-The <emphasis>command</emphasis> string is the command that can be
-used for closing the folders whose names match
-<emphasis>regexp</emphasis>. It has the same format as in the <link
-linkend="open-hook">open-hook</link> command. Temporary folder in this
-case is the folder previously produced by the <link
-linkend="open-hook">open-hook</link> command.
-
-The <emphasis>command</emphasis> should <emphasis
-role="bold">not</emphasis> remove the decompressed file. The
-<emphasis>command</emphasis> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-<screen>
-close-hook \\.gz$ "gzip -c %t > %f"
-</screen>
-
-If the <emphasis>command</emphasis> is empty, this operation is
-disabled for this file type, and the file can only be open in the
-read-only mode.
-
-<link linkend="close-hook">close-hook</link> is not called when you
-exit from the folder if the folder was not changed.
-</para>
-</sect2>
-
-<sect2 id="append-hook">
-<title>Append a message to a compressed mailbox</title>
-
-<para>
-Usage: <literal>append-hook</literal> <emphasis>regexp</emphasis> "<emphasis>command</emphasis>"
-
-This command is used for saving to an existing compressed folder. The
-<emphasis>command</emphasis> is the command that can be used for
-appending to the folders whose names match
-<emphasis>regexp</emphasis>. It has the same format as in the <link
-linkend="open-hook">open-hook</link> command. The temporary folder in
-this case contains the messages that are being appended.
-
-The <emphasis>command</emphasis> should <emphasis
-role="bold">not</emphasis> remove the decompressed file. The
-<emphasis>command</emphasis> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-<screen>
-append-hook \\.gz$ "gzip -c %t >> %f"
-</screen>
-
-When <link linkend="append-hook">append-hook</link> 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 (<link
-linkend="mbox-type">$mbox_type</link>) type is always
-supposed (i.e. this is the format used for the temporary folder).
-
-If the file does not exist when you save to it, <link
-linkend="close-hook">close-hook</link> is called, and not <link
-linkend="append-hook">append-hook</link>. <link
-linkend="append-hook">append-hook</link> is only for appending to
-existing folders.
-
-If the <emphasis>command</emphasis> is empty, this operation is
-disabled for this file type. In this case, the folder will be open and
-closed again (using <link linkend="open-hook">open-hook</link> and
-<link linkend="close-hook">close-hook</link>respectively) each time you
-will add to it.
-</para>
-</sect2>
-
-<sect2>
-<title>Encrypted folders</title>
-
-<para>
-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 use
-the following hooks:
-
-<screen>
-open-hook \\.pgp$ "pgp -f < %f > %t"
-close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-</screen>
-
-Please note, that PGP does not support appending to an encrypted
-folder, so there is no append-hook defined.
-
-If you are using GnuPG instead of PGP, you may use the following hooks
-instead:
-
-<screen>
-open-hook \\.gpg$ "gpg --decrypt < %f > %t"
-close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
-</screen>
-
-<emphasis role="bold">Note:</emphasis> the folder is temporary stored
-decrypted in the /tmp directory, where it can be read by your system
-administrator. So think about the security aspects of this.
-</para>
-</sect2>
-</sect1>
-
-<chapter id="mimesupport">
-<title>Mutt's MIME Support</title>
-
-<para>
-Quite a bit of effort has been made to make Mutt 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 for MIME, there are two extra
-types of configuration files which Mutt uses. One is the
-<literal>mime.types</literal> file, which contains the mapping of file extensions to
-IANA MIME types. The other is the <literal>mailcap</literal> file, which specifies
-the external commands to use for handling specific MIME types.
-</para>
-
-<sect1 id="using-mime">
-<title>Using MIME in Mutt</title>
-
-<para>
-There are three areas/menus in Mutt which deal with MIME, they are the
-pager (while viewing a message), the attachment menu and the compose
-menu.
-</para>
-
-<sect2 id="mime-pager">
-<title>Viewing MIME messages in the pager</title>
-
-<para>
-When you select a message from the index and view it in the pager, Mutt
-decodes the message to a text representation. Mutt internally supports
-a number of MIME types, including <literal>text/plain, text/enriched,
-message/rfc822, and message/news</literal>. In addition, the export
-controlled version of Mutt recognizes a variety of PGP MIME types,
-including PGP/MIME and application/pgp.
-</para>
-
-<para>
-Mutt will denote attachments with a couple lines describing them.
-These lines are of the form:
-</para>
-
-<screen>
-[-- Attachment #1: Description --]
-[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-</screen>
-
-<para>
-Where the <literal>Description</literal> is the description or filename given for the
-attachment, and the <literal>Encoding</literal> is one of
-<literal>7bit/8bit/quoted-printable/base64/binary</literal>.
-</para>
-
-<para>
-If Mutt cannot deal with a MIME type, it will display a message like:
-</para>
-
-<screen>
-[-- image/gif is unsupported (use 'v' to view this part) --]
-</screen>
-
-</sect2>
-
-<sect2 id="attach-menu">
-<title>The Attachment Menu</title>
-
-<para>
-The default binding for <literal>view-attachments</literal> is `v', which displays the
-attachment menu for a message. The attachment menu displays a list of
-the 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 <quote>tag-prefix</quote> 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.
-</para>
-
-<para>
-Finally, you can apply the usual message-related functions (like
-<link linkend="resend-message"><literal><resend-message></literal></link>, and the
-<literal><reply></literal> and <literal><forward></literal>
-functions) to attachments of type <literal>message/rfc822</literal>.
-</para>
-
-<para>
-See the help on the attachment menu for more information.
-</para>
-
-</sect2>
-
-<sect2 id="compose-menu">
-<title>The Compose Menu</title>
-
-<para>
-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.
-</para>
-
-<para>
-Attachments appear as follows:
-</para>
-
-<screen>
-- 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>
-</screen>
-
-<para>
-The '-' denotes that Mutt will delete the file after sending (or
-postponing, or canceling) the message. It can be toggled with the
-<literal>toggle-unlink</literal> command (default: u). The next field is the MIME
-content-type, and can be changed with the <literal>edit-type</literal> 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 <literal>edit-encoding</literal> 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 <literal>rename-file</literal> command (default: R).
-The final field is the description of the attachment, and can be
-changed with the <literal>edit-description</literal> command (default: d).
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="mime-types">
-<title>MIME Type configuration with <literal>mime.types</literal></title>
-
-<para>
-When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at <literal>${HOME}/.mime.types</literal>, and then
-the system mime.types file at <literal>/usr/local/share/mutt/mime.types</literal> or
-<literal>/etc/mime.types</literal>
-</para>
-
-<para>
-The mime.types file consist of lines containing a MIME type and a space
-separated list of extensions. For example:
-</para>
-
-<screen>
-application/postscript ps eps
-application/pgp pgp
-audio/x-aiff aif aifc aiff
-</screen>
-
-<para>
-A sample <literal>mime.types</literal> file comes with the Mutt distribution, and
-should contain most of the MIME types you are likely to use.
-</para>
-
-<para>
-If Mutt 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 will assume that the file is plain text, and mark it
-as <literal>text/plain</literal>. If the file contains binary information, then Mutt will
-mark it as <literal>application/octet-stream</literal>. You can change the MIME
-type that Mutt assigns to an attachment by using the <literal>edit-type</literal>
-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 recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
-major mime types, such as the chemical type that is widely used in the
-molecular modeling community to pass molecular data in various forms to
-various molecular viewers. Non-recognized mime types should only be used
-if the recipient of the message is likely to be expecting such attachments.
-</para>
-
-</sect1>
-
-<sect1 id="mailcap">
-<title>MIME Viewer configuration with <literal>mailcap</literal></title>
-
-<para>
-Mutt supports RFC 1524 MIME Configuration, in particular the Unix
-specific format specified in Appendix A of RFC 1524. 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.
-</para>
-
-<para>
-In order to handle various MIME types that Mutt can not handle
-internally, Mutt parses a series of external configuration files to
-find an external handler. The default search string for these files
-is a colon delimited list containing the following files:
-</para>
-
-<orderedlist>
-<listitem><para><literal>$HOME/.mailcap</literal></para></listitem>
-<listitem><para><literal>$PKGDATADIR/mailcap</literal></para></listitem>
-<listitem><para><literal>$SYSCONFDIR/mailcap</literal></para></listitem>
-<listitem><para><literal>/etc/mailcap</literal></para></listitem>
-<listitem><para><literal>/usr/etc/mailcap</literal></para></listitem>
-<listitem><para><literal>/usr/local/etc/mailcap</literal></para></listitem>
-</orderedlist>
-
-<para>
-where <literal>$HOME</literal> is your home directory. The
-<literal>$PKGDATADIR</literal> and the
-<literal>$SYSCONFDIR</literal> directories depend on where mutt
-is installed: the former is the default for shared data, the
-latter for system configuration files.
-</para>
-
-<para>
-The default search path can be obtained by running the following
-command:
-</para>
-
-<screen>
-mutt -nF /dev/null -Q mailcap_path
-</screen>
-
-<para>
-In particular, the metamail distribution will install a mailcap file,
-usually as <literal>/usr/local/etc/mailcap</literal>, which contains some baseline
-entries.
-</para>
-
-<sect2 id="mailcap-basics">
-<title>The Basics of the mailcap file</title>
-
-<para>
-A mailcap file consists of a series of lines which are comments, blank,
-or definitions.
-</para>
-
-<para>
-A comment line consists of a # character followed by anything you want.
-</para>
-
-<para>
-A blank line is blank.
-</para>
-
-<para>
-A definition line consists of a content type, a view command, and any
-number of optional fields. Each field of a definition line is divided
-by a semicolon ';' character.
-</para>
-
-<para>
-The content type is specified in the MIME standard type/subtype method.
-For example,
-<literal>text/plain, text/html, image/gif, </literal>
-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, <literal>image/*</literal>, or
-<literal>video,</literal> will match all image types and video types,
-respectively.
-</para>
-
-<para>
-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 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 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.
-</para>
-
-<para>
-So, in the simplest form, you can send a text/plain message to the
-external pager more on stdin:
-</para>
-
-<screen>
-text/plain; more
-</screen>
-
-<para>
-Or, you could send the message as a file:
-</para>
-
-<screen>
-text/plain; more %s
-</screen>
-
-<para>
-Perhaps you would like to use lynx to interactively view a text/html
-message:
-</para>
-
-<screen>
-text/html; lynx %s
-</screen>
-
-<para>
-In this case, lynx does not support viewing a file from stdin, so you
-must use the %s syntax.
-</para>
-
-<note>
-<para>
-<emphasis>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.</emphasis>
-</para>
-</note>
-
-<para>
-On the other hand, maybe you don't want to use lynx interactively, you
-just want to have it convert the text/html to text/plain, then you can
-use:
-</para>
-
-<screen>
-text/html; lynx -dump %s | more
-</screen>
-
-<para>
-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:
-</para>
-
-<screen>
-text/html; lynx %s
-text/*; more
-</screen>
-
-<para>
-This is the simplest form of a mailcap file.
-</para>
-
-</sect2>
-
-<sect2 id="secure-mailcap">
-<title>Secure use of mailcap</title>
-
-<para>
-The interpretation of shell meta-characters embedded in MIME parameters
-can lead to security problems in general. Mutt tries to quote parameters
-in expansion of %s syntaxes properly, and avoids risky characters by
-substituting them, see the <link linkend="mailcap-sanitize">$mailcap_sanitize</link> variable.
-</para>
-
-<para>
-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:
-</para>
-
-<para>
-<emphasis>Keep the %-expandos away from shell quoting.</emphasis>
-Don't quote them with single or double quotes. Mutt 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 behavior with quotes introduces new leaks - there is no
-alternative to correct quoting in the first place.
-</para>
-
-<para>
-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 <literal>$charset</literal> inside the backtick expansion is safe,
-since it is not itself subject to any further expansion):
-</para>
-
-<screen>
-text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-</screen>
-
-</sect2>
-
-<sect2 id="advanced-mailcap">
-<title>Advanced mailcap Usage</title>
-
-<sect3 id="optional-mailcap-fields">
-<title>Optional Fields</title>
-
-<para>
-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 recognizes the following optional fields:
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>copiousoutput</term>
-<listitem>
-<para>
-This flag tells Mutt that the command passes possibly large amounts of
-text on stdout. This causes Mutt 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 assumes that the command
-is interactive. One could use this to replace the pipe to <literal>more</literal>
-in the <literal>lynx -dump</literal> example in the Basic section:
-</para>
-
-<screen>
-text/html; lynx -dump %s ; copiousoutput
-</screen>
-
-<para>
-This will cause lynx to format the text/html output as text/plain
-and Mutt will use your standard pager to display the results.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>needsterminal</term>
-<listitem>
-<para>
-Mutt uses this flag when viewing attachments with <link linkend="auto-view">auto_view</link>, in order to decide whether it should honor the setting
-of the <link linkend="wait-key">$wait_key</link> variable or
-not. When an attachment is viewed using an interactive program, and the
-corresponding mailcap entry has a <emphasis>needsterminal</emphasis> flag, Mutt will use
-<link linkend="wait-key">$wait_key</link> and the exit status
-of 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.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>compose=<command></term>
-<listitem>
-<para>
-This flag specifies the command to use to create a new attachment of a
-specific MIME type. Mutt supports this from the compose menu.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>composetyped=<command></term>
-<listitem>
-<para>
-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 supports this from the compose menu.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>print=<command></term>
-<listitem>
-<para>
-This flag specifies the command to use to print a specific MIME type.
-Mutt supports this from the attachment and compose menus.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>edit=<command></term>
-<listitem>
-<para>
-This flag specifies the command to use to edit a specific MIME type.
-Mutt supports this from the compose menu, and also uses it to compose
-new attachments. Mutt will default to the defined editor for text
-attachments.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>nametemplate=<template></term>
-<listitem>
-<para>
-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 <literal>text/html</literal> if the file ends in <literal>.html</literal>.
-So, you would specify lynx as a <literal>text/html</literal> viewer with a line in
-the mailcap file like:
-</para>
-
-<screen>
-text/html; lynx %s; nametemplate=%s.html
-</screen>
-
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>test=<command></term>
-<listitem>
-<para>
-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 uses this entry. If the command returns non-zero,
-then the test failed, and Mutt continues searching for the right entry.
-Note that the content-type must match before Mutt performs the test.
-For example:
-</para>
-
-<screen>
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s
-</screen>
-
-<para>
-In this example, Mutt 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 will call netscape to display the
-text/html object. If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</sect3>
-
-<sect3 id="mailcap-search-order">
-<title>Search Order</title>
-
-<para>
-When searching for an entry in the mailcap file, Mutt will search for
-the most useful entry for its purpose. For instance, if you are
-attempting to print an <literal>image/gif</literal>, and you have the following
-entries in your mailcap file, Mutt will search for an entry with the
-print command:
-</para>
-
-<screen>
-image/*; xv %s
-image/gif; ; print= anytopnm %s | pnmtops | lpr; \
- nametemplate=%s.gif
-</screen>
-
-<para>
-Mutt will skip the <literal>image/*</literal> entry and use the <literal>image/gif</literal>
-entry with the print command.
-</para>
-
-<para>
-In addition, you can use this with <link linkend="auto-view">auto_view</link>
-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.
-</para>
-
-<screen>
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s; nametemplate=%s.html
-text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
-</screen>
-
-<para>
-For <link linkend="auto-view">auto_view</link>, Mutt 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 will use the second entry
-for interactive viewing.
-</para>
-
-</sect3>
-
-<sect3 id="mailcap-command-expansion">
-<title>Command Expansion</title>
-
-<para>
-The various commands defined in the mailcap files are passed to the
-<literal>/bin/sh</literal> shell using the system() function. Before the
-command is passed to <literal>/bin/sh -c</literal>, it is parsed to expand
-various special parameters with information from Mutt. The keywords
-Mutt expands are:
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>%s</term>
-<listitem>
-<para>
-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 to not pass the body of the message
-to the view/print/edit program on stdin.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>%t</term>
-<listitem>
-<para>
-Mutt 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 <literal>text/html</literal> or
-<literal>image/gif</literal>.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>%{<parameter>}</term>
-<listitem>
-<para>
-Mutt 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:
-</para>
-
-<screen>
-Content-Type: text/plain; charset=iso-8859-1
-</screen>
-
-<para>
-then Mutt 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.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>\%</term>
-<listitem>
-<para>
-This will be replaced by a %
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-<para>
-Mutt 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.
-</para>
-
-</sect3>
-
-</sect2>
-
-<sect2 id="mailcap-example">
-<title>Example mailcap files</title>
-
-<para>
-This mailcap file is fairly simple and standard:
-</para>
-
-<screen>
-# I'm always running X :)
-video/*; xanim %s > /dev/null
-image/*; xv %s > /dev/null
-
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html; netscape -remote 'openURL(%s)'
-</screen>
-
-<para>
-This mailcap file shows quite a number of examples:
-</para>
-
-<screen>
-# Use xanim to view all videos Xanim produces a header on startup,
-# send that to /dev/null so I don't see it
-video/*; xanim %s > /dev/null
-
-# Send html to a running netscape by remote
-text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
-
-# If I'm not running netscape but I am running X, start netscape on the
-# object
-text/html; netscape %s; test=RunningX
-
-# Else use lynx to view it as text
-text/html; lynx %s
-
-# This version would convert the text/html to text/plain
-text/html; lynx -dump %s; copiousoutput
-
-# I use enscript to print text in two columns to a page
-text/*; more %s; print=enscript -2Gr %s
-
-# Netscape adds a flag to tell itself to view jpegs internally
-image/jpeg;xv %s; x-mozilla-flags=internal
-
-# Use xv to view images if I'm running X
-# In addition, this uses the \ to extend the line and set my editor
-# for images
-image/*;xv %s; test=RunningX; \
- edit=xpaint %s
-
-# Convert images to text using the netpbm tools
-image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
-pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
-# Send excel spreadsheets to my NT box
-application/ms-excel; open.pl %s
-</screen>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="auto-view">
-<title>MIME Autoview</title>
-
-<para>
-In addition to explicitly telling Mutt to view an attachment with the
-MIME viewer defined in the mailcap file, Mutt has support for
-automatically viewing MIME attachments while in the pager.
-</para>
-
-<para>
-To work, you must define a viewer in the mailcap file which uses the
-<literal>copiousoutput</literal> 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.
-</para>
-
-<para>
-You then use the <literal>auto_view</literal> muttrc command to list the
-content-types that you wish to view automatically.
-</para>
-
-<para>
-For instance, if you set auto_view to:
-</para>
-
-<screen>
-auto_view text/html application/x-gunzip \
- application/postscript image/gif application/x-tar-gz
-</screen>
-
-<para>
-Mutt could use the following mailcap entries to automatically view
-attachments of these types.
-</para>
-
-<screen>
-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
-</screen>
-
-<para>
-<quote>unauto_view</quote> 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.
-<quote>unauto_view *</quote> will remove all previous entries.
-</para>
-
-</sect1>
-
-<sect1 id="alternative-order">
-<title>MIME Multipart/Alternative</title>
-
-<para>
-Mutt 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 types
-is preferred. The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
-</para>
-
-<screen>
-alternative_order text/enriched text/plain text application/postscript image/*
-</screen>
-
-<para>
-Next, mutt will check if any of the types have a defined
-<link linkend="auto-view">auto_view</link>, and use that. Failing
-that, Mutt will look for any text type. As a last attempt, mutt will
-look for any type it knows how to handle.
-</para>
-
-<para>
-To remove a MIME type from the <literal>alternative_order</literal> list, use the
-<literal>unalternative_order</literal> command.
-</para>
-
-</sect1>
-
-<sect1 id="attachments">
-<title>Attachment Searching and Counting</title>
-
-<para>
-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.
-</para>
-
-<para>
-In order to provide this information, mutt needs to fully MIME-parse
-all messages affected first. This can slow down operation especially for
-remote mail folders such as IMAP because all messages have to be
-downloaded first regardless whether the user really wants to view them
-or not.
-</para>
-
-<para>
-The syntax is:
-</para>
-
-<screen>
-attachments {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments ?
-</screen>
-
-<para>
-Disposition is the attachment's Content-disposition type -- either
-<literal>inline</literal> or <literal>attachment</literal>.
-You can abbreviate this to <literal>I</literal> or <literal>A</literal>.
-</para>
-
-<para>
-Disposition is prefixed by either a + symbol or 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.
-</para>
-
-<para>
-Mime-type is, unsurprisingly, the MIME type of the attachment you want
-to affect. A MIME type is always of the format <literal>major/minor</literal>, where
-<literal>major</literal> describes the broad category of document you're looking at, and
-<literal>minor</literal> describes the specific type within that category. The major
-part of mime-type must be literal text (or the special token <quote><literal>*</literal></quote>), but
-the minor part may be a regular expression. (Therefore, <quote><literal>*/.*</literal></quote> matches
-any MIME type.)
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-Some examples might help to illustrate. The examples that are not
-commented out define the default configuration of the lists.
-</para>
-
-<example id="ex-attach-count">
-<title>Attachment counting</title>
-<screen>
-## 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
-</screen>
-</example>
-
-<para>
-Entering the command <quote><literal>attachments ?</literal></quote>
-as a command will list your current settings in Muttrc format, so that
-it can be pasted elsewhere.
-</para>
-
-</sect1>
-
-<sect1 id="mime-lookup">
-<title>MIME Lookup</title>
-
-<para>
-Mutt's mime_lookup list specifies a list of mime-types that should not
-be treated according to their mailcap entry. This option is designed to
-deal 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:
-</para>
-
-<screen>
-mime_lookup application/octet-stream application/X-Lotus-Manuscript
-</screen>
-
-<para>
-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.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="optionalfeatures">
-<title>Optional features</title>
-
-<sect1 id="optionalfeatures-notes">
-<title>General notes</title>
-
-<sect2 id="compile-time-features">
-<title>Enabling/disabling features</title>
-
-<para>
-Mutt supports several of optional features which can be enabled or
-disabled at compile-time by giving the <emphasis>configure</emphasis> script
-certain arguments. These are listed in the <quote>Optional features</quote> section of
-the <emphasis>configure --help</emphasis> output.
-</para>
-
-<para>
-Which features are enabled or disabled can later be determined from the
-output of <literal>mutt -v</literal>. If a compile option starts with
-<quote>+</quote> it is enabled and disabled if prefixed with <quote>-</quote>. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
-OpenSSL, <literal>mutt -v</literal> would contain:
-</para>
-
-<screen>
--USE_SSL_OPENSSL +USE_SSL_GNUTLS</screen>
-
-</sect2>
-
-<sect2 id="url-syntax">
-<title>URL syntax</title>
-
-<para>
-Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
-to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in <literal>[]</literal> means it is optional and
-may be omitted):
-</para>
-
-<screen>
-proto[s]://[username[:password]@]server[:port]/[path]
-</screen>
-
-<para>
-<literal>proto</literal> is the communication protocol:
-<literal>imap</literal> for IMAP, <literal>pop</literal> for POP3 and
-<literal>smtp</literal> for SMTP. If <quote>s</quote> for <quote>secure communication</quote>
-is appended, mutt will attempt to establish an encrypted communication
-using SSL or TLS. If no explicit port is given, mutt will use the
-system's default for the given protocol.
-</para>
-
-<para>
-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the <literal>pop_user</literal> or
-<literal>imap_user</literal> variables. It may contain the <quote>@</quote> symbol
-being used by many mail systems as part of the login name. A password can be
-given, too but is not recommended if the URL is specified in a configuration
-file on disk.
-</para>
-
-<para>
-The optional path is only relevant for IMAP.
-</para>
-
-<para>
-For IMAP for example, you can select an alternative port by specifying it with the
-server: <literal>imap://imapserver:port/INBOX</literal>. You can also specify different
-username for each folder: <literal>imap://username@imapserver[:port]/INBOX</literal>
-or <literal>imap://username2@imapserver[:port]/path/to/folder</literal>.
-Replacing <literal>imap://</literal> by <literal>imaps://</literal>
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="ssl">
-<title>SSL/TLS Support</title>
-
-<para>
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
-compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
-by running the <emphasis>configure</emphasis> script with the
-<emphasis>--enable-ssl=...</emphasis> option for OpenSSL or
-<emphasis>--enable-gnutls=...</emphasis> for GnuTLS). Mutt can then
-attempt to encrypt communication with remote servers if these protocols
-are suffixed with <quote>s</quote> for <quote>secure communication</quote>.
-</para>
-
-</sect1>
-
-<sect1 id="pop">
-<title>POP3 Support</title>
-
-<para>
-If Mutt was compiled with POP3 support (by running the <emphasis>configure</emphasis>
-script with the <emphasis>--enable-pop</emphasis> flag), it has the ability to work
-with mailboxes located on a remote POP3 server and fetch mail for local
-browsing.
-</para>
-
-<para>
-Remote POP3 servers can be accessed using URLs with the <literal>pop</literal> protocol
-for unencrypted and <literal>pops</literal> for encrypted
-communication, see <xref linkend="url-syntax"/> for details.
-</para>
-
-<para>
-Polling for new mail is more expensive over POP3 than locally. For this
-reason the frequency at which Mutt will check for mail remotely can be
-controlled by the
-<link linkend="pop-checkinterval">$pop_checkinterval</link>
-variable, which defaults to every 60 seconds.
-</para>
-
-<anchor id="fetch-mail"/>
-<para>
-Another way to access your POP3 mail is the <literal><fetch-mail$</literal> function
-(default: G). It allows to connect to <link linkend="pop-host">$pop_host</link>, fetch all your new mail and place it in the
-local <link linkend="spoolfile">$spoolfile</link>. After this
-point, Mutt runs exactly as if the mail had always been local.
-</para>
-
-<note>
-<para>
-If you only need to fetch all messages to a
-local mailbox you should consider using a specialized program, such as
-<literal>fetchmail</literal>, <literal>getmail</literal> or similar.
-</para>
-</note>
-
-</sect1>
-
-<sect1 id="imap">
-<title>IMAP Support</title>
-
-<para>
-If Mutt was compiled with IMAP support (by running the <emphasis>configure</emphasis>
-script with the <emphasis>--enable-imap</emphasis> flag), it has the ability to work
-with folders located on a remote IMAP server.
-</para>
-
-<para>
-You can access the remote inbox by selecting the folder by its URL
-(see <xref linkend="url-syntax"/> for details) using the
-<literal>imap</literal> or <literal>imaps</literal> protocol.
-Alternatively, a pine-compatible notation is also supported, ie
-<literal>{[username@]imapserver[:port][/ssl]}path/to/folder</literal>
-</para>
-
-<para>
-Note that not all servers use <quote>/</quote> as the hierarchy separator. Mutt should
-correctly notice which separator is being used by the server and convert
-paths accordingly.
-</para>
-
-<para>
-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
-<emphasis>toggle-subscribed</emphasis> command. See also the
-<link linkend="imap-list-subscribed">$imap_list_subscribed</link> variable.
-</para>
-
-<para>
-Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
-want to carefully tune the
-<link linkend="mail-check">$mail_check</link>
-and
-<link linkend="timeout">$timeout</link>
-variables. Personally I use
-</para>
-
-<screen>
-set mail_check=90
-set timeout=15
-</screen>
-
-<para>
-with relatively good results over my slow modem line.
-</para>
-
-<note>
-<para>
-Note that if you are using mbox as the mail store on UW servers prior to
-v12.250, the server has been reported to disconnect a client if another client
-selects the same folder.
-</para>
-</note>
-
-<sect2 id="imap-browser">
-<title>The Folder Browser</title>
-
-<para>
-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:
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-In lieu 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.
-</para>
-</listitem>
-<listitem>
-
-<para>
-For the case where an entry can contain both messages and
-subfolders, the selection key (bound to <literal>enter</literal> by default)
-will choose to descend into the subfolder view. If you wish to view
-the messages in that folder, you must use <literal>view-file</literal> instead
-(bound to <literal>space</literal> by default).
-</para>
-</listitem>
-<listitem>
-
-<para>
-You can create, delete and rename mailboxes with the
-<literal>create-mailbox</literal>, <literal>delete-mailbox</literal>, and
-<literal>rename-mailbox</literal> commands (default bindings: <literal>C</literal>,
-<literal>d</literal> and <literal>r</literal>, respectively). You may also
-<literal>subscribe</literal> and <literal>unsubscribe</literal> to mailboxes (normally
-these are bound to <literal>s</literal> and <literal>u</literal>, respectively).
-</para>
-</listitem>
-
-</itemizedlist>
-
-</sect2>
-
-<sect2 id="imap-authentication">
-<title>Authentication</title>
-
-<para>
-Mutt 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".
-</para>
-
-<para>
-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 library
-installed on your system and compile mutt with the <emphasis>--with-sasl</emphasis> flag.
-</para>
-
-<para>
-Mutt will try whichever methods are compiled in and available on the server,
-in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-</para>
-
-<para>
-There are a few variables which control authentication:
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-<link linkend="imap-user">$imap_user</link> - 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 (ie by using a mailbox name of the form
-<literal>{user@host}</literal>).
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="imap-pass">$imap_pass</link> - a
-password which you may preset, used by all authentication methods where
-a password is needed.
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="imap-authenticators">$imap_authenticators</link> - 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).
-</para>
-</listitem>
-
-</itemizedlist>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="smtp">
-<title>SMTP Support</title>
-
-<para>
-Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
-was configured and built with <literal>--enable-smtp</literal>.
-</para>
-
-<para>
-If the configuration variable
-<link linkend="smtp-url">$smtp_url</link> is set, mutt
-will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by <link linkend="sendmail">$sendmail</link>.
-</para>
-
-<para>
-For details on the URL syntax, please see <xref linkend="url-syntax"/>.
-</para>
-
-<para>
-The built-in SMTP support supports encryption (the <literal>smtps</literal> protocol
-using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
-for SASL are specified in <link linkend="smtp-authenticators">$smtp_authenticators</link>
-defaulting to an empty list which makes mutt try all available methods
-from most-secure to least-secure.
-</para>
-
-</sect1>
-
-<sect1 id="account-hook">
-<title>Managing multiple accounts</title>
-
-<para>
-If you happen to have accounts on multiple IMAP, POP and/or SMTP 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 which includes (for example) polling for new mail, storing Fcc
-messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
-as passwords or tunnel commands but not settings such as sender
-address or name (because in general it should be considered unpredictable
-which account-hook was last used).
-</para>
-
-<para>
-Some examples:
-</para>
-
-<screen>
-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"'
-account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-</screen>
-
-</sect1>
-
-<sect1 id="caching">
-<title>Local caching</title>
-
-<para>
-Mutt contains two types of local caching: <emphasis>(1)</emphasis>
-the so-called <quote>header caching</quote> and <emphasis>(2)</emphasis> the
-so-called <quote>body caching</quote> which are both described in this section.
-</para>
-
-<para>
-Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
-support as these use it (body caching requires no external library).
-</para>
-
-<sect2 id="header-caching">
-<title>Header caching</title>
-
-<para>
-Mutt provides optional support for caching message headers for the
-following types of folders: IMAP, POP, Maildir and MH. Header caching
-greatly improves speed because for remote folders, headers
-usually only need to be downloaded once. For Maildir and MH, reading the
-headers from a single file is much faster than looking at possibly
-thousands of single files (since Maildir and MH use one file per message.)
-</para>
-
-<para>
-Header caching can be enabled via the configure script and the
-<emphasis>--enable-hcache</emphasis> option. It's not turned on
-by default because external database libraries are required: one
-of tokyocabinet, qdbm, gdbm or bdb must be present.
-</para>
-
-<para>
-If enabled, <link
-linkend="header-cache">$header_cache</link> can be
-used to either point to a file or a directory. If set to point to
-a file, one database file for all folders will be used (which may
-result in lower performance), but one file per folder if it points
-to a directory.
-</para>
-
-<para>
-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-</para>
-
-<screen>
-$ printf '%s' '/path/to/folder' | md5sum
-</screen>
-
-<para>
-The <literal>md5sum</literal> command may also be
-named <literal>md5</literal>, depending on your operating system.
-</para>
-
-</sect2>
-
-<sect2 id="body-caching">
-<title>Body caching</title>
-
-<para>
-Both cache methods can be combined using the same directory for storage
-(and for IMAP/POP even provide meaningful file names) which simplifies
-manual maintenance tasks.
-</para>
-
-
-<para>
-In addition to caching message headers only, mutt can also cache
-whole message bodies. This results in faster display of messages
-for POP and IMAP folders because messages usually have to be
-downloaded only once.
-</para>
-
-<para>
-For configuration, the variable <link linkend="message-cachedir"
->$message_cachedir</link> must point to a
-directory. There, mutt will create a hierarchy of subdirectories
-named like: <literal>proto:user@hostname</literal> where
-<literal>proto</literal> is either <quote>pop</quote> or <quote>imap.</quote> Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-</para>
-
-<para>
-All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
-</para>
-
-</sect2>
-
-<sect2 id="maint-cache">
-<title>Maintenance</title>
-
-<para>
-Mutt does not (yet) support maintenance features for header cache
-database files so that files have to be removed in case they grow too
-big. It depends on the database library used for header caching whether
-disk space freed by removing messages is re-used.
-</para>
-
-<para>
-For body caches, mutt can keep the local cache in sync with the
-remote mailbox if the
-<link linkend="message-cache-clean">$message_cache_clean</link>
-variable is set. Cleaning means to remove messages from the cache which
-are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
-delete messages (Mutt itself removes deleted messages from the cache
-when syncing a mailbox). As cleaning can take a noticeable amount of time,
-it should not be set in general but only occasionally.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="exact-address">
-<title>Exact address generation</title>
-
-<para>
-Mutt supports the <quote>Name <user@host></quote> address syntax for reading and
-writing messages, the older <quote>user@host (Name)</quote> syntax is only supported when
-reading messages. The <emphasis>--enable-exact-address</emphasis>
-switch can be given to configure to build it with write-support
-for the latter syntax. <literal>EXACT_ADDRESS</literal> in the output of
-<literal>mutt -v</literal> indicates whether it's supported.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="tuning">
-<title>Performance tuning</title>
-
-<sect1 id="tuning-mailboxes">
-<title>Reading and writing mailboxes</title>
-
-<para>
-Mutt's performance when reading mailboxes can be improved in two ways:
-</para>
-
-<orderedlist>
-
-<listitem>
-<para>
-For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
-performance can be greatly improved using
-<link linkend="header-caching">header caching</link>.
-Using a single database per folder may further increase
-performance.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Mutt provides the <link linkend="read-inc">$read_inc</link>
-and <link linkend="write-inc">$write_inc</link>
-variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
-time on updating the progress counter than it spends on
-actually reading/writing folders.
-</para>
-<para>
-For example, when opening a maildir folder with a few
-thousand messages, the default value for
-<link linkend="read-inc">$read_inc</link>
-may be too low. It can be tuned on on a folder-basis using
-<link linkend="folder-hook">folder-hooks</link>:
-</para>
-
-<screen>
-# use very high $read_inc to speed up reading hcache'd maildirs
-folder-hook . 'set read_inc=1000'
-# use lower value for reading slower remote IMAP folders
-folder-hook ^imap 'set read_inc=100'
-# use even lower value for reading even slower remote POP folders
-folder-hook ^pop 'set read_inc=1'</screen>
-
-</listitem>
-</orderedlist>
-
-<para>These settings work on a per-message basis. However, as messages may
-greatly differ in size and certain operations are much faster than others,
-even per-folder settings of the increment variables may not be
-desirable as they produce either too few or too much progress updates.
-Thus, Mutt allows to limit the number of progress updates per second it'll
-actually send to the terminal using the
-<link linkend="time-inc">$time_inc</link> variable.</para>
-
-</sect1>
-
-<sect1 id="tuning-messages">
-<title>Reading messages from remote folders</title>
-
-<para>
-Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
-limited number of recently viewed messages (usually 10) per
-session (so that it will be gone for the next session.)
-</para>
-
-<para>
-To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
-<link linkend="body-caching">body caching</link> for details.
-</para>
-
-</sect1>
-
-<sect1 id="tuning-search">
-<title>Searching and limiting</title>
-
-<para>
-When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
-searches. For regular expressions, patterns are prefixed with
-<quote>˜</quote> and with <quote>=</quote> for string searches.
-</para>
-
-<para>
-Even though a regular expression search is fast, it's several times
-slower than a pure string search which is noticeable especially on large
-folders. As a consequence, a string search should be used instead of a
-regular expression search if the user already knows enough about the
-search pattern.
-</para>
-
-<para>
-For example, when limiting a large folder to all messages sent to or by
-an author, it's much faster to search for the initial part of an e-mail
-address via <literal>=Luser@</literal> instead of
-<literal>˜Luser@</literal>. This is especially true for searching
-message bodies since a larger amount of input has to be searched.
-</para>
-
-<para>
-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="reference">
-<title>Reference</title>
-
-<sect1 id="commandline">
-<title>Command line options</title>
-
-<para>
-Running <literal>mutt</literal> with no arguments will make Mutt attempt to read your spool
-mailbox. However, it is possible to read other mailboxes and
-to send messages from the command line as well.
-</para>
-
-<table id="tab-commandline-options">
-<title>Command line options</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Option</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>-A</entry><entry>expand an alias</entry></row>
-<row><entry>-a</entry><entry>attach a file to a message</entry></row>
-<row><entry>-b</entry><entry>specify a blind carbon-copy (BCC) address</entry></row>
-<row><entry>-c</entry><entry>specify a carbon-copy (Cc) address</entry></row>
-<row><entry>-D</entry><entry>print the value of all mutt variables to stdout</entry></row>
-<row><entry>-e</entry><entry>specify a config command to be run after initialization files are read</entry></row>
-<row><entry>-f</entry><entry>specify a mailbox to load</entry></row>
-<row><entry>-F</entry><entry>specify an alternate file to read initialization commands</entry></row>
-<row><entry>-h</entry><entry>print help on command line options</entry></row>
-<row><entry>-H</entry><entry>specify a draft file from which to read a header and body</entry></row>
-<row><entry>-i</entry><entry>specify a file to include in a message composition</entry></row>
-<row><entry>-m</entry><entry>specify a default mailbox type</entry></row>
-<row><entry>-n</entry><entry>do not read the system Muttrc</entry></row>
-<row><entry>-p</entry><entry>recall a postponed message</entry></row>
-<row><entry>-Q</entry><entry>query a configuration variable</entry></row>
-<row><entry>-R</entry><entry>open mailbox in read-only mode</entry></row>
-<row><entry>-s</entry><entry>specify a subject (enclose in quotes if it contains spaces)</entry></row>
-<row><entry>-v</entry><entry>show version number and compile-time definitions</entry></row>
-<row><entry>-x</entry><entry>simulate the mailx(1) compose mode</entry></row>
-<row><entry>-y</entry><entry>show a menu containing the files specified by the mailboxes command</entry></row>
-<row><entry>-z</entry><entry>exit immediately if there are no messages in the mailbox</entry></row>
-<row><entry>-Z</entry><entry>open the first folder with new message,exit immediately if none</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-To read messages in a mailbox
-</para>
-
-<cmdsynopsis>
-<command>mutt</command>
-<arg choice="opt"><option>-nz</option></arg>
-<arg choice="opt"><option>-F</option>
-<replaceable>muttrc</replaceable>
-</arg>
-<arg choice="opt"><option>-m</option>
-<replaceable>type</replaceable>
-</arg>
-<arg choice="opt"><option>-f</option>
-<replaceable>mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-To compose a new message
-</para>
-
-<cmdsynopsis>
-<command>mutt</command>
-<arg choice="opt"><option>-n</option></arg>
-<arg choice="opt"><option>-F</option>
-<replaceable>muttrc</replaceable>
-</arg>
-<arg choice="opt"><option>-c</option>
-<replaceable>address</replaceable>
-</arg>
-<arg choice="opt"><option>-i</option>
-<replaceable>filename</replaceable>
-</arg>
-<arg choice="opt"><option>-s</option>
-<replaceable>subject</replaceable>
-</arg>
-<arg choice="opt">
-<option>-a</option>
-<replaceable>file</replaceable>
-<arg choice="opt" rep="repeat"/>
---
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>address</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-Mutt also supports a <quote>batch</quote> mode to send prepared messages. Simply redirect
-input from the file you wish to send. For example,
-</para>
-
-<para>
-<literal>mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat</literal>
-</para>
-
-<para>
-This command will send a message to <quote>professor@bigschool.edu</quote> with a subject
-of <quote>data set for run #2</quote>. In the body of the message will be the contents
-of the file <quote>˜/run2.dat</quote>.
-</para>
-
-<para>
-All files passed with -a <emphasis>file</emphasis> will be attached as a MIME
-part to the message. To attach several files, use <quote>--</quote> to separate files and
-recipient addresses: <literal>mutt -a *.png -- some@one.org</literal>
-</para>
-
-</sect1>
-
-<sect1 id="commands">
-<title>Configuration Commands</title>
-
-<para>
-The following are the commands understood by mutt.
-</para>
-
-<itemizedlist>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="account-hook">account-hook</link></command>
-<arg choice="plain">
-<replaceable>pattern</replaceable>
-<replaceable>command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alias">alias</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">address</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">address</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alias">unalias</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">key</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alternates">alternates</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable>regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alternates">unalternates</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alternative-order">alternative-order</link></command>
-<arg choice="plain">
-<replaceable>mimetype</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alternative-order">unalternative-order</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="auto-view">auto-view</link></command>
-<arg choice="plain">
-<replaceable>mimetype</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-
-<cmdsynopsis>
-<command><link linkend="auto-view">unauto-view</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="bind">bind</link></command>
-<arg choice="plain">
-<replaceable class="parameter">map</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">function</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="charset-hook">charset-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">alias</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">charset</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="charset-hook">iconv-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">charset</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">local-charset</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="color">color</link></command>
-<arg choice="plain">
-<replaceable class="parameter">object</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command><link linkend="color">color</link></command>
-<group choice="req">
-<arg choice="plain">
-<option>header</option>
-</arg>
-<arg choice="plain">
-<option>body</option>
-</arg>
-</group>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command><link linkend="color">color</link></command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="color">uncolor</link></command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="exec">exec</link></command>
-<arg choice="plain">
-<replaceable class="parameter">function</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">function</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="fcc-hook">fcc-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="fcc-save-hook">fcc-save-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="folder-hook">folder-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]regexp</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="addrgroup">group</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain" rep="repeat">
-<option>-rx</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-addr</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="addrgroup">ungroup</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-rx</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-addr</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="hdr-order">hdr_order</link></command>
-<arg choice="plain">
-<replaceable class="parameter">header</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">header</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="hdr-order">unhdr_order</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>header</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="ignore">ignore</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="ignore">unignore</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="lists">lists</link></command>
-<arg>
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="lists">unlists</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="macro">macro</link></command>
-<arg choice="plain">
-<replaceable class="parameter">menu</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">sequence</replaceable>
-</arg>
-<arg choice="opt">
-<replaceable class="parameter">description</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mailboxes">mailboxes</link></command>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mailboxes">unmailboxes</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mbox-hook">mbox-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="message-hook">message-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mime-lookup">mime-lookup</link></command>
-<arg choice="plain">
-<replaceable>mimetype</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mime-lookup">unmime-lookup</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mono">mono</link></command>
-<arg choice="plain">
-<replaceable class="parameter">object</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command><link linkend="mono">mono</link></command>
-<group choice="req">
-<arg choice="plain">
-<option>header</option>
-</arg>
-<arg choice="plain">
-<option>body</option>
-</arg>
-</group>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command><link linkend="mono">mono</link></command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mono">unmono</link></command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="my-hdr">my_hdr</link></command>
-<arg choice="plain">
-<replaceable class="parameter">string</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="my-hdr">unmy_hdr</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">field</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="crypt-hook">crypt-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">keyid</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="push">push</link></command>
-<arg choice="plain">
-<replaceable class="parameter">string</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">reset</link></command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="save-hook">save-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="score">score</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">value</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="score">unscore</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="reply-hook">reply-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="send-hook">send-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="send2-hook">send2-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">set</link></command>
-<group choice="req">
-<arg choice="plain">
-<group choice="opt">
-<arg choice="plain"><option>no</option></arg>
-<arg choice="plain"><option>inv</option></arg>
-</group>
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">variable=value</replaceable>
-</arg>
-</group>
-<arg choice="opt" rep="repeat"/>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">unset</link></command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="source">source</link></command>
-<arg choice="plain">
-<replaceable class="parameter">filename</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="spam">spam</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">format</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="spam">nospam</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="subscribe">subscribe</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="subscribe">unsubscribe</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">toggle</link></command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="unhook">unhook</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">hook-type</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="variables">
-<title>Configuration variables</title>
-
-<sect2 id="abort-nosubject">
-<title>abort_nosubject</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-If set to <emphasis>yes</emphasis>, when composing messages and no subject is given
-at the subject prompt, composition will be aborted. If set to
-<emphasis>no</emphasis>, composing messages with no subject given at the subject
-prompt will never be aborted.
-</para>
-</sect2>
-
-<sect2 id="abort-unmodified">
-<title>abort_unmodified</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-If set to <emphasis>yes</emphasis>, composition will automatically abort after
-editing the message body if no changes are made to the file (this
-check only happens after the <emphasis>first</emphasis> edit of the file). When set
-to <emphasis>no</emphasis>, composition will never be aborted.
-</para>
-</sect2>
-
-<sect2 id="alias-file">
-<title>alias_file</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/.muttrc</literal></quote></literallayout>
-
-<para>
-The default file in which to save aliases created by the
-<literal><link linkend="create-alias"><create-alias></link></literal> function. Entries added to this file are
-encoded in the character set specified by <link linkend="config-charset">$config_charset</link> if it
-is <emphasis>set</emphasis> or the current character set otherwise.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> Mutt will not automatically source this file; you must
-explicitly use the <quote><link linkend="source">source</link></quote> command for it to be executed in case
-this option points to a dedicated alias file.
-</para>
-<para>
-The default for this option is the currently used muttrc file, or
-<quote>˜/.muttrc</quote> if no user muttrc was found.
-</para>
-</sect2>
-
-<sect2 id="alias-format">
-<title>alias_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4n %2f %t %-10a %r</literal></quote></literallayout>
-
-<para>
-Specifies the format of the data displayed for the <quote><link linkend="alias">alias</link></quote> menu. The
-following <literal>printf(3)</literal>-style sequences are available:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%a </term>
-<listitem><para>alias name
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>flags - currently, a <quote>d</quote> for an alias marked for deletion
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>index number
-</para></listitem></varlistentry>
-<varlistentry><term>%r </term>
-<listitem><para>address which alias expands to
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para>character which indicates if the alias is tagged for inclusion
-</para></listitem></varlistentry></variablelist>
-</sect2>
-
-<sect2 id="allow-8bit">
-<title>allow_8bit</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether 8-bit data is converted to 7-bit using either Quoted-
-Printable or Base64 encoding when sending mail.
-</para>
-</sect2>
-
-<sect2 id="allow-ansi">
-<title>allow_ansi</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-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 <emphasis>set</emphasis>,
-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
-
-</para>
-
-<screen>
-[-- PGP output follows ...
-
-</screen><para>
-and give it the same color as your attachment color (see also
-<link linkend="crypt-timestamp">$crypt_timestamp</link>).
-</para>
-</sect2>
-
-<sect2 id="arrow-cursor">
-<title>arrow_cursor</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, an arrow (<quote>-></quote>) 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.
-</para>
-</sect2>
-
-<sect2 id="ascii-chars">
-<title>ascii_chars</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will use plain ASCII characters when displaying thread
-and attachment trees, instead of the default <emphasis>ACS</emphasis> characters.
-</para>
-</sect2>
-
-<sect2 id="askbcc">
-<title>askbcc</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
-before editing an outgoing message.
-</para>
-</sect2>
-
-<sect2 id="askcc">
-<title>askcc</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will prompt you for carbon-copy (Cc) recipients before
-editing the body of an outgoing message.
-</para>
-</sect2>
-
-<sect2 id="assumed-charset">
-<title>assumed_charset</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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 <quote>us-ascii</quote>.
-</para>
-<para>
-For example, Japanese users might prefer this:
-
-</para>
-
-<screen>
-set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</screen><para>
-However, only the first content is valid for the message body.
-</para>
-</sect2>
-
-<sect2 id="attach-charset">
-<title>attach_charset</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This variable is a colon-separated list of character encoding
-schemes for text file attachments. Mutt uses this setting to guess
-which encoding files being attached are encoded in to convert them to
-a proper character set given in <link linkend="send-charset">$send_charset</link>.
-</para>
-<para>
-If <emphasis>unset</emphasis>, the value of <link linkend="charset">$charset</link> will be used instead.
-For example, the following configuration would work for Japanese
-text handling:
-
-</para>
-
-<screen>
-set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</screen><para>
-Note: for Japanese users, <quote>iso-2022-*</quote> must be put at the head
-of the value as shown above if included.
-</para>
-</sect2>
-
-<sect2 id="attach-format">
-<title>attach_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] </literal></quote></literallayout>
-
-<para>
-This variable describes the format of the <quote>attachment</quote> menu. The
-following <literal>printf(3)</literal>-style sequences are understood:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%C </term>
-<listitem><para>charset
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>requires charset conversion (<quote>n</quote> or <quote>c</quote>)
-</para></listitem></varlistentry>
-<varlistentry><term>%D </term>
-<listitem><para>deleted flag
-</para></listitem></varlistentry>
-<varlistentry><term>%d </term>
-<listitem><para>description
-</para></listitem></varlistentry>
-<varlistentry><term>%e </term>
-<listitem><para>MIME content-transfer-encoding
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>filename
-</para></listitem></varlistentry>
-<varlistentry><term>%I </term>
-<listitem><para>disposition (<quote>I</quote> for inline, <quote>A</quote> for attachment)
-</para></listitem></varlistentry>
-<varlistentry><term>%m </term>
-<listitem><para>major MIME type
-</para></listitem></varlistentry>
-<varlistentry><term>%M </term>
-<listitem><para>MIME subtype
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>attachment number
-</para></listitem></varlistentry>
-<varlistentry><term>%Q </term>
-<listitem><para><quote>Q</quote>, if MIME part qualifies for attachment counting
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>size
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para>tagged flag
-</para></listitem></varlistentry>
-<varlistentry><term>%T </term>
-<listitem><para>graphic tree characters
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>unlink (=to delete) flag
-</para></listitem></varlistentry>
-<varlistentry><term>%X </term>
-<listitem><para>number of qualifying MIME parts in this part and its children
-(please see the <quote><link linkend="attachments">attachments</link></quote> section for possible speed effects)
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For an explanation of <quote>soft-fill</quote>, see the <link linkend="index-format">$index_format</link> documentation.
-</para>
-</sect2>
-
-<sect2 id="attach-sep">
-<title>attach_sep</title>
-<literallayout>Type: string
-Default: <quote><literal>\n</literal></quote></literallayout>
-
-<para>
-The separator to add between attachments when operating (saving,
-printing, piping, etc) on a list of tagged attachments.
-</para>
-</sect2>
-
-<sect2 id="attach-split">
-<title>attach_split</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If this variable is <emphasis>unset</emphasis>, when operating (saving, printing, piping,
-etc) on a list of tagged attachments, Mutt will concatenate the
-attachments and will operate on them as a single attachment. The
-<link linkend="attach-sep">$attach_sep</link> separator is added after each attachment. When <emphasis>set</emphasis>,
-Mutt will operate on the attachments one by one.
-</para>
-</sect2>
-
-<sect2 id="attribution">
-<title>attribution</title>
-<literallayout>Type: string
-Default: <quote><literal>On %d, %n wrote:</literal></quote></literallayout>
-
-<para>
-This is the string that will precede a message which has been included
-in a reply. For a full listing of defined <literal>printf(3)</literal>-like sequences see
-the section on <link linkend="index-format">$index_format</link>.
-</para>
-</sect2>
-
-<sect2 id="autoedit">
-<title>autoedit</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis> along with <link linkend="edit-headers">$edit_headers</link>, Mutt will skip the initial
-send-menu (prompting for subject and recipients) 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.
-</para>
-<para>
-Also see <link linkend="fast-reply">$fast_reply</link>.
-</para>
-</sect2>
-
-<sect2 id="auto-tag">
-<title>auto_tag</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, functions in the <emphasis>index</emphasis> menu which affect a message
-will be applied to all tagged messages (if there are any). When
-unset, you must first use the <literal><tag-prefix></literal> function (bound to <quote>;</quote>
-by default) to make the next function apply to all tagged messages.
-</para>
-</sect2>
-
-<sect2 id="beep">
-<title>beep</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will beep when an error occurs.
-</para>
-</sect2>
-
-<sect2 id="beep-new">
-<title>beep_new</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will beep whenever it prints a message
-notifying you of new mail. This is independent of the setting of the
-<link linkend="beep">$beep</link> variable.
-</para>
-</sect2>
-
-<sect2 id="bounce">
-<title>bounce</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether you will be asked to confirm bouncing messages.
-If set to <emphasis>yes</emphasis> you don't get asked if you want to bounce a
-message. Setting this variable to <emphasis>no</emphasis> is not generally useful,
-and thus not recommended, because you are unable to bounce messages.
-</para>
-</sect2>
-
-<sect2 id="bounce-delivered">
-<title>bounce_delivered</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will include Delivered-To headers when
-bouncing messages. Postfix users may wish to <emphasis>unset</emphasis> this variable.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this option is unset by default in
-/etc/Muttrc.
-</para>
-</sect2>
-
-<sect2 id="braille-friendly">
-<title>braille_friendly</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will place the cursor at the beginning
-of the current line in menus, even when the <link linkend="arrow-cursor">$arrow_cursor</link> variable
-is <emphasis>unset</emphasis>, making it easier for blind persons using Braille displays to
-follow these menus. The option is <emphasis>unset</emphasis> by default because many
-visual terminals don't permit making the cursor invisible.
-</para>
-</sect2>
-
-<sect2 id="check-mbox-size">
-<title>check_mbox_size</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
-</para>
-<para>
-This variable is <emphasis>unset</emphasis> by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
-</para>
-<para>
-Note that enabling this variable should happen before any <quote><link linkend="mailboxes">mailboxes</link></quote>
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-</para>
-</sect2>
-
-<sect2 id="charset">
-<title>charset</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Character set your terminal uses to display and enter textual data.
-It is also the fallback for <link linkend="send-charset">$send_charset</link>.
-</para>
-<para>
-Upon startup Mutt tries to derive this value from environment variables
-such as <literal>$LC_CTYPE</literal> or <literal>$LANG</literal>.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> It should only be set in case Mutt isn't abled to determine the
-character set used correctly.
-</para>
-</sect2>
-
-<sect2 id="check-new">
-<title>check_new</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-<emphasis role="bold">Note:</emphasis> this option only affects <emphasis>maildir</emphasis> and <emphasis>MH</emphasis> style
-mailboxes.
-</para>
-<para>
-When <emphasis>set</emphasis>, Mutt 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
-this variable is <emphasis>unset</emphasis>, no check for new mail is performed
-while the mailbox is open.
-</para>
-</sect2>
-
-<sect2 id="collapse-unread">
-<title>collapse_unread</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, Mutt will not collapse a thread if it contains any
-unread messages.
-</para>
-</sect2>
-
-<sect2 id="uncollapse-jump">
-<title>uncollapse_jump</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will jump to the next unread message, if any,
-when the current thread is <emphasis>un</emphasis>collapsed.
-</para>
-</sect2>
-
-<sect2 id="compose-format">
-<title>compose_format</title>
-<literallayout>Type: string
-Default: <quote><literal>-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-</literal></quote></literallayout>
-
-<para>
-Controls the format of the status line displayed in the <quote>compose</quote>
-menu. This string is similar to <link linkend="status-format">$status_format</link>, but has its own
-set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%a </term>
-<listitem><para>total number of attachments
-</para></listitem></varlistentry>
-<varlistentry><term>%h </term>
-<listitem><para>local hostname
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>approximate size (in bytes) of the current message
-</para></listitem></varlistentry>
-<varlistentry><term>%v </term>
-<listitem><para>Mutt version string
-</para></listitem></varlistentry></variablelist>
-
-<para>
-See the text describing the <link linkend="status-format">$status_format</link> option for more
-information on how to set <link linkend="compose-format">$compose_format</link>.
-</para>
-</sect2>
-
-<sect2 id="config-charset">
-<title>config_charset</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-When defined, Mutt will recode commands in rc files from this
-encoding to the current character set as specified by <link linkend="charset">$charset</link>
-and aliases written to <link linkend="alias-file">$alias_file</link> from the current character set.
-</para>
-<para>
-Please note that if setting <link linkend="charset">$charset</link> it must be done before
-setting <link linkend="config-charset">$config_charset</link>.
-</para>
-<para>
-Recoding should be avoided as it may render unconvertable
-characters as question marks which can lead to undesired
-side effects (for example in regular expressions).
-</para>
-</sect2>
-
-<sect2 id="confirmappend">
-<title>confirmappend</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will prompt for confirmation when appending messages to
-an existing mailbox.
-</para>
-</sect2>
-
-<sect2 id="confirmcreate">
-<title>confirmcreate</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will prompt for confirmation when saving messages to a
-mailbox which does not yet exist before creating it.
-</para>
-</sect2>
-
-<sect2 id="connect-timeout">
-<title>connect_timeout</title>
-<literallayout>Type: number
-Default: 30</literallayout>
-
-<para>
-Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-many seconds if the connection is not able to be established. A negative
-value causes Mutt to wait indefinitely for the connection attempt to succeed.
-</para>
-</sect2>
-
-<sect2 id="content-type">
-<title>content_type</title>
-<literallayout>Type: string
-Default: <quote><literal>text/plain</literal></quote></literallayout>
-
-<para>
-Sets the default Content-Type for the body of newly composed messages.
-</para>
-</sect2>
-
-<sect2 id="copy">
-<title>copy</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not copies of your outgoing messages
-will be saved for later references. Also see <link linkend="record">$record</link>,
-<link linkend="save-name">$save_name</link>, <link linkend="force-name">$force_name</link> and <quote><link linkend="fcc-hook">fcc-hook</link></quote>.
-</para>
-</sect2>
-
-<sect2 id="crypt-use-gpgme">
-<title>crypt_use_gpgme</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable controls the use of the GPGME-enabled crypto backends.
-If it is <emphasis>set</emphasis> and Mutt was built with gpgme support, the gpgme code for
-S/MIME and PGP will be used instead of the classic code. Note that
-you need to set this option in .muttrc; it won't have any effect when
-used interactively.
-</para>
-</sect2>
-
-<sect2 id="crypt-use-pka">
-<title>crypt_use_pka</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Controls whether mutt uses PKA
-(see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
-verification (only supported by the GPGME backend).
-</para>
-</sect2>
-
-<sect2 id="crypt-autopgp">
-<title>crypt_autopgp</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages. See also <link linkend="crypt-autoencrypt">$crypt_autoencrypt</link>,
-<link linkend="crypt-replyencrypt">$crypt_replyencrypt</link>,
-<link linkend="crypt-autosign">$crypt_autosign</link>, <link linkend="crypt-replysign">$crypt_replysign</link> and <link linkend="smime-is-default">$smime_is_default</link>.
-</para>
-</sect2>
-
-<sect2 id="crypt-autosmime">
-<title>crypt_autosmime</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also <link linkend="crypt-autoencrypt">$crypt_autoencrypt</link>,
-<link linkend="crypt-replyencrypt">$crypt_replyencrypt</link>,
-<link linkend="crypt-autosign">$crypt_autosign</link>, <link linkend="crypt-replysign">$crypt_replysign</link> and <link linkend="smime-is-default">$smime_is_default</link>.
-</para>
-</sect2>
-
-<sect2 id="date-format">
-<title>date_format</title>
-<literallayout>Type: string
-Default: <quote><literal>!%a, %b %d, %Y at %I:%M:%S%p %Z</literal></quote></literallayout>
-
-<para>
-This variable controls the format of the date printed by the <quote>%d</quote>
-sequence in <link linkend="index-format">$index_format</link>. This is passed to the <literal>strftime(3)</literal>
-function to process the date, see the man page for the proper syntax.
-</para>
-<para>
-Unless the first character in the string is a bang (<quote>!</quote>), the month
-and week day names are expanded according to the locale specified in
-the variable <link linkend="locale">$locale</link>. 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 <emphasis>C</emphasis> locale (that is in US
-English).
-</para>
-</sect2>
-
-<sect2 id="default-hook">
-<title>default_hook</title>
-<literallayout>Type: string
-Default: <quote><literal>˜f %s !˜P | (˜P ˜C %s)</literal></quote></literallayout>
-
-<para>
-This variable controls how <quote><link linkend="message-hook">message-hook</link></quote>, <quote><link linkend="reply-hook">reply-hook</link></quote>, <quote><link linkend="send-hook">send-hook</link></quote>,
-<quote><link linkend="send2-hook">send2-hook</link></quote>, <quote><link linkend="save-hook">save-hook</link></quote>, and <quote><link linkend="fcc-hook">fcc-hook</link></quote> 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.
-</para>
-<para>
-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
-<quote><link linkend="alternates">alternates</link></quote>) and is to or cc'ed to a user matching the given
-regular expression.
-</para>
-</sect2>
-
-<sect2 id="delete">
-<title>delete</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not messages are really deleted when closing or
-synchronizing a mailbox. If set to <emphasis>yes</emphasis>, messages marked for
-deleting will automatically be purged without prompting. If set to
-<emphasis>no</emphasis>, messages marked for deletion will be kept in the mailbox.
-</para>
-</sect2>
-
-<sect2 id="delete-untag">
-<title>delete_untag</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If this option is <emphasis>set</emphasis>, mutt 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.
-</para>
-</sect2>
-
-<sect2 id="digest-collapse">
-<title>digest_collapse</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If this option is <emphasis>set</emphasis>, mutt's received-attachments menu will not show the subparts of
-individual messages in a multipart/digest. To see these subparts, press <quote>v</quote> on that menu.
-</para>
-</sect2>
-
-<sect2 id="display-filter">
-<title>display_filter</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-When set, specifies a command used to filter messages. When a message
-is viewed it is passed as standard input to <link linkend="display-filter">$display_filter</link>, and the
-filtered message is read from the standard output.
-</para>
-</sect2>
-
-<sect2 id="dotlock-program">
-<title>dotlock_program</title>
-<literallayout>Type: path
-Default: <quote><literal>/usr/bin/mutt_dotlock</literal></quote></literallayout>
-
-<para>
-Contains the path of the <literal>mutt_dotlock(8)</literal> binary to be used by
-mutt.
-</para>
-</sect2>
-
-<sect2 id="dsn-notify">
-<title>dsn_notify</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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: <emphasis>never</emphasis>, to never request notification,
-<emphasis>failure</emphasis>, to request notification on transmission failure,
-<emphasis>delay</emphasis>, to be notified of message delays, <emphasis>success</emphasis>, to be
-notified of successful transmission.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set dsn_notify="failure,delay"
-
-</screen><para>
-<emphasis role="bold">Note:</emphasis> when using <link linkend="sendmail">$sendmail</link> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <literal>sendmail(1)</literal>-compatible interface supporting the <literal>-N</literal> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</para>
-</sect2>
-
-<sect2 id="dsn-return">
-<title>dsn_return</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This variable controls how much of your message is returned in DSN
-messages. It may be set to either <emphasis>hdrs</emphasis> to return just the
-message header, or <emphasis>full</emphasis> to return the full message.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set dsn_return=hdrs
-
-</screen><para>
-<emphasis role="bold">Note:</emphasis> when using <link linkend="sendmail">$sendmail</link> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <literal>sendmail(1)</literal>-compatible interface supporting the <literal>-R</literal> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</para>
-</sect2>
-
-<sect2 id="duplicate-threads">
-<title>duplicate_threads</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable controls whether mutt, when <link linkend="sort">$sort</link> is set to <emphasis>threads</emphasis>, threads
-messages with the same Message-Id together. If it is <emphasis>set</emphasis>, it will indicate
-that it thinks they are duplicates of each other with an equals sign
-in the thread tree.
-</para>
-</sect2>
-
-<sect2 id="edit-headers">
-<title>edit_headers</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This option allows you to edit the header of your outgoing messages
-along with the body of your message.
-</para>
-<para>
-<emphasis role="bold">Note</emphasis> that changes made to the References: and Date: headers are
-ignored for interoperability reasons.
-</para>
-</sect2>
-
-<sect2 id="editor">
-<title>editor</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable specifies which editor is used by mutt.
-It defaults to the value of the <literal>$VISUAL</literal>, or <literal>$EDITOR</literal>, environment
-variable, or to the string <quote>/usr/bin/editor</quote> if neither of those are set.
-</para>
-</sect2>
-
-<sect2 id="encode-from">
-<title>encode_from</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will quoted-printable encode messages when
-they contain the string <quote>From </quote> (note the trailing space) in the beginning of a line.
-This is useful to avoid the tampering certain mail delivery and transport
-agents tend to do with messages (in order to prevent tools from
-misinterpreting the line as a mbox message separator).
-</para>
-</sect2>
-
-<sect2 id="envelope-from-address">
-<title>envelope_from_address</title>
-<literallayout>Type: e-mail address
-Default: (empty)</literallayout>
-
-<para>
-Manually sets the <emphasis>envelope</emphasis> sender for outgoing messages.
-This value is ignored if <link linkend="use-envelope-from">$use_envelope_from</link> is <emphasis>unset</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="escape">
-<title>escape</title>
-<literallayout>Type: string
-Default: <quote><literal>˜</literal></quote></literallayout>
-
-<para>
-Escape character to use for functions in the builtin editor.
-</para>
-</sect2>
-
-<sect2 id="fast-reply">
-<title>fast_reply</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the initial prompt for recipients and subject are skipped
-when replying to messages, and the initial prompt for subject is
-skipped when forwarding messages.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> this variable has no effect when the <link linkend="autoedit">$autoedit</link>
-variable is <emphasis>set</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="fcc-attach">
-<title>fcc_attach</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not attachments on outgoing messages
-are saved along with the main body of your message.
-</para>
-</sect2>
-
-<sect2 id="fcc-clear">
-<title>fcc_clear</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, FCCs will be stored unencrypted and
-unsigned, even when the actual message is encrypted and/or
-signed.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="folder">
-<title>folder</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/Mail</literal></quote></literallayout>
-
-<para>
-Specifies the default location of your mailboxes. A <quote>+</quote> or <quote>=</quote> 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 <emphasis>before</emphasis>
-you use <quote>+</quote> or <quote>=</quote> for any other variables since expansion takes place
-when handling the <quote><link linkend="mailboxes">mailboxes</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="folder-format">
-<title>folder_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f</literal></quote></literallayout>
-
-<para>
-This variable allows you to customize the file browser display to your
-personal taste. This string is similar to <link linkend="index-format">$index_format</link>, but has
-its own set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%C </term>
-<listitem><para>current file number
-</para></listitem></varlistentry>
-<varlistentry><term>%d </term>
-<listitem><para>date/time folder was last modified
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>filename
-</para></listitem></varlistentry>
-<varlistentry><term>%F </term>
-<listitem><para>file permissions
-</para></listitem></varlistentry>
-<varlistentry><term>%g </term>
-<listitem><para>group name (or numeric gid, if missing)
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>number of hard links
-</para></listitem></varlistentry>
-<varlistentry><term>%N </term>
-<listitem><para>N if folder has new mail, blank otherwise
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>size in bytes
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para><quote>*</quote> if the file is tagged, blank otherwise
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>owner name (or numeric uid, if missing)
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For an explanation of <quote>soft-fill</quote>, see the <link linkend="index-format">$index_format</link> documentation.
-</para>
-</sect2>
-
-<sect2 id="followup-to">
-<title>followup_to</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether or not the <quote>Mail-Followup-To:</quote> header field is
-generated when sending mail. When <emphasis>set</emphasis>, Mutt will generate this
-field when you are replying to a known mailing list, specified with
-the <quote><link linkend="subscribe">subscribe</link></quote> or <quote><link linkend="lists">lists</link></quote> commands.
-</para>
-<para>
-This field has two purposes. First, preventing you from
-receiving duplicate copies of replies to messages which you send
-to mailing lists, and second, ensuring that you do get a reply
-separately for any messages sent to known lists to which you are
-not subscribed.
-</para>
-<para>
-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.
-</para>
-</sect2>
-
-<sect2 id="force-name">
-<title>force_name</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable is similar to <link linkend="save-name">$save_name</link>, except that Mutt 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.
-</para>
-<para>
-Also see the <link linkend="record">$record</link> variable.
-</para>
-</sect2>
-
-<sect2 id="forward-decode">
-<title>forward_decode</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls the decoding of complex MIME messages into <literal>text/plain</literal> when
-forwarding a message. The message header is also RFC2047 decoded.
-This variable is only used, if <link linkend="mime-forward">$mime_forward</link> is <emphasis>unset</emphasis>,
-otherwise <link linkend="mime-forward-decode">$mime_forward_decode</link> is used instead.
-</para>
-</sect2>
-
-<sect2 id="forward-edit">
-<title>forward_edit</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-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 <quote>no</quote>.
-</para>
-</sect2>
-
-<sect2 id="forward-format">
-<title>forward_format</title>
-<literallayout>Type: string
-Default: <quote><literal>[%a: %s]</literal></quote></literallayout>
-
-<para>
-This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the <link linkend="index-format">$index_format</link> variable.
-</para>
-</sect2>
-
-<sect2 id="forward-quote">
-<title>forward_quote</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, forwarded messages included in the main body of the
-message (when <link linkend="mime-forward">$mime_forward</link> is <emphasis>unset</emphasis>) will be quoted using
-<link linkend="indent-string">$indent_string</link>.
-</para>
-</sect2>
-
-<sect2 id="from">
-<title>from</title>
-<literallayout>Type: e-mail address
-Default: (empty)</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, this variable contains a default from address. It
-can be overridden using <quote><link linkend="my-hdr">my_hdr</link></quote> (including from a <quote><link linkend="send-hook">send-hook</link></quote>) and
-<link linkend="reverse-name">$reverse_name</link>. This variable is ignored if <link linkend="use-from">$use_from</link> is <emphasis>unset</emphasis>.
-</para>
-<para>
-This setting defaults to the contents of the environment variable <literal>$EMAIL</literal>.
-</para>
-</sect2>
-
-<sect2 id="gecos-mask">
-<title>gecos_mask</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>ˆ[ˆ,]*</literal></quote></literallayout>
-
-<para>
-A regular expression used by mutt to parse the GECOS field of a password
-entry when expanding the alias. The default value
-will return the string up to the first <quote>,</quote> encountered.
-If the GECOS field contains a string like <quote>lastname, firstname</quote> then you
-should set it to <quote><literal>.*</literal></quote>.
-</para>
-<para>
-This can be useful if you see the following behavior: you address an e-mail
-to user ID <quote>stevef</quote> whose full name is <quote>Steve Franklin</quote>. If mutt expands
-<quote>stevef</quote> to <quote>"Franklin" stevef@foo.bar</quote> then you should set the <link linkend="gecos-mask">$gecos_mask</link> to
-a regular expression that will match the whole name so mutt will expand
-<quote>Franklin</quote> to <quote>Franklin, Steve</quote>.
-</para>
-</sect2>
-
-<sect2 id="hdrs">
-<title>hdrs</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, the header fields normally added by the <quote><link linkend="my-hdr">my_hdr</link></quote>
-command are not created. This variable <emphasis>must</emphasis> be unset before
-composing a new message or replying in order to take effect. If <emphasis>set</emphasis>,
-the user defined header fields are added to every new message.
-</para>
-</sect2>
-
-<sect2 id="header">
-<title>header</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, this variable causes Mutt to include the header
-of the message you are replying to into the edit buffer.
-The <link linkend="weed">$weed</link> setting applies.
-</para>
-</sect2>
-
-<sect2 id="help">
-<title>help</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, help lines describing the bindings for the major functions
-provided by each menu are displayed on the first line of the screen.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> 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 is
-running. Since this variable is primarily aimed at new users, neither
-of these should present a major problem.
-</para>
-</sect2>
-
-<sect2 id="hidden-host">
-<title>hidden_host</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will skip the host name part of <link linkend="hostname">$hostname</link> variable
-when adding the domain part to addresses. This variable does not
-affect the generation of Message-IDs, and it will not lead to the
-cut-off of first-level domains.
-</para>
-</sect2>
-
-<sect2 id="hide-limited">
-<title>hide_limited</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the presence of messages that are hidden
-by limiting, in the thread tree.
-</para>
-</sect2>
-
-<sect2 id="hide-missing">
-<title>hide_missing</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the presence of missing messages in the
-thread tree.
-</para>
-</sect2>
-
-<sect2 id="hide-thread-subject">
-<title>hide_thread_subject</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the subject of messages in the thread
-tree that have the same subject as their parent or closest previously
-displayed sibling.
-</para>
-</sect2>
-
-<sect2 id="hide-top-limited">
-<title>hide_top_limited</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the presence of messages that are hidden
-by limiting, at the top of threads in the thread tree. Note that when
-<link linkend="hide-limited">$hide_limited</link> is <emphasis>set</emphasis>, this option will have no effect.
-</para>
-</sect2>
-
-<sect2 id="hide-top-missing">
-<title>hide_top_missing</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the presence of missing messages at the
-top of threads in the thread tree. Note that when <link linkend="hide-missing">$hide_missing</link> is
-<emphasis>set</emphasis>, this option will have no effect.
-</para>
-</sect2>
-
-<sect2 id="history">
-<title>history</title>
-<literallayout>Type: number
-Default: 10</literallayout>
-
-<para>
-This variable controls the size (in number of strings remembered) of
-the string history buffer per category. The buffer is cleared each time the
-variable is set.
-</para>
-</sect2>
-
-<sect2 id="history-file">
-<title>history_file</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/.mutthistory</literal></quote></literallayout>
-
-<para>
-The file in which Mutt will save its history.
-</para>
-</sect2>
-
-<sect2 id="honor-followup-to">
-<title>honor_followup_to</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not a Mail-Followup-To header is
-honored when group-replying to a message.
-</para>
-</sect2>
-
-<sect2 id="hostname">
-<title>hostname</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Specifies the fully-qualified hostname of the system mutt is running on
-containing the host's name and the DNS domain it belongs to. It is used
-as the domain part (after <quote>@</quote>) for local email addresses as well as
-Message-Id headers.
-</para>
-<para>
-Its value is determined at startup as follows: If the node's name
-as returned by the <literal>uname(3)</literal> function contains the hostname and the
-domain, these are used to construct <link linkend="hostname">$hostname</link>. If there is no
-domain part returned, Mutt will look for a <quote>domain</quote> or <quote>search</quote>
-line in <literal>/etc/resolv.conf</literal> to determine the domain. Optionally, Mutt
-can be compiled with a fixed domain name in which case a detected
-one is not used.
-</para>
-<para>
-Also see <link linkend="use-domain">$use_domain</link> and <link linkend="hidden-host">$hidden_host</link>.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, the default for this variable is obtained
-from /etc/mailname when Mutt starts.
-</para>
-</sect2>
-
-<sect2 id="ignore-linear-white-space">
-<title>ignore_linear_white_space</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This option replaces linear-white-space between encoded-word
-and text to a single space to prevent the display of MIME-encoded
-<quote>Subject:</quote> field from being divided into multiple lines.
-</para>
-</sect2>
-
-<sect2 id="ignore-list-reply-to">
-<title>ignore_list_reply_to</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Affects the behaviour of the <literal><reply></literal> function when replying to
-messages from mailing lists (as defined by the <quote><link linkend="subscribe">subscribe</link></quote> or
-<quote><link linkend="lists">lists</link></quote> commands). When <emphasis>set</emphasis>, if the <quote>Reply-To:</quote> field is
-set to the same value as the <quote>To:</quote> field, Mutt assumes that the
-<quote>Reply-To:</quote> 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 <emphasis>set</emphasis>, use the <literal><link linkend="list-reply"><list-reply></link></literal>
-function; <literal><group-reply></literal> will reply to both the sender and the
-list.
-</para>
-</sect2>
-
-<sect2 id="imap-authenticators">
-<title>imap_authenticators</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an IMAP server, in the order mutt should
-try them. Authentication methods are either <quote>login</quote> or the right
-side of an IMAP <quote>AUTH=xxx</quote> capability string, eg <quote>digest-md5</quote>, <quote>gssapi</quote>
-or <quote>cram-md5</quote>. This option is case-insensitive. If it's
-<emphasis>unset</emphasis> (the default) mutt will try all available methods,
-in order from most-secure to least-secure.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set imap_authenticators="gssapi:cram-md5:login"
-
-</screen><para>
-<emphasis role="bold">Note:</emphasis> Mutt will only fall back to other authentication methods if
-the previous methods are unavailable. If a method is available but
-authentication fails, mutt will not connect to the IMAP server.
-</para>
-</sect2>
-
-<sect2 id="imap-check-subscribed">
-<title>imap_check_subscribed</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, 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 just as if you had issued individual <quote><link linkend="mailboxes">mailboxes</link></quote>
-commands.
-</para>
-</sect2>
-
-<sect2 id="imap-delim-chars">
-<title>imap_delim_chars</title>
-<literallayout>Type: string
-Default: <quote><literal>/.</literal></quote></literallayout>
-
-<para>
-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 <quote>=</quote> shortcut for your <emphasis>folder</emphasis> variable.
-</para>
-</sect2>
-
-<sect2 id="imap-headers">
-<title>imap_headers</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Mutt requests these header fields in addition to the default headers
-(<quote>Date:</quote>, <quote>From:</quote>, <quote>Subject:</quote>, <quote>To:</quote>, <quote>Cc:</quote>, <quote>Message-Id:</quote>,
-<quote>References:</quote>, <quote>Content-Type:</quote>, <quote>Content-Description:</quote>, <quote>In-Reply-To:</quote>,
-<quote>Reply-To:</quote>, <quote>Lines:</quote>, <quote>List-Post:</quote>, <quote>X-Label:</quote>) from IMAP
-servers before displaying the index menu. You may want to add more
-headers for spam detection.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> This is a space separated list, items should be uppercase
-and not contain the colon, e.g. <quote>X-BOGOSITY X-SPAM-STATUS</quote> for the
-<quote>X-Bogosity:</quote> and <quote>X-Spam-Status:</quote> header fields.
-</para>
-</sect2>
-
-<sect2 id="imap-idle">
-<title>imap_idle</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will attempt to use the IMAP IDLE extension
-to check for new mail in the current mailbox. Some servers
-(dovecot was the inspiration for this option) react badly
-to mutt's implementation. If your connection seems to freeze
-up periodically, try unsetting this.
-</para>
-</sect2>
-
-<sect2 id="imap-keepalive">
-<title>imap_keepalive</title>
-<literallayout>Type: number
-Default: 900</literallayout>
-
-<para>
-This variable specifies the maximum amount of time in seconds that mutt
-will wait before polling open IMAP connections, to prevent the server
-from closing them before mutt 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.
-</para>
-</sect2>
-
-<sect2 id="imap-list-subscribed">
-<title>imap_list_subscribed</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-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 <literal><toggle-subscribed></literal> function.
-</para>
-</sect2>
-
-<sect2 id="imap-login">
-<title>imap_login</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Your login name on the IMAP server.
-</para>
-<para>
-This variable defaults to the value of <link linkend="imap-user">$imap_user</link>.
-</para>
-</sect2>
-
-<sect2 id="imap-pass">
-<title>imap_pass</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Specifies the password for your IMAP account. If <emphasis>unset</emphasis>, Mutt will
-prompt you for your password when you invoke the <literal><link linkend="fetch-mail"><fetch-mail></link></literal> function
-or try to open an IMAP folder.
-</para>
-<para>
-<emphasis role="bold">Warning</emphasis>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</para>
-</sect2>
-
-<sect2 id="imap-passive">
-<title>imap_passive</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not open new IMAP connections to check for new
-mail. Mutt 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 invocation, or if opening the connection
-is slow.
-</para>
-</sect2>
-
-<sect2 id="imap-peek">
-<title>imap_peek</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt 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.
-</para>
-</sect2>
-
-<sect2 id="imap-pipeline-depth">
-<title>imap_pipeline_depth</title>
-<literallayout>Type: number
-Default: 15</literallayout>
-
-<para>
-Controls the number of IMAP commands that may be queued up before they
-are sent to the server. A deeper pipeline reduces the amount of time
-mutt must wait for the server, and can make IMAP servers feel much
-more responsive. But not all servers correctly handle pipelined commands,
-so if you have problems you might want to try setting this variable to 0.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> Changes to this variable have no effect on open connections.
-</para>
-</sect2>
-
-<sect2 id="imap-servernoise">
-<title>imap_servernoise</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt 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.
-</para>
-</sect2>
-
-<sect2 id="imap-user">
-<title>imap_user</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-The name of the user whose mail you intend to access on the IMAP
-server.
-</para>
-<para>
-This variable defaults to your user name on the local machine.
-</para>
-</sect2>
-
-<sect2 id="implicit-autoview">
-<title>implicit_autoview</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If set to <quote>yes</quote>, mutt will look for a mailcap entry with the
-<quote><literal>copiousoutput</literal></quote> flag set for <emphasis>every</emphasis> MIME attachment it doesn't have
-an internal viewer defined for. If such an entry is found, mutt will
-use the viewer defined in that entry to convert the body part to text
-form.
-</para>
-</sect2>
-
-<sect2 id="include">
-<title>include</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not a copy of the message(s) you are replying to
-is included in your reply.
-</para>
-</sect2>
-
-<sect2 id="include-onlyfirst">
-<title>include_onlyfirst</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Controls whether or not Mutt includes only the first attachment
-of the message you are replying.
-</para>
-</sect2>
-
-<sect2 id="indent-string">
-<title>indent_string</title>
-<literallayout>Type: string
-Default: <quote><literal>> </literal></quote></literallayout>
-
-<para>
-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.
-</para>
-<para>
-This option is a format string, please see the description of
-<link linkend="index-format">$index_format</link> for supported <literal>printf(3)</literal>-style sequences.
-</para>
-<para>
-Because for <literal>format=lowed</literal> style messages the quoting mechanism
-is strictly defined, this setting is ignored if <link linkend="text-flowed">$text_flowed</link> is
-<emphasis>set</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="index-format">
-<title>index_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s</literal></quote></literallayout>
-
-<para>
-This variable allows you to customize the message index display to
-your personal taste.
-</para>
-<para>
-<quote>Format strings</quote> are similar to the strings used in the C
-function <literal>printf(3)</literal> to format output (see the man page for more details).
-The following sequences are defined in Mutt:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%a </term>
-<listitem><para>address of the author
-</para></listitem></varlistentry>
-<varlistentry><term>%A </term>
-<listitem><para>reply-to address (if present; otherwise: address of author)
-</para></listitem></varlistentry>
-<varlistentry><term>%b </term>
-<listitem><para>filename of the original message folder (think mailbox)
-</para></listitem></varlistentry>
-<varlistentry><term>%B </term>
-<listitem><para>the list to which the letter was sent, or else the folder name (%b).
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>number of characters (bytes) in the message
-</para></listitem></varlistentry>
-<varlistentry><term>%C </term>
-<listitem><para>current message number
-</para></listitem></varlistentry>
-<varlistentry><term>%d </term>
-<listitem><para>date and time of the message in the format specified by
-<link linkend="date-format">$date_format</link> converted to sender's time zone
-</para></listitem></varlistentry>
-<varlistentry><term>%D </term>
-<listitem><para>date and time of the message in the format specified by
-<link linkend="date-format">$date_format</link> converted to the local time zone
-</para></listitem></varlistentry>
-<varlistentry><term>%e </term>
-<listitem><para>current message number in thread
-</para></listitem></varlistentry>
-<varlistentry><term>%E </term>
-<listitem><para>number of messages in current thread
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>sender (address + real name), either From: or Return-Path:
-</para></listitem></varlistentry>
-<varlistentry><term>%F </term>
-<listitem><para>author name, or recipient name if the message is from you
-</para></listitem></varlistentry>
-<varlistentry><term>%H </term>
-<listitem><para>spam attribute(s) of this message
-</para></listitem></varlistentry>
-<varlistentry><term>%i </term>
-<listitem><para>message-id of the current message
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>number of lines in the message (does not work with maildir,
-mh, and possibly IMAP folders)
-</para></listitem></varlistentry>
-<varlistentry><term>%L </term>
-<listitem><para>If an address in the <quote>To:</quote> or <quote>Cc:</quote> header field matches an address
-defined by the users <quote><link linkend="subscribe">subscribe</link></quote> command, this displays
-"To <list-name>", otherwise the same as %F.
-</para></listitem></varlistentry>
-<varlistentry><term>%m </term>
-<listitem><para>total number of message in the mailbox
-</para></listitem></varlistentry>
-<varlistentry><term>%M </term>
-<listitem><para>number of hidden messages if the thread is collapsed.
-</para></listitem></varlistentry>
-<varlistentry><term>%N </term>
-<listitem><para>message score
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>author's real name (or address if missing)
-</para></listitem></varlistentry>
-<varlistentry><term>%O </term>
-<listitem><para>original save folder where mutt would formerly have
-stashed the message: list name or recipient name
-if not sent to a list
-</para></listitem></varlistentry>
-<varlistentry><term>%P </term>
-<listitem><para>progress indicator for the builtin pager (how much of the file has been displayed)
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>subject of the message
-</para></listitem></varlistentry>
-<varlistentry><term>%S </term>
-<listitem><para>status of the message (<quote>N</quote>/<quote>D</quote>/<quote>d</quote>/<quote>!</quote>/<quote>r</quote>/*)
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para><quote>To:</quote> field (recipients)
-</para></listitem></varlistentry>
-<varlistentry><term>%T </term>
-<listitem><para>the appropriate character from the <link linkend="to-chars">$to_chars</link> string
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>user (login) name of the author
-</para></listitem></varlistentry>
-<varlistentry><term>%v </term>
-<listitem><para>first name of the author, or the recipient if the message is from you
-</para></listitem></varlistentry>
-<varlistentry><term>%X </term>
-<listitem><para>number of attachments
-(please see the <quote><link linkend="attachments">attachments</link></quote> section for possible speed effects)
-</para></listitem></varlistentry>
-<varlistentry><term>%y </term>
-<listitem><para><quote>X-Label:</quote> field, if present
-</para></listitem></varlistentry>
-<varlistentry><term>%Y </term>
-<listitem><para><quote>X-Label:</quote> field, if present, and <emphasis>(1)</emphasis> not at part of a thread tree,
-<emphasis>(2)</emphasis> at the top of a thread, or <emphasis>(3)</emphasis> <quote>X-Label:</quote> is different from
-preceding message's <quote>X-Label:</quote>.
-</para></listitem></varlistentry>
-<varlistentry><term>%Z </term>
-<listitem><para>message status flags
-</para></listitem></varlistentry>
-<varlistentry><term>%{fmt} </term>
-<listitem><para>the date and time of the message is converted to sender's
-time zone, and <quote>fmt</quote> is expanded by the library function
-<literal>strftime(3)</literal>; a leading bang disables locales
-</para></listitem></varlistentry>
-<varlistentry><term>%[fmt] </term>
-<listitem><para>the date and time of the message is converted to the local
-time zone, and <quote>fmt</quote> is expanded by the library function
-<literal>strftime(3)</literal>; a leading bang disables locales
-</para></listitem></varlistentry>
-<varlistentry><term>%(fmt) </term>
-<listitem><para>the local date and time when the message was received.
-<quote>fmt</quote> is expanded by the library function <literal>strftime(3)</literal>;
-a leading bang disables locales
-</para></listitem></varlistentry>
-<varlistentry><term>%<fmt> </term>
-<listitem><para>the current local time. <quote>fmt</quote> is expanded by the library
-function <literal>strftime(3)</literal>; a leading bang disables locales.
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-<quote>Soft-fill</quote> deserves some explanation: Normal right-justification
-will print everything to the left of the <quote>%></quote>, displaying padding and
-whatever lies to the right only if there's room. By contrast,
-soft-fill gives priority to the right-hand side, guaranteeing space
-to display it and showing padding only if there's still room. If
-necessary, soft-fill will eat text leftwards to make room for
-rightward text.
-</para>
-<para>
-Note that these expandos are supported in
-<quote><link linkend="save-hook">save-hook</link></quote>, <quote><link linkend="fcc-hook">fcc-hook</link></quote> and <quote><link linkend="fcc-save-hook">fcc-save-hook</link></quote>, too.
-</para>
-</sect2>
-
-<sect2 id="ispell">
-<title>ispell</title>
-<literallayout>Type: path
-Default: <quote><literal>ispell</literal></quote></literallayout>
-
-<para>
-How to invoke ispell (GNU's spell-checking software).
-</para>
-</sect2>
-
-<sect2 id="keep-flagged">
-<title>keep_flagged</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, read messages marked as flagged will not be moved
-from your spool mailbox to your <link linkend="mbox">$mbox</link> mailbox, or as a result of
-a <quote><link linkend="mbox-hook">mbox-hook</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="locale">
-<title>locale</title>
-<literallayout>Type: string
-Default: <quote><literal>C</literal></quote></literallayout>
-
-<para>
-The locale used by <literal>strftime(3)</literal> to format dates. Legal values are
-the strings your system accepts for the locale environment variable <literal>$LC_TIME</literal>.
-</para>
-</sect2>
-
-<sect2 id="mail-check">
-<title>mail_check</title>
-<literallayout>Type: number
-Default: 5</literallayout>
-
-<para>
-This variable configures how often (in seconds) mutt should look for
-new mail. Also see the <link linkend="timeout">$timeout</link> variable.
-</para>
-</sect2>
-
-<sect2 id="mailcap-path">
-<title>mailcap_path</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This variable specifies which files to consult when attempting to
-display MIME bodies not directly supported by Mutt.
-</para>
-</sect2>
-
-<sect2 id="mailcap-sanitize">
-<title>mailcap_sanitize</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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.
-</para>
-<para>
-<emphasis role="bold">DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
-DOING!</emphasis>
-</para>
-</sect2>
-
-<sect2 id="maildir-mtime">
-<title>maildir_mtime</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If set, the sort-by-date option in the browser will sort maildirs
-smartly, not using the mtime of the maildir itself but that of the
-newest message in the new subdirectory, making the sorting by
-reverse date much more useful. People with maildirs over NFS may
-wish to leave this option unset.
-</para>
-</sect2>
-
-<sect2 id="header-cache">
-<title>header_cache</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is <emphasis>unset</emphasis> so no header
-caching will be used.
-</para>
-<para>
-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see <quote><link linkend="caching">caching</link></quote> for details.
-</para>
-</sect2>
-
-<sect2 id="maildir-header-cache-verify">
-<title>maildir_header_cache_verify</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Check for Maildir unaware programs other than mutt having modified maildir
-files when the header cache is in use. This incurs one <literal>stat(2)</literal> per
-message every time the folder is opened (which can be very slow for NFS
-folders).
-</para>
-</sect2>
-
-<sect2 id="header-cache-pagesize">
-<title>header_cache_pagesize</title>
-<literallayout>Type: string
-Default: <quote><literal>16384</literal></quote></literallayout>
-
-<para>
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-</para>
-</sect2>
-
-<sect2 id="maildir-trash">
-<title>maildir_trash</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, messages marked as deleted will be saved with the maildir
-trashed flag instead of unlinked. <emphasis role="bold">Note:</emphasis> this only applies
-to maildir-style mailboxes. Setting it will have no effect on other
-mailbox types.
-</para>
-</sect2>
-
-<sect2 id="mark-old">
-<title>mark_old</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether or not mutt marks <emphasis>new</emphasis> <emphasis role="bold">unread</emphasis>
-messages as <emphasis>old</emphasis> if you exit a mailbox without reading them.
-With this option <emphasis>set</emphasis>, the next time you start mutt, the messages
-will show up with an <quote>O</quote> next to them in the index menu,
-indicating that they are old.
-</para>
-</sect2>
-
-<sect2 id="markers">
-<title>markers</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls the display of wrapped lines in the internal pager. If set, a
-<quote>+</quote> marker is displayed at the beginning of wrapped lines.
-</para>
-<para>
-Also see the <link linkend="smart-wrap">$smart_wrap</link> variable.
-</para>
-</sect2>
-
-<sect2 id="mask">
-<title>mask</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>!ˆ\.[ˆ.]</literal></quote></literallayout>
-
-<para>
-A regular expression used in the file browser, optionally preceded by
-the <emphasis>not</emphasis> operator <quote>!</quote>. Only files whose names match this mask
-will be shown. The match is always case-sensitive.
-</para>
-</sect2>
-
-<sect2 id="mbox">
-<title>mbox</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/mbox</literal></quote></literallayout>
-
-<para>
-This specifies the folder into which read mail in your <link linkend="spoolfile">$spoolfile</link>
-folder will be appended.
-</para>
-<para>
-Also see the <link linkend="move">$move</link> variable.
-</para>
-</sect2>
-
-<sect2 id="mbox-type">
-<title>mbox_type</title>
-<literallayout>Type: folder magic
-Default: mbox</literallayout>
-
-<para>
-The default mailbox type used when creating new folders. May be any of
-<quote>mbox</quote>, <quote>MMDF</quote>, <quote>MH</quote> and <quote>Maildir</quote>.
-</para>
-</sect2>
-
-<sect2 id="metoo">
-<title>metoo</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>unset</emphasis>, Mutt will remove your address (see the <quote><link linkend="alternates">alternates</link></quote>
-command) from the list of recipients when replying to a message.
-</para>
-</sect2>
-
-<sect2 id="menu-context">
-<title>menu_context</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to <link linkend="pager-context">$pager_context</link>.)
-</para>
-</sect2>
-
-<sect2 id="menu-move-off">
-<title>menu_move_off</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, the bottom entry of menus will never scroll up past
-the bottom of the screen, unless there are less entries than lines.
-When <emphasis>set</emphasis>, the bottom entry may move off the bottom.
-</para>
-</sect2>
-
-<sect2 id="menu-scroll">
-<title>menu_scroll</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, menus will be scrolled up or down one line when you
-attempt to move across a screen boundary. If <emphasis>unset</emphasis>, the screen
-is cleared and the next or previous page of the menu is displayed
-(useful for slow links to avoid many redraws).
-</para>
-</sect2>
-
-<sect2 id="meta-key">
-<title>meta_key</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, forces Mutt 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 <literal>0xf8</literal>, then this is treated as if the user had
-pressed Esc then <quote>x</quote>. This is because the result of removing the
-high bit from <literal>0xf8</literal> is <literal>0x78</literal>, which is the ASCII character
-<quote>x</quote>.
-</para>
-</sect2>
-
-<sect2 id="mh-purge">
-<title>mh_purge</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, mutt will mimic mh's behaviour and rename deleted messages
-to <emphasis>,<old file name></emphasis> in mh folders instead of really deleting
-them. This leaves the message on disk but makes programs reading the folder
-ignore it. If the variable is <emphasis>set</emphasis>, the message files will simply be
-deleted.
-</para>
-<para>
-This option is similar to <link linkend="maildir-trash">$maildir_trash</link> for Maildir folders.
-</para>
-</sect2>
-
-<sect2 id="mh-seq-flagged">
-<title>mh_seq_flagged</title>
-<literallayout>Type: string
-Default: <quote><literal>flagged</literal></quote></literallayout>
-
-<para>
-The name of the MH sequence used for flagged messages.
-</para>
-</sect2>
-
-<sect2 id="mh-seq-replied">
-<title>mh_seq_replied</title>
-<literallayout>Type: string
-Default: <quote><literal>replied</literal></quote></literallayout>
-
-<para>
-The name of the MH sequence used to tag replied messages.
-</para>
-</sect2>
-
-<sect2 id="mh-seq-unseen">
-<title>mh_seq_unseen</title>
-<literallayout>Type: string
-Default: <quote><literal>unseen</literal></quote></literallayout>
-
-<para>
-The name of the MH sequence used for unseen messages.
-</para>
-</sect2>
-
-<sect2 id="mime-forward">
-<title>mime_forward</title>
-<literallayout>Type: quadoption
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the message you are forwarding will be attached as a
-separate <literal>message/rfc822</literal> 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 <quote>ask-no</quote> or <quote>ask-yes</quote>.
-</para>
-<para>
-Also see <link linkend="forward-decode">$forward_decode</link> and <link linkend="mime-forward-decode">$mime_forward_decode</link>.
-</para>
-</sect2>
-
-<sect2 id="mime-forward-decode">
-<title>mime_forward_decode</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Controls the decoding of complex MIME messages into <literal>text/plain</literal> when
-forwarding a message while <link linkend="mime-forward">$mime_forward</link> is <emphasis>set</emphasis>. Otherwise
-<link linkend="forward-decode">$forward_decode</link> is used instead.
-</para>
-</sect2>
-
-<sect2 id="mime-forward-rest">
-<title>mime_forward_rest</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-When forwarding multiple attachments of a MIME message from the attachment
-menu, attachments which cannot be decoded in a reasonable manner will
-be attached to the newly composed message if this option is <emphasis>set</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="mix-entry-format">
-<title>mix_entry_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4n %c %-16s %a</literal></quote></literallayout>
-
-<para>
-This variable describes the format of a remailer line on the mixmaster
-chain selection screen. The following <literal>printf(3)</literal>-like sequences are
-supported:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%n </term>
-<listitem><para>The running number on the menu.
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>Remailer capabilities.
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>The remailer's short name.
-</para></listitem></varlistentry>
-<varlistentry><term>%a </term>
-<listitem><para>The remailer's e-mail address.
-</para></listitem></varlistentry></variablelist>
-</sect2>
-
-<sect2 id="mixmaster">
-<title>mixmaster</title>
-<literallayout>Type: path
-Default: <quote><literal>mixmaster</literal></quote></literallayout>
-
-<para>
-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.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this option is set by default to
-<quote>mixmaster-filter</quote> in /etc/Muttrc.
-</para>
-</sect2>
-
-<sect2 id="move">
-<title>move</title>
-<literallayout>Type: quadoption
-Default: no</literallayout>
-
-<para>
-Controls whether or not Mutt will move read messages
-from your spool mailbox to your <link linkend="mbox">$mbox</link> mailbox, or as a result of
-a <quote><link linkend="mbox-hook">mbox-hook</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="message-cachedir">
-<title>message_cachedir</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-</para>
-<para>
-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-</para>
-<para>
-Also see the <link linkend="message-cache-clean">$message_cache_clean</link> variable.
-</para>
-</sect2>
-
-<sect2 id="message-cache-clean">
-<title>message_cache_clean</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-</para>
-</sect2>
-
-<sect2 id="message-format">
-<title>message_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%s</literal></quote></literallayout>
-
-<para>
-This is the string displayed in the <quote>attachment</quote> menu for
-attachments of type <literal>message/rfc822</literal>. For a full listing of defined
-<literal>printf(3)</literal>-like sequences see the section on <link linkend="index-format">$index_format</link>.
-</para>
-</sect2>
-
-<sect2 id="narrow-tree">
-<title>narrow_tree</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable, when <emphasis>set</emphasis>, makes the thread tree narrower, allowing
-deeper threads to fit on the screen.
-</para>
-</sect2>
-
-<sect2 id="net-inc">
-<title>net_inc</title>
-<literallayout>Type: number
-Default: 10</literallayout>
-
-<para>
-Operations that expect to transfer a large amount of data over the
-network will update their progress every <link linkend="net-inc">$net_inc</link> kilobytes.
-If set to 0, no progress messages will be displayed.
-</para>
-<para>
-See also <link linkend="read-inc">$read_inc</link>, <link linkend="write-inc">$write_inc</link> and <link linkend="net-inc">$net_inc</link>.
-</para>
-</sect2>
-
-<sect2 id="pager">
-<title>pager</title>
-<literallayout>Type: path
-Default: <quote><literal>builtin</literal></quote></literallayout>
-
-<para>
-This variable specifies which pager you would like to use to view
-messages. The value <quote>builtin</quote> means to use the builtin pager, otherwise this
-variable should specify the pathname of the external pager you would
-like to use.
-</para>
-<para>
-Using an external pager may have some disadvantages: Additional
-keystrokes are necessary because you can't call mutt functions
-directly from the pager, and screen resizes cause lines longer than
-the screen width to be badly formatted in the help menu.
-</para>
-</sect2>
-
-<sect2 id="pager-context">
-<title>pager_context</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-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 will display the line after the last one on the screen
-at the top of the next page (0 lines of context).
-</para>
-</sect2>
-
-<sect2 id="pager-format">
-<title>pager_format</title>
-<literallayout>Type: string
-Default: <quote><literal>-%Z- %C/%m: %-20.20n %s%* -- (%P)</literal></quote></literallayout>
-
-<para>
-This variable controls the format of the one-line message <quote>status</quote>
-displayed before each message in either the internal or an external
-pager. The valid sequences are listed in the <link linkend="index-format">$index_format</link>
-section.
-</para>
-</sect2>
-
-<sect2 id="pager-index-lines">
-<title>pager_index_lines</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-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 setting 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 <link linkend="pager-index-lines">$pager_index_lines</link>, then the index will only use as
-many lines as it needs.
-</para>
-</sect2>
-
-<sect2 id="pager-stop">
-<title>pager_stop</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the internal-pager will <emphasis role="bold">not</emphasis> move to the next message
-when you are at the end of a message and invoke the <literal><next-page></literal>
-function.
-</para>
-</sect2>
-
-<sect2 id="crypt-autosign">
-<title>crypt_autosign</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Setting this variable will cause Mutt 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 <link linkend="smime-is-default">$smime_is_default</link> is <emphasis>set</emphasis>,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="crypt-autoencrypt">
-<title>crypt_autoencrypt</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages. This is probably only useful in
-connection to the <quote><link linkend="send-hook">send-hook</link></quote> command. It can be overridden
-by use of the pgp menu, when encryption is not required or
-signing is requested as well. If <link linkend="smime-is-default">$smime_is_default</link> is <emphasis>set</emphasis>,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="pgp-ignore-subkeys">
-<title>pgp_ignore_subkeys</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities. <emphasis>Unset</emphasis> this
-if you want to play interesting key selection games.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="crypt-replyencrypt">
-<title>crypt_replyencrypt</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="crypt-replysign">
-<title>crypt_replysign</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, automatically PGP or OpenSSL sign replies to messages which are
-signed.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> this does not work on messages that are encrypted
-<emphasis>and</emphasis> signed!
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="crypt-replysignencrypted">
-<title>crypt_replysignencrypted</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, automatically PGP or OpenSSL sign replies to messages
-which are encrypted. This makes sense in combination with
-<link linkend="crypt-replyencrypt">$crypt_replyencrypt</link>, because it allows you to sign all
-messages which are automatically encrypted. This works around
-the problem noted in <link linkend="crypt-replysign">$crypt_replysign</link>, that mutt is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="crypt-timestamp">
-<title>crypt_timestamp</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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 <emphasis>unset</emphasis> this setting.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="sidebar-delim">
-<title>sidebar_delim</title>
-<literallayout>Type: string
-Default: <quote><literal>|</literal></quote></literallayout>
-
-<para>
-This specifies the delimiter between the sidebar (if visible) and
-other screens.
-</para>
-</sect2>
-
-<sect2 id="sidebar-visible">
-<title>sidebar_visible</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This specifies whether or not to show sidebar (left-side list of folders).
-</para>
-</sect2>
-
-<sect2 id="sidebar-width">
-<title>sidebar_width</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-The width of the sidebar.
-</para>
-</sect2>
-
-<sect2 id="pgp-use-gpg-agent">
-<title>pgp_use_gpg_agent</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt will use a possibly-running <literal>gpg-agent(1)</literal> process.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="crypt-verify-sig">
-<title>crypt_verify_sig</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-If <emphasis><quote>yes</quote></emphasis>, always attempt to verify PGP or S/MIME signatures.
-If <emphasis><quote>ask-*</quote></emphasis>, ask whether or not to verify the signature.
-If \Fi<quote>no</quote>, never attempt to verify cryptographic signatures.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="smime-is-default">
-<title>smime_is_default</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-The default behaviour of mutt is to use PGP on all auto-sign/encryption
-operations. To override and to use OpenSSL instead this must be <emphasis>set</emphasis>.
-However, this has no effect while replying, since mutt will automatically
-select the same application that was used to sign/encrypt the original
-message. (Note that this variable can be overridden by unsetting <link linkend="crypt-autosmime">$crypt_autosmime</link>.)
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-ask-cert-label">
-<title>smime_ask_cert_label</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-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
-<emphasis>set</emphasis> by default.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-decrypt-use-default-key">
-<title>smime_decrypt_use_default_key</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis> (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate-key-pairs, mutt 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)
-</para>
-</sect2>
-
-<sect2 id="pgp-entry-format">
-<title>pgp_entry_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4n %t%f %4l/0x%k %-4a %2c %u</literal></quote></literallayout>
-
-<para>
-This variable allows you to customize the PGP key selection menu to
-your personal taste. This string is similar to <link linkend="index-format">$index_format</link>, but
-has its own set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%n </term>
-<listitem><para>number
-</para></listitem></varlistentry>
-<varlistentry><term>%k </term>
-<listitem><para>key id
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>user id
-</para></listitem></varlistentry>
-<varlistentry><term>%a </term>
-<listitem><para>algorithm
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>key length
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>flags
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>capabilities
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para>trust/validity of the key-uid association
-</para></listitem></varlistentry>
-<varlistentry><term>%[<s>] </term>
-<listitem><para>date of the key where <s> is an <literal>strftime(3)</literal> expression
-</para></listitem></varlistentry></variablelist>
-
-<para>
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-good-sign">
-<title>pgp_good_sign</title>
-<literallayout>Type: regular expression
-Default: (empty)</literallayout>
-
-<para>
-If you assign a text to this variable, then a PGP signature is only
-considered verified if the output from <link linkend="pgp-verify-command">$pgp_verify_command</link> contains
-the text. Use this variable if the exit code from the command is 0
-even for bad signatures.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-check-exit">
-<title>pgp_check_exit</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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)
-</para>
-</sect2>
-
-<sect2 id="pgp-long-ids">
-<title>pgp_long_ids</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, use 64 bit PGP key IDs, if <emphasis>unset</emphasis> use the normal 32 bit key IDs.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-retainable-sigs">
-<title>pgp_retainable_sigs</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, signed and encrypted messages will consist of nested
-<literal>multipart/signed</literal> and <literal>multipart/encrypted</literal> body parts.
-</para>
-<para>
-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (<literal>multipart/encrypted</literal>) can be easily
-removed, while the inner <literal>multipart/signed</literal> part is retained.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-autoinline">
-<title>pgp_autoinline</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This option controls whether Mutt 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.
-</para>
-<para>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</para>
-<para>
-Also see the <link linkend="pgp-mime-auto">$pgp_mime_auto</link> variable.
-</para>
-<para>
-Also note that using the old-style PGP message format is <emphasis role="bold">strongly</emphasis>
-<emphasis role="bold">deprecated</emphasis>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-replyinline">
-<title>pgp_replyinline</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Setting this variable will cause Mutt 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
-internals for previously checked/flagged messages.
-</para>
-<para>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</para>
-<para>
-Also see the <link linkend="pgp-mime-auto">$pgp_mime_auto</link> variable.
-</para>
-<para>
-Also note that using the old-style PGP message format is <emphasis role="bold">strongly</emphasis>
-<emphasis role="bold">deprecated</emphasis>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-show-unusable">
-<title>pgp_show_unusable</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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 <quote>disabled</quote> by the user.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-sign-as">
-<title>pgp_sign_as</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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. <literal>0x00112233</literal>).
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-strict-enc">
-<title>pgp_strict_enc</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt 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)
-</para>
-</sect2>
-
-<sect2 id="pgp-timeout">
-<title>pgp_timeout</title>
-<literallayout>Type: number
-Default: 300</literallayout>
-
-<para>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-sort-keys">
-<title>pgp_sort_keys</title>
-<literallayout>Type: sort order
-Default: address</literallayout>
-
-<para>
-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-
-</para>
-
-<variablelist>
-<varlistentry><term>address </term>
-<listitem><para>sort alphabetically by user id
-</para></listitem></varlistentry>
-<varlistentry><term>keyid </term>
-<listitem><para>sort alphabetically by key id
-</para></listitem></varlistentry>
-<varlistentry><term>date </term>
-<listitem><para>sort by key creation date
-</para></listitem></varlistentry>
-<varlistentry><term>trust </term>
-<listitem><para>sort by the trust of the key
-</para></listitem></varlistentry></variablelist>
-
-<para>
-If you prefer reverse order of the above values, prefix it with
-<quote>reverse-</quote>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-mime-auto">
-<title>pgp_mime_auto</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-</para>
-<para>
-Also note that using the old-style PGP message format is <emphasis role="bold">strongly</emphasis>
-<emphasis role="bold">deprecated</emphasis>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-auto-decode">
-<title>pgp_auto_decode</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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 <literal><link linkend="check-traditional-pgp"><check-traditional-pgp></link></literal> function, mutt will automatically
-check the message for traditional pgp.
-</para>
-</sect2>
-
-<sect2 id="pgp-mime-signature-filename">
-<title>pgp_mime_signature_filename</title>
-<literallayout>Type: string
-Default: <quote><literal>signature.asc</literal></quote></literallayout>
-
-<para>
-This option sets the filename used for signature parts in PGP/MIME
-signed messages.
-</para>
-</sect2>
-
-<sect2 id="pgp-mime-signature-description">
-<title>pgp_mime_signature_description</title>
-<literallayout>Type: string
-Default: <quote><literal>Digital signature</literal></quote></literallayout>
-
-<para>
-This option sets the Content-Description used for signature parts in
-PGP/MIME signed messages.
-</para>
-</sect2>
-
-<sect2 id="pgp-decode-command">
-<title>pgp_decode_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This format strings specifies a command which is used to decode
-application/pgp attachments.
-</para>
-<para>
-The PGP command formats have their own set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%p </term>
-<listitem><para>Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-string otherwise. Note: This may be used with a %? construct.
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>Expands to the name of a file containing a message.
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>Expands to the name of a file containing the signature part
- of a <literal>multipart/signed</literal> attachment when verifying it.
-</para></listitem></varlistentry>
-<varlistentry><term>%a </term>
-<listitem><para>The value of <link linkend="pgp-sign-as">$pgp_sign_as</link>.
-</para></listitem></varlistentry>
-<varlistentry><term>%r </term>
-<listitem><para>One or more key IDs.
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For examples on how to configure these formats for the various versions
-of PGP which are floating around, see the pgp and gpg sample configuration files in
-the <literal>samples/</literal> subdirectory which has been installed on your system
-alongside the documentation.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-getkeys-command">
-<title>pgp_getkeys_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by <link linkend="pgp-decode-command">$pgp_decode_command</link>, %r is the only
-<literal>printf(3)</literal>-like sequence used with this format.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-verify-command">
-<title>pgp_verify_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to verify PGP signatures.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-decrypt-command">
-<title>pgp_decrypt_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to decrypt a PGP encrypted message.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-clearsign-command">
-<title>pgp_clearsign_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This format is used to create an old-style <quote>clearsigned</quote> PGP
-message. Note that the use of this format is <emphasis role="bold">strongly</emphasis>
-<emphasis role="bold">deprecated</emphasis>.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-sign-command">
-<title>pgp_sign_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to create the detached PGP signature for a
-<literal>multipart/signed</literal> PGP/MIME body part.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-encrypt-sign-command">
-<title>pgp_encrypt_sign_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to both sign and encrypt a body part.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-encrypt-only-command">
-<title>pgp_encrypt_only_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to encrypt a body part without signing it.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-import-command">
-<title>pgp_import_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to import a key from a message into
-the user's public key ring.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-export-command">
-<title>pgp_export_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to export a public key from the user's
-key ring.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-verify-key-command">
-<title>pgp_verify_key_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to verify key information from the key selection
-menu.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-list-secring-command">
-<title>pgp_list_secring_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to list the secret key ring's contents. The
-output format must be analogous to the one used by:
-
-</para>
-
-<screen>
-gpg --list-keys --with-colons.
-
-</screen><para>
-This format is also generated by the <literal>pgpring</literal> utility which comes
-with mutt.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-list-pubring-command">
-<title>pgp_list_pubring_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to list the public key ring's contents. The
-output format must be analogous to the one used by
-
-</para>
-
-<screen>
-gpg --list-keys --with-colons.
-
-</screen><para>
-This format is also generated by the <literal>pgpring</literal> utility which comes
-with mutt.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="forward-decrypt">
-<title>forward_decrypt</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls the handling of encrypted messages when forwarding a message.
-When <emphasis>set</emphasis>, the outer layer of encryption is stripped off. This
-variable is only used if <link linkend="mime-forward">$mime_forward</link> is <emphasis>set</emphasis> and
-<link linkend="mime-forward-decode">$mime_forward_decode</link> is <emphasis>unset</emphasis>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="smime-timeout">
-<title>smime_timeout</title>
-<literallayout>Type: number
-Default: 300</literallayout>
-
-<para>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-encrypt-with">
-<title>smime_encrypt_with</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This sets the algorithm that should be used for encryption.
-Valid choices are <quote>des</quote>, <quote>des3</quote>, <quote>rc2-40</quote>, <quote>rc2-64</quote>, <quote>rc2-128</quote>.
-If <emphasis>unset</emphasis>, <quote>3des</quote> (TripleDES) is used.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-keys">
-<title>smime_keys</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and 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 option points to the location of the private keys.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-ca-location">
-<title>smime_ca_location</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this defaults to the first existing file in
-the following list: ˜/.smime/ca-certificates.crt ˜/.smime/ca-bundle.crt
-/etc/ssl/certs/ca-certificates.crt.
-</para>
-</sect2>
-
-<sect2 id="smime-certificates">
-<title>smime_certificates</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-the location of the certificates.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-decrypt-command">
-<title>smime_decrypt_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This format string specifies a command which is used to decrypt
-<literal>application/x-pkcs7-mime</literal> attachments.
-</para>
-<para>
-The OpenSSL command formats have their own set of <literal>printf(3)</literal>-like sequences
-similar to PGP's:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%f </term>
-<listitem><para>Expands to the name of a file containing a message.
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>Expands to the name of a file containing the signature part
- of a <literal>multipart/signed</literal> attachment when verifying it.
-</para></listitem></varlistentry>
-<varlistentry><term>%k </term>
-<listitem><para>The key-pair specified with <link linkend="smime-default-key">$smime_default_key</link>
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>One or more certificate IDs.
-</para></listitem></varlistentry>
-<varlistentry><term>%a </term>
-<listitem><para>The algorithm used for encryption.
-</para></listitem></varlistentry>
-<varlistentry><term>%C </term>
-<listitem><para>CA location: Depending on whether <link linkend="smime-ca-location">$smime_ca_location</link>
- points to a directory or file, this expands to
- <quote>-CApath <link linkend="smime-ca-location">$smime_ca_location</link></quote> or <quote>-CAfile <link linkend="smime-ca-location">$smime_ca_location</link></quote>.
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For examples on how to configure these formats, see the <literal>smime.rc</literal> in
-the <literal>samples/</literal> subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-verify-command">
-<title>smime_verify_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to verify S/MIME signatures of type <literal>multipart/signed</literal>.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-verify-opaque-command">
-<title>smime_verify_opaque_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to verify S/MIME signatures of type
-<literal>application/x-pkcs7-mime</literal>.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-sign-command">
-<title>smime_sign_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to created S/MIME signatures of type
-<literal>multipart/signed</literal>, which can be read by all mail clients.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-sign-opaque-command">
-<title>smime_sign_opaque_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to created S/MIME signatures of type
-<literal>application/x-pkcs7-signature</literal>, which can only be handled by mail
-clients supporting the S/MIME extension.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-encrypt-command">
-<title>smime_encrypt_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to create encrypted S/MIME messages.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-pk7out-command">
-<title>smime_pk7out_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-get-cert-command">
-<title>smime_get_cert_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to extract X509 certificates from a PKCS7 structure.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-get-signer-cert-command">
-<title>smime_get_signer_cert_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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 <quote>From:</quote> field.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-import-cert-command">
-<title>smime_import_cert_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to import a certificate via smime_keys.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-get-cert-email-command">
-<title>smime_get_cert_email_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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).
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-default-key">
-<title>smime_default_key</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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)
-</para>
-</sect2>
-
-<sect2 id="ssl-client-cert">
-<title>ssl_client_cert</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-The file containing a client certificate and its associated private
-key.
-</para>
-</sect2>
-
-<sect2 id="ssl-force-tls">
-<title>ssl_force_tls</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If this variable is <emphasis>set</emphasis>, Mutt 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 <link linkend="ssl-starttls">$ssl_starttls</link>.
-</para>
-</sect2>
-
-<sect2 id="ssl-starttls">
-<title>ssl_starttls</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis> (the default), mutt will attempt to use <literal>STARTTLS</literal> on servers
-advertising the capability. When <emphasis>unset</emphasis>, mutt will not attempt to
-use <literal>STARTTLS</literal> regardless of the server's capabilities.
-</para>
-</sect2>
-
-<sect2 id="certificate-file">
-<title>certificate_file</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/.mutt_certificates</literal></quote></literallayout>
-
-<para>
-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.
-</para>
-<para>
-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set certificate_file=~/.mutt/certificates
-
-</screen></sect2>
-
-<sect2 id="ssl-use-sslv3">
-<title>ssl_use_sslv3</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-</para>
-</sect2>
-
-<sect2 id="ssl-use-tlsv1">
-<title>ssl_use_tlsv1</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-</para>
-</sect2>
-
-<sect2 id="ssl-min-dh-prime-bits">
-<title>ssl_min_dh_prime_bits</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-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.
-</para>
-</sect2>
-
-<sect2 id="ssl-ca-certificates-file">
-<title>ssl_ca_certificates_file</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-</screen><para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this variable defaults to the example
-mentioned. This file is managed by the <quote>ca-certificates</quote> package.
-</para>
-</sect2>
-
-<sect2 id="pipe-split">
-<title>pipe_split</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Used in connection with the <literal><pipe-message></literal> function following
-<literal><tag-prefix></literal>. If this variable is <emphasis>unset</emphasis>, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated. When <emphasis>set</emphasis>, Mutt will pipe the messages one by one.
-In both cases the messages are piped in the current sorted order,
-and the <link linkend="pipe-sep">$pipe_sep</link> separator is added after each message.
-</para>
-</sect2>
-
-<sect2 id="pipe-decode">
-<title>pipe_decode</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Used in connection with the <literal><pipe-message></literal> command. When <emphasis>unset</emphasis>,
-Mutt will pipe the messages without any preprocessing. When <emphasis>set</emphasis>, Mutt
-will weed headers and will attempt to decode the messages
-first.
-</para>
-</sect2>
-
-<sect2 id="pipe-sep">
-<title>pipe_sep</title>
-<literallayout>Type: string
-Default: <quote><literal>\n</literal></quote></literallayout>
-
-<para>
-The separator to add between messages when piping a list of tagged
-messages to an external Unix command.
-</para>
-</sect2>
-
-<sect2 id="pop-authenticators">
-<title>pop_authenticators</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an POP server, in the order mutt should
-try them. Authentication methods are either <quote>user</quote>, <quote>apop</quote> or any
-SASL mechanism, eg <quote>digest-md5</quote>, <quote>gssapi</quote> or <quote>cram-md5</quote>.
-This option is case-insensitive. If this option is <emphasis>unset</emphasis>
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set pop_authenticators="digest-md5:apop:user"
-
-</screen></sect2>
-
-<sect2 id="pop-auth-try-all">
-<title>pop_auth_try_all</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will try all available authentication methods.
-When <emphasis>unset</emphasis>, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-</para>
-</sect2>
-
-<sect2 id="pop-checkinterval">
-<title>pop_checkinterval</title>
-<literallayout>Type: number
-Default: 60</literallayout>
-
-<para>
-This variable configures how often (in seconds) mutt should look for
-new mail in the currently selected mailbox if it is a POP mailbox.
-</para>
-</sect2>
-
-<sect2 id="pop-delete">
-<title>pop_delete</title>
-<literallayout>Type: quadoption
-Default: ask-no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will delete successfully downloaded messages from the POP
-server when using the <literal><link linkend="fetch-mail"><fetch-mail></link></literal> function. When <emphasis>unset</emphasis>, Mutt will
-download messages but also leave them on the POP server.
-</para>
-</sect2>
-
-<sect2 id="pop-host">
-<title>pop_host</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-The name of your POP server for the <literal><link linkend="fetch-mail"><fetch-mail></link></literal> function. You
-can also specify an alternative port, username and password, ie:
-
-</para>
-
-<screen>
-[pop[s]://][username[:password]@]popserver[:port]
-
-</screen><para>
-where <quote>[...]</quote> denotes an optional part.
-</para>
-</sect2>
-
-<sect2 id="pop-last">
-<title>pop_last</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If this variable is <emphasis>set</emphasis>, mutt will try to use the <quote><literal>LAST</literal></quote> POP command
-for retrieving only unread messages from the POP server when using
-the <literal><link linkend="fetch-mail"><fetch-mail></link></literal> function.
-</para>
-</sect2>
-
-<sect2 id="pop-reconnect">
-<title>pop_reconnect</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-</para>
-</sect2>
-
-<sect2 id="pop-user">
-<title>pop_user</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Your login name on the POP server.
-</para>
-<para>
-This variable defaults to your user name on the local machine.
-</para>
-</sect2>
-
-<sect2 id="pop-pass">
-<title>pop_pass</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Specifies the password for your POP account. If <emphasis>unset</emphasis>, Mutt will
-prompt you for your password when you open a POP mailbox.
-</para>
-<para>
-<emphasis role="bold">Warning</emphasis>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc
-even if you are the only one who can read the file.
-</para>
-</sect2>
-
-<sect2 id="post-indent-string">
-<title>post_indent_string</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Similar to the <link linkend="attribution">$attribution</link> variable, Mutt will append this
-string after the inclusion of a message which is being replied to.
-</para>
-</sect2>
-
-<sect2 id="postpone">
-<title>postpone</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not messages are saved in the <link linkend="postponed">$postponed</link>
-mailbox when you elect not to send immediately.
-</para>
-<para>
-Also see the <link linkend="recall">$recall</link> variable.
-</para>
-</sect2>
-
-<sect2 id="postponed">
-<title>postponed</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/postponed</literal></quote></literallayout>
-
-<para>
-Mutt allows you to indefinitely <quote><link linkend="postpone">postpone</link> sending a message</quote> which
-you are editing. When you choose to postpone a message, Mutt saves it
-in the mailbox specified by this variable.
-</para>
-<para>
-Also see the <link linkend="postpone">$postpone</link> variable.
-</para>
-</sect2>
-
-<sect2 id="preconnect">
-<title>preconnect</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, a shell command to be executed if mutt fails to establish
-a connection to the server. This is useful for setting up secure
-connections, e.g. with <literal>ssh(1)</literal>. If the command returns a nonzero
-status, mutt gives up opening the server. Example:
-
-</para>
-
-<screen>
-set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
-sleep 20 < /dev/null > /dev/null"
-
-</screen><para>
-Mailbox <quote>foo</quote> on <quote>mailhost.net</quote> can now be reached
-as <quote>{localhost:1234}foo</quote>.
-</para>
-<para>
-Note: For this example to work, you must be able to log in to the
-remote machine without having to enter a password.
-</para>
-<para>
-When set, Mutt uses the tunnel for all remote connections.
-Please see <quote><link linkend="account-hook">account-hook</link></quote> in the manual for how to use different
-tunnel commands per connection.
-</para>
-</sect2>
-
-<sect2 id="print">
-<title>print</title>
-<literallayout>Type: quadoption
-Default: ask-no</literallayout>
-
-<para>
-Controls whether or not Mutt really prints messages.
-This is set to <quote>ask-no</quote> by default, because some people
-accidentally hit <quote>p</quote> often.
-</para>
-</sect2>
-
-<sect2 id="print-command">
-<title>print_command</title>
-<literallayout>Type: path
-Default: <quote><literal>lpr</literal></quote></literallayout>
-
-<para>
-This specifies the command pipe that should be used to print messages.
-</para>
-</sect2>
-
-<sect2 id="print-decode">
-<title>print_decode</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Used in connection with the <literal><print-message></literal> command. If this
-option is <emphasis>set</emphasis>, the message is decoded before it is passed to the
-external command specified by <link linkend="print-command">$print_command</link>. If this option
-is <emphasis>unset</emphasis>, 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.
-</para>
-</sect2>
-
-<sect2 id="print-split">
-<title>print_split</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Used in connection with the <literal><print-message></literal> command. If this option
-is <emphasis>set</emphasis>, the command specified by <link linkend="print-command">$print_command</link> is executed once for
-each message which is to be printed. If this option is <emphasis>unset</emphasis>,
-the command specified by <link linkend="print-command">$print_command</link> is executed only once, and
-all the messages are concatenated, with a form feed as the message
-separator.
-</para>
-<para>
-Those who use the <literal>enscript</literal>(1) program's mail-printing mode will
-most likely want to <emphasis>set</emphasis> this option.
-</para>
-</sect2>
-
-<sect2 id="prompt-after">
-<title>prompt_after</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If you use an <emphasis>external</emphasis> <link linkend="pager">$pager</link>, setting this variable will
-cause Mutt to prompt you for a command when the pager exits rather
-than returning to the index menu. If <emphasis>unset</emphasis>, Mutt will return to the
-index menu when the external pager exits.
-</para>
-</sect2>
-
-<sect2 id="query-command">
-<title>query_command</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This specifies the command that mutt will use to make external address
-queries. The string should contain a <quote>%s</quote>, which will be substituted
-with the query string the user types. See <quote><link linkend="query">query</link></quote> for more
-information.
-</para>
-</sect2>
-
-<sect2 id="query-format">
-<title>query_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4c %t %-25.25a %-25.25n %?e?(%e)?</literal></quote></literallayout>
-
-<para>
-This variable describes the format of the <quote>query</quote> menu. The
-following <literal>printf(3)</literal>-style sequences are understood:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%a </term>
-<listitem><para>destination address
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>current entry number
-</para></listitem></varlistentry>
-<varlistentry><term>%e </term>
-<listitem><para>extra information *
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>destination name
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para><quote>*</quote> if current entry is tagged, a space otherwise
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For an explanation of <quote>soft-fill</quote>, see the <link linkend="index-format">$index_format</link> documentation.
-</para>
-<para>
-* = can be optionally printed if nonzero, see the <link linkend="status-format">$status_format</link> documentation.
-</para>
-</sect2>
-
-<sect2 id="quit">
-<title>quit</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-This variable controls whether <quote>quit</quote> and <quote>exit</quote> actually quit
-from mutt. If this option is <emphasis>set</emphasis>, they do quit, if it is <emphasis>unset</emphasis>, they
-have no effect, and if it is set to <emphasis>ask-yes</emphasis> or <emphasis>ask-no</emphasis>, you are
-prompted for confirmation when you try to quit.
-</para>
-</sect2>
-
-<sect2 id="quote-regexp">
-<title>quote_regexp</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>ˆ([ \t]*[|>:}#])+</literal></quote></literallayout>
-
-<para>
-A regular expression used in the internal pager to determine quoted
-sections of text in the body of a message. Quoted text may be filtered
-out using the <literal><toggle-quoted></literal> command, or colored according to the
-<quote>color quoted</quote> family of directives.
-</para>
-<para>
-Higher levels of quoting may be colored differently (<quote>color quoted1</quote>,
-<quote>color quoted2</quote>, etc.). The quoting level is determined by removing
-the last character from the matched text and recursively reapplying
-the regular expression until it fails to produce a match.
-</para>
-<para>
-Match detection may be overridden by the <link linkend="smileys">$smileys</link> regular expression.
-</para>
-</sect2>
-
-<sect2 id="read-inc">
-<title>read_inc</title>
-<literallayout>Type: number
-Default: 10</literallayout>
-
-<para>
-If set to a value greater than 0, Mutt will display which message it
-is currently on when reading a mailbox or when performing search actions
-such as search and limit. The message is printed after
-this many messages have been read or searched (e.g., if set to 25, Mutt will
-print a message when it is at message 25, and then again when it gets
-to message 50). This variable is meant to indicate progress when
-reading or searching large mailboxes which may take some time.
-When set to 0, only a single message will appear before the reading
-the mailbox.
-</para>
-<para>
-Also see the <link linkend="write-inc">$write_inc</link>, <link linkend="net-inc">$net_inc</link> and <link linkend="time-inc">$time_inc</link> variables and the
-<quote><link linkend="tuning">tuning</link></quote> section of the manual for performance considerations.
-</para>
-</sect2>
-
-<sect2 id="read-only">
-<title>read_only</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, all folders are opened in read-only mode.
-</para>
-</sect2>
-
-<sect2 id="realname">
-<title>realname</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This variable specifies what <quote>real</quote> or <quote>personal</quote> name should be used
-when sending messages.
-</para>
-<para>
-By default, this is the GECOS field from <literal>/etc/passwd</literal>. Note that this
-variable will <emphasis>not</emphasis> be used when the user has set a real name
-in the <link linkend="from">$from</link> variable.
-</para>
-</sect2>
-
-<sect2 id="recall">
-<title>recall</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not Mutt recalls postponed messages
-when composing a new message.
-</para>
-<para>
-<emphasis>Setting</emphasis> this variable to is not generally useful, and thus not
-recommended.
-</para>
-<para>
-Also see <link linkend="postponed">$postponed</link> variable.
-</para>
-</sect2>
-
-<sect2 id="record">
-<title>record</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/sent</literal></quote></literallayout>
-
-<para>
-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 <quote><link linkend="my-hdr">my_hdr</link></quote>
-command to create a <quote>Bcc:</quote> field with your email address in it.)
-</para>
-<para>
-The value of <emphasis><link linkend="record">$record</link></emphasis> is overridden by the <link linkend="force-name">$force_name</link> and
-<link linkend="save-name">$save_name</link> variables, and the <quote><link linkend="fcc-hook">fcc-hook</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="reply-regexp">
-<title>reply_regexp</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>ˆ(re([\[0-9\]+])*|aw):[ \t]*</literal></quote></literallayout>
-
-<para>
-A regular expression used to recognize reply messages when threading
-and replying. The default value corresponds to the English "Re:" and
-the German "Aw:".
-</para>
-</sect2>
-
-<sect2 id="reply-self">
-<title>reply_self</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>unset</emphasis> and you are replying to a message sent by you, Mutt will
-assume that you want to reply to the recipients of that message rather
-than to yourself.
-</para>
-<para>
-Also see the <quote><link linkend="alternates">alternates</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="reply-to">
-<title>reply_to</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, when replying to a message, Mutt will use the address listed
-in the Reply-to: header as the recipient of the reply. If <emphasis>unset</emphasis>,
-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.
-</para>
-</sect2>
-
-<sect2 id="resolve">
-<title>resolve</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the cursor will be automatically advanced to the next
-(possibly undeleted) message whenever a command that modifies the
-current message is executed.
-</para>
-</sect2>
-
-<sect2 id="reverse-alias">
-<title>reverse_alias</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable controls whether or not Mutt will display the <quote>personal</quote>
-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:
-
-</para>
-
-<screen>
-alias juser abd30425@somewhere.net (Joe User)
-
-</screen><para>
-and then you receive mail which contains the following header:
-
-</para>
-
-<screen>
-From: abd30425@somewhere.net
-
-</screen><para>
-It would be displayed in the index menu as <quote>Joe User</quote> instead of
-<quote>abd30425@somewhere.net.</quote> This is useful when the person's e-mail
-address is not human friendly.
-</para>
-</sect2>
-
-<sect2 id="reverse-name">
-<title>reverse_name</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-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 <emphasis>set</emphasis>, the default <emphasis>From:</emphasis> line of
-the reply messages is built using the address where you received the
-messages you are replying to <emphasis role="bold">if</emphasis> that address matches your
-<quote><link linkend="alternates">alternates</link></quote>. If the variable is <emphasis>unset</emphasis>, or the address that would be
-used doesn't match your <quote><link linkend="alternates">alternates</link></quote>, the <emphasis>From:</emphasis> line will use
-your address on the current machine.
-</para>
-<para>
-Also see the <quote><link linkend="alternates">alternates</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="reverse-realname">
-<title>reverse_realname</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable fine-tunes the behaviour of the <link linkend="reverse-name">$reverse_name</link> feature.
-When it is <emphasis>set</emphasis>, mutt will use the address from incoming messages as-is,
-possibly including eventual real names. When it is <emphasis>unset</emphasis>, mutt will
-override any such real names with the setting of the <link linkend="realname">$realname</link> variable.
-</para>
-</sect2>
-
-<sect2 id="rfc2047-parameters">
-<title>rfc2047_parameters</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, Mutt will decode RFC2047-encoded MIME
-parameters. You want to set this variable when mutt suggests you
-to save attachments to files named like:
-
-</para>
-
-<screen>
-=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-</screen><para>
-When this variable is <emphasis>set</emphasis> interactively, the change won't be
-active until you change folders.
-</para>
-<para>
-Note that this use of RFC2047's encoding is explicitly
-prohibited by the standard, but nevertheless encountered in the
-wild.
-</para>
-<para>
-Also note that setting this parameter will <emphasis>not</emphasis> have the effect
-that mutt <emphasis>generates</emphasis> this kind of encoding. Instead, mutt will
-unconditionally use the encoding specified in RFC2231.
-</para>
-</sect2>
-
-<sect2 id="save-address">
-<title>save_address</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If <link linkend="save-name">$save_name</link> or <link linkend="force-name">$force_name</link>
-is <emphasis>set</emphasis> too, the selection of the Fcc folder will be changed as well.
-</para>
-</sect2>
-
-<sect2 id="save-empty">
-<title>save_empty</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, mailboxes which contain no saved messages will be removed
-when closed (the exception is <link linkend="spoolfile">$spoolfile</link> which is never removed).
-If <emphasis>set</emphasis>, mailboxes are never removed.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> This only applies to mbox and MMDF folders, Mutt does not
-delete MH and Maildir directories.
-</para>
-</sect2>
-
-<sect2 id="save-history">
-<title>save_history</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-This variable controls the size of the history (per category) saved in the
-<link linkend="history-file">$history_file</link> file.
-</para>
-</sect2>
-
-<sect2 id="save-name">
-<title>save_name</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable controls how copies of outgoing messages are saved.
-When <emphasis>set</emphasis>, 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 <link linkend="folder">$folder</link> directory with the <emphasis>username</emphasis> 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
-<link linkend="record">$record</link> mailbox.
-</para>
-<para>
-Also see the <link linkend="force-name">$force_name</link> variable.
-</para>
-</sect2>
-
-<sect2 id="score">
-<title>score</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When this variable is <emphasis>unset</emphasis>, scoring is turned off. This can
-be useful to selectively disable scoring for certain folders when the
-<link linkend="score-threshold-delete">$score_threshold_delete</link> variable and related are used.
-</para>
-</sect2>
-
-<sect2 id="score-threshold-delete">
-<title>score_threshold_delete</title>
-<literallayout>Type: number
-Default: -1</literallayout>
-
-<para>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked for deletion by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message for deletion.
-</para>
-</sect2>
-
-<sect2 id="score-threshold-flag">
-<title>score_threshold_flag</title>
-<literallayout>Type: number
-Default: 9999</literallayout>
-
-<para>
-Messages which have been assigned a score greater than or equal to this
-variable's value are automatically marked "flagged".
-</para>
-</sect2>
-
-<sect2 id="score-threshold-read">
-<title>score_threshold_read</title>
-<literallayout>Type: number
-Default: -1</literallayout>
-
-<para>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked as read by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message read.
-</para>
-</sect2>
-
-<sect2 id="send-charset">
-<title>send_charset</title>
-<literallayout>Type: string
-Default: <quote><literal>us-ascii:iso-8859-1:utf-8</literal></quote></literallayout>
-
-<para>
-A colon-delimited list of character sets for outgoing messages. Mutt will use the
-first character set into which the text can be converted exactly.
-If your <link linkend="charset">$charset</link> is not <quote>iso-8859-1</quote> and recipients may not
-understand <quote>UTF-8</quote>, it is advisable to include in the list an
-appropriate widely used standard character set (such as
-<quote>iso-8859-2</quote>, <quote>koi8-r</quote> or <quote>iso-2022-jp</quote>) either instead of or after
-<quote>iso-8859-1</quote>.
-</para>
-<para>
-In case the text cannot be converted into one of these exactly,
-mutt uses <link linkend="charset">$charset</link> as a fallback.
-</para>
-</sect2>
-
-<sect2 id="sendmail">
-<title>sendmail</title>
-<literallayout>Type: path
-Default: <quote><literal>/usr/sbin/sendmail -oem -oi</literal></quote></literallayout>
-
-<para>
-Specifies the program and arguments used to deliver mail sent by Mutt.
-Mutt expects that the specified program interprets additional
-arguments as recipient addresses.
-</para>
-</sect2>
-
-<sect2 id="sendmail-wait">
-<title>sendmail_wait</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-Specifies the number of seconds to wait for the <link linkend="sendmail">$sendmail</link> process
-to finish before giving up and putting delivery in the background.
-</para>
-<para>
-Mutt interprets the value of this variable as follows:
-
-</para>
-
-<variablelist>
-<varlistentry><term>>0 </term>
-<listitem><para>number of seconds to wait for sendmail to finish before continuing
-</para></listitem></varlistentry>
-<varlistentry><term>0 </term>
-<listitem><para>wait forever for sendmail to finish
-</para></listitem></varlistentry>
-<varlistentry><term><0 </term>
-<listitem><para>always put sendmail in the background without waiting
-</para></listitem></varlistentry></variablelist>
-
-<para>
-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.
-</para>
-</sect2>
-
-<sect2 id="shell">
-<title>shell</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Command to use when spawning a subshell. By default, the user's login
-shell from <literal>/etc/passwd</literal> is used.
-</para>
-</sect2>
-
-<sect2 id="sig-dashes">
-<title>sig_dashes</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, a line containing <quote>-- </quote> (note the trailing space) will be inserted before your
-<link linkend="signature">$signature</link>. It is <emphasis role="bold">strongly</emphasis> recommended that you not <emphasis>unset</emphasis>
-this variable unless your signature contains just your name. The
-reason for this is because many software packages use <quote>-- \n</quote> to
-detect your signature. For example, Mutt has the ability to highlight
-the signature in a different color in the builtin pager.
-</para>
-</sect2>
-
-<sect2 id="sig-on-top">
-<title>sig_on_top</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, the signature will be included before any quoted or forwarded
-text. It is <emphasis role="bold">strongly</emphasis> 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.
-</para>
-</sect2>
-
-<sect2 id="signature">
-<title>signature</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/.signature</literal></quote></literallayout>
-
-<para>
-Specifies the filename of your signature, which is appended to all
-outgoing messages. If the filename ends with a pipe (<quote>|</quote>), it is
-assumed that filename is a shell command and input should be read from
-its standard output.
-</para>
-</sect2>
-
-<sect2 id="simple-search">
-<title>simple_search</title>
-<literallayout>Type: string
-Default: <quote><literal>˜f %s | ˜s %s</literal></quote></literallayout>
-
-<para>
-Specifies how Mutt should expand a simple search into a real search
-pattern. A simple search is one that does not contain any of the <quote>˜</quote> pattern
-operators. See <quote><link linkend="patterns">patterns</link></quote> for more information on search patterns.
-</para>
-<para>
-For example, if you simply type <quote>joe</quote> at a search or limit prompt, Mutt
-will automatically expand it to the value specified by this variable by
-replacing <quote>%s</quote> with the supplied string.
-For the default value, <quote>joe</quote> would be expanded to: <quote>˜f joe | ˜s joe</quote>.
-</para>
-</sect2>
-
-<sect2 id="smart-wrap">
-<title>smart_wrap</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls the display of lines longer than the screen width in the
-internal pager. If <emphasis>set</emphasis>, long lines are wrapped at a word boundary. If
-<emphasis>unset</emphasis>, lines are simply wrapped at the screen edge. Also see the
-<link linkend="markers">$markers</link> variable.
-</para>
-</sect2>
-
-<sect2 id="smileys">
-<title>smileys</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>(>From )|(:[-ˆ]?[][)(><}{|/DP])</literal></quote></literallayout>
-
-<para>
-The <emphasis>pager</emphasis> uses this variable to catch some common false
-positives of <link linkend="quote-regexp">$quote_regexp</link>, most notably smileys and not consider
-a line quoted text if it also matches <link linkend="smileys">$smileys</link>. This mostly
-happens at the beginning of a line.
-</para>
-</sect2>
-
-<sect2 id="sleep-time">
-<title>sleep_time</title>
-<literallayout>Type: number
-Default: 1</literallayout>
-
-<para>
-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.
-</para>
-</sect2>
-
-<sect2 id="smtp-authenticators">
-<title>smtp_authenticators</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an SMTP server, in the order mutt should
-try them. Authentication methods are any SASL mechanism, eg
-<quote>digest-md5</quote>, <quote>gssapi</quote> or <quote>cram-md5</quote>.
-This option is case-insensitive. If it is <quote>unset</quote>
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set smtp_authenticators="digest-md5:cram-md5"
-
-</screen></sect2>
-
-<sect2 id="smtp-pass">
-<title>smtp_pass</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Specifies the password for your SMTP account. If <emphasis>unset</emphasis>, Mutt will
-prompt you for your password when you first send mail via SMTP.
-See <link linkend="smtp-url">$smtp_url</link> to configure mutt to send mail via SMTP.
-</para>
-<para>
-<emphasis role="bold">Warning</emphasis>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</para>
-</sect2>
-
-<sect2 id="smtp-url">
-<title>smtp_url</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Defines the SMTP smarthost where sent messages should relayed for
-delivery. This should take the form of an SMTP URL, eg:
-
-</para>
-
-<screen>
-smtp[s]://[user[:pass]@]host[:port]/
-
-</screen><para>
-\.\.\. where <quote>[...]</quote> denotes an optional part.
-Setting this variable overrides the value of the <link linkend="sendmail">$sendmail</link>
-variable.
-</para>
-</sect2>
-
-<sect2 id="sort">
-<title>sort</title>
-<literallayout>Type: sort order
-Default: date</literallayout>
-
-<para>
-Specifies how to sort messages in the <quote>index</quote> menu. Valid values
-are:
-
-</para>
-
-<itemizedlist>
-<listitem><para>date or date-sent
-</para></listitem><listitem><para>date-received
-</para></listitem><listitem><para>from
-</para></listitem><listitem><para>mailbox-order (unsorted)
-</para></listitem><listitem><para>score
-</para></listitem><listitem><para>size
-</para></listitem><listitem><para>spam
-</para></listitem><listitem><para>subject
-</para></listitem><listitem><para>threads
-</para></listitem><listitem><para>to
-</para></listitem></itemizedlist>
-
-<para>
-You may optionally use the <quote>reverse-</quote> prefix to specify reverse sorting
-order (example: <quote><literal>set sort=reverse-date-sent</literal></quote>).
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this option is set by default to
-<quote>threads</quote> in /etc/Muttrc.
-</para>
-</sect2>
-
-<sect2 id="sort-alias">
-<title>sort_alias</title>
-<literallayout>Type: sort order
-Default: alias</literallayout>
-
-<para>
-Specifies how the entries in the <quote>alias</quote> menu are sorted. The
-following are legal values:
-
-</para>
-
-<itemizedlist>
-<listitem><para>address (sort alphabetically by email address)
-</para></listitem><listitem><para>alias (sort alphabetically by alias name)
-</para></listitem><listitem><para>unsorted (leave in order specified in .muttrc)
-</para></listitem></itemizedlist>
-</sect2>
-
-<sect2 id="sort-aux">
-<title>sort_aux</title>
-<literallayout>Type: sort order
-Default: date</literallayout>
-
-<para>
-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 <link linkend="sort">$sort</link> can, except
-<quote>threads</quote> (in that case, mutt will just use <quote>date-sent</quote>). You can also
-specify the <quote>last-</quote> prefix in addition to the <quote>reverse-</quote> prefix, but <quote>last-</quote>
-must come after <quote>reverse-</quote>. The <quote>last-</quote> prefix causes messages to be
-sorted against its siblings by which has the last descendant, using
-the rest of <link linkend="sort-aux">$sort_aux</link> as an ordering. For instance,
-
-</para>
-
-<screen>
-set sort_aux=last-date-received
-
-</screen><para>
-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 <quote><literal>set sort=reverse-threads</literal></quote>.)
-</para>
-<para>
-Note: For reversed <link linkend="sort">$sort</link>
-order <link linkend="sort-aux">$sort_aux</link> is reversed again (which is not the right thing to do,
-but kept to not break any existing configuration setting).
-</para>
-</sect2>
-
-<sect2 id="sort-browser">
-<title>sort_browser</title>
-<literallayout>Type: sort order
-Default: alpha</literallayout>
-
-<para>
-Specifies how to sort entries in the file browser. By default, the
-entries are sorted alphabetically. Valid values:
-
-</para>
-
-<itemizedlist>
-<listitem><para>alpha (alphabetically)
-</para></listitem><listitem><para>date
-</para></listitem><listitem><para>size
-</para></listitem><listitem><para>unsorted
-</para></listitem></itemizedlist>
-
-<para>
-You may optionally use the <quote>reverse-</quote> prefix to specify reverse sorting
-order (example: <quote><literal>set sort_browser=reverse-date</literal></quote>).
-</para>
-</sect2>
-
-<sect2 id="sort-re">
-<title>sort_re</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable is only useful when sorting by threads with
-<link linkend="strict-threads">$strict_threads</link> <emphasis>unset</emphasis>. In that case, it changes the heuristic
-mutt uses to thread messages by subject. With <link linkend="sort-re">$sort_re</link> <emphasis>set</emphasis>, mutt 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 <link linkend="reply-regexp">$reply_regexp</link>. With <link linkend="sort-re">$sort_re</link> <emphasis>unset</emphasis>, mutt will attach
-the message whether or not this is the case, as long as the
-non-<link linkend="reply-regexp">$reply_regexp</link> parts of both messages are identical.
-</para>
-</sect2>
-
-<sect2 id="spam-separator">
-<title>spam_separator</title>
-<literallayout>Type: string
-Default: <quote><literal>,</literal></quote></literallayout>
-
-<para>
-This variable controls what happens when multiple spam headers
-are matched: if <emphasis>unset</emphasis>, each successive header will overwrite any
-previous matches value for the spam label. If <emphasis>set</emphasis>, each successive
-match will append to the previous, using this variable's value as a
-separator.
-</para>
-</sect2>
-
-<sect2 id="spoolfile">
-<title>spoolfile</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-If your spool mailbox is in a non-default place where Mutt cannot find
-it, you can specify its location with this variable. Mutt will
-automatically set this variable to the value of the environment
-variable <literal>$MAIL</literal> if it is not set.
-</para>
-</sect2>
-
-<sect2 id="status-chars">
-<title>status_chars</title>
-<literallayout>Type: string
-Default: <quote><literal>-*%A</literal></quote></literallayout>
-
-<para>
-Controls the characters used by the <quote>%r</quote> indicator in
-<link linkend="status-format">$status_format</link>. 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 <literal><toggle-write></literal> operation, bound by default to <quote>%</quote>). 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).
-</para>
-</sect2>
-
-<sect2 id="status-format">
-<title>status_format</title>
-<literallayout>Type: string
-Default: <quote><literal>-%r-Mutt: %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)---</literal></quote></literallayout>
-
-<para>
-Controls the format of the status line displayed in the <quote>index</quote>
-menu. This string is similar to <link linkend="index-format">$index_format</link>, but has its own
-set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%b </term>
-<listitem><para>number of mailboxes with new mail *
-</para></listitem></varlistentry>
-<varlistentry><term>%d </term>
-<listitem><para>number of deleted messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>the full pathname of the current mailbox
-</para></listitem></varlistentry>
-<varlistentry><term>%F </term>
-<listitem><para>number of flagged messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%h </term>
-<listitem><para>local hostname
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>size (in bytes) of the current mailbox *
-</para></listitem></varlistentry>
-<varlistentry><term>%L </term>
-<listitem><para>size (in bytes) of the messages shown
-(i.e., which match the current limit) *
-</para></listitem></varlistentry>
-<varlistentry><term>%m </term>
-<listitem><para>the number of messages in the mailbox *
-</para></listitem></varlistentry>
-<varlistentry><term>%M </term>
-<listitem><para>the number of messages shown (i.e., which match the current limit) *
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>number of new messages in the mailbox *
-</para></listitem></varlistentry>
-<varlistentry><term>%o </term>
-<listitem><para>number of old unread messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%p </term>
-<listitem><para>number of postponed messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%P </term>
-<listitem><para>percentage of the way through the index
-</para></listitem></varlistentry>
-<varlistentry><term>%r </term>
-<listitem><para>modified/read-only/won't-write/attach-message indicator,
-according to <link linkend="status-chars">$status_chars</link>
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>current sorting mode (<link linkend="sort">$sort</link>)
-</para></listitem></varlistentry>
-<varlistentry><term>%S </term>
-<listitem><para>current aux sorting method (<link linkend="sort-aux">$sort_aux</link>)
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para>number of tagged messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>number of unread messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%v </term>
-<listitem><para>Mutt version string
-</para></listitem></varlistentry>
-<varlistentry><term>%V </term>
-<listitem><para>currently active limit pattern, if any *
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For an explanation of <quote>soft-fill</quote>, see the <link linkend="index-format">$index_format</link> documentation.
-</para>
-<para>
-* = can be optionally printed if nonzero
-</para>
-<para>
-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:
-</para>
-<para>
-<literal>%?<sequence_char>?<optional_string>?</literal>
-</para>
-<para>
-where <emphasis>sequence_char</emphasis> is a character from the table above, and
-<emphasis>optional_string</emphasis> is the string you would like printed if
-<emphasis>sequence_char</emphasis> is nonzero. <emphasis>optional_string</emphasis> <emphasis role="bold">may</emphasis> contain
-other sequences as well as normal text, but you may <emphasis role="bold">not</emphasis> nest
-optional strings.
-</para>
-<para>
-Here is an example illustrating how to optionally print the number of
-new messages in a mailbox:
-</para>
-<para>
-<literal>%?n?%n new messages.?</literal>
-</para>
-<para>
-You can also switch between two strings using the following construct:
-</para>
-<para>
-<literal>%?<sequence_char>?<if_string>&<else_string>?</literal>
-</para>
-<para>
-If the value of <emphasis>sequence_char</emphasis> is non-zero, <emphasis>if_string</emphasis> will
-be expanded, otherwise <emphasis>else_string</emphasis> will be expanded.
-</para>
-<para>
-You can force the result of any <literal>printf(3)</literal>-like sequence to be lowercase
-by prefixing the sequence character with an underscore (<quote>_</quote>) sign.
-For example, if you want to display the local hostname in lowercase,
-you would use: <quote><literal>%_h</literal></quote>.
-</para>
-<para>
-If you prefix the sequence character with a colon (<quote>:</quote>) character, mutt
-will replace any dots in the expansion by underscores. This might be helpful
-with IMAP folders that don't like dots in folder names.
-</para>
-</sect2>
-
-<sect2 id="status-on-top">
-<title>status_on_top</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Setting this variable causes the <quote>status bar</quote> to be displayed on
-the first line of the screen rather than near the bottom. If <link linkend="help">$help</link>
-is <emphasis>set</emphasis>, too it'll be placed at the bottom.
-</para>
-</sect2>
-
-<sect2 id="strict-threads">
-<title>strict_threads</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, threading will only make use of the <quote>In-Reply-To</quote> and
-<quote>References:</quote> fields when you <link linkend="sort">$sort</link> by message threads. By
-default, messages with the same subject are grouped together in
-<quote>pseudo threads.</quote>. This may not always be desirable, such as in a
-personal mailbox where you might have several unrelated messages with
-the subjects like <quote>hi</quote> which will get grouped together. See also
-<link linkend="sort-re">$sort_re</link> for a less drastic way of controlling this
-behaviour.
-</para>
-</sect2>
-
-<sect2 id="suspend">
-<title>suspend</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, mutt won't stop when the user presses the terminal's
-<emphasis>susp</emphasis> key, usually <quote>ˆZ</quote>. This is useful if you run mutt
-inside an xterm using a command like <quote><literal>xterm -e mutt</literal></quote>.
-</para>
-</sect2>
-
-<sect2 id="text-flowed">
-<title>text_flowed</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will generate <quote>format=flowed</quote> bodies with a content type
-of <quote><literal>text/plain; format=flowed</literal></quote>.
-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.
-</para>
-<para>
-Note that <link linkend="indent-string">$indent_string</link> is ignored when this option is <emphasis>set</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="thread-received">
-<title>thread_received</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt uses the date received rather than the date sent
-to thread messages by subject.
-</para>
-</sect2>
-
-<sect2 id="thorough-search">
-<title>thorough_search</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Affects the <literal>˜b</literal> and <literal>˜h</literal> search operations described in
-section <quote><link linkend="patterns">patterns</link></quote>. If <emphasis>set</emphasis>, the headers and body/attachments of
-messages to be searched are decoded before searching. If <emphasis>unset</emphasis>,
-messages are searched as they appear in the folder.
-</para>
-<para>
-Users searching attachments or for non-ASCII characters should <emphasis>set</emphasis>
-this value because decoding also includes MIME parsing/decoding and possible
-character set conversions. Otherwise mutt will attempt to match against the
-raw message received (for example quoted-printable encoded or with encoded
-headers) which may lead to incorrect search results.
-</para>
-</sect2>
-
-<sect2 id="tilde">
-<title>tilde</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the internal-pager will pad blank lines to the bottom of the
-screen with a tilde (<quote>˜</quote>).
-</para>
-</sect2>
-
-<sect2 id="time-inc">
-<title>time_inc</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-Along with <link linkend="read-inc">$read_inc</link>, <link linkend="write-inc">$write_inc</link>, and <link linkend="net-inc">$net_inc</link>, this
-variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than <link linkend="time-inc">$time_inc</link> milliseconds
-apart. This can improve throughput on systems with slow terminals,
-or when running mutt on a remote system.
-</para>
-<para>
-Also see the <quote><link linkend="tuning">tuning</link></quote> section of the manual for performance considerations.
-</para>
-</sect2>
-
-<sect2 id="timeout">
-<title>timeout</title>
-<literallayout>Type: number
-Default: 600</literallayout>
-
-<para>
-When Mutt is waiting for user input either idleing in menus or
-in an interactive prompt, Mutt would block until input is
-present. Depending on the context, this would prevent certain
-operations from working, like checking for new mail or keeping
-an IMAP connection alive.
-</para>
-<para>
-This variable controls how many seconds Mutt will at most wait
-until it aborts waiting for input, performs these operations and
-continues to wait for input.
-</para>
-<para>
-A value of zero or less will cause Mutt to never time out.
-</para>
-</sect2>
-
-<sect2 id="tmpdir">
-<title>tmpdir</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable allows you to specify where Mutt will place its
-temporary files needed for displaying and composing messages. If
-this variable is not set, the environment variable <literal>$TMPDIR</literal> is
-used. If <literal>$TMPDIR</literal> is not set then <quote><literal>/tmp</literal></quote> is used.
-</para>
-</sect2>
-
-<sect2 id="to-chars">
-<title>to_chars</title>
-<literallayout>Type: string
-Default: <quote><literal> +TCFL</literal></quote></literallayout>
-
-<para>
-Controls the character used to indicate mail addressed to you. The
-first character is the one used when the mail is <emphasis>not</emphasis> addressed to your
-address. The second is used when you are the only
-recipient of the message. The third is when your address
-appears in the <quote>To:</quote> header field, but you are not the only recipient of
-the message. The fourth character is used when your
-address is specified in the <quote>Cc:</quote> header field, but you are not the only
-recipient. The fifth character is used to indicate mail that was sent
-by <emphasis>you</emphasis>. The sixth character is used to indicate when a mail
-was sent to a mailing-list you subscribe to.
-</para>
-</sect2>
-
-<sect2 id="trash">
-<title>trash</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-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.
-</para>
-<para>
-NOTE: When you delete a message in the trash folder, it is really
-deleted, so that you have a way to clean the trash.
-</para>
-</sect2>
-
-<sect2 id="tunnel">
-<title>tunnel</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Setting this variable will cause mutt 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/SMTP server. Example:
-
-</para>
-
-<screen>
-set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-
-</screen><para>
-Note: For this example to work you must be able to log in to the remote
-machine without having to enter a password.
-</para>
-</sect2>
-
-<sect2 id="use-8bitmime">
-<title>use_8bitmime</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-<emphasis role="bold">Warning:</emphasis> do not set this variable unless you are using a version
-of sendmail which supports the <literal>-B8BITMIME</literal> flag (such as sendmail
-8.8.x) or you may not be able to send mail.
-</para>
-<para>
-When <emphasis>set</emphasis>, Mutt will invoke <link linkend="sendmail">$sendmail</link> with the <literal>-B8BITMIME</literal>
-flag when sending 8-bit messages to enable ESMTP negotiation.
-</para>
-</sect2>
-
-<sect2 id="use-domain">
-<title>use_domain</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will qualify all local addresses (ones without the
-<quote>@host</quote> portion) with the value of <link linkend="hostname">$hostname</link>. If <emphasis>unset</emphasis>, no
-addresses will be qualified.
-</para>
-</sect2>
-
-<sect2 id="use-envelope-from">
-<title>use_envelope_from</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will set the <emphasis>envelope</emphasis> sender of the message.
-If <link linkend="envelope-from-address">$envelope_from_address</link> is <emphasis>set</emphasis>, it will be used as the sender
-address. If <emphasis>unset</emphasis>, mutt will attempt to derive the sender from the
-<quote>From:</quote> header.
-</para>
-<para>
-Note that this information is passed to sendmail command using the
-<literal>-f</literal> command line switch. Therefore setting this option is not useful
-if the <link linkend="sendmail">$sendmail</link> variable already contains <literal>-f</literal> or if the
-executable pointed to by <link linkend="sendmail">$sendmail</link> doesn't support the <literal>-f</literal> switch.
-</para>
-</sect2>
-
-<sect2 id="use-from">
-<title>use_from</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will generate the <quote>From:</quote> header field when
-sending messages. If <emphasis>unset</emphasis>, no <quote>From:</quote> header field will be
-generated unless the user explicitly sets one using the <quote><link linkend="my-hdr">my_hdr</link></quote>
-command.
-</para>
-</sect2>
-
-<sect2 id="use-idn">
-<title>use_idn</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will show you international domain names decoded.
-Note: You can use IDNs for addresses even if this is <emphasis>unset</emphasis>.
-This variable only affects decoding.
-</para>
-</sect2>
-
-<sect2 id="use-ipv6">
-<title>use_ipv6</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will look for IPv6 addresses of hosts it tries to
-contact. If this option is <emphasis>unset</emphasis>, Mutt will restrict itself to IPv4 addresses.
-Normally, the default should work.
-</para>
-</sect2>
-
-<sect2 id="user-agent">
-<title>user_agent</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will add a <quote>User-Agent:</quote> header to outgoing
-messages, indicating which version of mutt was used for composing
-them.
-</para>
-</sect2>
-
-<sect2 id="visual">
-<title>visual</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Specifies the visual editor to invoke when the <quote><literal>˜v</literal></quote> command is
-given in the builtin editor.
-</para>
-</sect2>
-
-<sect2 id="wait-key">
-<title>wait_key</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether Mutt will ask you to press a key after an external command
-has been invoked by these functions: <literal><shell-escape></literal>,
-<literal><pipe-message></literal>, <literal><pipe-entry></literal>, <literal><print-message></literal>,
-and <literal><print-entry></literal> commands.
-</para>
-<para>
-It is also used when viewing attachments with <quote><link linkend="auto-view">auto_view</link></quote>, provided
-that the corresponding mailcap entry has a <emphasis>needsterminal</emphasis> flag,
-and the external program is interactive.
-</para>
-<para>
-When <emphasis>set</emphasis>, Mutt will always ask for a key. When <emphasis>unset</emphasis>, Mutt will wait
-for a key only if the external command returned a non-zero status.
-</para>
-</sect2>
-
-<sect2 id="weed">
-<title>weed</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will weed headers when displaying, forwarding,
-printing, or replying to messages.
-</para>
-</sect2>
-
-<sect2 id="wrap">
-<title>wrap</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-When set to a positive value, mutt will wrap text at <link linkend="wrap">$wrap</link> characters.
-When set to a negative value, mutt will wrap text so that there are <link linkend="wrap">$wrap</link>
-characters of empty space on the right side of the terminal.
-</para>
-</sect2>
-
-<sect2 id="wrap-search">
-<title>wrap_search</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether searches wrap around the end.
-</para>
-<para>
-When <emphasis>set</emphasis>, searches will wrap around the first (or last) item. When
-<emphasis>unset</emphasis>, incremental searches will not wrap.
-</para>
-</sect2>
-
-<sect2 id="wrapmargin">
-<title>wrapmargin</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-(DEPRECATED) Equivalent to setting <link linkend="wrap">$wrap</link> with a negative value.
-</para>
-</sect2>
-
-<sect2 id="write-inc">
-<title>write_inc</title>
-<literallayout>Type: number
-Default: 10</literallayout>
-
-<para>
-When writing a mailbox, a message will be printed every
-<link linkend="write-inc">$write_inc</link> messages to indicate progress. If set to 0, only a
-single message will be displayed before writing a mailbox.
-</para>
-<para>
-Also see the <link linkend="read-inc">$read_inc</link>, <link linkend="net-inc">$net_inc</link> and <link linkend="time-inc">$time_inc</link> variables and the
-<quote><link linkend="tuning">tuning</link></quote> section of the manual for performance considerations.
-</para>
-</sect2>
-
-<sect2 id="write-bcc">
-<title>write_bcc</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether mutt writes out the <quote>Bcc:</quote> header when preparing
-messages to be sent. Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see <link linkend="smtp-url">$smtp_url</link>), this
-option does nothing: mutt will never write out the <quote>Bcc:</quote> header
-in this case.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, exim4 and postfix strip BCC headers by
-default. The above warning applies to exim3 users, see /etc/Muttrc.
-</para>
-</sect2>
-
-<sect2 id="xterm-icon">
-<title>xterm_icon</title>
-<literallayout>Type: string
-Default: <quote><literal>M%?n?AIL&ail?</literal></quote></literallayout>
-
-<para>
-Controls the format of the icon title, as long as xterm_set_titles
-is enabled. This string is identical in formatting to the one used by
-<quote><link linkend="status-format">$status_format</link></quote>.
-</para>
-</sect2>
-
-<sect2 id="xterm-set-titles">
-<title>xterm_set_titles</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Controls whether mutt sets the xterm title bar and icon name
-(as long as you are in an appropriate terminal).
-</para>
-</sect2>
-
-<sect2 id="xterm-title">
-<title>xterm_title</title>
-<literallayout>Type: string
-Default: <quote><literal>Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?</literal></quote></literallayout>
-
-<para>
-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 <quote><link linkend="status-format">$status_format</link></quote>.
-</para>
-</sect2>
-
-</sect1>
-
-<sect1 id="functions">
-<title>Functions</title>
-
-<para>
-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 <link linkend="bind">bind</link>
-command.
-</para>
-
-<sect2 id="generic_map">
-<title>generic menu</title>
-<para>
-The <emphasis>generic</emphasis> menu is not a real menu, but specifies common functions
-(such as movement) available in all menus except for <emphasis>pager</emphasis> and
-<emphasis>editor</emphasis>. Changing settings for this menu will affect the default
-bindings for all menus (except as noted).
-</para>
-
-
-<table id="generic_table">
-<title>Default generic function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><top-page></literal></entry><entry>H</entry><entry>move to the top of the page</entry></row>
-<row><entry><literal><next-entry></literal></entry><entry>j</entry><entry>move to the next entry</entry></row>
-<row><entry><literal><previous-entry></literal></entry><entry>k</entry><entry>move to the previous entry</entry></row>
-<row><entry><literal><bottom-page></literal></entry><entry>L</entry><entry>move to the bottom of the page</entry></row>
-<row><entry><literal><refresh></literal></entry><entry>^L</entry><entry>clear and redraw the screen</entry></row>
-<row><entry><literal><middle-page></literal></entry><entry>M</entry><entry>move to the middle of the page</entry></row>
-<row><entry><literal><search-next></literal></entry><entry>n</entry><entry>search for next match</entry></row>
-<row><entry><literal><exit></literal></entry><entry>q</entry><entry>exit this menu</entry></row>
-<row><entry><literal><tag-entry></literal></entry><entry>t</entry><entry>tag the current entry</entry></row>
-<row><entry><literal><next-page></literal></entry><entry>z</entry><entry>move to the next page</entry></row>
-<row><entry><literal><previous-page></literal></entry><entry>Z</entry><entry>move to the previous page</entry></row>
-<row><entry><literal><last-entry></literal></entry><entry>*</entry><entry>move to the last entry</entry></row>
-<row><entry><literal><first-entry></literal></entry><entry>=</entry><entry>move to the first entry</entry></row>
-<row><entry><literal><enter-command></literal></entry><entry>:</entry><entry>enter a muttrc command</entry></row>
-<row><entry><literal><next-line></literal></entry><entry>></entry><entry>scroll down one line</entry></row>
-<row><entry><literal><previous-line></literal></entry><entry><</entry><entry>scroll up one line</entry></row>
-<row><entry><literal><half-up></literal></entry><entry>[</entry><entry>scroll up 1/2 page</entry></row>
-<row><entry><literal><half-down></literal></entry><entry>]</entry><entry>scroll down 1/2 page</entry></row>
-<row><entry><literal><help></literal></entry><entry>?</entry><entry>this screen</entry></row>
-<row><entry><literal><tag-prefix></literal></entry><entry>;</entry><entry>apply next function to tagged messages</entry></row>
-<row><entry><literal><tag-prefix-cond></literal></entry><entry></entry><entry>apply next function ONLY to tagged messages</entry></row>
-<row><entry><literal><end-cond></literal></entry><entry></entry><entry>end of conditional execution (noop)</entry></row>
-<row><entry><literal><shell-escape></literal></entry><entry>!</entry><entry>invoke a command in a subshell</entry></row>
-<row><entry><literal><select-entry></literal></entry><entry><Return></entry><entry>select the current entry</entry></row>
-<row><entry><literal><search></literal></entry><entry>/</entry><entry>search for a regular expression</entry></row>
-<row><entry><literal><search-reverse></literal></entry><entry>Esc /</entry><entry>search backwards for a regular expression</entry></row>
-<row><entry><literal><search-opposite></literal></entry><entry></entry><entry>search for next match in opposite direction</entry></row>
-<row><entry><literal><jump></literal></entry><entry></entry><entry>jump to an index number</entry></row>
-<row><entry><literal><current-top></literal></entry><entry></entry><entry>move entry to top of screen</entry></row>
-<row><entry><literal><current-middle></literal></entry><entry></entry><entry>move entry to middle of screen</entry></row>
-<row><entry><literal><current-bottom></literal></entry><entry></entry><entry>move entry to bottom of screen</entry></row>
-<row><entry><literal><what-key></literal></entry><entry></entry><entry>display the keycode for a key press</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="index_map">
-<title>index menu</title>
-
-
-<table id="index_table">
-<title>Default index function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><create-alias></literal></entry><entry>a</entry><entry>create an alias from a message sender</entry></row>
-<row><entry><literal><bounce-message></literal></entry><entry>b</entry><entry>remail a message to another user</entry></row>
-<row><entry><literal><break-thread></literal></entry><entry>#</entry><entry>break the thread in two</entry></row>
-<row><entry><literal><change-folder></literal></entry><entry>c</entry><entry>open a different folder</entry></row>
-<row><entry><literal><change-folder-readonly></literal></entry><entry>Esc c</entry><entry>open a different folder in read only mode</entry></row>
-<row><entry><literal><next-unread-mailbox></literal></entry><entry></entry><entry>open next mailbox with new mail</entry></row>
-<row><entry><literal><collapse-thread></literal></entry><entry>Esc v</entry><entry>collapse/uncollapse current thread</entry></row>
-<row><entry><literal><collapse-all></literal></entry><entry>Esc V</entry><entry>collapse/uncollapse all threads</entry></row>
-<row><entry><literal><copy-message></literal></entry><entry>C</entry><entry>copy a message to a file/mailbox</entry></row>
-<row><entry><literal><decode-copy></literal></entry><entry>Esc C</entry><entry>make decoded (text/plain) copy</entry></row>
-<row><entry><literal><decode-save></literal></entry><entry>Esc s</entry><entry>make decoded copy (text/plain) and delete</entry></row>
-<row><entry><literal><delete-message></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><delete-pattern></literal></entry><entry>D</entry><entry>delete messages matching a pattern</entry></row>
-<row><entry><literal><delete-thread></literal></entry><entry>^D</entry><entry>delete all messages in thread</entry></row>
-<row><entry><literal><delete-subthread></literal></entry><entry>Esc d</entry><entry>delete all messages in subthread</entry></row>
-<row><entry><literal><edit></literal></entry><entry>e</entry><entry>edit the raw message</entry></row>
-<row><entry><literal><edit-type></literal></entry><entry>^E</entry><entry>edit attachment content type</entry></row>
-<row><entry><literal><forward-message></literal></entry><entry>f</entry><entry>forward a message with comments</entry></row>
-<row><entry><literal><flag-message></literal></entry><entry>F</entry><entry>toggle a message's 'important' flag</entry></row>
-<row><entry><literal><group-reply></literal></entry><entry>g</entry><entry>reply to all recipients</entry></row>
-<row><entry><literal><fetch-mail></literal></entry><entry>G</entry><entry>retrieve mail from POP server</entry></row>
-<row><entry><literal><imap-fetch-mail></literal></entry><entry></entry><entry>force retrieval of mail from IMAP server</entry></row>
-<row><entry><literal><display-toggle-weed></literal></entry><entry>h</entry><entry>display message and toggle header weeding</entry></row>
-<row><entry><literal><next-undeleted></literal></entry><entry>j</entry><entry>move to the next undeleted message</entry></row>
-<row><entry><literal><previous-undeleted></literal></entry><entry>k</entry><entry>move to the previous undeleted message</entry></row>
-<row><entry><literal><limit></literal></entry><entry>l</entry><entry>show only messages matching a pattern</entry></row>
-<row><entry><literal><link-threads></literal></entry><entry>&</entry><entry>link tagged message to the current one</entry></row>
-<row><entry><literal><list-reply></literal></entry><entry>L</entry><entry>reply to specified mailing list</entry></row>
-<row><entry><literal><mail></literal></entry><entry>m</entry><entry>compose a new mail message</entry></row>
-<row><entry><literal><toggle-new></literal></entry><entry>N</entry><entry>toggle a message's 'new' flag</entry></row>
-<row><entry><literal><toggle-write></literal></entry><entry>%</entry><entry>toggle whether the mailbox will be rewritten</entry></row>
-<row><entry><literal><next-thread></literal></entry><entry>^N</entry><entry>jump to the next thread</entry></row>
-<row><entry><literal><next-subthread></literal></entry><entry>Esc n</entry><entry>jump to the next subthread</entry></row>
-<row><entry><literal><purge-message></literal></entry><entry></entry><entry>really delete the current entry, bypassing the trash folder</entry></row>
-<row><entry><literal><query></literal></entry><entry>Q</entry><entry>query external program for addresses</entry></row>
-<row><entry><literal><quit></literal></entry><entry>q</entry><entry>save changes to mailbox and quit</entry></row>
-<row><entry><literal><reply></literal></entry><entry>r</entry><entry>reply to a message</entry></row>
-<row><entry><literal><show-limit></literal></entry><entry>Esc l</entry><entry>show currently active limit pattern</entry></row>
-<row><entry><literal><sort-mailbox></literal></entry><entry>o</entry><entry>sort messages</entry></row>
-<row><entry><literal><sort-reverse></literal></entry><entry>O</entry><entry>sort messages in reverse order</entry></row>
-<row><entry><literal><print-message></literal></entry><entry>p</entry><entry>print the current entry</entry></row>
-<row><entry><literal><previous-thread></literal></entry><entry>^P</entry><entry>jump to previous thread</entry></row>
-<row><entry><literal><previous-subthread></literal></entry><entry>Esc p</entry><entry>jump to previous subthread</entry></row>
-<row><entry><literal><recall-message></literal></entry><entry>R</entry><entry>recall a postponed message</entry></row>
-<row><entry><literal><read-thread></literal></entry><entry>^R</entry><entry>mark the current thread as read</entry></row>
-<row><entry><literal><read-subthread></literal></entry><entry>Esc r</entry><entry>mark the current subthread as read</entry></row>
-<row><entry><literal><resend-message></literal></entry><entry>Esc e</entry><entry>use the current message as a template for a new one</entry></row>
-<row><entry><literal><save-message></literal></entry><entry>s</entry><entry>save message/attachment to a file</entry></row>
-<row><entry><literal><tag-pattern></literal></entry><entry>T</entry><entry>tag messages matching a pattern</entry></row>
-<row><entry><literal><tag-subthread></literal></entry><entry></entry><entry>tag the current subthread</entry></row>
-<row><entry><literal><tag-thread></literal></entry><entry>Esc t</entry><entry>tag the current thread</entry></row>
-<row><entry><literal><untag-pattern></literal></entry><entry>^T</entry><entry>untag messages matching a pattern</entry></row>
-<row><entry><literal><undelete-message></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-<row><entry><literal><undelete-pattern></literal></entry><entry>U</entry><entry>undelete messages matching a pattern</entry></row>
-<row><entry><literal><undelete-subthread></literal></entry><entry>Esc u</entry><entry>undelete all messages in subthread</entry></row>
-<row><entry><literal><undelete-thread></literal></entry><entry>^U</entry><entry>undelete all messages in thread</entry></row>
-<row><entry><literal><view-attachments></literal></entry><entry>v</entry><entry>show MIME attachments</entry></row>
-<row><entry><literal><show-version></literal></entry><entry>V</entry><entry>show the Mutt version number and date</entry></row>
-<row><entry><literal><set-flag></literal></entry><entry>w</entry><entry>set a status flag on a message</entry></row>
-<row><entry><literal><clear-flag></literal></entry><entry>W</entry><entry>clear a status flag from a message</entry></row>
-<row><entry><literal><display-message></literal></entry><entry><Return></entry><entry>display a message</entry></row>
-<row><entry><literal><buffy-list></literal></entry><entry>.</entry><entry>list mailboxes with new mail</entry></row>
-<row><entry><literal><sync-mailbox></literal></entry><entry>$</entry><entry>save changes to mailbox</entry></row>
-<row><entry><literal><display-address></literal></entry><entry>@</entry><entry>display full address of sender</entry></row>
-<row><entry><literal><pipe-message></literal></entry><entry>|</entry><entry>pipe message/attachment to a shell command</entry></row>
-<row><entry><literal><next-new></literal></entry><entry></entry><entry>jump to the next new message</entry></row>
-<row><entry><literal><next-new-then-unread></literal></entry><entry><Tab></entry><entry>jump to the next new or unread message</entry></row>
-<row><entry><literal><previous-new></literal></entry><entry></entry><entry>jump to the previous new message</entry></row>
-<row><entry><literal><previous-new-then-unread></literal></entry><entry>Esc <Tab></entry><entry>jump to the previous new or unread message</entry></row>
-<row><entry><literal><next-unread></literal></entry><entry></entry><entry>jump to the next unread message</entry></row>
-<row><entry><literal><previous-unread></literal></entry><entry></entry><entry>jump to the previous unread message</entry></row>
-<row><entry><literal><parent-message></literal></entry><entry>P</entry><entry>jump to parent message in thread</entry></row>
-<row><entry><literal><extract-keys></literal></entry><entry>^K</entry><entry>extract supported public keys</entry></row>
-<row><entry><literal><forget-passphrase></literal></entry><entry>^F</entry><entry>wipe passphrase(s) from memory</entry></row>
-<row><entry><literal><check-traditional-pgp></literal></entry><entry>Esc P</entry><entry>check for classic PGP</entry></row>
-<row><entry><literal><mail-key></literal></entry><entry>Esc k</entry><entry>mail a PGP public key</entry></row>
-<row><entry><literal><decrypt-copy></literal></entry><entry></entry><entry>make decrypted copy</entry></row>
-<row><entry><literal><decrypt-save></literal></entry><entry></entry><entry>make decrypted copy and delete</entry></row>
-<row><entry><literal><sidebar-scroll-up></literal></entry><entry></entry><entry>scroll the mailbox pane up 1 page</entry></row>
-<row><entry><literal><sidebar-scroll-down></literal></entry><entry></entry><entry>scroll the mailbox pane down 1 page</entry></row>
-<row><entry><literal><sidebar-next></literal></entry><entry></entry><entry>go down to next mailbox</entry></row>
-<row><entry><literal><sidebar-prev></literal></entry><entry></entry><entry>go to previous mailbox</entry></row>
-<row><entry><literal><sidebar-open></literal></entry><entry></entry><entry>open hilighted mailbox</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="pager_map">
-<title>pager menu</title>
-
-
-<table id="pager_table">
-<title>Default pager function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><break-thread></literal></entry><entry>#</entry><entry>break the thread in two</entry></row>
-<row><entry><literal><create-alias></literal></entry><entry>a</entry><entry>create an alias from a message sender</entry></row>
-<row><entry><literal><bounce-message></literal></entry><entry>b</entry><entry>remail a message to another user</entry></row>
-<row><entry><literal><change-folder></literal></entry><entry>c</entry><entry>open a different folder</entry></row>
-<row><entry><literal><change-folder-readonly></literal></entry><entry>Esc c</entry><entry>open a different folder in read only mode</entry></row>
-<row><entry><literal><next-unread-mailbox></literal></entry><entry></entry><entry>open next mailbox with new mail</entry></row>
-<row><entry><literal><copy-message></literal></entry><entry>C</entry><entry>copy a message to a file/mailbox</entry></row>
-<row><entry><literal><decode-copy></literal></entry><entry>Esc C</entry><entry>make decoded (text/plain) copy</entry></row>
-<row><entry><literal><delete-message></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><delete-thread></literal></entry><entry>^D</entry><entry>delete all messages in thread</entry></row>
-<row><entry><literal><delete-subthread></literal></entry><entry>Esc d</entry><entry>delete all messages in subthread</entry></row>
-<row><entry><literal><edit></literal></entry><entry>e</entry><entry>edit the raw message</entry></row>
-<row><entry><literal><edit-type></literal></entry><entry>^E</entry><entry>edit attachment content type</entry></row>
-<row><entry><literal><forward-message></literal></entry><entry>f</entry><entry>forward a message with comments</entry></row>
-<row><entry><literal><flag-message></literal></entry><entry>F</entry><entry>toggle a message's 'important' flag</entry></row>
-<row><entry><literal><group-reply></literal></entry><entry>g</entry><entry>reply to all recipients</entry></row>
-<row><entry><literal><imap-fetch-mail></literal></entry><entry></entry><entry>force retrieval of mail from IMAP server</entry></row>
-<row><entry><literal><display-toggle-weed></literal></entry><entry>h</entry><entry>display message and toggle header weeding</entry></row>
-<row><entry><literal><next-undeleted></literal></entry><entry>j</entry><entry>move to the next undeleted message</entry></row>
-<row><entry><literal><next-entry></literal></entry><entry>J</entry><entry>move to the next entry</entry></row>
-<row><entry><literal><previous-undeleted></literal></entry><entry>k</entry><entry>move to the previous undeleted message</entry></row>
-<row><entry><literal><previous-entry></literal></entry><entry>K</entry><entry>move to the previous entry</entry></row>
-<row><entry><literal><link-threads></literal></entry><entry>&</entry><entry>link tagged message to the current one</entry></row>
-<row><entry><literal><list-reply></literal></entry><entry>L</entry><entry>reply to specified mailing list</entry></row>
-<row><entry><literal><redraw-screen></literal></entry><entry>^L</entry><entry>clear and redraw the screen</entry></row>
-<row><entry><literal><mail></literal></entry><entry>m</entry><entry>compose a new mail message</entry></row>
-<row><entry><literal><mark-as-new></literal></entry><entry>N</entry><entry>toggle a message's 'new' flag</entry></row>
-<row><entry><literal><search-next></literal></entry><entry>n</entry><entry>search for next match</entry></row>
-<row><entry><literal><next-thread></literal></entry><entry>^N</entry><entry>jump to the next thread</entry></row>
-<row><entry><literal><next-subthread></literal></entry><entry>Esc n</entry><entry>jump to the next subthread</entry></row>
-<row><entry><literal><print-message></literal></entry><entry>p</entry><entry>print the current entry</entry></row>
-<row><entry><literal><previous-thread></literal></entry><entry>^P</entry><entry>jump to previous thread</entry></row>
-<row><entry><literal><previous-subthread></literal></entry><entry>Esc p</entry><entry>jump to previous subthread</entry></row>
-<row><entry><literal><purge-message></literal></entry><entry></entry><entry>really delete the current entry, bypassing the trash folder</entry></row>
-<row><entry><literal><quit></literal></entry><entry>Q</entry><entry>save changes to mailbox and quit</entry></row>
-<row><entry><literal><exit></literal></entry><entry>q</entry><entry>exit this menu</entry></row>
-<row><entry><literal><reply></literal></entry><entry>r</entry><entry>reply to a message</entry></row>
-<row><entry><literal><recall-message></literal></entry><entry>R</entry><entry>recall a postponed message</entry></row>
-<row><entry><literal><read-thread></literal></entry><entry>^R</entry><entry>mark the current thread as read</entry></row>
-<row><entry><literal><read-subthread></literal></entry><entry>Esc r</entry><entry>mark the current subthread as read</entry></row>
-<row><entry><literal><resend-message></literal></entry><entry>Esc e</entry><entry>use the current message as a template for a new one</entry></row>
-<row><entry><literal><save-message></literal></entry><entry>s</entry><entry>save message/attachment to a file</entry></row>
-<row><entry><literal><skip-quoted></literal></entry><entry>S</entry><entry>skip beyond quoted text</entry></row>
-<row><entry><literal><decode-save></literal></entry><entry>Esc s</entry><entry>make decoded copy (text/plain) and delete</entry></row>
-<row><entry><literal><tag-message></literal></entry><entry>t</entry><entry>tag the current entry</entry></row>
-<row><entry><literal><toggle-quoted></literal></entry><entry>T</entry><entry>toggle display of quoted text</entry></row>
-<row><entry><literal><undelete-message></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-<row><entry><literal><undelete-subthread></literal></entry><entry>Esc u</entry><entry>undelete all messages in subthread</entry></row>
-<row><entry><literal><undelete-thread></literal></entry><entry>^U</entry><entry>undelete all messages in thread</entry></row>
-<row><entry><literal><view-attachments></literal></entry><entry>v</entry><entry>show MIME attachments</entry></row>
-<row><entry><literal><show-version></literal></entry><entry>V</entry><entry>show the Mutt version number and date</entry></row>
-<row><entry><literal><search-toggle></literal></entry><entry>\\</entry><entry>toggle search pattern coloring</entry></row>
-<row><entry><literal><display-address></literal></entry><entry>@</entry><entry>display full address of sender</entry></row>
-<row><entry><literal><next-new></literal></entry><entry></entry><entry>jump to the next new message</entry></row>
-<row><entry><literal><pipe-message></literal></entry><entry>|</entry><entry>pipe message/attachment to a shell command</entry></row>
-<row><entry><literal><help></literal></entry><entry>?</entry><entry>this screen</entry></row>
-<row><entry><literal><next-page></literal></entry><entry><Space></entry><entry>move to the next page</entry></row>
-<row><entry><literal><previous-page></literal></entry><entry>-</entry><entry>move to the previous page</entry></row>
-<row><entry><literal><top></literal></entry><entry>^</entry><entry>jump to the top of the message</entry></row>
-<row><entry><literal><sync-mailbox></literal></entry><entry>$</entry><entry>save changes to mailbox</entry></row>
-<row><entry><literal><shell-escape></literal></entry><entry>!</entry><entry>invoke a command in a subshell</entry></row>
-<row><entry><literal><enter-command></literal></entry><entry>:</entry><entry>enter a muttrc command</entry></row>
-<row><entry><literal><buffy-list></literal></entry><entry>.</entry><entry>list mailboxes with new mail</entry></row>
-<row><entry><literal><search></literal></entry><entry>/</entry><entry>search for a regular expression</entry></row>
-<row><entry><literal><search-reverse></literal></entry><entry>Esc /</entry><entry>search backwards for a regular expression</entry></row>
-<row><entry><literal><search-opposite></literal></entry><entry></entry><entry>search for next match in opposite direction</entry></row>
-<row><entry><literal><next-line></literal></entry><entry><Return></entry><entry>scroll down one line</entry></row>
-<row><entry><literal><jump></literal></entry><entry></entry><entry>jump to an index number</entry></row>
-<row><entry><literal><next-unread></literal></entry><entry></entry><entry>jump to the next unread message</entry></row>
-<row><entry><literal><previous-new></literal></entry><entry></entry><entry>jump to the previous new message</entry></row>
-<row><entry><literal><previous-unread></literal></entry><entry></entry><entry>jump to the previous unread message</entry></row>
-<row><entry><literal><half-up></literal></entry><entry></entry><entry>scroll up 1/2 page</entry></row>
-<row><entry><literal><half-down></literal></entry><entry></entry><entry>scroll down 1/2 page</entry></row>
-<row><entry><literal><previous-line></literal></entry><entry></entry><entry>scroll up one line</entry></row>
-<row><entry><literal><bottom></literal></entry><entry></entry><entry>jump to the bottom of the message</entry></row>
-<row><entry><literal><parent-message></literal></entry><entry>P</entry><entry>jump to parent message in thread</entry></row>
-<row><entry><literal><check-traditional-pgp></literal></entry><entry>Esc P</entry><entry>check for classic PGP</entry></row>
-<row><entry><literal><mail-key></literal></entry><entry>Esc k</entry><entry>mail a PGP public key</entry></row>
-<row><entry><literal><extract-keys></literal></entry><entry>^K</entry><entry>extract supported public keys</entry></row>
-<row><entry><literal><forget-passphrase></literal></entry><entry>^F</entry><entry>wipe passphrase(s) from memory</entry></row>
-<row><entry><literal><decrypt-copy></literal></entry><entry></entry><entry>make decrypted copy</entry></row>
-<row><entry><literal><decrypt-save></literal></entry><entry></entry><entry>make decrypted copy and delete</entry></row>
-<row><entry><literal><what-key></literal></entry><entry></entry><entry>display the keycode for a key press</entry></row>
-<row><entry><literal><sidebar-scroll-up></literal></entry><entry></entry><entry>scroll the mailbox pane up 1 page</entry></row>
-<row><entry><literal><sidebar-scroll-down></literal></entry><entry></entry><entry>scroll the mailbox pane down 1 page</entry></row>
-<row><entry><literal><sidebar-next></literal></entry><entry></entry><entry>go down to next mailbox</entry></row>
-<row><entry><literal><sidebar-prev></literal></entry><entry></entry><entry>go to previous mailbox</entry></row>
-<row><entry><literal><sidebar-open></literal></entry><entry></entry><entry>open hilighted mailbox</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="alias_map">
-<title>alias menu</title>
-
-
-<table id="alias_table">
-<title>Default alias function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><delete-entry></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><undelete-entry></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="query_map">
-<title>query menu</title>
-
-
-<table id="query_table">
-<title>Default query function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><create-alias></literal></entry><entry>a</entry><entry>create an alias from a message sender</entry></row>
-<row><entry><literal><mail></literal></entry><entry>m</entry><entry>compose a new mail message</entry></row>
-<row><entry><literal><query></literal></entry><entry>Q</entry><entry>query external program for addresses</entry></row>
-<row><entry><literal><query-append></literal></entry><entry>A</entry><entry>append new query results to current results</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="attach_map">
-<title>attach menu</title>
-
-
-<table id="attach_table">
-<title>Default attach function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><bounce-message></literal></entry><entry>b</entry><entry>remail a message to another user</entry></row>
-<row><entry><literal><display-toggle-weed></literal></entry><entry>h</entry><entry>display message and toggle header weeding</entry></row>
-<row><entry><literal><edit-type></literal></entry><entry>^E</entry><entry>edit attachment content type</entry></row>
-<row><entry><literal><print-entry></literal></entry><entry>p</entry><entry>print the current entry</entry></row>
-<row><entry><literal><save-entry></literal></entry><entry>s</entry><entry>save message/attachment to a file</entry></row>
-<row><entry><literal><pipe-entry></literal></entry><entry>|</entry><entry>pipe message/attachment to a shell command</entry></row>
-<row><entry><literal><view-mailcap></literal></entry><entry>m</entry><entry>force viewing of attachment using mailcap</entry></row>
-<row><entry><literal><reply></literal></entry><entry>r</entry><entry>reply to a message</entry></row>
-<row><entry><literal><resend-message></literal></entry><entry>Esc e</entry><entry>use the current message as a template for a new one</entry></row>
-<row><entry><literal><group-reply></literal></entry><entry>g</entry><entry>reply to all recipients</entry></row>
-<row><entry><literal><list-reply></literal></entry><entry>L</entry><entry>reply to specified mailing list</entry></row>
-<row><entry><literal><forward-message></literal></entry><entry>f</entry><entry>forward a message with comments</entry></row>
-<row><entry><literal><view-text></literal></entry><entry>T</entry><entry>view attachment as text</entry></row>
-<row><entry><literal><view-attach></literal></entry><entry><Return></entry><entry>view attachment using mailcap entry if necessary</entry></row>
-<row><entry><literal><delete-entry></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><undelete-entry></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-<row><entry><literal><collapse-parts></literal></entry><entry>v</entry><entry>Toggle display of subparts</entry></row>
-<row><entry><literal><check-traditional-pgp></literal></entry><entry>Esc P</entry><entry>check for classic PGP</entry></row>
-<row><entry><literal><extract-keys></literal></entry><entry>^K</entry><entry>extract supported public keys</entry></row>
-<row><entry><literal><forget-passphrase></literal></entry><entry>^F</entry><entry>wipe passphrase(s) from memory</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="compose_map">
-<title>compose menu</title>
-
-
-<table id="compose_table">
-<title>Default compose function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><attach-file></literal></entry><entry>a</entry><entry>attach file(s) to this message</entry></row>
-<row><entry><literal><attach-message></literal></entry><entry>A</entry><entry>attach message(s) to this message</entry></row>
-<row><entry><literal><edit-bcc></literal></entry><entry>b</entry><entry>edit the BCC list</entry></row>
-<row><entry><literal><edit-cc></literal></entry><entry>c</entry><entry>edit the CC list</entry></row>
-<row><entry><literal><copy-file></literal></entry><entry>C</entry><entry>save message/attachment to a file</entry></row>
-<row><entry><literal><detach-file></literal></entry><entry>D</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><toggle-disposition></literal></entry><entry>^D</entry><entry>toggle disposition between inline/attachment</entry></row>
-<row><entry><literal><edit-description></literal></entry><entry>d</entry><entry>edit attachment description</entry></row>
-<row><entry><literal><edit-message></literal></entry><entry>e</entry><entry>edit the message</entry></row>
-<row><entry><literal><edit-headers></literal></entry><entry>E</entry><entry>edit the message with headers</entry></row>
-<row><entry><literal><edit-file></literal></entry><entry>^X e</entry><entry>edit the file to be attached</entry></row>
-<row><entry><literal><edit-encoding></literal></entry><entry>^E</entry><entry>edit attachment transfer-encoding</entry></row>
-<row><entry><literal><edit-from></literal></entry><entry>Esc f</entry><entry>edit the from field</entry></row>
-<row><entry><literal><edit-fcc></literal></entry><entry>f</entry><entry>enter a file to save a copy of this message in</entry></row>
-<row><entry><literal><filter-entry></literal></entry><entry>F</entry><entry>filter attachment through a shell command</entry></row>
-<row><entry><literal><get-attachment></literal></entry><entry>G</entry><entry>get a temporary copy of an attachment</entry></row>
-<row><entry><literal><display-toggle-weed></literal></entry><entry>h</entry><entry>display message and toggle header weeding</entry></row>
-<row><entry><literal><ispell></literal></entry><entry>i</entry><entry>run ispell on the message</entry></row>
-<row><entry><literal><print-entry></literal></entry><entry>l</entry><entry>print the current entry</entry></row>
-<row><entry><literal><edit-mime></literal></entry><entry>m</entry><entry>edit attachment using mailcap entry</entry></row>
-<row><entry><literal><new-mime></literal></entry><entry>n</entry><entry>compose new attachment using mailcap entry</entry></row>
-<row><entry><literal><postpone-message></literal></entry><entry>P</entry><entry>save this message to send later</entry></row>
-<row><entry><literal><edit-reply-to></literal></entry><entry>r</entry><entry>edit the Reply-To field</entry></row>
-<row><entry><literal><rename-file></literal></entry><entry>R</entry><entry>rename/move an attached file</entry></row>
-<row><entry><literal><edit-subject></literal></entry><entry>s</entry><entry>edit the subject of this message</entry></row>
-<row><entry><literal><edit-to></literal></entry><entry>t</entry><entry>edit the TO list</entry></row>
-<row><entry><literal><edit-type></literal></entry><entry>^T</entry><entry>edit attachment content type</entry></row>
-<row><entry><literal><write-fcc></literal></entry><entry>w</entry><entry>write the message to a folder</entry></row>
-<row><entry><literal><toggle-unlink></literal></entry><entry>u</entry><entry>toggle whether to delete file after sending it</entry></row>
-<row><entry><literal><toggle-recode></literal></entry><entry></entry><entry>toggle recoding of this attachment</entry></row>
-<row><entry><literal><update-encoding></literal></entry><entry>U</entry><entry>update an attachment's encoding info</entry></row>
-<row><entry><literal><view-attach></literal></entry><entry><Return></entry><entry>view attachment using mailcap entry if necessary</entry></row>
-<row><entry><literal><send-message></literal></entry><entry>y</entry><entry>send the message</entry></row>
-<row><entry><literal><pipe-entry></literal></entry><entry>|</entry><entry>pipe message/attachment to a shell command</entry></row>
-<row><entry><literal><attach-key></literal></entry><entry>Esc k</entry><entry>attach a PGP public key</entry></row>
-<row><entry><literal><pgp-menu></literal></entry><entry>p</entry><entry>show PGP options</entry></row>
-<row><entry><literal><forget-passphrase></literal></entry><entry>^F</entry><entry>wipe passphrase(s) from memory</entry></row>
-<row><entry><literal><smime-menu></literal></entry><entry>S</entry><entry>show S/MIME options</entry></row>
-<row><entry><literal><mix></literal></entry><entry>M</entry><entry>send the message through a mixmaster remailer chain</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="postpone_map">
-<title>postpone menu</title>
-
-
-<table id="postpone_table">
-<title>Default postpone function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><delete-entry></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><undelete-entry></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="browser_map">
-<title>browser menu</title>
-
-
-<table id="browser_table">
-<title>Default browser function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><change-dir></literal></entry><entry>c</entry><entry>change directories</entry></row>
-<row><entry><literal><display-filename></literal></entry><entry>@</entry><entry>display the currently selected file's name</entry></row>
-<row><entry><literal><enter-mask></literal></entry><entry>m</entry><entry>enter a file mask</entry></row>
-<row><entry><literal><sort></literal></entry><entry>o</entry><entry>sort messages</entry></row>
-<row><entry><literal><sort-reverse></literal></entry><entry>O</entry><entry>sort messages in reverse order</entry></row>
-<row><entry><literal><select-new></literal></entry><entry>N</entry><entry>select a new file in this directory</entry></row>
-<row><entry><literal><check-new></literal></entry><entry></entry><entry>check mailboxes for new mail</entry></row>
-<row><entry><literal><toggle-mailboxes></literal></entry><entry><Tab></entry><entry>toggle whether to browse mailboxes or all files</entry></row>
-<row><entry><literal><view-file></literal></entry><entry><Space></entry><entry>view file</entry></row>
-<row><entry><literal><buffy-list></literal></entry><entry>.</entry><entry>list mailboxes with new mail</entry></row>
-<row><entry><literal><create-mailbox></literal></entry><entry>C</entry><entry>create a new mailbox (IMAP only)</entry></row>
-<row><entry><literal><delete-mailbox></literal></entry><entry>d</entry><entry>delete the current mailbox (IMAP only)</entry></row>
-<row><entry><literal><rename-mailbox></literal></entry><entry>r</entry><entry>rename the current mailbox (IMAP only)</entry></row>
-<row><entry><literal><subscribe></literal></entry><entry>s</entry><entry>subscribe to current mailbox (IMAP only)</entry></row>
-<row><entry><literal><unsubscribe></literal></entry><entry>u</entry><entry>unsubscribe from current mailbox (IMAP only)</entry></row>
-<row><entry><literal><toggle-subscribed></literal></entry><entry>T</entry><entry>toggle view all/subscribed mailboxes (IMAP only)</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="pgp_map">
-<title>pgp menu</title>
-
-
-<table id="pgp_table">
-<title>Default pgp function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><verify-key></literal></entry><entry>c</entry><entry>verify a PGP public key</entry></row>
-<row><entry><literal><view-name></literal></entry><entry>%</entry><entry>view the key's user id</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="smime_map">
-<title>smime menu</title>
-
-
-<table id="smime_table">
-<title>Default smime function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><verify-key></literal></entry><entry>c</entry><entry>verify a PGP public key</entry></row>
-<row><entry><literal><view-name></literal></entry><entry>%</entry><entry>view the key's user id</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="mix_map">
-<title>mix menu</title>
-
-
-<table id="mix_table">
-<title>Default mix function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><accept></literal></entry><entry><Return></entry><entry>Accept the chain constructed</entry></row>
-<row><entry><literal><append></literal></entry><entry>a</entry><entry>Append a remailer to the chain</entry></row>
-<row><entry><literal><insert></literal></entry><entry>i</entry><entry>Insert a remailer into the chain</entry></row>
-<row><entry><literal><delete></literal></entry><entry>d</entry><entry>Delete a remailer from the chain</entry></row>
-<row><entry><literal><chain-prev></literal></entry><entry><Left></entry><entry>Select the previous element of the chain</entry></row>
-<row><entry><literal><chain-next></literal></entry><entry><Right></entry><entry>Select the next element of the chain</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="editor_map">
-<title>editor menu</title>
-
-
-<table id="editor_table">
-<title>Default editor function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><bol></literal></entry><entry>^A</entry><entry>jump to the beginning of the line</entry></row>
-<row><entry><literal><backward-char></literal></entry><entry>^B</entry><entry>move the cursor one character to the left</entry></row>
-<row><entry><literal><backward-word></literal></entry><entry>Esc b</entry><entry>move the cursor to the beginning of the word</entry></row>
-<row><entry><literal><capitalize-word></literal></entry><entry>Esc c</entry><entry>capitalize the word</entry></row>
-<row><entry><literal><downcase-word></literal></entry><entry>Esc l</entry><entry>convert the word to lower case</entry></row>
-<row><entry><literal><upcase-word></literal></entry><entry>Esc u</entry><entry>convert the word to upper case</entry></row>
-<row><entry><literal><delete-char></literal></entry><entry>^D</entry><entry>delete the char under the cursor</entry></row>
-<row><entry><literal><eol></literal></entry><entry>^E</entry><entry>jump to the end of the line</entry></row>
-<row><entry><literal><forward-char></literal></entry><entry>^F</entry><entry>move the cursor one character to the right</entry></row>
-<row><entry><literal><forward-word></literal></entry><entry>Esc f</entry><entry>move the cursor to the end of the word</entry></row>
-<row><entry><literal><backspace></literal></entry><entry><Backspace></entry><entry>delete the char in front of the cursor</entry></row>
-<row><entry><literal><kill-eol></literal></entry><entry>^K</entry><entry>delete chars from cursor to end of line</entry></row>
-<row><entry><literal><kill-eow></literal></entry><entry>Esc d</entry><entry>delete chars from the cursor to the end of the word</entry></row>
-<row><entry><literal><kill-line></literal></entry><entry>^U</entry><entry>delete all chars on the line</entry></row>
-<row><entry><literal><quote-char></literal></entry><entry>^V</entry><entry>quote the next typed key</entry></row>
-<row><entry><literal><kill-word></literal></entry><entry>^W</entry><entry>delete the word in front of the cursor</entry></row>
-<row><entry><literal><complete></literal></entry><entry><Tab></entry><entry>complete filename or alias</entry></row>
-<row><entry><literal><complete-query></literal></entry><entry>^T</entry><entry>complete address with query</entry></row>
-<row><entry><literal><buffy-cycle></literal></entry><entry><Space></entry><entry>cycle among incoming mailboxes</entry></row>
-<row><entry><literal><history-up></literal></entry><entry></entry><entry>scroll up through the history list</entry></row>
-<row><entry><literal><history-down></literal></entry><entry></entry><entry>scroll down through the history list</entry></row>
-<row><entry><literal><transpose-chars></literal></entry><entry></entry><entry>transpose character under cursor with previous</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-
-</sect1>
-
-</chapter>
-
-<chapter id="miscellany">
-<title>Miscellany</title>
-
-<sect1 id="acknowledgements">
-<title>Acknowledgements</title>
-
-<para>
-Kari Hurtta <email>kari.hurtta@fmi.fi</email>
-co-developed the original MIME parsing code back in the ELM-ME days.
-</para>
-
-<para>
-The following people have been very helpful to the development of Mutt:
-</para>
-
-<itemizedlist>
-<listitem><para>Vikas Agnihotri <email>vikasa@writeme.com</email></para></listitem>
-<listitem><para>Francois Berjon <email>Francois.Berjon@aar.alcatel-alsthom.fr</email></para></listitem>
-<listitem><para>Aric Blumer <email>aric@fore.com</email></para></listitem>
-<listitem><para>John Capo <email>jc@irbs.com</email></para></listitem>
-<listitem><para>David Champion <email>dgc@uchicago.edu</email></para></listitem>
-<listitem><para>Brendan Cully <email>brendan@kublai.com</email></para></listitem>
-<listitem><para>Liviu Daia <email>daia@stoilow.imar.ro</email></para></listitem>
-<listitem><para>Thomas E. Dickey <email>dickey@herndon4.his.com</email></para></listitem>
-<listitem><para>David DeSimone <email>fox@convex.hp.com</email></para></listitem>
-<listitem><para>Nickolay N. Dudorov <email>nnd@wint.itfs.nsk.su</email></para></listitem>
-<listitem><para>Ruslan Ermilov <email>ru@freebsd.org</email></para></listitem>
-<listitem><para>Edmund Grimley Evans <email>edmundo@rano.org</email></para></listitem>
-<listitem><para>Michael Finken <email>finken@conware.de</email></para></listitem>
-<listitem><para>Sven Guckes <email>guckes@math.fu-berlin.de</email></para></listitem>
-<listitem><para>Lars Hecking <email>lhecking@nmrc.ie</email></para></listitem>
-<listitem><para>Mark Holloman <email>holloman@nando.net</email></para></listitem>
-<listitem><para>Andreas Holzmann <email>holzmann@fmi.uni-passau.de</email></para></listitem>
-<listitem><para>Marco d'Itri <email>md@linux.it</email></para></listitem>
-<listitem><para>Björn Jacke <email>bjacke@suse.com</email></para></listitem>
-<listitem><para>Byrial Jensen <email>byrial@image.dk</email></para></listitem>
-<listitem><para>David Jeske <email>jeske@igcom.net</email></para></listitem>
-<listitem><para>Christophe Kalt <email>kalt@hugo.int-evry.fr</email></para></listitem>
-<listitem><para>Tommi Komulainen <email>Tommi.Komulainen@iki.fi</email></para></listitem>
-<listitem><para>Felix von Leitner (a.k.a <quote>Fefe</quote>) <email>leitner@math.fu-berlin.de</email></para></listitem>
-<listitem><para>Brandon Long <email>blong@fiction.net</email></para></listitem>
-<listitem><para>Jimmy Mäkelä <email>jmy@flashback.net</email></para></listitem>
-<listitem><para>Lars Marowsky-Bree <email>lmb@pointer.in-minden.de</email></para></listitem>
-<listitem><para>Thomas <quote>Mike</quote> Michlmayr <email>mike@cosy.sbg.ac.at</email></para></listitem>
-<listitem><para>Andrew W. Nosenko <email>awn@bcs.zp.ua</email></para></listitem>
-<listitem><para>David O'Brien <email>obrien@Nuxi.cs.ucdavis.edu</email></para></listitem>
-<listitem><para>Clint Olsen <email>olsenc@ichips.intel.com</email></para></listitem>
-<listitem><para>Park Myeong Seok <email>pms@romance.kaist.ac.kr</email></para></listitem>
-<listitem><para>Thomas Parmelan <email>tom@ankh.fr.eu.org</email></para></listitem>
-<listitem><para>Ollivier Robert <email>roberto@keltia.freenix.fr</email></para></listitem>
-<listitem><para>Thomas Roessler <email>roessler@does-not-exist.org</email></para></listitem>
-<listitem><para>Roland Rosenfeld <email>roland@spinnaker.de</email></para></listitem>
-<listitem><para>Rocco Rutte <email>pdmef@gmx.net</email></para></listitem>
-<listitem><para>TAKIZAWA Takashi <email>taki@luna.email.ne.jp</email></para></listitem>
-<listitem><para>Allain Thivillon <email>Allain.Thivillon@alma.fr</email></para></listitem>
-<listitem><para>Gero Treuner <email>gero@70t.de</email></para></listitem>
-<listitem><para>Vsevolod Volkov <email>vvv@lucky.net</email></para></listitem>
-<listitem><para>Ken Weinert <email>kenw@ihs.com</email></para></listitem>
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="about">
-<title>About this document</title>
-
-<para>
-This document was written in <ulink url="http://docbook.sourceforge.net">DocBook</ulink>,
-and then rendered using the <ulink url="http://xmlsoft.org/XSLT/">Gnome XSLT toolkit</ulink>.
-</para>
-
-</sect1>
-
-</chapter>
-
-</book>
-
-<!--
-vim:ft=xml
--->
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 5. Mutt's MIME Support</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="advancedusage.html" title="Chapter 4. Advanced Usage" /><link rel="next" href="optionalfeatures.html" title="Chapter 6. Optional features" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 5. Mutt's MIME Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="advancedusage.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="optionalfeatures.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="mimesupport"></a>Chapter 5. Mutt's MIME Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="mimesupport.html#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="mimesupport.html#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="mimesupport.html#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="mimesupport.html#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="mimesupport.html#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="mimesupport.html#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#mime-lookup">7. MIME Lookup</a></span></dt></dl></div><p>
-Quite a bit of effort has been made to make Mutt 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 for MIME, there are two extra
-types of configuration files which Mutt uses. One is the
-<code class="literal">mime.types</code> file, which contains the mapping of file extensions to
-IANA MIME types. The other is the <code class="literal">mailcap</code> file, which specifies
-the external commands to use for handling specific MIME types.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-mime"></a>1. Using MIME in Mutt</h2></div></div></div><p>
-There are three areas/menus in Mutt which deal with MIME, they are the
-pager (while viewing a message), the attachment menu and the compose
-menu.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-pager"></a>1.1. Viewing MIME messages in the pager</h3></div></div></div><p>
-When you select a message from the index and view it in the pager, Mutt
-decodes the message to a text representation. Mutt internally supports
-a number of MIME types, including <code class="literal">text/plain, text/enriched,
-message/rfc822, and message/news</code>. In addition, the export
-controlled version of Mutt recognizes a variety of PGP MIME types,
-including PGP/MIME and application/pgp.
-</p><p>
-Mutt will denote attachments with a couple lines describing them.
-These lines are of the form:
-</p><pre class="screen">
-[-- Attachment #1: Description --]
-[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-</pre><p>
-Where the <code class="literal">Description</code> is the description or filename given for the
-attachment, and the <code class="literal">Encoding</code> is one of
-<code class="literal">7bit/8bit/quoted-printable/base64/binary</code>.
-</p><p>
-If Mutt cannot deal with a MIME type, it will display a message like:
-</p><pre class="screen">
-[-- image/gif is unsupported (use 'v' to view this part) --]
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-menu"></a>1.2. The Attachment Menu</h3></div></div></div><p>
-The default binding for <code class="literal">view-attachments</code> is `v', which displays the
-attachment menu for a message. The attachment menu displays a list of
-the 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 “<span class="quote">tag-prefix</span>” 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.
-</p><p>
-Finally, you can apply the usual message-related functions (like
-<a class="link" href="gettingstarted.html#resend-message"><code class="literal"><resend-message></code></a>, and the
-<code class="literal"><reply></code> and <code class="literal"><forward></code>
-functions) to attachments of type <code class="literal">message/rfc822</code>.
-</p><p>
-See the help on the attachment menu for more information.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-menu"></a>1.3. The Compose Menu</h3></div></div></div><p>
-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.
-</p><p>
-Attachments appear as follows:
-</p><pre class="screen">
-- 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>
-</pre><p>
-The '-' denotes that Mutt will delete the file after sending (or
-postponing, or canceling) the message. It can be toggled with the
-<code class="literal">toggle-unlink</code> command (default: u). The next field is the MIME
-content-type, and can be changed with the <code class="literal">edit-type</code> 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 <code class="literal">edit-encoding</code> 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 <code class="literal">rename-file</code> command (default: R).
-The final field is the description of the attachment, and can be
-changed with the <code class="literal">edit-description</code> command (default: d).
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-types"></a>2. MIME Type configuration with <code class="literal">mime.types</code></h2></div></div></div><p>
-When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at <code class="literal">${HOME}/.mime.types</code>, and then
-the system mime.types file at <code class="literal">/usr/local/share/mutt/mime.types</code> or
-<code class="literal">/etc/mime.types</code>
-</p><p>
-The mime.types file consist of lines containing a MIME type and a space
-separated list of extensions. For example:
-</p><pre class="screen">
-application/postscript ps eps
-application/pgp pgp
-audio/x-aiff aif aifc aiff
-</pre><p>
-A sample <code class="literal">mime.types</code> file comes with the Mutt distribution, and
-should contain most of the MIME types you are likely to use.
-</p><p>
-If Mutt 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 will assume that the file is plain text, and mark it
-as <code class="literal">text/plain</code>. If the file contains binary information, then Mutt will
-mark it as <code class="literal">application/octet-stream</code>. You can change the MIME
-type that Mutt assigns to an attachment by using the <code class="literal">edit-type</code>
-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 recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
-major mime types, such as the chemical type that is widely used in the
-molecular modeling community to pass molecular data in various forms to
-various molecular viewers. Non-recognized mime types should only be used
-if the recipient of the message is likely to be expecting such attachments.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailcap"></a>3. MIME Viewer configuration with <code class="literal">mailcap</code></h2></div></div></div><p>
-Mutt supports RFC 1524 MIME Configuration, in particular the Unix
-specific format specified in Appendix A of RFC 1524. 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.
-</p><p>
-In order to handle various MIME types that Mutt can not handle
-internally, Mutt parses a series of external configuration files to
-find an external handler. The default search string for these files
-is a colon delimited list containing the following files:
-</p><div class="orderedlist"><ol type="1"><li><p><code class="literal">$HOME/.mailcap</code></p></li><li><p><code class="literal">$PKGDATADIR/mailcap</code></p></li><li><p><code class="literal">$SYSCONFDIR/mailcap</code></p></li><li><p><code class="literal">/etc/mailcap</code></p></li><li><p><code class="literal">/usr/etc/mailcap</code></p></li><li><p><code class="literal">/usr/local/etc/mailcap</code></p></li></ol></div><p>
-where <code class="literal">$HOME</code> is your home directory. The
-<code class="literal">$PKGDATADIR</code> and the
-<code class="literal">$SYSCONFDIR</code> directories depend on where mutt
-is installed: the former is the default for shared data, the
-latter for system configuration files.
-</p><p>
-The default search path can be obtained by running the following
-command:
-</p><pre class="screen">
-mutt -nF /dev/null -Q mailcap_path
-</pre><p>
-In particular, the metamail distribution will install a mailcap file,
-usually as <code class="literal">/usr/local/etc/mailcap</code>, which contains some baseline
-entries.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-basics"></a>3.1. The Basics of the mailcap file</h3></div></div></div><p>
-A mailcap file consists of a series of lines which are comments, blank,
-or definitions.
-</p><p>
-A comment line consists of a # character followed by anything you want.
-</p><p>
-A blank line is blank.
-</p><p>
-A definition line consists of a content type, a view command, and any
-number of optional fields. Each field of a definition line is divided
-by a semicolon ';' character.
-</p><p>
-The content type is specified in the MIME standard type/subtype method.
-For example,
-<code class="literal">text/plain, text/html, image/gif, </code>
-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, <code class="literal">image/*</code>, or
-<code class="literal">video,</code> will match all image types and video types,
-respectively.
-</p><p>
-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 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 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.
-</p><p>
-So, in the simplest form, you can send a text/plain message to the
-external pager more on stdin:
-</p><pre class="screen">
-text/plain; more
-</pre><p>
-Or, you could send the message as a file:
-</p><pre class="screen">
-text/plain; more %s
-</pre><p>
-Perhaps you would like to use lynx to interactively view a text/html
-message:
-</p><pre class="screen">
-text/html; lynx %s
-</pre><p>
-In this case, lynx does not support viewing a file from stdin, so you
-must use the %s syntax.
-</p><div class="note"><h3 class="title">Note</h3><p>
-<span class="emphasis"><em>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.</em></span>
-</p></div><p>
-On the other hand, maybe you don't want to use lynx interactively, you
-just want to have it convert the text/html to text/plain, then you can
-use:
-</p><pre class="screen">
-text/html; lynx -dump %s | more
-</pre><p>
-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:
-</p><pre class="screen">
-text/html; lynx %s
-text/*; more
-</pre><p>
-This is the simplest form of a mailcap file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="secure-mailcap"></a>3.2. Secure use of mailcap</h3></div></div></div><p>
-The interpretation of shell meta-characters embedded in MIME parameters
-can lead to security problems in general. Mutt tries to quote parameters
-in expansion of %s syntaxes properly, and avoids risky characters by
-substituting them, see the <a class="link" href="reference.html#mailcap-sanitize" title="3.107. mailcap_sanitize">$mailcap_sanitize</a> variable.
-</p><p>
-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:
-</p><p>
-<span class="emphasis"><em>Keep the %-expandos away from shell quoting.</em></span>
-Don't quote them with single or double quotes. Mutt 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 behavior with quotes introduces new leaks - there is no
-alternative to correct quoting in the first place.
-</p><p>
-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 <code class="literal">$charset</code> inside the backtick expansion is safe,
-since it is not itself subject to any further expansion):
-</p><pre class="screen">
-text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="advanced-mailcap"></a>3.3. Advanced mailcap Usage</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="optional-mailcap-fields"></a>3.3.1. Optional Fields</h4></div></div></div><p>
-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 recognizes the following optional fields:
-</p><div class="variablelist"><dl><dt><span class="term">copiousoutput</span></dt><dd><p>
-This flag tells Mutt that the command passes possibly large amounts of
-text on stdout. This causes Mutt 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 assumes that the command
-is interactive. One could use this to replace the pipe to <code class="literal">more</code>
-in the <code class="literal">lynx -dump</code> example in the Basic section:
-</p><pre class="screen">
-text/html; lynx -dump %s ; copiousoutput
-</pre><p>
-This will cause lynx to format the text/html output as text/plain
-and Mutt will use your standard pager to display the results.
-</p></dd><dt><span class="term">needsterminal</span></dt><dd><p>
-Mutt uses this flag when viewing attachments with <a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a>, in order to decide whether it should honor the setting
-of the <a class="link" href="reference.html#wait-key" title="3.303. wait_key">$wait_key</a> variable or
-not. When an attachment is viewed using an interactive program, and the
-corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag, Mutt will use
-<a class="link" href="reference.html#wait-key" title="3.303. wait_key">$wait_key</a> and the exit status
-of 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.
-</p></dd><dt><span class="term">compose=<command></span></dt><dd><p>
-This flag specifies the command to use to create a new attachment of a
-specific MIME type. Mutt supports this from the compose menu.
-</p></dd><dt><span class="term">composetyped=<command></span></dt><dd><p>
-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 supports this from the compose menu.
-</p></dd><dt><span class="term">print=<command></span></dt><dd><p>
-This flag specifies the command to use to print a specific MIME type.
-Mutt supports this from the attachment and compose menus.
-</p></dd><dt><span class="term">edit=<command></span></dt><dd><p>
-This flag specifies the command to use to edit a specific MIME type.
-Mutt supports this from the compose menu, and also uses it to compose
-new attachments. Mutt will default to the defined editor for text
-attachments.
-</p></dd><dt><span class="term">nametemplate=<template></span></dt><dd><p>
-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 <code class="literal">text/html</code> if the file ends in <code class="literal">.html</code>.
-So, you would specify lynx as a <code class="literal">text/html</code> viewer with a line in
-the mailcap file like:
-</p><pre class="screen">
-text/html; lynx %s; nametemplate=%s.html
-</pre></dd><dt><span class="term">test=<command></span></dt><dd><p>
-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 uses this entry. If the command returns non-zero,
-then the test failed, and Mutt continues searching for the right entry.
-Note that the content-type must match before Mutt performs the test.
-For example:
-</p><pre class="screen">
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s
-</pre><p>
-In this example, Mutt 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 will call netscape to display the
-text/html object. If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
-</p></dd></dl></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-search-order"></a>3.3.2. Search Order</h4></div></div></div><p>
-When searching for an entry in the mailcap file, Mutt will search for
-the most useful entry for its purpose. For instance, if you are
-attempting to print an <code class="literal">image/gif</code>, and you have the following
-entries in your mailcap file, Mutt will search for an entry with the
-print command:
-</p><pre class="screen">
-image/*; xv %s
-image/gif; ; print= anytopnm %s | pnmtops | lpr; \
- nametemplate=%s.gif
-</pre><p>
-Mutt will skip the <code class="literal">image/*</code> entry and use the <code class="literal">image/gif</code>
-entry with the print command.
-</p><p>
-In addition, you can use this with <a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a>
-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.
-</p><pre class="screen">
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s; nametemplate=%s.html
-text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
-</pre><p>
-For <a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a>, Mutt 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 will use the second entry
-for interactive viewing.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-command-expansion"></a>3.3.3. Command Expansion</h4></div></div></div><p>
-The various commands defined in the mailcap files are passed to the
-<code class="literal">/bin/sh</code> shell using the system() function. Before the
-command is passed to <code class="literal">/bin/sh -c</code>, it is parsed to expand
-various special parameters with information from Mutt. The keywords
-Mutt expands are:
-</p><div class="variablelist"><dl><dt><span class="term">%s</span></dt><dd><p>
-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 to not pass the body of the message
-to the view/print/edit program on stdin.
-</p></dd><dt><span class="term">%t</span></dt><dd><p>
-Mutt 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 <code class="literal">text/html</code> or
-<code class="literal">image/gif</code>.
-</p></dd><dt><span class="term">%{<parameter>}</span></dt><dd><p>
-Mutt 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:
-</p><pre class="screen">
-Content-Type: text/plain; charset=iso-8859-1
-</pre><p>
-then Mutt 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.
-</p></dd><dt><span class="term">\%</span></dt><dd><p>
-This will be replaced by a %
-</p></dd></dl></div><p>
-Mutt 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.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-example"></a>3.4. Example mailcap files</h3></div></div></div><p>
-This mailcap file is fairly simple and standard:
-</p><pre class="screen">
-# I'm always running X :)
-video/*; xanim %s > /dev/null
-image/*; xv %s > /dev/null
-
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html; netscape -remote 'openURL(%s)'
-</pre><p>
-This mailcap file shows quite a number of examples:
-</p><pre class="screen">
-# Use xanim to view all videos Xanim produces a header on startup,
-# send that to /dev/null so I don't see it
-video/*; xanim %s > /dev/null
-
-# Send html to a running netscape by remote
-text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
-
-# If I'm not running netscape but I am running X, start netscape on the
-# object
-text/html; netscape %s; test=RunningX
-
-# Else use lynx to view it as text
-text/html; lynx %s
-
-# This version would convert the text/html to text/plain
-text/html; lynx -dump %s; copiousoutput
-
-# I use enscript to print text in two columns to a page
-text/*; more %s; print=enscript -2Gr %s
-
-# Netscape adds a flag to tell itself to view jpegs internally
-image/jpeg;xv %s; x-mozilla-flags=internal
-
-# Use xv to view images if I'm running X
-# In addition, this uses the \ to extend the line and set my editor
-# for images
-image/*;xv %s; test=RunningX; \
- edit=xpaint %s
-
-# Convert images to text using the netpbm tools
-image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
-pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
-# Send excel spreadsheets to my NT box
-application/ms-excel; open.pl %s
-</pre></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="auto-view"></a>4. MIME Autoview</h2></div></div></div><p>
-In addition to explicitly telling Mutt to view an attachment with the
-MIME viewer defined in the mailcap file, Mutt has support for
-automatically viewing MIME attachments while in the pager.
-</p><p>
-To work, you must define a viewer in the mailcap file which uses the
-<code class="literal">copiousoutput</code> 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.
-</p><p>
-You then use the <code class="literal">auto_view</code> muttrc command to list the
-content-types that you wish to view automatically.
-</p><p>
-For instance, if you set auto_view to:
-</p><pre class="screen">
-auto_view text/html application/x-gunzip \
- application/postscript image/gif application/x-tar-gz
-</pre><p>
-Mutt could use the following mailcap entries to automatically view
-attachments of these types.
-</p><pre class="screen">
-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
-</pre><p>
-“<span class="quote">unauto_view</span>” 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.
-“<span class="quote">unauto_view *</span>” will remove all previous entries.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternative-order"></a>5. MIME Multipart/Alternative</h2></div></div></div><p>
-Mutt 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 types
-is preferred. The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
-</p><pre class="screen">
-alternative_order text/enriched text/plain text application/postscript image/*
-</pre><p>
-Next, mutt will check if any of the types have a defined
-<a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a>, and use that. Failing
-that, Mutt will look for any text type. As a last attempt, mutt will
-look for any type it knows how to handle.
-</p><p>
-To remove a MIME type from the <code class="literal">alternative_order</code> list, use the
-<code class="literal">unalternative_order</code> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="attachments"></a>6. Attachment Searching and Counting</h2></div></div></div><p>
-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.
-</p><p>
-In order to provide this information, mutt needs to fully MIME-parse
-all messages affected first. This can slow down operation especially for
-remote mail folders such as IMAP because all messages have to be
-downloaded first regardless whether the user really wants to view them
-or not.
-</p><p>
-The syntax is:
-</p><pre class="screen">
-attachments {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments ?
-</pre><p>
-Disposition is the attachment's Content-disposition type -- either
-<code class="literal">inline</code> or <code class="literal">attachment</code>.
-You can abbreviate this to <code class="literal">I</code> or <code class="literal">A</code>.
-</p><p>
-Disposition is prefixed by either a + symbol or 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.
-</p><p>
-Mime-type is, unsurprisingly, the MIME type of the attachment you want
-to affect. A MIME type is always of the format <code class="literal">major/minor</code>, where
-<code class="literal">major</code> describes the broad category of document you're looking at, and
-<code class="literal">minor</code> describes the specific type within that category. The major
-part of mime-type must be literal text (or the special token “<span class="quote"><code class="literal">*</code></span>”), but
-the minor part may be a regular expression. (Therefore, “<span class="quote"><code class="literal">*/.*</code></span>” matches
-any MIME type.)
-</p><p>
-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.
-</p><p>
-Some examples might help to illustrate. The examples that are not
-commented out define the default configuration of the lists.
-</p><div class="example"><a id="ex-attach-count"></a><p class="title"><b>Example 5.1. Attachment counting</b></p><div class="example-contents"><pre class="screen">
-## 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
-</pre></div></div><br class="example-break" /><p>
-Entering the command “<span class="quote"><code class="literal">attachments ?</code></span>”
-as a command will list your current settings in Muttrc format, so that
-it can be pasted elsewhere.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-lookup"></a>7. MIME Lookup</h2></div></div></div><p>
-Mutt's mime_lookup list specifies a list of mime-types that should not
-be treated according to their mailcap entry. This option is designed to
-deal 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:
-</p><pre class="screen">
-mime_lookup application/octet-stream application/X-Lotus-Manuscript
-</pre><p>
-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.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="advancedusage.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="optionalfeatures.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Advanced Usage </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 6. Optional features</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 9. Miscellany</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="reference.html" title="Chapter 8. Reference" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 9. Miscellany</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="reference.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="miscellany"></a>Chapter 9. Miscellany</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="miscellany.html#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="miscellany.html#about">2. About this document</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="acknowledgements"></a>1. Acknowledgements</h2></div></div></div><p>
-Kari Hurtta <code class="email"><<a class="email" href="mailto:kari.hurtta@fmi.fi">kari.hurtta@fmi.fi</a>></code>
-co-developed the original MIME parsing code back in the ELM-ME days.
-</p><p>
-The following people have been very helpful to the development of Mutt:
-</p><div class="itemizedlist"><ul type="disc"><li><p>Vikas Agnihotri <code class="email"><<a class="email" href="mailto:vikasa@writeme.com">vikasa@writeme.com</a>></code></p></li><li><p>Francois Berjon <code class="email"><<a class="email" href="mailto:Francois.Berjon@aar.alcatel-alsthom.fr">Francois.Berjon@aar.alcatel-alsthom.fr</a>></code></p></li><li><p>Aric Blumer <code class="email"><<a class="email" href="mailto:aric@fore.com">aric@fore.com</a>></code></p></li><li><p>John Capo <code class="email"><<a class="email" href="mailto:jc@irbs.com">jc@irbs.com</a>></code></p></li><li><p>David Champion <code class="email"><<a class="email" href="mailto:dgc@uchicago.edu">dgc@uchicago.edu</a>></code></p></li><li><p>Brendan Cully <code class="email"><<a class="email" href="mailto:brendan@kublai.com">brendan@kublai.com</a>></code></p></li><li><p>Liviu Daia <code class="email"><<a class="email" href="mailto:daia@stoilow.imar.ro">daia@stoilow.imar.ro</a>></code></p></li><li><p>Thomas E. Dickey <code class="email"><<a class="email" href="mailto:dickey@herndon4.his.com">dickey@herndon4.his.com</a>></code></p></li><li><p>David DeSimone <code class="email"><<a class="email" href="mailto:fox@convex.hp.com">fox@convex.hp.com</a>></code></p></li><li><p>Nickolay N. Dudorov <code class="email"><<a class="email" href="mailto:nnd@wint.itfs.nsk.su">nnd@wint.itfs.nsk.su</a>></code></p></li><li><p>Ruslan Ermilov <code class="email"><<a class="email" href="mailto:ru@freebsd.org">ru@freebsd.org</a>></code></p></li><li><p>Edmund Grimley Evans <code class="email"><<a class="email" href="mailto:edmundo@rano.org">edmundo@rano.org</a>></code></p></li><li><p>Michael Finken <code class="email"><<a class="email" href="mailto:finken@conware.de">finken@conware.de</a>></code></p></li><li><p>Sven Guckes <code class="email"><<a class="email" href="mailto:guckes@math.fu-berlin.de">guckes@math.fu-berlin.de</a>></code></p></li><li><p>Lars Hecking <code class="email"><<a class="email" href="mailto:lhecking@nmrc.ie">lhecking@nmrc.ie</a>></code></p></li><li><p>Mark Holloman <code class="email"><<a class="email" href="mailto:holloman@nando.net">holloman@nando.net</a>></code></p></li><li><p>Andreas Holzmann <code class="email"><<a class="email" href="mailto:holzmann@fmi.uni-passau.de">holzmann@fmi.uni-passau.de</a>></code></p></li><li><p>Marco d'Itri <code class="email"><<a class="email" href="mailto:md@linux.it">md@linux.it</a>></code></p></li><li><p>Björn Jacke <code class="email"><<a class="email" href="mailto:bjacke@suse.com">bjacke@suse.com</a>></code></p></li><li><p>Byrial Jensen <code class="email"><<a class="email" href="mailto:byrial@image.dk">byrial@image.dk</a>></code></p></li><li><p>David Jeske <code class="email"><<a class="email" href="mailto:jeske@igcom.net">jeske@igcom.net</a>></code></p></li><li><p>Christophe Kalt <code class="email"><<a class="email" href="mailto:kalt@hugo.int-evry.fr">kalt@hugo.int-evry.fr</a>></code></p></li><li><p>Tommi Komulainen <code class="email"><<a class="email" href="mailto:Tommi.Komulainen@iki.fi">Tommi.Komulainen@iki.fi</a>></code></p></li><li><p>Felix von Leitner (a.k.a “<span class="quote">Fefe</span>”) <code class="email"><<a class="email" href="mailto:leitner@math.fu-berlin.de">leitner@math.fu-berlin.de</a>></code></p></li><li><p>Brandon Long <code class="email"><<a class="email" href="mailto:blong@fiction.net">blong@fiction.net</a>></code></p></li><li><p>Jimmy Mäkelä <code class="email"><<a class="email" href="mailto:jmy@flashback.net">jmy@flashback.net</a>></code></p></li><li><p>Lars Marowsky-Bree <code class="email"><<a class="email" href="mailto:lmb@pointer.in-minden.de">lmb@pointer.in-minden.de</a>></code></p></li><li><p>Thomas “<span class="quote">Mike</span>” Michlmayr <code class="email"><<a class="email" href="mailto:mike@cosy.sbg.ac.at">mike@cosy.sbg.ac.at</a>></code></p></li><li><p>Andrew W. Nosenko <code class="email"><<a class="email" href="mailto:awn@bcs.zp.ua">awn@bcs.zp.ua</a>></code></p></li><li><p>David O'Brien <code class="email"><<a class="email" href="mailto:obrien@Nuxi.cs.ucdavis.edu">obrien@Nuxi.cs.ucdavis.edu</a>></code></p></li><li><p>Clint Olsen <code class="email"><<a class="email" href="mailto:olsenc@ichips.intel.com">olsenc@ichips.intel.com</a>></code></p></li><li><p>Park Myeong Seok <code class="email"><<a class="email" href="mailto:pms@romance.kaist.ac.kr">pms@romance.kaist.ac.kr</a>></code></p></li><li><p>Thomas Parmelan <code class="email"><<a class="email" href="mailto:tom@ankh.fr.eu.org">tom@ankh.fr.eu.org</a>></code></p></li><li><p>Ollivier Robert <code class="email"><<a class="email" href="mailto:roberto@keltia.freenix.fr">roberto@keltia.freenix.fr</a>></code></p></li><li><p>Thomas Roessler <code class="email"><<a class="email" href="mailto:roessler@does-not-exist.org">roessler@does-not-exist.org</a>></code></p></li><li><p>Roland Rosenfeld <code class="email"><<a class="email" href="mailto:roland@spinnaker.de">roland@spinnaker.de</a>></code></p></li><li><p>Rocco Rutte <code class="email"><<a class="email" href="mailto:pdmef@gmx.net">pdmef@gmx.net</a>></code></p></li><li><p>TAKIZAWA Takashi <code class="email"><<a class="email" href="mailto:taki@luna.email.ne.jp">taki@luna.email.ne.jp</a>></code></p></li><li><p>Allain Thivillon <code class="email"><<a class="email" href="mailto:Allain.Thivillon@alma.fr">Allain.Thivillon@alma.fr</a>></code></p></li><li><p>Gero Treuner <code class="email"><<a class="email" href="mailto:gero@70t.de">gero@70t.de</a>></code></p></li><li><p>Vsevolod Volkov <code class="email"><<a class="email" href="mailto:vvv@lucky.net">vvv@lucky.net</a>></code></p></li><li><p>Ken Weinert <code class="email"><<a class="email" href="mailto:kenw@ihs.com">kenw@ihs.com</a>></code></p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="about"></a>2. About this document</h2></div></div></div><p>
-This document was written in <a class="ulink" href="http://docbook.sourceforge.net" target="_top">DocBook</a>,
-and then rendered using the <a class="ulink" href="http://xmlsoft.org/XSLT/" target="_top">Gnome XSLT toolkit</a>.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="reference.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">Chapter 8. Reference </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
+++ /dev/null
-.\" -*-nroff-*-
-.\"
-.\"
-.\" Copyright (C) 1996-2004 Michael R. Elkins <me@cs.hmc.edu>
-.\"
-.\" This program is free software; you can redistribute it and/or modify
-.\" it under the terms of the GNU General Public License as published by
-.\" the Free Software Foundation; either version 2 of the License, or
-.\" (at your option) any later version.
-.\"
-.\" This program is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-.\"
-.TH mutt 1 "January 2009" Unix "User Manuals"
-.SH NAME
-mutt \- The Mutt Mail User Agent
-.SH SYNOPSIS
-.PP
-.B mutt
-[\-nRyzZ]
-[\-e \fIcmd\fP] [\-F \fIfile\fP] [\-m \fItype\fP] [\-f \fIfile\fP]
-.PP
-.B mutt
-[\-nx]
-[\-e \fIcmd\fP]
-[\-F \fIfile\fP]
-[\-H \fIfile\fP]
-[\-i \fIfile\fP]
-[\-s \fIsubj\fP]
-[\-b \fIaddr\fP]
-[\-c \fIaddr\fP]
-[\-a \fIfile\fP [...]]
-[\-\-]
-\fIaddr\fP [...]
-.PP
-.B mutt
-[\-nx]
-[\-e \fIcmd\fP]
-[\-F \fIfile\fP]
-[\-s \fIsubj\fP]
-[\-b \fIaddr\fP]
-[\-c \fIaddr\fP]
-[\-a \fIfile\fP [...]]
-[\-\-]
-\fIaddr\fP [...]
-< message
-.PP
-.B mutt
-[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-p
-.PP
-.B mutt
-[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-A \fIalias\fP
-.PP
-.B mutt
-[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-Q \fIquery\fP
-.PP
-.B mutt
-\-v[v]
-.PP
-.B mutt
-\-D
-.SH DESCRIPTION
-.PP
-Mutt is a small but very powerful text based program for reading and sending electronic
-mail under unix operating systems, including support for color terminals, MIME,
-OpenPGP, and a threaded sorting mode.
-.PP
-.I Note:
-.IR
-This manual page gives a brief overview of mutt's command line
-options. You should find a copy of the full manual in /usr/share/doc, in
-text, HTML, and/or PDF format.
-.SH OPTIONS
-.PP
-.IP "-A \fIalias\fP"
-An expanded version of the given alias is passed to stdout.
-.IP "-a \fIfile\fP [...]"
-Attach a file to your message using MIME.
-When attaching single or multiple files, separating filenames and recipient addresses with
-"\-\-" is mandatory, e.g. \fBmutt \-a image.jpg \-\- addr1\fP or
-\fBmutt \-a img.jpg *.png \-\- addr1 addr2\fP.
-The \-a option must be placed at the end of command line options.
-.IP "-b \fIaddress\fP"
-Specify a blind-carbon-copy (BCC) recipient
-.IP "-c \fIaddress\fP"
-Specify a carbon-copy (CC) recipient
-.IP "-d \fIlevel\fp"
-If mutt was complied with +DEBUG log debugging output to ~/.muttdebug0.
-\fILevel\fP can range from 1-5 and effects verbosity. A value of 2 is
-recommended.
-.IP "-D"
-Print the value of all configuration options to stdout.
-.IP "-e \fIcommand\fP"
-Specify a configuration command to be run after processing of initialization
-files.
-.IP "-f \fImailbox\fP"
-Specify which mailbox to load.
-.IP "-F \fImuttrc\fP"
-Specify an initialization file to read instead of ~/.muttrc
-.IP "-h"
-Display help.
-.IP "-H \fIdraft\fP"
-Specify a draft file which contains header and body to use to send a
-message.
-.IP "-i \fIinclude\fP"
-Specify a file to include into the body of a message.
-.IP "-m \fItype\fP "
-specify a default mailbox type
-.IP "-n"
-Causes Mutt to bypass the system configuration file.
-.IP "-p"
-Resume a postponed message.
-.IP "-Q \fIquery\fP"
-Query a configuration variables value. The query is executed after
-all configuration files have been parsed, and any commands given on
-the command line have been executed.
-.IP "-R"
-Open a mailbox in \fIread-only\fP mode.
-.IP "-s \fIsubject\fP"
-Specify the subject of the message.
-.IP "-v"
-Display the Mutt version number and compile-time definitions.
-.IP "-vv"
-Display license and copyright information.
-.IP "-x"
-Emulate the mailx compose mode.
-.IP "-y"
-Start Mutt with a listing of all mailboxes specified by the \fImailboxes\fP
-command.
-.IP "-z"
-When used with \-f, causes Mutt not to start if there are no messages in the
-mailbox.
-.IP "-Z"
-Causes Mutt to open the first mailbox specified by the \fImailboxes\fP
-command which contains new mail.
-.IP "--"
-Treat remaining arguments as \fIaddr\fP even if they start with a dash.
-See also "\-a" above.
-.SH ENVIRONMENT
-.PP
-.IP "EDITOR"
-Specifies the editor to use if VISUAL is unset.
-.IP "EMAIL"
-The user's e-mail address.
-.IP "HOME"
-Full path of the user's home directory.
-.IP "MAIL"
-Full path of the user's spool mailbox.
-.IP "MAILDIR"
-Full path of the user's spool mailbox. Commonly used when the spool
-mailbox is a
-.B maildir (5)
-folder.
-.IP "MAILCAPS"
-Path to search for mailcap files.
-.IP "MM_NOASK"
-If this variable is set, mailcap are always used without prompting first.
-.IP "PGPPATH"
-Directory in which the user's PGP public keyring can be found.
-.IP "TMPDIR"
-Directory in which temporary files are created.
-.IP "REPLYTO"
-Default Reply-To address.
-.IP "VISUAL"
-Specifies the editor to use when composing messages.
-.SH FILES
-.PP
-.IP "~/.muttrc or ~/.mutt/muttrc"
-User configuration file.
-.IP "/etc/Muttrc"
-System-wide configuration file.
-.IP "/tmp/muttXXXXXX"
-Temporary files created by Mutt.
-.IP "~/.mailcap"
-User definition for handling non-text MIME types.
-.IP "/etc/mailcap"
-System definition for handling non-text MIME types.
-.IP "~/.mime.types"
-User's personal mapping between MIME types and file extensions.
-.IP "/etc/mime.types"
-System mapping between MIME types and file extensions.
-.IP "/usr/bin/mutt_dotlock"
-The privileged dotlocking program.
-.IP "/usr/share/doc/mutt/manual.txt.gz"
-The Mutt manual.
-.SH BUGS
-.PP
-None. Mutts have fleas, not bugs.
-.SH FLEAS
-.PP
-Suspend/resume while editing a file with an external editor does not work
-under SunOS 4.x if you use the curses lib in /usr/5lib. It \fIdoes\fP work
-with the S-Lang library, however.
-.PP
-Resizing the screen while using an external pager causes Mutt to go haywire
-on some systems.
-.PP
-Suspend/resume does not work under Ultrix.
-.PP
-The help line for the index menu is not updated if you change the bindings
-for one of the functions listed while Mutt is running.
-.PP
-For a more up-to-date list of bugs, errm, fleas, please visit the
-mutt project's bug tracking system under http://bugs.mutt.org/.
-.SH NO WARRANTIES
-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.
-.SH SEE ALSO
-.PP
-.BR curses (3),
-.BR mailcap (5),
-.BR maildir (5),
-.BR mbox (5),
-.BR mutt_dotlock (1),
-.BR muttrc (5),
-.BR ncurses (3),
-.BR sendmail (1),
-.BR smail (1).
-.PP
-Mutt Home Page: http://www.mutt.org/
-.PP
-The Mutt manual
-.SH AUTHOR
-.PP
-Michael Elkins, and others. Use <mutt-dev@mutt.org> to contact
-the developers.
+++ /dev/null
-'\" t
-.\" -*-nroff-*-
-.\"
-.\" Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu>
-.\" Copyright (C) 1999-2000 Thomas Roessler <roessler@does-not-exist.org>
-.\"
-.\" This program is free software; you can redistribute it and/or modify
-.\" it under the terms of the GNU General Public License as published by
-.\" the Free Software Foundation; either version 2 of the License, or
-.\" (at your option) any later version.
-.\"
-.\" This program is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-.\"
-.TH muttrc 5 "September 2002" Unix "User Manuals"
-.SH NAME
-muttrc \- Configuration file for the Mutt Mail User Agent
-.SH DESCRIPTION
-.PP
-A mutt configuration file consists of a series of \(lqcommands\(rq.
-Each line of the file may contain one or more commands. When
-multiple commands are used, they must be separated by a semicolon
-(\(lq\fB;\fP\(rq).
-.PP
-The hash mark, or pound sign (\(lq\fB#\fP\(rq), is used as a
-\(lqcomment\(rq character. You can use it to annotate your
-initialization file. All text after the comment character to the end
-of the line is ignored.
-.PP
-Single quotes (\(lq\fB'\fP\(rq) and double quotes (\(lq\fB"\fP\(rq)
-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 which
-should be evaluated. For example, backticks are evaluated inside of
-double quotes, but not single quotes.
-.PP
-\fB\(rs\fP quotes the next character, just as in shells such as bash and zsh.
-For example, if want to put quotes (\(lq\fB"\fP\(rq) inside of a
-string, you can use \(lq\fB\(rs\fP\(rq to force the next character
-to be a literal instead of interpreted character.
-.PP
-\(lq\fB\(rs\(rs\fP\(rq means to insert a literal \(lq\fB\(rs\fP\(rq into the
-line. \(lq\fB\(rsn\fP\(rq and \(lq\fB\(rsr\fP\(rq have their usual
-C meanings of linefeed and carriage-return, respectively.
-.PP
-A \(lq\fB\(rs\fP\(rq 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.
-.PP
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command
-in backticks (\fB`\fP\fIcommand\fP\fB`\fP).
-.PP
-UNIX environment variables can be accessed like the way it is done in shells
-like sh and bash: Prepend the name of the variable by a dollar
-(\(lq\fB\(Do\fP\(rq) sign.
-.PP
-.SH COMMANDS
-.PP
-.nf
-\fBalias\fP [\fB-group\fP \fIname\fP [...]] \fIkey\fP \fIaddress\fP [\fB,\fP \fIaddress\fP [ ... ]]
-\fBunalias\fP [\fB * \fP | \fIkey\fP ]
-.fi
-.IP
-\fBalias\fP defines an alias \fIkey\fP for the given addresses. Each
-\fIaddress\fP will be resolved into either an email address (user@example.com)
-or a named email address (User Name <user@example.com>). The address may be specified in either format, or in the format \(lquser@example.com (User
-Name)\(rq.
-\fBunalias\fP removes the alias corresponding to the given \fIkey\fP or
-all aliases when \(lq\fB*\fP\(rq is used as an argument. The optional
-\fB-group\fP argument to \fBalias\fP causes the aliased address(es) to be
-added to the named \fIgroup\fP.
-.PP
-.nf
-\fBgroup\fP [\fB-group\fP \fIname\fP] [\fB-rx\fP \fIEXPR\fP [ \fI...\fP ]] [\fB-addr\fP \fIaddress\fP [ \fI...\fP ]]
-\fBungroup\fP [\fB-group\fP \fIname\fP ] [ \fB*\fP | [[\fB-rx\fP \fIEXPR\fP [ \fI...\fP ]] [\fB-addr\fP \fIaddress\fP [ \fI...\fP ]]]
-.fi
-.IP
-\fBgroup\fP is used to directly add either addresses or regular expressions to
-the specified group or groups. The different categories of arguments to the
-\fBgroup\fP command can be in any order. The flags \fI-rx\fP and \fI-addr\fP
-specify what the following strings (that cannot begin with a hyphen) should be
-interpreted as: either a regular expression or an email address, respectively.
-\fBungroup\fP is used to remove addresses or regular expressions from the
-specified group or groups. The syntax is similar to the \fBgroup\fP command,
-however the special character \fB*\fP can be used to empty a group of all of
-its contents.
-.IP
-These address groups can also be created implicitly by the \fBalias\fP, \fBlists\fP,
-\fBsubscribe\fP and \fBalternates\fP commands by specifying the optional \fI-group\fP
-option.
-.IP
-Once defined, these address groups can be used in patterns to search for and limit the
-display to messages matching a group.
-.PP
-.nf
-\fBalternates\fP [\fB-group\fP \fIname\fP] \fIregexp\fP [ \fB,\fP \fIregexp\fP [ ... ]]
-\fBunalternates\fP [\fB * \fP | \fIregexp\fP [ \fB,\fP \fIregexp\fP [ ... ]] ]
-.fi
-.IP
-\fBalternates\fP is used to inform mutt about alternate addresses
-where you receive mail; you can use regular expressions to specify
-alternate addresses. This affects mutt's idea about messages
-from you, and messages addressed to you. \fBunalternates\fP removes
-a regular expression from the list of known alternates. The \fB-group\fP flag
-causes all of the subsequent regular expressions to be added to the named group.
-.PP
-.nf
-\fBalternative_order\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-\fBunalternative_order\fP [\fB * \fP | \fItype\fP/\fIsubtype\fP] [...]
-.fi
-.IP
-\fBalternative_order\fP command permits you to define an order of preference which is
-used by mutt to determine which part of a
-\fBmultipart/alternative\fP body to display.
-A subtype of \(lq\fB*\fP\(rq matches any subtype, as does an empty
-subtype. \fBunalternative_order\fP removes entries from the
-ordered list or deletes the entire list when \(lq\fB*\fP\(rq is used
-as an argument.
-.PP
-.nf
-\fBauto_view\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-\fBunauto_view\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-.fi
-.IP
-This commands permits you to specify that mutt should automatically
-convert the given MIME types to text/plain when displaying messages.
-For this to work, there must be a
-.BR mailcap (5)
-entry for the given MIME type with the
-.B copiousoutput
-flag set. A subtype of \(lq\fB*\fP\(rq
-matches any subtype, as does an empty subtype.
-.PP
-.nf
-\fBmime_lookup\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-\fBunmime_lookup\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-.fi
-.IP
-This command permits you to define a list of "data" MIME content
-types for which mutt will try to determine the actual file type from
-the file name, and not use a
-.BR mailcap (5)
-entry given for the original MIME type. For instance, you may add
-the \fBapplication/octet-stream\fP MIME type to this list.
-.TP
-\fBbind\fP \fImap1,map2,...\fP \fIkey\fP \fIfunction\fP
-This command binds the given \fIkey\fP for the given \fImap\fP or maps
-to the given \fIfunction\fP. Multiple maps may be specified by
-separating them with commas (no whitespace is allowed).
-.IP
-Valid maps are:
-.BR generic ", " alias ", " attach ", "
-.BR browser ", " editor ", "
-.BR index ", " compose ", "
-.BR pager ", " pgp ", " postpone ", "
-.BR mix .
-.IP
-For more information on keys and functions, please consult the Mutt
-Manual.
-.TP
-\fBaccount-hook\fP [\fB!\fP]\fIregexp\fP \fIcommand\fP
-This hook is executed whenever you access a remote mailbox. Useful
-to adjust configuration settings to different IMAP or POP servers.
-.TP
-\fBcharset-hook\fP \fIalias\fP \fIcharset\fP
-This 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.
-.TP
-\fBiconv-hook\fP \fIcharset\fP \fIlocal-charset\fP
-This command defines a system-specific name for a character set.
-This is useful when your system's
-.BR iconv (3)
-implementation does not understand MIME character set names (such as
-.BR iso-8859-1 ),
-but instead insists on being fed with implementation-specific
-character set names (such as
-.BR 8859-1 ).
-In this specific case, you'd put this into your configuration file:
-.IP
-.B "iconv-hook iso-8859-1 8859-1"
-.TP
-\fBmessage-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP
-Before mutt displays (or formats for replying or forwarding) a
-message which matches the given \fIpattern\fP (or, when it is
-preceded by an exclamation mark, does not match the \fIpattern\fP),
-the given \fIcommand\fP is executed. When multiple
-\fBmessage-hook\fPs match, they are executed in the order in
-which they occur in the configuration file.
-.TP
-\fBfolder-hook\fP [\fB!\fP]\fIregexp\fP \fIcommand\fP
-When mutt enters a folder which matches \fIregexp\fP (or, when
-\fIregexp\fP is preceded by an exclamation mark, does not match
-\fIregexp\fP), the given \fIcommand\fP is executed.
-.IP
-When several \fBfolder-hook\fPs match a given mail folder, they are
-executed in the order given in the configuration file.
-.TP
-\fBmacro\fP \fImap\fP \fIkey\fP \fIsequence\fP [ \fIdescription\fP ]
-This command binds the given \fIsequence\fP of keys to the given
-\fIkey\fP in the given \fImap\fP or maps. For valid maps, see \fBbind\fP. To
-specify multiple maps, put only a comma between the maps.
-.PP
-.nf
-\fBcolor\fP \fIobject\fP \fIforeground\fP \fIbackground\fP [ \fI regexp\fP ]
-\fBcolor\fP index \fIforeground\fP \fIbackground\fP [ \fI pattern\fP ]
-\fBuncolor\fP index \fIpattern\fP [ \fIpattern\fP ... ]
-.fi
-.IP
-If your terminal supports color, these commands can be used to
-assign \fIforeground\fP/\fIbackground\fP combinations to certain
-objects. Valid objects are:
-.BR attachment ", " body ", " bold ", " header ", "
-.BR hdrdefault ", " index ", " indicator ", " markers ", "
-.BR message ", " normal ", " quoted ", " quoted\fIN\fP ", "
-.BR search ", " signature ", " status ", " tilde ", " tree ", "
-.BR underline .
-The
-.BR body " and " header
-objects allow you to restrict the colorization to a regular
-expression. The \fBindex\fP object permits you to select colored
-messages by pattern.
-.IP
-Valid colors include:
-.BR white ", " black ", " green ", " magenta ", " blue ", "
-.BR cyan ", " yellow ", " red ", " default ", " color\fIN\fP .
-.PP
-.nf
-\fBmono\fP \fIobject\fP \fIattribute\fP [ \fIregexp\fP ]
-\fBmono\fP index \fIattribute\fP [ \fIpattern\fP ]
-.fi
-.IP
-For terminals which don't support color, you can still assign
-attributes to objects. Valid attributes include:
-.BR none ", " bold ", " underline ", "
-.BR reverse ", and " standout .
-.TP
-[\fBun\fP]\fBignore\fP \fIpattern\fP [ \fIpattern\fP ... ]
-The \fBignore\fP command permits you to specify header fields which
-you usually don't wish to see. Any header field whose tag
-\fIbegins\fP with an \(lqignored\(rq pattern will be ignored.
-.IP
-The \fBunignore\fP command permits you to define exceptions from
-the above mentioned list of ignored headers.
-.PP
-.nf
-\fBlists\fP [\fB-group\fP \fIname\fP] \fIregexp\fP [ \fIregexp\fP ... ]
-\fBunlists\fP \fIregexp\fP [ \fIregexp\fP ... ]
-\fBsubscribe\fP [\fB-group\fP \fIname\fP] \fIregexp\fP [ \fIregexp\fP ... ]
-\fBunsubscribe\fP \fIregexp\fP [ \fIregexp\fP ... ]
-.fi
-.IP
-Mutt maintains two lists of mailing list address patterns, a list of
-subscribed mailing lists, and a list of known mailing lists. All
-subscribed mailing lists are known. Patterns use regular expressions.
-.IP
-The \fBlists\fP command adds a mailing list address to the list of
-known mailing lists. The \fBunlists\fP command removes a mailing
-list from the lists of known and subscribed mailing lists. The
-\fBsubscribe\fP command adds a mailing list to the lists of known
-and subscribed mailing lists. The \fBunsubscribe\fP command removes
-it from the list of subscribed mailing lists. The \fb-group\fP flag
-adds all of the subsequent regular expressions to the named group.
-.TP
-\fBmbox-hook\fP [\fB!\fP]\fIpattern\fP \fImailbox\fP
-When mutt changes to a mail folder which matches \fIpattern\fP,
-\fImailbox\fP will be used as the \(lqmbox\(rq folder, i.e., read
-messages will be moved to that folder when the mail folder is left.
-.IP
-The first matching \fBmbox-hook\fP applies.
-.PP
-.nf
-\fBmailboxes\fP \fIfilename\fP [ \fIfilename\fP ... ]
-\fBunmailboxes\fP [ \fB*\fP | \fIfilename\fP ... ]
-.fi
-.IP
-The \fBmailboxes\fP specifies folders which can receive mail and which will
-be checked for new messages. When changing folders, pressing space
-will cycle through folders with new mail. The \fBunmailboxes\fP
-command is used to remove a file name from the list of folders which
-can receive mail. If "\fB*\fP" is specified as the file name, the
-list is emptied.
-.PP
-.nf
-\fBmy_hdr\fP \fIstring\fP
-\fBunmy_hdr\fP \fIfield\fP
-.fi
-.IP
-Using \fBmy_hdr\fP, you can define headers which will be added to
-the messages you compose. \fBunmy_hdr\fP will remove the given
-user-defined headers.
-.TP
-\fBhdr_order\fP \fIheader1\fP \fIheader2\fP [ ... ]
-With this command, you can specify an order in which mutt will
-attempt to present headers to you when viewing messages.
-.TP
-\fBsave-hook\fP [\fB!\fP]\fIpattern\fP \fIfilename\fP
-When a message matches \fIpattern\fP, the default file name when
-saving it will be the given \fIfilename\fP.
-.TP
-\fBfcc-hook\fP [\fB!\fP]\fIpattern\fP \fIfilename\fP
-When an outgoing message matches \fIpattern\fP, the default file
-name for storing a copy (fcc) will be the given \fIfilename\fP.
-.TP
-\fBfcc-save-hook\fP [\fB!\fP]\fIpattern\fP \fIfilename\fP
-This command is an abbreviation for identical \fBfcc-hook\fP and
-\fBsave-hook\fP commands.
-.TP
-\fBsend-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP
-When composing a message matching \fIpattern\fP, \fIcommand\fP is
-executed. When multiple \fBsend-hook\fPs match, they are executed
-in the order in which they occur in the configuration file.
-.TP
-\fBsend2-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP
-Whenever a message matching \fIpattern\fP is changed (either by
-editing it or by using the compose menu), \fIcommand\fP
-is executed. When multiple \fBsend2-hook\fPs match, they are
-executed in the order in which they occur in the configuration file.
-Possible applications include setting the $sendmail variable when a
-message's from header is changed.
-.IP
-\fBsend2-hook\fP execution is not triggered by use of
-\fBenter-command\fP from the compose menu.
-.TP
-\fBreply-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP
-When replying to a message matching \fIpattern\fP, \fIcommand\fP is
-executed. When multiple \fBreply-hook\fPs match, they are executed
-in the order in which they occur in the configuration file, but all
-\fBreply-hook\fPs are matched and executed before \fBsend-hook\fPs,
-regardless of their order in the configuration file.
-.TP
-\fBcrypt-hook\fP \fIpattern\fP \fIkey-id\fP
-The crypt-hook command provides a method by which you can
-specify the ID of the public key to be used when encrypting messages
-to a certain recipient. The meaning of "key ID" is to be taken
-broadly: This can be a different e-mail address, a numerical key ID,
-or even just an arbitrary search string.
-.PP
-.nf
-\fBopen-hook\fP \fIregexp\fP "\fIcommand\fP"
-\fBclose-hook\fP \fIregexp\fP "\fIcommand\fP"
-\fBappend-hook\fP \fIregexp\fP "\fIcommand\fP"
-.fi
-.IP
-These commands provide a way to handle compressed folders. The given
-\fBregexp\fP specifies which folders are taken as compressed (e.g.
-"\fI\\\\.gz$\fP"). The commands tell Mutt how to uncompress a folder
-(\fBopen-hook\fP), compress a folder (\fBclose-hook\fP) or append a
-compressed mail to a compressed folder (\fBappend-hook\fP). The
-\fIcommand\fP string is the
-.BR printf (3)
-like format string, and it should accept two parameters: \fB%f\fP,
-which is replaced with the (compressed) folder name, and \fB%t\fP
-which is replaced with the name of the temporary folder to which to
-write.
-.TP
-\fBpush\fP \fIstring\fP
-This command adds the named \fIstring\fP to the keyboard buffer.
-.PP
-.nf
-\fBset\fP [\fBno\fP|\fBinv\fP|\fB&\fP|\fB?\fP]\fIvariable\fP[=\fIvalue\fP] [ ... ]
-\fBtoggle\fP \fIvariable\fP [ ... ]
-\fBunset\fP \fIvariable\fP [ ... ]
-\fBreset\fP \fIvariable\fP [ ... ]
-.fi
-.IP
-These commands are used to set and manipulate configuration
-variables.
-.IP
-Mutt knows four basic types of variables: boolean, number, string
-and quadoption. Boolean variables can be \fBset\fP (true),
-\fBunset\fP (false), or \fBtoggle\fPd. Number variables can be assigned
-a positive integer value.
-.IP
-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 \(lqC\(rq escape sequences \fB\\n\fP and
-\fB\\t\fP for newline and tab, respectively.
-.IP
-Quadoption variables are used to control whether or not to be
-prompted for certain actions, or to specify a default action. A
-value of \fByes\fP will cause the action to be carried out automatically
-as if you had answered yes to the question. Similarly, a value of
-\fBno\fP will cause the the action to be carried out as if you had
-answered \(lqno.\(rq A value of \fBask-yes\fP will cause a prompt
-with a default answer of \(lqyes\(rq and \fBask-no\fP will provide a
-default answer of \(lqno.\(rq
-.IP
-The \fBreset\fP command resets all given variables to the compile
-time defaults. If you reset the special variable \fBall\fP, all
-variables will reset to their compile time defaults.
-.TP
-\fBsource\fP \fIfilename\fP
-The given file will be evaluated as a configuration file.
-.TP
-.nf
-\fBspam\fP \fIpattern\fP \fIformat\fP
-\fBnospam\fP \fIpattern\fP
-.fi
-These commands define spam-detection patterns from external spam
-filters, so that mutt can sort, limit, and search on
-``spam tags'' or ``spam attributes'', or display them
-in the index. See the Mutt manual for details.
-.TP
-\fBunhook\fP [\fB * \fP | \fIhook-type\fP ]
-This command will remove all hooks of a given type, or all hooks
-when \(lq\fB*\fP\(rq is used as an argument. \fIhook-type\fP
-can be any of the \fB-hook\fP commands documented above.
-.SH PATTERNS
-.PP
-In various places with mutt, including some of the abovementioned
-\fBhook\fP commands, you can specify patterns to match messages.
-.SS Constructing Patterns
-.PP
-A simple pattern consists of an operator of the form
-\(lq\fB~\fP\fIcharacter\fP\(rq, possibly followed by a parameter
-against which mutt is supposed to match the object specified by
-this operator. For some \fIcharacter\fPs, the \fB~\fP may be
-replaced by another character to alter the behavior of the match.
-These are described in the list of operators, below.
-.PP
-With some of these operators, the object to be matched consists of
-several e-mail addresses. In these cases, the object is matched if
-at least one of these e-mail addresses matches. You can prepend a
-hat (\(lq\fB^\fP\(rq) character to such a pattern to indicate that
-\fIall\fP addresses must match in order to match the object.
-.PP
-You can construct complex patterns by combining simple patterns with
-logical operators. Logical AND is specified by simply concatenating
-two simple patterns, for instance \(lq~C mutt-dev ~s bug\(rq.
-Logical OR is specified by inserting a vertical bar (\(lq\fB|\fP\(rq)
-between two patterns, for instance \(lq~C mutt-dev | ~s bug\(rq.
-Additionally, you can negate a pattern by prepending a bang
-(\(lq\fB!\fP\(rq) character. For logical grouping, use braces
-(\(lq()\(rq). Example: \(lq!(~t mutt|~c mutt) ~f elkins\(rq.
-.SS Simple Patterns
-.PP
-Mutt understands the following simple patterns:
-.P
-.PD 0
-.TP 12
-~A
-all messages
-.TP
-~b \fIEXPR\fP
-messages which contain \fIEXPR\fP in the message body.
-.TP
-=b \fISTRING\fP
-messages which contain \fISTRING\fP in the message body. If IMAP is enabled, searches for \fISTRING\fP on the server, rather than downloading each message and searching it locally.
-.TP
-~B \fIEXPR\fP
-messages which contain \fIEXPR\fP in the whole message.
-.TP
-~c \fIEXPR\fP
-messages carbon-copied to \fIEXPR\fP
-.TP
-%c \fIGROUP\fP
-messages carbon-copied to any member of \fIGROUP\fP
-.TP
-~C \fIEXPR\fP
-messages either to: or cc: \fIEXPR\fP
-.TP
-%C \fIGROUP\fP
-messages either to: or cc: to any member of \fIGROUP\fP
-.TP
-~d \fIMIN\fP-\fIMAX\fP
-messages with \(lqdate-sent\(rq in a Date range
-.TP
-~D
-deleted messages
-.TP
-~e \fIEXPR\fP
-messages which contain \fIEXPR\fP in the \(lqSender\(rq field
-.TP
-%e \fIGROUP\fP
-messages which contain a member of \fIGROUP\fP in the \(lqSender\(rq field
-.TP
-~E
-expired messages
-.TP
-~f \fIEXPR\fP
-messages originating from \fIEXPR\fP
-.TP
-%f \fIGROUP\fP
-messages originating form any member of \fIGROUP\fP
-.TP
-~F
-flagged messages
-.TP
-~g
-PGP signed messages
-.TP
-~G
-PGP encrypted messages
-.TP
-~h \fIEXPR\fP
-messages which contain \fIEXPR\fP in the message header
-.TP
-~H \fIEXPR\fP
-messages with spam tags matching \fIEXPR\fP
-.TP
-~i \fIEXPR\fP
-messages which match \fIEXPR\fP in the \(lqMessage-ID\(rq field
-.TP
-~k
-messages containing PGP key material
-.TP
-~l
-messages addressed to a known mailing list (defined by either \fBsubscribe\fP or \fBlist\fP)
-.TP
-~L \fIEXPR\fP
-messages either originated or received by \fIEXPR\fP
-.TP
-%L \fIGROUP\fP
-messages either originated or received by any member of \fIGROUP\fP
-.TP
-~m \fIMIN\fP-\fIMAX\fP
-message in the range \fIMIN\fP to \fIMAX\fP
-.TP
-~n \fIMIN\fP-\fIMAX\fP
-messages with a score in the range \fIMIN\fP to \fIMAX\fP
-.TP
-~N
-new messages
-.TP
-~O
-old messages
-.TP
-~p
-messages addressed to you (as defined by \fBalternates\fP)
-.TP
-~P
-messages from you (as defined by \fBalternates\fP)
-.TP
-~Q
-messages which have been replied to
-.TP
-~r \fIMIN\fP-\fIMAX\fP
-messages with \(lqdate-received\(rq in a Date range
-.TP
-~R
-read messages
-.TP
-~s \fIEXPR\fP
-messages having \fIEXPR\fP in the \(lqSubject\(rq field.
-.TP
-~S
-superseded messages
-.TP
-~t \fIEXPR\fP
-messages addressed to \fIEXPR\fP
-.TP
-~T
-tagged messages
-.TP
-~u
-messages addressed to a subscribed mailing list (defined by \fBsubscribe\fP commands)
-.TP
-~U
-unread messages
-.TP
-~v
-message is part of a collapsed thread.
-.TP
-~V
-cryptographically verified messages
-.TP
-~x \fIEXPR\fP
-messages which contain \fIEXPR\fP in the \(lqReferences\(rq field
-.TP
-~X \fIMIN\fP-\fIMAX\fP
-messages with MIN - MAX attachments
-.TP
-~y \fIEXPR\fP
-messages which contain \fIEXPR\fP in the \(lqX-Label\(rq field
-.TP
-~z \fIMIN\fP-\fIMAX\fP
-messages with a size in the range \fIMIN\fP to \fIMAX\fP
-.TP
-~=
-duplicated messages (see $duplicate_threads)
-.TP
-~$
-unreferenced message (requires threaded view)
-.TP
-~(PATTERN)
-messages in threads containing messages matching a certain pattern, e.g. all threads containing messages from you: ~(~P)
-.PD 1
-.DT
-.PP
-In the above, \fIEXPR\fP is a regular expression.
-.PP
-With the \fB~m\fP, \fB~n\fP, \fB~X\fP, and \fB~z\fP operators, you can also
-specify ranges in the forms \fB<\fP\fIMAX\fP, \fB>\fP\fIMIN\fP,
-\fIMIN\fP\fB-\fP, and \fB-\fP\fIMAX\fP.
-.SS Matching dates
-.PP
-The \fB~d\fP and \fB~r\fP operators are used to match date ranges,
-which are interpreted to be given in your local time zone.
-.PP
-A date is of the form
-\fIDD\fP[\fB/\fP\fIMM\fP[\fB/\fP[\fIcc\fP]\fIYY\fP]], that is, a
-two-digit date, optionally followed by a two-digit month, optionally
-followed by a year specifications. Omitted fields default to the
-current month and year.
-.PP
-Mutt understands either two or four digit year specifications. When
-given a two-digit year, mutt will interpret values less than 70 as
-lying in the 21st century (i.e., \(lq38\(rq means 2038 and not 1938,
-and \(lq00\(rq is interpreted as 2000), and values
-greater than or equal to 70 as lying in the 20th century.
-.PP
-Note that this behaviour \fIis\fP Y2K compliant, but that mutt
-\fIdoes\fP have a Y2.07K problem.
-.PP
-If a date range consists of a single date, the operator in question
-will match that precise date. If the date range consists of a dash
-(\(lq\fB-\fP\(rq), followed by a date, this range will match any
-date before and up to the date given. Similarly, a date followed by
-a dash matches the date given and any later point of time. Two
-dates, separated by a dash, match any date which lies in the given
-range of time.
-.PP
-You can also modify any absolute date by giving an error range. An
-error range consists of one of the characters
-.BR + ,
-.BR - ,
-.BR * ,
-followed by a positive number, followed by one of the unit
-characters
-.BR y ,
-.BR m ,
-.BR w ", or"
-.BR d ,
-specifying a unit of years, months, weeks, or days.
-.B +
-increases the maximum date matched by the given interval of time,
-.B -
-decreases the minimum date matched by the given interval of time, and
-.B *
-increases the maximum date and decreases the minimum date matched by
-the given interval of time. It is possible to give multiple error
-margins, which cumulate. Example:
-.B "1/1/2001-1w+2w*3d"
-.PP
-You can also specify offsets relative to the current date. An
-offset is specified as one of the characters
-.BR < ,
-.BR > ,
-.BR = ,
-followed by a positive number, followed by one of the unit
-characters
-.BR y ,
-.BR m ,
-.BR w ", or"
-.BR d .
-.B >
-matches dates which are older than the specified amount of time, an
-offset which begins with the character
-.B <
-matches dates which are more recent than the specified amount of time,
-and an offset which begins with the character
-.B =
-matches points of time which are precisely the given amount of time
-ago.
-.SH CONFIGURATION VARIABLES
-
-.TP
-.B abort_nosubject
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-If set to \fIyes\fP, when composing messages and no subject is given
-at the subject prompt, composition will be aborted. If set to
-\fIno\fP, composing messages with no subject given at the subject
-prompt will never be aborted.
-
-
-.TP
-.B abort_unmodified
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-If set to \fIyes\fP, composition will automatically abort after
-editing the message body if no changes are made to the file (this
-check only happens after the \fIfirst\fP edit of the file). When set
-to \fIno\fP, composition will never be aborted.
-
-
-.TP
-.B alias_file
-.nf
-Type: path
-Default: \(lq~/.muttrc\(rq
-.fi
-.IP
-The default file in which to save aliases created by the
-\fC<create-alias>\fP function. Entries added to this file are
-encoded in the character set specified by $config_charset if it
-is \fIset\fP or the current character set otherwise.
-.IP
-\fBNote:\fP Mutt will not automatically source this file; you must
-explicitly use the \(lqsource\(rq command for it to be executed in case
-this option points to a dedicated alias file.
-.IP
-The default for this option is the currently used muttrc file, or
-\(lq~/.muttrc\(rq if no user muttrc was found.
-
-
-.TP
-.B alias_format
-.nf
-Type: string
-Default: \(lq%4n %2f %t %\-10a %r\(rq
-.fi
-.IP
-Specifies the format of the data displayed for the \(lqalias\(rq menu. The
-following \fCprintf(3)\fP\-style sequences are available:
-.RS
-.PD 0
-.TP
-%a
-alias name
-.TP
-%f
-flags \- currently, a \(lqd\(rq for an alias marked for deletion
-.TP
-%n
-index number
-.TP
-%r
-address which alias expands to
-.TP
-%t
-character which indicates if the alias is tagged for inclusion
-.RE
-.PD 1
-
-.TP
-.B allow_8bit
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether 8\-bit data is converted to 7\-bit using either Quoted\-
-Printable or Base64 encoding when sending mail.
-
-
-.TP
-.B allow_ansi
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-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 \fIset\fP,
-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
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-[\-\- PGP output follows ...
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-and give it the same color as your attachment color (see also
-$crypt_timestamp).
-
-
-.TP
-.B arrow_cursor
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, an arrow (\(lq\->\(rq) 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.
-
-
-.TP
-.B ascii_chars
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, Mutt will use plain ASCII characters when displaying thread
-and attachment trees, instead of the default \fIACS\fP characters.
-
-
-.TP
-.B askbcc
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, Mutt will prompt you for blind\-carbon\-copy (Bcc) recipients
-before editing an outgoing message.
-
-
-.TP
-.B askcc
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, Mutt will prompt you for carbon\-copy (Cc) recipients before
-editing the body of an outgoing message.
-
-
-.TP
-.B assumed_charset
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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 \(lqus\-ascii\(rq.
-.IP
-For example, Japanese users might prefer this:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set assumed_charset=\(rqiso\-2022\-jp:euc\-jp:shift_jis:utf\-8\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-However, only the first content is valid for the message body.
-
-
-.TP
-.B attach_charset
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This variable is a colon\-separated list of character encoding
-schemes for text file attachments. Mutt uses this setting to guess
-which encoding files being attached are encoded in to convert them to
-a proper character set given in $send_charset.
-.IP
-If \fIunset\fP, the value of $charset will be used instead.
-For example, the following configuration would work for Japanese
-text handling:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set attach_charset=\(rqiso\-2022\-jp:euc\-jp:shift_jis:utf\-8\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-Note: for Japanese users, \(lqiso\-2022\-*\(rq must be put at the head
-of the value as shown above if included.
-
-
-.TP
-.B attach_format
-.nf
-Type: string
-Default: \(lq%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] \(rq
-.fi
-.IP
-This variable describes the format of the \(lqattachment\(rq menu. The
-following \fCprintf(3)\fP\-style sequences are understood:
-.RS
-.PD 0
-.TP
-%C
-charset
-.TP
-%c
-requires charset conversion (\(lqn\(rq or \(lqc\(rq)
-.TP
-%D
-deleted flag
-.TP
-%d
-description
-.TP
-%e
-MIME content\-transfer\-encoding
-.TP
-%f
-filename
-.TP
-%I
-disposition (\(lqI\(rq for inline, \(lqA\(rq for attachment)
-.TP
-%m
-major MIME type
-.TP
-%M
-MIME subtype
-.TP
-%n
-attachment number
-.TP
-%Q
-\(lqQ\(rq, if MIME part qualifies for attachment counting
-.TP
-%s
-size
-.TP
-%t
-tagged flag
-.TP
-%T
-graphic tree characters
-.TP
-%u
-unlink (=to delete) flag
-.TP
-%X
-number of qualifying MIME parts in this part and its children
-(please see the \(lqattachments\(rq section for possible speed effects)
-.TP
-%>X
-right justify the rest of the string and pad with character \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with character \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-For an explanation of \(lqsoft\-fill\(rq, see the $index_format documentation.
-
-
-.TP
-.B attach_sep
-.nf
-Type: string
-Default: \(lq\\n\(rq
-.fi
-.IP
-The separator to add between attachments when operating (saving,
-printing, piping, etc) on a list of tagged attachments.
-
-
-.TP
-.B attach_split
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If this variable is \fIunset\fP, when operating (saving, printing, piping,
-etc) on a list of tagged attachments, Mutt will concatenate the
-attachments and will operate on them as a single attachment. The
-$attach_sep separator is added after each attachment. When \fIset\fP,
-Mutt will operate on the attachments one by one.
-
-
-.TP
-.B attribution
-.nf
-Type: string
-Default: \(lqOn %d, %n wrote:\(rq
-.fi
-.IP
-This is the string that will precede a message which has been included
-in a reply. For a full listing of defined \fCprintf(3)\fP\-like sequences see
-the section on $index_format.
-
-
-.TP
-.B autoedit
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP along with $edit_headers, Mutt will skip the initial
-send\-menu (prompting for subject and recipients) 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.
-.IP
-Also see $fast_reply.
-
-
-.TP
-.B auto_tag
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, functions in the \fIindex\fP menu which affect a message
-will be applied to all tagged messages (if there are any). When
-unset, you must first use the \fC<tag\-prefix>\fP function (bound to \(lq;\(rq
-by default) to make the next function apply to all tagged messages.
-
-
-.TP
-.B beep
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When this variable is \fIset\fP, mutt will beep when an error occurs.
-
-
-.TP
-.B beep_new
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, mutt will beep whenever it prints a message
-notifying you of new mail. This is independent of the setting of the
-$beep variable.
-
-
-.TP
-.B bounce
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether you will be asked to confirm bouncing messages.
-If set to \fIyes\fP you don't get asked if you want to bounce a
-message. Setting this variable to \fIno\fP is not generally useful,
-and thus not recommended, because you are unable to bounce messages.
-
-
-.TP
-.B bounce_delivered
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When this variable is \fIset\fP, mutt will include Delivered\-To headers when
-bouncing messages. Postfix users may wish to \fIunset\fP this variable.
-.IP
-\fBNote:\fP On Debian systems, this option is unset by default in
-/etc/Muttrc.
-
-
-.TP
-.B braille_friendly
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, mutt will place the cursor at the beginning
-of the current line in menus, even when the $arrow_cursor variable
-is \fIunset\fP, making it easier for blind persons using Braille displays to
-follow these menus. The option is \fIunset\fP by default because many
-visual terminals don't permit making the cursor invisible.
-
-
-.TP
-.B check_mbox_size
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
-.IP
-This variable is \fIunset\fP by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
-.IP
-Note that enabling this variable should happen before any \(lqmailboxes\(rq
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-
-
-.TP
-.B charset
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Character set your terminal uses to display and enter textual data.
-It is also the fallback for $send_charset.
-.IP
-Upon startup Mutt tries to derive this value from environment variables
-such as \fC$LC_CTYPE\fP or \fC$LANG\fP.
-.IP
-\fBNote:\fP It should only be set in case Mutt isn't abled to determine the
-character set used correctly.
-
-
-.TP
-.B check_new
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-\fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
-mailboxes.
-.IP
-When \fIset\fP, Mutt 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
-this variable is \fIunset\fP, no check for new mail is performed
-while the mailbox is open.
-
-
-.TP
-.B collapse_unread
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, Mutt will not collapse a thread if it contains any
-unread messages.
-
-
-.TP
-.B uncollapse_jump
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, Mutt will jump to the next unread message, if any,
-when the current thread is \fIun\fPcollapsed.
-
-
-.TP
-.B compose_format
-.nf
-Type: string
-Default: \(lq\-\- Mutt: Compose [Approx. msg size: %l Atts: %a]%>\-\(rq
-.fi
-.IP
-Controls the format of the status line displayed in the \(lqcompose\(rq
-menu. This string is similar to $status_format, but has its own
-set of \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%a
-total number of attachments
-.TP
-%h
-local hostname
-.TP
-%l
-approximate size (in bytes) of the current message
-.TP
-%v
-Mutt version string
-.RE
-.PD 1
-.IP
-See the text describing the $status_format option for more
-information on how to set $compose_format.
-
-
-.TP
-.B config_charset
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-When defined, Mutt will recode commands in rc files from this
-encoding to the current character set as specified by $charset
-and aliases written to $alias_file from the current character set.
-.IP
-Please note that if setting $charset it must be done before
-setting $config_charset.
-.IP
-Recoding should be avoided as it may render unconvertable
-characters as question marks which can lead to undesired
-side effects (for example in regular expressions).
-
-
-.TP
-.B confirmappend
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will prompt for confirmation when appending messages to
-an existing mailbox.
-
-
-.TP
-.B confirmcreate
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will prompt for confirmation when saving messages to a
-mailbox which does not yet exist before creating it.
-
-
-.TP
-.B connect_timeout
-.nf
-Type: number
-Default: 30
-.fi
-.IP
-Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-many seconds if the connection is not able to be established. A negative
-value causes Mutt to wait indefinitely for the connection attempt to succeed.
-
-
-.TP
-.B content_type
-.nf
-Type: string
-Default: \(lqtext/plain\(rq
-.fi
-.IP
-Sets the default Content\-Type for the body of newly composed messages.
-
-
-.TP
-.B copy
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-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 \(lqfcc-hook\(rq.
-
-
-.TP
-.B crypt_use_gpgme
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable controls the use of the GPGME\-enabled crypto backends.
-If it is \fIset\fP and Mutt was built with gpgme support, the gpgme code for
-S/MIME and PGP will be used instead of the classic code. Note that
-you need to set this option in .muttrc; it won't have any effect when
-used interactively.
-
-
-.TP
-.B crypt_use_pka
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Controls whether mutt uses PKA
-(see http://www.g10code.de/docs/pka\-intro.de.pdf) during signature
-verification (only supported by the GPGME backend).
-
-
-.TP
-.B crypt_autopgp
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages. See also $crypt_autoencrypt,
-$crypt_replyencrypt,
-$crypt_autosign, $crypt_replysign and $smime_is_default.
-
-
-.TP
-.B crypt_autosmime
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also $crypt_autoencrypt,
-$crypt_replyencrypt,
-$crypt_autosign, $crypt_replysign and $smime_is_default.
-
-
-.TP
-.B date_format
-.nf
-Type: string
-Default: \(lq!%a, %b %d, %Y at %I:%M:%S%p %Z\(rq
-.fi
-.IP
-This variable controls the format of the date printed by the \(lq%d\(rq
-sequence in $index_format. This is passed to the \fCstrftime(3)\fP
-function to process the date, see the man page for the proper syntax.
-.IP
-Unless the first character in the string is a bang (\(lq!\(rq), 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 \fIC\fP locale (that is in US
-English).
-
-
-.TP
-.B default_hook
-.nf
-Type: string
-Default: \(lq~f %s !~P | (~P ~C %s)\(rq
-.fi
-.IP
-This variable controls how \(lqmessage-hook\(rq, \(lqreply-hook\(rq, \(lqsend-hook\(rq,
-\(lqsend2-hook\(rq, \(lqsave-hook\(rq, and \(lqfcc-hook\(rq 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.
-.IP
-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
-\(lqalternates\(rq) and is to or cc'ed to a user matching the given
-regular expression.
-
-
-.TP
-.B delete
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not messages are really deleted when closing or
-synchronizing a mailbox. If set to \fIyes\fP, messages marked for
-deleting will automatically be purged without prompting. If set to
-\fIno\fP, messages marked for deletion will be kept in the mailbox.
-
-
-.TP
-.B delete_untag
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If this option is \fIset\fP, mutt 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.
-
-
-.TP
-.B digest_collapse
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If this option is \fIset\fP, mutt's received\-attachments menu will not show the subparts of
-individual messages in a multipart/digest. To see these subparts, press \(lqv\(rq on that menu.
-
-
-.TP
-.B display_filter
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-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.
-
-
-.TP
-.B dotlock_program
-.nf
-Type: path
-Default: \(lq/usr/bin/mutt_dotlock\(rq
-.fi
-.IP
-Contains the path of the \fCmutt_dotlock(8)\fP binary to be used by
-mutt.
-
-
-.TP
-.B dsn_notify
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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: \fInever\fP, to never request notification,
-\fIfailure\fP, to request notification on transmission failure,
-\fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
-notified of successful transmission.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set dsn_notify=\(rqfailure,delay\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\fBNote:\fP when using $sendmail for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a \fCsendmail(1)\fP\-compatible interface supporting the \fC\-N\fP option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-
-
-.TP
-.B dsn_return
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This variable controls how much of your message is returned in DSN
-messages. It may be set to either \fIhdrs\fP to return just the
-message header, or \fIfull\fP to return the full message.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set dsn_return=hdrs
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\fBNote:\fP when using $sendmail for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a \fCsendmail(1)\fP\-compatible interface supporting the \fC\-R\fP option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-
-
-.TP
-.B duplicate_threads
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable controls whether mutt, when $sort is set to \fIthreads\fP, threads
-messages with the same Message\-Id together. If it is \fIset\fP, it will indicate
-that it thinks they are duplicates of each other with an equals sign
-in the thread tree.
-
-
-.TP
-.B edit_headers
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This option allows you to edit the header of your outgoing messages
-along with the body of your message.
-.IP
-\fBNote\fP that changes made to the References: and Date: headers are
-ignored for interoperability reasons.
-
-
-.TP
-.B editor
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable specifies which editor is used by mutt.
-It defaults to the value of the \fC$VISUAL\fP, or \fC$EDITOR\fP, environment
-variable, or to the string \(lq/usr/bin/editor\(rq if neither of those are set.
-
-
-.TP
-.B encode_from
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will quoted\-printable encode messages when
-they contain the string \(lqFrom \(rq (note the trailing space) in the beginning of a line.
-This is useful to avoid the tampering certain mail delivery and transport
-agents tend to do with messages (in order to prevent tools from
-misinterpreting the line as a mbox message separator).
-
-
-.TP
-.B envelope_from_address
-.nf
-Type: e-mail address
-Default: \(lq\(rq
-.fi
-.IP
-Manually sets the \fIenvelope\fP sender for outgoing messages.
-This value is ignored if $use_envelope_from is \fIunset\fP.
-
-
-.TP
-.B escape
-.nf
-Type: string
-Default: \(lq~\(rq
-.fi
-.IP
-Escape character to use for functions in the builtin editor.
-
-
-.TP
-.B fast_reply
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, the initial prompt for recipients and subject are skipped
-when replying to messages, and the initial prompt for subject is
-skipped when forwarding messages.
-.IP
-\fBNote:\fP this variable has no effect when the $autoedit
-variable is \fIset\fP.
-
-
-.TP
-.B fcc_attach
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable controls whether or not attachments on outgoing messages
-are saved along with the main body of your message.
-
-
-.TP
-.B fcc_clear
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, FCCs will be stored unencrypted and
-unsigned, even when the actual message is encrypted and/or
-signed.
-(PGP only)
-
-
-.TP
-.B folder
-.nf
-Type: path
-Default: \(lq~/Mail\(rq
-.fi
-.IP
-Specifies the default location of your mailboxes. A \(lq+\(rq or \(lq=\(rq 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 \fIbefore\fP
-you use \(lq+\(rq or \(lq=\(rq for any other variables since expansion takes place
-when handling the \(lqmailboxes\(rq command.
-
-
-.TP
-.B folder_format
-.nf
-Type: string
-Default: \(lq%2C %t %N %F %2l %\-8.8u %\-8.8g %8s %d %f\(rq
-.fi
-.IP
-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 \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%C
-current file number
-.TP
-%d
-date/time folder was last modified
-.TP
-%f
-filename
-.TP
-%F
-file permissions
-.TP
-%g
-group name (or numeric gid, if missing)
-.TP
-%l
-number of hard links
-.TP
-%N
-N if folder has new mail, blank otherwise
-.TP
-%s
-size in bytes
-.TP
-%t
-\(lq*\(rq if the file is tagged, blank otherwise
-.TP
-%u
-owner name (or numeric uid, if missing)
-.TP
-%>X
-right justify the rest of the string and pad with character \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with character \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-For an explanation of \(lqsoft\-fill\(rq, see the $index_format documentation.
-
-
-.TP
-.B followup_to
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether or not the \(lqMail\-Followup\-To:\(rq header field is
-generated when sending mail. When \fIset\fP, Mutt will generate this
-field when you are replying to a known mailing list, specified with
-the \(lqsubscribe\(rq or \(lqlists\(rq commands.
-.IP
-This field has two purposes. First, preventing you from
-receiving duplicate copies of replies to messages which you send
-to mailing lists, and second, ensuring that you do get a reply
-separately for any messages sent to known lists to which you are
-not subscribed.
-.IP
-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.
-
-
-.TP
-.B force_name
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable is similar to $save_name, except that Mutt 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.
-.IP
-Also see the $record variable.
-
-
-.TP
-.B forward_decode
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls the decoding of complex MIME messages into \fCtext/plain\fP when
-forwarding a message. The message header is also RFC2047 decoded.
-This variable is only used, if $mime_forward is \fIunset\fP,
-otherwise $mime_forward_decode is used instead.
-
-
-.TP
-.B forward_edit
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-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 \(lqno\(rq.
-
-
-.TP
-.B forward_format
-.nf
-Type: string
-Default: \(lq[%a: %s]\(rq
-.fi
-.IP
-This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the $index_format variable.
-
-
-.TP
-.B forward_quote
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, forwarded messages included in the main body of the
-message (when $mime_forward is \fIunset\fP) will be quoted using
-$indent_string.
-
-
-.TP
-.B from
-.nf
-Type: e-mail address
-Default: \(lq\(rq
-.fi
-.IP
-When \fIset\fP, this variable contains a default from address. It
-can be overridden using \(lqmy_hdr\(rq (including from a \(lqsend-hook\(rq) and
-$reverse_name. This variable is ignored if $use_from is \fIunset\fP.
-.IP
-This setting defaults to the contents of the environment variable \fC$EMAIL\fP.
-
-
-.TP
-.B gecos_mask
-.nf
-Type: regular expression
-Default: \(lq^[^,]*\(rq
-.fi
-.IP
-A regular expression used by mutt to parse the GECOS field of a password
-entry when expanding the alias. The default value
-will return the string up to the first \(lq,\(rq encountered.
-If the GECOS field contains a string like \(lqlastname, firstname\(rq then you
-should set it to \(lq\fC.*\fP\(rq.
-.IP
-This can be useful if you see the following behavior: you address an e\-mail
-to user ID \(lqstevef\(rq whose full name is \(lqSteve Franklin\(rq. If mutt expands
-\(lqstevef\(rq to \(lq\(rqFranklin\(rq stevef@foo.bar\(rq then you should set the $gecos_mask to
-a regular expression that will match the whole name so mutt will expand
-\(lqFranklin\(rq to \(lqFranklin, Steve\(rq.
-
-
-.TP
-.B hdrs
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, the header fields normally added by the \(lqmy_hdr\(rq
-command are not created. This variable \fImust\fP be unset before
-composing a new message or replying in order to take effect. If \fIset\fP,
-the user defined header fields are added to every new message.
-
-
-.TP
-.B header
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, this variable causes Mutt to include the header
-of the message you are replying to into the edit buffer.
-The $weed setting applies.
-
-
-.TP
-.B help
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, help lines describing the bindings for the major functions
-provided by each menu are displayed on the first line of the screen.
-.IP
-\fBNote:\fP 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 is
-running. Since this variable is primarily aimed at new users, neither
-of these should present a major problem.
-
-
-.TP
-.B hidden_host
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt 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\-IDs, and it will not lead to the
-cut\-off of first\-level domains.
-
-
-.TP
-.B hide_limited
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will not show the presence of messages that are hidden
-by limiting, in the thread tree.
-
-
-.TP
-.B hide_missing
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will not show the presence of missing messages in the
-thread tree.
-
-
-.TP
-.B hide_thread_subject
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will not show the subject of messages in the thread
-tree that have the same subject as their parent or closest previously
-displayed sibling.
-
-
-.TP
-.B hide_top_limited
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt 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_limited is \fIset\fP, this option will have no effect.
-
-
-.TP
-.B hide_top_missing
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will not show the presence of missing messages at the
-top of threads in the thread tree. Note that when $hide_missing is
-\fIset\fP, this option will have no effect.
-
-
-.TP
-.B history
-.nf
-Type: number
-Default: 10
-.fi
-.IP
-This variable controls the size (in number of strings remembered) of
-the string history buffer per category. The buffer is cleared each time the
-variable is set.
-
-
-.TP
-.B history_file
-.nf
-Type: path
-Default: \(lq~/.mutthistory\(rq
-.fi
-.IP
-The file in which Mutt will save its history.
-
-
-.TP
-.B honor_followup_to
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-This variable controls whether or not a Mail\-Followup\-To header is
-honored when group\-replying to a message.
-
-
-.TP
-.B hostname
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the fully\-qualified hostname of the system mutt is running on
-containing the host's name and the DNS domain it belongs to. It is used
-as the domain part (after \(lq@\(rq) for local email addresses as well as
-Message\-Id headers.
-.IP
-Its value is determined at startup as follows: If the node's name
-as returned by the \fCuname(3)\fP function contains the hostname and the
-domain, these are used to construct $hostname. If there is no
-domain part returned, Mutt will look for a \(lqdomain\(rq or \(lqsearch\(rq
-line in \fC/etc/resolv.conf\fP to determine the domain. Optionally, Mutt
-can be compiled with a fixed domain name in which case a detected
-one is not used.
-.IP
-Also see $use_domain and $hidden_host.
-.IP
-\fBNote:\fP On Debian systems, the default for this variable is obtained
-from /etc/mailname when Mutt starts.
-
-
-.TP
-.B ignore_linear_white_space
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This option replaces linear\-white\-space between encoded\-word
-and text to a single space to prevent the display of MIME\-encoded
-\(lqSubject:\(rq field from being divided into multiple lines.
-
-
-.TP
-.B ignore_list_reply_to
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Affects the behaviour of the \fC<reply>\fP function when replying to
-messages from mailing lists (as defined by the \(lqsubscribe\(rq or
-\(lqlists\(rq commands). When \fIset\fP, if the \(lqReply\-To:\(rq field is
-set to the same value as the \(lqTo:\(rq field, Mutt assumes that the
-\(lqReply\-To:\(rq 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 \fIset\fP, use the \fC<list-reply>\fP
-function; \fC<group\-reply>\fP will reply to both the sender and the
-list.
-
-
-.TP
-.B imap_authenticators
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This is a colon\-delimited list of authentication methods mutt may
-attempt to use to log in to an IMAP server, in the order mutt should
-try them. Authentication methods are either \(lqlogin\(rq or the right
-side of an IMAP \(lqAUTH=xxx\(rq capability string, eg \(lqdigest\-md5\(rq, \(lqgssapi\(rq
-or \(lqcram\-md5\(rq. This option is case\-insensitive. If it's
-\fIunset\fP (the default) mutt will try all available methods,
-in order from most\-secure to least\-secure.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set imap_authenticators=\(rqgssapi:cram\-md5:login\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\fBNote:\fP Mutt will only fall back to other authentication methods if
-the previous methods are unavailable. If a method is available but
-authentication fails, mutt will not connect to the IMAP server.
-
-
-.TP
-.B imap_check_subscribed
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, 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 just as if you had issued individual \(lqmailboxes\(rq
-commands.
-
-
-.TP
-.B imap_delim_chars
-.nf
-Type: string
-Default: \(lq/.\(rq
-.fi
-.IP
-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 \(lq=\(rq shortcut for your \fIfolder\fP variable.
-
-
-.TP
-.B imap_headers
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Mutt requests these header fields in addition to the default headers
-(\(lqDate:\(rq, \(lqFrom:\(rq, \(lqSubject:\(rq, \(lqTo:\(rq, \(lqCc:\(rq, \(lqMessage\-Id:\(rq,
-\(lqReferences:\(rq, \(lqContent\-Type:\(rq, \(lqContent\-Description:\(rq, \(lqIn\-Reply\-To:\(rq,
-\(lqReply\-To:\(rq, \(lqLines:\(rq, \(lqList\-Post:\(rq, \(lqX\-Label:\(rq) from IMAP
-servers before displaying the index menu. You may want to add more
-headers for spam detection.
-.IP
-\fBNote:\fP This is a space separated list, items should be uppercase
-and not contain the colon, e.g. \(lqX\-BOGOSITY X\-SPAM\-STATUS\(rq for the
-\(lqX\-Bogosity:\(rq and \(lqX\-Spam\-Status:\(rq header fields.
-
-
-.TP
-.B imap_idle
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will attempt to use the IMAP IDLE extension
-to check for new mail in the current mailbox. Some servers
-(dovecot was the inspiration for this option) react badly
-to mutt's implementation. If your connection seems to freeze
-up periodically, try unsetting this.
-
-
-.TP
-.B imap_keepalive
-.nf
-Type: number
-Default: 900
-.fi
-.IP
-This variable specifies the maximum amount of time in seconds that mutt
-will wait before polling open IMAP connections, to prevent the server
-from closing them before mutt 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.
-
-
-.TP
-.B imap_list_subscribed
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-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 \fC<toggle\-subscribed>\fP function.
-
-
-.TP
-.B imap_login
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Your login name on the IMAP server.
-.IP
-This variable defaults to the value of $imap_user.
-
-
-.TP
-.B imap_pass
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the password for your IMAP account. If \fIunset\fP, Mutt will
-prompt you for your password when you invoke the \fC<fetch-mail>\fP function
-or try to open an IMAP folder.
-.IP
-\fBWarning\fP: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-
-
-.TP
-.B imap_passive
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will not open new IMAP connections to check for new
-mail. Mutt 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 invocation, or if opening the connection
-is slow.
-
-
-.TP
-.B imap_peek
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt 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.
-
-
-.TP
-.B imap_pipeline_depth
-.nf
-Type: number
-Default: 15
-.fi
-.IP
-Controls the number of IMAP commands that may be queued up before they
-are sent to the server. A deeper pipeline reduces the amount of time
-mutt must wait for the server, and can make IMAP servers feel much
-more responsive. But not all servers correctly handle pipelined commands,
-so if you have problems you might want to try setting this variable to 0.
-.IP
-\fBNote:\fP Changes to this variable have no effect on open connections.
-
-
-.TP
-.B imap_servernoise
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt 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.
-
-
-.TP
-.B imap_user
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-The name of the user whose mail you intend to access on the IMAP
-server.
-.IP
-This variable defaults to your user name on the local machine.
-
-
-.TP
-.B implicit_autoview
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If set to \(lqyes\(rq, mutt will look for a mailcap entry with the
-\(lq\fCcopiousoutput\fP\(rq flag set for \fIevery\fP MIME attachment it doesn't have
-an internal viewer defined for. If such an entry is found, mutt will
-use the viewer defined in that entry to convert the body part to text
-form.
-
-
-.TP
-.B include
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not a copy of the message(s) you are replying to
-is included in your reply.
-
-
-.TP
-.B include_onlyfirst
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Controls whether or not Mutt includes only the first attachment
-of the message you are replying.
-
-
-.TP
-.B indent_string
-.nf
-Type: string
-Default: \(lq> \(rq
-.fi
-.IP
-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.
-.IP
-This option is a format string, please see the description of
-$index_format for supported \fCprintf(3)\fP\-style sequences.
-.IP
-Because for \fCformat=lowed\fP style messages the quoting mechanism
-is strictly defined, this setting is ignored if $text_flowed is
-\fIset\fP.
-
-
-.TP
-.B index_format
-.nf
-Type: string
-Default: \(lq%4C %Z %{%b %d} %\-15.15L (%?l?%4l&%4c?) %s\(rq
-.fi
-.IP
-This variable allows you to customize the message index display to
-your personal taste.
-.IP
-\(lqFormat strings\(rq are similar to the strings used in the C
-function \fCprintf(3)\fP to format output (see the man page for more details).
-The following sequences are defined in Mutt:
-.RS
-.PD 0
-.TP
-%a
-address of the author
-.TP
-%A
-reply\-to address (if present; otherwise: address of author)
-.TP
-%b
-filename of the original message folder (think mailbox)
-.TP
-%B
-the list to which the letter was sent, or else the folder name (%b).
-.TP
-%c
-number of characters (bytes) in the message
-.TP
-%C
-current message number
-.TP
-%d
-date and time of the message in the format specified by
-$date_format converted to sender's time zone
-.TP
-%D
-date and time of the message in the format specified by
-$date_format converted to the local time zone
-.TP
-%e
-current message number in thread
-.TP
-%E
-number of messages in current thread
-.TP
-%f
-sender (address + real name), either From: or Return\-Path:
-.TP
-%F
-author name, or recipient name if the message is from you
-.TP
-%H
-spam attribute(s) of this message
-.TP
-%i
-message\-id of the current message
-.TP
-%l
-number of lines in the message (does not work with maildir,
-mh, and possibly IMAP folders)
-.TP
-%L
-If an address in the \(lqTo:\(rq or \(lqCc:\(rq header field matches an address
-defined by the users \(lqsubscribe\(rq command, this displays
-\(rqTo <list\-name>\(rq, otherwise the same as %F.
-.TP
-%m
-total number of message in the mailbox
-.TP
-%M
-number of hidden messages if the thread is collapsed.
-.TP
-%N
-message score
-.TP
-%n
-author's real name (or address if missing)
-.TP
-%O
-original save folder where mutt would formerly have
-stashed the message: list name or recipient name
-if not sent to a list
-.TP
-%P
-progress indicator for the builtin pager (how much of the file has been displayed)
-.TP
-%s
-subject of the message
-.TP
-%S
-status of the message (\(lqN\(rq/\(lqD\(rq/\(lqd\(rq/\(lq!\(rq/\(lqr\(rq/*)
-.TP
-%t
-\(lqTo:\(rq field (recipients)
-.TP
-%T
-the appropriate character from the $to_chars string
-.TP
-%u
-user (login) name of the author
-.TP
-%v
-first name of the author, or the recipient if the message is from you
-.TP
-%X
-number of attachments
-(please see the \(lqattachments\(rq section for possible speed effects)
-.TP
-%y
-\(lqX\-Label:\(rq field, if present
-.TP
-%Y
-\(lqX\-Label:\(rq field, if present, and \fI(1)\fP not at part of a thread tree,
-\fI(2)\fP at the top of a thread, or \fI(3)\fP \(lqX\-Label:\(rq is different from
-preceding message's \(lqX\-Label:\(rq.
-.TP
-%Z
-message status flags
-.TP
-%{fmt}
-the date and time of the message is converted to sender's
-time zone, and \(lqfmt\(rq is expanded by the library function
-\fCstrftime(3)\fP; a leading bang disables locales
-.TP
-%[fmt]
-the date and time of the message is converted to the local
-time zone, and \(lqfmt\(rq is expanded by the library function
-\fCstrftime(3)\fP; a leading bang disables locales
-.TP
-%(fmt)
-the local date and time when the message was received.
-\(lqfmt\(rq is expanded by the library function \fCstrftime(3)\fP;
-a leading bang disables locales
-.TP
-%<fmt>
-the current local time. \(lqfmt\(rq is expanded by the library
-function \fCstrftime(3)\fP; a leading bang disables locales.
-.TP
-%>X
-right justify the rest of the string and pad with character \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with character \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-\(lqSoft\-fill\(rq deserves some explanation: Normal right\-justification
-will print everything to the left of the \(lq%>\(rq, displaying padding and
-whatever lies to the right only if there's room. By contrast,
-soft\-fill gives priority to the right\-hand side, guaranteeing space
-to display it and showing padding only if there's still room. If
-necessary, soft\-fill will eat text leftwards to make room for
-rightward text.
-.IP
-Note that these expandos are supported in
-\(lqsave-hook\(rq, \(lqfcc-hook\(rq and \(lqfcc-save-hook\(rq, too.
-
-
-.TP
-.B ispell
-.nf
-Type: path
-Default: \(lqispell\(rq
-.fi
-.IP
-How to invoke ispell (GNU's spell\-checking software).
-
-
-.TP
-.B keep_flagged
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, read messages marked as flagged will not be moved
-from your spool mailbox to your $mbox mailbox, or as a result of
-a \(lqmbox-hook\(rq command.
-
-
-.TP
-.B locale
-.nf
-Type: string
-Default: \(lqC\(rq
-.fi
-.IP
-The locale used by \fCstrftime(3)\fP to format dates. Legal values are
-the strings your system accepts for the locale environment variable \fC$LC_TIME\fP.
-
-
-.TP
-.B mail_check
-.nf
-Type: number
-Default: 5
-.fi
-.IP
-This variable configures how often (in seconds) mutt should look for
-new mail. Also see the $timeout variable.
-
-
-.TP
-.B mailcap_path
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This variable specifies which files to consult when attempting to
-display MIME bodies not directly supported by Mutt.
-
-
-.TP
-.B mailcap_sanitize
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, mutt 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.
-.IP
-\fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
-DOING!\fP
-
-
-.TP
-.B maildir_mtime
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If set, the sort\-by\-date option in the browser will sort maildirs
-smartly, not using the mtime of the maildir itself but that of the
-newest message in the new subdirectory, making the sorting by
-reverse date much more useful. People with maildirs over NFS may
-wish to leave this option unset.
-
-
-.TP
-.B header_cache
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is \fIunset\fP so no header
-caching will be used.
-.IP
-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see \(lqcaching\(rq for details.
-
-
-.TP
-.B maildir_header_cache_verify
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Check for Maildir unaware programs other than mutt having modified maildir
-files when the header cache is in use. This incurs one \fCstat(2)\fP per
-message every time the folder is opened (which can be very slow for NFS
-folders).
-
-
-.TP
-.B header_cache_pagesize
-.nf
-Type: string
-Default: \(lq16384\(rq
-.fi
-.IP
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-
-
-.TP
-.B maildir_trash
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, messages marked as deleted will be saved with the maildir
-trashed flag instead of unlinked. \fBNote:\fP this only applies
-to maildir\-style mailboxes. Setting it will have no effect on other
-mailbox types.
-
-
-.TP
-.B mark_old
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether or not mutt marks \fInew\fP \fBunread\fP
-messages as \fIold\fP if you exit a mailbox without reading them.
-With this option \fIset\fP, the next time you start mutt, the messages
-will show up with an \(lqO\(rq next to them in the index menu,
-indicating that they are old.
-
-
-.TP
-.B markers
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls the display of wrapped lines in the internal pager. If set, a
-\(lq+\(rq marker is displayed at the beginning of wrapped lines.
-.IP
-Also see the $smart_wrap variable.
-
-
-.TP
-.B mask
-.nf
-Type: regular expression
-Default: \(lq!^\\.[^.]\(rq
-.fi
-.IP
-A regular expression used in the file browser, optionally preceded by
-the \fInot\fP operator \(lq!\(rq. Only files whose names match this mask
-will be shown. The match is always case\-sensitive.
-
-
-.TP
-.B mbox
-.nf
-Type: path
-Default: \(lq~/mbox\(rq
-.fi
-.IP
-This specifies the folder into which read mail in your $spoolfile
-folder will be appended.
-.IP
-Also see the $move variable.
-
-
-.TP
-.B mbox_type
-.nf
-Type: folder magic
-Default: mbox
-.fi
-.IP
-The default mailbox type used when creating new folders. May be any of
-\(lqmbox\(rq, \(lqMMDF\(rq, \(lqMH\(rq and \(lqMaildir\(rq.
-
-
-.TP
-.B metoo
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIunset\fP, Mutt will remove your address (see the \(lqalternates\(rq
-command) from the list of recipients when replying to a message.
-
-
-.TP
-.B menu_context
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to $pager_context.)
-
-
-.TP
-.B menu_move_off
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, the bottom entry of menus will never scroll up past
-the bottom of the screen, unless there are less entries than lines.
-When \fIset\fP, the bottom entry may move off the bottom.
-
-
-.TP
-.B menu_scroll
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, menus will be scrolled up or down one line when you
-attempt to move across a screen boundary. If \fIunset\fP, the screen
-is cleared and the next or previous page of the menu is displayed
-(useful for slow links to avoid many redraws).
-
-
-.TP
-.B meta_key
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, forces Mutt 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 \fC0xf8\fP, then this is treated as if the user had
-pressed Esc then \(lqx\(rq. This is because the result of removing the
-high bit from \fC0xf8\fP is \fC0x78\fP, which is the ASCII character
-\(lqx\(rq.
-
-
-.TP
-.B mh_purge
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIunset\fP, mutt will mimic mh's behaviour and rename deleted messages
-to \fI,<old file name>\fP in mh folders instead of really deleting
-them. This leaves the message on disk but makes programs reading the folder
-ignore it. If the variable is \fIset\fP, the message files will simply be
-deleted.
-.IP
-This option is similar to $maildir_trash for Maildir folders.
-
-
-.TP
-.B mh_seq_flagged
-.nf
-Type: string
-Default: \(lqflagged\(rq
-.fi
-.IP
-The name of the MH sequence used for flagged messages.
-
-
-.TP
-.B mh_seq_replied
-.nf
-Type: string
-Default: \(lqreplied\(rq
-.fi
-.IP
-The name of the MH sequence used to tag replied messages.
-
-
-.TP
-.B mh_seq_unseen
-.nf
-Type: string
-Default: \(lqunseen\(rq
-.fi
-.IP
-The name of the MH sequence used for unseen messages.
-
-
-.TP
-.B mime_forward
-.nf
-Type: quadoption
-Default: no
-.fi
-.IP
-When \fIset\fP, the message you are forwarding will be attached as a
-separate \fCmessage/rfc822\fP 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 \(lqask\-no\(rq or \(lqask\-yes\(rq.
-.IP
-Also see $forward_decode and $mime_forward_decode.
-
-
-.TP
-.B mime_forward_decode
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Controls the decoding of complex MIME messages into \fCtext/plain\fP when
-forwarding a message while $mime_forward is \fIset\fP. Otherwise
-$forward_decode is used instead.
-
-
-.TP
-.B mime_forward_rest
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-When forwarding multiple attachments of a MIME message from the attachment
-menu, attachments which cannot be decoded in a reasonable manner will
-be attached to the newly composed message if this option is \fIset\fP.
-
-
-.TP
-.B mix_entry_format
-.nf
-Type: string
-Default: \(lq%4n %c %\-16s %a\(rq
-.fi
-.IP
-This variable describes the format of a remailer line on the mixmaster
-chain selection screen. The following \fCprintf(3)\fP\-like sequences are
-supported:
-.RS
-.PD 0
-.TP
-%n
-The running number on the menu.
-.TP
-%c
-Remailer capabilities.
-.TP
-%s
-The remailer's short name.
-.TP
-%a
-The remailer's e\-mail address.
-.RE
-.PD 1
-
-.TP
-.B mixmaster
-.nf
-Type: path
-Default: \(lqmixmaster\(rq
-.fi
-.IP
-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.
-.IP
-\fBNote:\fP On Debian systems, this option is set by default to
-\(lqmixmaster\-filter\(rq in /etc/Muttrc.
-
-
-.TP
-.B move
-.nf
-Type: quadoption
-Default: no
-.fi
-.IP
-Controls whether or not Mutt will move read messages
-from your spool mailbox to your $mbox mailbox, or as a result of
-a \(lqmbox-hook\(rq command.
-
-
-.TP
-.B message_cachedir
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-.IP
-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-.IP
-Also see the $message_cache_clean variable.
-
-
-.TP
-.B message_cache_clean
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-
-
-.TP
-.B message_format
-.nf
-Type: string
-Default: \(lq%s\(rq
-.fi
-.IP
-This is the string displayed in the \(lqattachment\(rq menu for
-attachments of type \fCmessage/rfc822\fP. For a full listing of defined
-\fCprintf(3)\fP\-like sequences see the section on $index_format.
-
-
-.TP
-.B narrow_tree
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable, when \fIset\fP, makes the thread tree narrower, allowing
-deeper threads to fit on the screen.
-
-
-.TP
-.B net_inc
-.nf
-Type: number
-Default: 10
-.fi
-.IP
-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.
-.IP
-See also $read_inc, $write_inc and $net_inc.
-
-
-.TP
-.B pager
-.nf
-Type: path
-Default: \(lqbuiltin\(rq
-.fi
-.IP
-This variable specifies which pager you would like to use to view
-messages. The value \(lqbuiltin\(rq means to use the builtin pager, otherwise this
-variable should specify the pathname of the external pager you would
-like to use.
-.IP
-Using an external pager may have some disadvantages: Additional
-keystrokes are necessary because you can't call mutt functions
-directly from the pager, and screen resizes cause lines longer than
-the screen width to be badly formatted in the help menu.
-
-
-.TP
-.B pager_context
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-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 will display the line after the last one on the screen
-at the top of the next page (0 lines of context).
-
-
-.TP
-.B pager_format
-.nf
-Type: string
-Default: \(lq\-%Z\- %C/%m: %\-20.20n %s%* \-\- (%P)\(rq
-.fi
-.IP
-This variable controls the format of the one\-line message \(lqstatus\(rq
-displayed before each message in either the internal or an external
-pager. The valid sequences are listed in the $index_format
-section.
-
-
-.TP
-.B pager_index_lines
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-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 setting 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.
-
-
-.TP
-.B pager_stop
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, the internal\-pager will \fBnot\fP move to the next message
-when you are at the end of a message and invoke the \fC<next\-page>\fP
-function.
-
-
-.TP
-.B crypt_autosign
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Setting this variable will cause Mutt 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 \fIset\fP,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-
-
-.TP
-.B crypt_autoencrypt
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages. This is probably only useful in
-connection to the \(lqsend-hook\(rq 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 \fIset\fP,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-
-
-.TP
-.B pgp_ignore_subkeys
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
-if you want to play interesting key selection games.
-(PGP only)
-
-
-.TP
-.B crypt_replyencrypt
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-
-
-.TP
-.B crypt_replysign
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
-signed.
-.IP
-\fBNote:\fP this does not work on messages that are encrypted
-\fIand\fP signed!
-(Crypto only)
-
-
-.TP
-.B crypt_replysignencrypted
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, 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 is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-
-
-.TP
-.B crypt_timestamp
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, mutt 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 \fIunset\fP this setting.
-(Crypto only)
-
-
-.TP
-.B sidebar_delim
-.nf
-Type: string
-Default: \(lq|\(rq
-.fi
-.IP
-This specifies the delimiter between the sidebar (if visible) and
-other screens.
-
-
-.TP
-.B sidebar_visible
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This specifies whether or not to show sidebar (left\-side list of folders).
-
-
-.TP
-.B sidebar_width
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-The width of the sidebar.
-
-
-.TP
-.B pgp_use_gpg_agent
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, mutt will use a possibly\-running \fCgpg\-agent(1)\fP process.
-(PGP only)
-
-
-.TP
-.B crypt_verify_sig
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-If \fI\(lqyes\(rq\fP, always attempt to verify PGP or S/MIME signatures.
-If \fI\(lqask\-*\(rq\fP, ask whether or not to verify the signature.
-If \\Fi\(lqno\(rq\fP, never attempt to verify cryptographic signatures.
-(Crypto only)
-
-
-.TP
-.B smime_is_default
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-The default behaviour of mutt is to use PGP on all auto\-sign/encryption
-operations. To override and to use OpenSSL instead this must be \fIset\fP.
-However, this has no effect while replying, since mutt 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)
-
-
-.TP
-.B smime_ask_cert_label
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-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
-\fIset\fP by default.
-(S/MIME only)
-
-
-.TP
-.B smime_decrypt_use_default_key
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate\-key\-pairs, mutt 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)
-
-
-.TP
-.B pgp_entry_format
-.nf
-Type: string
-Default: \(lq%4n %t%f %4l/0x%k %\-4a %2c %u\(rq
-.fi
-.IP
-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 \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%n
-number
-.TP
-%k
-key id
-.TP
-%u
-user id
-.TP
-%a
-algorithm
-.TP
-%l
-key length
-.TP
-%f
-flags
-.TP
-%c
-capabilities
-.TP
-%t
-trust/validity of the key\-uid association
-.TP
-%[<s>]
-date of the key where <s> is an \fCstrftime(3)\fP expression
-.RE
-.PD 1
-.IP
-(PGP only)
-
-
-.TP
-.B pgp_good_sign
-.nf
-Type: regular expression
-Default: \(lq\(rq
-.fi
-.IP
-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)
-
-
-.TP
-.B pgp_check_exit
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, mutt 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)
-
-
-.TP
-.B pgp_long_ids
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, use 64 bit PGP key IDs, if \fIunset\fP use the normal 32 bit key IDs.
-(PGP only)
-
-
-.TP
-.B pgp_retainable_sigs
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, signed and encrypted messages will consist of nested
-\fCmultipart/signed\fP and \fCmultipart/encrypted\fP body parts.
-.IP
-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (\fCmultipart/encrypted\fP) can be easily
-removed, while the inner \fCmultipart/signed\fP part is retained.
-(PGP only)
-
-
-.TP
-.B pgp_autoinline
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This option controls whether Mutt 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.
-.IP
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-.IP
-Also see the $pgp_mime_auto variable.
-.IP
-Also note that using the old\-style PGP message format is \fBstrongly\fP
-\fBdeprecated\fP.
-(PGP only)
-
-
-.TP
-.B pgp_replyinline
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Setting this variable will cause Mutt 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
-internals for previously checked/flagged messages.
-.IP
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-.IP
-Also see the $pgp_mime_auto variable.
-.IP
-Also note that using the old\-style PGP message format is \fBstrongly\fP
-\fBdeprecated\fP.
-(PGP only)
-
-
-.TP
-.B pgp_show_unusable
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, mutt 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 \(lqdisabled\(rq by the user.
-(PGP only)
-
-
-.TP
-.B pgp_sign_as
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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. \fC0x00112233\fP).
-(PGP only)
-
-
-.TP
-.B pgp_strict_enc
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, Mutt 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)
-
-
-.TP
-.B pgp_timeout
-.nf
-Type: number
-Default: 300
-.fi
-.IP
-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-
-
-.TP
-.B pgp_sort_keys
-.nf
-Type: sort order
-Default: address
-.fi
-.IP
-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-.RS
-.PD 0
-.TP
-address
-sort alphabetically by user id
-.TP
-keyid
-sort alphabetically by key id
-.TP
-date
-sort by key creation date
-.TP
-trust
-sort by the trust of the key
-.RE
-.PD 1
-.IP
-If you prefer reverse order of the above values, prefix it with
-\(lqreverse\-\(rq.
-(PGP only)
-
-
-.TP
-.B pgp_mime_auto
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-.IP
-Also note that using the old\-style PGP message format is \fBstrongly\fP
-\fBdeprecated\fP.
-(PGP only)
-
-
-.TP
-.B pgp_auto_decode
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, mutt 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 \fC<check-traditional-pgp>\fP function, mutt will automatically
-check the message for traditional pgp.
-
-
-.TP
-.B pgp_mime_signature_filename
-.nf
-Type: string
-Default: \(lqsignature.asc\(rq
-.fi
-.IP
-This option sets the filename used for signature parts in PGP/MIME
-signed messages.
-
-
-.TP
-.B pgp_mime_signature_description
-.nf
-Type: string
-Default: \(lqDigital signature\(rq
-.fi
-.IP
-This option sets the Content\-Description used for signature parts in
-PGP/MIME signed messages.
-
-
-.TP
-.B pgp_decode_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This format strings specifies a command which is used to decode
-application/pgp attachments.
-.IP
-The PGP command formats have their own set of \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%p
-Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-string otherwise. Note: This may be used with a %? construct.
-.TP
-%f
-Expands to the name of a file containing a message.
-.TP
-%s
-Expands to the name of a file containing the signature part
- of a \fCmultipart/signed\fP attachment when verifying it.
-.TP
-%a
-The value of $pgp_sign_as.
-.TP
-%r
-One or more key IDs.
-.RE
-.PD 1
-.IP
-For examples on how to configure these formats for the various versions
-of PGP which are floating around, see the pgp and gpg sample configuration files in
-the \fCsamples/\fP subdirectory which has been installed on your system
-alongside the documentation.
-(PGP only)
-
-
-.TP
-.B pgp_getkeys_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by $pgp_decode_command, %r is the only
-\fCprintf(3)\fP\-like sequence used with this format.
-(PGP only)
-
-
-.TP
-.B pgp_verify_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to verify PGP signatures.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_decrypt_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to decrypt a PGP encrypted message.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_clearsign_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This format is used to create an old\-style \(lqclearsigned\(rq PGP
-message. Note that the use of this format is \fBstrongly\fP
-\fBdeprecated\fP.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_sign_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to create the detached PGP signature for a
-\fCmultipart/signed\fP PGP/MIME body part.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_encrypt_sign_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to both sign and encrypt a body part.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_encrypt_only_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to encrypt a body part without signing it.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_import_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to import a key from a message into
-the user's public key ring.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_export_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to export a public key from the user's
-key ring.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_verify_key_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to verify key information from the key selection
-menu.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_list_secring_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to list the secret key ring's contents. The
-output format must be analogous to the one used by:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-gpg \-\-list\-keys \-\-with\-colons.
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-This format is also generated by the \fCpgpring\fP utility which comes
-with mutt.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_list_pubring_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to list the public key ring's contents. The
-output format must be analogous to the one used by
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-gpg \-\-list\-keys \-\-with\-colons.
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-This format is also generated by the \fCpgpring\fP utility which comes
-with mutt.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B forward_decrypt
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls the handling of encrypted messages when forwarding a message.
-When \fIset\fP, the outer layer of encryption is stripped off. This
-variable is only used if $mime_forward is \fIset\fP and
-$mime_forward_decode is \fIunset\fP.
-(PGP only)
-
-
-.TP
-.B smime_timeout
-.nf
-Type: number
-Default: 300
-.fi
-.IP
-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-
-
-.TP
-.B smime_encrypt_with
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This sets the algorithm that should be used for encryption.
-Valid choices are \(lqdes\(rq, \(lqdes3\(rq, \(lqrc2\-40\(rq, \(lqrc2\-64\(rq, \(lqrc2\-128\(rq.
-If \fIunset\fP, \(lq3des\(rq (TripleDES) is used.
-(S/MIME only)
-
-
-.TP
-.B smime_keys
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and 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 option points to the location of the private keys.
-(S/MIME only)
-
-
-.TP
-.B smime_ca_location
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-.IP
-\fBNote:\fP On Debian systems, this defaults to the first existing file in
-the following list: ~/.smime/ca\-certificates.crt ~/.smime/ca\-bundle.crt
-/etc/ssl/certs/ca\-certificates.crt.
-
-
-.TP
-.B smime_certificates
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-the location of the certificates.
-(S/MIME only)
-
-
-.TP
-.B smime_decrypt_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This format string specifies a command which is used to decrypt
-\fCapplication/x\-pkcs7\-mime\fP attachments.
-.IP
-The OpenSSL command formats have their own set of \fCprintf(3)\fP\-like sequences
-similar to PGP's:
-.RS
-.PD 0
-.TP
-%f
-Expands to the name of a file containing a message.
-.TP
-%s
-Expands to the name of a file containing the signature part
- of a \fCmultipart/signed\fP attachment when verifying it.
-.TP
-%k
-The key\-pair specified with $smime_default_key
-.TP
-%c
-One or more certificate IDs.
-.TP
-%a
-The algorithm used for encryption.
-.TP
-%C
-CA location: Depending on whether $smime_ca_location
- points to a directory or file, this expands to
- \(lq\-CApath $smime_ca_location\(rq or \(lq\-CAfile $smime_ca_location\(rq.
-.RE
-.PD 1
-.IP
-For examples on how to configure these formats, see the \fCsmime.rc\fP in
-the \fCsamples/\fP subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-
-
-.TP
-.B smime_verify_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to verify S/MIME signatures of type \fCmultipart/signed\fP.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_verify_opaque_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to verify S/MIME signatures of type
-\fCapplication/x\-pkcs7\-mime\fP.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_sign_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to created S/MIME signatures of type
-\fCmultipart/signed\fP, which can be read by all mail clients.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_sign_opaque_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to created S/MIME signatures of type
-\fCapplication/x\-pkcs7\-signature\fP, which can only be handled by mail
-clients supporting the S/MIME extension.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_encrypt_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to create encrypted S/MIME messages.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_pk7out_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_get_cert_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to extract X509 certificates from a PKCS7 structure.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_get_signer_cert_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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 \(lqFrom:\(rq field.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_import_cert_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to import a certificate via smime_keys.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_get_cert_email_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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).
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_default_key
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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)
-
-
-.TP
-.B ssl_client_cert
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-The file containing a client certificate and its associated private
-key.
-
-
-.TP
-.B ssl_force_tls
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If this variable is \fIset\fP, Mutt 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.
-
-
-.TP
-.B ssl_starttls
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-If \fIset\fP (the default), mutt will attempt to use \fCSTARTTLS\fP on servers
-advertising the capability. When \fIunset\fP, mutt will not attempt to
-use \fCSTARTTLS\fP regardless of the server's capabilities.
-
-
-.TP
-.B certificate_file
-.nf
-Type: path
-Default: \(lq~/.mutt_certificates\(rq
-.fi
-.IP
-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.
-.IP
-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set certificate_file=~/.mutt/certificates
-
-.fi
-.ec
-.ft P
-.sp
-
-
-.TP
-.B ssl_use_sslv3
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-
-
-.TP
-.B ssl_use_tlsv1
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-
-
-.TP
-.B ssl_min_dh_prime_bits
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-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.
-
-
-.TP
-.B ssl_ca_certificates_file
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set ssl_ca_certificates_file=/etc/ssl/certs/ca\-certificates.crt
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\fBNote:\fP On Debian systems, this variable defaults to the example
-mentioned. This file is managed by the \(lqca\-certificates\(rq package.
-
-
-.TP
-.B pipe_split
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Used in connection with the \fC<pipe\-message>\fP function following
-\fC<tag\-prefix>\fP. If this variable is \fIunset\fP, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated. When \fIset\fP, Mutt 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.
-
-
-.TP
-.B pipe_decode
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Used in connection with the \fC<pipe\-message>\fP command. When \fIunset\fP,
-Mutt will pipe the messages without any preprocessing. When \fIset\fP, Mutt
-will weed headers and will attempt to decode the messages
-first.
-
-
-.TP
-.B pipe_sep
-.nf
-Type: string
-Default: \(lq\\n\(rq
-.fi
-.IP
-The separator to add between messages when piping a list of tagged
-messages to an external Unix command.
-
-
-.TP
-.B pop_authenticators
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This is a colon\-delimited list of authentication methods mutt may
-attempt to use to log in to an POP server, in the order mutt should
-try them. Authentication methods are either \(lquser\(rq, \(lqapop\(rq or any
-SASL mechanism, eg \(lqdigest\-md5\(rq, \(lqgssapi\(rq or \(lqcram\-md5\(rq.
-This option is case\-insensitive. If this option is \fIunset\fP
-(the default) mutt will try all available methods, in order from
-most\-secure to least\-secure.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set pop_authenticators=\(rqdigest\-md5:apop:user\(rq
-
-.fi
-.ec
-.ft P
-.sp
-
-
-.TP
-.B pop_auth_try_all
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, Mutt will try all available authentication methods.
-When \fIunset\fP, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-
-
-.TP
-.B pop_checkinterval
-.nf
-Type: number
-Default: 60
-.fi
-.IP
-This variable configures how often (in seconds) mutt should look for
-new mail in the currently selected mailbox if it is a POP mailbox.
-
-
-.TP
-.B pop_delete
-.nf
-Type: quadoption
-Default: ask\-no
-.fi
-.IP
-If \fIset\fP, Mutt will delete successfully downloaded messages from the POP
-server when using the \fC<fetch-mail>\fP function. When \fIunset\fP, Mutt will
-download messages but also leave them on the POP server.
-
-
-.TP
-.B pop_host
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-The name of your POP server for the \fC<fetch-mail>\fP function. You
-can also specify an alternative port, username and password, ie:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-[pop[s]://][username[:password]@]popserver[:port]
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-where \(lq[...]\(rq denotes an optional part.
-
-
-.TP
-.B pop_last
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If this variable is \fIset\fP, mutt will try to use the \(lq\fCLAST\fP\(rq POP command
-for retrieving only unread messages from the POP server when using
-the \fC<fetch-mail>\fP function.
-
-
-.TP
-.B pop_reconnect
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-
-
-.TP
-.B pop_user
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Your login name on the POP server.
-.IP
-This variable defaults to your user name on the local machine.
-
-
-.TP
-.B pop_pass
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the password for your POP account. If \fIunset\fP, Mutt will
-prompt you for your password when you open a POP mailbox.
-.IP
-\fBWarning\fP: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc
-even if you are the only one who can read the file.
-
-
-.TP
-.B post_indent_string
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Similar to the $attribution variable, Mutt will append this
-string after the inclusion of a message which is being replied to.
-
-
-.TP
-.B postpone
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not messages are saved in the $postponed
-mailbox when you elect not to send immediately.
-.IP
-Also see the $recall variable.
-
-
-.TP
-.B postponed
-.nf
-Type: path
-Default: \(lq~/postponed\(rq
-.fi
-.IP
-Mutt allows you to indefinitely \(lqpostpone sending a message\(rq which
-you are editing. When you choose to postpone a message, Mutt saves it
-in the mailbox specified by this variable.
-.IP
-Also see the $postpone variable.
-
-
-.TP
-.B preconnect
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-If \fIset\fP, a shell command to be executed if mutt fails to establish
-a connection to the server. This is useful for setting up secure
-connections, e.g. with \fCssh(1)\fP. If the command returns a nonzero
-status, mutt gives up opening the server. Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set preconnect=\(rqssh \-f \-q \-L 1234:mailhost.net:143 mailhost.net \\
-sleep 20 < /dev/null > /dev/null\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-Mailbox \(lqfoo\(rq on \(lqmailhost.net\(rq can now be reached
-as \(lq{localhost:1234}foo\(rq.
-.IP
-Note: For this example to work, you must be able to log in to the
-remote machine without having to enter a password.
-.IP
-When set, Mutt uses the tunnel for all remote connections.
-Please see \(lqaccount-hook\(rq in the manual for how to use different
-tunnel commands per connection.
-
-
-.TP
-.B print
-.nf
-Type: quadoption
-Default: ask\-no
-.fi
-.IP
-Controls whether or not Mutt really prints messages.
-This is set to \(lqask\-no\(rq by default, because some people
-accidentally hit \(lqp\(rq often.
-
-
-.TP
-.B print_command
-.nf
-Type: path
-Default: \(lqlpr\(rq
-.fi
-.IP
-This specifies the command pipe that should be used to print messages.
-
-
-.TP
-.B print_decode
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Used in connection with the \fC<print\-message>\fP command. If this
-option is \fIset\fP, the message is decoded before it is passed to the
-external command specified by $print_command. If this option
-is \fIunset\fP, 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.
-
-
-.TP
-.B print_split
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Used in connection with the \fC<print\-message>\fP command. If this option
-is \fIset\fP, the command specified by $print_command is executed once for
-each message which is to be printed. If this option is \fIunset\fP,
-the command specified by $print_command is executed only once, and
-all the messages are concatenated, with a form feed as the message
-separator.
-.IP
-Those who use the \fCenscript\fP(1) program's mail\-printing mode will
-most likely want to \fIset\fP this option.
-
-
-.TP
-.B prompt_after
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If you use an \fIexternal\fP $pager, setting this variable will
-cause Mutt to prompt you for a command when the pager exits rather
-than returning to the index menu. If \fIunset\fP, Mutt will return to the
-index menu when the external pager exits.
-
-
-.TP
-.B query_command
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This specifies the command that mutt will use to make external address
-queries. The string should contain a \(lq%s\(rq, which will be substituted
-with the query string the user types. See \(lqquery\(rq for more
-information.
-
-
-.TP
-.B query_format
-.nf
-Type: string
-Default: \(lq%4c %t %\-25.25a %\-25.25n %?e?(%e)?\(rq
-.fi
-.IP
-This variable describes the format of the \(lqquery\(rq menu. The
-following \fCprintf(3)\fP\-style sequences are understood:
-.RS
-.PD 0
-.TP
-%a
-destination address
-.TP
-%c
-current entry number
-.TP
-%e
-extra information *
-.TP
-%n
-destination name
-.TP
-%t
-\(lq*\(rq if current entry is tagged, a space otherwise
-.TP
-%>X
-right justify the rest of the string and pad with \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-For an explanation of \(lqsoft\-fill\(rq, see the $index_format documentation.
-.IP
-* = can be optionally printed if nonzero, see the $status_format documentation.
-
-
-.TP
-.B quit
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-This variable controls whether \(lqquit\(rq and \(lqexit\(rq actually quit
-from mutt. If this option is \fIset\fP, they do quit, if it is \fIunset\fP, they
-have no effect, and if it is set to \fIask\-yes\fP or \fIask\-no\fP, you are
-prompted for confirmation when you try to quit.
-
-
-.TP
-.B quote_regexp
-.nf
-Type: regular expression
-Default: \(lq^([ \\t]*[|>:}#])+\(rq
-.fi
-.IP
-A regular expression used in the internal pager to determine quoted
-sections of text in the body of a message. Quoted text may be filtered
-out using the \fC<toggle\-quoted>\fP command, or colored according to the
-\(lqcolor quoted\(rq family of directives.
-.IP
-Higher levels of quoting may be colored differently (\(lqcolor quoted1\(rq,
-\(lqcolor quoted2\(rq, etc.). The quoting level is determined by removing
-the last character from the matched text and recursively reapplying
-the regular expression until it fails to produce a match.
-.IP
-Match detection may be overridden by the $smileys regular expression.
-
-
-.TP
-.B read_inc
-.nf
-Type: number
-Default: 10
-.fi
-.IP
-If set to a value greater than 0, Mutt will display which message it
-is currently on when reading a mailbox or when performing search actions
-such as search and limit. The message is printed after
-this many messages have been read or searched (e.g., if set to 25, Mutt will
-print a message when it is at message 25, and then again when it gets
-to message 50). This variable is meant to indicate progress when
-reading or searching large mailboxes which may take some time.
-When set to 0, only a single message will appear before the reading
-the mailbox.
-.IP
-Also see the $write_inc, $net_inc and $time_inc variables and the
-\(lqtuning\(rq section of the manual for performance considerations.
-
-
-.TP
-.B read_only
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, all folders are opened in read\-only mode.
-
-
-.TP
-.B realname
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This variable specifies what \(lqreal\(rq or \(lqpersonal\(rq name should be used
-when sending messages.
-.IP
-By default, this is the GECOS field from \fC/etc/passwd\fP. Note that this
-variable will \fInot\fP be used when the user has set a real name
-in the $from variable.
-
-
-.TP
-.B recall
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not Mutt recalls postponed messages
-when composing a new message.
-.IP
-\fISetting\fP this variable to is not generally useful, and thus not
-recommended.
-.IP
-Also see $postponed variable.
-
-
-.TP
-.B record
-.nf
-Type: path
-Default: \(lq~/sent\(rq
-.fi
-.IP
-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 \(lqmy_hdr\(rq
-command to create a \(lqBcc:\(rq field with your email address in it.)
-.IP
-The value of \fI$record\fP is overridden by the $force_name and
-$save_name variables, and the \(lqfcc-hook\(rq command.
-
-
-.TP
-.B reply_regexp
-.nf
-Type: regular expression
-Default: \(lq^(re([\\[0\-9\\]+])*|aw):[ \\t]*\(rq
-.fi
-.IP
-A regular expression used to recognize reply messages when threading
-and replying. The default value corresponds to the English \(rqRe:\(rq and
-the German \(rqAw:\(rq.
-
-
-.TP
-.B reply_self
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIunset\fP and you are replying to a message sent by you, Mutt will
-assume that you want to reply to the recipients of that message rather
-than to yourself.
-.IP
-Also see the \(lqalternates\(rq command.
-
-
-.TP
-.B reply_to
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-If \fIset\fP, when replying to a message, Mutt will use the address listed
-in the Reply\-to: header as the recipient of the reply. If \fIunset\fP,
-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.
-
-
-.TP
-.B resolve
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, the cursor will be automatically advanced to the next
-(possibly undeleted) message whenever a command that modifies the
-current message is executed.
-
-
-.TP
-.B reverse_alias
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable controls whether or not Mutt will display the \(lqpersonal\(rq
-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:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-alias juser abd30425@somewhere.net (Joe User)
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-and then you receive mail which contains the following header:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-From: abd30425@somewhere.net
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-It would be displayed in the index menu as \(lqJoe User\(rq instead of
-\(lqabd30425@somewhere.net.\(rq This is useful when the person's e\-mail
-address is not human friendly.
-
-
-.TP
-.B reverse_name
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-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 \fIset\fP, the default \fIFrom:\fP line of
-the reply messages is built using the address where you received the
-messages you are replying to \fBif\fP that address matches your
-\(lqalternates\(rq. If the variable is \fIunset\fP, or the address that would be
-used doesn't match your \(lqalternates\(rq, the \fIFrom:\fP line will use
-your address on the current machine.
-.IP
-Also see the \(lqalternates\(rq command.
-
-
-.TP
-.B reverse_realname
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable fine\-tunes the behaviour of the $reverse_name feature.
-When it is \fIset\fP, mutt will use the address from incoming messages as\-is,
-possibly including eventual real names. When it is \fIunset\fP, mutt will
-override any such real names with the setting of the $realname variable.
-
-
-.TP
-.B rfc2047_parameters
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, Mutt will decode RFC2047\-encoded MIME
-parameters. You want to set this variable when mutt suggests you
-to save attachments to files named like:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-=?iso\-8859\-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-When this variable is \fIset\fP interactively, the change won't be
-active until you change folders.
-.IP
-Note that this use of RFC2047's encoding is explicitly
-prohibited by the standard, but nevertheless encountered in the
-wild.
-.IP
-Also note that setting this parameter will \fInot\fP have the effect
-that mutt \fIgenerates\fP this kind of encoding. Instead, mutt will
-unconditionally use the encoding specified in RFC2231.
-
-
-.TP
-.B save_address
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If $save_name or $force_name
-is \fIset\fP too, the selection of the Fcc folder will be changed as well.
-
-
-.TP
-.B save_empty
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, mailboxes which contain no saved messages will be removed
-when closed (the exception is $spoolfile which is never removed).
-If \fIset\fP, mailboxes are never removed.
-.IP
-\fBNote:\fP This only applies to mbox and MMDF folders, Mutt does not
-delete MH and Maildir directories.
-
-
-.TP
-.B save_history
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-This variable controls the size of the history (per category) saved in the
-$history_file file.
-
-
-.TP
-.B save_name
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable controls how copies of outgoing messages are saved.
-When \fIset\fP, 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 \fIusername\fP 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.
-.IP
-Also see the $force_name variable.
-
-
-.TP
-.B score
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When this variable is \fIunset\fP, scoring is turned off. This can
-be useful to selectively disable scoring for certain folders when the
-$score_threshold_delete variable and related are used.
-
-
-.TP
-.B score_threshold_delete
-.nf
-Type: number
-Default: \-1
-.fi
-.IP
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked for deletion by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message for deletion.
-
-
-.TP
-.B score_threshold_flag
-.nf
-Type: number
-Default: 9999
-.fi
-.IP
-Messages which have been assigned a score greater than or equal to this
-variable's value are automatically marked \(rqflagged\(rq.
-
-
-.TP
-.B score_threshold_read
-.nf
-Type: number
-Default: \-1
-.fi
-.IP
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked as read by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message read.
-
-
-.TP
-.B send_charset
-.nf
-Type: string
-Default: \(lqus\-ascii:iso\-8859\-1:utf\-8\(rq
-.fi
-.IP
-A colon\-delimited list of character sets for outgoing messages. Mutt will use the
-first character set into which the text can be converted exactly.
-If your $charset is not \(lqiso\-8859\-1\(rq and recipients may not
-understand \(lqUTF\-8\(rq, it is advisable to include in the list an
-appropriate widely used standard character set (such as
-\(lqiso\-8859\-2\(rq, \(lqkoi8\-r\(rq or \(lqiso\-2022\-jp\(rq) either instead of or after
-\(lqiso\-8859\-1\(rq.
-.IP
-In case the text cannot be converted into one of these exactly,
-mutt uses $charset as a fallback.
-
-
-.TP
-.B sendmail
-.nf
-Type: path
-Default: \(lq/usr/sbin/sendmail \-oem \-oi\(rq
-.fi
-.IP
-Specifies the program and arguments used to deliver mail sent by Mutt.
-Mutt expects that the specified program interprets additional
-arguments as recipient addresses.
-
-
-.TP
-.B sendmail_wait
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-Specifies the number of seconds to wait for the $sendmail process
-to finish before giving up and putting delivery in the background.
-.IP
-Mutt interprets the value of this variable as follows:
-.RS
-.PD 0
-.TP
->0
-number of seconds to wait for sendmail to finish before continuing
-.TP
-0
-wait forever for sendmail to finish
-.TP
-<0
-always put sendmail in the background without waiting
-.RE
-.PD 1
-.IP
-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.
-
-
-.TP
-.B shell
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Command to use when spawning a subshell. By default, the user's login
-shell from \fC/etc/passwd\fP is used.
-
-
-.TP
-.B sig_dashes
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, a line containing \(lq\-\- \(rq (note the trailing space) will be inserted before your
-$signature. It is \fBstrongly\fP recommended that you not \fIunset\fP
-this variable unless your signature contains just your name. The
-reason for this is because many software packages use \(lq\-\- \\n\(rq to
-detect your signature. For example, Mutt has the ability to highlight
-the signature in a different color in the builtin pager.
-
-
-.TP
-.B sig_on_top
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, the signature will be included before any quoted or forwarded
-text. It is \fBstrongly\fP 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.
-
-
-.TP
-.B signature
-.nf
-Type: path
-Default: \(lq~/.signature\(rq
-.fi
-.IP
-Specifies the filename of your signature, which is appended to all
-outgoing messages. If the filename ends with a pipe (\(lq|\(rq), it is
-assumed that filename is a shell command and input should be read from
-its standard output.
-
-
-.TP
-.B simple_search
-.nf
-Type: string
-Default: \(lq~f %s | ~s %s\(rq
-.fi
-.IP
-Specifies how Mutt should expand a simple search into a real search
-pattern. A simple search is one that does not contain any of the \(lq~\(rq pattern
-operators. See \(lqpatterns\(rq for more information on search patterns.
-.IP
-For example, if you simply type \(lqjoe\(rq at a search or limit prompt, Mutt
-will automatically expand it to the value specified by this variable by
-replacing \(lq%s\(rq with the supplied string.
-For the default value, \(lqjoe\(rq would be expanded to: \(lq~f joe | ~s joe\(rq.
-
-
-.TP
-.B smart_wrap
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls the display of lines longer than the screen width in the
-internal pager. If \fIset\fP, long lines are wrapped at a word boundary. If
-\fIunset\fP, lines are simply wrapped at the screen edge. Also see the
-$markers variable.
-
-
-.TP
-.B smileys
-.nf
-Type: regular expression
-Default: \(lq(>From )|(:[\-^]?[][)(><}{|/DP])\(rq
-.fi
-.IP
-The \fIpager\fP uses this variable to catch some common false
-positives of $quote_regexp, most notably smileys and not consider
-a line quoted text if it also matches $smileys. This mostly
-happens at the beginning of a line.
-
-
-.TP
-.B sleep_time
-.nf
-Type: number
-Default: 1
-.fi
-.IP
-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.
-
-
-.TP
-.B smtp_authenticators
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This is a colon\-delimited list of authentication methods mutt may
-attempt to use to log in to an SMTP server, in the order mutt should
-try them. Authentication methods are any SASL mechanism, eg
-\(lqdigest\-md5\(rq, \(lqgssapi\(rq or \(lqcram\-md5\(rq.
-This option is case\-insensitive. If it is \(lqunset\(rq
-(the default) mutt will try all available methods, in order from
-most\-secure to least\-secure.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set smtp_authenticators=\(rqdigest\-md5:cram\-md5\(rq
-
-.fi
-.ec
-.ft P
-.sp
-
-
-.TP
-.B smtp_pass
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the password for your SMTP account. If \fIunset\fP, Mutt will
-prompt you for your password when you first send mail via SMTP.
-See $smtp_url to configure mutt to send mail via SMTP.
-.IP
-\fBWarning\fP: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-
-
-.TP
-.B smtp_url
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Defines the SMTP smarthost where sent messages should relayed for
-delivery. This should take the form of an SMTP URL, eg:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-smtp[s]://[user[:pass]@]host[:port]/
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\\.\\.\\. where \(lq[...]\(rq denotes an optional part.
-Setting this variable overrides the value of the $sendmail
-variable.
-
-
-.TP
-.B sort
-.nf
-Type: sort order
-Default: date
-.fi
-.IP
-Specifies how to sort messages in the \(lqindex\(rq menu. Valid values
-are:
-.RS
-.PD 0
-.TP
-\(hy date or date\-sent
-.TP
-\(hy date\-received
-.TP
-\(hy from
-.TP
-\(hy mailbox\-order (unsorted)
-.TP
-\(hy score
-.TP
-\(hy size
-.TP
-\(hy spam
-.TP
-\(hy subject
-.TP
-\(hy threads
-.TP
-\(hy to
-.RE
-.PD 1
-.IP
-You may optionally use the \(lqreverse\-\(rq prefix to specify reverse sorting
-order (example: \(lq\fCset sort=reverse\-date\-sent\fP\(rq).
-.IP
-\fBNote:\fP On Debian systems, this option is set by default to
-\(lqthreads\(rq in /etc/Muttrc.
-
-
-.TP
-.B sort_alias
-.nf
-Type: sort order
-Default: alias
-.fi
-.IP
-Specifies how the entries in the \(lqalias\(rq menu are sorted. The
-following are legal values:
-.RS
-.PD 0
-.TP
-\(hy address (sort alphabetically by email address)
-.TP
-\(hy alias (sort alphabetically by alias name)
-.TP
-\(hy unsorted (leave in order specified in .muttrc)
-.RE
-.PD 1
-
-.TP
-.B sort_aux
-.nf
-Type: sort order
-Default: date
-.fi
-.IP
-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
-\(lqthreads\(rq (in that case, mutt will just use \(lqdate\-sent\(rq). You can also
-specify the \(lqlast\-\(rq prefix in addition to the \(lqreverse\-\(rq prefix, but \(lqlast\-\(rq
-must come after \(lqreverse\-\(rq. The \(lqlast\-\(rq 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,
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set sort_aux=last\-date\-received
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-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 \(lq\fCset sort=reverse\-threads\fP\(rq.)
-.IP
-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).
-
-
-.TP
-.B sort_browser
-.nf
-Type: sort order
-Default: alpha
-.fi
-.IP
-Specifies how to sort entries in the file browser. By default, the
-entries are sorted alphabetically. Valid values:
-.RS
-.PD 0
-.TP
-\(hy alpha (alphabetically)
-.TP
-\(hy date
-.TP
-\(hy size
-.TP
-\(hy unsorted
-.RE
-.PD 1
-.IP
-You may optionally use the \(lqreverse\-\(rq prefix to specify reverse sorting
-order (example: \(lq\fCset sort_browser=reverse\-date\fP\(rq).
-
-
-.TP
-.B sort_re
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable is only useful when sorting by threads with
-$strict_threads \fIunset\fP. In that case, it changes the heuristic
-mutt uses to thread messages by subject. With $sort_re \fIset\fP, mutt 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_re \fIunset\fP, mutt will attach
-the message whether or not this is the case, as long as the
-non\-$reply_regexp parts of both messages are identical.
-
-
-.TP
-.B spam_separator
-.nf
-Type: string
-Default: \(lq,\(rq
-.fi
-.IP
-This variable controls what happens when multiple spam headers
-are matched: if \fIunset\fP, each successive header will overwrite any
-previous matches value for the spam label. If \fIset\fP, each successive
-match will append to the previous, using this variable's value as a
-separator.
-
-
-.TP
-.B spoolfile
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-If your spool mailbox is in a non\-default place where Mutt cannot find
-it, you can specify its location with this variable. Mutt will
-automatically set this variable to the value of the environment
-variable \fC$MAIL\fP if it is not set.
-
-
-.TP
-.B status_chars
-.nf
-Type: string
-Default: \(lq\-*%A\(rq
-.fi
-.IP
-Controls the characters used by the \(lq%r\(rq 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 \fC<toggle\-write>\fP operation, bound by default to \(lq%\(rq). 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).
-
-
-.TP
-.B status_format
-.nf
-Type: string
-Default: \(lq\-%r\-Mutt: %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)\-\-\-\(rq
-.fi
-.IP
-Controls the format of the status line displayed in the \(lqindex\(rq
-menu. This string is similar to $index_format, but has its own
-set of \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%b
-number of mailboxes with new mail *
-.TP
-%d
-number of deleted messages *
-.TP
-%f
-the full pathname of the current mailbox
-.TP
-%F
-number of flagged messages *
-.TP
-%h
-local hostname
-.TP
-%l
-size (in bytes) of the current mailbox *
-.TP
-%L
-size (in bytes) of the messages shown
-(i.e., which match the current limit) *
-.TP
-%m
-the number of messages in the mailbox *
-.TP
-%M
-the number of messages shown (i.e., which match the current limit) *
-.TP
-%n
-number of new messages in the mailbox *
-.TP
-%o
-number of old unread messages *
-.TP
-%p
-number of postponed messages *
-.TP
-%P
-percentage of the way through the index
-.TP
-%r
-modified/read\-only/won't\-write/attach\-message indicator,
-according to $status_chars
-.TP
-%s
-current sorting mode ($sort)
-.TP
-%S
-current aux sorting method ($sort_aux)
-.TP
-%t
-number of tagged messages *
-.TP
-%u
-number of unread messages *
-.TP
-%v
-Mutt version string
-.TP
-%V
-currently active limit pattern, if any *
-.TP
-%>X
-right justify the rest of the string and pad with \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-For an explanation of \(lqsoft\-fill\(rq, see the $index_format documentation.
-.IP
-* = can be optionally printed if nonzero
-.IP
-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:
-.IP
-\fC%?<sequence_char>?<optional_string>?\fP
-.IP
-where \fIsequence_char\fP is a character from the table above, and
-\fIoptional_string\fP is the string you would like printed if
-\fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
-other sequences as well as normal text, but you may \fBnot\fP nest
-optional strings.
-.IP
-Here is an example illustrating how to optionally print the number of
-new messages in a mailbox:
-.IP
-\fC%?n?%n new messages.?\fP
-.IP
-You can also switch between two strings using the following construct:
-.IP
-\fC%?<sequence_char>?<if_string>&<else_string>?\fP
-.IP
-If the value of \fIsequence_char\fP is non\-zero, \fIif_string\fP will
-be expanded, otherwise \fIelse_string\fP will be expanded.
-.IP
-You can force the result of any \fCprintf(3)\fP\-like sequence to be lowercase
-by prefixing the sequence character with an underscore (\(lq_\(rq) sign.
-For example, if you want to display the local hostname in lowercase,
-you would use: \(lq\fC%_h\fP\(rq.
-.IP
-If you prefix the sequence character with a colon (\(lq:\(rq) character, mutt
-will replace any dots in the expansion by underscores. This might be helpful
-with IMAP folders that don't like dots in folder names.
-
-
-.TP
-.B status_on_top
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Setting this variable causes the \(lqstatus bar\(rq to be displayed on
-the first line of the screen rather than near the bottom. If $help
-is \fIset\fP, too it'll be placed at the bottom.
-
-
-.TP
-.B strict_threads
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, threading will only make use of the \(lqIn\-Reply\-To\(rq and
-\(lqReferences:\(rq fields when you $sort by message threads. By
-default, messages with the same subject are grouped together in
-\(lqpseudo threads.\(rq. This may not always be desirable, such as in a
-personal mailbox where you might have several unrelated messages with
-the subjects like \(lqhi\(rq which will get grouped together. See also
-$sort_re for a less drastic way of controlling this
-behaviour.
-
-
-.TP
-.B suspend
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, mutt won't stop when the user presses the terminal's
-\fIsusp\fP key, usually \(lq^Z\(rq. This is useful if you run mutt
-inside an xterm using a command like \(lq\fCxterm \-e mutt\fP\(rq.
-
-
-.TP
-.B text_flowed
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will generate \(lqformat=flowed\(rq bodies with a content type
-of \(lq\fCtext/plain; format=flowed\fP\(rq.
-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.
-.IP
-Note that $indent_string is ignored when this option is \fIset\fP.
-
-
-.TP
-.B thread_received
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt uses the date received rather than the date sent
-to thread messages by subject.
-
-
-.TP
-.B thorough_search
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Affects the \fC~b\fP and \fC~h\fP search operations described in
-section \(lqpatterns\(rq. If \fIset\fP, the headers and body/attachments of
-messages to be searched are decoded before searching. If \fIunset\fP,
-messages are searched as they appear in the folder.
-.IP
-Users searching attachments or for non\-ASCII characters should \fIset\fP
-this value because decoding also includes MIME parsing/decoding and possible
-character set conversions. Otherwise mutt will attempt to match against the
-raw message received (for example quoted\-printable encoded or with encoded
-headers) which may lead to incorrect search results.
-
-
-.TP
-.B tilde
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, the internal\-pager will pad blank lines to the bottom of the
-screen with a tilde (\(lq~\(rq).
-
-
-.TP
-.B time_inc
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-Along with $read_inc, $write_inc, and $net_inc, this
-variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than $time_inc milliseconds
-apart. This can improve throughput on systems with slow terminals,
-or when running mutt on a remote system.
-.IP
-Also see the \(lqtuning\(rq section of the manual for performance considerations.
-
-
-.TP
-.B timeout
-.nf
-Type: number
-Default: 600
-.fi
-.IP
-When Mutt is waiting for user input either idleing in menus or
-in an interactive prompt, Mutt would block until input is
-present. Depending on the context, this would prevent certain
-operations from working, like checking for new mail or keeping
-an IMAP connection alive.
-.IP
-This variable controls how many seconds Mutt will at most wait
-until it aborts waiting for input, performs these operations and
-continues to wait for input.
-.IP
-A value of zero or less will cause Mutt to never time out.
-
-
-.TP
-.B tmpdir
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable allows you to specify where Mutt will place its
-temporary files needed for displaying and composing messages. If
-this variable is not set, the environment variable \fC$TMPDIR\fP is
-used. If \fC$TMPDIR\fP is not set then \(lq\fC/tmp\fP\(rq is used.
-
-
-.TP
-.B to_chars
-.nf
-Type: string
-Default: \(lq +TCFL\(rq
-.fi
-.IP
-Controls the character used to indicate mail addressed to you. The
-first character is the one used when the mail is \fInot\fP addressed to your
-address. The second is used when you are the only
-recipient of the message. The third is when your address
-appears in the \(lqTo:\(rq header field, but you are not the only recipient of
-the message. The fourth character is used when your
-address is specified in the \(lqCc:\(rq header field, but you are not the only
-recipient. The fifth character is used to indicate mail that was sent
-by \fIyou\fP. The sixth character is used to indicate when a mail
-was sent to a mailing\-list you subscribe to.
-
-
-.TP
-.B trash
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-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.
-.IP
-NOTE: When you delete a message in the trash folder, it is really
-deleted, so that you have a way to clean the trash.
-
-
-.TP
-.B tunnel
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Setting this variable will cause mutt 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/SMTP server. Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set tunnel=\(rqssh \-q mailhost.net /usr/local/libexec/imapd\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-Note: For this example to work you must be able to log in to the remote
-machine without having to enter a password.
-
-
-.TP
-.B use_8bitmime
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-\fBWarning:\fP do not set this variable unless you are using a version
-of sendmail which supports the \fC\-B8BITMIME\fP flag (such as sendmail
-8.8.x) or you may not be able to send mail.
-.IP
-When \fIset\fP, Mutt will invoke $sendmail with the \fC\-B8BITMIME\fP
-flag when sending 8\-bit messages to enable ESMTP negotiation.
-
-
-.TP
-.B use_domain
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will qualify all local addresses (ones without the
-\(lq@host\(rq portion) with the value of $hostname. If \fIunset\fP, no
-addresses will be qualified.
-
-
-.TP
-.B use_envelope_from
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will set the \fIenvelope\fP sender of the message.
-If $envelope_from_address is \fIset\fP, it will be used as the sender
-address. If \fIunset\fP, mutt will attempt to derive the sender from the
-\(lqFrom:\(rq header.
-.IP
-Note that this information is passed to sendmail command using the
-\fC\-f\fP command line switch. Therefore setting this option is not useful
-if the $sendmail variable already contains \fC\-f\fP or if the
-executable pointed to by $sendmail doesn't support the \fC\-f\fP switch.
-
-
-.TP
-.B use_from
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will generate the \(lqFrom:\(rq header field when
-sending messages. If \fIunset\fP, no \(lqFrom:\(rq header field will be
-generated unless the user explicitly sets one using the \(lqmy_hdr\(rq
-command.
-
-
-.TP
-.B use_idn
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will show you international domain names decoded.
-Note: You can use IDNs for addresses even if this is \fIunset\fP.
-This variable only affects decoding.
-
-
-.TP
-.B use_ipv6
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will look for IPv6 addresses of hosts it tries to
-contact. If this option is \fIunset\fP, Mutt will restrict itself to IPv4 addresses.
-Normally, the default should work.
-
-
-.TP
-.B user_agent
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will add a \(lqUser\-Agent:\(rq header to outgoing
-messages, indicating which version of mutt was used for composing
-them.
-
-
-.TP
-.B visual
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the visual editor to invoke when the \(lq\fC~v\fP\(rq command is
-given in the builtin editor.
-
-
-.TP
-.B wait_key
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether Mutt will ask you to press a key after an external command
-has been invoked by these functions: \fC<shell\-escape>\fP,
-\fC<pipe\-message>\fP, \fC<pipe\-entry>\fP, \fC<print\-message>\fP,
-and \fC<print\-entry>\fP commands.
-.IP
-It is also used when viewing attachments with \(lqauto_view\(rq, provided
-that the corresponding mailcap entry has a \fIneedsterminal\fP flag,
-and the external program is interactive.
-.IP
-When \fIset\fP, Mutt will always ask for a key. When \fIunset\fP, Mutt will wait
-for a key only if the external command returned a non\-zero status.
-
-
-.TP
-.B weed
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will weed headers when displaying, forwarding,
-printing, or replying to messages.
-
-
-.TP
-.B wrap
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-When set to a positive value, mutt will wrap text at $wrap characters.
-When set to a negative value, mutt will wrap text so that there are $wrap
-characters of empty space on the right side of the terminal.
-
-
-.TP
-.B wrap_search
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether searches wrap around the end.
-.IP
-When \fIset\fP, searches will wrap around the first (or last) item. When
-\fIunset\fP, incremental searches will not wrap.
-
-
-.TP
-.B wrapmargin
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-(DEPRECATED) Equivalent to setting $wrap with a negative value.
-
-
-.TP
-.B write_inc
-.nf
-Type: number
-Default: 10
-.fi
-.IP
-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.
-.IP
-Also see the $read_inc, $net_inc and $time_inc variables and the
-\(lqtuning\(rq section of the manual for performance considerations.
-
-
-.TP
-.B write_bcc
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether mutt writes out the \(lqBcc:\(rq header when preparing
-messages to be sent. Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see $smtp_url), this
-option does nothing: mutt will never write out the \(lqBcc:\(rq header
-in this case.
-.IP
-\fBNote:\fP On Debian systems, exim4 and postfix strip BCC headers by
-default. The above warning applies to exim3 users, see /etc/Muttrc.
-
-
-.TP
-.B xterm_icon
-.nf
-Type: string
-Default: \(lqM%?n?AIL&ail?\(rq
-.fi
-.IP
-Controls the format of the icon title, as long as xterm_set_titles
-is enabled. This string is identical in formatting to the one used by
-\(lq$status_format\(rq.
-
-
-.TP
-.B xterm_set_titles
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Controls whether mutt sets the xterm title bar and icon name
-(as long as you are in an appropriate terminal).
-
-
-.TP
-.B xterm_title
-.nf
-Type: string
-Default: \(lqMutt with %?m?%m messages&no messages?%?n? [%n NEW]?\(rq
-.fi
-.IP
-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 \(lq$status_format\(rq.
-
-
-.\" -*-nroff-*-
-.SH SEE ALSO
-.PP
-.BR iconv (1),
-.BR iconv (3),
-.BR mailcap (5),
-.BR maildir (5),
-.BR mbox (5),
-.BR mutt (1),
-.BR printf (3),
-.BR regex (7),
-.BR strftime (3)
-.PP
-The Mutt Manual
-.PP
-The Mutt home page: http://www.mutt.org/
-.SH AUTHOR
-.PP
-Michael Elkins, and others. Use <mutt-dev@mutt.org> to contact
-the developers.
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Optional features</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="mimesupport.html" title="Chapter 5. Mutt's MIME Support" /><link rel="next" href="tuning.html" title="Chapter 7. Performance tuning" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Optional features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="mimesupport.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="tuning.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="optionalfeatures"></a>Chapter 6. Optional features</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="optionalfeatures.html#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#exact-address">8. Exact address generation</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="optionalfeatures-notes"></a>1. General notes</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compile-time-features"></a>1.1. Enabling/disabling features</h3></div></div></div><p>
-Mutt supports several of optional features which can be enabled or
-disabled at compile-time by giving the <span class="emphasis"><em>configure</em></span> script
-certain arguments. These are listed in the “<span class="quote">Optional features</span>” section of
-the <span class="emphasis"><em>configure --help</em></span> output.
-</p><p>
-Which features are enabled or disabled can later be determined from the
-output of <code class="literal">mutt -v</code>. If a compile option starts with
-“<span class="quote">+</span>” it is enabled and disabled if prefixed with “<span class="quote">-</span>”. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
-OpenSSL, <code class="literal">mutt -v</code> would contain:
-</p><pre class="screen">
--USE_SSL_OPENSSL +USE_SSL_GNUTLS</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="url-syntax"></a>1.2. URL syntax</h3></div></div></div><p>
-Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
-to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in <code class="literal">[]</code> means it is optional and
-may be omitted):
-</p><pre class="screen">
-proto[s]://[username[:password]@]server[:port]/[path]
-</pre><p>
-<code class="literal">proto</code> is the communication protocol:
-<code class="literal">imap</code> for IMAP, <code class="literal">pop</code> for POP3 and
-<code class="literal">smtp</code> for SMTP. If “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”
-is appended, mutt will attempt to establish an encrypted communication
-using SSL or TLS. If no explicit port is given, mutt will use the
-system's default for the given protocol.
-</p><p>
-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the <code class="literal">pop_user</code> or
-<code class="literal">imap_user</code> variables. It may contain the “<span class="quote">@</span>” symbol
-being used by many mail systems as part of the login name. A password can be
-given, too but is not recommended if the URL is specified in a configuration
-file on disk.
-</p><p>
-The optional path is only relevant for IMAP.
-</p><p>
-For IMAP for example, you can select an alternative port by specifying it with the
-server: <code class="literal">imap://imapserver:port/INBOX</code>. You can also specify different
-username for each folder: <code class="literal">imap://username@imapserver[:port]/INBOX</code>
-or <code class="literal">imap://username2@imapserver[:port]/path/to/folder</code>.
-Replacing <code class="literal">imap://</code> by <code class="literal">imaps://</code>
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ssl"></a>2. SSL/TLS Support</h2></div></div></div><p>
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
-compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
-by running the <span class="emphasis"><em>configure</em></span> script with the
-<span class="emphasis"><em>--enable-ssl=...</em></span> option for OpenSSL or
-<span class="emphasis"><em>--enable-gnutls=...</em></span> for GnuTLS). Mutt can then
-attempt to encrypt communication with remote servers if these protocols
-are suffixed with “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="pop"></a>3. POP3 Support</h2></div></div></div><p>
-If Mutt was compiled with POP3 support (by running the <span class="emphasis"><em>configure</em></span>
-script with the <span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work
-with mailboxes located on a remote POP3 server and fetch mail for local
-browsing.
-</p><p>
-Remote POP3 servers can be accessed using URLs with the <code class="literal">pop</code> protocol
-for unencrypted and <code class="literal">pops</code> for encrypted
-communication, see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details.
-</p><p>
-Polling for new mail is more expensive over POP3 than locally. For this
-reason the frequency at which Mutt will check for mail remotely can be
-controlled by the
-<a class="link" href="reference.html#pop-checkinterval" title="3.218. pop_checkinterval">$pop_checkinterval</a>
-variable, which defaults to every 60 seconds.
-</p><a id="fetch-mail"></a><p>
-Another way to access your POP3 mail is the <code class="literal"><fetch-mail$</code> function
-(default: G). It allows to connect to <a class="link" href="reference.html#pop-host" title="3.220. pop_host">$pop_host</a>, fetch all your new mail and place it in the
-local <a class="link" href="reference.html#spoolfile" title="3.279. spoolfile">$spoolfile</a>. After this
-point, Mutt runs exactly as if the mail had always been local.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you only need to fetch all messages to a
-local mailbox you should consider using a specialized program, such as
-<code class="literal">fetchmail</code>, <code class="literal">getmail</code> or similar.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="imap"></a>4. IMAP Support</h2></div></div></div><p>
-If Mutt was compiled with IMAP support (by running the <span class="emphasis"><em>configure</em></span>
-script with the <span class="emphasis"><em>--enable-imap</em></span> flag), it has the ability to work
-with folders located on a remote IMAP server.
-</p><p>
-You can access the remote inbox by selecting the folder by its URL
-(see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details) using the
-<code class="literal">imap</code> or <code class="literal">imaps</code> protocol.
-Alternatively, a pine-compatible notation is also supported, ie
-<code class="literal">{[username@]imapserver[:port][/ssl]}path/to/folder</code>
-</p><p>
-Note that not all servers use “<span class="quote">/</span>” as the hierarchy separator. Mutt should
-correctly notice which separator is being used by the server and convert
-paths accordingly.
-</p><p>
-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
-<span class="emphasis"><em>toggle-subscribed</em></span> command. See also the
-<a class="link" href="reference.html#imap-list-subscribed" title="3.89. imap_list_subscribed">$imap_list_subscribed</a> variable.
-</p><p>
-Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
-want to carefully tune the
-<a class="link" href="reference.html#mail-check" title="3.105. mail_check">$mail_check</a>
-and
-<a class="link" href="reference.html#timeout" title="3.290. timeout">$timeout</a>
-variables. Personally I use
-</p><pre class="screen">
-set mail_check=90
-set timeout=15
-</pre><p>
-with relatively good results over my slow modem line.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that if you are using mbox as the mail store on UW servers prior to
-v12.250, the server has been reported to disconnect a client if another client
-selects the same folder.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-browser"></a>4.1. The Folder Browser</h3></div></div></div><p>
-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:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-In lieu 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.
-</p></li><li><p>
-For the case where an entry can contain both messages and
-subfolders, the selection key (bound to <code class="literal">enter</code> by default)
-will choose to descend into the subfolder view. If you wish to view
-the messages in that folder, you must use <code class="literal">view-file</code> instead
-(bound to <code class="literal">space</code> by default).
-</p></li><li><p>
-You can create, delete and rename mailboxes with the
-<code class="literal">create-mailbox</code>, <code class="literal">delete-mailbox</code>, and
-<code class="literal">rename-mailbox</code> commands (default bindings: <code class="literal">C</code>,
-<code class="literal">d</code> and <code class="literal">r</code>, respectively). You may also
-<code class="literal">subscribe</code> and <code class="literal">unsubscribe</code> to mailboxes (normally
-these are bound to <code class="literal">s</code> and <code class="literal">u</code>, respectively).
-</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authentication"></a>4.2. Authentication</h3></div></div></div><p>
-Mutt 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".
-</p><p>
-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 library
-installed on your system and compile mutt with the <span class="emphasis"><em>--with-sasl</em></span> flag.
-</p><p>
-Mutt will try whichever methods are compiled in and available on the server,
-in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-</p><p>
-There are a few variables which control authentication:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="link" href="reference.html#imap-user" title="3.96. imap_user">$imap_user</a> - 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 (ie by using a mailbox name of the form
-<code class="literal">{user@host}</code>).
-</p></li><li><p>
-<a class="link" href="reference.html#imap-pass" title="3.91. imap_pass">$imap_pass</a> - a
-password which you may preset, used by all authentication methods where
-a password is needed.
-</p></li><li><p>
-<a class="link" href="reference.html#imap-authenticators" title="3.83. imap_authenticators">$imap_authenticators</a> - 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).
-</p></li></ul></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="smtp"></a>5. SMTP Support</h2></div></div></div><p>
-Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
-was configured and built with <code class="literal">--enable-smtp</code>.
-</p><p>
-If the configuration variable
-<a class="link" href="reference.html#smtp-url" title="3.272. smtp_url">$smtp_url</a> is set, mutt
-will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a>.
-</p><p>
-For details on the URL syntax, please see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>.
-</p><p>
-The built-in SMTP support supports encryption (the <code class="literal">smtps</code> protocol
-using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
-for SASL are specified in <a class="link" href="reference.html#smtp-authenticators" title="3.270. smtp_authenticators">$smtp_authenticators</a>
-defaulting to an empty list which makes mutt try all available methods
-from most-secure to least-secure.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="account-hook"></a>6. Managing multiple accounts</h2></div></div></div><p>
-If you happen to have accounts on multiple IMAP, POP and/or SMTP 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 which includes (for example) polling for new mail, storing Fcc
-messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
-as passwords or tunnel commands but not settings such as sender
-address or name (because in general it should be considered unpredictable
-which account-hook was last used).
-</p><p>
-Some examples:
-</p><pre class="screen">
-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"'
-account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="caching"></a>7. Local caching</h2></div></div></div><p>
-Mutt contains two types of local caching: <span class="emphasis"><em>(1)</em></span>
-the so-called “<span class="quote">header caching</span>” and <span class="emphasis"><em>(2)</em></span> the
-so-called “<span class="quote">body caching</span>” which are both described in this section.
-</p><p>
-Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
-support as these use it (body caching requires no external library).
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-caching"></a>7.1. Header caching</h3></div></div></div><p>
-Mutt provides optional support for caching message headers for the
-following types of folders: IMAP, POP, Maildir and MH. Header caching
-greatly improves speed because for remote folders, headers
-usually only need to be downloaded once. For Maildir and MH, reading the
-headers from a single file is much faster than looking at possibly
-thousands of single files (since Maildir and MH use one file per message.)
-</p><p>
-Header caching can be enabled via the configure script and the
-<span class="emphasis"><em>--enable-hcache</em></span> option. It's not turned on
-by default because external database libraries are required: one
-of tokyocabinet, qdbm, gdbm or bdb must be present.
-</p><p>
-If enabled, <a class="link" href="reference.html#header-cache" title="3.109. header_cache">$header_cache</a> can be
-used to either point to a file or a directory. If set to point to
-a file, one database file for all folders will be used (which may
-result in lower performance), but one file per folder if it points
-to a directory.
-</p><p>
-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-</p><pre class="screen">
-$ printf '%s' '/path/to/folder' | md5sum
-</pre><p>
-The <code class="literal">md5sum</code> command may also be
-named <code class="literal">md5</code>, depending on your operating system.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="body-caching"></a>7.2. Body caching</h3></div></div></div><p>
-Both cache methods can be combined using the same directory for storage
-(and for IMAP/POP even provide meaningful file names) which simplifies
-manual maintenance tasks.
-</p><p>
-In addition to caching message headers only, mutt can also cache
-whole message bodies. This results in faster display of messages
-for POP and IMAP folders because messages usually have to be
-downloaded only once.
-</p><p>
-For configuration, the variable <a class="link" href="reference.html#message-cachedir" title="3.133. message_cachedir">$message_cachedir</a> must point to a
-directory. There, mutt will create a hierarchy of subdirectories
-named like: <code class="literal">proto:user@hostname</code> where
-<code class="literal">proto</code> is either “<span class="quote">pop</span>” or “<span class="quote">imap.</span>” Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-</p><p>
-All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maint-cache"></a>7.3. Maintenance</h3></div></div></div><p>
-Mutt does not (yet) support maintenance features for header cache
-database files so that files have to be removed in case they grow too
-big. It depends on the database library used for header caching whether
-disk space freed by removing messages is re-used.
-</p><p>
-For body caches, mutt can keep the local cache in sync with the
-remote mailbox if the
-<a class="link" href="reference.html#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a>
-variable is set. Cleaning means to remove messages from the cache which
-are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
-delete messages (Mutt itself removes deleted messages from the cache
-when syncing a mailbox). As cleaning can take a noticeable amount of time,
-it should not be set in general but only occasionally.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exact-address"></a>8. Exact address generation</h2></div></div></div><p>
-Mutt supports the “<span class="quote">Name <user@host></span>” address syntax for reading and
-writing messages, the older “<span class="quote">user@host (Name)</span>” syntax is only supported when
-reading messages. The <span class="emphasis"><em>--enable-exact-address</em></span>
-switch can be given to configure to build it with write-support
-for the latter syntax. <code class="literal">EXACT_ADDRESS</code> in the output of
-<code class="literal">mutt -v</code> indicates whether it's supported.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="mimesupport.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="tuning.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Mutt's MIME Support </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Performance tuning</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 8. Reference</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="tuning.html" title="Chapter 7. Performance tuning" /><link rel="next" href="miscellany.html" title="Chapter 9. Miscellany" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 8. Reference</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="tuning.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="miscellany.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="reference"></a>Chapter 8. Reference</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="reference.html#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="reference.html#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="reference.html#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="reference.html#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="reference.html#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="reference.html#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="reference.html#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="reference.html#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="reference.html#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="reference.html#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="reference.html#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="reference.html#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="reference.html#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="reference.html#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="reference.html#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="reference.html#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="reference.html#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="reference.html#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="reference.html#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="reference.html#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="reference.html#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="reference.html#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="reference.html#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="reference.html#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="reference.html#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="reference.html#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="reference.html#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="reference.html#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="reference.html#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="reference.html#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="reference.html#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="reference.html#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="reference.html#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="reference.html#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="reference.html#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="reference.html#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="reference.html#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="reference.html#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="reference.html#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="reference.html#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="reference.html#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="reference.html#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="reference.html#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="reference.html#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="reference.html#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="reference.html#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="reference.html#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="reference.html#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="reference.html#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="reference.html#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="reference.html#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="reference.html#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="reference.html#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="reference.html#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="reference.html#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="reference.html#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="reference.html#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="reference.html#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="reference.html#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="reference.html#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="reference.html#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="reference.html#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="reference.html#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="reference.html#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="reference.html#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="reference.html#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="reference.html#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="reference.html#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="reference.html#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="reference.html#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="reference.html#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="reference.html#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="reference.html#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="reference.html#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="reference.html#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="reference.html#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="reference.html#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="reference.html#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="reference.html#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="reference.html#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="reference.html#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="reference.html#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="reference.html#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="reference.html#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="reference.html#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="reference.html#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="reference.html#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="reference.html#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="reference.html#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="reference.html#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="reference.html#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="reference.html#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="reference.html#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="reference.html#sidebar-delim">3.150. sidebar_delim</a></span></dt><dt><span class="sect2"><a href="reference.html#sidebar-visible">3.151. sidebar_visible</a></span></dt><dt><span class="sect2"><a href="reference.html#sidebar-width">3.152. sidebar_width</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-use-gpg-agent">3.153. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-verify-sig">3.154. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-is-default">3.155. smime_is_default</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-ask-cert-label">3.156. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-decrypt-use-default-key">3.157. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-entry-format">3.158. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-good-sign">3.159. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-check-exit">3.160. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-long-ids">3.161. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-retainable-sigs">3.162. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-autoinline">3.163. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-replyinline">3.164. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-show-unusable">3.165. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sign-as">3.166. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-strict-enc">3.167. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-timeout">3.168. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sort-keys">3.169. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-auto">3.170. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-auto-decode">3.171. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-signature-filename">3.172. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-signature-description">3.173. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-decode-command">3.174. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-getkeys-command">3.175. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-verify-command">3.176. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-decrypt-command">3.177. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-clearsign-command">3.178. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sign-command">3.179. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-encrypt-sign-command">3.180. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-encrypt-only-command">3.181. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-import-command">3.182. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-export-command">3.183. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-verify-key-command">3.184. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-list-secring-command">3.185. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-list-pubring-command">3.186. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-decrypt">3.187. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-timeout">3.188. smime_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-encrypt-with">3.189. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-keys">3.190. smime_keys</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-ca-location">3.191. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-certificates">3.192. smime_certificates</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-decrypt-command">3.193. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-verify-command">3.194. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-verify-opaque-command">3.195. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-sign-command">3.196. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-sign-opaque-command">3.197. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-encrypt-command">3.198. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-pk7out-command">3.199. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-cert-command">3.200. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-signer-cert-command">3.201. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-import-cert-command">3.202. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-cert-email-command">3.203. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-default-key">3.204. smime_default_key</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-client-cert">3.205. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-force-tls">3.206. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-starttls">3.207. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="reference.html#certificate-file">3.208. certificate_file</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-use-sslv3">3.209. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-use-tlsv1">3.210. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-min-dh-prime-bits">3.211. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-ca-certificates-file">3.212. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-split">3.213. pipe_split</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-decode">3.214. pipe_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-sep">3.215. pipe_sep</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-authenticators">3.216. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-auth-try-all">3.217. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-checkinterval">3.218. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-delete">3.219. pop_delete</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-host">3.220. pop_host</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-last">3.221. pop_last</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-reconnect">3.222. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-user">3.223. pop_user</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-pass">3.224. pop_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#post-indent-string">3.225. post_indent_string</a></span></dt><dt><span class="sect2"><a href="reference.html#postpone">3.226. postpone</a></span></dt><dt><span class="sect2"><a href="reference.html#postponed">3.227. postponed</a></span></dt><dt><span class="sect2"><a href="reference.html#preconnect">3.228. preconnect</a></span></dt><dt><span class="sect2"><a href="reference.html#print">3.229. print</a></span></dt><dt><span class="sect2"><a href="reference.html#print-command">3.230. print_command</a></span></dt><dt><span class="sect2"><a href="reference.html#print-decode">3.231. print_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#print-split">3.232. print_split</a></span></dt><dt><span class="sect2"><a href="reference.html#prompt-after">3.233. prompt_after</a></span></dt><dt><span class="sect2"><a href="reference.html#query-command">3.234. query_command</a></span></dt><dt><span class="sect2"><a href="reference.html#query-format">3.235. query_format</a></span></dt><dt><span class="sect2"><a href="reference.html#quit">3.236. quit</a></span></dt><dt><span class="sect2"><a href="reference.html#quote-regexp">3.237. quote_regexp</a></span></dt><dt><span class="sect2"><a href="reference.html#read-inc">3.238. read_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#read-only">3.239. read_only</a></span></dt><dt><span class="sect2"><a href="reference.html#realname">3.240. realname</a></span></dt><dt><span class="sect2"><a href="reference.html#recall">3.241. recall</a></span></dt><dt><span class="sect2"><a href="reference.html#record">3.242. record</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-regexp">3.243. reply_regexp</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-self">3.244. reply_self</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-to">3.245. reply_to</a></span></dt><dt><span class="sect2"><a href="reference.html#resolve">3.246. resolve</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-alias">3.247. reverse_alias</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-name">3.248. reverse_name</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-realname">3.249. reverse_realname</a></span></dt><dt><span class="sect2"><a href="reference.html#rfc2047-parameters">3.250. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="reference.html#save-address">3.251. save_address</a></span></dt><dt><span class="sect2"><a href="reference.html#save-empty">3.252. save_empty</a></span></dt><dt><span class="sect2"><a href="reference.html#save-history">3.253. save_history</a></span></dt><dt><span class="sect2"><a href="reference.html#save-name">3.254. save_name</a></span></dt><dt><span class="sect2"><a href="reference.html#score">3.255. score</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-delete">3.256. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-flag">3.257. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-read">3.258. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="reference.html#send-charset">3.259. send_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#sendmail">3.260. sendmail</a></span></dt><dt><span class="sect2"><a href="reference.html#sendmail-wait">3.261. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="reference.html#shell">3.262. shell</a></span></dt><dt><span class="sect2"><a href="reference.html#sig-dashes">3.263. sig_dashes</a></span></dt><dt><span class="sect2"><a href="reference.html#sig-on-top">3.264. sig_on_top</a></span></dt><dt><span class="sect2"><a href="reference.html#signature">3.265. signature</a></span></dt><dt><span class="sect2"><a href="reference.html#simple-search">3.266. simple_search</a></span></dt><dt><span class="sect2"><a href="reference.html#smart-wrap">3.267. smart_wrap</a></span></dt><dt><span class="sect2"><a href="reference.html#smileys">3.268. smileys</a></span></dt><dt><span class="sect2"><a href="reference.html#sleep-time">3.269. sleep_time</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-authenticators">3.270. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-pass">3.271. smtp_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-url">3.272. smtp_url</a></span></dt><dt><span class="sect2"><a href="reference.html#sort">3.273. sort</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-alias">3.274. sort_alias</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-aux">3.275. sort_aux</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-browser">3.276. sort_browser</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-re">3.277. sort_re</a></span></dt><dt><span class="sect2"><a href="reference.html#spam-separator">3.278. spam_separator</a></span></dt><dt><span class="sect2"><a href="reference.html#spoolfile">3.279. spoolfile</a></span></dt><dt><span class="sect2"><a href="reference.html#status-chars">3.280. status_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#status-format">3.281. status_format</a></span></dt><dt><span class="sect2"><a href="reference.html#status-on-top">3.282. status_on_top</a></span></dt><dt><span class="sect2"><a href="reference.html#strict-threads">3.283. strict_threads</a></span></dt><dt><span class="sect2"><a href="reference.html#suspend">3.284. suspend</a></span></dt><dt><span class="sect2"><a href="reference.html#text-flowed">3.285. text_flowed</a></span></dt><dt><span class="sect2"><a href="reference.html#thread-received">3.286. thread_received</a></span></dt><dt><span class="sect2"><a href="reference.html#thorough-search">3.287. thorough_search</a></span></dt><dt><span class="sect2"><a href="reference.html#tilde">3.288. tilde</a></span></dt><dt><span class="sect2"><a href="reference.html#time-inc">3.289. time_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#timeout">3.290. timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#tmpdir">3.291. tmpdir</a></span></dt><dt><span class="sect2"><a href="reference.html#to-chars">3.292. to_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#trash">3.293. trash</a></span></dt><dt><span class="sect2"><a href="reference.html#tunnel">3.294. tunnel</a></span></dt><dt><span class="sect2"><a href="reference.html#use-8bitmime">3.295. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="reference.html#use-domain">3.296. use_domain</a></span></dt><dt><span class="sect2"><a href="reference.html#use-envelope-from">3.297. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="reference.html#use-from">3.298. use_from</a></span></dt><dt><span class="sect2"><a href="reference.html#use-idn">3.299. use_idn</a></span></dt><dt><span class="sect2"><a href="reference.html#use-ipv6">3.300. use_ipv6</a></span></dt><dt><span class="sect2"><a href="reference.html#user-agent">3.301. user_agent</a></span></dt><dt><span class="sect2"><a href="reference.html#visual">3.302. visual</a></span></dt><dt><span class="sect2"><a href="reference.html#wait-key">3.303. wait_key</a></span></dt><dt><span class="sect2"><a href="reference.html#weed">3.304. weed</a></span></dt><dt><span class="sect2"><a href="reference.html#wrap">3.305. wrap</a></span></dt><dt><span class="sect2"><a href="reference.html#wrap-search">3.306. wrap_search</a></span></dt><dt><span class="sect2"><a href="reference.html#wrapmargin">3.307. wrapmargin</a></span></dt><dt><span class="sect2"><a href="reference.html#write-inc">3.308. write_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#write-bcc">3.309. write_bcc</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-icon">3.310. xterm_icon</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-set-titles">3.311. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-title">3.312. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="reference.html#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="reference.html#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="reference.html#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="reference.html#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="reference.html#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="reference.html#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="reference.html#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="reference.html#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="reference.html#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="reference.html#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="reference.html#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="reference.html#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="reference.html#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commandline"></a>1. Command line options</h2></div></div></div><p>
-Running <code class="literal">mutt</code> with no arguments will make Mutt attempt to read your spool
-mailbox. However, it is possible to read other mailboxes and
-to send messages from the command line as well.
-</p><div class="table"><a id="tab-commandline-options"></a><p class="title"><b>Table 8.1. Command line options</b></p><div class="table-contents"><table summary="Command line options" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td>-A</td><td>expand an alias</td></tr><tr><td>-a</td><td>attach a file to a message</td></tr><tr><td>-b</td><td>specify a blind carbon-copy (BCC) address</td></tr><tr><td>-c</td><td>specify a carbon-copy (Cc) address</td></tr><tr><td>-D</td><td>print the value of all mutt variables to stdout</td></tr><tr><td>-e</td><td>specify a config command to be run after initialization files are read</td></tr><tr><td>-f</td><td>specify a mailbox to load</td></tr><tr><td>-F</td><td>specify an alternate file to read initialization commands</td></tr><tr><td>-h</td><td>print help on command line options</td></tr><tr><td>-H</td><td>specify a draft file from which to read a header and body</td></tr><tr><td>-i</td><td>specify a file to include in a message composition</td></tr><tr><td>-m</td><td>specify a default mailbox type</td></tr><tr><td>-n</td><td>do not read the system Muttrc</td></tr><tr><td>-p</td><td>recall a postponed message</td></tr><tr><td>-Q</td><td>query a configuration variable</td></tr><tr><td>-R</td><td>open mailbox in read-only mode</td></tr><tr><td>-s</td><td>specify a subject (enclose in quotes if it contains spaces)</td></tr><tr><td>-v</td><td>show version number and compile-time definitions</td></tr><tr><td>-x</td><td>simulate the mailx(1) compose mode</td></tr><tr><td>-y</td><td>show a menu containing the files specified by the mailboxes command</td></tr><tr><td>-z</td><td>exit immediately if there are no messages in the mailbox</td></tr><tr><td>-Z</td><td>open the first folder with new message,exit immediately if none</td></tr></tbody></table></div></div><br class="table-break" /><p>
-To read messages in a mailbox
-</p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-nz</code>] [<code class="option">-F</code>
-<em class="replaceable"><code>muttrc</code></em>
-] [<code class="option">-m</code>
-<em class="replaceable"><code>type</code></em>
-] [<code class="option">-f</code>
-<em class="replaceable"><code>mailbox</code></em>
-]</p></div><p>
-To compose a new message
-</p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-n</code>] [<code class="option">-F</code>
-<em class="replaceable"><code>muttrc</code></em>
-] [<code class="option">-c</code>
-<em class="replaceable"><code>address</code></em>
-] [<code class="option">-i</code>
-<em class="replaceable"><code>filename</code></em>
-] [<code class="option">-s</code>
-<em class="replaceable"><code>subject</code></em>
-] [
-<code class="option">-a</code>
-<em class="replaceable"><code>file</code></em>
- [...]
---
-]
-<em class="replaceable"><code>address</code></em>
-... </p></div><p>
-Mutt also supports a “<span class="quote">batch</span>” mode to send prepared messages. Simply redirect
-input from the file you wish to send. For example,
-</p><p>
-<code class="literal">mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat</code>
-</p><p>
-This command will send a message to “<span class="quote">professor@bigschool.edu</span>” with a subject
-of “<span class="quote">data set for run #2</span>”. In the body of the message will be the contents
-of the file “<span class="quote">˜/run2.dat</span>”.
-</p><p>
-All files passed with -a <span class="emphasis"><em>file</em></span> will be attached as a MIME
-part to the message. To attach several files, use “<span class="quote">--</span>” to separate files and
-recipient addresses: <code class="literal">mutt -a *.png -- some@one.org</code>
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commands"></a>2. Configuration Commands</h2></div></div></div><p>
-The following are the commands understood by mutt.
-</p><div class="itemizedlist"><ul type="disc"><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="optionalfeatures.html#account-hook" title="6. Managing multiple accounts">account-hook</a></code>
-<em class="replaceable"><code>pattern</code></em>
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">alias</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>address</code></em>
- [
-<em class="replaceable"><code>address</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">unalias</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>key</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">unalternates</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#alternative-order" title="5. MIME Multipart/Alternative">alternative-order</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#alternative-order" title="5. MIME Multipart/Alternative">unalternative-order</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto-view</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">unauto-view</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">bind</a></code>
-<em class="replaceable"><code>map</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>function</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#charset-hook" title="6. Defining aliases for character sets">charset-hook</a></code>
-<em class="replaceable"><code>alias</code></em>
-
-<em class="replaceable"><code>charset</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#charset-hook" title="6. Defining aliases for character sets">iconv-hook</a></code>
-<em class="replaceable"><code>charset</code></em>
-
-<em class="replaceable"><code>local-charset</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">color</a></code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">color</a></code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">color</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">uncolor</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>pattern</code></em>
-... </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#exec" title="23. Executing functions">exec</a></code>
-<em class="replaceable"><code>function</code></em>
- [
-<em class="replaceable"><code>function</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a></code>
-<em class="replaceable"><code>[!]regexp</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#addrgroup" title="3. Address groups">group</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#addrgroup" title="3. Address groups">ungroup</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#hdr-order">hdr_order</a></code>
-<em class="replaceable"><code>header</code></em>
- [
-<em class="replaceable"><code>header</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#hdr-order">unhdr_order</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>header</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#ignore" title="10. Message header display">ignore</a></code>
-<em class="replaceable"><code>pattern</code></em>
- [
-<em class="replaceable"><code>pattern</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#ignore" title="10. Message header display">unignore</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#lists" title="12. Mailing lists">lists</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#lists" title="12. Mailing lists">unlists</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#macro" title="8. Keyboard macros">macro</a></code>
-<em class="replaceable"><code>menu</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>sequence</code></em>
- [
-<em class="replaceable"><code>description</code></em>
-]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></code>
-<em class="replaceable"><code>mailbox</code></em>
- [
-<em class="replaceable"><code>mailbox</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">unmailboxes</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mailbox</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#message-hook" title="20. Change settings before formatting a message">message-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#mime-lookup" title="7. MIME Lookup">mime-lookup</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#mime-lookup" title="7. MIME Lookup">unmime-lookup</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mono">mono</a></code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>attribute</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mono">mono</a></code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mono">mono</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mono">unmono</a></code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></code>
-<em class="replaceable"><code>string</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">unmy_hdr</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>field</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#crypt-hook" title="21. Choosing the cryptographic key of the recipient">crypt-hook</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>keyid</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#push" title="22. Adding key sequences to the keyboard buffer">push</a></code>
-<em class="replaceable"><code>string</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#set" title="26. Setting and Querying Variables">reset</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="reference.html#score" title="3.255. score">score</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>value</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="reference.html#score" title="3.255. score">unscore</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#reply-hook">reply-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#send2-hook">send2-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#set" title="26. Setting and Querying Variables">set</a></code> {
-[ <code class="option">no</code> | <code class="option">inv</code> ]
-<em class="replaceable"><code>variable</code></em>
- |
-<em class="replaceable"><code>variable=value</code></em>
- } [...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#set" title="26. Setting and Querying Variables">unset</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a></code>
-<em class="replaceable"><code>filename</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#spam" title="25. Spam detection">spam</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>format</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#spam" title="25. Spam detection">nospam</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
- }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#subscribe">subscribe</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#subscribe">unsubscribe</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#set" title="26. Setting and Querying Variables">toggle</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#unhook" title="29. Removing hooks">unhook</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>hook-type</code></em>
- }</p></div></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="variables"></a>3. Configuration variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-nosubject"></a>3.1. abort_nosubject</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-If set to <span class="emphasis"><em>yes</em></span>, when composing messages and no subject is given
-at the subject prompt, composition will be aborted. If set to
-<span class="emphasis"><em>no</em></span>, composing messages with no subject given at the subject
-prompt will never be aborted.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-unmodified"></a>3.2. abort_unmodified</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If set to <span class="emphasis"><em>yes</em></span>, composition will automatically abort after
-editing the message body if no changes are made to the file (this
-check only happens after the <span class="emphasis"><em>first</em></span> edit of the file). When set
-to <span class="emphasis"><em>no</em></span>, composition will never be aborted.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-file"></a>3.3. alias_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.muttrc</code></span>”</p></div><p>
-The default file in which to save aliases created by the
-<code class="literal"><a class="link" href="gettingstarted.html#create-alias"><create-alias></a></code> function. Entries added to this file are
-encoded in the character set specified by <a class="link" href="reference.html#config-charset" title="3.30. config_charset">$config_charset</a> if it
-is <span class="emphasis"><em>set</em></span> or the current character set otherwise.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> Mutt will not automatically source this file; you must
-explicitly use the “<span class="quote"><a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a></span>” command for it to be executed in case
-this option points to a dedicated alias file.
-</p><p>
-The default for this option is the currently used muttrc file, or
-“<span class="quote">˜/.muttrc</span>” if no user muttrc was found.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-format"></a>3.4. alias_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %2f %t %-10a %r</code></span>”</p></div><p>
-Specifies the format of the data displayed for the “<span class="quote"><a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">alias</a></span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are available:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>alias name
-</p></dd><dt><span class="term">%f </span></dt><dd><p>flags - currently, a “<span class="quote">d</span>” for an alias marked for deletion
-</p></dd><dt><span class="term">%n </span></dt><dd><p>index number
-</p></dd><dt><span class="term">%r </span></dt><dd><p>address which alias expands to
-</p></dd><dt><span class="term">%t </span></dt><dd><p>character which indicates if the alias is tagged for inclusion
-</p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-8bit"></a>3.5. allow_8bit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether 8-bit data is converted to 7-bit using either Quoted-
-Printable or Base64 encoding when sending mail.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-ansi"></a>3.6. allow_ansi</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <span class="emphasis"><em>set</em></span>,
-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
-
-</p><pre class="screen">
-[-- PGP output follows ...
-
-</pre><p>
-and give it the same color as your attachment color (see also
-<a class="link" href="reference.html#crypt-timestamp" title="3.149. crypt_timestamp">$crypt_timestamp</a>).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="arrow-cursor"></a>3.7. arrow_cursor</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, an arrow (“<span class="quote">-></span>”) 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ascii-chars"></a>3.8. ascii_chars</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will use plain ASCII characters when displaying thread
-and attachment trees, instead of the default <span class="emphasis"><em>ACS</em></span> characters.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askbcc"></a>3.9. askbcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
-before editing an outgoing message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askcc"></a>3.10. askcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for carbon-copy (Cc) recipients before
-editing the body of an outgoing message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="assumed-charset"></a>3.11. assumed_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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 “<span class="quote">us-ascii</span>”.
-</p><p>
-For example, Japanese users might prefer this:
-
-</p><pre class="screen">
-set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</pre><p>
-However, only the first content is valid for the message body.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-charset"></a>3.12. attach_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable is a colon-separated list of character encoding
-schemes for text file attachments. Mutt uses this setting to guess
-which encoding files being attached are encoded in to convert them to
-a proper character set given in <a class="link" href="reference.html#send-charset" title="3.259. send_charset">$send_charset</a>.
-</p><p>
-If <span class="emphasis"><em>unset</em></span>, the value of <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> will be used instead.
-For example, the following configuration would work for Japanese
-text handling:
-
-</p><pre class="screen">
-set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</pre><p>
-Note: for Japanese users, “<span class="quote">iso-2022-*</span>” must be put at the head
-of the value as shown above if included.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-format"></a>3.13. attach_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] </code></span>”</p></div><p>
-This variable describes the format of the “<span class="quote">attachment</span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are understood:
-
-</p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>charset
-</p></dd><dt><span class="term">%c </span></dt><dd><p>requires charset conversion (“<span class="quote">n</span>” or “<span class="quote">c</span>”)
-</p></dd><dt><span class="term">%D </span></dt><dd><p>deleted flag
-</p></dd><dt><span class="term">%d </span></dt><dd><p>description
-</p></dd><dt><span class="term">%e </span></dt><dd><p>MIME content-transfer-encoding
-</p></dd><dt><span class="term">%f </span></dt><dd><p>filename
-</p></dd><dt><span class="term">%I </span></dt><dd><p>disposition (“<span class="quote">I</span>” for inline, “<span class="quote">A</span>” for attachment)
-</p></dd><dt><span class="term">%m </span></dt><dd><p>major MIME type
-</p></dd><dt><span class="term">%M </span></dt><dd><p>MIME subtype
-</p></dd><dt><span class="term">%n </span></dt><dd><p>attachment number
-</p></dd><dt><span class="term">%Q </span></dt><dd><p>“<span class="quote">Q</span>”, if MIME part qualifies for attachment counting
-</p></dd><dt><span class="term">%s </span></dt><dd><p>size
-</p></dd><dt><span class="term">%t </span></dt><dd><p>tagged flag
-</p></dd><dt><span class="term">%T </span></dt><dd><p>graphic tree characters
-</p></dd><dt><span class="term">%u </span></dt><dd><p>unlink (=to delete) flag
-</p></dd><dt><span class="term">%X </span></dt><dd><p>number of qualifying MIME parts in this part and its children
-(please see the “<span class="quote"><a class="link" href="mimesupport.html#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-sep"></a>3.14. attach_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
-The separator to add between attachments when operating (saving,
-printing, piping, etc) on a list of tagged attachments.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-split"></a>3.15. attach_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this variable is <span class="emphasis"><em>unset</em></span>, when operating (saving, printing, piping,
-etc) on a list of tagged attachments, Mutt will concatenate the
-attachments and will operate on them as a single attachment. The
-<a class="link" href="reference.html#attach-sep" title="3.14. attach_sep">$attach_sep</a> separator is added after each attachment. When <span class="emphasis"><em>set</em></span>,
-Mutt will operate on the attachments one by one.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attribution"></a>3.16. attribution</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">On %d, %n wrote:</code></span>”</p></div><p>
-This is the string that will precede a message which has been included
-in a reply. For a full listing of defined <code class="literal">printf(3)</code>-like sequences see
-the section on <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="autoedit"></a>3.17. autoedit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span> along with <a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a>, Mutt will skip the initial
-send-menu (prompting for subject and recipients) 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.
-</p><p>
-Also see <a class="link" href="reference.html#fast-reply" title="3.55. fast_reply">$fast_reply</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="auto-tag"></a>3.18. auto_tag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, functions in the <span class="emphasis"><em>index</em></span> menu which affect a message
-will be applied to all tagged messages (if there are any). When
-unset, you must first use the <code class="literal"><tag-prefix></code> function (bound to “<span class="quote">;</span>”
-by default) to make the next function apply to all tagged messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep"></a>3.19. beep</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep when an error occurs.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep-new"></a>3.20. beep_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep whenever it prints a message
-notifying you of new mail. This is independent of the setting of the
-<a class="link" href="reference.html#beep" title="3.19. beep">$beep</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce"></a>3.21. bounce</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether you will be asked to confirm bouncing messages.
-If set to <span class="emphasis"><em>yes</em></span> you don't get asked if you want to bounce a
-message. Setting this variable to <span class="emphasis"><em>no</em></span> is not generally useful,
-and thus not recommended, because you are unable to bounce messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce-delivered"></a>3.22. bounce_delivered</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will include Delivered-To headers when
-bouncing messages. Postfix users may wish to <span class="emphasis"><em>unset</em></span> this variable.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is unset by default in
-/etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="braille-friendly"></a>3.23. braille_friendly</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will place the cursor at the beginning
-of the current line in menus, even when the <a class="link" href="reference.html#arrow-cursor" title="3.7. arrow_cursor">$arrow_cursor</a> variable
-is <span class="emphasis"><em>unset</em></span>, making it easier for blind persons using Braille displays to
-follow these menus. The option is <span class="emphasis"><em>unset</em></span> by default because many
-visual terminals don't permit making the cursor invisible.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-mbox-size"></a>3.24. check_mbox_size</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
-</p><p>
-This variable is <span class="emphasis"><em>unset</em></span> by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
-</p><p>
-Note that enabling this variable should happen before any “<span class="quote"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="charset"></a>3.25. charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Character set your terminal uses to display and enter textual data.
-It is also the fallback for <a class="link" href="reference.html#send-charset" title="3.259. send_charset">$send_charset</a>.
-</p><p>
-Upon startup Mutt tries to derive this value from environment variables
-such as <code class="literal">$LC_CTYPE</code> or <code class="literal">$LANG</code>.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> It should only be set in case Mutt isn't abled to determine the
-character set used correctly.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-new"></a>3.26. check_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-<span class="bold"><strong>Note:</strong></span> this option only affects <span class="emphasis"><em>maildir</em></span> and <span class="emphasis"><em>MH</em></span> style
-mailboxes.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt 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
-this variable is <span class="emphasis"><em>unset</em></span>, no check for new mail is performed
-while the mailbox is open.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="collapse-unread"></a>3.27. collapse_unread</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, Mutt will not collapse a thread if it contains any
-unread messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="uncollapse-jump"></a>3.28. uncollapse_jump</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will jump to the next unread message, if any,
-when the current thread is <span class="emphasis"><em>un</em></span>collapsed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-format"></a>3.29. compose_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-</code></span>”</p></div><p>
-Controls the format of the status line displayed in the “<span class="quote">compose</span>”
-menu. This string is similar to <a class="link" href="reference.html#status-format" title="3.281. status_format">$status_format</a>, but has its own
-set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>total number of attachments
-</p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
-</p></dd><dt><span class="term">%l </span></dt><dd><p>approximate size (in bytes) of the current message
-</p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
-</p></dd></dl></div><p>
-See the text describing the <a class="link" href="reference.html#status-format" title="3.281. status_format">$status_format</a> option for more
-information on how to set <a class="link" href="reference.html#compose-format" title="3.29. compose_format">$compose_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="config-charset"></a>3.30. config_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-When defined, Mutt will recode commands in rc files from this
-encoding to the current character set as specified by <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a>
-and aliases written to <a class="link" href="reference.html#alias-file" title="3.3. alias_file">$alias_file</a> from the current character set.
-</p><p>
-Please note that if setting <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> it must be done before
-setting <a class="link" href="reference.html#config-charset" title="3.30. config_charset">$config_charset</a>.
-</p><p>
-Recoding should be avoided as it may render unconvertable
-characters as question marks which can lead to undesired
-side effects (for example in regular expressions).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmappend"></a>3.31. confirmappend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when appending messages to
-an existing mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmcreate"></a>3.32. confirmcreate</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when saving messages to a
-mailbox which does not yet exist before creating it.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="connect-timeout"></a>3.33. connect_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 30</p></div><p>
-Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-many seconds if the connection is not able to be established. A negative
-value causes Mutt to wait indefinitely for the connection attempt to succeed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="content-type"></a>3.34. content_type</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">text/plain</code></span>”</p></div><p>
-Sets the default Content-Type for the body of newly composed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="copy"></a>3.35. copy</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether or not copies of your outgoing messages
-will be saved for later references. Also see <a class="link" href="reference.html#record" title="3.242. record">$record</a>,
-<a class="link" href="reference.html#save-name" title="3.254. save_name">$save_name</a>, <a class="link" href="reference.html#force-name" title="3.61. force_name">$force_name</a> and “<span class="quote"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-gpgme"></a>3.36. crypt_use_gpgme</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls the use of the GPGME-enabled crypto backends.
-If it is <span class="emphasis"><em>set</em></span> and Mutt was built with gpgme support, the gpgme code for
-S/MIME and PGP will be used instead of the classic code. Note that
-you need to set this option in .muttrc; it won't have any effect when
-used interactively.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-pka"></a>3.37. crypt_use_pka</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether mutt uses PKA
-(see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
-verification (only supported by the GPGME backend).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autopgp"></a>3.38. crypt_autopgp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages. See also <a class="link" href="reference.html#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
-<a class="link" href="reference.html#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
-<a class="link" href="reference.html#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="reference.html#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="reference.html#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosmime"></a>3.39. crypt_autosmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also <a class="link" href="reference.html#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
-<a class="link" href="reference.html#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
-<a class="link" href="reference.html#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="reference.html#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="reference.html#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-format"></a>3.40. date_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">!%a, %b %d, %Y at %I:%M:%S%p %Z</code></span>”</p></div><p>
-This variable controls the format of the date printed by the “<span class="quote">%d</span>”
-sequence in <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>. This is passed to the <code class="literal">strftime(3)</code>
-function to process the date, see the man page for the proper syntax.
-</p><p>
-Unless the first character in the string is a bang (“<span class="quote">!</span>”), the month
-and week day names are expanded according to the locale specified in
-the variable <a class="link" href="reference.html#locale" title="3.104. locale">$locale</a>. 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 <span class="emphasis"><em>C</em></span> locale (that is in US
-English).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="default-hook"></a>3.41. default_hook</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜f %s !˜P | (˜P ˜C %s)</code></span>”</p></div><p>
-This variable controls how “<span class="quote"><a class="link" href="configuration.html#message-hook" title="20. Change settings before formatting a message">message-hook</a></span>”, “<span class="quote"><a class="link" href="configuration.html#reply-hook">reply-hook</a></span>”, “<span class="quote"><a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”,
-“<span class="quote"><a class="link" href="configuration.html#send2-hook">send2-hook</a></span>”, “<span class="quote"><a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, and “<span class="quote"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” 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.
-</p><p>
-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
-“<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>”) and is to or cc'ed to a user matching the given
-regular expression.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete"></a>3.42. delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not messages are really deleted when closing or
-synchronizing a mailbox. If set to <span class="emphasis"><em>yes</em></span>, messages marked for
-deleting will automatically be purged without prompting. If set to
-<span class="emphasis"><em>no</em></span>, messages marked for deletion will be kept in the mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete-untag"></a>3.43. delete_untag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this option is <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="digest-collapse"></a>3.44. digest_collapse</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this option is <span class="emphasis"><em>set</em></span>, mutt's received-attachments menu will not show the subparts of
-individual messages in a multipart/digest. To see these subparts, press “<span class="quote">v</span>” on that menu.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="display-filter"></a>3.45. display_filter</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-When set, specifies a command used to filter messages. When a message
-is viewed it is passed as standard input to <a class="link" href="reference.html#display-filter" title="3.45. display_filter">$display_filter</a>, and the
-filtered message is read from the standard output.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dotlock-program"></a>3.46. dotlock_program</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">/usr/bin/mutt_dotlock</code></span>”</p></div><p>
-Contains the path of the <code class="literal">mutt_dotlock(8)</code> binary to be used by
-mutt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-notify"></a>3.47. dsn_notify</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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: <span class="emphasis"><em>never</em></span>, to never request notification,
-<span class="emphasis"><em>failure</em></span>, to request notification on transmission failure,
-<span class="emphasis"><em>delay</em></span>, to be notified of message delays, <span class="emphasis"><em>success</em></span>, to be
-notified of successful transmission.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set dsn_notify="failure,delay"
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> when using <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-N</code> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-return"></a>3.48. dsn_return</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable controls how much of your message is returned in DSN
-messages. It may be set to either <span class="emphasis"><em>hdrs</em></span> to return just the
-message header, or <span class="emphasis"><em>full</em></span> to return the full message.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set dsn_return=hdrs
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> when using <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-R</code> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="duplicate-threads"></a>3.49. duplicate_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether mutt, when <a class="link" href="reference.html#sort" title="3.273. sort">$sort</a> is set to <span class="emphasis"><em>threads</em></span>, threads
-messages with the same Message-Id together. If it is <span class="emphasis"><em>set</em></span>, it will indicate
-that it thinks they are duplicates of each other with an equals sign
-in the thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-headers"></a>3.50. edit_headers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option allows you to edit the header of your outgoing messages
-along with the body of your message.
-</p><p>
-<span class="bold"><strong>Note</strong></span> that changes made to the References: and Date: headers are
-ignored for interoperability reasons.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor"></a>3.51. editor</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable specifies which editor is used by mutt.
-It defaults to the value of the <code class="literal">$VISUAL</code>, or <code class="literal">$EDITOR</code>, environment
-variable, or to the string “<span class="quote">/usr/bin/editor</span>” if neither of those are set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="encode-from"></a>3.52. encode_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will quoted-printable encode messages when
-they contain the string “<span class="quote">From </span>” (note the trailing space) in the beginning of a line.
-This is useful to avoid the tampering certain mail delivery and transport
-agents tend to do with messages (in order to prevent tools from
-misinterpreting the line as a mbox message separator).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="envelope-from-address"></a>3.53. envelope_from_address</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
-Default: (empty)</p></div><p>
-Manually sets the <span class="emphasis"><em>envelope</em></span> sender for outgoing messages.
-This value is ignored if <a class="link" href="reference.html#use-envelope-from" title="3.297. use_envelope_from">$use_envelope_from</a> is <span class="emphasis"><em>unset</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="escape"></a>3.54. escape</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜</code></span>”</p></div><p>
-Escape character to use for functions in the builtin editor.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fast-reply"></a>3.55. fast_reply</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, 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><p>
-<span class="bold"><strong>Note:</strong></span> this variable has no effect when the <a class="link" href="reference.html#autoedit" title="3.17. autoedit">$autoedit</a>
-variable is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-attach"></a>3.56. fcc_attach</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not attachments on outgoing messages
-are saved along with the main body of your message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-clear"></a>3.57. fcc_clear</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, FCCs will be stored unencrypted and
-unsigned, even when the actual message is encrypted and/or
-signed.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder"></a>3.58. folder</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/Mail</code></span>”</p></div><p>
-Specifies the default location of your mailboxes. A “<span class="quote">+</span>” or “<span class="quote">=</span>” 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 <span class="emphasis"><em>before</em></span>
-you use “<span class="quote">+</span>” or “<span class="quote">=</span>” for any other variables since expansion takes place
-when handling the “<span class="quote"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder-format"></a>3.59. folder_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f</code></span>”</p></div><p>
-This variable allows you to customize the file browser display to your
-personal taste. This string is similar to <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>, but has
-its own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>current file number
-</p></dd><dt><span class="term">%d </span></dt><dd><p>date/time folder was last modified
-</p></dd><dt><span class="term">%f </span></dt><dd><p>filename
-</p></dd><dt><span class="term">%F </span></dt><dd><p>file permissions
-</p></dd><dt><span class="term">%g </span></dt><dd><p>group name (or numeric gid, if missing)
-</p></dd><dt><span class="term">%l </span></dt><dd><p>number of hard links
-</p></dd><dt><span class="term">%N </span></dt><dd><p>N if folder has new mail, blank otherwise
-</p></dd><dt><span class="term">%s </span></dt><dd><p>size in bytes
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if the file is tagged, blank otherwise
-</p></dd><dt><span class="term">%u </span></dt><dd><p>owner name (or numeric uid, if missing)
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="followup-to"></a>3.60. followup_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether or not the “<span class="quote">Mail-Followup-To:</span>” header field is
-generated when sending mail. When <span class="emphasis"><em>set</em></span>, Mutt will generate this
-field when you are replying to a known mailing list, specified with
-the “<span class="quote"><a class="link" href="configuration.html#subscribe">subscribe</a></span>” or “<span class="quote"><a class="link" href="configuration.html#lists" title="12. Mailing lists">lists</a></span>” commands.
-</p><p>
-This field has two purposes. First, preventing you from
-receiving duplicate copies of replies to messages which you send
-to mailing lists, and second, ensuring that you do get a reply
-separately for any messages sent to known lists to which you are
-not subscribed.
-</p><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="force-name"></a>3.61. force_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable is similar to <a class="link" href="reference.html#save-name" title="3.254. save_name">$save_name</a>, except that Mutt 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.
-</p><p>
-Also see the <a class="link" href="reference.html#record" title="3.242. record">$record</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decode"></a>3.62. forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
-forwarding a message. The message header is also RFC2047 decoded.
-This variable is only used, if <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>,
-otherwise <a class="link" href="reference.html#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is used instead.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-edit"></a>3.63. forward_edit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-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 “<span class="quote">no</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-format"></a>3.64. forward_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">[%a: %s]</code></span>”</p></div><p>
-This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-quote"></a>3.65. forward_quote</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, forwarded messages included in the main body of the
-message (when <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>) will be quoted using
-<a class="link" href="reference.html#indent-string" title="3.100. indent_string">$indent_string</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="from"></a>3.66. from</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
-Default: (empty)</p></div><p>
-When <span class="emphasis"><em>set</em></span>, this variable contains a default from address. It
-can be overridden using “<span class="quote"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></span>” (including from a “<span class="quote"><a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”) and
-<a class="link" href="reference.html#reverse-name" title="3.248. reverse_name">$reverse_name</a>. This variable is ignored if <a class="link" href="reference.html#use-from" title="3.298. use_from">$use_from</a> is <span class="emphasis"><em>unset</em></span>.
-</p><p>
-This setting defaults to the contents of the environment variable <code class="literal">$EMAIL</code>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="gecos-mask"></a>3.67. gecos_mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^[^,]*</code></span>”</p></div><p>
-A regular expression used by mutt to parse the GECOS field of a password
-entry when expanding the alias. The default value
-will return the string up to the first “<span class="quote">,</span>” encountered.
-If the GECOS field contains a string like “<span class="quote">lastname, firstname</span>” then you
-should set it to “<span class="quote"><code class="literal">.*</code></span>”.
-</p><p>
-This can be useful if you see the following behavior: you address an e-mail
-to user ID “<span class="quote">stevef</span>” whose full name is “<span class="quote">Steve Franklin</span>”. If mutt expands
-“<span class="quote">stevef</span>” to “<span class="quote">"Franklin" stevef@foo.bar</span>” then you should set the <a class="link" href="reference.html#gecos-mask" title="3.67. gecos_mask">$gecos_mask</a> to
-a regular expression that will match the whole name so mutt will expand
-“<span class="quote">Franklin</span>” to “<span class="quote">Franklin, Steve</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hdrs"></a>3.68. hdrs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, the header fields normally added by the “<span class="quote"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command are not created. This variable <span class="emphasis"><em>must</em></span> be unset before
-composing a new message or replying in order to take effect. If <span class="emphasis"><em>set</em></span>,
-the user defined header fields are added to every new message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header"></a>3.69. header</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, this variable causes Mutt to include the header
-of the message you are replying to into the edit buffer.
-The <a class="link" href="reference.html#weed" title="3.304. weed">$weed</a> setting applies.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="help"></a>3.70. help</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, help lines describing the bindings for the major functions
-provided by each menu are displayed on the first line of the screen.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> 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 is
-running. Since this variable is primarily aimed at new users, neither
-of these should present a major problem.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hidden-host"></a>3.71. hidden_host</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will skip the host name part of <a class="link" href="reference.html#hostname" title="3.80. hostname">$hostname</a> variable
-when adding the domain part to addresses. This variable does not
-affect the generation of Message-IDs, and it will not lead to the
-cut-off of first-level domains.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-limited"></a>3.72. hide_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
-by limiting, in the thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-missing"></a>3.73. hide_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages in the
-thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-thread-subject"></a>3.74. hide_thread_subject</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the subject of messages in the thread
-tree that have the same subject as their parent or closest previously
-displayed sibling.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-limited"></a>3.75. hide_top_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
-by limiting, at the top of threads in the thread tree. Note that when
-<a class="link" href="reference.html#hide-limited" title="3.72. hide_limited">$hide_limited</a> is <span class="emphasis"><em>set</em></span>, this option will have no effect.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-missing"></a>3.76. hide_top_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages at the
-top of threads in the thread tree. Note that when <a class="link" href="reference.html#hide-missing" title="3.73. hide_missing">$hide_missing</a> is
-<span class="emphasis"><em>set</em></span>, this option will have no effect.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history"></a>3.77. history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-This variable controls the size (in number of strings remembered) of
-the string history buffer per category. The buffer is cleared each time the
-variable is set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history-file"></a>3.78. history_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.mutthistory</code></span>”</p></div><p>
-The file in which Mutt will save its history.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="honor-followup-to"></a>3.79. honor_followup_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether or not a Mail-Followup-To header is
-honored when group-replying to a message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hostname"></a>3.80. hostname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the fully-qualified hostname of the system mutt is running on
-containing the host's name and the DNS domain it belongs to. It is used
-as the domain part (after “<span class="quote">@</span>”) for local email addresses as well as
-Message-Id headers.
-</p><p>
-Its value is determined at startup as follows: If the node's name
-as returned by the <code class="literal">uname(3)</code> function contains the hostname and the
-domain, these are used to construct <a class="link" href="reference.html#hostname" title="3.80. hostname">$hostname</a>. If there is no
-domain part returned, Mutt will look for a “<span class="quote">domain</span>” or “<span class="quote">search</span>”
-line in <code class="literal">/etc/resolv.conf</code> to determine the domain. Optionally, Mutt
-can be compiled with a fixed domain name in which case a detected
-one is not used.
-</p><p>
-Also see <a class="link" href="reference.html#use-domain" title="3.296. use_domain">$use_domain</a> and <a class="link" href="reference.html#hidden-host" title="3.71. hidden_host">$hidden_host</a>.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, the default for this variable is obtained
-from /etc/mailname when Mutt starts.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-linear-white-space"></a>3.81. ignore_linear_white_space</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option replaces linear-white-space between encoded-word
-and text to a single space to prevent the display of MIME-encoded
-“<span class="quote">Subject:</span>” field from being divided into multiple lines.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-list-reply-to"></a>3.82. ignore_list_reply_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Affects the behaviour of the <code class="literal"><reply></code> function when replying to
-messages from mailing lists (as defined by the “<span class="quote"><a class="link" href="configuration.html#subscribe">subscribe</a></span>” or
-“<span class="quote"><a class="link" href="configuration.html#lists" title="12. Mailing lists">lists</a></span>” commands). When <span class="emphasis"><em>set</em></span>, if the “<span class="quote">Reply-To:</span>” field is
-set to the same value as the “<span class="quote">To:</span>” field, Mutt assumes that the
-“<span class="quote">Reply-To:</span>” 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 <span class="emphasis"><em>set</em></span>, use the <code class="literal"><a class="link" href="gettingstarted.html#list-reply"><list-reply></a></code>
-function; <code class="literal"><group-reply></code> will reply to both the sender and the
-list.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authenticators"></a>3.83. imap_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an IMAP server, in the order mutt should
-try them. Authentication methods are either “<span class="quote">login</span>” or the right
-side of an IMAP “<span class="quote">AUTH=xxx</span>” capability string, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>”
-or “<span class="quote">cram-md5</span>”. This option is case-insensitive. If it's
-<span class="emphasis"><em>unset</em></span> (the default) mutt will try all available methods,
-in order from most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set imap_authenticators="gssapi:cram-md5:login"
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> Mutt will only fall back to other authentication methods if
-the previous methods are unavailable. If a method is available but
-authentication fails, mutt will not connect to the IMAP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-check-subscribed"></a>3.84. imap_check_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, 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 just as if you had issued individual “<span class="quote"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
-commands.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-delim-chars"></a>3.85. imap_delim_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">/.</code></span>”</p></div><p>
-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 “<span class="quote">=</span>” shortcut for your <span class="emphasis"><em>folder</em></span> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-headers"></a>3.86. imap_headers</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Mutt requests these header fields in addition to the default headers
-(“<span class="quote">Date:</span>”, “<span class="quote">From:</span>”, “<span class="quote">Subject:</span>”, “<span class="quote">To:</span>”, “<span class="quote">Cc:</span>”, “<span class="quote">Message-Id:</span>”,
-“<span class="quote">References:</span>”, “<span class="quote">Content-Type:</span>”, “<span class="quote">Content-Description:</span>”, “<span class="quote">In-Reply-To:</span>”,
-“<span class="quote">Reply-To:</span>”, “<span class="quote">Lines:</span>”, “<span class="quote">List-Post:</span>”, “<span class="quote">X-Label:</span>”) from IMAP
-servers before displaying the index menu. You may want to add more
-headers for spam detection.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> This is a space separated list, items should be uppercase
-and not contain the colon, e.g. “<span class="quote">X-BOGOSITY X-SPAM-STATUS</span>” for the
-“<span class="quote">X-Bogosity:</span>” and “<span class="quote">X-Spam-Status:</span>” header fields.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-idle"></a>3.87. imap_idle</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will attempt to use the IMAP IDLE extension
-to check for new mail in the current mailbox. Some servers
-(dovecot was the inspiration for this option) react badly
-to mutt's implementation. If your connection seems to freeze
-up periodically, try unsetting this.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-keepalive"></a>3.88. imap_keepalive</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 900</p></div><p>
-This variable specifies the maximum amount of time in seconds that mutt
-will wait before polling open IMAP connections, to prevent the server
-from closing them before mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-list-subscribed"></a>3.89. imap_list_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <code class="literal"><toggle-subscribed></code> function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-login"></a>3.90. imap_login</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Your login name on the IMAP server.
-</p><p>
-This variable defaults to the value of <a class="link" href="reference.html#imap-user" title="3.96. imap_user">$imap_user</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pass"></a>3.91. imap_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your IMAP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you invoke the <code class="literal"><a class="link" href="optionalfeatures.html#fetch-mail"><fetch-mail></a></code> function
-or try to open an IMAP folder.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-passive"></a>3.92. imap_passive</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not open new IMAP connections to check for new
-mail. Mutt 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 invocation, or if opening the connection
-is slow.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-peek"></a>3.93. imap_peek</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pipeline-depth"></a>3.94. imap_pipeline_depth</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 15</p></div><p>
-Controls the number of IMAP commands that may be queued up before they
-are sent to the server. A deeper pipeline reduces the amount of time
-mutt must wait for the server, and can make IMAP servers feel much
-more responsive. But not all servers correctly handle pipelined commands,
-so if you have problems you might want to try setting this variable to 0.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> Changes to this variable have no effect on open connections.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-servernoise"></a>3.95. imap_servernoise</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-user"></a>3.96. imap_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-The name of the user whose mail you intend to access on the IMAP
-server.
-</p><p>
-This variable defaults to your user name on the local machine.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="implicit-autoview"></a>3.97. implicit_autoview</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If set to “<span class="quote">yes</span>”, mutt will look for a mailcap entry with the
-“<span class="quote"><code class="literal">copiousoutput</code></span>” flag set for <span class="emphasis"><em>every</em></span> MIME attachment it doesn't have
-an internal viewer defined for. If such an entry is found, mutt will
-use the viewer defined in that entry to convert the body part to text
-form.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include"></a>3.98. include</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not a copy of the message(s) you are replying to
-is included in your reply.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include-onlyfirst"></a>3.99. include_onlyfirst</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether or not Mutt includes only the first attachment
-of the message you are replying.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="indent-string"></a>3.100. indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">> </code></span>”</p></div><p>
-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.
-</p><p>
-This option is a format string, please see the description of
-<a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> for supported <code class="literal">printf(3)</code>-style sequences.
-</p><p>
-Because for <code class="literal">format=lowed</code> style messages the quoting mechanism
-is strictly defined, this setting is ignored if <a class="link" href="reference.html#text-flowed" title="3.285. text_flowed">$text_flowed</a> is
-<span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-format"></a>3.101. index_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s</code></span>”</p></div><p>
-This variable allows you to customize the message index display to
-your personal taste.
-</p><p>
-“<span class="quote">Format strings</span>” are similar to the strings used in the C
-function <code class="literal">printf(3)</code> to format output (see the man page for more details).
-The following sequences are defined in Mutt:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>address of the author
-</p></dd><dt><span class="term">%A </span></dt><dd><p>reply-to address (if present; otherwise: address of author)
-</p></dd><dt><span class="term">%b </span></dt><dd><p>filename of the original message folder (think mailbox)
-</p></dd><dt><span class="term">%B </span></dt><dd><p>the list to which the letter was sent, or else the folder name (%b).
-</p></dd><dt><span class="term">%c </span></dt><dd><p>number of characters (bytes) in the message
-</p></dd><dt><span class="term">%C </span></dt><dd><p>current message number
-</p></dd><dt><span class="term">%d </span></dt><dd><p>date and time of the message in the format specified by
-<a class="link" href="reference.html#date-format" title="3.40. date_format">$date_format</a> converted to sender's time zone
-</p></dd><dt><span class="term">%D </span></dt><dd><p>date and time of the message in the format specified by
-<a class="link" href="reference.html#date-format" title="3.40. date_format">$date_format</a> converted to the local time zone
-</p></dd><dt><span class="term">%e </span></dt><dd><p>current message number in thread
-</p></dd><dt><span class="term">%E </span></dt><dd><p>number of messages in current thread
-</p></dd><dt><span class="term">%f </span></dt><dd><p>sender (address + real name), either From: or Return-Path:
-</p></dd><dt><span class="term">%F </span></dt><dd><p>author name, or recipient name if the message is from you
-</p></dd><dt><span class="term">%H </span></dt><dd><p>spam attribute(s) of this message
-</p></dd><dt><span class="term">%i </span></dt><dd><p>message-id of the current message
-</p></dd><dt><span class="term">%l </span></dt><dd><p>number of lines in the message (does not work with maildir,
-mh, and possibly IMAP folders)
-</p></dd><dt><span class="term">%L </span></dt><dd><p>If an address in the “<span class="quote">To:</span>” or “<span class="quote">Cc:</span>” header field matches an address
-defined by the users “<span class="quote"><a class="link" href="configuration.html#subscribe">subscribe</a></span>” command, this displays
-"To <list-name>", otherwise the same as %F.
-</p></dd><dt><span class="term">%m </span></dt><dd><p>total number of message in the mailbox
-</p></dd><dt><span class="term">%M </span></dt><dd><p>number of hidden messages if the thread is collapsed.
-</p></dd><dt><span class="term">%N </span></dt><dd><p>message score
-</p></dd><dt><span class="term">%n </span></dt><dd><p>author's real name (or address if missing)
-</p></dd><dt><span class="term">%O </span></dt><dd><p>original save folder where mutt would formerly have
-stashed the message: list name or recipient name
-if not sent to a list
-</p></dd><dt><span class="term">%P </span></dt><dd><p>progress indicator for the builtin pager (how much of the file has been displayed)
-</p></dd><dt><span class="term">%s </span></dt><dd><p>subject of the message
-</p></dd><dt><span class="term">%S </span></dt><dd><p>status of the message (“<span class="quote">N</span>”/“<span class="quote">D</span>”/“<span class="quote">d</span>”/“<span class="quote">!</span>”/“<span class="quote">r</span>”/*)
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">To:</span>” field (recipients)
-</p></dd><dt><span class="term">%T </span></dt><dd><p>the appropriate character from the <a class="link" href="reference.html#to-chars" title="3.292. to_chars">$to_chars</a> string
-</p></dd><dt><span class="term">%u </span></dt><dd><p>user (login) name of the author
-</p></dd><dt><span class="term">%v </span></dt><dd><p>first name of the author, or the recipient if the message is from you
-</p></dd><dt><span class="term">%X </span></dt><dd><p>number of attachments
-(please see the “<span class="quote"><a class="link" href="mimesupport.html#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
-</p></dd><dt><span class="term">%y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present
-</p></dd><dt><span class="term">%Y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present, and <span class="emphasis"><em>(1)</em></span> not at part of a thread tree,
-<span class="emphasis"><em>(2)</em></span> at the top of a thread, or <span class="emphasis"><em>(3)</em></span> “<span class="quote">X-Label:</span>” is different from
-preceding message's “<span class="quote">X-Label:</span>”.
-</p></dd><dt><span class="term">%Z </span></dt><dd><p>message status flags
-</p></dd><dt><span class="term">%{fmt} </span></dt><dd><p>the date and time of the message is converted to sender's
-time zone, and “<span class="quote">fmt</span>” is expanded by the library function
-<code class="literal">strftime(3)</code>; a leading bang disables locales
-</p></dd><dt><span class="term">%[fmt] </span></dt><dd><p>the date and time of the message is converted to the local
-time zone, and “<span class="quote">fmt</span>” is expanded by the library function
-<code class="literal">strftime(3)</code>; a leading bang disables locales
-</p></dd><dt><span class="term">%(fmt) </span></dt><dd><p>the local date and time when the message was received.
-“<span class="quote">fmt</span>” is expanded by the library function <code class="literal">strftime(3)</code>;
-a leading bang disables locales
-</p></dd><dt><span class="term">%<fmt> </span></dt><dd><p>the current local time. “<span class="quote">fmt</span>” is expanded by the library
-function <code class="literal">strftime(3)</code>; a leading bang disables locales.
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-“<span class="quote">Soft-fill</span>” deserves some explanation: Normal right-justification
-will print everything to the left of the “<span class="quote">%></span>”, displaying padding and
-whatever lies to the right only if there's room. By contrast,
-soft-fill gives priority to the right-hand side, guaranteeing space
-to display it and showing padding only if there's still room. If
-necessary, soft-fill will eat text leftwards to make room for
-rightward text.
-</p><p>
-Note that these expandos are supported in
-“<span class="quote"><a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, “<span class="quote"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” and “<span class="quote"><a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></span>”, too.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ispell"></a>3.102. ispell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">ispell</code></span>”</p></div><p>
-How to invoke ispell (GNU's spell-checking software).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="keep-flagged"></a>3.103. keep_flagged</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, read messages marked as flagged will not be moved
-from your spool mailbox to your <a class="link" href="reference.html#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
-a “<span class="quote"><a class="link" href="configuration.html#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="locale"></a>3.104. locale</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">C</code></span>”</p></div><p>
-The locale used by <code class="literal">strftime(3)</code> to format dates. Legal values are
-the strings your system accepts for the locale environment variable <code class="literal">$LC_TIME</code>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mail-check"></a>3.105. mail_check</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 5</p></div><p>
-This variable configures how often (in seconds) mutt should look for
-new mail. Also see the <a class="link" href="reference.html#timeout" title="3.290. timeout">$timeout</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-path"></a>3.106. mailcap_path</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable specifies which files to consult when attempting to
-display MIME bodies not directly supported by Mutt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-sanitize"></a>3.107. mailcap_sanitize</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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.
-</p><p>
-<span class="bold"><strong>DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
-DOING!</strong></span>
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-mtime"></a>3.108. maildir_mtime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If set, the sort-by-date option in the browser will sort maildirs
-smartly, not using the mtime of the maildir itself but that of the
-newest message in the new subdirectory, making the sorting by
-reverse date much more useful. People with maildirs over NFS may
-wish to leave this option unset.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache"></a>3.109. header_cache</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is <span class="emphasis"><em>unset</em></span> so no header
-caching will be used.
-</p><p>
-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see “<span class="quote"><a class="link" href="optionalfeatures.html#caching" title="7. Local caching">caching</a></span>” for details.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-header-cache-verify"></a>3.110. maildir_header_cache_verify</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Check for Maildir unaware programs other than mutt having modified maildir
-files when the header cache is in use. This incurs one <code class="literal">stat(2)</code> per
-message every time the folder is opened (which can be very slow for NFS
-folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache-pagesize"></a>3.111. header_cache_pagesize</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">16384</code></span>”</p></div><p>
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-trash"></a>3.112. maildir_trash</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, messages marked as deleted will be saved with the maildir
-trashed flag instead of unlinked. <span class="bold"><strong>Note:</strong></span> this only applies
-to maildir-style mailboxes. Setting it will have no effect on other
-mailbox types.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mark-old"></a>3.113. mark_old</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether or not mutt marks <span class="emphasis"><em>new</em></span> <span class="bold"><strong>unread</strong></span>
-messages as <span class="emphasis"><em>old</em></span> if you exit a mailbox without reading them.
-With this option <span class="emphasis"><em>set</em></span>, the next time you start mutt, the messages
-will show up with an “<span class="quote">O</span>” next to them in the index menu,
-indicating that they are old.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="markers"></a>3.114. markers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the display of wrapped lines in the internal pager. If set, a
-“<span class="quote">+</span>” marker is displayed at the beginning of wrapped lines.
-</p><p>
-Also see the <a class="link" href="reference.html#smart-wrap" title="3.267. smart_wrap">$smart_wrap</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mask"></a>3.115. mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">!^\.[^.]</code></span>”</p></div><p>
-A regular expression used in the file browser, optionally preceded by
-the <span class="emphasis"><em>not</em></span> operator “<span class="quote">!</span>”. Only files whose names match this mask
-will be shown. The match is always case-sensitive.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox"></a>3.116. mbox</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/mbox</code></span>”</p></div><p>
-This specifies the folder into which read mail in your <a class="link" href="reference.html#spoolfile" title="3.279. spoolfile">$spoolfile</a>
-folder will be appended.
-</p><p>
-Also see the <a class="link" href="reference.html#move" title="3.132. move">$move</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox-type"></a>3.117. mbox_type</h3></div></div></div><div class="literallayout"><p>Type: folder magic<br />
-Default: mbox</p></div><p>
-The default mailbox type used when creating new folders. May be any of
-“<span class="quote">mbox</span>”, “<span class="quote">MMDF</span>”, “<span class="quote">MH</span>” and “<span class="quote">Maildir</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="metoo"></a>3.118. metoo</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>unset</em></span>, Mutt will remove your address (see the “<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>”
-command) from the list of recipients when replying to a message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-context"></a>3.119. menu_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to <a class="link" href="reference.html#pager-context" title="3.139. pager_context">$pager_context</a>.)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-move-off"></a>3.120. menu_move_off</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, the bottom entry of menus will never scroll up past
-the bottom of the screen, unless there are less entries than lines.
-When <span class="emphasis"><em>set</em></span>, the bottom entry may move off the bottom.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-scroll"></a>3.121. menu_scroll</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, menus will be scrolled up or down one line when you
-attempt to move across a screen boundary. If <span class="emphasis"><em>unset</em></span>, the screen
-is cleared and the next or previous page of the menu is displayed
-(useful for slow links to avoid many redraws).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="meta-key"></a>3.122. meta_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, forces Mutt 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 <code class="literal">0xf8</code>, then this is treated as if the user had
-pressed Esc then “<span class="quote">x</span>”. This is because the result of removing the
-high bit from <code class="literal">0xf8</code> is <code class="literal">0x78</code>, which is the ASCII character
-“<span class="quote">x</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-purge"></a>3.123. mh_purge</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mutt will mimic mh's behaviour and rename deleted messages
-to <span class="emphasis"><em>,<old file name></em></span> in mh folders instead of really deleting
-them. This leaves the message on disk but makes programs reading the folder
-ignore it. If the variable is <span class="emphasis"><em>set</em></span>, the message files will simply be
-deleted.
-</p><p>
-This option is similar to <a class="link" href="reference.html#maildir-trash" title="3.112. maildir_trash">$maildir_trash</a> for Maildir folders.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-flagged"></a>3.124. mh_seq_flagged</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">flagged</code></span>”</p></div><p>
-The name of the MH sequence used for flagged messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-replied"></a>3.125. mh_seq_replied</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">replied</code></span>”</p></div><p>
-The name of the MH sequence used to tag replied messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-unseen"></a>3.126. mh_seq_unseen</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">unseen</code></span>”</p></div><p>
-The name of the MH sequence used for unseen messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward"></a>3.127. mime_forward</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the message you are forwarding will be attached as a
-separate <code class="literal">message/rfc822</code> 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 “<span class="quote">ask-no</span>” or “<span class="quote">ask-yes</span>”.
-</p><p>
-Also see <a class="link" href="reference.html#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="reference.html#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-decode"></a>3.128. mime_forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
-forwarding a message while <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span>. Otherwise
-<a class="link" href="reference.html#forward-decode" title="3.62. forward_decode">$forward_decode</a> is used instead.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-rest"></a>3.129. mime_forward_rest</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-When forwarding multiple attachments of a MIME message from the attachment
-menu, attachments which cannot be decoded in a reasonable manner will
-be attached to the newly composed message if this option is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix-entry-format"></a>3.130. mix_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %c %-16s %a</code></span>”</p></div><p>
-This variable describes the format of a remailer line on the mixmaster
-chain selection screen. The following <code class="literal">printf(3)</code>-like sequences are
-supported:
-
-</p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>The running number on the menu.
-</p></dd><dt><span class="term">%c </span></dt><dd><p>Remailer capabilities.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>The remailer's short name.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The remailer's e-mail address.
-</p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mixmaster"></a>3.131. mixmaster</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">mixmaster</code></span>”</p></div><p>
-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.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
-“<span class="quote">mixmaster-filter</span>” in /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="move"></a>3.132. move</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: no</p></div><p>
-Controls whether or not Mutt will move read messages
-from your spool mailbox to your <a class="link" href="reference.html#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
-a “<span class="quote"><a class="link" href="configuration.html#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cachedir"></a>3.133. message_cachedir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-</p><p>
-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-</p><p>
-Also see the <a class="link" href="reference.html#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cache-clean"></a>3.134. message_cache_clean</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-format"></a>3.135. message_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%s</code></span>”</p></div><p>
-This is the string displayed in the “<span class="quote">attachment</span>” menu for
-attachments of type <code class="literal">message/rfc822</code>. For a full listing of defined
-<code class="literal">printf(3)</code>-like sequences see the section on <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="narrow-tree"></a>3.136. narrow_tree</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable, when <span class="emphasis"><em>set</em></span>, makes the thread tree narrower, allowing
-deeper threads to fit on the screen.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="net-inc"></a>3.137. net_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-Operations that expect to transfer a large amount of data over the
-network will update their progress every <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a> kilobytes.
-If set to 0, no progress messages will be displayed.
-</p><p>
-See also <a class="link" href="reference.html#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="reference.html#write-inc" title="3.308. write_inc">$write_inc</a> and <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager"></a>3.138. pager</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">builtin</code></span>”</p></div><p>
-This variable specifies which pager you would like to use to view
-messages. The value “<span class="quote">builtin</span>” means to use the builtin pager, otherwise this
-variable should specify the pathname of the external pager you would
-like to use.
-</p><p>
-Using an external pager may have some disadvantages: Additional
-keystrokes are necessary because you can't call mutt functions
-directly from the pager, and screen resizes cause lines longer than
-the screen width to be badly formatted in the help menu.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-context"></a>3.139. pager_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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 will display the line after the last one on the screen
-at the top of the next page (0 lines of context).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-format"></a>3.140. pager_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-%Z- %C/%m: %-20.20n %s%* -- (%P)</code></span>”</p></div><p>
-This variable controls the format of the one-line message “<span class="quote">status</span>”
-displayed before each message in either the internal or an external
-pager. The valid sequences are listed in the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>
-section.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-index-lines"></a>3.141. pager_index_lines</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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 setting 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 <a class="link" href="reference.html#pager-index-lines" title="3.141. pager_index_lines">$pager_index_lines</a>, then the index will only use as
-many lines as it needs.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-stop"></a>3.142. pager_stop</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the internal-pager will <span class="bold"><strong>not</strong></span> move to the next message
-when you are at the end of a message and invoke the <code class="literal"><next-page></code>
-function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosign"></a>3.143. crypt_autosign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt 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 <a class="link" href="reference.html#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autoencrypt"></a>3.144. crypt_autoencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages. This is probably only useful in
-connection to the “<span class="quote"><a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>” command. It can be overridden
-by use of the pgp menu, when encryption is not required or
-signing is requested as well. If <a class="link" href="reference.html#smime-is-default" title="3.155. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-ignore-subkeys"></a>3.145. pgp_ignore_subkeys</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities. <span class="emphasis"><em>Unset</em></span> this
-if you want to play interesting key selection games.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replyencrypt"></a>3.146. crypt_replyencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysign"></a>3.147. crypt_replysign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages which are
-signed.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> this does not work on messages that are encrypted
-<span class="emphasis"><em>and</em></span> signed!
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysignencrypted"></a>3.148. crypt_replysignencrypted</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages
-which are encrypted. This makes sense in combination with
-<a class="link" href="reference.html#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>, because it allows you to sign all
-messages which are automatically encrypted. This works around
-the problem noted in <a class="link" href="reference.html#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a>, that mutt is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-timestamp"></a>3.149. crypt_timestamp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 <span class="emphasis"><em>unset</em></span> this setting.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-delim"></a>3.150. sidebar_delim</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">|</code></span>”</p></div><p>
-This specifies the delimiter between the sidebar (if visible) and
-other screens.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-visible"></a>3.151. sidebar_visible</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This specifies whether or not to show sidebar (left-side list of folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sidebar-width"></a>3.152. sidebar_width</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-The width of the sidebar.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-use-gpg-agent"></a>3.153. pgp_use_gpg_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will use a possibly-running <code class="literal">gpg-agent(1)</code> process.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-verify-sig"></a>3.154. crypt_verify_sig</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>“<span class="quote">yes</span>”</em></span>, always attempt to verify PGP or S/MIME signatures.
-If <span class="emphasis"><em>“<span class="quote">ask-*</span>”</em></span>, ask whether or not to verify the signature.
-If \Fi“<span class="quote">no</span>”, never attempt to verify cryptographic signatures.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-is-default"></a>3.155. smime_is_default</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-The default behaviour of mutt is to use PGP on all auto-sign/encryption
-operations. To override and to use OpenSSL instead this must be <span class="emphasis"><em>set</em></span>.
-However, this has no effect while replying, since mutt will automatically
-select the same application that was used to sign/encrypt the original
-message. (Note that this variable can be overridden by unsetting <a class="link" href="reference.html#crypt-autosmime" title="3.39. crypt_autosmime">$crypt_autosmime</a>.)
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ask-cert-label"></a>3.156. smime_ask_cert_label</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-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
-<span class="emphasis"><em>set</em></span> by default.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-use-default-key"></a>3.157. smime_decrypt_use_default_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span> (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate-key-pairs, mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-entry-format"></a>3.158. pgp_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %t%f %4l/0x%k %-4a %2c %u</code></span>”</p></div><p>
-This variable allows you to customize the PGP key selection menu to
-your personal taste. This string is similar to <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>, but
-has its own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>number
-</p></dd><dt><span class="term">%k </span></dt><dd><p>key id
-</p></dd><dt><span class="term">%u </span></dt><dd><p>user id
-</p></dd><dt><span class="term">%a </span></dt><dd><p>algorithm
-</p></dd><dt><span class="term">%l </span></dt><dd><p>key length
-</p></dd><dt><span class="term">%f </span></dt><dd><p>flags
-</p></dd><dt><span class="term">%c </span></dt><dd><p>capabilities
-</p></dd><dt><span class="term">%t </span></dt><dd><p>trust/validity of the key-uid association
-</p></dd><dt><span class="term">%[<s>] </span></dt><dd><p>date of the key where <s> is an <code class="literal">strftime(3)</code> expression
-</p></dd></dl></div><p>
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-good-sign"></a>3.159. pgp_good_sign</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: (empty)</p></div><p>
-If you assign a text to this variable, then a PGP signature is only
-considered verified if the output from <a class="link" href="reference.html#pgp-verify-command" title="3.176. pgp_verify_command">$pgp_verify_command</a> contains
-the text. Use this variable if the exit code from the command is 0
-even for bad signatures.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-check-exit"></a>3.160. pgp_check_exit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-long-ids"></a>3.161. pgp_long_ids</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, use 64 bit PGP key IDs, if <span class="emphasis"><em>unset</em></span> use the normal 32 bit key IDs.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-retainable-sigs"></a>3.162. pgp_retainable_sigs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, signed and encrypted messages will consist of nested
-<code class="literal">multipart/signed</code> and <code class="literal">multipart/encrypted</code> body parts.
-</p><p>
-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (<code class="literal">multipart/encrypted</code>) can be easily
-removed, while the inner <code class="literal">multipart/signed</code> part is retained.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-autoinline"></a>3.163. pgp_autoinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option controls whether Mutt 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.
-</p><p>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</p><p>
-Also see the <a class="link" href="reference.html#pgp-mime-auto" title="3.170. pgp_mime_auto">$pgp_mime_auto</a> variable.
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-replyinline"></a>3.164. pgp_replyinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt 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
-internals for previously checked/flagged messages.
-</p><p>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</p><p>
-Also see the <a class="link" href="reference.html#pgp-mime-auto" title="3.170. pgp_mime_auto">$pgp_mime_auto</a> variable.
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-show-unusable"></a>3.165. pgp_show_unusable</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 “<span class="quote">disabled</span>” by the user.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-as"></a>3.166. pgp_sign_as</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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. <code class="literal">0x00112233</code>).
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-strict-enc"></a>3.167. pgp_strict_enc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-timeout"></a>3.168. pgp_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 300</p></div><p>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sort-keys"></a>3.169. pgp_sort_keys</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: address</p></div><p>
-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-
-</p><div class="variablelist"><dl><dt><span class="term">address </span></dt><dd><p>sort alphabetically by user id
-</p></dd><dt><span class="term">keyid </span></dt><dd><p>sort alphabetically by key id
-</p></dd><dt><span class="term">date </span></dt><dd><p>sort by key creation date
-</p></dd><dt><span class="term">trust </span></dt><dd><p>sort by the trust of the key
-</p></dd></dl></div><p>
-If you prefer reverse order of the above values, prefix it with
-“<span class="quote">reverse-</span>”.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-auto"></a>3.170. pgp_mime_auto</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-auto-decode"></a>3.171. pgp_auto_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 <code class="literal"><a class="link" href="gettingstarted.html#check-traditional-pgp"><check-traditional-pgp></a></code> function, mutt will automatically
-check the message for traditional pgp.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-filename"></a>3.172. pgp_mime_signature_filename</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">signature.asc</code></span>”</p></div><p>
-This option sets the filename used for signature parts in PGP/MIME
-signed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-description"></a>3.173. pgp_mime_signature_description</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">Digital signature</code></span>”</p></div><p>
-This option sets the Content-Description used for signature parts in
-PGP/MIME signed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decode-command"></a>3.174. pgp_decode_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format strings specifies a command which is used to decode
-application/pgp attachments.
-</p><p>
-The PGP command formats have their own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%p </span></dt><dd><p>Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-string otherwise. Note: This may be used with a %? construct.
-</p></dd><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
- of a <code class="literal">multipart/signed</code> attachment when verifying it.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The value of <a class="link" href="reference.html#pgp-sign-as" title="3.166. pgp_sign_as">$pgp_sign_as</a>.
-</p></dd><dt><span class="term">%r </span></dt><dd><p>One or more key IDs.
-</p></dd></dl></div><p>
-For examples on how to configure these formats for the various versions
-of PGP which are floating around, see the pgp and gpg sample configuration files in
-the <code class="literal">samples/</code> subdirectory which has been installed on your system
-alongside the documentation.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-getkeys-command"></a>3.175. pgp_getkeys_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a>, %r is the only
-<code class="literal">printf(3)</code>-like sequence used with this format.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-command"></a>3.176. pgp_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify PGP signatures.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decrypt-command"></a>3.177. pgp_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to decrypt a PGP encrypted message.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-clearsign-command"></a>3.178. pgp_clearsign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format is used to create an old-style “<span class="quote">clearsigned</span>” PGP
-message. Note that the use of this format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-command"></a>3.179. pgp_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to create the detached PGP signature for a
-<code class="literal">multipart/signed</code> PGP/MIME body part.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-sign-command"></a>3.180. pgp_encrypt_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to both sign and encrypt a body part.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-only-command"></a>3.181. pgp_encrypt_only_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to encrypt a body part without signing it.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-import-command"></a>3.182. pgp_import_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to import a key from a message into
-the user's public key ring.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-export-command"></a>3.183. pgp_export_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to export a public key from the user's
-key ring.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-key-command"></a>3.184. pgp_verify_key_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify key information from the key selection
-menu.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-secring-command"></a>3.185. pgp_list_secring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to list the secret key ring's contents. The
-output format must be analogous to the one used by:
-
-</p><pre class="screen">
-gpg --list-keys --with-colons.
-
-</pre><p>
-This format is also generated by the <code class="literal">pgpring</code> utility which comes
-with mutt.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-pubring-command"></a>3.186. pgp_list_pubring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to list the public key ring's contents. The
-output format must be analogous to the one used by
-
-</p><pre class="screen">
-gpg --list-keys --with-colons.
-
-</pre><p>
-This format is also generated by the <code class="literal">pgpring</code> utility which comes
-with mutt.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.174. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decrypt"></a>3.187. forward_decrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the handling of encrypted messages when forwarding a message.
-When <span class="emphasis"><em>set</em></span>, the outer layer of encryption is stripped off. This
-variable is only used if <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span> and
-<a class="link" href="reference.html#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is <span class="emphasis"><em>unset</em></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-timeout"></a>3.188. smime_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 300</p></div><p>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-with"></a>3.189. smime_encrypt_with</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This sets the algorithm that should be used for encryption.
-Valid choices are “<span class="quote">des</span>”, “<span class="quote">des3</span>”, “<span class="quote">rc2-40</span>”, “<span class="quote">rc2-64</span>”, “<span class="quote">rc2-128</span>”.
-If <span class="emphasis"><em>unset</em></span>, “<span class="quote">3des</span>” (TripleDES) is used.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-keys"></a>3.190. smime_keys</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and 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 option points to the location of the private keys.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ca-location"></a>3.191. smime_ca_location</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this defaults to the first existing file in
-the following list: ˜/.smime/ca-certificates.crt ˜/.smime/ca-bundle.crt
-/etc/ssl/certs/ca-certificates.crt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-certificates"></a>3.192. smime_certificates</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-the location of the certificates.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-command"></a>3.193. smime_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format string specifies a command which is used to decrypt
-<code class="literal">application/x-pkcs7-mime</code> attachments.
-</p><p>
-The OpenSSL command formats have their own set of <code class="literal">printf(3)</code>-like sequences
-similar to PGP's:
-
-</p><div class="variablelist"><dl><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
- of a <code class="literal">multipart/signed</code> attachment when verifying it.
-</p></dd><dt><span class="term">%k </span></dt><dd><p>The key-pair specified with <a class="link" href="reference.html#smime-default-key" title="3.204. smime_default_key">$smime_default_key</a>
-</p></dd><dt><span class="term">%c </span></dt><dd><p>One or more certificate IDs.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The algorithm used for encryption.
-</p></dd><dt><span class="term">%C </span></dt><dd><p>CA location: Depending on whether <a class="link" href="reference.html#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a>
- points to a directory or file, this expands to
- “<span class="quote">-CApath <a class="link" href="reference.html#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a></span>” or “<span class="quote">-CAfile <a class="link" href="reference.html#smime-ca-location" title="3.191. smime_ca_location">$smime_ca_location</a></span>”.
-</p></dd></dl></div><p>
-For examples on how to configure these formats, see the <code class="literal">smime.rc</code> in
-the <code class="literal">samples/</code> subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-command"></a>3.194. smime_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify S/MIME signatures of type <code class="literal">multipart/signed</code>.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-opaque-command"></a>3.195. smime_verify_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify S/MIME signatures of type
-<code class="literal">application/x-pkcs7-mime</code>.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-command"></a>3.196. smime_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to created S/MIME signatures of type
-<code class="literal">multipart/signed</code>, which can be read by all mail clients.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-opaque-command"></a>3.197. smime_sign_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to created S/MIME signatures of type
-<code class="literal">application/x-pkcs7-signature</code>, which can only be handled by mail
-clients supporting the S/MIME extension.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-command"></a>3.198. smime_encrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to create encrypted S/MIME messages.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-pk7out-command"></a>3.199. smime_pk7out_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-command"></a>3.200. smime_get_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to extract X509 certificates from a PKCS7 structure.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-signer-cert-command"></a>3.201. smime_get_signer_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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 “<span class="quote">From:</span>” field.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-import-cert-command"></a>3.202. smime_import_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to import a certificate via smime_keys.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-email-command"></a>3.203. smime_get_cert_email_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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).
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.193. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-default-key"></a>3.204. smime_default_key</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-client-cert"></a>3.205. ssl_client_cert</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-The file containing a client certificate and its associated private
-key.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-force-tls"></a>3.206. ssl_force_tls</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If this variable is <span class="emphasis"><em>set</em></span>, Mutt 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 <a class="link" href="reference.html#ssl-starttls" title="3.207. ssl_starttls">$ssl_starttls</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-starttls"></a>3.207. ssl_starttls</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span> (the default), mutt will attempt to use <code class="literal">STARTTLS</code> on servers
-advertising the capability. When <span class="emphasis"><em>unset</em></span>, mutt will not attempt to
-use <code class="literal">STARTTLS</code> regardless of the server's capabilities.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="certificate-file"></a>3.208. certificate_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.mutt_certificates</code></span>”</p></div><p>
-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.
-</p><p>
-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set certificate_file=~/.mutt/certificates
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-sslv3"></a>3.209. ssl_use_sslv3</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-tlsv1"></a>3.210. ssl_use_tlsv1</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-min-dh-prime-bits"></a>3.211. ssl_min_dh_prime_bits</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-ca-certificates-file"></a>3.212. ssl_ca_certificates_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this variable defaults to the example
-mentioned. This file is managed by the “<span class="quote">ca-certificates</span>” package.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-split"></a>3.213. pipe_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><pipe-message></code> function following
-<code class="literal"><tag-prefix></code>. If this variable is <span class="emphasis"><em>unset</em></span>, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated. When <span class="emphasis"><em>set</em></span>, Mutt will pipe the messages one by one.
-In both cases the messages are piped in the current sorted order,
-and the <a class="link" href="reference.html#pipe-sep" title="3.215. pipe_sep">$pipe_sep</a> separator is added after each message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-decode"></a>3.214. pipe_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><pipe-message></code> command. When <span class="emphasis"><em>unset</em></span>,
-Mutt will pipe the messages without any preprocessing. When <span class="emphasis"><em>set</em></span>, Mutt
-will weed headers and will attempt to decode the messages
-first.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-sep"></a>3.215. pipe_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
-The separator to add between messages when piping a list of tagged
-messages to an external Unix command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-authenticators"></a>3.216. pop_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an POP server, in the order mutt should
-try them. Authentication methods are either “<span class="quote">user</span>”, “<span class="quote">apop</span>” or any
-SASL mechanism, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
-This option is case-insensitive. If this option is <span class="emphasis"><em>unset</em></span>
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set pop_authenticators="digest-md5:apop:user"
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-auth-try-all"></a>3.217. pop_auth_try_all</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will try all available authentication methods.
-When <span class="emphasis"><em>unset</em></span>, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-checkinterval"></a>3.218. pop_checkinterval</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 60</p></div><p>
-This variable configures how often (in seconds) mutt should look for
-new mail in the currently selected mailbox if it is a POP mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-delete"></a>3.219. pop_delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will delete successfully downloaded messages from the POP
-server when using the <code class="literal"><a class="link" href="optionalfeatures.html#fetch-mail"><fetch-mail></a></code> function. When <span class="emphasis"><em>unset</em></span>, Mutt will
-download messages but also leave them on the POP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-host"></a>3.220. pop_host</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-The name of your POP server for the <code class="literal"><a class="link" href="optionalfeatures.html#fetch-mail"><fetch-mail></a></code> function. You
-can also specify an alternative port, username and password, ie:
-
-</p><pre class="screen">
-[pop[s]://][username[:password]@]popserver[:port]
-
-</pre><p>
-where “<span class="quote">[...]</span>” denotes an optional part.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-last"></a>3.221. pop_last</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If this variable is <span class="emphasis"><em>set</em></span>, mutt will try to use the “<span class="quote"><code class="literal">LAST</code></span>” POP command
-for retrieving only unread messages from the POP server when using
-the <code class="literal"><a class="link" href="optionalfeatures.html#fetch-mail"><fetch-mail></a></code> function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-reconnect"></a>3.222. pop_reconnect</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-user"></a>3.223. pop_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Your login name on the POP server.
-</p><p>
-This variable defaults to your user name on the local machine.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-pass"></a>3.224. pop_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your POP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you open a POP mailbox.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc
-even if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="post-indent-string"></a>3.225. post_indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Similar to the <a class="link" href="reference.html#attribution" title="3.16. attribution">$attribution</a> variable, Mutt will append this
-string after the inclusion of a message which is being replied to.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone"></a>3.226. postpone</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not messages are saved in the <a class="link" href="reference.html#postponed" title="3.227. postponed">$postponed</a>
-mailbox when you elect not to send immediately.
-</p><p>
-Also see the <a class="link" href="reference.html#recall" title="3.241. recall">$recall</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postponed"></a>3.227. postponed</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/postponed</code></span>”</p></div><p>
-Mutt allows you to indefinitely “<span class="quote"><a class="link" href="reference.html#postpone" title="3.226. postpone">postpone</a> sending a message</span>” which
-you are editing. When you choose to postpone a message, Mutt saves it
-in the mailbox specified by this variable.
-</p><p>
-Also see the <a class="link" href="reference.html#postpone" title="3.226. postpone">$postpone</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="preconnect"></a>3.228. preconnect</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-If <span class="emphasis"><em>set</em></span>, a shell command to be executed if mutt fails to establish
-a connection to the server. This is useful for setting up secure
-connections, e.g. with <code class="literal">ssh(1)</code>. If the command returns a nonzero
-status, mutt gives up opening the server. Example:
-
-</p><pre class="screen">
-set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
-sleep 20 < /dev/null > /dev/null"
-
-</pre><p>
-Mailbox “<span class="quote">foo</span>” on “<span class="quote">mailhost.net</span>” can now be reached
-as “<span class="quote">{localhost:1234}foo</span>”.
-</p><p>
-Note: For this example to work, you must be able to log in to the
-remote machine without having to enter a password.
-</p><p>
-When set, Mutt uses the tunnel for all remote connections.
-Please see “<span class="quote"><a class="link" href="optionalfeatures.html#account-hook" title="6. Managing multiple accounts">account-hook</a></span>” in the manual for how to use different
-tunnel commands per connection.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print"></a>3.229. print</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-no</p></div><p>
-Controls whether or not Mutt really prints messages.
-This is set to “<span class="quote">ask-no</span>” by default, because some people
-accidentally hit “<span class="quote">p</span>” often.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-command"></a>3.230. print_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">lpr</code></span>”</p></div><p>
-This specifies the command pipe that should be used to print messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-decode"></a>3.231. print_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Used in connection with the <code class="literal"><print-message></code> command. If this
-option is <span class="emphasis"><em>set</em></span>, the message is decoded before it is passed to the
-external command specified by <a class="link" href="reference.html#print-command" title="3.230. print_command">$print_command</a>. If this option
-is <span class="emphasis"><em>unset</em></span>, 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-split"></a>3.232. print_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><print-message></code> command. If this option
-is <span class="emphasis"><em>set</em></span>, the command specified by <a class="link" href="reference.html#print-command" title="3.230. print_command">$print_command</a> is executed once for
-each message which is to be printed. If this option is <span class="emphasis"><em>unset</em></span>,
-the command specified by <a class="link" href="reference.html#print-command" title="3.230. print_command">$print_command</a> is executed only once, and
-all the messages are concatenated, with a form feed as the message
-separator.
-</p><p>
-Those who use the <code class="literal">enscript</code>(1) program's mail-printing mode will
-most likely want to <span class="emphasis"><em>set</em></span> this option.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="prompt-after"></a>3.233. prompt_after</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If you use an <span class="emphasis"><em>external</em></span> <a class="link" href="reference.html#pager" title="3.138. pager">$pager</a>, setting this variable will
-cause Mutt to prompt you for a command when the pager exits rather
-than returning to the index menu. If <span class="emphasis"><em>unset</em></span>, Mutt will return to the
-index menu when the external pager exits.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-command"></a>3.234. query_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This specifies the command that mutt will use to make external address
-queries. The string should contain a “<span class="quote">%s</span>”, which will be substituted
-with the query string the user types. See “<span class="quote"><a class="link" href="advancedusage.html#query" title="5. External Address Queries">query</a></span>” for more
-information.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-format"></a>3.235. query_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4c %t %-25.25a %-25.25n %?e?(%e)?</code></span>”</p></div><p>
-This variable describes the format of the “<span class="quote">query</span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are understood:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>destination address
-</p></dd><dt><span class="term">%c </span></dt><dd><p>current entry number
-</p></dd><dt><span class="term">%e </span></dt><dd><p>extra information *
-</p></dd><dt><span class="term">%n </span></dt><dd><p>destination name
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if current entry is tagged, a space otherwise
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p><p>
-* = can be optionally printed if nonzero, see the <a class="link" href="reference.html#status-format" title="3.281. status_format">$status_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quit"></a>3.236. quit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether “<span class="quote">quit</span>” and “<span class="quote">exit</span>” actually quit
-from mutt. If this option is <span class="emphasis"><em>set</em></span>, they do quit, if it is <span class="emphasis"><em>unset</em></span>, they
-have no effect, and if it is set to <span class="emphasis"><em>ask-yes</em></span> or <span class="emphasis"><em>ask-no</em></span>, you are
-prompted for confirmation when you try to quit.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quote-regexp"></a>3.237. quote_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^([ \t]*[|>:}#])+</code></span>”</p></div><p>
-A regular expression used in the internal pager to determine quoted
-sections of text in the body of a message. Quoted text may be filtered
-out using the <code class="literal"><toggle-quoted></code> command, or colored according to the
-“<span class="quote">color quoted</span>” family of directives.
-</p><p>
-Higher levels of quoting may be colored differently (“<span class="quote">color quoted1</span>”,
-“<span class="quote">color quoted2</span>”, etc.). The quoting level is determined by removing
-the last character from the matched text and recursively reapplying
-the regular expression until it fails to produce a match.
-</p><p>
-Match detection may be overridden by the <a class="link" href="reference.html#smileys" title="3.268. smileys">$smileys</a> regular expression.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-inc"></a>3.238. read_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-If set to a value greater than 0, Mutt will display which message it
-is currently on when reading a mailbox or when performing search actions
-such as search and limit. The message is printed after
-this many messages have been read or searched (e.g., if set to 25, Mutt will
-print a message when it is at message 25, and then again when it gets
-to message 50). This variable is meant to indicate progress when
-reading or searching large mailboxes which may take some time.
-When set to 0, only a single message will appear before the reading
-the mailbox.
-</p><p>
-Also see the <a class="link" href="reference.html#write-inc" title="3.308. write_inc">$write_inc</a>, <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="reference.html#time-inc" title="3.289. time_inc">$time_inc</a> variables and the
-“<span class="quote"><a class="link" href="tuning.html" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-only"></a>3.239. read_only</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, all folders are opened in read-only mode.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="realname"></a>3.240. realname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable specifies what “<span class="quote">real</span>” or “<span class="quote">personal</span>” name should be used
-when sending messages.
-</p><p>
-By default, this is the GECOS field from <code class="literal">/etc/passwd</code>. Note that this
-variable will <span class="emphasis"><em>not</em></span> be used when the user has set a real name
-in the <a class="link" href="reference.html#from" title="3.66. from">$from</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="recall"></a>3.241. recall</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not Mutt recalls postponed messages
-when composing a new message.
-</p><p>
-<span class="emphasis"><em>Setting</em></span> this variable to is not generally useful, and thus not
-recommended.
-</p><p>
-Also see <a class="link" href="reference.html#postponed" title="3.227. postponed">$postponed</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="record"></a>3.242. record</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/sent</code></span>”</p></div><p>
-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 “<span class="quote"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command to create a “<span class="quote">Bcc:</span>” field with your email address in it.)
-</p><p>
-The value of <span class="emphasis"><em><a class="link" href="reference.html#record" title="3.242. record">$record</a></em></span> is overridden by the <a class="link" href="reference.html#force-name" title="3.61. force_name">$force_name</a> and
-<a class="link" href="reference.html#save-name" title="3.254. save_name">$save_name</a> variables, and the “<span class="quote"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-regexp"></a>3.243. reply_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^(re([\[0-9\]+])*|aw):[ \t]*</code></span>”</p></div><p>
-A regular expression used to recognize reply messages when threading
-and replying. The default value corresponds to the English "Re:" and
-the German "Aw:".
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-self"></a>3.244. reply_self</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>unset</em></span> and you are replying to a message sent by you, Mutt will
-assume that you want to reply to the recipients of that message rather
-than to yourself.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-to"></a>3.245. reply_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, when replying to a message, Mutt will use the address listed
-in the Reply-to: header as the recipient of the reply. If <span class="emphasis"><em>unset</em></span>,
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="resolve"></a>3.246. resolve</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the cursor will be automatically advanced to the next
-(possibly undeleted) message whenever a command that modifies the
-current message is executed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-alias"></a>3.247. reverse_alias</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls whether or not Mutt will display the “<span class="quote">personal</span>”
-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:
-
-</p><pre class="screen">
-alias juser abd30425@somewhere.net (Joe User)
-
-</pre><p>
-and then you receive mail which contains the following header:
-
-</p><pre class="screen">
-From: abd30425@somewhere.net
-
-</pre><p>
-It would be displayed in the index menu as “<span class="quote">Joe User</span>” instead of
-“<span class="quote">abd30425@somewhere.net.</span>” This is useful when the person's e-mail
-address is not human friendly.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-name"></a>3.248. reverse_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <span class="emphasis"><em>set</em></span>, the default <span class="emphasis"><em>From:</em></span> line of
-the reply messages is built using the address where you received the
-messages you are replying to <span class="bold"><strong>if</strong></span> that address matches your
-“<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>”. If the variable is <span class="emphasis"><em>unset</em></span>, or the address that would be
-used doesn't match your “<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>”, the <span class="emphasis"><em>From:</em></span> line will use
-your address on the current machine.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-realname"></a>3.249. reverse_realname</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable fine-tunes the behaviour of the <a class="link" href="reference.html#reverse-name" title="3.248. reverse_name">$reverse_name</a> feature.
-When it is <span class="emphasis"><em>set</em></span>, mutt will use the address from incoming messages as-is,
-possibly including eventual real names. When it is <span class="emphasis"><em>unset</em></span>, mutt will
-override any such real names with the setting of the <a class="link" href="reference.html#realname" title="3.240. realname">$realname</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="rfc2047-parameters"></a>3.250. rfc2047_parameters</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, Mutt will decode RFC2047-encoded MIME
-parameters. You want to set this variable when mutt suggests you
-to save attachments to files named like:
-
-</p><pre class="screen">
-=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-</pre><p>
-When this variable is <span class="emphasis"><em>set</em></span> interactively, the change won't be
-active until you change folders.
-</p><p>
-Note that this use of RFC2047's encoding is explicitly
-prohibited by the standard, but nevertheless encountered in the
-wild.
-</p><p>
-Also note that setting this parameter will <span class="emphasis"><em>not</em></span> have the effect
-that mutt <span class="emphasis"><em>generates</em></span> this kind of encoding. Instead, mutt will
-unconditionally use the encoding specified in RFC2231.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-address"></a>3.251. save_address</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If <a class="link" href="reference.html#save-name" title="3.254. save_name">$save_name</a> or <a class="link" href="reference.html#force-name" title="3.61. force_name">$force_name</a>
-is <span class="emphasis"><em>set</em></span> too, the selection of the Fcc folder will be changed as well.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-empty"></a>3.252. save_empty</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mailboxes which contain no saved messages will be removed
-when closed (the exception is <a class="link" href="reference.html#spoolfile" title="3.279. spoolfile">$spoolfile</a> which is never removed).
-If <span class="emphasis"><em>set</em></span>, mailboxes are never removed.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> This only applies to mbox and MMDF folders, Mutt does not
-delete MH and Maildir directories.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-history"></a>3.253. save_history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-This variable controls the size of the history (per category) saved in the
-<a class="link" href="reference.html#history-file" title="3.78. history_file">$history_file</a> file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-name"></a>3.254. save_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls how copies of outgoing messages are saved.
-When <span class="emphasis"><em>set</em></span>, 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 <a class="link" href="reference.html#folder" title="3.58. folder">$folder</a> directory with the <span class="emphasis"><em>username</em></span> 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
-<a class="link" href="reference.html#record" title="3.242. record">$record</a> mailbox.
-</p><p>
-Also see the <a class="link" href="reference.html#force-name" title="3.61. force_name">$force_name</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score"></a>3.255. score</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>unset</em></span>, scoring is turned off. This can
-be useful to selectively disable scoring for certain folders when the
-<a class="link" href="reference.html#score-threshold-delete" title="3.256. score_threshold_delete">$score_threshold_delete</a> variable and related are used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-delete"></a>3.256. score_threshold_delete</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: -1</p></div><p>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked for deletion by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message for deletion.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-flag"></a>3.257. score_threshold_flag</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 9999</p></div><p>
-Messages which have been assigned a score greater than or equal to this
-variable's value are automatically marked "flagged".
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-read"></a>3.258. score_threshold_read</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: -1</p></div><p>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked as read by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message read.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="send-charset"></a>3.259. send_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">us-ascii:iso-8859-1:utf-8</code></span>”</p></div><p>
-A colon-delimited list of character sets for outgoing messages. Mutt will use the
-first character set into which the text can be converted exactly.
-If your <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> is not “<span class="quote">iso-8859-1</span>” and recipients may not
-understand “<span class="quote">UTF-8</span>”, it is advisable to include in the list an
-appropriate widely used standard character set (such as
-“<span class="quote">iso-8859-2</span>”, “<span class="quote">koi8-r</span>” or “<span class="quote">iso-2022-jp</span>”) either instead of or after
-“<span class="quote">iso-8859-1</span>”.
-</p><p>
-In case the text cannot be converted into one of these exactly,
-mutt uses <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> as a fallback.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail"></a>3.260. sendmail</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">/usr/sbin/sendmail -oem -oi</code></span>”</p></div><p>
-Specifies the program and arguments used to deliver mail sent by Mutt.
-Mutt expects that the specified program interprets additional
-arguments as recipient addresses.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail-wait"></a>3.261. sendmail_wait</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-Specifies the number of seconds to wait for the <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a> process
-to finish before giving up and putting delivery in the background.
-</p><p>
-Mutt interprets the value of this variable as follows:
-
-</p><div class="variablelist"><dl><dt><span class="term">>0 </span></dt><dd><p>number of seconds to wait for sendmail to finish before continuing
-</p></dd><dt><span class="term">0 </span></dt><dd><p>wait forever for sendmail to finish
-</p></dd><dt><span class="term"><0 </span></dt><dd><p>always put sendmail in the background without waiting
-</p></dd></dl></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="shell"></a>3.262. shell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Command to use when spawning a subshell. By default, the user's login
-shell from <code class="literal">/etc/passwd</code> is used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-dashes"></a>3.263. sig_dashes</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, a line containing “<span class="quote">-- </span>” (note the trailing space) will be inserted before your
-<a class="link" href="reference.html#signature" title="3.265. signature">$signature</a>. It is <span class="bold"><strong>strongly</strong></span> recommended that you not <span class="emphasis"><em>unset</em></span>
-this variable unless your signature contains just your name. The
-reason for this is because many software packages use “<span class="quote">-- \n</span>” to
-detect your signature. For example, Mutt has the ability to highlight
-the signature in a different color in the builtin pager.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-on-top"></a>3.264. sig_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, the signature will be included before any quoted or forwarded
-text. It is <span class="bold"><strong>strongly</strong></span> 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="signature"></a>3.265. signature</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.signature</code></span>”</p></div><p>
-Specifies the filename of your signature, which is appended to all
-outgoing messages. If the filename ends with a pipe (“<span class="quote">|</span>”), it is
-assumed that filename is a shell command and input should be read from
-its standard output.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-search"></a>3.266. simple_search</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜f %s | ˜s %s</code></span>”</p></div><p>
-Specifies how Mutt should expand a simple search into a real search
-pattern. A simple search is one that does not contain any of the “<span class="quote">˜</span>” pattern
-operators. See “<span class="quote"><a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>” for more information on search patterns.
-</p><p>
-For example, if you simply type “<span class="quote">joe</span>” at a search or limit prompt, Mutt
-will automatically expand it to the value specified by this variable by
-replacing “<span class="quote">%s</span>” with the supplied string.
-For the default value, “<span class="quote">joe</span>” would be expanded to: “<span class="quote">˜f joe | ˜s joe</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smart-wrap"></a>3.267. smart_wrap</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the display of lines longer than the screen width in the
-internal pager. If <span class="emphasis"><em>set</em></span>, long lines are wrapped at a word boundary. If
-<span class="emphasis"><em>unset</em></span>, lines are simply wrapped at the screen edge. Also see the
-<a class="link" href="reference.html#markers" title="3.114. markers">$markers</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smileys"></a>3.268. smileys</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">(>From )|(:[-^]?[][)(><}{|/DP])</code></span>”</p></div><p>
-The <span class="emphasis"><em>pager</em></span> uses this variable to catch some common false
-positives of <a class="link" href="reference.html#quote-regexp" title="3.237. quote_regexp">$quote_regexp</a>, most notably smileys and not consider
-a line quoted text if it also matches <a class="link" href="reference.html#smileys" title="3.268. smileys">$smileys</a>. This mostly
-happens at the beginning of a line.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sleep-time"></a>3.269. sleep_time</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 1</p></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-authenticators"></a>3.270. smtp_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an SMTP server, in the order mutt should
-try them. Authentication methods are any SASL mechanism, eg
-“<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
-This option is case-insensitive. If it is “<span class="quote">unset</span>”
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set smtp_authenticators="digest-md5:cram-md5"
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-pass"></a>3.271. smtp_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your SMTP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you first send mail via SMTP.
-See <a class="link" href="reference.html#smtp-url" title="3.272. smtp_url">$smtp_url</a> to configure mutt to send mail via SMTP.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-url"></a>3.272. smtp_url</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Defines the SMTP smarthost where sent messages should relayed for
-delivery. This should take the form of an SMTP URL, eg:
-
-</p><pre class="screen">
-smtp[s]://[user[:pass]@]host[:port]/
-
-</pre><p>
-\.\.\. where “<span class="quote">[...]</span>” denotes an optional part.
-Setting this variable overrides the value of the <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a>
-variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort"></a>3.273. sort</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: date</p></div><p>
-Specifies how to sort messages in the “<span class="quote">index</span>” menu. Valid values
-are:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>date or date-sent
-</p></li><li><p>date-received
-</p></li><li><p>from
-</p></li><li><p>mailbox-order (unsorted)
-</p></li><li><p>score
-</p></li><li><p>size
-</p></li><li><p>spam
-</p></li><li><p>subject
-</p></li><li><p>threads
-</p></li><li><p>to
-</p></li></ul></div><p>
-You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
-order (example: “<span class="quote"><code class="literal">set sort=reverse-date-sent</code></span>”).
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
-“<span class="quote">threads</span>” in /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-alias"></a>3.274. sort_alias</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: alias</p></div><p>
-Specifies how the entries in the “<span class="quote">alias</span>” menu are sorted. The
-following are legal values:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>address (sort alphabetically by email address)
-</p></li><li><p>alias (sort alphabetically by alias name)
-</p></li><li><p>unsorted (leave in order specified in .muttrc)
-</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-aux"></a>3.275. sort_aux</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: date</p></div><p>
-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 <a class="link" href="reference.html#sort" title="3.273. sort">$sort</a> can, except
-“<span class="quote">threads</span>” (in that case, mutt will just use “<span class="quote">date-sent</span>”). You can also
-specify the “<span class="quote">last-</span>” prefix in addition to the “<span class="quote">reverse-</span>” prefix, but “<span class="quote">last-</span>”
-must come after “<span class="quote">reverse-</span>”. The “<span class="quote">last-</span>” prefix causes messages to be
-sorted against its siblings by which has the last descendant, using
-the rest of <a class="link" href="reference.html#sort-aux" title="3.275. sort_aux">$sort_aux</a> as an ordering. For instance,
-
-</p><pre class="screen">
-set sort_aux=last-date-received
-
-</pre><p>
-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 “<span class="quote"><code class="literal">set sort=reverse-threads</code></span>”.)
-</p><p>
-Note: For reversed <a class="link" href="reference.html#sort" title="3.273. sort">$sort</a>
-order <a class="link" href="reference.html#sort-aux" title="3.275. sort_aux">$sort_aux</a> is reversed again (which is not the right thing to do,
-but kept to not break any existing configuration setting).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-browser"></a>3.276. sort_browser</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: alpha</p></div><p>
-Specifies how to sort entries in the file browser. By default, the
-entries are sorted alphabetically. Valid values:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>alpha (alphabetically)
-</p></li><li><p>date
-</p></li><li><p>size
-</p></li><li><p>unsorted
-</p></li></ul></div><p>
-You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
-order (example: “<span class="quote"><code class="literal">set sort_browser=reverse-date</code></span>”).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-re"></a>3.277. sort_re</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable is only useful when sorting by threads with
-<a class="link" href="reference.html#strict-threads" title="3.283. strict_threads">$strict_threads</a> <span class="emphasis"><em>unset</em></span>. In that case, it changes the heuristic
-mutt uses to thread messages by subject. With <a class="link" href="reference.html#sort-re" title="3.277. sort_re">$sort_re</a> <span class="emphasis"><em>set</em></span>, mutt 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 <a class="link" href="reference.html#reply-regexp" title="3.243. reply_regexp">$reply_regexp</a>. With <a class="link" href="reference.html#sort-re" title="3.277. sort_re">$sort_re</a> <span class="emphasis"><em>unset</em></span>, mutt will attach
-the message whether or not this is the case, as long as the
-non-<a class="link" href="reference.html#reply-regexp" title="3.243. reply_regexp">$reply_regexp</a> parts of both messages are identical.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spam-separator"></a>3.278. spam_separator</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">,</code></span>”</p></div><p>
-This variable controls what happens when multiple spam headers
-are matched: if <span class="emphasis"><em>unset</em></span>, each successive header will overwrite any
-previous matches value for the spam label. If <span class="emphasis"><em>set</em></span>, each successive
-match will append to the previous, using this variable's value as a
-separator.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spoolfile"></a>3.279. spoolfile</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-If your spool mailbox is in a non-default place where Mutt cannot find
-it, you can specify its location with this variable. Mutt will
-automatically set this variable to the value of the environment
-variable <code class="literal">$MAIL</code> if it is not set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-chars"></a>3.280. status_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-*%A</code></span>”</p></div><p>
-Controls the characters used by the “<span class="quote">%r</span>” indicator in
-<a class="link" href="reference.html#status-format" title="3.281. status_format">$status_format</a>. 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 <code class="literal"><toggle-write></code> operation, bound by default to “<span class="quote">%</span>”). 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).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-format"></a>3.281. status_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-%r-Mutt: %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)---</code></span>”</p></div><p>
-Controls the format of the status line displayed in the “<span class="quote">index</span>”
-menu. This string is similar to <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>, but has its own
-set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%b </span></dt><dd><p>number of mailboxes with new mail *
-</p></dd><dt><span class="term">%d </span></dt><dd><p>number of deleted messages *
-</p></dd><dt><span class="term">%f </span></dt><dd><p>the full pathname of the current mailbox
-</p></dd><dt><span class="term">%F </span></dt><dd><p>number of flagged messages *
-</p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
-</p></dd><dt><span class="term">%l </span></dt><dd><p>size (in bytes) of the current mailbox *
-</p></dd><dt><span class="term">%L </span></dt><dd><p>size (in bytes) of the messages shown
-(i.e., which match the current limit) *
-</p></dd><dt><span class="term">%m </span></dt><dd><p>the number of messages in the mailbox *
-</p></dd><dt><span class="term">%M </span></dt><dd><p>the number of messages shown (i.e., which match the current limit) *
-</p></dd><dt><span class="term">%n </span></dt><dd><p>number of new messages in the mailbox *
-</p></dd><dt><span class="term">%o </span></dt><dd><p>number of old unread messages *
-</p></dd><dt><span class="term">%p </span></dt><dd><p>number of postponed messages *
-</p></dd><dt><span class="term">%P </span></dt><dd><p>percentage of the way through the index
-</p></dd><dt><span class="term">%r </span></dt><dd><p>modified/read-only/won't-write/attach-message indicator,
-according to <a class="link" href="reference.html#status-chars" title="3.280. status_chars">$status_chars</a>
-</p></dd><dt><span class="term">%s </span></dt><dd><p>current sorting mode (<a class="link" href="reference.html#sort" title="3.273. sort">$sort</a>)
-</p></dd><dt><span class="term">%S </span></dt><dd><p>current aux sorting method (<a class="link" href="reference.html#sort-aux" title="3.275. sort_aux">$sort_aux</a>)
-</p></dd><dt><span class="term">%t </span></dt><dd><p>number of tagged messages *
-</p></dd><dt><span class="term">%u </span></dt><dd><p>number of unread messages *
-</p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
-</p></dd><dt><span class="term">%V </span></dt><dd><p>currently active limit pattern, if any *
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p><p>
-* = can be optionally printed if nonzero
-</p><p>
-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:
-</p><p>
-<code class="literal">%?<sequence_char>?<optional_string>?</code>
-</p><p>
-where <span class="emphasis"><em>sequence_char</em></span> is a character from the table above, and
-<span class="emphasis"><em>optional_string</em></span> is the string you would like printed if
-<span class="emphasis"><em>sequence_char</em></span> is nonzero. <span class="emphasis"><em>optional_string</em></span> <span class="bold"><strong>may</strong></span> contain
-other sequences as well as normal text, but you may <span class="bold"><strong>not</strong></span> nest
-optional strings.
-</p><p>
-Here is an example illustrating how to optionally print the number of
-new messages in a mailbox:
-</p><p>
-<code class="literal">%?n?%n new messages.?</code>
-</p><p>
-You can also switch between two strings using the following construct:
-</p><p>
-<code class="literal">%?<sequence_char>?<if_string>&<else_string>?</code>
-</p><p>
-If the value of <span class="emphasis"><em>sequence_char</em></span> is non-zero, <span class="emphasis"><em>if_string</em></span> will
-be expanded, otherwise <span class="emphasis"><em>else_string</em></span> will be expanded.
-</p><p>
-You can force the result of any <code class="literal">printf(3)</code>-like sequence to be lowercase
-by prefixing the sequence character with an underscore (“<span class="quote">_</span>”) sign.
-For example, if you want to display the local hostname in lowercase,
-you would use: “<span class="quote"><code class="literal">%_h</code></span>”.
-</p><p>
-If you prefix the sequence character with a colon (“<span class="quote">:</span>”) character, mutt
-will replace any dots in the expansion by underscores. This might be helpful
-with IMAP folders that don't like dots in folder names.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-on-top"></a>3.282. status_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable causes the “<span class="quote">status bar</span>” to be displayed on
-the first line of the screen rather than near the bottom. If <a class="link" href="reference.html#help" title="3.70. help">$help</a>
-is <span class="emphasis"><em>set</em></span>, too it'll be placed at the bottom.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="strict-threads"></a>3.283. strict_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, threading will only make use of the “<span class="quote">In-Reply-To</span>” and
-“<span class="quote">References:</span>” fields when you <a class="link" href="reference.html#sort" title="3.273. sort">$sort</a> by message threads. By
-default, messages with the same subject are grouped together in
-“<span class="quote">pseudo threads.</span>”. This may not always be desirable, such as in a
-personal mailbox where you might have several unrelated messages with
-the subjects like “<span class="quote">hi</span>” which will get grouped together. See also
-<a class="link" href="reference.html#sort-re" title="3.277. sort_re">$sort_re</a> for a less drastic way of controlling this
-behaviour.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="suspend"></a>3.284. suspend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mutt won't stop when the user presses the terminal's
-<span class="emphasis"><em>susp</em></span> key, usually “<span class="quote">^Z</span>”. This is useful if you run mutt
-inside an xterm using a command like “<span class="quote"><code class="literal">xterm -e mutt</code></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="text-flowed"></a>3.285. text_flowed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will generate “<span class="quote">format=flowed</span>” bodies with a content type
-of “<span class="quote"><code class="literal">text/plain; format=flowed</code></span>”.
-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.
-</p><p>
-Note that <a class="link" href="reference.html#indent-string" title="3.100. indent_string">$indent_string</a> is ignored when this option is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thread-received"></a>3.286. thread_received</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt uses the date received rather than the date sent
-to thread messages by subject.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thorough-search"></a>3.287. thorough_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Affects the <code class="literal">˜b</code> and <code class="literal">˜h</code> search operations described in
-section “<span class="quote"><a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>”. If <span class="emphasis"><em>set</em></span>, the headers and body/attachments of
-messages to be searched are decoded before searching. If <span class="emphasis"><em>unset</em></span>,
-messages are searched as they appear in the folder.
-</p><p>
-Users searching attachments or for non-ASCII characters should <span class="emphasis"><em>set</em></span>
-this value because decoding also includes MIME parsing/decoding and possible
-character set conversions. Otherwise mutt will attempt to match against the
-raw message received (for example quoted-printable encoded or with encoded
-headers) which may lead to incorrect search results.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tilde"></a>3.288. tilde</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the internal-pager will pad blank lines to the bottom of the
-screen with a tilde (“<span class="quote">˜</span>”).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="time-inc"></a>3.289. time_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-Along with <a class="link" href="reference.html#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="reference.html#write-inc" title="3.308. write_inc">$write_inc</a>, and <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a>, this
-variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than <a class="link" href="reference.html#time-inc" title="3.289. time_inc">$time_inc</a> milliseconds
-apart. This can improve throughput on systems with slow terminals,
-or when running mutt on a remote system.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="tuning.html" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="timeout"></a>3.290. timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 600</p></div><p>
-When Mutt is waiting for user input either idleing in menus or
-in an interactive prompt, Mutt would block until input is
-present. Depending on the context, this would prevent certain
-operations from working, like checking for new mail or keeping
-an IMAP connection alive.
-</p><p>
-This variable controls how many seconds Mutt will at most wait
-until it aborts waiting for input, performs these operations and
-continues to wait for input.
-</p><p>
-A value of zero or less will cause Mutt to never time out.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tmpdir"></a>3.291. tmpdir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable allows you to specify where Mutt will place its
-temporary files needed for displaying and composing messages. If
-this variable is not set, the environment variable <code class="literal">$TMPDIR</code> is
-used. If <code class="literal">$TMPDIR</code> is not set then “<span class="quote"><code class="literal">/tmp</code></span>” is used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="to-chars"></a>3.292. to_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal"> +TCFL</code></span>”</p></div><p>
-Controls the character used to indicate mail addressed to you. The
-first character is the one used when the mail is <span class="emphasis"><em>not</em></span> addressed to your
-address. The second is used when you are the only
-recipient of the message. The third is when your address
-appears in the “<span class="quote">To:</span>” header field, but you are not the only recipient of
-the message. The fourth character is used when your
-address is specified in the “<span class="quote">Cc:</span>” header field, but you are not the only
-recipient. The fifth character is used to indicate mail that was sent
-by <span class="emphasis"><em>you</em></span>. The sixth character is used to indicate when a mail
-was sent to a mailing-list you subscribe to.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="trash"></a>3.293. trash</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-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.
-</p><p>
-NOTE: When you delete a message in the trash folder, it is really
-deleted, so that you have a way to clean the trash.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tunnel"></a>3.294. tunnel</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Setting this variable will cause mutt 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/SMTP server. Example:
-
-</p><pre class="screen">
-set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-
-</pre><p>
-Note: For this example to work you must be able to log in to the remote
-machine without having to enter a password.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-8bitmime"></a>3.295. use_8bitmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-<span class="bold"><strong>Warning:</strong></span> do not set this variable unless you are using a version
-of sendmail which supports the <code class="literal">-B8BITMIME</code> flag (such as sendmail
-8.8.x) or you may not be able to send mail.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will invoke <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a> with the <code class="literal">-B8BITMIME</code>
-flag when sending 8-bit messages to enable ESMTP negotiation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-domain"></a>3.296. use_domain</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will qualify all local addresses (ones without the
-“<span class="quote">@host</span>” portion) with the value of <a class="link" href="reference.html#hostname" title="3.80. hostname">$hostname</a>. If <span class="emphasis"><em>unset</em></span>, no
-addresses will be qualified.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-envelope-from"></a>3.297. use_envelope_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will set the <span class="emphasis"><em>envelope</em></span> sender of the message.
-If <a class="link" href="reference.html#envelope-from-address" title="3.53. envelope_from_address">$envelope_from_address</a> is <span class="emphasis"><em>set</em></span>, it will be used as the sender
-address. If <span class="emphasis"><em>unset</em></span>, mutt will attempt to derive the sender from the
-“<span class="quote">From:</span>” header.
-</p><p>
-Note that this information is passed to sendmail command using the
-<code class="literal">-f</code> command line switch. Therefore setting this option is not useful
-if the <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a> variable already contains <code class="literal">-f</code> or if the
-executable pointed to by <a class="link" href="reference.html#sendmail" title="3.260. sendmail">$sendmail</a> doesn't support the <code class="literal">-f</code> switch.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-from"></a>3.298. use_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will generate the “<span class="quote">From:</span>” header field when
-sending messages. If <span class="emphasis"><em>unset</em></span>, no “<span class="quote">From:</span>” header field will be
-generated unless the user explicitly sets one using the “<span class="quote"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-idn"></a>3.299. use_idn</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will show you international domain names decoded.
-Note: You can use IDNs for addresses even if this is <span class="emphasis"><em>unset</em></span>.
-This variable only affects decoding.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-ipv6"></a>3.300. use_ipv6</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will look for IPv6 addresses of hosts it tries to
-contact. If this option is <span class="emphasis"><em>unset</em></span>, Mutt will restrict itself to IPv4 addresses.
-Normally, the default should work.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="user-agent"></a>3.301. user_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will add a “<span class="quote">User-Agent:</span>” header to outgoing
-messages, indicating which version of mutt was used for composing
-them.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="visual"></a>3.302. visual</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Specifies the visual editor to invoke when the “<span class="quote"><code class="literal">˜v</code></span>” command is
-given in the builtin editor.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wait-key"></a>3.303. wait_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether Mutt will ask you to press a key after an external command
-has been invoked by these functions: <code class="literal"><shell-escape></code>,
-<code class="literal"><pipe-message></code>, <code class="literal"><pipe-entry></code>, <code class="literal"><print-message></code>,
-and <code class="literal"><print-entry></code> commands.
-</p><p>
-It is also used when viewing attachments with “<span class="quote"><a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a></span>”, provided
-that the corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag,
-and the external program is interactive.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will always ask for a key. When <span class="emphasis"><em>unset</em></span>, Mutt will wait
-for a key only if the external command returned a non-zero status.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="weed"></a>3.304. weed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will weed headers when displaying, forwarding,
-printing, or replying to messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap"></a>3.305. wrap</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-When set to a positive value, mutt will wrap text at <a class="link" href="reference.html#wrap" title="3.305. wrap">$wrap</a> characters.
-When set to a negative value, mutt will wrap text so that there are <a class="link" href="reference.html#wrap" title="3.305. wrap">$wrap</a>
-characters of empty space on the right side of the terminal.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap-search"></a>3.306. wrap_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether searches wrap around the end.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, searches will wrap around the first (or last) item. When
-<span class="emphasis"><em>unset</em></span>, incremental searches will not wrap.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrapmargin"></a>3.307. wrapmargin</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-(DEPRECATED) Equivalent to setting <a class="link" href="reference.html#wrap" title="3.305. wrap">$wrap</a> with a negative value.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-inc"></a>3.308. write_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-When writing a mailbox, a message will be printed every
-<a class="link" href="reference.html#write-inc" title="3.308. write_inc">$write_inc</a> messages to indicate progress. If set to 0, only a
-single message will be displayed before writing a mailbox.
-</p><p>
-Also see the <a class="link" href="reference.html#read-inc" title="3.238. read_inc">$read_inc</a>, <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="reference.html#time-inc" title="3.289. time_inc">$time_inc</a> variables and the
-“<span class="quote"><a class="link" href="tuning.html" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-bcc"></a>3.309. write_bcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether mutt writes out the “<span class="quote">Bcc:</span>” header when preparing
-messages to be sent. Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see <a class="link" href="reference.html#smtp-url" title="3.272. smtp_url">$smtp_url</a>), this
-option does nothing: mutt will never write out the “<span class="quote">Bcc:</span>” header
-in this case.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, exim4 and postfix strip BCC headers by
-default. The above warning applies to exim3 users, see /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-icon"></a>3.310. xterm_icon</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">M%?n?AIL&ail?</code></span>”</p></div><p>
-Controls the format of the icon title, as long as xterm_set_titles
-is enabled. This string is identical in formatting to the one used by
-“<span class="quote"><a class="link" href="reference.html#status-format" title="3.281. status_format">$status_format</a></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-set-titles"></a>3.311. xterm_set_titles</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether mutt sets the xterm title bar and icon name
-(as long as you are in an appropriate terminal).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-title"></a>3.312. xterm_title</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?</code></span>”</p></div><p>
-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 “<span class="quote"><a class="link" href="reference.html#status-format" title="3.281. status_format">$status_format</a></span>”.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="functions"></a>4. Functions</h2></div></div></div><p>
-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 <a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">bind</a>
-command.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="generic_map"></a>4.1. generic menu</h3></div></div></div><p>
-The <span class="emphasis"><em>generic</em></span> menu is not a real menu, but specifies common functions
-(such as movement) available in all menus except for <span class="emphasis"><em>pager</em></span> and
-<span class="emphasis"><em>editor</em></span>. Changing settings for this menu will affect the default
-bindings for all menus (except as noted).
-</p><div class="table"><a id="generic_table"></a><p class="title"><b>Table 8.2. Default generic function bindings</b></p><div class="table-contents"><table summary="Default generic function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><top-page></code></td><td>H</td><td>move to the top of the page</td></tr><tr><td><code class="literal"><next-entry></code></td><td>j</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>k</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><bottom-page></code></td><td>L</td><td>move to the bottom of the page</td></tr><tr><td><code class="literal"><refresh></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><middle-page></code></td><td>M</td><td>move to the middle of the page</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><tag-entry></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><next-page></code></td><td>z</td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>Z</td><td>move to the previous page</td></tr><tr><td><code class="literal"><last-entry></code></td><td>*</td><td>move to the last entry</td></tr><tr><td><code class="literal"><first-entry></code></td><td>=</td><td>move to the first entry</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><next-line></code></td><td>></td><td>scroll down one line</td></tr><tr><td><code class="literal"><previous-line></code></td><td><</td><td>scroll up one line</td></tr><tr><td><code class="literal"><half-up></code></td><td>[</td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td>]</td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><tag-prefix></code></td><td>;</td><td>apply next function to tagged messages</td></tr><tr><td><code class="literal"><tag-prefix-cond></code></td><td> </td><td>apply next function ONLY to tagged messages</td></tr><tr><td><code class="literal"><end-cond></code></td><td> </td><td>end of conditional execution (noop)</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><select-entry></code></td><td><Return></td><td>select the current entry</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><current-top></code></td><td> </td><td>move entry to top of screen</td></tr><tr><td><code class="literal"><current-middle></code></td><td> </td><td>move entry to middle of screen</td></tr><tr><td><code class="literal"><current-bottom></code></td><td> </td><td>move entry to bottom of screen</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index_map"></a>4.2. index menu</h3></div></div></div><div class="table"><a id="index_table"></a><p class="title"><b>Table 8.3. Default index function bindings</b></p><div class="table-contents"><table summary="Default index function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><collapse-thread></code></td><td>Esc v</td><td>collapse/uncollapse current thread</td></tr><tr><td><code class="literal"><collapse-all></code></td><td>Esc V</td><td>collapse/uncollapse all threads</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-pattern></code></td><td>D</td><td>delete messages matching a pattern</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><fetch-mail></code></td><td>G</td><td>retrieve mail from POP server</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><limit></code></td><td>l</td><td>show only messages matching a pattern</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><toggle-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><toggle-write></code></td><td>%</td><td>toggle whether the mailbox will be rewritten</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><quit></code></td><td>q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><show-limit></code></td><td>Esc l</td><td>show currently active limit pattern</td></tr><tr><td><code class="literal"><sort-mailbox></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><tag-pattern></code></td><td>T</td><td>tag messages matching a pattern</td></tr><tr><td><code class="literal"><tag-subthread></code></td><td> </td><td>tag the current subthread</td></tr><tr><td><code class="literal"><tag-thread></code></td><td>Esc t</td><td>tag the current thread</td></tr><tr><td><code class="literal"><untag-pattern></code></td><td>^T</td><td>untag messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-pattern></code></td><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><set-flag></code></td><td>w</td><td>set a status flag on a message</td></tr><tr><td><code class="literal"><clear-flag></code></td><td>W</td><td>clear a status flag from a message</td></tr><tr><td><code class="literal"><display-message></code></td><td><Return></td><td>display a message</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><next-new-then-unread></code></td><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-new-then-unread></code></td><td>Esc <Tab></td><td>jump to the previous new or unread message</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr><tr><td><code class="literal"><sidebar-scroll-up></code></td><td> </td><td>scroll the mailbox pane up 1 page</td></tr><tr><td><code class="literal"><sidebar-scroll-down></code></td><td> </td><td>scroll the mailbox pane down 1 page</td></tr><tr><td><code class="literal"><sidebar-next></code></td><td> </td><td>go down to next mailbox</td></tr><tr><td><code class="literal"><sidebar-prev></code></td><td> </td><td>go to previous mailbox</td></tr><tr><td><code class="literal"><sidebar-open></code></td><td> </td><td>open hilighted mailbox</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager_map"></a>4.3. pager menu</h3></div></div></div><div class="table"><a id="pager_table"></a><p class="title"><b>Table 8.4. Default pager function bindings</b></p><div class="table-contents"><table summary="Default pager function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><next-entry></code></td><td>J</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>K</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><redraw-screen></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><mark-as-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><quit></code></td><td>Q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><skip-quoted></code></td><td>S</td><td>skip beyond quoted text</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><tag-message></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><toggle-quoted></code></td><td>T</td><td>toggle display of quoted text</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><search-toggle></code></td><td>\\</td><td>toggle search pattern coloring</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><next-page></code></td><td><Space></td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>-</td><td>move to the previous page</td></tr><tr><td><code class="literal"><top></code></td><td>^</td><td>jump to the top of the message</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><next-line></code></td><td><Return></td><td>scroll down one line</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><half-up></code></td><td> </td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td> </td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><previous-line></code></td><td> </td><td>scroll up one line</td></tr><tr><td><code class="literal"><bottom></code></td><td> </td><td>jump to the bottom of the message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr><tr><td><code class="literal"><sidebar-scroll-up></code></td><td> </td><td>scroll the mailbox pane up 1 page</td></tr><tr><td><code class="literal"><sidebar-scroll-down></code></td><td> </td><td>scroll the mailbox pane down 1 page</td></tr><tr><td><code class="literal"><sidebar-next></code></td><td> </td><td>go down to next mailbox</td></tr><tr><td><code class="literal"><sidebar-prev></code></td><td> </td><td>go to previous mailbox</td></tr><tr><td><code class="literal"><sidebar-open></code></td><td> </td><td>open hilighted mailbox</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias_map"></a>4.4. alias menu</h3></div></div></div><div class="table"><a id="alias_table"></a><p class="title"><b>Table 8.5. Default alias function bindings</b></p><div class="table-contents"><table summary="Default alias function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query_map"></a>4.5. query menu</h3></div></div></div><div class="table"><a id="query_table"></a><p class="title"><b>Table 8.6. Default query function bindings</b></p><div class="table-contents"><table summary="Default query function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><query-append></code></td><td>A</td><td>append new query results to current results</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach_map"></a>4.6. attach menu</h3></div></div></div><div class="table"><a id="attach_table"></a><p class="title"><b>Table 8.7. Default attach function bindings</b></p><div class="table-contents"><table summary="Default attach function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><print-entry></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><save-entry></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><view-mailcap></code></td><td>m</td><td>force viewing of attachment using mailcap</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><view-text></code></td><td>T</td><td>view attachment as text</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><collapse-parts></code></td><td>v</td><td>Toggle display of subparts</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose_map"></a>4.7. compose menu</h3></div></div></div><div class="table"><a id="compose_table"></a><p class="title"><b>Table 8.8. Default compose function bindings</b></p><div class="table-contents"><table summary="Default compose function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><attach-file></code></td><td>a</td><td>attach file(s) to this message</td></tr><tr><td><code class="literal"><attach-message></code></td><td>A</td><td>attach message(s) to this message</td></tr><tr><td><code class="literal"><edit-bcc></code></td><td>b</td><td>edit the BCC list</td></tr><tr><td><code class="literal"><edit-cc></code></td><td>c</td><td>edit the CC list</td></tr><tr><td><code class="literal"><copy-file></code></td><td>C</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><detach-file></code></td><td>D</td><td>delete the current entry</td></tr><tr><td><code class="literal"><toggle-disposition></code></td><td>^D</td><td>toggle disposition between inline/attachment</td></tr><tr><td><code class="literal"><edit-description></code></td><td>d</td><td>edit attachment description</td></tr><tr><td><code class="literal"><edit-message></code></td><td>e</td><td>edit the message</td></tr><tr><td><code class="literal"><edit-headers></code></td><td>E</td><td>edit the message with headers</td></tr><tr><td><code class="literal"><edit-file></code></td><td>^X e</td><td>edit the file to be attached</td></tr><tr><td><code class="literal"><edit-encoding></code></td><td>^E</td><td>edit attachment transfer-encoding</td></tr><tr><td><code class="literal"><edit-from></code></td><td>Esc f</td><td>edit the from field</td></tr><tr><td><code class="literal"><edit-fcc></code></td><td>f</td><td>enter a file to save a copy of this message in</td></tr><tr><td><code class="literal"><filter-entry></code></td><td>F</td><td>filter attachment through a shell command</td></tr><tr><td><code class="literal"><get-attachment></code></td><td>G</td><td>get a temporary copy of an attachment</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><ispell></code></td><td>i</td><td>run ispell on the message</td></tr><tr><td><code class="literal"><print-entry></code></td><td>l</td><td>print the current entry</td></tr><tr><td><code class="literal"><edit-mime></code></td><td>m</td><td>edit attachment using mailcap entry</td></tr><tr><td><code class="literal"><new-mime></code></td><td>n</td><td>compose new attachment using mailcap entry</td></tr><tr><td><code class="literal"><postpone-message></code></td><td>P</td><td>save this message to send later</td></tr><tr><td><code class="literal"><edit-reply-to></code></td><td>r</td><td>edit the Reply-To field</td></tr><tr><td><code class="literal"><rename-file></code></td><td>R</td><td>rename/move an attached file</td></tr><tr><td><code class="literal"><edit-subject></code></td><td>s</td><td>edit the subject of this message</td></tr><tr><td><code class="literal"><edit-to></code></td><td>t</td><td>edit the TO list</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^T</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><write-fcc></code></td><td>w</td><td>write the message to a folder</td></tr><tr><td><code class="literal"><toggle-unlink></code></td><td>u</td><td>toggle whether to delete file after sending it</td></tr><tr><td><code class="literal"><toggle-recode></code></td><td> </td><td>toggle recoding of this attachment</td></tr><tr><td><code class="literal"><update-encoding></code></td><td>U</td><td>update an attachment's encoding info</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><send-message></code></td><td>y</td><td>send the message</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><attach-key></code></td><td>Esc k</td><td>attach a PGP public key</td></tr><tr><td><code class="literal"><pgp-menu></code></td><td>p</td><td>show PGP options</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><smime-menu></code></td><td>S</td><td>show S/MIME options</td></tr><tr><td><code class="literal"><mix></code></td><td>M</td><td>send the message through a mixmaster remailer chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone_map"></a>4.8. postpone menu</h3></div></div></div><div class="table"><a id="postpone_table"></a><p class="title"><b>Table 8.9. Default postpone function bindings</b></p><div class="table-contents"><table summary="Default postpone function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="browser_map"></a>4.9. browser menu</h3></div></div></div><div class="table"><a id="browser_table"></a><p class="title"><b>Table 8.10. Default browser function bindings</b></p><div class="table-contents"><table summary="Default browser function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><change-dir></code></td><td>c</td><td>change directories</td></tr><tr><td><code class="literal"><display-filename></code></td><td>@</td><td>display the currently selected file's name</td></tr><tr><td><code class="literal"><enter-mask></code></td><td>m</td><td>enter a file mask</td></tr><tr><td><code class="literal"><sort></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><select-new></code></td><td>N</td><td>select a new file in this directory</td></tr><tr><td><code class="literal"><check-new></code></td><td> </td><td>check mailboxes for new mail</td></tr><tr><td><code class="literal"><toggle-mailboxes></code></td><td><Tab></td><td>toggle whether to browse mailboxes or all files</td></tr><tr><td><code class="literal"><view-file></code></td><td><Space></td><td>view file</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><create-mailbox></code></td><td>C</td><td>create a new mailbox (IMAP only)</td></tr><tr><td><code class="literal"><delete-mailbox></code></td><td>d</td><td>delete the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><rename-mailbox></code></td><td>r</td><td>rename the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><subscribe></code></td><td>s</td><td>subscribe to current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><unsubscribe></code></td><td>u</td><td>unsubscribe from current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><toggle-subscribed></code></td><td>T</td><td>toggle view all/subscribed mailboxes (IMAP only)</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp_map"></a>4.10. pgp menu</h3></div></div></div><div class="table"><a id="pgp_table"></a><p class="title"><b>Table 8.11. Default pgp function bindings</b></p><div class="table-contents"><table summary="Default pgp function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime_map"></a>4.11. smime menu</h3></div></div></div><div class="table"><a id="smime_table"></a><p class="title"><b>Table 8.12. Default smime function bindings</b></p><div class="table-contents"><table summary="Default smime function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix_map"></a>4.12. mix menu</h3></div></div></div><div class="table"><a id="mix_table"></a><p class="title"><b>Table 8.13. Default mix function bindings</b></p><div class="table-contents"><table summary="Default mix function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><accept></code></td><td><Return></td><td>Accept the chain constructed</td></tr><tr><td><code class="literal"><append></code></td><td>a</td><td>Append a remailer to the chain</td></tr><tr><td><code class="literal"><insert></code></td><td>i</td><td>Insert a remailer into the chain</td></tr><tr><td><code class="literal"><delete></code></td><td>d</td><td>Delete a remailer from the chain</td></tr><tr><td><code class="literal"><chain-prev></code></td><td><Left></td><td>Select the previous element of the chain</td></tr><tr><td><code class="literal"><chain-next></code></td><td><Right></td><td>Select the next element of the chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor_map"></a>4.13. editor menu</h3></div></div></div><div class="table"><a id="editor_table"></a><p class="title"><b>Table 8.14. Default editor function bindings</b></p><div class="table-contents"><table summary="Default editor function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bol></code></td><td>^A</td><td>jump to the beginning of the line</td></tr><tr><td><code class="literal"><backward-char></code></td><td>^B</td><td>move the cursor one character to the left</td></tr><tr><td><code class="literal"><backward-word></code></td><td>Esc b</td><td>move the cursor to the beginning of the word</td></tr><tr><td><code class="literal"><capitalize-word></code></td><td>Esc c</td><td>capitalize the word</td></tr><tr><td><code class="literal"><downcase-word></code></td><td>Esc l</td><td>convert the word to lower case</td></tr><tr><td><code class="literal"><upcase-word></code></td><td>Esc u</td><td>convert the word to upper case</td></tr><tr><td><code class="literal"><delete-char></code></td><td>^D</td><td>delete the char under the cursor</td></tr><tr><td><code class="literal"><eol></code></td><td>^E</td><td>jump to the end of the line</td></tr><tr><td><code class="literal"><forward-char></code></td><td>^F</td><td>move the cursor one character to the right</td></tr><tr><td><code class="literal"><forward-word></code></td><td>Esc f</td><td>move the cursor to the end of the word</td></tr><tr><td><code class="literal"><backspace></code></td><td><Backspace></td><td>delete the char in front of the cursor</td></tr><tr><td><code class="literal"><kill-eol></code></td><td>^K</td><td>delete chars from cursor to end of line</td></tr><tr><td><code class="literal"><kill-eow></code></td><td>Esc d</td><td>delete chars from the cursor to the end of the word</td></tr><tr><td><code class="literal"><kill-line></code></td><td>^U</td><td>delete all chars on the line</td></tr><tr><td><code class="literal"><quote-char></code></td><td>^V</td><td>quote the next typed key</td></tr><tr><td><code class="literal"><kill-word></code></td><td>^W</td><td>delete the word in front of the cursor</td></tr><tr><td><code class="literal"><complete></code></td><td><Tab></td><td>complete filename or alias</td></tr><tr><td><code class="literal"><complete-query></code></td><td>^T</td><td>complete address with query</td></tr><tr><td><code class="literal"><buffy-cycle></code></td><td><Space></td><td>cycle among incoming mailboxes</td></tr><tr><td><code class="literal"><history-up></code></td><td> </td><td>scroll up through the history list</td></tr><tr><td><code class="literal"><history-down></code></td><td> </td><td>scroll down through the history list</td></tr><tr><td><code class="literal"><transpose-chars></code></td><td> </td><td>transpose character under cursor with previous</td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="tuning.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="miscellany.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 7. Performance tuning </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 9. Miscellany</td></tr></table></div></body></html>
+++ /dev/null
-.\" -*-nroff-*-
-.\"
-.\"
-.\" Copyright (C) 2009 Antonio Radici <antonio@dyne.org>
-.\"
-.\" This program is free software; you can redistribute it and/or modify
-.\" it under the terms of the GNU General Public License as published by
-.\" the Free Software Foundation; either version 2 of the License, or
-.\" (at your option) any later version.
-.\"
-.\" This program is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-.\"
-.TH smime_keys 1 "May 2009" Unix "User Manuals"
-.SH "NAME"
-smime_keys \- Utility to add S/MIME certificate to the internal database used by mutt
-.SH SYNOPSIS
-.PP
-.B smime_keys
-<operation> [file(s) | keyID [file(s)]]
-.SH "DESCRIPTION"
-The purpose of this tool is to manipulate the internal database of S/MIME certificates
-used by mutt to sign mail messages which will be sent or to verify mail messages received
-and signed with S/MIME
-.SH OPTIONS
-.PP
-.IP \fBinit\fP
-no files needed, inits directory structure.
-.IP \fBlist\fP
-lists the certificates stored in database.
-.IP \fBlabel\fP
-keyID required. changes/removes/adds label.
-.IP \fBremove\fP
-keyID required.
-.IP \fBverify\fP
-1=keyID and optionally 2=CRL
-Verifies the certificate chain, and optionally wether
-this certificate is included in supplied CRL (PEM format).
-Note: to verify all certificates at the same time,
-replace keyID with "all"
-.IP \fBadd_cert\fP
-certificate required.
-.IP \fBadd_chain\fP
-three files reqd: 1=Key, 2=certificate
-plus 3=intermediate certificate(s).
-.IP \fBadd_p12\fP
-one file reqd. Adds keypair to database.
-file is PKCS12 (e.g. export from netscape).
-.IP \fBadd_pem\fP
-one file reqd. Adds keypair to database.
-(file was converted from e.g. PKCS12).
-.IP \fBadd_root\fP
-one file reqd. Adds PEM root certificate to the location
-specified within muttrc (smime_verify_* command)
-.SH NO WARRANTIES
-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.
-.PP
-Mutt Home Page: http://www.mutt.org/
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. Performance tuning</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="optionalfeatures.html" title="Chapter 6. Optional features" /><link rel="next" href="reference.html" title="Chapter 8. Reference" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 7. Performance tuning</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="optionalfeatures.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="reference.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="tuning"></a>Chapter 7. Performance tuning</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="tuning.html#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="tuning.html#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="tuning.html#tuning-search">3. Searching and limiting</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-mailboxes"></a>1. Reading and writing mailboxes</h2></div></div></div><p>
-Mutt's performance when reading mailboxes can be improved in two ways:
-</p><div class="orderedlist"><ol type="1"><li><p>
-For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
-performance can be greatly improved using
-<a class="link" href="optionalfeatures.html#header-caching" title="7.1. Header caching">header caching</a>.
-Using a single database per folder may further increase
-performance.
-</p></li><li><p>
-Mutt provides the <a class="link" href="reference.html#read-inc" title="3.238. read_inc">$read_inc</a>
-and <a class="link" href="reference.html#write-inc" title="3.308. write_inc">$write_inc</a>
-variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
-time on updating the progress counter than it spends on
-actually reading/writing folders.
-</p><p>
-For example, when opening a maildir folder with a few
-thousand messages, the default value for
-<a class="link" href="reference.html#read-inc" title="3.238. read_inc">$read_inc</a>
-may be too low. It can be tuned on on a folder-basis using
-<a class="link" href="configuration.html#folder-hook" title="7. Setting variables based upon mailbox">folder-hooks</a>:
-</p><pre class="screen">
-# use very high $read_inc to speed up reading hcache'd maildirs
-folder-hook . 'set read_inc=1000'
-# use lower value for reading slower remote IMAP folders
-folder-hook ^imap 'set read_inc=100'
-# use even lower value for reading even slower remote POP folders
-folder-hook ^pop 'set read_inc=1'</pre></li></ol></div><p>These settings work on a per-message basis. However, as messages may
-greatly differ in size and certain operations are much faster than others,
-even per-folder settings of the increment variables may not be
-desirable as they produce either too few or too much progress updates.
-Thus, Mutt allows to limit the number of progress updates per second it'll
-actually send to the terminal using the
-<a class="link" href="reference.html#time-inc" title="3.289. time_inc">$time_inc</a> variable.</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-messages"></a>2. Reading messages from remote folders</h2></div></div></div><p>
-Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
-limited number of recently viewed messages (usually 10) per
-session (so that it will be gone for the next session.)
-</p><p>
-To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
-<a class="link" href="optionalfeatures.html#body-caching" title="7.2. Body caching">body caching</a> for details.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-search"></a>3. Searching and limiting</h2></div></div></div><p>
-When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
-searches. For regular expressions, patterns are prefixed with
-“<span class="quote">˜</span>” and with “<span class="quote">=</span>” for string searches.
-</p><p>
-Even though a regular expression search is fast, it's several times
-slower than a pure string search which is noticeable especially on large
-folders. As a consequence, a string search should be used instead of a
-regular expression search if the user already knows enough about the
-search pattern.
-</p><p>
-For example, when limiting a large folder to all messages sent to or by
-an author, it's much faster to search for the initial part of an e-mail
-address via <code class="literal">=Luser@</code> instead of
-<code class="literal">˜Luser@</code>. This is especially true for searching
-message bodies since a larger amount of input has to be searched.
-</p><p>
-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="optionalfeatures.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="reference.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 6. Optional features </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 8. Reference</td></tr></table></div></body></html>
+++ /dev/null
-#!/bin/sh
-
-#
-# File a bug against the Mutt mail user agent.
-#
-
-#
-# $Id$
-#
-
-#
-# Copyright (c) 2000 Thomas Roessler <roessler@does-not-exist.org>
-#
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-#
-
-SUBMIT="fleas@mutt.org"
-DEBIAN_SUBMIT="submit@bugs.debian.org"
-
-prefix=/usr
-
-DEBUGGER=/usr/bin/gdb
-SENDMAIL=/usr/sbin/sendmail
-sysconfdir=/etc
-pkgdatadir=@pkgdatadir@
-
-include_file ()
-{
- echo
- echo "--- Begin $1"
- sed -e '/^[ ]*#/d; /^[ ]*$/d; s/^-/- -/' $1
- echo "--- End $1"
- echo
-}
-
-debug_gdb ()
-{
- cat << EOF > $SCRATCH/gdb.rc
-bt
-list
-quit
-EOF
- $DEBUGGER -n -x $SCRATCH/gdb.rc -c $CORE mutt
-}
-
-debug_dbx ()
-{
- cat << EOF > $SCRATCH/dbx.rc
-where
-list
-quit
-EOF
- $DEBUGGER -s $SCRATCH/dbx.rc mutt $CORE
-}
-
-debug_sdb ()
-{
- cat << EOF > $SCRATCH/sdb.rc
-t
-w
-q
-EOF
- $DEBUGGER mutt $CORE < $SCRATCH/sdb.rc
-}
-
-case `echo -n` in
-"") n=-n; c= ;;
- *) n=; c='\c' ;;
-esac
-
-
-exec > /dev/tty
-exec < /dev/tty
-
-SCRATCH=${TMPDIR-/tmp}/`basename $0`.`hostname`.$$
-
-mkdir ${SCRATCH} || \
-{
- echo "`basename $0`: Can't create temporary directory." >& 2 ;
- exit 1 ;
-}
-
-trap "rm -r -f ${SCRATCH} ; trap '' 0 ; exit" 0 1 2
-
-TEMPLATE=${SCRATCH}/template.txt
-
-if test -z "$EMAIL" ; then
- EMAIL="`mutt -Q from 2> /dev/null | sed -e 's/^from=.\(.*\).$/\1/'`"
-fi
-
-EMAILTMP=''
-while test -z "$EMAILTMP"
-do
- echo "Please enter your e-mail address [$EMAIL]:"
- echo $n "> $c"
- read EMAILTMP
-
- if test -z "$EMAILTMP"; then EMAILTMP="$EMAIL"; fi
-
- if ! echo "$EMAILTMP" | grep -q @
- then
- echo "$EMAILTMP does not appear to be a valid email address"
- EMAILTMP=''
- continue
- fi
-
- EMAIL="$EMAILTMP"
-done
-
-echo "Please enter a one-line description of the problem you experience:"
-echo $n "> $c"
-read SUBJECT
-
-cat <<EOF
-What should the severity for this bug report be?
-
- 0) Feature request, or maybe a bug which is very difficult to
- fix due to major design considerations.
-
- 1) The package fails to perform correctly in some conditions,
- or on some systems, or fails to comply with current policy
- documents. Most bugs are in this category.
-
- 2) This bug makes this version of the package unsuitable for
- a stable release.
-
- 3) Dangerous bug. Makes the package in question unusable by
- anyone or mostly so, or causes data loss, or introduces a
- security hole allowing access to the accounts of users who
- use the package.
-
- 4) Critical bug. Makes unrelated software on the system (or
- the whole system) break, or causes serious data loss, or
- introduces a security hole on systems where you install the
- package.
-
-EOF
-echo $n "Severity? [01234] $c"
-read severity
-case "$severity" in
-0|[Ww]) severity=wishlist ;;
-2|[Ii]) severity=important ;;
-3|[Gg]) severity=grave ;;
-4|[Cc]) severity=critical ;;
- *) severity=normal ;;
-esac
-
-if test -x $DEBUGGER ; then
- test -f core && CORE=core
- echo "If mutt has crashed, it may have saved some program state in"
- echo "a file named core. We can include this information with the bug"
- echo "report if you wish so."
- echo "Do you want to include information gathered from a core file?"
- echo "If yes, please enter the path - otherwise just say no: [$CORE]"
- echo $n "> $c"
- read _CORE
- test "$_CORE" && CORE="$_CORE"
-fi
-
-echo $n "Do you want to include your personal mutt configuration files? [Y|n] $c"
-read personal
-case "$personal" in
-[nN]*) personal=no ;;
- *) personal=yes ;;
-esac
-
-echo $n "Do you want to include your system's global mutt configuration file? [Y|n] $c"
-read global
-case "$global" in
-[nN]*) global=no ;;
- *) global=yes ;;
-esac
-
-if test -f /etc/debian_version ; then
- DEBIAN=yes
- echo $n "Checking whether mutt has been installed as a package... $c"
- DEBIANVERSION="`dpkg -l mutt | grep '^[ih]' | awk '{print $3}'`" 2> /dev/null
- if test "$DEBIANVERSION" ; then
- DPKG=yes
- else
- DPKG=no
- unset DEBIANVERSION
- fi
- echo "$DPKG"
- echo $n "File this bug with Debian? [Y|n] $c"
- read DPKG
- case "$DPKG" in
- [nN]) DPKG=no ;;
- *) DPKG=yes ;;
- esac
-else
- DEBIAN=no
- DPKG=no
-fi
-
-if rpm -q mutt > /dev/null 2> /dev/null ; then
- echo "Mutt seems to come from an RPM package."
- RPMVERSION="`rpm -q mutt`"
- RPMPACKAGER="`rpm -q -i mutt | sed -n -e 's/^Packager *: *//p'`"
-fi
-
-MUTTVERSION="`mutt -v | awk '{print $2; exit; }'`"
-test "$DPKG" = "yes" && SUBMIT="$SUBMIT, $DEBIAN_SUBMIT"
-
-exec > ${TEMPLATE}
-
-test "$EMAIL" && echo "From: $EMAIL"
-test "$REPLYTO" && echo "Reply-To: $REPLYTO"
-test "$ORGANIZATION" && echo "Organization: $ORGANIZATION"
-
-echo "Subject: mutt-$MUTTVERSION: $SUBJECT"
-echo "To: $SUBMIT"
-test "$EMAIL" && echo "Bcc: ${EMAIL}"
-echo
-echo "Package: mutt"
-echo "Version: ${DEBIANVERSION-${RPMVERSION-$MUTTVERSION}}"
-echo "Severity: $severity"
-echo
-echo "-- Please type your report below this line"
-echo
-echo
-echo
-
-if test "$DEBIAN" = "yes" ; then
- echo "Obtaining Debian-specific information..." > /dev/tty
- bug -p -s dummy mutt < /dev/null 2> /dev/null | \
- sed -n -e "/^-- System Information/,/^---/p" | \
- grep -v '^---'
-else
- echo "-- System Information"
- echo "System Version: `uname -a`"
- test -z "$RPMPACKAGER" || echo "RPM Packager: $RPMPACKAGER";
- test -f /etc/redhat-release && echo "RedHat Release: `cat /etc/redhat-release`"
- test -f /etc/SuSE-release && echo "SuSE Release: `sed 1q /etc/SuSE-release`"
- # Please provide more of these if you have any.
-fi
-
-echo
-echo "-- Build environment information"
-echo
-echo "(Note: This is the build environment installed on the system"
-echo "muttbug is run on. Information may or may not match the environment"
-echo "used to build mutt.)"
-echo
-echo "- gcc version information"
-echo "gcc"
-gcc -v 2>&1
-echo
-echo "- CFLAGS"
-echo -Wall -pedantic -Wno-long-long -Wall -g -O2
-
-
-echo
-echo "-- Mutt Version Information"
-echo
-LC_ALL=C mutt -v
-
-if test "$CORE" && test -f "$CORE" ; then
- echo
- echo "-- Core Dump Analysis Output"
- echo
-
- case "$DEBUGGER" in
- *sdb) debug_sdb $CORE ;;
- *dbx) debug_dbx $CORE ;;
- *gdb) debug_gdb $CORE ;;
- esac
-
- echo
-fi
-
-if test "$personal" = "yes" ; then
- CANDIDATES=".muttrc-${MUTTVERSION} .muttrc .mutt/muttrc-${MUTTVERSION} .mutt/muttrc"
- MATCHED="none"
- for f in $CANDIDATES; do
- if test -f "${HOME}/$f" ; then
- MATCHED="${HOME}/$f"
- break
- fi
- done
-
- if test "$MATCHED" = "none" ; then
- echo "Warning: Can't find your personal .muttrc." >&2
- else
- include_file $MATCHED
- fi
-fi
-
-
-if test "$global" = "yes" ; then
- CANDIDATES="Muttrc-${MUTTVERSION} Muttrc"
- DIRECTORIES="$sysconfdir $pkgdatadir"
- MATCHED="none"
- for d in $DIRECTORIES ; do
- for f in $CANDIDATES; do
- if test -f $d/$f ; then
- MATCHED="$d/$f"
- break
- fi
- done
- test "$MATCHED" = "none" || break
- done
-
- if test "$MATCHED" = "none" ; then
- echo "Warning: Can't find global Muttrc." >&2
- else
- include_file $MATCHED
- fi
-fi
-
-exec > /dev/tty
-
-cp $TEMPLATE $SCRATCH/mutt-bug.txt
-
-input="e"
-while : ; do
- if test "$input" = "e" ; then
- ${VISUAL-${EDITOR-vi}} $SCRATCH/mutt-bug.txt
- if cmp $SCRATCH/mutt-bug.txt ${TEMPLATE} > /dev/null ; then
- echo "Warning: Bug report was not modified!"
- fi
- fi
-
- echo $n "Submit, Edit, View, Quit? [S|e|v|q] $c"
- read _input
- input="`echo $_input | tr EVSQ evsq`"
- case $input in
- e*) ;;
- v*) ${PAGER-more} $SCRATCH/mutt-bug.txt ;;
- s*|"") $SENDMAIL -t < $SCRATCH/mutt-bug.txt ; exit ;;
- q*) exit
- esac
-done
-
+++ /dev/null
-#!/bin/sh
-
-BASEVERSION=2
-
-cleanstruct () {
- echo "$1" | sed -e 's/} *//' -e 's/;$//'
-}
-
-cleanbody () {
- echo "$1" | sed -e 's/{ *//'
-}
-
-getstruct () {
- STRUCT=""
- BODY=''
- inbody=0
- case "$1" in
- *'{') inbody=1 ;;
- *';') return ;;
- esac
-
- while read line
- do
- if test $inbody -eq 0
- then
- case "$line" in
- '{'*) inbody=1 ;;
- *';') return ;;
- esac
- fi
-
- case "$line" in
- '} '*)
- STRUCT=`cleanstruct "$line"`
- break
- ;;
- '}')
- read line
- STRUCT=`cleanstruct "$line"`
- break
- ;;
- '#'*) continue ;;
- *)
- if test $inbody -ne 0
- then
- BODY="$BODY $line"
- fi
- ;;
- esac
- done
-
- case $STRUCT in
- ADDRESS|LIST|BUFFER|PARAMETER|BODY|ENVELOPE|HEADER)
- BODY=`cleanbody "$BODY"`
- echo "$STRUCT: $BODY"
- ;;
- esac
- return
-}
-
-DEST="$1"
-TMPD="$DEST.tmp"
-
-TEXT="$BASEVERSION"
-
-echo "/* base version: $BASEVERSION" > $TMPD
-while read line
-do
- case "$line" in
- 'typedef struct'*)
- STRUCT=`getstruct "$line"`
- if test -n "$STRUCT"
- then
- NAME=`echo $STRUCT | cut -d: -f1`
- BODY=`echo $STRUCT | cut -d' ' -f2-`
- echo " * $NAME:" $BODY >> $TMPD
- TEXT="$TEXT $NAME {$BODY}"
- fi
- ;;
- esac
-done
-echo " */" >> $TMPD
-
-MD5TEXT=`echo "$TEXT" | ./mutt_md5`
-echo "#define HCACHEVER 0x"`echo $MD5TEXT | cut -c-8` >> $TMPD
-
-# TODO: validate we have all structs
-
-mv $TMPD $DEST
+++ /dev/null
-/* base version: 2
- * ADDRESS: char *personal; char *mailbox; int group; struct address_t *next; unsigned is_idn : 1; unsigned idn_checked : 1;
- * BUFFER: char *data; char *dptr; size_t dsize; int destroy;
- * LIST: char *data; struct list_t *next;
- * ENVELOPE: ADDRESS *return_path; ADDRESS *from; ADDRESS *to; ADDRESS *cc; ADDRESS *bcc; ADDRESS *sender; ADDRESS *reply_to; ADDRESS *mail_followup_to; char *list_post; char *subject; char *real_subj; char *message_id; char *supersedes; char *date; char *x_label; BUFFER *spam; LIST *references; LIST *in_reply_to; LIST *userhdrs; unsigned int irt_changed : 1; unsigned int refs_changed : 1;
- * PARAMETER: char *attribute; char *value; struct parameter *next;
- * BODY: char *xtype; char *subtype; PARAMETER *parameter; char *description; char *form_name; long hdr_offset; off_t offset; off_t length; char *filename; char *d_filename; char *charset; CONTENT *content; struct body *next; struct body *parts; struct header *hdr; struct attachptr *aptr; signed short attach_count; time_t stamp; unsigned int type : 4; unsigned int encoding : 3; unsigned int disposition : 2; unsigned int use_disp : 1; unsigned int unlink : 1; unsigned int tagged : 1; unsigned int deleted : 1; unsigned int noconv : 1; unsigned int force_charset : 1; unsigned int is_signed_data : 1; unsigned int goodsig : 1; unsigned int warnsig : 1; unsigned int badsig : 1; unsigned int collapsed : 1; unsigned int attach_qualifies : 1;
- * HEADER: unsigned int security : 11; unsigned int mime : 1; unsigned int flagged : 1; unsigned int tagged : 1; unsigned int appended : 1; unsigned int purged : 1; unsigned int deleted : 1; unsigned int changed : 1; unsigned int attach_del : 1; unsigned int old : 1; unsigned int read : 1; unsigned int expired : 1; unsigned int superseded : 1; unsigned int replied : 1; unsigned int subject_changed : 1; unsigned int threaded : 1; unsigned int display_subject : 1; unsigned int recip_valid : 1; unsigned int active : 1; unsigned int trash : 1; unsigned int zhours : 5; unsigned int zminutes : 6; unsigned int zoccident : 1; unsigned int searched : 1; unsigned int matched : 1; unsigned int attach_valid : 1; unsigned int collapsed : 1; unsigned int limited : 1; size_t num_hidden; short recipient; int pair; time_t date_sent; time_t received; off_t offset; int lines; int index; int msgno; int virtual; int score; ENVELOPE *env; BODY *content; char *path; char *tree; struct thread *thread; short attach_total; LIST *chain; int refno; void *data; char *maildir_flags;
- */
-#define HCACHEVER 0xafe521b0
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# imap/Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-
-
-VPATH = ../../imap
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-subdir = imap
-DIST_COMMON = README $(noinst_HEADERS) $(srcdir)/Makefile.am \
- $(srcdir)/Makefile.in TODO
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES =
-LIBRARIES = $(noinst_LIBRARIES)
-ARFLAGS = cru
-libimap_a_AR = $(AR) $(ARFLAGS)
-libimap_a_LIBADD =
-am__libimap_a_SOURCES_DIST = auth.c auth_login.c browse.c command.c \
- imap.c imap.h message.c utf7.c util.c auth_anon.c auth_cram.c \
- auth_sasl.c auth_gss.c
-#am__objects_1 = auth_anon.$(OBJEXT) \
-# auth_cram.$(OBJEXT)
-am__objects_1 = auth_sasl.$(OBJEXT)
-am__objects_2 = auth_gss.$(OBJEXT)
-am_libimap_a_OBJECTS = auth.$(OBJEXT) auth_login.$(OBJEXT) \
- browse.$(OBJEXT) command.$(OBJEXT) imap.$(OBJEXT) \
- message.$(OBJEXT) utf7.$(OBJEXT) util.$(OBJEXT) \
- $(am__objects_1) $(am__objects_2)
-libimap_a_OBJECTS = $(am_libimap_a_OBJECTS)
-DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)
-depcomp = $(SHELL) $(top_srcdir)/depcomp
-am__depfiles_maybe = depfiles
-COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
- $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
-CCLD = $(CC)
-LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
-SOURCES = $(libimap_a_SOURCES)
-DIST_SOURCES = $(am__libimap_a_SOURCES_DIST)
-HEADERS = $(noinst_HEADERS)
-ETAGS = etags
-CTAGS = ctags
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DHAVE_CONFIG_H
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/imap
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/../imap
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ../../imap
-sysconfdir = /etc
-target_alias =
-top_build_prefix = ../
-top_builddir = ..
-top_srcdir = ../..
-AUTOMAKE_OPTIONS = 1.6 foreign
-GSSSOURCES = auth_gss.c
-#AUTHENTICATORS = auth_anon.c auth_cram.c
-AUTHENTICATORS = auth_sasl.c
-EXTRA_DIST = README TODO auth_anon.c auth_cram.c auth_gss.c auth_sasl.c
-AM_CPPFLAGS = -I$(top_srcdir) -I../intl
-noinst_LIBRARIES = libimap.a
-noinst_HEADERS = auth.h imap_private.h message.h
-libimap_a_SOURCES = auth.c auth_login.c browse.c command.c imap.c imap.h \
- message.c utf7.c util.c $(AUTHENTICATORS) $(GSSSOURCES)
-
-all: all-am
-
-.SUFFIXES:
-.SUFFIXES: .c .o .obj
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign imap/Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --foreign imap/Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-clean-noinstLIBRARIES:
- -test -z "$(noinst_LIBRARIES)" || rm -f $(noinst_LIBRARIES)
-libimap.a: $(libimap_a_OBJECTS) $(libimap_a_DEPENDENCIES)
- -rm -f libimap.a
- $(libimap_a_AR) libimap.a $(libimap_a_OBJECTS) $(libimap_a_LIBADD)
- $(RANLIB) libimap.a
-
-mostlyclean-compile:
- -rm -f *.$(OBJEXT)
-
-distclean-compile:
- -rm -f *.tab.c
-
-#include ./$(DEPDIR)/auth.Po
-#include ./$(DEPDIR)/auth_anon.Po
-#include ./$(DEPDIR)/auth_cram.Po
-#include ./$(DEPDIR)/auth_gss.Po
-#include ./$(DEPDIR)/auth_login.Po
-#include ./$(DEPDIR)/auth_sasl.Po
-#include ./$(DEPDIR)/browse.Po
-#include ./$(DEPDIR)/command.Po
-#include ./$(DEPDIR)/imap.Po
-#include ./$(DEPDIR)/message.Po
-#include ./$(DEPDIR)/utf7.Po
-#include ./$(DEPDIR)/util.Po
-
-.c.o:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c $<
-
-.c.obj:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'`
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c `$(CYGPATH_W) '$<'`
-
-ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- mkid -fID $$unique
-tags: TAGS
-
-TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- here=`pwd`; \
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
- test -n "$$unique" || unique=$$empty_fix; \
- $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
- $$tags $$unique; \
- fi
-ctags: CTAGS
-CTAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- test -z "$(CTAGS_ARGS)$$tags$$unique" \
- || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
- $$tags $$unique
-
-GTAGS:
- here=`$(am__cd) $(top_builddir) && pwd` \
- && cd $(top_srcdir) \
- && gtags -i $(GTAGS_ARGS) $$here
-
-distclean-tags:
- -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
-distdir: $(DISTFILES)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
-check-am: all-am
-check: check-am
-all-am: Makefile $(LIBRARIES) $(HEADERS)
-installdirs:
-install: install-am
-install-exec: install-exec-am
-install-data: install-data-am
-uninstall: uninstall-am
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-am
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
-clean: clean-am
-
-clean-am: clean-generic clean-noinstLIBRARIES mostlyclean-am
-
-distclean: distclean-am
- -rm -rf ./$(DEPDIR)
- -rm -f Makefile
-distclean-am: clean-am distclean-compile distclean-generic \
- distclean-tags
-
-dvi: dvi-am
-
-dvi-am:
-
-html: html-am
-
-info: info-am
-
-info-am:
-
-install-data-am:
-
-install-dvi: install-dvi-am
-
-install-exec-am:
-
-install-html: install-html-am
-
-install-info: install-info-am
-
-install-man:
-
-install-pdf: install-pdf-am
-
-install-ps: install-ps-am
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-am
- -rm -rf ./$(DEPDIR)
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-am
-
-mostlyclean-am: mostlyclean-compile mostlyclean-generic
-
-pdf: pdf-am
-
-pdf-am:
-
-ps: ps-am
-
-ps-am:
-
-uninstall-am:
-
-.MAKE: install-am install-strip
-
-.PHONY: CTAGS GTAGS all all-am check check-am clean clean-generic \
- clean-noinstLIBRARIES ctags distclean distclean-compile \
- distclean-generic distclean-tags distdir dvi dvi-am html \
- html-am info info-am install install-am install-data \
- install-data-am install-dvi install-dvi-am install-exec \
- install-exec-am install-html install-html-am install-info \
- install-info-am install-man install-pdf install-pdf-am \
- install-ps install-ps-am install-strip installcheck \
- installcheck-am installdirs maintainer-clean \
- maintainer-clean-generic mostlyclean mostlyclean-compile \
- mostlyclean-generic pdf pdf-am ps ps-am tags uninstall \
- uninstall-am
-
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-# Makefile for directory with message catalog handling in GNU NLS Utilities.
-# Copyright (C) 1995-1998, 2000, 2001 Free Software Foundation, Inc.
-#
-# This program is free software; you can redistribute it and/or modify it
-# under the terms of the GNU Library General Public License as published
-# by the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-# Library General Public License for more details.
-#
-# You should have received a copy of the GNU Library 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.
-
-PACKAGE = mutt
-VERSION = 1.5.19
-
-SHELL = /bin/sh
-
-srcdir = ../../intl
-top_srcdir = ../..
-top_builddir = ..
-VPATH = ../../intl
-
-prefix = /usr
-exec_prefix = ${prefix}
-transform = s,x,x,
-libdir = ${exec_prefix}/lib
-includedir = ${prefix}/include
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-localedir = $(datadir)/locale
-gettextsrcdir = $(datadir)/gettext/intl
-aliaspath = $(localedir)
-subdir = intl
-
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-MKINSTALLDIRS = ../mkinstalldirs
-mkinstalldirs = $(SHELL) `case "$(MKINSTALLDIRS)" in /*) echo "$(MKINSTALLDIRS)" ;; *) echo "$(top_builddir)/$(MKINSTALLDIRS)" ;; esac`
-
-l =
-
-AR = ar
-CC = gcc
-LIBTOOL = @LIBTOOL@
-RANLIB = ranlib
-YACC = bison -y -d
-YFLAGS = --name-prefix=__gettext
-
-DEFS = -DLOCALEDIR=\"$(localedir)\" -DLOCALE_ALIAS_PATH=\"$(aliaspath)\" \
--DLIBDIR=\"$(libdir)\" -DHAVE_CONFIG_H
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-LDFLAGS = -L/lib
-
-COMPILE = $(CC) -c $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $(XCFLAGS)
-
-HEADERS = $(COMHDRS) libgnuintl.h libgettext.h loadinfo.h
-COMHDRS = gettext.h gettextP.h hash-string.h
-SOURCES = $(COMSRCS) intl-compat.c
-COMSRCS = bindtextdom.c dcgettext.c dgettext.c gettext.c \
-finddomain.c loadmsgcat.c localealias.c textdomain.c l10nflist.c \
-explodename.c dcigettext.c dcngettext.c dngettext.c ngettext.c plural.y \
-localcharset.c
-OBJECTS = bindtextdom.$lo dcgettext.$lo dgettext.$lo gettext.$lo \
-finddomain.$lo loadmsgcat.$lo localealias.$lo textdomain.$lo l10nflist.$lo \
-explodename.$lo dcigettext.$lo dcngettext.$lo dngettext.$lo ngettext.$lo \
-plural.$lo localcharset.$lo
-GETTOBJS = intl-compat.$lo
-DISTFILES.common = Makefile.in \
-config.charset locale.alias ref-add.sin ref-del.sin $(HEADERS) $(SOURCES)
-DISTFILES.generated = plural.c
-DISTFILES.normal = VERSION
-DISTFILES.gettext = COPYING.LIB-2 COPYING.LIB-2.1 libintl.glibc
-DISTFILES.obsolete = xopen-msg.sed linux-msg.sed po2tbl.sed.in cat-compat.c
-
-# Libtool's library version information for libintl.
-# Before making a gettext release, the gettext maintainer must change this
-# according to the libtool documentation, section "Library interface versions".
-# Maintainers of other packages that include the intl directory must *not*
-# change these values.
-LTV_CURRENT=1
-LTV_REVISION=1
-LTV_AGE=0
-
-.SUFFIXES:
-.SUFFIXES: .c .y .o .lo .sin .sed
-.c.o:
- $(COMPILE) $<
-.c.lo:
- $(LIBTOOL) --mode=compile $(COMPILE) $<
-
-.y.c:
- $(YACC) $(YFLAGS) --output $@ $<
- rm -f $*.h
-
-.sin.sed:
- sed -e '/^#/d' -e 's/@''PACKAGE''@/mutt/g' $< > t-$@
- mv t-$@ $@
-
-INCLUDES = -I.. -I. -I$(top_srcdir)/intl
-
-all: all-no
-all-yes: libintl.$la libintl.h charset.alias ref-add.sed ref-del.sed
-all-no: all-no-no
-all-no-yes: libgnuintl.$la
-all-no-no:
-
-libintl.a libgnuintl.a: $(OBJECTS)
- rm -f $@
- $(AR) cru $@ $(OBJECTS)
- $(RANLIB) $@
-
-libintl.la libgnuintl.la: $(OBJECTS)
- $(LIBTOOL) --mode=link \
- $(CC) $(CPPFLAGS) $(CFLAGS) $(XCFLAGS) $(LDFLAGS) -o $@ \
- $(OBJECTS) \
- -version-info $(LTV_CURRENT):$(LTV_REVISION):$(LTV_AGE) \
- -rpath $(libdir) \
- -no-undefined
-
-libintl.h: libgnuintl.h
- cp $(srcdir)/libgnuintl.h libintl.h
-
-charset.alias: config.charset
- $(SHELL) $(srcdir)/config.charset 'i486-pc-linux-gnu' > t-$@
- mv t-$@ $@
-
-check: all
-
-# This installation goal is only used in GNU gettext. Packages which
-# only use the library should use install instead.
-
-# We must not install the libintl.h/libintl.a files if we are on a
-# system which has the GNU gettext() function in its C library or in a
-# separate library.
-# If you want to use the one which comes with this version of the
-# package, you have to use `configure --with-included-gettext'.
-install: install-exec install-data
-install-exec: all
- if test "$(PACKAGE)" = "gettext" \
- && test '' = '$(GETTOBJS)'; then \
- $(mkinstalldirs) $(DESTDIR)$(libdir) $(DESTDIR)$(includedir); \
- $(INSTALL_DATA) libintl.h $(DESTDIR)$(includedir)/libintl.h; \
- $(LIBTOOL) --mode=install \
- $(INSTALL_DATA) libintl.$la $(DESTDIR)$(libdir)/libintl.$la; \
- else \
- : ; \
- fi
- if test 'no' = yes; then \
- $(mkinstalldirs) $(DESTDIR)$(libdir); \
- temp=$(DESTDIR)$(libdir)/t-charset.alias; \
- dest=$(DESTDIR)$(libdir)/charset.alias; \
- if test -f $(DESTDIR)$(libdir)/charset.alias; then \
- orig=$(DESTDIR)$(libdir)/charset.alias; \
- sed -f ref-add.sed $$orig > $$temp; \
- $(INSTALL_DATA) $$temp $$dest; \
- rm -f $$temp; \
- else \
- if test yes = no; then \
- orig=charset.alias; \
- sed -f ref-add.sed $$orig > $$temp; \
- $(INSTALL_DATA) $$temp $$dest; \
- rm -f $$temp; \
- fi; \
- fi; \
- $(mkinstalldirs) $(DESTDIR)$(localedir); \
- test -f $(DESTDIR)$(localedir)/locale.alias \
- && orig=$(DESTDIR)$(localedir)/locale.alias \
- || orig=$(srcdir)/locale.alias; \
- temp=$(DESTDIR)$(localedir)/t-locale.alias; \
- dest=$(DESTDIR)$(localedir)/locale.alias; \
- sed -f ref-add.sed $$orig > $$temp; \
- $(INSTALL_DATA) $$temp $$dest; \
- rm -f $$temp; \
- else \
- : ; \
- fi
-install-data: all
- if test "$(PACKAGE)" = "gettext"; then \
- $(mkinstalldirs) $(DESTDIR)$(gettextsrcdir); \
- $(INSTALL_DATA) VERSION $(DESTDIR)$(gettextsrcdir)/VERSION; \
- $(INSTALL_DATA) ChangeLog.inst $(DESTDIR)$(gettextsrcdir)/ChangeLog; \
- dists="COPYING.LIB-2 COPYING.LIB-2.1 $(DISTFILES.common)"; \
- for file in $$dists; do \
- $(INSTALL_DATA) $(srcdir)/$$file \
- $(DESTDIR)$(gettextsrcdir)/$$file; \
- done; \
- chmod a+x $(DESTDIR)$(gettextsrcdir)/config.charset; \
- dists="$(DISTFILES.generated)"; \
- for file in $$dists; do \
- if test -f $$file; then dir=.; else dir=$(srcdir); fi; \
- $(INSTALL_DATA) $$dir/$$file \
- $(DESTDIR)$(gettextsrcdir)/$$file; \
- done; \
- dists="$(DISTFILES.obsolete)"; \
- for file in $$dists; do \
- rm -f $(DESTDIR)$(gettextsrcdir)/$$file; \
- done; \
- else \
- : ; \
- fi
-
-# Define this as empty until I found a useful application.
-installcheck:
-
-uninstall:
- if test "$(PACKAGE)" = "gettext" \
- && test '' = '$(GETTOBJS)'; then \
- rm -f $(DESTDIR)$(includedir)/libintl.h; \
- $(LIBTOOL) --mode=uninstall \
- rm -f $(DESTDIR)$(libdir)/libintl.$la; \
- else \
- : ; \
- fi
- if test 'no' = yes; then \
- if test -f $(DESTDIR)$(libdir)/charset.alias; then \
- temp=$(DESTDIR)$(libdir)/t-charset.alias; \
- dest=$(DESTDIR)$(libdir)/charset.alias; \
- sed -f ref-del.sed $$dest > $$temp; \
- if grep '^# Packages using this file: $$' $$temp > /dev/null; then \
- rm -f $$dest; \
- else \
- $(INSTALL_DATA) $$temp $$dest; \
- fi; \
- rm -f $$temp; \
- fi; \
- if test -f $(DESTDIR)$(localedir)/locale.alias; then \
- temp=$(DESTDIR)$(localedir)/t-locale.alias; \
- dest=$(DESTDIR)$(localedir)/locale.alias; \
- sed -f ref-del.sed $$dest > $$temp; \
- if grep '^# Packages using this file: $$' $$temp > /dev/null; then \
- rm -f $$dest; \
- else \
- $(INSTALL_DATA) $$temp $$dest; \
- fi; \
- rm -f $$temp; \
- fi; \
- else \
- : ; \
- fi
- if test "$(PACKAGE)" = "gettext"; then \
- for file in VERSION ChangeLog COPYING.LIB-2 COPYING.LIB-2.1 $(DISTFILES.common) $(DISTFILES.generated); do \
- rm -f $(DESTDIR)$(gettextsrcdir)/$$file; \
- done; \
- else \
- : ; \
- fi
-
-info dvi:
-
-$(OBJECTS): ../config.h libgnuintl.h
-bindtextdom.$lo finddomain.$lo loadmsgcat.$lo: gettextP.h gettext.h loadinfo.h
-dcgettext.$lo: gettextP.h gettext.h hash-string.h loadinfo.h
-
-tags: TAGS
-
-TAGS: $(HEADERS) $(SOURCES)
- here=`pwd`; cd $(srcdir) && etags -o $$here/TAGS $(HEADERS) $(SOURCES)
-
-id: ID
-
-ID: $(HEADERS) $(SOURCES)
- here=`pwd`; cd $(srcdir) && mkid -f$$here/ID $(HEADERS) $(SOURCES)
-
-
-mostlyclean:
- rm -f *.a *.la *.o *.lo core core.*
- rm -f libintl.h charset.alias ref-add.sed ref-del.sed
- rm -f -r .libs _libs
-
-clean: mostlyclean
-
-distclean: clean
- rm -f Makefile ID TAGS
- if test "$(PACKAGE)" = gettext; then \
- rm -f ChangeLog.inst $(DISTFILES.normal); \
- else \
- : ; \
- fi
-
-maintainer-clean: distclean
- @echo "This command is intended for maintainers to use;"
- @echo "it deletes files that may require special tools to rebuild."
-
-
-# GNU gettext needs not contain the file `VERSION' but contains some
-# other files which should not be distributed in other packages.
-distdir = ../$(PACKAGE)-$(VERSION)/$(subdir)
-dist distdir: Makefile
- if test "$(PACKAGE)" = gettext; then \
- additional="$(DISTFILES.gettext)"; \
- else \
- additional="$(DISTFILES.normal)"; \
- fi; \
- $(MAKE) $(DISTFILES.common) $(DISTFILES.generated) $$additional; \
- for file in ChangeLog $(DISTFILES.common) $(DISTFILES.generated) $$additional; do \
- if test -f $$file; then dir=.; else dir=$(srcdir); fi; \
- ln $$dir/$$file $(distdir) 2> /dev/null \
- || cp -p $$dir/$$file $(distdir); \
- done
-
-Makefile: Makefile.in ../config.status
- cd .. \
- && CONFIG_FILES=$(subdir)/$@ CONFIG_HEADERS= $(SHELL) ./config.status
-
-# Tell versions [3.59,3.63) of GNU make not to export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-/* Automatically generated by gen_defs. Do not edit! */
-
-#ifdef HELP_C
-const char *HelpStrings[] = {
- N_("null operation"),
- N_("end of conditional execution (noop)"),
- N_("force viewing of attachment using mailcap"),
- N_("view attachment as text"),
- N_("Toggle display of subparts"),
- N_("move to the bottom of the page"),
- N_("remail a message to another user"),
- N_("select a new file in this directory"),
- N_("view file"),
- N_("display the currently selected file's name"),
- N_("subscribe to current mailbox (IMAP only)"),
- N_("unsubscribe from current mailbox (IMAP only)"),
- N_("toggle view all/subscribed mailboxes (IMAP only)"),
- N_("list mailboxes with new mail"),
- N_("change directories"),
- N_("check mailboxes for new mail"),
- N_("attach file(s) to this message"),
- N_("attach message(s) to this message"),
- N_("edit the BCC list"),
- N_("edit the CC list"),
- N_("edit attachment description"),
- N_("edit attachment transfer-encoding"),
- N_("enter a file to save a copy of this message in"),
- N_("edit the file to be attached"),
- N_("edit the from field"),
- N_("edit the message with headers"),
- N_("edit the message"),
- N_("edit attachment using mailcap entry"),
- N_("edit the Reply-To field"),
- N_("edit the subject of this message"),
- N_("edit the TO list"),
- N_("create a new mailbox (IMAP only)"),
- N_("edit attachment content type"),
- N_("get a temporary copy of an attachment"),
- N_("run ispell on the message"),
- N_("compose new attachment using mailcap entry"),
- N_("toggle recoding of this attachment"),
- N_("save this message to send later"),
- N_("rename/move an attached file"),
- N_("send the message"),
- N_("toggle disposition between inline/attachment"),
- N_("toggle whether to delete file after sending it"),
- N_("update an attachment's encoding info"),
- N_("write the message to a folder"),
- N_("copy a message to a file/mailbox"),
- N_("create an alias from a message sender"),
- N_("move entry to bottom of screen"),
- N_("move entry to middle of screen"),
- N_("move entry to top of screen"),
- N_("make decoded (text/plain) copy"),
- N_("make decoded copy (text/plain) and delete"),
- N_("delete the current entry"),
- N_("delete the current mailbox (IMAP only)"),
- N_("delete all messages in subthread"),
- N_("delete all messages in thread"),
- N_("display full address of sender"),
- N_("display message and toggle header weeding"),
- N_("display a message"),
- N_("edit the raw message"),
- N_("delete the char in front of the cursor"),
- N_("move the cursor one character to the left"),
- N_("move the cursor to the beginning of the word"),
- N_("jump to the beginning of the line"),
- N_("cycle among incoming mailboxes"),
- N_("complete filename or alias"),
- N_("complete address with query"),
- N_("delete the char under the cursor"),
- N_("jump to the end of the line"),
- N_("move the cursor one character to the right"),
- N_("move the cursor to the end of the word"),
- N_("scroll down through the history list"),
- N_("scroll up through the history list"),
- N_("delete chars from cursor to end of line"),
- N_("delete chars from the cursor to the end of the word"),
- N_("delete all chars on the line"),
- N_("delete the word in front of the cursor"),
- N_("quote the next typed key"),
- N_("transpose character under cursor with previous"),
- N_("capitalize the word"),
- N_("convert the word to lower case"),
- N_("convert the word to upper case"),
- N_("enter a muttrc command"),
- N_("enter a file mask"),
- N_("exit this menu"),
- N_("filter attachment through a shell command"),
- N_("move to the first entry"),
- N_("toggle a message's 'important' flag"),
- N_("forward a message with comments"),
- N_("select the current entry"),
- N_("reply to all recipients"),
- N_("scroll down 1/2 page"),
- N_("scroll up 1/2 page"),
- N_("this screen"),
- N_("jump to an index number"),
- N_("move to the last entry"),
- N_("reply to specified mailing list"),
- N_("execute a macro"),
- N_("compose a new mail message"),
- N_("break the thread in two"),
- N_("open a different folder"),
- N_("open a different folder in read only mode"),
- N_("clear a status flag from a message"),
- N_("delete messages matching a pattern"),
- N_("force retrieval of mail from IMAP server"),
- N_("retrieve mail from POP server"),
- N_("move to the first message"),
- N_("move to the last message"),
- N_("show only messages matching a pattern"),
- N_("link tagged message to the current one"),
- N_("open next mailbox with new mail"),
- N_("jump to the next new message"),
- N_("jump to the next new or unread message"),
- N_("jump to the next subthread"),
- N_("jump to the next thread"),
- N_("move to the next undeleted message"),
- N_("jump to the next unread message"),
- N_("jump to parent message in thread"),
- N_("jump to previous thread"),
- N_("jump to previous subthread"),
- N_("move to the previous undeleted message"),
- N_("jump to the previous new message"),
- N_("jump to the previous new or unread message"),
- N_("jump to the previous unread message"),
- N_("mark the current thread as read"),
- N_("mark the current subthread as read"),
- N_("set a status flag on a message"),
- N_("save changes to mailbox"),
- N_("tag messages matching a pattern"),
- N_("undelete messages matching a pattern"),
- N_("untag messages matching a pattern"),
- N_("move to the middle of the page"),
- N_("move to the next entry"),
- N_("scroll down one line"),
- N_("move to the next page"),
- N_("jump to the bottom of the message"),
- N_("toggle display of quoted text"),
- N_("skip beyond quoted text"),
- N_("jump to the top of the message"),
- N_("pipe message/attachment to a shell command"),
- N_("move to the previous entry"),
- N_("scroll up one line"),
- N_("move to the previous page"),
- N_("print the current entry"),
- N_("really delete the current entry, bypassing the trash folder"),
- N_("query external program for addresses"),
- N_("append new query results to current results"),
- N_("save changes to mailbox and quit"),
- N_("recall a postponed message"),
- N_("clear and redraw the screen"),
- N_("{internal}"),
- N_("rename the current mailbox (IMAP only)"),
- N_("reply to a message"),
- N_("use the current message as a template for a new one"),
- N_("save message/attachment to a file"),
- N_("search for a regular expression"),
- N_("search backwards for a regular expression"),
- N_("search for next match"),
- N_("search for next match in opposite direction"),
- N_("toggle search pattern coloring"),
- N_("invoke a command in a subshell"),
- N_("sort messages"),
- N_("sort messages in reverse order"),
- N_("tag the current entry"),
- N_("apply next function to tagged messages"),
- N_("apply next function ONLY to tagged messages"),
- N_("tag the current subthread"),
- N_("tag the current thread"),
- N_("toggle a message's 'new' flag"),
- N_("toggle whether the mailbox will be rewritten"),
- N_("toggle whether to browse mailboxes or all files"),
- N_("move to the top of the page"),
- N_("undelete the current entry"),
- N_("undelete all messages in thread"),
- N_("undelete all messages in subthread"),
- N_("show the Mutt version number and date"),
- N_("view attachment using mailcap entry if necessary"),
- N_("show MIME attachments"),
- N_("display the keycode for a key press"),
- N_("show currently active limit pattern"),
- N_("collapse/uncollapse current thread"),
- N_("collapse/uncollapse all threads"),
- N_("scroll the mailbox pane up 1 page"),
- N_("scroll the mailbox pane down 1 page"),
- N_("go down to next mailbox"),
- N_("go to previous mailbox"),
- N_("open hilighted mailbox"),
- N_("Accept the chain constructed"),
- N_("Append a remailer to the chain"),
- N_("Insert a remailer into the chain"),
- N_("Delete a remailer from the chain"),
- N_("Select the previous element of the chain"),
- N_("Select the next element of the chain"),
- N_("send the message through a mixmaster remailer chain"),
- N_("attach a PGP public key"),
- N_("show PGP options"),
- N_("mail a PGP public key"),
- N_("verify a PGP public key"),
- N_("view the key's user id"),
- N_("check for classic PGP"),
- N_("show S/MIME options"),
- N_("make decrypted copy and delete"),
- N_("make decrypted copy"),
- N_("wipe passphrase(s) from memory"),
- N_("extract supported public keys"),
- NULL
-};
-#endif /* MAIN_C */
-
-enum {
- OP_NULL,
- OP_END_COND,
- OP_ATTACH_VIEW_MAILCAP,
- OP_ATTACH_VIEW_TEXT,
- OP_ATTACH_COLLAPSE,
- OP_BOTTOM_PAGE,
- OP_BOUNCE_MESSAGE,
- OP_BROWSER_NEW_FILE,
- OP_BROWSER_VIEW_FILE,
- OP_BROWSER_TELL,
- OP_BROWSER_SUBSCRIBE,
- OP_BROWSER_UNSUBSCRIBE,
- OP_BROWSER_TOGGLE_LSUB,
- OP_BUFFY_LIST,
- OP_CHANGE_DIRECTORY,
- OP_CHECK_NEW,
- OP_COMPOSE_ATTACH_FILE,
- OP_COMPOSE_ATTACH_MESSAGE,
- OP_COMPOSE_EDIT_BCC,
- OP_COMPOSE_EDIT_CC,
- OP_COMPOSE_EDIT_DESCRIPTION,
- OP_COMPOSE_EDIT_ENCODING,
- OP_COMPOSE_EDIT_FCC,
- OP_COMPOSE_EDIT_FILE,
- OP_COMPOSE_EDIT_FROM,
- OP_COMPOSE_EDIT_HEADERS,
- OP_COMPOSE_EDIT_MESSAGE,
- OP_COMPOSE_EDIT_MIME,
- OP_COMPOSE_EDIT_REPLY_TO,
- OP_COMPOSE_EDIT_SUBJECT,
- OP_COMPOSE_EDIT_TO,
- OP_CREATE_MAILBOX,
- OP_EDIT_TYPE,
- OP_COMPOSE_GET_ATTACHMENT,
- OP_COMPOSE_ISPELL,
- OP_COMPOSE_NEW_MIME,
- OP_COMPOSE_TOGGLE_RECODE,
- OP_COMPOSE_POSTPONE_MESSAGE,
- OP_COMPOSE_RENAME_FILE,
- OP_COMPOSE_SEND_MESSAGE,
- OP_COMPOSE_TOGGLE_DISPOSITION,
- OP_COMPOSE_TOGGLE_UNLINK,
- OP_COMPOSE_UPDATE_ENCODING,
- OP_COMPOSE_WRITE_MESSAGE,
- OP_COPY_MESSAGE,
- OP_CREATE_ALIAS,
- OP_CURRENT_BOTTOM,
- OP_CURRENT_MIDDLE,
- OP_CURRENT_TOP,
- OP_DECODE_COPY,
- OP_DECODE_SAVE,
- OP_DELETE,
- OP_DELETE_MAILBOX,
- OP_DELETE_SUBTHREAD,
- OP_DELETE_THREAD,
- OP_DISPLAY_ADDRESS,
- OP_DISPLAY_HEADERS,
- OP_DISPLAY_MESSAGE,
- OP_EDIT_MESSAGE,
- OP_EDITOR_BACKSPACE,
- OP_EDITOR_BACKWARD_CHAR,
- OP_EDITOR_BACKWARD_WORD,
- OP_EDITOR_BOL,
- OP_EDITOR_BUFFY_CYCLE,
- OP_EDITOR_COMPLETE,
- OP_EDITOR_COMPLETE_QUERY,
- OP_EDITOR_DELETE_CHAR,
- OP_EDITOR_EOL,
- OP_EDITOR_FORWARD_CHAR,
- OP_EDITOR_FORWARD_WORD,
- OP_EDITOR_HISTORY_DOWN,
- OP_EDITOR_HISTORY_UP,
- OP_EDITOR_KILL_EOL,
- OP_EDITOR_KILL_EOW,
- OP_EDITOR_KILL_LINE,
- OP_EDITOR_KILL_WORD,
- OP_EDITOR_QUOTE_CHAR,
- OP_EDITOR_TRANSPOSE_CHARS,
- OP_EDITOR_CAPITALIZE_WORD,
- OP_EDITOR_DOWNCASE_WORD,
- OP_EDITOR_UPCASE_WORD,
- OP_ENTER_COMMAND,
- OP_ENTER_MASK,
- OP_EXIT,
- OP_FILTER,
- OP_FIRST_ENTRY,
- OP_FLAG_MESSAGE,
- OP_FORWARD_MESSAGE,
- OP_GENERIC_SELECT_ENTRY,
- OP_GROUP_REPLY,
- OP_HALF_DOWN,
- OP_HALF_UP,
- OP_HELP,
- OP_JUMP,
- OP_LAST_ENTRY,
- OP_LIST_REPLY,
- OP_MACRO,
- OP_MAIL,
- OP_MAIN_BREAK_THREAD,
- OP_MAIN_CHANGE_FOLDER,
- OP_MAIN_CHANGE_FOLDER_READONLY,
- OP_MAIN_CLEAR_FLAG,
- OP_MAIN_DELETE_PATTERN,
- OP_MAIN_IMAP_FETCH,
- OP_MAIN_FETCH_MAIL,
- OP_MAIN_FIRST_MESSAGE,
- OP_MAIN_LAST_MESSAGE,
- OP_MAIN_LIMIT,
- OP_MAIN_LINK_THREADS,
- OP_MAIN_NEXT_UNREAD_MAILBOX,
- OP_MAIN_NEXT_NEW,
- OP_MAIN_NEXT_NEW_THEN_UNREAD,
- OP_MAIN_NEXT_SUBTHREAD,
- OP_MAIN_NEXT_THREAD,
- OP_MAIN_NEXT_UNDELETED,
- OP_MAIN_NEXT_UNREAD,
- OP_MAIN_PARENT_MESSAGE,
- OP_MAIN_PREV_THREAD,
- OP_MAIN_PREV_SUBTHREAD,
- OP_MAIN_PREV_UNDELETED,
- OP_MAIN_PREV_NEW,
- OP_MAIN_PREV_NEW_THEN_UNREAD,
- OP_MAIN_PREV_UNREAD,
- OP_MAIN_READ_THREAD,
- OP_MAIN_READ_SUBTHREAD,
- OP_MAIN_SET_FLAG,
- OP_MAIN_SYNC_FOLDER,
- OP_MAIN_TAG_PATTERN,
- OP_MAIN_UNDELETE_PATTERN,
- OP_MAIN_UNTAG_PATTERN,
- OP_MIDDLE_PAGE,
- OP_NEXT_ENTRY,
- OP_NEXT_LINE,
- OP_NEXT_PAGE,
- OP_PAGER_BOTTOM,
- OP_PAGER_HIDE_QUOTED,
- OP_PAGER_SKIP_QUOTED,
- OP_PAGER_TOP,
- OP_PIPE,
- OP_PREV_ENTRY,
- OP_PREV_LINE,
- OP_PREV_PAGE,
- OP_PRINT,
- OP_PURGE_MESSAGE,
- OP_QUERY,
- OP_QUERY_APPEND,
- OP_QUIT,
- OP_RECALL_MESSAGE,
- OP_REDRAW,
- OP_REFORMAT_WINCH,
- OP_RENAME_MAILBOX,
- OP_REPLY,
- OP_RESEND,
- OP_SAVE,
- OP_SEARCH,
- OP_SEARCH_REVERSE,
- OP_SEARCH_NEXT,
- OP_SEARCH_OPPOSITE,
- OP_SEARCH_TOGGLE,
- OP_SHELL_ESCAPE,
- OP_SORT,
- OP_SORT_REVERSE,
- OP_TAG,
- OP_TAG_PREFIX,
- OP_TAG_PREFIX_COND,
- OP_TAG_SUBTHREAD,
- OP_TAG_THREAD,
- OP_TOGGLE_NEW,
- OP_TOGGLE_WRITE,
- OP_TOGGLE_MAILBOXES,
- OP_TOP_PAGE,
- OP_UNDELETE,
- OP_UNDELETE_THREAD,
- OP_UNDELETE_SUBTHREAD,
- OP_VERSION,
- OP_VIEW_ATTACH,
- OP_VIEW_ATTACHMENTS,
- OP_WHAT_KEY,
- OP_MAIN_SHOW_LIMIT,
- OP_MAIN_COLLAPSE_THREAD,
- OP_MAIN_COLLAPSE_ALL,
- OP_SIDEBAR_SCROLL_UP,
- OP_SIDEBAR_SCROLL_DOWN,
- OP_SIDEBAR_NEXT,
- OP_SIDEBAR_PREV,
- OP_SIDEBAR_OPEN,
- OP_MIX_USE,
- OP_MIX_APPEND,
- OP_MIX_INSERT,
- OP_MIX_DELETE,
- OP_MIX_CHAIN_PREV,
- OP_MIX_CHAIN_NEXT,
- OP_COMPOSE_MIX,
- OP_COMPOSE_ATTACH_KEY,
- OP_COMPOSE_PGP_MENU,
- OP_MAIL_KEY,
- OP_VERIFY_KEY,
- OP_VIEW_ID,
- OP_CHECK_TRADITIONAL,
- OP_COMPOSE_SMIME_MENU,
- OP_DECRYPT_SAVE,
- OP_DECRYPT_COPY,
- OP_FORGET_PASSPHRASE,
- OP_EXTRACT_KEYS,
- OP_MAX
-};
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# m4/Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-VPATH = ../../m4
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-subdir = m4
-DIST_COMMON = README $(srcdir)/Makefile.am $(srcdir)/Makefile.in
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES =
-SOURCES =
-DIST_SOURCES =
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DHAVE_CONFIG_H
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/m4
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/../m4
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu-patched/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ../../m4
-sysconfdir = /etc
-target_alias =
-top_build_prefix = ../
-top_builddir = ..
-top_srcdir = ../..
-EXTRA_DIST = README
-all: all-am
-
-.SUFFIXES:
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu m4/Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --gnu m4/Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-tags: TAGS
-TAGS:
-
-ctags: CTAGS
-CTAGS:
-
-
-distdir: $(DISTFILES)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
- $(MAKE) $(AM_MAKEFLAGS) \
- top_distdir="$(top_distdir)" distdir="$(distdir)" \
- dist-hook
-check-am: all-am
-check: check-am
-all-am: Makefile
-installdirs:
-install: install-am
-install-exec: install-exec-am
-install-data: install-data-am
-uninstall: uninstall-am
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-am
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
-clean: clean-am
-
-clean-am: clean-generic mostlyclean-am
-
-distclean: distclean-am
- -rm -f Makefile
-distclean-am: clean-am distclean-generic
-
-dvi: dvi-am
-
-dvi-am:
-
-html: html-am
-
-info: info-am
-
-info-am:
-
-install-data-am:
-
-install-dvi: install-dvi-am
-
-install-exec-am:
-
-install-html: install-html-am
-
-install-info: install-info-am
-
-install-man:
-
-install-pdf: install-pdf-am
-
-install-ps: install-ps-am
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-am
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-am
-
-mostlyclean-am: mostlyclean-generic
-
-pdf: pdf-am
-
-pdf-am:
-
-ps: ps-am
-
-ps-am:
-
-uninstall-am:
-
-.MAKE: install-am install-strip
-
-.PHONY: all all-am check check-am clean clean-generic dist-hook \
- distclean distclean-generic distdir dvi dvi-am html html-am \
- info info-am install install-am install-data install-data-am \
- install-dvi install-dvi-am install-exec install-exec-am \
- install-html install-html-am install-info install-info-am \
- install-man install-pdf install-pdf-am install-ps \
- install-ps-am install-strip installcheck installcheck-am \
- installdirs maintainer-clean maintainer-clean-generic \
- mostlyclean mostlyclean-generic pdf pdf-am ps ps-am uninstall \
- uninstall-am
-
-
-dist-hook:
- for i in $(srcdir)/*.m4 ; do \
- cp -f -p $$i $(distdir) ; \
- done
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-#!/bin/sh
-
-#
-# File a bug against the Mutt mail user agent.
-#
-
-#
-# $Id$
-#
-
-#
-# Copyright (c) 2000 Thomas Roessler <roessler@does-not-exist.org>
-#
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-#
-
-SUBMIT="fleas@mutt.org"
-DEBIAN_SUBMIT="submit@bugs.debian.org"
-
-prefix=/usr
-
-DEBUGGER=/usr/bin/gdb
-SENDMAIL=/usr/sbin/sendmail
-sysconfdir=/etc
-pkgdatadir=@pkgdatadir@
-
-include_file ()
-{
- echo
- echo "--- Begin $1"
- sed -e '/^[ ]*#/d; /^[ ]*$/d; s/^-/- -/' $1
- echo "--- End $1"
- echo
-}
-
-debug_gdb ()
-{
- cat << EOF > $SCRATCH/gdb.rc
-bt
-list
-quit
-EOF
- $DEBUGGER -n -x $SCRATCH/gdb.rc -c $CORE mutt
-}
-
-debug_dbx ()
-{
- cat << EOF > $SCRATCH/dbx.rc
-where
-list
-quit
-EOF
- $DEBUGGER -s $SCRATCH/dbx.rc mutt $CORE
-}
-
-debug_sdb ()
-{
- cat << EOF > $SCRATCH/sdb.rc
-t
-w
-q
-EOF
- $DEBUGGER mutt $CORE < $SCRATCH/sdb.rc
-}
-
-case `echo -n` in
-"") n=-n; c= ;;
- *) n=; c='\c' ;;
-esac
-
-
-exec > /dev/tty
-exec < /dev/tty
-
-SCRATCH=${TMPDIR-/tmp}/`basename $0`.`hostname`.$$
-
-mkdir ${SCRATCH} || \
-{
- echo "`basename $0`: Can't create temporary directory." >& 2 ;
- exit 1 ;
-}
-
-trap "rm -r -f ${SCRATCH} ; trap '' 0 ; exit" 0 1 2
-
-TEMPLATE=${SCRATCH}/template.txt
-
-if test -z "$EMAIL" ; then
- EMAIL="`mutt -Q from 2> /dev/null | sed -e 's/^from=.\(.*\).$/\1/'`"
-fi
-
-EMAILTMP=''
-while test -z "$EMAILTMP"
-do
- echo "Please enter your e-mail address [$EMAIL]:"
- echo $n "> $c"
- read EMAILTMP
-
- if test -z "$EMAILTMP"; then EMAILTMP="$EMAIL"; fi
-
- if ! echo "$EMAILTMP" | grep -q @
- then
- echo "$EMAILTMP does not appear to be a valid email address"
- EMAILTMP=''
- continue
- fi
-
- EMAIL="$EMAILTMP"
-done
-
-echo "Please enter a one-line description of the problem you experience:"
-echo $n "> $c"
-read SUBJECT
-
-cat <<EOF
-What should the severity for this bug report be?
-
- 0) Feature request, or maybe a bug which is very difficult to
- fix due to major design considerations.
-
- 1) The package fails to perform correctly in some conditions,
- or on some systems, or fails to comply with current policy
- documents. Most bugs are in this category.
-
- 2) This bug makes this version of the package unsuitable for
- a stable release.
-
- 3) Dangerous bug. Makes the package in question unusable by
- anyone or mostly so, or causes data loss, or introduces a
- security hole allowing access to the accounts of users who
- use the package.
-
- 4) Critical bug. Makes unrelated software on the system (or
- the whole system) break, or causes serious data loss, or
- introduces a security hole on systems where you install the
- package.
-
-EOF
-echo $n "Severity? [01234] $c"
-read severity
-case "$severity" in
-0|[Ww]) severity=wishlist ;;
-2|[Ii]) severity=important ;;
-3|[Gg]) severity=grave ;;
-4|[Cc]) severity=critical ;;
- *) severity=normal ;;
-esac
-
-if test -x $DEBUGGER ; then
- test -f core && CORE=core
- echo "If mutt has crashed, it may have saved some program state in"
- echo "a file named core. We can include this information with the bug"
- echo "report if you wish so."
- echo "Do you want to include information gathered from a core file?"
- echo "If yes, please enter the path - otherwise just say no: [$CORE]"
- echo $n "> $c"
- read _CORE
- test "$_CORE" && CORE="$_CORE"
-fi
-
-echo $n "Do you want to include your personal mutt configuration files? [Y|n] $c"
-read personal
-case "$personal" in
-[nN]*) personal=no ;;
- *) personal=yes ;;
-esac
-
-echo $n "Do you want to include your system's global mutt configuration file? [Y|n] $c"
-read global
-case "$global" in
-[nN]*) global=no ;;
- *) global=yes ;;
-esac
-
-if test -f /etc/debian_version ; then
- DEBIAN=yes
- echo $n "Checking whether mutt has been installed as a package... $c"
- DEBIANVERSION="`dpkg -l mutt | grep '^[ih]' | awk '{print $3}'`" 2> /dev/null
- if test "$DEBIANVERSION" ; then
- DPKG=yes
- else
- DPKG=no
- unset DEBIANVERSION
- fi
- echo "$DPKG"
- echo $n "File this bug with Debian? [Y|n] $c"
- read DPKG
- case "$DPKG" in
- [nN]) DPKG=no ;;
- *) DPKG=yes ;;
- esac
-else
- DEBIAN=no
- DPKG=no
-fi
-
-if rpm -q mutt > /dev/null 2> /dev/null ; then
- echo "Mutt seems to come from an RPM package."
- RPMVERSION="`rpm -q mutt`"
- RPMPACKAGER="`rpm -q -i mutt | sed -n -e 's/^Packager *: *//p'`"
-fi
-
-MUTTVERSION="`mutt -v | awk '{print $2; exit; }'`"
-test "$DPKG" = "yes" && SUBMIT="$SUBMIT, $DEBIAN_SUBMIT"
-
-exec > ${TEMPLATE}
-
-test "$EMAIL" && echo "From: $EMAIL"
-test "$REPLYTO" && echo "Reply-To: $REPLYTO"
-test "$ORGANIZATION" && echo "Organization: $ORGANIZATION"
-
-echo "Subject: mutt-$MUTTVERSION: $SUBJECT"
-echo "To: $SUBMIT"
-test "$EMAIL" && echo "Bcc: ${EMAIL}"
-echo
-echo "Package: mutt"
-echo "Version: ${DEBIANVERSION-${RPMVERSION-$MUTTVERSION}}"
-echo "Severity: $severity"
-echo
-echo "-- Please type your report below this line"
-echo
-echo
-echo
-
-if test "$DEBIAN" = "yes" ; then
- echo "Obtaining Debian-specific information..." > /dev/tty
- bug -p -s dummy mutt < /dev/null 2> /dev/null | \
- sed -n -e "/^-- System Information/,/^---/p" | \
- grep -v '^---'
-else
- echo "-- System Information"
- echo "System Version: `uname -a`"
- test -z "$RPMPACKAGER" || echo "RPM Packager: $RPMPACKAGER";
- test -f /etc/redhat-release && echo "RedHat Release: `cat /etc/redhat-release`"
- test -f /etc/SuSE-release && echo "SuSE Release: `sed 1q /etc/SuSE-release`"
- # Please provide more of these if you have any.
-fi
-
-echo
-echo "-- Build environment information"
-echo
-echo "(Note: This is the build environment installed on the system"
-echo "muttbug is run on. Information may or may not match the environment"
-echo "used to build mutt.)"
-echo
-echo "- gcc version information"
-echo "gcc"
-gcc -v 2>&1
-echo
-echo "- CFLAGS"
-echo -Wall -pedantic -Wno-long-long -Wall -g -O2
-
-
-echo
-echo "-- Mutt Version Information"
-echo
-LC_ALL=C mutt -v
-
-if test "$CORE" && test -f "$CORE" ; then
- echo
- echo "-- Core Dump Analysis Output"
- echo
-
- case "$DEBUGGER" in
- *sdb) debug_sdb $CORE ;;
- *dbx) debug_dbx $CORE ;;
- *gdb) debug_gdb $CORE ;;
- esac
-
- echo
-fi
-
-if test "$personal" = "yes" ; then
- CANDIDATES=".muttrc-${MUTTVERSION} .muttrc .mutt/muttrc-${MUTTVERSION} .mutt/muttrc"
- MATCHED="none"
- for f in $CANDIDATES; do
- if test -f "${HOME}/$f" ; then
- MATCHED="${HOME}/$f"
- break
- fi
- done
-
- if test "$MATCHED" = "none" ; then
- echo "Warning: Can't find your personal .muttrc." >&2
- else
- include_file $MATCHED
- fi
-fi
-
-
-if test "$global" = "yes" ; then
- CANDIDATES="Muttrc-${MUTTVERSION} Muttrc"
- DIRECTORIES="$sysconfdir $pkgdatadir"
- MATCHED="none"
- for d in $DIRECTORIES ; do
- for f in $CANDIDATES; do
- if test -f $d/$f ; then
- MATCHED="$d/$f"
- break
- fi
- done
- test "$MATCHED" = "none" || break
- done
-
- if test "$MATCHED" = "none" ; then
- echo "Warning: Can't find global Muttrc." >&2
- else
- include_file $MATCHED
- fi
-fi
-
-exec > /dev/tty
-
-cp $TEMPLATE $SCRATCH/mutt-bug.txt
-
-input="e"
-while : ; do
- if test "$input" = "e" ; then
- ${VISUAL-${EDITOR-vi}} $SCRATCH/mutt-bug.txt
- if cmp $SCRATCH/mutt-bug.txt ${TEMPLATE} > /dev/null ; then
- echo "Warning: Bug report was not modified!"
- fi
- fi
-
- echo $n "Submit, Edit, View, Quit? [S|e|v|q] $c"
- read _input
- input="`echo $_input | tr EVSQ evsq`"
- case $input in
- e*) ;;
- v*) ${PAGER-more} $SCRATCH/mutt-bug.txt ;;
- s*|"") $SENDMAIL -t < $SCRATCH/mutt-bug.txt ; exit ;;
- q*) exit
- esac
-done
-
+++ /dev/null
-/* this is an autogenerated file. edit patchlist.sh instead. */
-#include "config.h"
-
-#include <stdio.h>
-#include <stdlib.h>
-
-#include "mutt.h"
-
-void mutt_print_patchlist (void)
-{
- puts ("patch-1.5.13.cd.ifdef.2");
- puts ("patch-1.5.18.rr.compressed.1");
- puts ("patch-1.5.19.sidebar.20090522.txt");
-}
+++ /dev/null
-# Makefile for program source directory in GNU NLS utilities package.
-# Copyright (C) 1995-1997, 2000, 2001 by Ulrich Drepper <drepper@gnu.ai.mit.edu>
-#
-# This file file be copied and used freely without restrictions. It can
-# be used in projects which are not available under the GNU General Public License
-# but which still want to provide support for the GNU gettext functionality.
-# Please note that the actual code is *not* freely available.
-
-PACKAGE = mutt
-VERSION = 1.5.19
-
-# These two variables depend on the location of this directory.
-subdir = po
-top_builddir = ..
-
-SHELL = /bin/sh
-
-
-srcdir = ../../po
-top_srcdir = ../..
-VPATH = ../../po
-
-prefix = /usr
-exec_prefix = ${prefix}
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-localedir = $(datadir)/locale
-gettextsrcdir = $(datadir)/gettext/po
-
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-MKINSTALLDIRS = ../mkinstalldirs
-mkinstalldirs = $(SHELL) `case "$(MKINSTALLDIRS)" in /*) echo "$(MKINSTALLDIRS)" ;; *) echo "$(top_builddir)/$(MKINSTALLDIRS)" ;; esac`
-
-CC = gcc
-GMSGFMT = /usr/bin/msgfmt
-MSGFMT = /usr/bin/msgfmt
-XGETTEXT = /usr/bin/xgettext
-MSGMERGE = msgmerge
-
-DEFS = -DHAVE_CONFIG_H
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-
-INCLUDES = -I.. -I$(top_srcdir)/intl
-
-COMPILE = $(CC) -c $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $(XCFLAGS)
-
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-DISTFILES = Makefile.in.in POTFILES.in $(PACKAGE).pot \
-$(POFILES) $(GMOFILES)
-
-# need two spaces before = as m4/gettext.m4 matches against
-# 'POTFILES[space]=' to add files from POTFILES
-BUILT_POTFILES = $(top_builddir)/keymap_alldefs.h
-
-POTFILES = \
- ../../account.c \
- ../../addrbook.c \
- ../../alias.c \
- ../../attach.c \
- ../../browser.c \
- ../../buffy.c \
- ../../charset.c \
- ../../color.c \
- ../../commands.c \
- ../../compose.c \
- ../../compress.c \
- ../../crypt-gpgme.c \
- ../../crypt.c \
- ../../cryptglue.c \
- ../../curs_lib.c \
- ../../curs_main.c \
- ../../edit.c \
- ../../editmsg.c \
- ../../flags.c \
- ../../handler.c \
- ../../headers.c \
- ../../help.c \
- ../../history.c \
- ../../hook.c \
- ../../imap/auth.c \
- ../../imap/auth_anon.c \
- ../../imap/auth_cram.c \
- ../../imap/auth_gss.c \
- ../../imap/auth_login.c \
- ../../imap/auth_sasl.c \
- ../../imap/browse.c \
- ../../imap/command.c \
- ../../imap/imap.c \
- ../../imap/message.c \
- ../../imap/util.c \
- ../../init.c \
- ../../keymap.c \
- ../../lib.c \
- ../../main.c \
- ../../mbox.c \
- ../../menu.c \
- ../../mh.c \
- ../../mutt_sasl.c \
- ../../mutt_socket.c \
- ../../mutt_ssl.c \
- ../../mutt_ssl_gnutls.c \
- ../../mutt_tunnel.c \
- ../../muttlib.c \
- ../../mx.c \
- ../../pager.c \
- ../../parse.c \
- ../../pattern.c \
- ../../pgp.c \
- ../../pgpinvoke.c \
- ../../pgpkey.c \
- ../../pop.c \
- ../../pop_auth.c \
- ../../pop_lib.c \
- ../../postpone.c \
- ../../query.c \
- ../../recvattach.c \
- ../../recvcmd.c \
- ../../remailer.c \
- ../../rfc1524.c \
- ../../score.c \
- ../../send.c \
- ../../sendlib.c \
- ../../signal.c \
- ../../smime.c \
- ../../smtp.c \
- ../../sort.c \
- ../../status.c \
- ../../thread.c
-
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-
-.SUFFIXES:
-.SUFFIXES: .c .o .po .pox .gmo .mo
-
-.c.o:
- $(COMPILE) $<
-
-.po.pox:
- $(MAKE) $(PACKAGE).pot
- $(MSGMERGE) $< $(PACKAGE).pot -o $*.pox
-
-.po.mo:
- $(MSGFMT) -o $@ $<
-
-.po.gmo:
- file=`echo $* | sed 's,.*/,,'`.gmo \
- && rm -f $$file && $(GMSGFMT) --statistics -o $$file $<
-
-
-all: all-yes
-
-all-yes: $(CATALOGS)
-all-no:
-
-$(top_builddir)/keymap_alldefs.h:
- ( cd $(top_builddir) && $(MAKE) keymap_alldefs.h )
-
-# Note: Target 'all' must not depend on target '$(srcdir)/$(PACKAGE).pot',
-# otherwise packages like GCC can not be built if only parts of the source
-# have been downloaded.
-
-$(PACKAGE).pot: $(POTFILES) $(BUILT_POTFILES) $(srcdir)/POTFILES.in
- rm -f $(PACKAGE).pot $(PACKAGE).po
- $(XGETTEXT) --default-domain=$(PACKAGE) --directory=$(top_srcdir) \
- --add-comments --keyword=_ --keyword=N_ \
- --files-from=$(srcdir)/POTFILES.in \
- && \
- $(XGETTEXT) --default-domain=$(PACKAGE) \
- --add-comments --keyword=_ --keyword=N_ \
- --join $(BUILT_POTFILES) \
- && test ! -f $(PACKAGE).po \
- || ( rm -f $(PACKAGE).pot \
- && mv $(PACKAGE).po $(PACKAGE).pot )
-
-
-install: install-exec install-data
-install-exec:
-install-data: install-data-yes
- if test "$(PACKAGE)" = "gettext"; then \
- $(mkinstalldirs) $(DESTDIR)$(gettextsrcdir); \
- $(INSTALL_DATA) $(srcdir)/Makefile.in.in \
- $(DESTDIR)$(gettextsrcdir)/Makefile.in.in; \
- else \
- : ; \
- fi
-install-data-no: all
-install-data-yes: all
- $(mkinstalldirs) $(DESTDIR)$(datadir)
- @catalogs='$(CATALOGS)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- dir=$(localedir)/$$lang/LC_MESSAGES; \
- $(mkinstalldirs) $(DESTDIR)$$dir; \
- if test -r $$cat; then \
- $(INSTALL_DATA) $$cat $(DESTDIR)$$dir/$(PACKAGE).mo; \
- echo "installing $$cat as $(DESTDIR)$$dir/$(PACKAGE).mo"; \
- else \
- $(INSTALL_DATA) $(srcdir)/$$cat $(DESTDIR)$$dir/$(PACKAGE).mo; \
- echo "installing $(srcdir)/$$cat as" \
- "$(DESTDIR)$$dir/$(PACKAGE).mo"; \
- fi; \
- done
-
-# Define this as empty until I found a useful application.
-installcheck:
-
-uninstall:
- catalogs='$(CATALOGS)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- rm -f $(DESTDIR)$(localedir)/$$lang/LC_MESSAGES/$(PACKAGE).mo; \
- done
- if test "$(PACKAGE)" = "gettext"; then \
- rm -f $(DESTDIR)$(gettextsrcdir)/Makefile.in.in; \
- else \
- : ; \
- fi
-
-check: all
-
-dvi info tags TAGS ID:
-
-mostlyclean:
- rm -f core core.* *.pox $(PACKAGE).po *.new.po
- rm -fr *.o
-
-clean: mostlyclean
-
-distclean: clean
- rm -f Makefile Makefile.in POTFILES *.mo
-
-maintainer-clean: distclean
- @echo "This command is intended for maintainers to use;"
- @echo "it deletes files that may require special tools to rebuild."
- rm -f $(GMOFILES)
-
-distdir = $(top_builddir)/$(PACKAGE)-$(VERSION)/$(subdir)
-dist distdir: $(DISTFILES)
- dists="$(DISTFILES)"; \
- for file in $$dists; do \
- if test -f $$file; then dir=.; else dir=$(srcdir); fi; \
- cp -p $$dir/$$file $(distdir); \
- done
-
-update-po: Makefile
- $(MAKE) $(PACKAGE).pot
- if test "$(PACKAGE)" = "gettext"; then PATH=`pwd`/../src:$$PATH; fi; \
- cd $(srcdir); \
- catalogs='$(GMOFILES)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- echo "$$lang:"; \
- if $(MSGMERGE) $$lang.po $(PACKAGE).pot -o $$lang.new.po; then \
- mv -f $$lang.new.po $$lang.po; \
- else \
- echo "msgmerge for $$cat failed!"; \
- rm -f $$lang.new.po; \
- fi; \
- done
- $(MAKE) update-gmo
-
-update-gmo: Makefile $(GMOFILES)
- @:
-
-Makefile: Makefile.in.in $(top_builddir)/config.status POTFILES.in
- cd $(top_builddir) \
- && CONFIG_FILES=$(subdir)/$@.in CONFIG_HEADERS= \
- $(SHELL) ./config.status
-
-# Tell versions [3.59,3.63) of GNU make not to export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-# Makefile for program source directory in GNU NLS utilities package.
-# Copyright (C) 1995-1997, 2000, 2001 by Ulrich Drepper <drepper@gnu.ai.mit.edu>
-#
-# This file file be copied and used freely without restrictions. It can
-# be used in projects which are not available under the GNU General Public License
-# but which still want to provide support for the GNU gettext functionality.
-# Please note that the actual code is *not* freely available.
-
-PACKAGE = mutt
-VERSION = 1.5.19
-
-# These two variables depend on the location of this directory.
-subdir = po
-top_builddir = ..
-
-SHELL = /bin/sh
-
-
-srcdir = ../../po
-top_srcdir = ../..
-VPATH = ../../po
-
-prefix = /usr
-exec_prefix = ${prefix}
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-localedir = $(datadir)/locale
-gettextsrcdir = $(datadir)/gettext/po
-
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-MKINSTALLDIRS = ../mkinstalldirs
-mkinstalldirs = $(SHELL) `case "$(MKINSTALLDIRS)" in /*) echo "$(MKINSTALLDIRS)" ;; *) echo "$(top_builddir)/$(MKINSTALLDIRS)" ;; esac`
-
-CC = gcc
-GMSGFMT = /usr/bin/msgfmt
-MSGFMT = /usr/bin/msgfmt
-XGETTEXT = /usr/bin/xgettext
-MSGMERGE = msgmerge
-
-DEFS = -DHAVE_CONFIG_H
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-
-INCLUDES = -I.. -I$(top_srcdir)/intl
-
-COMPILE = $(CC) -c $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $(XCFLAGS)
-
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-DISTFILES = Makefile.in.in POTFILES.in $(PACKAGE).pot \
-$(POFILES) $(GMOFILES)
-
-# need two spaces before = as m4/gettext.m4 matches against
-# 'POTFILES[space]=' to add files from POTFILES
-BUILT_POTFILES = $(top_builddir)/keymap_alldefs.h
-
-POTFILES = \
-
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-
-.SUFFIXES:
-.SUFFIXES: .c .o .po .pox .gmo .mo
-
-.c.o:
- $(COMPILE) $<
-
-.po.pox:
- $(MAKE) $(PACKAGE).pot
- $(MSGMERGE) $< $(PACKAGE).pot -o $*.pox
-
-.po.mo:
- $(MSGFMT) -o $@ $<
-
-.po.gmo:
- file=`echo $* | sed 's,.*/,,'`.gmo \
- && rm -f $$file && $(GMSGFMT) --statistics -o $$file $<
-
-
-all: all-yes
-
-all-yes: $(CATALOGS)
-all-no:
-
-$(top_builddir)/keymap_alldefs.h:
- ( cd $(top_builddir) && $(MAKE) keymap_alldefs.h )
-
-# Note: Target 'all' must not depend on target '$(srcdir)/$(PACKAGE).pot',
-# otherwise packages like GCC can not be built if only parts of the source
-# have been downloaded.
-
-$(PACKAGE).pot: $(POTFILES) $(BUILT_POTFILES) $(srcdir)/POTFILES.in
- rm -f $(PACKAGE).pot $(PACKAGE).po
- $(XGETTEXT) --default-domain=$(PACKAGE) --directory=$(top_srcdir) \
- --add-comments --keyword=_ --keyword=N_ \
- --files-from=$(srcdir)/POTFILES.in \
- && \
- $(XGETTEXT) --default-domain=$(PACKAGE) \
- --add-comments --keyword=_ --keyword=N_ \
- --join $(BUILT_POTFILES) \
- && test ! -f $(PACKAGE).po \
- || ( rm -f $(PACKAGE).pot \
- && mv $(PACKAGE).po $(PACKAGE).pot )
-
-
-install: install-exec install-data
-install-exec:
-install-data: install-data-yes
- if test "$(PACKAGE)" = "gettext"; then \
- $(mkinstalldirs) $(DESTDIR)$(gettextsrcdir); \
- $(INSTALL_DATA) $(srcdir)/Makefile.in.in \
- $(DESTDIR)$(gettextsrcdir)/Makefile.in.in; \
- else \
- : ; \
- fi
-install-data-no: all
-install-data-yes: all
- $(mkinstalldirs) $(DESTDIR)$(datadir)
- @catalogs='$(CATALOGS)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- dir=$(localedir)/$$lang/LC_MESSAGES; \
- $(mkinstalldirs) $(DESTDIR)$$dir; \
- if test -r $$cat; then \
- $(INSTALL_DATA) $$cat $(DESTDIR)$$dir/$(PACKAGE).mo; \
- echo "installing $$cat as $(DESTDIR)$$dir/$(PACKAGE).mo"; \
- else \
- $(INSTALL_DATA) $(srcdir)/$$cat $(DESTDIR)$$dir/$(PACKAGE).mo; \
- echo "installing $(srcdir)/$$cat as" \
- "$(DESTDIR)$$dir/$(PACKAGE).mo"; \
- fi; \
- done
-
-# Define this as empty until I found a useful application.
-installcheck:
-
-uninstall:
- catalogs='$(CATALOGS)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- rm -f $(DESTDIR)$(localedir)/$$lang/LC_MESSAGES/$(PACKAGE).mo; \
- done
- if test "$(PACKAGE)" = "gettext"; then \
- rm -f $(DESTDIR)$(gettextsrcdir)/Makefile.in.in; \
- else \
- : ; \
- fi
-
-check: all
-
-dvi info tags TAGS ID:
-
-mostlyclean:
- rm -f core core.* *.pox $(PACKAGE).po *.new.po
- rm -fr *.o
-
-clean: mostlyclean
-
-distclean: clean
- rm -f Makefile Makefile.in POTFILES *.mo
-
-maintainer-clean: distclean
- @echo "This command is intended for maintainers to use;"
- @echo "it deletes files that may require special tools to rebuild."
- rm -f $(GMOFILES)
-
-distdir = $(top_builddir)/$(PACKAGE)-$(VERSION)/$(subdir)
-dist distdir: $(DISTFILES)
- dists="$(DISTFILES)"; \
- for file in $$dists; do \
- if test -f $$file; then dir=.; else dir=$(srcdir); fi; \
- cp -p $$dir/$$file $(distdir); \
- done
-
-update-po: Makefile
- $(MAKE) $(PACKAGE).pot
- if test "$(PACKAGE)" = "gettext"; then PATH=`pwd`/../src:$$PATH; fi; \
- cd $(srcdir); \
- catalogs='$(GMOFILES)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- echo "$$lang:"; \
- if $(MSGMERGE) $$lang.po $(PACKAGE).pot -o $$lang.new.po; then \
- mv -f $$lang.new.po $$lang.po; \
- else \
- echo "msgmerge for $$cat failed!"; \
- rm -f $$lang.new.po; \
- fi; \
- done
- $(MAKE) update-gmo
-
-update-gmo: Makefile $(GMOFILES)
- @:
-
-Makefile: Makefile.in.in $(top_builddir)/config.status POTFILES.in
- cd $(top_builddir) \
- && CONFIG_FILES=$(subdir)/$@.in CONFIG_HEADERS= \
- $(SHELL) ./config.status
-
-# Tell versions [3.59,3.63) of GNU make not to export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
- ../../account.c \
- ../../addrbook.c \
- ../../alias.c \
- ../../attach.c \
- ../../browser.c \
- ../../buffy.c \
- ../../charset.c \
- ../../color.c \
- ../../commands.c \
- ../../compose.c \
- ../../compress.c \
- ../../crypt-gpgme.c \
- ../../crypt.c \
- ../../cryptglue.c \
- ../../curs_lib.c \
- ../../curs_main.c \
- ../../edit.c \
- ../../editmsg.c \
- ../../flags.c \
- ../../handler.c \
- ../../headers.c \
- ../../help.c \
- ../../history.c \
- ../../hook.c \
- ../../imap/auth.c \
- ../../imap/auth_anon.c \
- ../../imap/auth_cram.c \
- ../../imap/auth_gss.c \
- ../../imap/auth_login.c \
- ../../imap/auth_sasl.c \
- ../../imap/browse.c \
- ../../imap/command.c \
- ../../imap/imap.c \
- ../../imap/message.c \
- ../../imap/util.c \
- ../../init.c \
- ../../keymap.c \
- ../../lib.c \
- ../../main.c \
- ../../mbox.c \
- ../../menu.c \
- ../../mh.c \
- ../../mutt_sasl.c \
- ../../mutt_socket.c \
- ../../mutt_ssl.c \
- ../../mutt_ssl_gnutls.c \
- ../../mutt_tunnel.c \
- ../../muttlib.c \
- ../../mx.c \
- ../../pager.c \
- ../../parse.c \
- ../../pattern.c \
- ../../pgp.c \
- ../../pgpinvoke.c \
- ../../pgpkey.c \
- ../../pop.c \
- ../../pop_auth.c \
- ../../pop_lib.c \
- ../../postpone.c \
- ../../query.c \
- ../../recvattach.c \
- ../../recvcmd.c \
- ../../remailer.c \
- ../../rfc1524.c \
- ../../score.c \
- ../../send.c \
- ../../sendlib.c \
- ../../signal.c \
- ../../smime.c \
- ../../smtp.c \
- ../../sort.c \
- ../../status.c \
- ../../thread.c
+++ /dev/null
-const char *ReleaseDate = "2009-01-05";
+++ /dev/null
-#! /usr/bin/perl -w
-
-# Copyright (C) 2001,2002 Oliver Ehli <elmy@acm.org>
-# Copyright (C) 2001 Mike Schiraldi <raldi@research.netsol.com>
-# Copyright (C) 2003 Bjoern Jacke <bjoern@j3e.de>
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-
-use strict;
-use File::Copy;
-use File::Glob ':glob';
-
-umask 077;
-
-require "timelocal.pl";
-
-sub usage ();
-sub newfile ($;$$);
-sub mutt_Q ($ );
-sub mycopy ($$);
-
-# directory setup routines
-sub mkdir_recursive ($ );
-sub init_paths ();
-
-# key/certificate management methods
-sub list_certs ();
-sub query_label ();
-sub add_entry ($$$$$ );
-sub add_certificate ($$$$;$ );
-sub add_key ($$$$);
-sub add_root_cert ($ );
-sub parse_pem (@ );
-sub handle_pem (@ );
-sub modify_entry ($$$;$ );
-sub remove_pair ($ );
-sub change_label ($ );
-sub verify_cert($$);
-sub do_verify($$$ );
-
-# Get the directories mutt uses for certificate/key storage.
-
-my $mutt = $ENV{MUTT_CMDLINE} || 'mutt';
-my $opensslbin = "/usr/bin/openssl";
-my @tempfiles = ();
-my @cert_tmp_file = ();
-
-my $tmpdir;
-my $private_keys_path = mutt_Q 'smime_keys';
-die "smime_keys is not set in mutt's configuration file"
- if length $private_keys_path == 0;
-
-my $certificates_path = mutt_Q 'smime_certificates';
-die "smime_certificates is not set in mutt's configuration file"
- if length $certificates_path == 0;
-my $root_certs_path = mutt_Q 'smime_ca_location';
-die "smime_ca_location is not set in mutt's configuration file"
- if length $root_certs_path == 0;
-
-my $root_certs_switch;
-if ( -d $root_certs_path) {
- $root_certs_switch = -CApath;
-} else {
- $root_certs_switch = -CAfile;
-}
-
-
-#
-# OPS
-#
-
-if(@ARGV == 1 and $ARGV[0] eq "init") {
- init_paths;
-}
-elsif(@ARGV == 1 and $ARGV[0] eq "list") {
- list_certs;
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "label") {
- change_label($ARGV[1]);
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "add_cert") {
- my $format = -B $ARGV[1] ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -noout -hash -in $ARGV[1] -inform $format";
- my $cert_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
- chomp($cert_hash);
- my $label = query_label;
- &add_certificate($ARGV[1], \$cert_hash, 1, $label, '?');
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "add_pem") {
- -e $ARGV[1] and -s $ARGV[1] or die("$ARGV[1] is nonexistent or empty.");
- open(PEM_FILE, "<$ARGV[1]") or die("Can't open $ARGV[1]: $!");
- my @pem = <PEM_FILE>;
- close(PEM_FILE);
- handle_pem(@pem);
-}
-elsif( @ARGV == 2 and $ARGV[0] eq "add_p12") {
- -e $ARGV[1] and -s $ARGV[1] or die("$ARGV[1] is nonexistent or empty.");
-
- print "\nNOTE: This will ask you for two passphrases:\n";
- print " 1. The passphrase you used for exporting\n";
- print " 2. The passphrase you wish to secure your private key with.\n\n";
-
- my $pem_file = "$ARGV[1].pem";
-
- my $cmd = "$opensslbin pkcs12 -in $ARGV[1] -out $pem_file";
- system $cmd and die "'$cmd' returned $?";
-
- -e $pem_file and -s $pem_file or die("Conversion of $ARGV[1] failed.");
- open(PEM_FILE, $pem_file) or die("Can't open $pem_file: $!");
- my @pem = <PEM_FILE>;
- close(PEM_FILE);
- unlink $pem_file;
- handle_pem(@pem);
-}
-elsif(@ARGV == 4 and $ARGV[0] eq "add_chain") {
- my $mailbox;
- my $format = -B $ARGV[2] ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -noout -hash -in $ARGV[2] -inform $format";
- my $cert_hash = `$cmd`;
-
- $? and die "'$cmd' returned $?";
-
- $format = -B $ARGV[3] ? 'DER' : 'PEM';
-
- $cmd = "$opensslbin x509 -noout -hash -in $ARGV[3] -inform $format";
- my $issuer_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- chomp($cert_hash);
- chomp($issuer_hash);
-
- my $label = query_label;
-
- add_certificate($ARGV[3], \$issuer_hash, 0, $label);
- my @mailbox = &add_certificate($ARGV[2], \$cert_hash, 1, $label, $issuer_hash);
-
- foreach $mailbox (@mailbox) {
- chomp($mailbox);
- add_key($ARGV[1], $cert_hash, $mailbox, $label);
- }
-}
-elsif((@ARGV == 2 or @ARGV == 3) and $ARGV[0] eq "verify") {
- verify_cert($ARGV[1], $ARGV[2]);
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "remove") {
- remove_pair($ARGV[1]);
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "add_root") {
- add_root_cert($ARGV[1]);
-}
-else {
- usage;
- exit(1);
-}
-
-exit(0);
-
-
-
-
-
-############## sub-routines ########################
-
-sub usage () {
- print <<EOF;
-
-Usage: smime_keys <operation> [file(s) | keyID [file(s)]]
-
- with operation being one of:
-
- init : no files needed, inits directory structure.
-
- list : lists the certificates stored in database.
- label : keyID required. changes/removes/adds label.
- remove : keyID required.
- verify : 1=keyID and optionally 2=CRL
- Verifies the certificate chain, and optionally wether
- this certificate is included in supplied CRL (PEM format).
- Note: to verify all certificates at the same time,
- replace keyID with "all"
-
- add_cert : certificate required.
- add_chain : three files reqd: 1=Key, 2=certificate
- plus 3=intermediate certificate(s).
- add_p12 : one file reqd. Adds keypair to database.
- file is PKCS12 (e.g. export from netscape).
- add_pem : one file reqd. Adds keypair to database.
- (file was converted from e.g. PKCS12).
-
- add_root : one file reqd. Adds PEM root certificate to the location
- specified within muttrc (smime_verify_* command)
-
-EOF
-}
-
-sub mutt_Q ($) {
- my $var = shift or die;
-
- my $cmd = "$mutt -v >/dev/null 2>/dev/null";
- system ($cmd) == 0
- or die<<EOF;
-Couldn't launch mutt. I attempted to do so by running the command "$mutt".
-If that's not the right command, you can override it by setting the
-environment variable \$MUTT_CMDLINE
-EOF
-
- $cmd = "$mutt -Q $var 2>/dev/null";
- my $answer = `$cmd`;
-
- $? and die<<EOF;
-Couldn't look up the value of the mutt variable "$var".
-You must set this in your mutt config file. See contrib/smime.rc for an example.
-EOF
-#'
-
- $answer =~ /\"(.*?)\"/ and return bsd_glob($1, GLOB_TILDE | GLOB_NOCHECK);
-
- $answer =~ /^Mutt (.*?) / and die<<EOF;
-This script requires mutt 1.5.0 or later. You are using mutt $1.
-EOF
-
- die "Value of $var is weird\n";
-}
-
-sub mycopy ($$) {
- my $source = shift or die;
- my $dest = shift or die;
-
- copy $source, $dest or die "Problem copying $source to $dest: $!\n";
-}
-
-#
-# directory setup routines
-#
-
-
-sub mkdir_recursive ($) {
- my $path = shift or die;
- my $tmp_path;
-
- for my $dir (split /\//, $path) {
- $tmp_path .= "$dir/";
-
- -d $tmp_path
- or mkdir $tmp_path, 0700
- or die "Can't mkdir $tmp_path: $!";
- }
-}
-
-sub init_paths () {
- mkdir_recursive($certificates_path);
- mkdir_recursive($private_keys_path);
-
- my $file;
-
- $file = $certificates_path . "/.index";
- -f $file or open(TMP_FILE, ">$file") and close(TMP_FILE)
- or die "Can't touch $file: $!";
-
- $file = $private_keys_path . "/.index";
- -f $file or open(TMP_FILE, ">$file") and close(TMP_FILE)
- or die "Can't touch $file: $!";
-}
-
-
-
-#
-# certificate management methods
-#
-
-sub list_certs () {
- my %keyflags = ( 'i', '(Invalid)', 'r', '(Revoked)', 'e', '(Expired)',
- 'u', '(Unverified)', 'v', '(Valid)', 't', '(Trusted)');
-
- open(INDEX, "<$certificates_path/.index") or
- die "Couldn't open $certificates_path/.index: $!";
-
- print "\n";
- while(<INDEX>) {
- my $tmp;
- my @tmp;
- my $tab = " ";
- my @fields = split;
-
- if($fields[2] eq '-') {
- print "$fields[1]: Issued for: $fields[0] $keyflags{$fields[4]}\n";
- } else {
- print "$fields[1]: Issued for: $fields[0] \"$fields[2]\" $keyflags{$fields[4]}\n";
- }
-
- my $certfile = "$certificates_path/$fields[1]";
- my $cert;
- {
- open F, $certfile or
- die "Couldn't open $certfile: $!";
- local $/;
- $cert = <F>;
- close F;
- }
-
- my $subject_in;
- my $issuer_in;
- my $date1_in;
- my $date2_in;
-
- my $format = -B $certfile ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -subject -issuer -dates -noout -in $certfile -inform $format";
- ($subject_in, $issuer_in, $date1_in, $date2_in) = `$cmd`;
- $? and print "ERROR: '$cmd' returned $?\n\n" and next;
-
-
- my @subject = split(/\//, $subject_in);
- while(@subject) {
- $tmp = shift @subject;
- ($tmp =~ /^CN\=/) and last;
- undef $tmp;
- }
- defined $tmp and @tmp = split (/\=/, $tmp) and
- print $tab."Subject: $tmp[1]\n";
-
- my @issuer = split(/\//, $issuer_in);
- while(@issuer) {
- $tmp = shift @issuer;
- ($tmp =~ /^CN\=/) and last;
- undef $tmp;
- }
- defined $tmp and @tmp = split (/\=/, $tmp) and
- print $tab."Issued by: $tmp[1]";
-
- if ( defined $date1_in and defined $date2_in ) {
- @tmp = split (/\=/, $date1_in);
- $tmp = $tmp[1];
- @tmp = split (/\=/, $date2_in);
- print $tab."Certificate is not valid before $tmp".
- $tab." or after ".$tmp[1];
- }
-
- -e "$private_keys_path/$fields[1]" and
- print "$tab - Matching private key installed -\n";
-
- $format = -B "$certificates_path/$fields[1]" ? 'DER' : 'PEM';
- $cmd = "$opensslbin x509 -purpose -noout -in $certfile -inform $format";
- my $purpose_in = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- my @purpose = split (/\n/, $purpose_in);
- print "$tab$purpose[0] (displays S/MIME options only)\n";
- while(@purpose) {
- $tmp = shift @purpose;
- ($tmp =~ /^S\/MIME/ and $tmp =~ /Yes/) or next;
- my @tmptmp = split (/:/, $tmp);
- print "$tab $tmptmp[0]\n";
- }
-
- print "\n";
- }
-
- close(INDEX);
-}
-
-
-
-sub query_label () {
- my @words;
- my $input;
-
- print "\nYou may assign a label to this key, so you don't have to remember\n";
- print "the key ID. This has to be _one_ word (no whitespaces).\n\n";
-
- print "Enter label: ";
- chomp($input = <STDIN>);
-
- my ($label, $junk) = split(/\s/, $input, 2);
-
- defined $junk
- and print "\nUsing '$label' as label; ignoring '$junk'\n";
-
- defined $label || ($label = "-");
-
- return $label;
-}
-
-
-
-sub add_entry ($$$$$) {
- my $mailbox = shift or die;
- my $hashvalue = shift or die;
- my $use_cert = shift;
- my $label = shift or die;
- my $issuer_hash = shift;
-
- my @fields;
-
- if ($use_cert) {
- open(INDEX, "+<$certificates_path/.index") or
- die "Couldn't open $certificates_path/.index: $!";
- }
- else {
- open(INDEX, "+<$private_keys_path/.index") or
- die "Couldn't open $private_keys_path/.index: $!";
- }
-
- while(<INDEX>) {
- @fields = split;
- return if ($fields[0] eq $mailbox && $fields[1] eq $hashvalue);
- }
-
- if ($use_cert) {
- print INDEX "$mailbox $hashvalue $label $issuer_hash u\n";
- }
- else {
- print INDEX "$mailbox $hashvalue $label \n";
- }
-
- close(INDEX);
-}
-
-
-sub add_certificate ($$$$;$) {
- my $filename = shift or die;
- my $hashvalue = shift or die;
- my $add_to_index = shift;
- my $label = shift or die;
- my $issuer_hash = shift;
-
- my $iter = 0;
- my @mailbox;
- my $mailbox;
-
- while(-e "$certificates_path/$$hashvalue.$iter") {
- my ($t1, $t2);
- my $format = -B $filename ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -in $filename -inform $format -fingerprint -noout";
- $t1 = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- $format = -B "$certificates_path/$$hashvalue.$iter" ? 'DER' : 'PEM';
- $cmd = "$opensslbin x509 -in $certificates_path/$$hashvalue.$iter -inform $format -fingerprint -noout";
- $t2 = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- $t1 eq $t2 and last;
-
- $iter++;
- }
- $$hashvalue .= ".$iter";
-
- if (-e "$certificates_path/$$hashvalue") {
- print "\nCertificate: $certificates_path/$$hashvalue already installed.\n";
- }
- else {
- mycopy $filename, "$certificates_path/$$hashvalue";
-
- if ($add_to_index) {
- my $format = -B $filename ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -in $filename -inform $format -email -noout";
- @mailbox = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- foreach $mailbox (@mailbox) {
- chomp($mailbox);
- add_entry($mailbox, $$hashvalue, 1, $label, $issuer_hash);
-
- print "\ncertificate $$hashvalue ($label) for $mailbox added.\n";
- }
- verify_cert($$hashvalue, undef);
- }
- else {
- print "added certificate: $certificates_path/$$hashvalue.\n";
- }
- }
-
- return @mailbox;
-}
-
-
-sub add_key ($$$$) {
- my $file = shift or die;
- my $hashvalue = shift or die;
- my $mailbox = shift or die;
- my $label = shift or die;
-
- unless (-e "$private_keys_path/$hashvalue") {
- mycopy $file, "$private_keys_path/$hashvalue";
- }
-
- add_entry($mailbox, $hashvalue, 0, $label, "");
- print "added private key: " .
- "$private_keys_path/$hashvalue for $mailbox\n";
-}
-
-
-
-
-
-
-sub parse_pem (@) {
- my $state = 0;
- my $cert_iter = 0;
- my @bag_attribs;
- my $numBags = 0;
-
- $cert_tmp_file[$cert_iter] = newfile("cert_tmp.$cert_iter","temp");
- my $cert_tmp_iter = $cert_tmp_file[$cert_iter];
- open(CERT_FILE, ">$cert_tmp_iter")
- or die "Couldn't open $cert_tmp_iter: $!";
-
- while($_ = shift(@_)) {
- if(/^Bag Attributes/) {
- $numBags++;
- $state == 0 or die("PEM-parse error at: $.");
- $state = 1;
- $bag_attribs[$cert_iter*4+1] = "";
- $bag_attribs[$cert_iter*4+2] = "";
- $bag_attribs[$cert_iter*4+3] = "";
- }
-
- ($state == 1) and /localKeyID:\s*(.*)/
- and ($bag_attribs[$cert_iter*4+1] = $1);
-
- ($state == 1) and /subject=\s*(.*)/
- and ($bag_attribs[$cert_iter*4+2] = $1);
-
- ($state == 1) and /issuer=\s*(.*)/
- and ($bag_attribs[$cert_iter*4+3] = $1);
-
- if(/^-----/) {
- if(/BEGIN/) {
- print CERT_FILE;
- $state = 2;
-
- if(/PRIVATE/) {
- $bag_attribs[$cert_iter*4] = "K";
- next;
- }
- if(/CERTIFICATE/) {
- $bag_attribs[$cert_iter*4] = "C";
- next;
- }
- die("What's this: $_");
- }
- if(/END/) {
- $state = 0;
- print CERT_FILE;
- close(CERT_FILE);
- $cert_iter++;
- $cert_tmp_file[$cert_iter] = newfile("cert_tmp.$cert_iter","temp");
- $cert_tmp_iter = $cert_tmp_file[$cert_iter];
- open(CERT_FILE, ">$cert_tmp_iter")
- or die "Couldn't open $cert_tmp_iter: $!";
- next;
- }
- }
- print CERT_FILE;
- }
- close(CERT_FILE);
-
- # I'll add support for unbagged cetificates, in case this is needed.
- $numBags == $cert_iter or
- die("Not all contents were bagged. can't continue.");
-
- return @bag_attribs;
-}
-
-
-# This requires the Bag Attributes to be set
-sub handle_pem (@) {
-
- my @pem_contents;
- my $iter=0;
- my $root_cert;
- my $key;
- my $certificate;
- my $intermediate;
- my @mailbox;
- my $mailbox;
-
- @pem_contents = &parse_pem(@_);
-
- # private key and certificate use the same 'localKeyID'
- while($iter <= $#pem_contents / 4) {
- if($pem_contents[$iter * 4] eq "K") {
- $key = $iter;
- last;
- }
- $iter++;
- }
- ($iter > $#pem_contents / 2) and die("Couldn't find private key!");
-
- $pem_contents[($key * 4)+1] or die("Attribute 'localKeyID' wasn't set.");
-
- $iter = 0;
- while($iter <= $#pem_contents / 4) {
- $iter == $key and ($iter++) and next;
- if($pem_contents[($iter * 4)+1] eq $pem_contents[($key * 4)+1]) {
- $certificate = $iter;
- last;
- }
- $iter++;
- }
- ($iter > $#pem_contents / 4) and die("Couldn't find matching certificate!");
-
- my $tmp_key = newfile("tmp_key","temp");
- mycopy $cert_tmp_file[$key], $tmp_key;
- my $tmp_certificate = newfile("tmp_certificate","temp");
- mycopy $cert_tmp_file[$certificate], $tmp_certificate;
-
- # root certificate is self signed
- $iter = 0;
-
- while($iter <= $#pem_contents / 4) {
- if ($iter == $key or $iter == $certificate) {
- $iter++;
- next;
- }
-
- if($pem_contents[($iter * 4)+2] eq $pem_contents[($iter * 4)+3]) {
- $root_cert = $iter;
- last;
- }
- $iter++;
- }
- if ($iter > $#pem_contents / 4) {
- print "Couldn't identify root certificate!\n";
- $root_cert = -1;
- }
-
- # what's left are intermediate certificates.
- $iter = 0;
-
- # needs to be set, so we can check it later
- $intermediate = $root_cert;
- my $tmp_issuer_cert = newfile("tmp_issuer_cert","temp");
- while($iter <= $#pem_contents / 4) {
- if ($iter == $key or $iter == $certificate or $iter == $root_cert) {
- $iter++;
- next;
- }
-
- open (IC, ">> $tmp_issuer_cert") or die "can't open $tmp_issuer_cert: $?";
- my $cert_tmp_iter = $cert_tmp_file[$iter];
- open (CERT, "< $cert_tmp_iter") or die "can't open $cert_tmp_iter: $?";
- print IC while (<CERT>);
- close IC;
- close CERT;
-
- # although there may be many, just need to know if there was any
- $intermediate = $iter;
-
- $iter++;
- }
-
- # no intermediate certificates ? use root-cert instead (if that was found...)
- if($intermediate == $root_cert) {
- if ($root_cert == -1) {
- die("No root and no intermediate certificates. Can't continue.");
- }
- mycopy $cert_tmp_file[$root_cert], $tmp_issuer_cert;
- }
-
- my $label = query_label;
-
- my $format = -B $tmp_certificate ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -noout -hash -in $tmp_certificate -inform $format";
- my $cert_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- $format = -B $tmp_issuer_cert ? 'DER' : 'PEM';
- $cmd = "$opensslbin x509 -noout -hash -in $tmp_issuer_cert -inform $format";
- my $issuer_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- chomp($cert_hash); chomp($issuer_hash);
-
- # Note: $cert_hash will be changed to reflect the correct filename
- # within add_cert() ONLY, so these _have_ to get called first..
- add_certificate($tmp_issuer_cert, \$issuer_hash, 0, $label);
- @mailbox = &add_certificate("$tmp_certificate", \$cert_hash, 1, $label, $issuer_hash);
- foreach $mailbox (@mailbox) {
- chomp($mailbox);
- add_key($tmp_key, $cert_hash, $mailbox, $label);
- }
-}
-
-
-
-
-
-
-sub modify_entry ($$$;$ ) {
- my $op = shift or die;
- my $hashvalue = shift or die;
- my $use_cert = shift;
- my $crl;
- my $label;
- my $path;
- my @fields;
-
- $op eq 'L' and ($label = shift or die);
- $op eq 'V' and ($crl = shift);
-
-
- if ($use_cert) {
- $path = $certificates_path;
- }
- else {
- $path = $private_keys_path;
- }
-
- open(INDEX, "<$path/.index") or
- die "Couldn't open $path/.index: $!";
- my $newindex = newfile("$path/.index.tmp");
- open(NEW_INDEX, ">$newindex") or
- die "Couldn't create $newindex: $!";
-
- while(<INDEX>) {
- @fields = split;
- if($fields[1] eq $hashvalue or $hashvalue eq 'all') {
- $op eq 'R' and next;
- print NEW_INDEX "$fields[0] $fields[1]";
- if($op eq 'L') {
- if($use_cert) {
- print NEW_INDEX " $label $fields[3] $fields[4]";
- }
- else {
- print NEW_INDEX " $label";
- }
- }
- if ($op eq 'V') {
- print "\n==> about to verify certificate of $fields[0]\n";
- my $flag = &do_verify($fields[1], $fields[3], $crl);
- print NEW_INDEX " $fields[2] $fields[3] $flag";
- }
- print NEW_INDEX "\n";
- next;
- }
- print NEW_INDEX;
- }
- close(INDEX);
- close(NEW_INDEX);
-
- rename $newindex, "$path/.index"
- or die "Couldn't rename $newindex to $path/.index: $!\n";
-
- print "\n";
-}
-
-
-
-
-sub remove_pair ($ ) {
- my $keyid = shift or die;
-
- if (-e "$certificates_path/$keyid") {
- unlink "$certificates_path/$keyid";
- modify_entry('R', $keyid, 1);
- print "Removed certificate $keyid.\n";
- }
- else {
- die "No such certificate: $keyid";
- }
-
- if (-e "$private_keys_path/$keyid") {
- unlink "$private_keys_path/$keyid";
- modify_entry('R', $keyid, 0);
- print "Removed private key $keyid.\n";
- }
-}
-
-
-
-sub change_label ($ ) {
- my $keyid = shift or die;
-
- my $label = query_label;
-
- if (-e "$certificates_path/$keyid") {
- modify_entry('L', $keyid, 1, $label);
- print "Changed label for certificate $keyid.\n";
- }
- else {
- die "No such certificate: $keyid";
- }
-
- if (-e "$private_keys_path/$keyid") {
- modify_entry('L', $keyid, 0, $label);
- print "Changed label for private key $keyid.\n";
- }
-
-}
-
-
-
-
-sub verify_cert ($$) {
- my $keyid = shift or die;
- my $crl = shift;
-
- -e "$certificates_path/$keyid" or $keyid eq 'all'
- or die "No such certificate: $keyid";
- modify_entry('V', $keyid, 1, $crl);
-}
-
-
-
-
-sub do_verify($$$) {
-
- my $cert = shift or die;
- my $issuerid = shift or die;
- my $crl = shift;
-
- my $result = 'i';
- my $trust_q;
- my $issuer_path;
- my $cert_path = "$certificates_path/$cert";
-
- if($issuerid eq '?') {
- $issuer_path = "$certificates_path/$cert";
- } else {
- $issuer_path = "$certificates_path/$issuerid";
- }
-
- my $cmd = "$opensslbin verify $root_certs_switch $root_certs_path -purpose smimesign -purpose smimeencrypt -untrusted $issuer_path $cert_path";
- my $output = `$cmd`;
- $? and die "'$cmd' returned $?";
- chop $output;
- print "\n$output\n";
-
- ($output =~ /OK/) and ($result = 'v');
-
- $result eq 'i' and return $result;
-
- my $format = -B $cert_path ? 'DER' : 'PEM';
- $cmd = "$opensslbin x509 -dates -serial -noout -in $cert_path -inform $format";
- (my $date1_in, my $date2_in, my $serial_in) = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- if ( defined $date1_in and defined $date2_in ) {
- my @tmp = split (/\=/, $date1_in);
- my $tmp = $tmp[1];
- @tmp = split (/\=/, $date2_in);
- my %months = ('Jan', '00', 'Feb', '01', 'Mar', '02', 'Apr', '03',
- 'May', '04', 'Jun', '05', 'Jul', '06', 'Aug', '07',
- 'Sep', '08', 'Oct', '09', 'Nov', '10', 'Dec', '11');
-
- my @fields =
- $tmp =~ /(\w+)\s*(\d+)\s*(\d+):(\d+):(\d+)\s*(\d+)\s*GMT/;
-
- $#fields != 5 and print "Expiration Date: Parse Error : $tmp\n\n" or
- timegm($fields[4], $fields[3], $fields[2], $fields[1],
- $months{$fields[0]}, $fields[5]) > time and $result = 'e';
- $result eq 'e' and print "Certificate is not yet valid.\n" and return $result;
-
- @fields =
- $tmp[1] =~ /(\w+)\s*(\d+)\s*(\d+):(\d+):(\d+)\s*(\d+)\s*GMT/;
-
- $#fields != 5 and print "Expiration Date: Parse Error : $tmp[1]\n\n" or
- timegm($fields[4], $fields[3], $fields[2], $fields[1],
- $months{$fields[0]}, $fields[5]) < time and $result = 'e';
- $result eq 'e' and print "Certificate has expired.\n" and return $result;
-
- }
-
- if ( defined $crl ) {
- my @serial = split (/\=/, $serial_in);
- my $cmd = "$opensslbin crl -text -noout -in $crl | grep -A1 $serial[1]";
- (my $l1, my $l2) = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- if ( defined $l2 ) {
- my @revoke_date = split (/:\s/, $l2);
- print "FAILURE: Certificate $cert has been revoked on $revoke_date[1]\n";
- $result = 'r';
- }
- }
- print "\n";
-
- if ($result eq 'v') {
- return 't';
- }
-
- return $result;
-}
-
-
-
-sub add_root_cert ($) {
- my $root_cert = shift or die;
-
- my $format = -B $root_cert ? 'DER' : 'PEM';
-
- my $cmd = "$opensslbin x509 -noout -hash -in $root_cert -inform $format";
- my $root_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- if (-d $root_certs_path) {
- -e "$root_certs_path/$root_hash" or
- mycopy $root_cert, "$root_certs_path/$root_hash";
- }
- else {
- open(ROOT_CERTS, ">>$root_certs_path") or
- die ("Couldn't open $root_certs_path for writing");
-
- $cmd = "$opensslbin x509 -in $root_cert -inform $format -fingerprint -noout";
- $? and die "'$cmd' returned $?";
- chomp(my $md5fp = `$cmd`);
-
- $cmd = "$opensslbin x509 -in $root_cert -inform $format -text -noout";
- $? and die "'$cmd' returned $?";
- my @cert_text = `$cmd`;
-
- print "Enter a label, name or description for this certificate: ";
- my $input = <STDIN>;
-
- my $line = "=======================================\n";
- print ROOT_CERTS "\n$input$line$md5fp\nPEM-Data:\n";
-
- $cmd = "$opensslbin x509 -in $root_cert -inform $format";
- my $cert = `$cmd`;
- $? and die "'$cmd' returned $?";
- print ROOT_CERTS $cert;
- print ROOT_CERTS @cert_text;
- close (ROOT_CERTS);
- }
-
-}
-
-sub newfile ($;$$) {
- # returns a file name which does not exist for tmp file creation
- my $filename = shift;
- my $option = shift;
- $option = "notemp" if (not defined($option));
- if (! $tmpdir and $option eq "temp") {
- $tmpdir = mutt_Q 'tmpdir';
- $tmpdir = newfile("$tmpdir/smime");
- mkdir $tmpdir, 0700 || die "Can't create $tmpdir: $!\n";
- }
- $filename = "$tmpdir/$filename" if ($option eq "temp");
- my $newfilename = $filename;
- my $count = 0;
- while (-e $newfilename) {
- $newfilename = "$filename.$count";
- $count++;
- }
- unshift(@tempfiles,$newfilename);
- return $newfilename;
-}
-
-
-END {
- # remove all our temporary files in the end:
- for (@tempfiles){
- if (-f) {
- unlink;
- } elsif (-d) {
- rmdir;
- }
- }
-}
+++ /dev/null
-timestamp for config.h
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-
-
-VPATH = ..
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-EXTRA_PROGRAMS = mutt_dotlock$(EXEEXT) pgpring$(EXEEXT) \
- pgpewrap$(EXEEXT) mutt_md5$(EXEEXT)
-bin_PROGRAMS = mutt$(EXEEXT) mutt_dotlock$(EXEEXT) pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-subdir = .
-DIST_COMMON = README $(am__configure_deps) $(srcdir)/Makefile.am \
- $(srcdir)/Makefile.in $(srcdir)/config.h.in \
- $(srcdir)/hcachever.sh.in $(srcdir)/muttbug.sh.in \
- $(top_srcdir)/configure $(top_srcdir)/intl/Makefile.in \
- ABOUT-NLS ChangeLog INSTALL NEWS TODO config.guess config.sub \
- depcomp install-sh missing mkinstalldirs regex.c setenv.c \
- snprintf.c strcasecmp.c strdup.c strsep.c strtok_r.c
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
- configure.lineno config.status.lineno
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = config.h
-CONFIG_CLEAN_FILES = intl/Makefile hcachever.sh muttbug.sh
-am__installdirs = "$(DESTDIR)$(bindir)" "$(DESTDIR)$(bindir)"
-binPROGRAMS_INSTALL = $(INSTALL_PROGRAM)
-PROGRAMS = $(bin_PROGRAMS) $(noinst_PROGRAMS)
-am_mutt_OBJECTS = addrbook.$(OBJEXT) alias.$(OBJEXT) attach.$(OBJEXT) \
- base64.$(OBJEXT) browser.$(OBJEXT) buffy.$(OBJEXT) \
- color.$(OBJEXT) crypt.$(OBJEXT) cryptglue.$(OBJEXT) \
- compress.$(OBJEXT) commands.$(OBJEXT) complete.$(OBJEXT) \
- compose.$(OBJEXT) copy.$(OBJEXT) curs_lib.$(OBJEXT) \
- curs_main.$(OBJEXT) date.$(OBJEXT) edit.$(OBJEXT) \
- enter.$(OBJEXT) flags.$(OBJEXT) init.$(OBJEXT) \
- filter.$(OBJEXT) from.$(OBJEXT) getdomain.$(OBJEXT) \
- group.$(OBJEXT) handler.$(OBJEXT) hash.$(OBJEXT) \
- hdrline.$(OBJEXT) headers.$(OBJEXT) help.$(OBJEXT) \
- hook.$(OBJEXT) keymap.$(OBJEXT) main.$(OBJEXT) mbox.$(OBJEXT) \
- menu.$(OBJEXT) mh.$(OBJEXT) mx.$(OBJEXT) pager.$(OBJEXT) \
- parse.$(OBJEXT) pattern.$(OBJEXT) postpone.$(OBJEXT) \
- query.$(OBJEXT) recvattach.$(OBJEXT) recvcmd.$(OBJEXT) \
- rfc822.$(OBJEXT) rfc1524.$(OBJEXT) rfc2047.$(OBJEXT) \
- rfc2231.$(OBJEXT) rfc3676.$(OBJEXT) score.$(OBJEXT) \
- send.$(OBJEXT) sendlib.$(OBJEXT) signal.$(OBJEXT) \
- sort.$(OBJEXT) status.$(OBJEXT) system.$(OBJEXT) \
- thread.$(OBJEXT) charset.$(OBJEXT) history.$(OBJEXT) \
- lib.$(OBJEXT) muttlib.$(OBJEXT) editmsg.$(OBJEXT) \
- mbyte.$(OBJEXT) url.$(OBJEXT) ascii.$(OBJEXT) \
- crypt-mod.$(OBJEXT)
-am__objects_1 = patchlist.$(OBJEXT)
-nodist_mutt_OBJECTS = $(am__objects_1)
-mutt_OBJECTS = $(am_mutt_OBJECTS) $(nodist_mutt_OBJECTS)
-am__DEPENDENCIES_1 =
-am_mutt_dotlock_OBJECTS = mutt_dotlock.$(OBJEXT)
-mutt_dotlock_OBJECTS = $(am_mutt_dotlock_OBJECTS)
-am_mutt_md5_OBJECTS = mutt_md5-md5.$(OBJEXT)
-mutt_md5_OBJECTS = $(am_mutt_md5_OBJECTS)
-mutt_md5_DEPENDENCIES =
-mutt_md5_LINK = $(CCLD) $(mutt_md5_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) \
- $(LDFLAGS) -o $@
-pgpewrap_SOURCES = pgpewrap.c
-pgpewrap_OBJECTS = pgpewrap.$(OBJEXT)
-pgpewrap_LDADD = $(LDADD)
-pgpewrap_DEPENDENCIES =
-am_pgpring_OBJECTS = pgppubring.$(OBJEXT) pgplib.$(OBJEXT) \
- lib.$(OBJEXT) extlib.$(OBJEXT) sha1.$(OBJEXT) md5.$(OBJEXT) \
- pgppacket.$(OBJEXT) ascii.$(OBJEXT)
-pgpring_OBJECTS = $(am_pgpring_OBJECTS)
-binSCRIPT_INSTALL = $(INSTALL_SCRIPT)
-SCRIPTS = $(bin_SCRIPTS)
-DEFAULT_INCLUDES = -I. -I$(srcdir)
-depcomp = $(SHELL) $(top_srcdir)/depcomp
-am__depfiles_maybe = depfiles
-COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
- $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
-CCLD = $(CC)
-LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
-SOURCES = $(mutt_SOURCES) $(EXTRA_mutt_SOURCES) $(nodist_mutt_SOURCES) \
- $(mutt_dotlock_SOURCES) $(mutt_md5_SOURCES) pgpewrap.c \
- $(pgpring_SOURCES)
-DIST_SOURCES = $(mutt_SOURCES) $(EXTRA_mutt_SOURCES) \
- $(mutt_dotlock_SOURCES) $(mutt_md5_SOURCES) pgpewrap.c \
- $(pgpring_SOURCES)
-RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
- html-recursive info-recursive install-data-recursive \
- install-dvi-recursive install-exec-recursive \
- install-html-recursive install-info-recursive \
- install-pdf-recursive install-ps-recursive install-recursive \
- installcheck-recursive installdirs-recursive pdf-recursive \
- ps-recursive uninstall-recursive
-RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \
- distclean-recursive maintainer-clean-recursive
-ETAGS = etags
-CTAGS = ctags
-DIST_SUBDIRS = m4 po intl doc contrib imap
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-distdir = $(PACKAGE)-$(VERSION)
-top_distdir = $(distdir)
-am__remove_distdir = \
- { test ! -d $(distdir) \
- || { find $(distdir) -type d ! -perm -200 -exec chmod u+w {} ';' \
- && rm -fr $(distdir); }; }
-DIST_ARCHIVES = $(distdir).tar.gz
-GZIP_ENV = --best
-distuninstallcheck_listfiles = find . -type f -print
-distcleancheck_listfiles = find . -type f -print
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DPKGDATADIR=\"$(pkgdatadir)\" -DSYSCONFDIR=\"$(sysconfdir)\" \
- -DBINDIR=\"$(bindir)\" -DMUTTLOCALEDIR=\"$(datadir)/locale\" \
- -DHAVE_CONFIG_H=1
-
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/..
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ..
-sysconfdir = /etc
-target_alias =
-top_build_prefix =
-top_builddir = .
-top_srcdir = ..
-AUTOMAKE_OPTIONS = 1.6 foreign
-IMAP_SUBDIR = imap
-IMAP_INCLUDES = -I$(top_srcdir)/imap
-SUBDIRS = m4 po intl doc contrib $(IMAP_SUBDIR)
-bin_SCRIPTS = muttbug flea smime_keys
-BUILT_SOURCES = keymap_defs.h patchlist.c reldate.h hcversion.h
-mutt_SOURCES = \
- addrbook.c alias.c attach.c base64.c browser.c buffy.c color.c \
- crypt.c cryptglue.c compress.c \
- commands.c complete.c compose.c copy.c curs_lib.c curs_main.c date.c \
- edit.c enter.c flags.c init.c filter.c from.c \
- getdomain.c group.c \
- handler.c hash.c hdrline.c headers.c help.c hook.c keymap.c \
- main.c mbox.c menu.c mh.c mx.c pager.c parse.c pattern.c \
- postpone.c query.c recvattach.c recvcmd.c \
- rfc822.c rfc1524.c rfc2047.c rfc2231.c rfc3676.c \
- score.c send.c sendlib.c signal.c sort.c \
- status.c system.c thread.c charset.c history.c lib.c \
- muttlib.c editmsg.c mbyte.c \
- url.c ascii.c crypt-mod.c crypt-mod.h
-
-nodist_mutt_SOURCES = $(BUILT_SOURCES)
-mutt_LDADD = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o $(LIBIMAP) $(MUTTLIBS) \
- $(INTLLIBS) $(LIBICONV) $(GPGME_LIBS)
-
-mutt_DEPENDENCIES = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o $(LIBIMAPDEPS) \
- $(INTLDEPS)
-
-AM_CPPFLAGS = -I. -I$(top_srcdir) $(IMAP_INCLUDES) $(GPGME_CFLAGS) -Iintl
-EXTRA_mutt_SOURCES = account.c bcache.c crypt-gpgme.c crypt-mod-pgp-classic.c \
- crypt-mod-pgp-gpgme.c crypt-mod-smime-classic.c \
- crypt-mod-smime-gpgme.c dotlock.c gnupgparse.c hcache.c md5.c \
- mutt_idna.c mutt_sasl.c mutt_socket.c mutt_ssl.c mutt_ssl_gnutls.c \
- mutt_tunnel.c pgp.c pgpinvoke.c pgpkey.c pgplib.c pgpmicalg.c \
- pgppacket.c pop.c pop_auth.c pop_lib.c remailer.c resize.c sha1.c \
- smime.c smtp.c utf8.c wcwidth.c \
- bcache.h browser.h hcache.h mbyte.h mutt_idna.h remailer.h url.h
-
-EXTRA_DIST = COPYRIGHT GPL OPS OPS.PGP OPS.CRYPT OPS.SMIME TODO UPDATING \
- configure account.h compress.h \
- attach.h buffy.h charset.h copy.h crypthash.h dotlock.h functions.h gen_defs \
- globals.h hash.h history.h init.h keymap.h mutt_crypt.h \
- mailbox.h mapping.h md5.h mime.h mutt.h mutt_curses.h mutt_menu.h \
- mutt_regex.h mutt_sasl.h mutt_socket.h mutt_ssl.h mutt_tunnel.h \
- mx.h pager.h pgp.h pop.h protos.h rfc1524.h rfc2047.h \
- rfc2231.h rfc822.h rfc3676.h sha1.h sort.h mime.types VERSION prepare \
- _regex.h OPS.MIX README.SECURITY remailer.c remailer.h browser.h \
- mbyte.h lib.h extlib.c pgpewrap.c smime_keys.pl pgplib.h \
- README.SSL smime.h \
- muttbug pgppacket.h depcomp ascii.h BEWARE PATCHES patchlist.sh \
- ChangeLog mkchangelog.sh mutt_idna.h \
- snprintf.c regex.c crypt-gpgme.h hcachever.sh.in
-
-EXTRA_SCRIPTS = smime_keys
-mutt_dotlock_SOURCES = mutt_dotlock.c
-mutt_dotlock_LDADD =
-mutt_dotlock_DEPENDENCIES =
-pgpring_SOURCES = pgppubring.c pgplib.c lib.c extlib.c sha1.c md5.c pgppacket.c ascii.c
-pgpring_LDADD = $(INTLLIBS)
-pgpring_DEPENDENCIES = $(INTLDEPS)
-mutt_md5_SOURCES = md5.c
-mutt_md5_CFLAGS = -DMD5UTIL
-mutt_md5_LDADD =
-noinst_PROGRAMS = $(MUTT_MD5)
-CLEANFILES = mutt_dotlock.c keymap_alldefs.h $(BUILT_SOURCES)
-DISTCLEANFILES = flea smime_keys
-ACLOCAL_AMFLAGS = -I m4
-LDADD =
-all: $(BUILT_SOURCES) config.h
- $(MAKE) $(AM_MAKEFLAGS) all-recursive
-
-.SUFFIXES:
-.SUFFIXES: .c .o .obj
-am--refresh:
- @:
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- echo ' cd $(srcdir) && $(AUTOMAKE) --foreign '; \
- cd $(srcdir) && $(AUTOMAKE) --foreign \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --foreign Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- echo ' $(SHELL) ./config.status'; \
- $(SHELL) ./config.status;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- $(SHELL) ./config.status --recheck
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(srcdir) && $(AUTOCONF)
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
-
-config.h: stamp-h1
- @if test ! -f $@; then \
- rm -f stamp-h1; \
- $(MAKE) $(AM_MAKEFLAGS) stamp-h1; \
- else :; fi
-
-stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status
- @rm -f stamp-h1
- cd $(top_builddir) && $(SHELL) ./config.status config.h
-$(srcdir)/config.h.in: # $(am__configure_deps)
- cd $(top_srcdir) && $(AUTOHEADER)
- rm -f stamp-h1
- touch $@
-
-distclean-hdr:
- -rm -f config.h stamp-h1
-intl/Makefile: $(top_builddir)/config.status $(top_srcdir)/intl/Makefile.in
- cd $(top_builddir) && $(SHELL) ./config.status $@
-hcachever.sh: $(top_builddir)/config.status $(srcdir)/hcachever.sh.in
- cd $(top_builddir) && $(SHELL) ./config.status $@
-muttbug.sh: $(top_builddir)/config.status $(srcdir)/muttbug.sh.in
- cd $(top_builddir) && $(SHELL) ./config.status $@
-install-binPROGRAMS: $(bin_PROGRAMS)
- @$(NORMAL_INSTALL)
- test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)"
- @list='$(bin_PROGRAMS)'; for p in $$list; do \
- p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \
- if test -f $$p \
- ; then \
- f=`echo "$$p1" | sed 's,^.*/,,;$(transform);s/$$/$(EXEEXT)/'`; \
- echo " $(INSTALL_PROGRAM_ENV) $(binPROGRAMS_INSTALL) '$$p' '$(DESTDIR)$(bindir)/$$f'"; \
- $(INSTALL_PROGRAM_ENV) $(binPROGRAMS_INSTALL) "$$p" "$(DESTDIR)$(bindir)/$$f" || exit 1; \
- else :; fi; \
- done
-
-uninstall-binPROGRAMS:
- @$(NORMAL_UNINSTALL)
- @list='$(bin_PROGRAMS)'; for p in $$list; do \
- f=`echo "$$p" | sed 's,^.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/'`; \
- echo " rm -f '$(DESTDIR)$(bindir)/$$f'"; \
- rm -f "$(DESTDIR)$(bindir)/$$f"; \
- done
-
-clean-binPROGRAMS:
- -test -z "$(bin_PROGRAMS)" || rm -f $(bin_PROGRAMS)
-
-clean-noinstPROGRAMS:
- -test -z "$(noinst_PROGRAMS)" || rm -f $(noinst_PROGRAMS)
-mutt$(EXEEXT): $(mutt_OBJECTS) $(mutt_DEPENDENCIES)
- @rm -f mutt$(EXEEXT)
- $(LINK) $(mutt_OBJECTS) $(mutt_LDADD) $(LIBS)
-mutt_dotlock$(EXEEXT): $(mutt_dotlock_OBJECTS) $(mutt_dotlock_DEPENDENCIES)
- @rm -f mutt_dotlock$(EXEEXT)
- $(LINK) $(mutt_dotlock_OBJECTS) $(mutt_dotlock_LDADD) $(LIBS)
-mutt_md5$(EXEEXT): $(mutt_md5_OBJECTS) $(mutt_md5_DEPENDENCIES)
- @rm -f mutt_md5$(EXEEXT)
- $(mutt_md5_LINK) $(mutt_md5_OBJECTS) $(mutt_md5_LDADD) $(LIBS)
-pgpewrap$(EXEEXT): $(pgpewrap_OBJECTS) $(pgpewrap_DEPENDENCIES)
- @rm -f pgpewrap$(EXEEXT)
- $(LINK) $(pgpewrap_OBJECTS) $(pgpewrap_LDADD) $(LIBS)
-pgpring$(EXEEXT): $(pgpring_OBJECTS) $(pgpring_DEPENDENCIES)
- @rm -f pgpring$(EXEEXT)
- $(LINK) $(pgpring_OBJECTS) $(pgpring_LDADD) $(LIBS)
-install-binSCRIPTS: $(bin_SCRIPTS)
- @$(NORMAL_INSTALL)
- test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)"
- @list='$(bin_SCRIPTS)'; for p in $$list; do \
- if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
- if test -f $$d$$p; then \
- f=`echo "$$p" | sed 's|^.*/||;$(transform)'`; \
- echo " $(binSCRIPT_INSTALL) '$$d$$p' '$(DESTDIR)$(bindir)/$$f'"; \
- $(binSCRIPT_INSTALL) "$$d$$p" "$(DESTDIR)$(bindir)/$$f"; \
- else :; fi; \
- done
-
-uninstall-binSCRIPTS:
- @$(NORMAL_UNINSTALL)
- @list='$(bin_SCRIPTS)'; for p in $$list; do \
- f=`echo "$$p" | sed 's|^.*/||;$(transform)'`; \
- echo " rm -f '$(DESTDIR)$(bindir)/$$f'"; \
- rm -f "$(DESTDIR)$(bindir)/$$f"; \
- done
-
-mostlyclean-compile:
- -rm -f *.$(OBJEXT)
-
-distclean-compile:
- -rm -f *.tab.c
-
-#include $(DEPDIR)/regex.Po
-#include $(DEPDIR)/setenv.Po
-#include $(DEPDIR)/snprintf.Po
-#include $(DEPDIR)/strcasecmp.Po
-#include $(DEPDIR)/strdup.Po
-#include $(DEPDIR)/strsep.Po
-#include $(DEPDIR)/strtok_r.Po
-#include ./$(DEPDIR)/account.Po
-#include ./$(DEPDIR)/addrbook.Po
-#include ./$(DEPDIR)/alias.Po
-#include ./$(DEPDIR)/ascii.Po
-#include ./$(DEPDIR)/attach.Po
-#include ./$(DEPDIR)/base64.Po
-#include ./$(DEPDIR)/bcache.Po
-#include ./$(DEPDIR)/browser.Po
-#include ./$(DEPDIR)/buffy.Po
-#include ./$(DEPDIR)/charset.Po
-#include ./$(DEPDIR)/color.Po
-#include ./$(DEPDIR)/commands.Po
-#include ./$(DEPDIR)/complete.Po
-#include ./$(DEPDIR)/compose.Po
-#include ./$(DEPDIR)/compress.Po
-#include ./$(DEPDIR)/copy.Po
-#include ./$(DEPDIR)/crypt-gpgme.Po
-#include ./$(DEPDIR)/crypt-mod-pgp-classic.Po
-#include ./$(DEPDIR)/crypt-mod-pgp-gpgme.Po
-#include ./$(DEPDIR)/crypt-mod-smime-classic.Po
-#include ./$(DEPDIR)/crypt-mod-smime-gpgme.Po
-#include ./$(DEPDIR)/crypt-mod.Po
-#include ./$(DEPDIR)/crypt.Po
-#include ./$(DEPDIR)/cryptglue.Po
-#include ./$(DEPDIR)/curs_lib.Po
-#include ./$(DEPDIR)/curs_main.Po
-#include ./$(DEPDIR)/date.Po
-#include ./$(DEPDIR)/dotlock.Po
-#include ./$(DEPDIR)/edit.Po
-#include ./$(DEPDIR)/editmsg.Po
-#include ./$(DEPDIR)/enter.Po
-#include ./$(DEPDIR)/extlib.Po
-#include ./$(DEPDIR)/filter.Po
-#include ./$(DEPDIR)/flags.Po
-#include ./$(DEPDIR)/from.Po
-#include ./$(DEPDIR)/getdomain.Po
-#include ./$(DEPDIR)/gnupgparse.Po
-#include ./$(DEPDIR)/group.Po
-#include ./$(DEPDIR)/handler.Po
-#include ./$(DEPDIR)/hash.Po
-#include ./$(DEPDIR)/hcache.Po
-#include ./$(DEPDIR)/hdrline.Po
-#include ./$(DEPDIR)/headers.Po
-#include ./$(DEPDIR)/help.Po
-#include ./$(DEPDIR)/history.Po
-#include ./$(DEPDIR)/hook.Po
-#include ./$(DEPDIR)/init.Po
-#include ./$(DEPDIR)/keymap.Po
-#include ./$(DEPDIR)/lib.Po
-#include ./$(DEPDIR)/main.Po
-#include ./$(DEPDIR)/mbox.Po
-#include ./$(DEPDIR)/mbyte.Po
-#include ./$(DEPDIR)/md5.Po
-#include ./$(DEPDIR)/menu.Po
-#include ./$(DEPDIR)/mh.Po
-#include ./$(DEPDIR)/mutt_dotlock.Po
-#include ./$(DEPDIR)/mutt_idna.Po
-#include ./$(DEPDIR)/mutt_md5-md5.Po
-#include ./$(DEPDIR)/mutt_sasl.Po
-#include ./$(DEPDIR)/mutt_socket.Po
-#include ./$(DEPDIR)/mutt_ssl.Po
-#include ./$(DEPDIR)/mutt_ssl_gnutls.Po
-#include ./$(DEPDIR)/mutt_tunnel.Po
-#include ./$(DEPDIR)/muttlib.Po
-#include ./$(DEPDIR)/mx.Po
-#include ./$(DEPDIR)/pager.Po
-#include ./$(DEPDIR)/parse.Po
-#include ./$(DEPDIR)/patchlist.Po
-#include ./$(DEPDIR)/pattern.Po
-#include ./$(DEPDIR)/pgp.Po
-#include ./$(DEPDIR)/pgpewrap.Po
-#include ./$(DEPDIR)/pgpinvoke.Po
-#include ./$(DEPDIR)/pgpkey.Po
-#include ./$(DEPDIR)/pgplib.Po
-#include ./$(DEPDIR)/pgpmicalg.Po
-#include ./$(DEPDIR)/pgppacket.Po
-#include ./$(DEPDIR)/pgppubring.Po
-#include ./$(DEPDIR)/pop.Po
-#include ./$(DEPDIR)/pop_auth.Po
-#include ./$(DEPDIR)/pop_lib.Po
-#include ./$(DEPDIR)/postpone.Po
-#include ./$(DEPDIR)/query.Po
-#include ./$(DEPDIR)/recvattach.Po
-#include ./$(DEPDIR)/recvcmd.Po
-#include ./$(DEPDIR)/remailer.Po
-#include ./$(DEPDIR)/resize.Po
-#include ./$(DEPDIR)/rfc1524.Po
-#include ./$(DEPDIR)/rfc2047.Po
-#include ./$(DEPDIR)/rfc2231.Po
-#include ./$(DEPDIR)/rfc3676.Po
-#include ./$(DEPDIR)/rfc822.Po
-#include ./$(DEPDIR)/score.Po
-#include ./$(DEPDIR)/send.Po
-#include ./$(DEPDIR)/sendlib.Po
-#include ./$(DEPDIR)/sha1.Po
-#include ./$(DEPDIR)/signal.Po
-#include ./$(DEPDIR)/smime.Po
-#include ./$(DEPDIR)/smtp.Po
-#include ./$(DEPDIR)/sort.Po
-#include ./$(DEPDIR)/status.Po
-#include ./$(DEPDIR)/system.Po
-#include ./$(DEPDIR)/thread.Po
-#include ./$(DEPDIR)/url.Po
-#include ./$(DEPDIR)/utf8.Po
-#include ./$(DEPDIR)/wcwidth.Po
-
-.c.o:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c $<
-
-.c.obj:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'`
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c `$(CYGPATH_W) '$<'`
-
-mutt_md5-md5.o: md5.c
-# $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -MT mutt_md5-md5.o -MD -MP -MF $(DEPDIR)/mutt_md5-md5.Tpo -c -o mutt_md5-md5.o `test -f 'md5.c' || echo '$(srcdir)/'`md5.c
-# mv -f $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po
-# source='md5.c' object='mutt_md5-md5.o' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -c -o mutt_md5-md5.o `test -f 'md5.c' || echo '$(srcdir)/'`md5.c
-
-mutt_md5-md5.obj: md5.c
-# $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -MT mutt_md5-md5.obj -MD -MP -MF $(DEPDIR)/mutt_md5-md5.Tpo -c -o mutt_md5-md5.obj `if test -f 'md5.c'; then $(CYGPATH_W) 'md5.c'; else $(CYGPATH_W) '$(srcdir)/md5.c'; fi`
-# mv -f $(DEPDIR)/mutt_md5-md5.Tpo $(DEPDIR)/mutt_md5-md5.Po
-# source='md5.c' object='mutt_md5-md5.obj' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(mutt_md5_CFLAGS) $(CFLAGS) -c -o mutt_md5-md5.obj `if test -f 'md5.c'; then $(CYGPATH_W) 'md5.c'; else $(CYGPATH_W) '$(srcdir)/md5.c'; fi`
-
-# This directory's subdirectories are mostly independent; you can cd
-# into them and run `make' without going through this Makefile.
-# To change the values of `make' variables: instead of editing Makefiles,
-# (1) if the variable is set in `config.status', edit `config.status'
-# (which will cause the Makefiles to be regenerated when you run `make');
-# (2) otherwise, pass the desired values on the `make' command line.
-$(RECURSIVE_TARGETS):
- @failcom='exit 1'; \
- for f in x $$MAKEFLAGS; do \
- case $$f in \
- *=* | --[!k]*);; \
- *k*) failcom='fail=yes';; \
- esac; \
- done; \
- dot_seen=no; \
- target=`echo $@ | sed s/-recursive//`; \
- list='$(SUBDIRS)'; for subdir in $$list; do \
- echo "Making $$target in $$subdir"; \
- if test "$$subdir" = "."; then \
- dot_seen=yes; \
- local_target="$$target-am"; \
- else \
- local_target="$$target"; \
- fi; \
- (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
- || eval $$failcom; \
- done; \
- if test "$$dot_seen" = "no"; then \
- $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
- fi; test -z "$$fail"
-
-$(RECURSIVE_CLEAN_TARGETS):
- @failcom='exit 1'; \
- for f in x $$MAKEFLAGS; do \
- case $$f in \
- *=* | --[!k]*);; \
- *k*) failcom='fail=yes';; \
- esac; \
- done; \
- dot_seen=no; \
- case "$@" in \
- distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
- *) list='$(SUBDIRS)' ;; \
- esac; \
- rev=''; for subdir in $$list; do \
- if test "$$subdir" = "."; then :; else \
- rev="$$subdir $$rev"; \
- fi; \
- done; \
- rev="$$rev ."; \
- target=`echo $@ | sed s/-recursive//`; \
- for subdir in $$rev; do \
- echo "Making $$target in $$subdir"; \
- if test "$$subdir" = "."; then \
- local_target="$$target-am"; \
- else \
- local_target="$$target"; \
- fi; \
- (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
- || eval $$failcom; \
- done && test -z "$$fail"
-tags-recursive:
- list='$(SUBDIRS)'; for subdir in $$list; do \
- test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
- done
-ctags-recursive:
- list='$(SUBDIRS)'; for subdir in $$list; do \
- test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
- done
-
-ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- mkid -fID $$unique
-tags: TAGS
-
-TAGS: tags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- here=`pwd`; \
- if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
- include_option=--etags-include; \
- empty_fix=.; \
- else \
- include_option=--include; \
- empty_fix=; \
- fi; \
- list='$(SUBDIRS)'; for subdir in $$list; do \
- if test "$$subdir" = .; then :; else \
- test ! -f $$subdir/TAGS || \
- tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
- fi; \
- done; \
- list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
- test -n "$$unique" || unique=$$empty_fix; \
- $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
- $$tags $$unique; \
- fi
-ctags: CTAGS
-CTAGS: ctags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- test -z "$(CTAGS_ARGS)$$tags$$unique" \
- || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
- $$tags $$unique
-
-GTAGS:
- here=`$(am__cd) $(top_builddir) && pwd` \
- && cd $(top_srcdir) \
- && gtags -i $(GTAGS_ARGS) $$here
-
-distclean-tags:
- -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
-distdir: $(DISTFILES)
- $(am__remove_distdir)
- test -d $(distdir) || mkdir $(distdir)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
- list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
- if test "$$subdir" = .; then :; else \
- test -d "$(distdir)/$$subdir" \
- || $(MKDIR_P) "$(distdir)/$$subdir" \
- || exit 1; \
- distdir=`$(am__cd) $(distdir) && pwd`; \
- top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
- (cd $$subdir && \
- $(MAKE) $(AM_MAKEFLAGS) \
- top_distdir="$$top_distdir" \
- distdir="$$distdir/$$subdir" \
- am__remove_distdir=: \
- am__skip_length_check=: \
- distdir) \
- || exit 1; \
- fi; \
- done
- -find $(distdir) -type d ! -perm -777 -exec chmod a+rwx {} \; -o \
- ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \
- ! -type d ! -perm -400 -exec chmod a+r {} \; -o \
- ! -type d ! -perm -444 -exec $(install_sh) -c -m a+r {} {} \; \
- || chmod -R a+r $(distdir)
-dist-gzip: distdir
- tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
- $(am__remove_distdir)
-
-dist-bzip2: distdir
- tardir=$(distdir) && $(am__tar) | bzip2 -9 -c >$(distdir).tar.bz2
- $(am__remove_distdir)
-
-dist-lzma: distdir
- tardir=$(distdir) && $(am__tar) | lzma -9 -c >$(distdir).tar.lzma
- $(am__remove_distdir)
-
-dist-tarZ: distdir
- tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z
- $(am__remove_distdir)
-
-dist-shar: distdir
- shar $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).shar.gz
- $(am__remove_distdir)
-
-dist-zip: distdir
- -rm -f $(distdir).zip
- zip -rq $(distdir).zip $(distdir)
- $(am__remove_distdir)
-
-dist dist-all: distdir
- tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
- $(am__remove_distdir)
-
-# This target untars the dist file and tries a VPATH configuration. Then
-# it guarantees that the distribution is self-contained by making another
-# tarfile.
-distcheck: dist
- case '$(DIST_ARCHIVES)' in \
- *.tar.gz*) \
- GZIP=$(GZIP_ENV) gunzip -c $(distdir).tar.gz | $(am__untar) ;;\
- *.tar.bz2*) \
- bunzip2 -c $(distdir).tar.bz2 | $(am__untar) ;;\
- *.tar.lzma*) \
- unlzma -c $(distdir).tar.lzma | $(am__untar) ;;\
- *.tar.Z*) \
- uncompress -c $(distdir).tar.Z | $(am__untar) ;;\
- *.shar.gz*) \
- GZIP=$(GZIP_ENV) gunzip -c $(distdir).shar.gz | unshar ;;\
- *.zip*) \
- unzip $(distdir).zip ;;\
- esac
- chmod -R a-w $(distdir); chmod a+w $(distdir)
- mkdir $(distdir)/_build
- mkdir $(distdir)/_inst
- chmod a-w $(distdir)
- dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \
- && dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \
- && cd $(distdir)/_build \
- && ../configure --srcdir=.. --prefix="$$dc_install_base" \
- $(DISTCHECK_CONFIGURE_FLAGS) \
- && $(MAKE) $(AM_MAKEFLAGS) \
- && $(MAKE) $(AM_MAKEFLAGS) dvi \
- && $(MAKE) $(AM_MAKEFLAGS) check \
- && $(MAKE) $(AM_MAKEFLAGS) install \
- && $(MAKE) $(AM_MAKEFLAGS) installcheck \
- && $(MAKE) $(AM_MAKEFLAGS) uninstall \
- && $(MAKE) $(AM_MAKEFLAGS) distuninstallcheck_dir="$$dc_install_base" \
- distuninstallcheck \
- && chmod -R a-w "$$dc_install_base" \
- && ({ \
- (cd ../.. && umask 077 && mkdir "$$dc_destdir") \
- && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" install \
- && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" uninstall \
- && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" \
- distuninstallcheck_dir="$$dc_destdir" distuninstallcheck; \
- } || { rm -rf "$$dc_destdir"; exit 1; }) \
- && rm -rf "$$dc_destdir" \
- && $(MAKE) $(AM_MAKEFLAGS) dist \
- && rm -rf $(DIST_ARCHIVES) \
- && $(MAKE) $(AM_MAKEFLAGS) distcleancheck
- $(am__remove_distdir)
- @(echo "$(distdir) archives ready for distribution: "; \
- list='$(DIST_ARCHIVES)'; for i in $$list; do echo $$i; done) | \
- sed -e 1h -e 1s/./=/g -e 1p -e 1x -e '$$p' -e '$$x'
-distuninstallcheck:
- @cd $(distuninstallcheck_dir) \
- && test `$(distuninstallcheck_listfiles) | wc -l` -le 1 \
- || { echo "ERROR: files left after uninstall:" ; \
- if test -n "$(DESTDIR)"; then \
- echo " (check DESTDIR support)"; \
- fi ; \
- $(distuninstallcheck_listfiles) ; \
- exit 1; } >&2
-distcleancheck: distclean
- @if test '$(srcdir)' = . ; then \
- echo "ERROR: distcleancheck can only run from a VPATH build" ; \
- exit 1 ; \
- fi
- @test `$(distcleancheck_listfiles) | wc -l` -eq 0 \
- || { echo "ERROR: files left in build directory after distclean:" ; \
- $(distcleancheck_listfiles) ; \
- exit 1; } >&2
-check-am: all-am
-check: $(BUILT_SOURCES)
- $(MAKE) $(AM_MAKEFLAGS) check-recursive
-all-am: Makefile $(PROGRAMS) $(SCRIPTS) config.h
-installdirs: installdirs-recursive
-installdirs-am:
- for dir in "$(DESTDIR)$(bindir)" "$(DESTDIR)$(bindir)"; do \
- test -z "$$dir" || $(MKDIR_P) "$$dir"; \
- done
-install: $(BUILT_SOURCES)
- $(MAKE) $(AM_MAKEFLAGS) install-recursive
-install-exec: install-exec-recursive
-install-data: install-data-recursive
-uninstall: uninstall-recursive
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-recursive
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
- -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES)
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
- -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
- -test -z "$(BUILT_SOURCES)" || rm -f $(BUILT_SOURCES)
-clean: clean-recursive
-
-clean-am: clean-binPROGRAMS clean-generic clean-noinstPROGRAMS \
- mostlyclean-am
-
-distclean: distclean-recursive
- -rm -f $(am__CONFIG_DISTCLEAN_FILES)
- -rm -rf $(DEPDIR) ./$(DEPDIR)
- -rm -f Makefile
-distclean-am: clean-am distclean-compile distclean-generic \
- distclean-hdr distclean-tags
-
-dvi: dvi-recursive
-
-dvi-am:
-
-html: html-recursive
-
-info: info-recursive
-
-info-am:
-
-install-data-am: install-data-local
-
-install-dvi: install-dvi-recursive
-
-install-exec-am: install-binPROGRAMS install-binSCRIPTS
- @$(NORMAL_INSTALL)
- $(MAKE) $(AM_MAKEFLAGS) install-exec-hook
-
-install-html: install-html-recursive
-
-install-info: install-info-recursive
-
-install-man:
-
-install-pdf: install-pdf-recursive
-
-install-ps: install-ps-recursive
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-recursive
- -rm -f $(am__CONFIG_DISTCLEAN_FILES)
- -rm -rf $(top_srcdir)/autom4te.cache
- -rm -rf $(DEPDIR) ./$(DEPDIR)
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-recursive
-
-mostlyclean-am: mostlyclean-compile mostlyclean-generic
-
-pdf: pdf-recursive
-
-pdf-am:
-
-ps: ps-recursive
-
-ps-am:
-
-uninstall-am: uninstall-binPROGRAMS uninstall-binSCRIPTS \
- uninstall-local
-
-.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
- install-exec-am install-strip
-
-.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
- all all-am am--refresh check check-am clean clean-binPROGRAMS \
- clean-generic clean-noinstPROGRAMS ctags ctags-recursive dist \
- dist-all dist-bzip2 dist-gzip dist-lzma dist-shar dist-tarZ \
- dist-zip distcheck distclean distclean-compile \
- distclean-generic distclean-hdr distclean-tags distcleancheck \
- distdir distuninstallcheck dvi dvi-am html html-am info \
- info-am install install-am install-binPROGRAMS \
- install-binSCRIPTS install-data install-data-am \
- install-data-local install-dvi install-dvi-am install-exec \
- install-exec-am install-exec-hook install-html install-html-am \
- install-info install-info-am install-man install-pdf \
- install-pdf-am install-ps install-ps-am install-strip \
- installcheck installcheck-am installdirs installdirs-am \
- maintainer-clean maintainer-clean-generic mostlyclean \
- mostlyclean-compile mostlyclean-generic pdf pdf-am ps ps-am \
- tags tags-recursive uninstall uninstall-am \
- uninstall-binPROGRAMS uninstall-binSCRIPTS uninstall-local
-
-
-mutt_dotlock.c: dotlock.c
- cp $(srcdir)/dotlock.c mutt_dotlock.c
-
-flea: muttbug.sh
- cp muttbug.sh flea
- chmod +x flea
-
-smime_keys: $(srcdir)/smime_keys.pl
- cp $(srcdir)/smime_keys.pl smime_keys
- chmod +x smime_keys
-
-keymap_defs.h: $(OPS) $(srcdir)/gen_defs
- $(srcdir)/gen_defs $(OPS) > keymap_defs.h
-
-keymap_alldefs.h: $(srcdir)/OPS $(srcdir)/OPS.PGP $(srcdir)/OPS.MIX $(srcdir)/OPS.CRYPT $(srcdir)/OPS.SMIME $(srcdir)/gen_defs
- rm -f $@
- $(srcdir)/gen_defs $(srcdir)/OPS $(srcdir)/OPS.PGP \
- $(srcdir)/OPS.MIX $(srcdir)/OPS.CRYPT $(srcdir)/OPS.SMIME \
- > keymap_alldefs.h
-
-reldate.h: $(srcdir)/ChangeLog
- echo 'const char *ReleaseDate = "'`head -n 1 $(srcdir)/ChangeLog | LC_ALL=C cut -d ' ' -f 1`'";' > reldate.h.tmp; \
- cmp -s reldate.h.tmp reldate.h || cp reldate.h.tmp reldate.h; \
- rm reldate.h.tmp
-
-hcversion.h: $(srcdir)/mutt.h $(srcdir)/rfc822.h hcachever.sh $(MUTT_MD5)
- ( echo '#include "config.h"'; echo '#include "mutt.h"'; ) \
- | $(CPP) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) - | sh ./hcachever.sh hcversion.h
-
-patchlist.c: $(srcdir)/PATCHES $(srcdir)/patchlist.sh
- $(srcdir)/patchlist.sh < $(srcdir)/PATCHES > patchlist.c
-
-install-exec-hook:
- if test -f $(DESTDIR)$(bindir)/mutt.dotlock && test -f $(DESTDIR)$(bindir)/mutt_dotlock ; then \
- rm -f $(DESTDIR)$(bindir)/mutt.dotlock ; \
- ln -sf $(DESTDIR)$(bindir)/mutt_dotlock $(DESTDIR)$(bindir)/mutt.dotlock ; \
- fi
- if test -f $(DESTDIR)$(bindir)/mutt_dotlock && test xmail != x ; then \
- chgrp mail $(DESTDIR)$(bindir)/mutt_dotlock && \
- chmod 2755 $(DESTDIR)$(bindir)/mutt_dotlock || \
- { echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
- fi
-
-install-data-local:
- $(srcdir)/mkinstalldirs $(DESTDIR)$(sysconfdir)
- $(INSTALL) -m 644 $(srcdir)/mime.types $(DESTDIR)$(sysconfdir)/mime.types.dist
- -if [ ! -f $(DESTDIR)$(sysconfdir)/mime.types ]; then \
- $(INSTALL) -m 644 $(srcdir)/mime.types $(DESTDIR)$(sysconfdir); \
- fi
-
-uninstall-local:
- for i in mime.types ; do \
- if cmp -s $(DESTDIR)$(sysconfdir)/$$i.dist $(DESTDIR)$(sysconfdir)/$$i ; then \
- rm $(DESTDIR)$(sysconfdir)/$$i ; \
- fi ; \
- rm $(DESTDIR)$(sysconfdir)/$${i}.dist ; \
- done
-
-pclean:
- cat /dev/null > $(top_srcdir)/PATCHES
-
-check-security:
- (cd $(top_srcdir) && ./check_sec.sh)
-
-commit:
- @echo "make commit is obsolete; use hg-commit"; false
-
-update-changelog:
- (cd $(top_srcdir); \
- sh ./mkchangelog.sh | cat - ChangeLog > ChangeLog.$$$$ && mv ChangeLog.$$$$ ChangeLog; \
- $${VISUAL:-vi} ChangeLog)
-
-mutt-dist:
- (cd $(srcdir) && ./build-release )
-
-update-doc:
- (cd doc && $(MAKE) update-doc)
-
-.PHONY: commit pclean check-security
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-/* config.h. Generated from config.h.in by configure. */
-/* config.h.in. Generated from configure.ac by autoheader. */
-
-/* Define if building universal (internal helper macro) */
-/* #undef AC_APPLE_UNIVERSAL_BUILD */
-
-/* Define to one of `_getb67', `GETB67', `getb67' for Cray-2 and Cray-YMP
- systems. This function is required for `alloca.c' support on those systems.
- */
-/* #undef CRAY_STACKSEG_END */
-
-/* Define if you want classic PGP support. */
-#define CRYPT_BACKEND_CLASSIC_PGP 1
-
-/* Define if you want clasic S/MIME support. */
-#define CRYPT_BACKEND_CLASSIC_SMIME 1
-
-/* Define if you use GPGME to support OpenPGP */
-#define CRYPT_BACKEND_GPGME 1
-
-/* Define to 1 if using `alloca.c'. */
-/* #undef C_ALLOCA */
-
-/* Define to enable debugging info. */
-#define DEBUG 1
-
-/* Define if you want to use an external dotlocking program. */
-#define DL_STANDALONE 1
-
-/* Define your domain name. */
-/* #undef DOMAIN */
-
-/* Define to 1 if translation of program messages to the user's native
- language is requested. */
-#define ENABLE_NLS 1
-
-/* Enable exact regeneration of email addresses as parsed? NOTE: this requires
- significant more memory when defined. */
-/* #undef EXACT_ADDRESS */
-
-/* program to use for shell commands */
-#define EXECSHELL "/bin/sh"
-
-/* Define to 1 if you have `alloca', as a function or macro. */
-#define HAVE_ALLOCA 1
-
-/* Define to 1 if you have <alloca.h> and it should be used (not on Ultrix).
- */
-#define HAVE_ALLOCA_H 1
-
-/* Define to 1 if you have the <argz.h> header file. */
-#define HAVE_ARGZ_H 1
-
-/* Define to 1 if you have the `bind_textdomain_codeset' function. */
-#define HAVE_BIND_TEXTDOMAIN_CODESET 1
-
-/* Define if you have bkgdset, as a function or macro. */
-#define HAVE_BKGDSET 1
-
-/* Define if you have the C99 integer types */
-#define HAVE_C99_INTTYPES 1
-
-/* Define if your curses library supports color. */
-#define HAVE_COLOR 1
-
-/* Define if you have curs_set, as a function or macro. */
-#define HAVE_CURS_SET 1
-
-/* Berkeley DB4 Support */
-/* #undef HAVE_DB4 */
-
-/* Define to 1 if you have the `dcgettext' function. */
-#define HAVE_DCGETTEXT 1
-
-/* Define to 1 if you have the declaration of `sys_siglist', and to 0 if you
- don't. */
-#define HAVE_DECL_SYS_SIGLIST 1
-
-/* Define to 1 if your system has the dirent::d_ino member */
-#define HAVE_DIRENT_D_INO 1
-
-/* Define to 1 if you have the `fchdir' function. */
-#define HAVE_FCHDIR 1
-
-/* Define to 1 if you have the `feof_unlocked' function. */
-#define HAVE_FEOF_UNLOCKED 1
-
-/* Define to 1 if you have the `fgetpos' function. */
-#define HAVE_FGETPOS 1
-
-/* Define to 1 if you have the `fgets_unlocked' function. */
-#define HAVE_FGETS_UNLOCKED 1
-
-/* Define to 1 if fseeko (and presumably ftello) exists and is declared. */
-#define HAVE_FSEEKO 1
-
-/* Define to 1 if you have the `ftruncate' function. */
-#define HAVE_FTRUNCATE 1
-
-/* GDBM Support */
-#define HAVE_GDBM 1
-
-/* Define to 1 if you have the `getaddrinfo' function. */
-#define HAVE_GETADDRINFO 1
-
-/* Define to 1 if you have the `getcwd' function. */
-#define HAVE_GETCWD 1
-
-/* Define to 1 if you have the `getegid' function. */
-#define HAVE_GETEGID 1
-
-/* Define to 1 if you have the `geteuid' function. */
-#define HAVE_GETEUID 1
-
-/* Define to 1 if you have the `getgid' function. */
-#define HAVE_GETGID 1
-
-/* Define to 1 if you have the <getopt.h> header file. */
-#define HAVE_GETOPT_H 1
-
-/* Define to 1 if you have the `getpagesize' function. */
-#define HAVE_GETPAGESIZE 1
-
-/* Define to 1 if you have the `getsid' function. */
-#define HAVE_GETSID 1
-
-/* Define if the GNU gettext() function is already present or preinstalled. */
-#define HAVE_GETTEXT 1
-
-/* Define to 1 if you have the `getuid' function. */
-#define HAVE_GETUID 1
-
-/* Define if GPGME supports PKA */
-#define HAVE_GPGME_PKA_TRUST 1
-
-/* Define if your GSSAPI implementation is Heimdal */
-/* #undef HAVE_HEIMDAL */
-
-/* Define if you have the iconv() function. */
-#define HAVE_ICONV 1
-
-/* Define to 1 if you have the <iconv.h> header file. */
-#define HAVE_ICONV_H 1
-
-/* Define if <iconv.h> defines iconv_t. */
-#define HAVE_ICONV_T_DEF 1
-
-/* Define to 1 if you have the `idna_to_ascii_8z' function. */
-#define HAVE_IDNA_TO_ASCII_8Z 1
-
-/* Define to 1 if you have the `idna_to_ascii_from_locale' function. */
-/* #undef HAVE_IDNA_TO_ASCII_FROM_LOCALE */
-
-/* Define to 1 if you have the `idna_to_ascii_from_utf8' function. */
-/* #undef HAVE_IDNA_TO_ASCII_FROM_UTF8 */
-
-/* Define to 1 if you have the `idna_to_ascii_lz' function. */
-#define HAVE_IDNA_TO_ASCII_LZ 1
-
-/* Define to 1 if you have the `idna_to_unicode_8z8z' function. */
-#define HAVE_IDNA_TO_UNICODE_8Z8Z 1
-
-/* Define to 1 if you have the `idna_to_unicode_utf8_from_utf8' function. */
-/* #undef HAVE_IDNA_TO_UNICODE_UTF8_FROM_UTF8 */
-
-/* Define to 1 if you have the <inttypes.h> header file. */
-#define HAVE_INTTYPES_H 1
-
-/* Define to 1 if you have the <ioctl.h> header file. */
-/* #undef HAVE_IOCTL_H */
-
-/* Define to 1 if you have the `iswalnum' function. */
-#define HAVE_ISWALNUM 1
-
-/* Define to 1 if you have the `iswalpha' function. */
-#define HAVE_ISWALPHA 1
-
-/* Define to 1 if you have the `iswcntrl' function. */
-#define HAVE_ISWCNTRL 1
-
-/* Define to 1 if you have the `iswdigit' function. */
-#define HAVE_ISWDIGIT 1
-
-/* Define to 1 if you have the `iswgraph' function. */
-#define HAVE_ISWGRAPH 1
-
-/* Define to 1 if you have the `iswlower' function. */
-#define HAVE_ISWLOWER 1
-
-/* Define to 1 if you have the `iswprint' function. */
-#define HAVE_ISWPRINT 1
-
-/* Define to 1 if you have the `iswpunct' function. */
-#define HAVE_ISWPUNCT 1
-
-/* Define to 1 if you have the `iswspace' function. */
-#define HAVE_ISWSPACE 1
-
-/* Define to 1 if you have the `iswupper' function. */
-#define HAVE_ISWUPPER 1
-
-/* Define to 1 if you have the `iswxdigit' function. */
-#define HAVE_ISWXDIGIT 1
-
-/* Define if you have <langinfo.h> and nl_langinfo(CODESET). */
-#define HAVE_LANGINFO_CODESET 1
-
-/* Define if you have <langinfo.h> and nl_langinfo(YESEXPR). */
-#define HAVE_LANGINFO_YESEXPR 1
-
-/* Define if your <locale.h> file defines LC_MESSAGES. */
-#define HAVE_LC_MESSAGES 1
-
-/* Define to 1 if you have the `idn' library */
-#define HAVE_LIBIDN 1
-
-/* Define to 1 if you have the `intl' library (-lintl). */
-/* #undef HAVE_LIBINTL */
-
-/* Define to 1 if you have the `nsl' library (-lnsl). */
-/* #undef HAVE_LIBNSL */
-
-/* Define to 1 if you have the `sasl2' library (-lsasl2). */
-#define HAVE_LIBSASL2 1
-
-/* Define to 1 if you have the `socket' library (-lsocket). */
-/* #undef HAVE_LIBSOCKET */
-
-/* Define to 1 if you have the `ssl' library (-lssl). */
-/* #undef HAVE_LIBSSL */
-
-/* Define to 1 if you have the `termlib' library (-ltermlib). */
-/* #undef HAVE_LIBTERMLIB */
-
-/* Define to 1 if you have the `x' library (-lx). */
-/* #undef HAVE_LIBX */
-
-/* Define to 1 if you have the <limits.h> header file. */
-#define HAVE_LIMITS_H 1
-
-/* Define to 1 if you have the <locale.h> header file. */
-#define HAVE_LOCALE_H 1
-
-/* Define to 1 if you have the <malloc.h> header file. */
-#define HAVE_MALLOC_H 1
-
-/* Define to 1 if you have the `memmove' function. */
-#define HAVE_MEMMOVE 1
-
-/* Define to 1 if you have the <memory.h> header file. */
-#define HAVE_MEMORY_H 1
-
-/* Define to 1 if you have the `mempcpy' function. */
-#define HAVE_MEMPCPY 1
-
-/* Define if you have meta, as a function or macro. */
-#define HAVE_META 1
-
-/* Define to 1 if you have a working `mmap' system call. */
-#define HAVE_MMAP 1
-
-/* Define to 1 if you have the `munmap' function. */
-#define HAVE_MUNMAP 1
-
-/* Define to 1 if you have the <ncursesw/ncurses.h> header file. */
-#define HAVE_NCURSESW_NCURSES_H 1
-
-/* Define to 1 if you have the <ncurses.h> header file. */
-/* #undef HAVE_NCURSES_H */
-
-/* Define to 1 if you have the <ncurses/ncurses.h> header file. */
-/* #undef HAVE_NCURSES_NCURSES_H */
-
-/* Define to 1 if you have the <nl_types.h> header file. */
-#define HAVE_NL_TYPES_H 1
-
-/* Define to 1 if you have the `putenv' function. */
-#define HAVE_PUTENV 1
-
-/* QDBM Support */
-/* #undef HAVE_QDBM */
-
-/* Define to 1 if you have the `RAND_egd' function. */
-/* #undef HAVE_RAND_EGD */
-
-/* Define to 1 if you have the `RAND_status' function. */
-/* #undef HAVE_RAND_STATUS */
-
-/* Define to 1 if you have the `regcomp' function. */
-#define HAVE_REGCOMP 1
-
-/* Define if you have resizeterm, as a function or macro. */
-#define HAVE_RESIZETERM 1
-
-/* Define to 1 if you have the `setegid' function. */
-#define HAVE_SETEGID 1
-
-/* Define to 1 if you have the `setenv' function. */
-#define HAVE_SETENV 1
-
-/* Define to 1 if you have the `setlocale' function. */
-#define HAVE_SETLOCALE 1
-
-/* Define to 1 if you have the `setrlimit' function. */
-#define HAVE_SETRLIMIT 1
-
-/* Define to 1 if you have a C99 compliant snprintf function. */
-#define HAVE_SNPRINTF 1
-
-/* Define to 1 if you have the `srand48' function. */
-#define HAVE_SRAND48 1
-
-/* Define if you have start_color, as a function or macro. */
-#define HAVE_START_COLOR 1
-
-/* Define to 1 if you have the <stdarg.h> header file. */
-#define HAVE_STDARG_H 1
-
-/* Define to 1 if you have the <stddef.h> header file. */
-#define HAVE_STDDEF_H 1
-
-/* Define to 1 if you have the <stdint.h> header file. */
-#define HAVE_STDINT_H 1
-
-/* Define to 1 if you have the <stdlib.h> header file. */
-#define HAVE_STDLIB_H 1
-
-/* Define to 1 if you have the `stpcpy' function. */
-#define HAVE_STPCPY 1
-
-/* Define to 1 if you have the `strcasecmp' function. */
-#define HAVE_STRCASECMP 1
-
-/* Define to 1 if you have the `strchr' function. */
-#define HAVE_STRCHR 1
-
-/* Define to 1 if you have the `strdup' function. */
-#define HAVE_STRDUP 1
-
-/* Define to 1 if you have the `strerror' function. */
-#define HAVE_STRERROR 1
-
-/* Define to 1 if you have the `strftime' function. */
-#define HAVE_STRFTIME 1
-
-/* Define to 1 if you have the <strings.h> header file. */
-#define HAVE_STRINGS_H 1
-
-/* Define to 1 if you have the <string.h> header file. */
-#define HAVE_STRING_H 1
-
-/* Define to 1 if you have the `strsep' function. */
-#define HAVE_STRSEP 1
-
-/* Define to 1 if you have the `strtok_r' function. */
-#define HAVE_STRTOK_R 1
-
-/* Define to 1 if you have the `strtoul' function. */
-#define HAVE_STRTOUL 1
-
-/* Define to 1 if you have the <sysexits.h> header file. */
-#define HAVE_SYSEXITS_H 1
-
-/* Define to 1 if you have the <sys/ioctl.h> header file. */
-#define HAVE_SYS_IOCTL_H 1
-
-/* Define to 1 if you have the <sys/param.h> header file. */
-#define HAVE_SYS_PARAM_H 1
-
-/* Define to 1 if you have the <sys/resource.h> header file. */
-#define HAVE_SYS_RESOURCE_H 1
-
-/* Define to 1 if you have the <sys/select.h> header file. */
-#define HAVE_SYS_SELECT_H 1
-
-/* Define to 1 if you have the <sys/stat.h> header file. */
-#define HAVE_SYS_STAT_H 1
-
-/* Define to 1 if you have the <sys/time.h> header file. */
-#define HAVE_SYS_TIME_H 1
-
-/* Define to 1 if you have the <sys/types.h> header file. */
-#define HAVE_SYS_TYPES_H 1
-
-/* Tokyo Cabinet Support */
-/* #undef HAVE_TC */
-
-/* Define to 1 if you have the `towlower' function. */
-#define HAVE_TOWLOWER 1
-
-/* Define to 1 if you have the `towupper' function. */
-#define HAVE_TOWUPPER 1
-
-/* Define to 1 if you have the `tsearch' function. */
-#define HAVE_TSEARCH 1
-
-/* Define if you have typeahead, as a function or macro. */
-#define HAVE_TYPEAHEAD 1
-
-/* Define to 1 if you have the <unistd.h> header file. */
-#define HAVE_UNISTD_H 1
-
-/* Define to 1 if you have the <unix.h> header file. */
-/* #undef HAVE_UNIX_H */
-
-/* Define if you have use_default_colors, as a function or macro. */
-#define HAVE_USE_DEFAULT_COLORS 1
-
-/* Define to 1 if you have the <villa.h> header file. */
-/* #undef HAVE_VILLA_H */
-
-/* Define to 1 if you have a C99 compliant vsnprintf function. */
-#define HAVE_VSNPRINTF 1
-
-/* Define to 1 if you have the <wchar.h> header file. */
-#define HAVE_WCHAR_H 1
-
-/* Define to 1 if you have the <wctype.h> header file. */
-#define HAVE_WCTYPE_H 1
-
-/* Define if you are using the system's wchar_t functions. */
-#define HAVE_WC_FUNCS 1
-
-/* Define to 1 if you have the `__argz_count' function. */
-#define HAVE___ARGZ_COUNT 1
-
-/* Define to 1 if you have the `__argz_next' function. */
-#define HAVE___ARGZ_NEXT 1
-
-/* Define to 1 if you have the `__argz_stringify' function. */
-#define HAVE___ARGZ_STRINGIFY 1
-
-/* Is mail spooled to the user's home directory? If defined, MAILPATH should
- be set to the filename of the spool mailbox relative the the home
- directory. use: configure --with-homespool=FILE */
-/* #undef HOMESPOOL */
-
-/* Define as const if the declaration of iconv() needs const. */
-#define ICONV_CONST
-
-/* Define as 1 if iconv() only converts exactly and we should treat all return
- values other than (size_t)(-1) as equivalent. */
-#define ICONV_NONTRANS 0
-
-/* Where to find ispell on your system. */
-/* #undef ISPELL */
-
-/* Define if the result of isprint() is unreliable. */
-/* #undef LOCALES_HACK */
-
-/* Where new mail is spooled. */
-#define MAILPATH "/var/mail"
-
-/* Define if you want complete documentation. */
-#define MAKEDOC_FULL 1
-
-/* Where to find mixmaster on your system. */
-#define MIXMASTER "mixmaster"
-
-/* Define if you have problems with mutt not detecting new/old mailboxes over
- NFS. Some NFS implementations incorrectly cache the attributes of small
- files. */
-/* #undef NFS_ATTRIBUTE_HACK */
-
-/* Name of package */
-#define PACKAGE "mutt"
-
-/* Define to the address where bug reports for this package should be sent. */
-#define PACKAGE_BUGREPORT ""
-
-/* Define to the full name of this package. */
-#define PACKAGE_NAME ""
-
-/* Define to the full name and version of this package. */
-#define PACKAGE_STRING ""
-
-/* Define to the one symbol short name of this package. */
-#define PACKAGE_TARNAME ""
-
-/* Define to the version of this package. */
-#define PACKAGE_VERSION ""
-
-/* Define to 1 if the C compiler supports function prototypes. */
-#define PROTOTYPES 1
-
-/* Define as the return type of signal handlers (`int' or `void'). */
-#define RETSIGTYPE void
-
-/* Where to find sendmail on your system. */
-#define SENDMAIL "/usr/sbin/sendmail"
-
-/* Some systems declare sig_atomic_t as volatile, some others -- no. This
- define will have value `sig_atomic_t' or `volatile sig_atomic_t'
- accordingly. */
-#define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-
-/* The size of `int', as computed by sizeof. */
-#define SIZEOF_INT 4
-
-/* The size of `long', as computed by sizeof. */
-#define SIZEOF_LONG 4
-
-/* The size of `long long', as computed by sizeof. */
-#define SIZEOF_LONG_LONG 8
-
-/* The size of `off_t', as computed by sizeof. */
-#define SIZEOF_OFF_T 8
-
-/* The size of `short', as computed by sizeof. */
-#define SIZEOF_SHORT 2
-
-/* If using the C implementation of alloca, define if you know the
- direction of stack growth for your system; otherwise it will be
- automatically deduced at runtime.
- STACK_DIRECTION > 0 => grows toward higher addresses
- STACK_DIRECTION < 0 => grows toward lower addresses
- STACK_DIRECTION = 0 => direction of growth unknown */
-/* #undef STACK_DIRECTION */
-
-/* Define to 1 if you have the ANSI C header files. */
-#define STDC_HEADERS 1
-
-/* Define to enable Sun mailtool attachments support. */
-/* #undef SUN_ATTACHMENT */
-
-/* Define to support compressed folders. */
-#define USE_COMPRESSED 1
-
-/* Define to use dotlocking for mailboxes. */
-#define USE_DOTLOCK 1
-
-/* Define to use fcntl() to lock folders. */
-#define USE_FCNTL 1
-
-/* Define to use flock() to lock mailboxes. */
-/* #undef USE_FLOCK */
-
-/* Define if you want to use the included regex.c. */
-/* #undef USE_GNU_REGEX */
-
-/* Define if you have GSSAPI libraries available */
-#define USE_GSS 1
-
-/* Enable header caching */
-#define USE_HCACHE 1
-
-/* Define if you want support for the IMAP protocol. */
-#define USE_IMAP 1
-
-/* Define if you want support for the POP3 protocol. */
-#define USE_POP 1
-
-/* Define if want to use the Cyrus SASL library for POP/IMAP authentication.
- */
-#define USE_SASL 1
-
-/* Define if mutt should run setgid "mail". */
-#define USE_SETGID 1
-
-/* Define if you compile with SLang instead of curses/ncurses. */
-/* #undef USE_SLANG_CURSES */
-
-/* Include internal SMTP relay support */
-#define USE_SMTP 1
-
-/* Include code for socket support. Set automatically if you enable POP3 or
- IMAP */
-#define USE_SOCKET 1
-
-/* Define if you want support for SSL. */
-#define USE_SSL 1
-
-/* Define if you want support for SSL via GNUTLS. */
-#define USE_SSL_GNUTLS 1
-
-/* Define if you want support for SSL via OpenSSL. */
-/* #undef USE_SSL_OPENSSL */
-
-/* Enable extensions on AIX 3, Interix. */
-#ifndef _ALL_SOURCE
-# define _ALL_SOURCE 1
-#endif
-/* Enable GNU extensions on systems that have them. */
-#ifndef _GNU_SOURCE
-# define _GNU_SOURCE 1
-#endif
-/* Enable threading extensions on Solaris. */
-#ifndef _POSIX_PTHREAD_SEMANTICS
-# define _POSIX_PTHREAD_SEMANTICS 1
-#endif
-/* Enable extensions on HP NonStop. */
-#ifndef _TANDEM_SOURCE
-# define _TANDEM_SOURCE 1
-#endif
-/* Enable general extensions on Solaris. */
-#ifndef __EXTENSIONS__
-# define __EXTENSIONS__ 1
-#endif
-
-
-/* Version number of package */
-#define VERSION "1.5.19"
-
-/* Define WORDS_BIGENDIAN to 1 if your processor stores words with the most
- significant byte first (like Motorola and SPARC, unlike Intel). */
-#if defined AC_APPLE_UNIVERSAL_BUILD
-# if defined __BIG_ENDIAN__
-# define WORDS_BIGENDIAN 1
-# endif
-#else
-# ifndef WORDS_BIGENDIAN
-/* # undef WORDS_BIGENDIAN */
-# endif
-#endif
-
-#ifndef HAVE_C99_INTTYPES
-# if SIZEOF_SHORT == 4
-typedef unsigned short uint32_t;
-# elif SIZEOF_INT == 4
-typedef unsigned int uint32_t;
-# elif SIZEOF_LONG == 4
-typedef unsigned long uint32_t;
-# endif
-# if SIZEOF_INT == 8
-typedef unsigned int uint64_t;
-# elif SIZEOF_LONG == 8
-typedef unsigned long uint64_t;
-# elif SIZEOF_LONG_LONG == 8
-typedef unsigned long long uint64_t;
-# endif
-#endif
-
-
-/* Number of bits in a file offset, on hosts where this is settable. */
-#define _FILE_OFFSET_BITS 64
-
-/* Define to 1 to make fseeko visible on some hosts (e.g. glibc 2.2). */
-/* #undef _LARGEFILE_SOURCE */
-
-/* Define for large files, on AIX-style hosts. */
-/* #undef _LARGE_FILES */
-
-/* Define to 1 if on MINIX. */
-/* #undef _MINIX */
-
-/* Define to 2 if the system does not provide POSIX.1 features except with
- this defined. */
-/* #undef _POSIX_1_SOURCE */
-
-/* Define to 1 if you need to in order for `stat' and other things to work. */
-/* #undef _POSIX_SOURCE */
-
-/* Define like PROTOTYPES; this can be used by system headers. */
-#define __PROTOTYPES 1
-
-/* Define to empty if `const' does not conform to ANSI C. */
-/* #undef const */
-
-/* Define to `__inline__' or `__inline' if that's what the C compiler
- calls it, or to nothing if 'inline' is not supported under any name. */
-#ifndef __cplusplus
-/* #undef inline */
-#endif
-
-/* Define to 'int' if system headers don't define. */
-/* #undef mbstate_t */
-
-/* Define to `long int' if <sys/types.h> does not define. */
-/* #undef off_t */
-
-/* Define to `int' if <sys/types.h> does not define. */
-/* #undef pid_t */
-
-/* Define to `int' if <sys/types.h> does not define. */
-/* #undef sig_atomic_t */
-
-/* Define to `unsigned int' if <sys/types.h> does not define. */
-/* #undef size_t */
-
-/* Define to 'int' if <sys/socket.h> doesn't have it. */
-/* #undef socklen_t */
-
-/* Define to `int' if <sys/types.h> does not define. */
-/* #undef ssize_t */
-
-/* define if va_copy is not available */
-/* #undef va_copy */
-
-/* Define to 'int' if system headers don't define. */
-/* #undef wchar_t */
-
-/* Define to 'int' if system headers don't define. */
-/* #undef wint_t */
-
-/* fseeko portability defines */
-#ifdef HAVE_FSEEKO
-# define LOFF_T off_t
-# if HAVE_C99_INTTYPES && HAVE_INTTYPES_H
-# if SIZEOF_OFF_T == 8
-# define OFF_T_FMT "%" PRId64
-# else
-# define OFF_T_FMT "%" PRId32
-# endif
-# else
-# if (SIZEOF_OFF_T == 8) && (SIZEOF_LONG == 4)
-# define OFF_T_FMT "%lld"
-# else
-# define OFF_T_FMT "%ld"
-# endif
-# endif
-#else
-# define LOFF_T long
-# define fseeko fseek
-# define ftello ftell
-# define OFF_T_FMT "%ld"
-#endif
-
-#include "config-debian.h"
+++ /dev/null
-This file contains any messages produced by compilers while
-running configure, to aid debugging if configure makes a mistake.
-
-It was created by configure, which was
-generated by GNU Autoconf 2.63. Invocation command line was
-
- $ ../configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-sharedir=/usr/share/mutt --with-docdir=/usr/share/doc --with-mailpath=/var/mail --disable-dependency-tracking --enable-compressed --enable-debug --enable-fcntl --enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-inodesort --enable-pop --with-curses --with-gnutls --with-gss --with-idn --with-mixmaster --with-sasl --without-qdbm --without-bdb --without-tokyocabinet --build i486-linux-gnu
-
-## --------- ##
-## Platform. ##
-## --------- ##
-
-hostname = debian
-uname -m = i686
-uname -r = 2.6.26-1-686
-uname -s = Linux
-uname -v = #1 SMP Sat Jan 10 18:29:31 UTC 2009
-
-/usr/bin/uname -p = unknown
-/bin/uname -X = unknown
-
-/bin/arch = unknown
-/usr/bin/arch -k = unknown
-/usr/convex/getsysinfo = unknown
-/usr/bin/hostinfo = unknown
-/bin/machine = unknown
-/usr/bin/oslevel = unknown
-/bin/universe = unknown
-
-PATH: /usr/sbin
-PATH: /usr/bin
-PATH: /sbin
-PATH: /bin
-PATH: /usr/bin/X11
-
-
-## ----------- ##
-## Core tests. ##
-## ----------- ##
-
-configure:2040: checking for a BSD-compatible install
-configure:2108: result: /usr/bin/install -c
-configure:2119: checking whether build environment is sane
-configure:2162: result: yes
-configure:2187: checking for a thread-safe mkdir -p
-configure:2226: result: /bin/mkdir -p
-configure:2239: checking for gawk
-configure:2255: found /usr/bin/gawk
-configure:2266: result: gawk
-configure:2277: checking whether make sets $(MAKE)
-configure:2299: result: yes
-configure:2483: checking whether to enable maintainer-specific portions of Makefiles
-configure:2492: result: no
-configure:2520: checking for style of include used by make
-configure:2548: result: GNU
-configure:2618: checking for gcc
-configure:2634: found /usr/bin/gcc
-configure:2645: result: gcc
-configure:2877: checking for C compiler version
-configure:2885: gcc --version >&5
-gcc (Debian 4.3.3-5) 4.3.3
-Copyright (C) 2008 Free Software Foundation, Inc.
-This is free software; see the source for copying conditions. There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
-configure:2889: $? = 0
-configure:2896: gcc -v >&5
-Using built-in specs.
-Target: i486-linux-gnu
-Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-5' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
-Thread model: posix
-gcc version 4.3.3 (Debian 4.3.3-5)
-configure:2900: $? = 0
-configure:2907: gcc -V >&5
-gcc: '-V' option must have argument
-configure:2911: $? = 1
-configure:2934: checking for C compiler default output file name
-configure:2956: gcc -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:2960: $? = 0
-configure:2998: result: a.out
-configure:3017: checking whether the C compiler works
-configure:3027: ./a.out
-configure:3031: $? = 0
-configure:3050: result: yes
-configure:3057: checking whether we are cross compiling
-configure:3059: result: no
-configure:3062: checking for suffix of executables
-configure:3069: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:3073: $? = 0
-configure:3099: result:
-configure:3105: checking for suffix of object files
-configure:3131: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:3135: $? = 0
-configure:3160: result: o
-configure:3164: checking whether we are using the GNU C compiler
-configure:3193: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:3200: $? = 0
-configure:3217: result: yes
-configure:3226: checking whether gcc accepts -g
-configure:3256: gcc -c -g -I/usr/include/qdbm conftest.c >&5
-configure:3263: $? = 0
-configure:3364: result: yes
-configure:3381: checking for gcc option to accept ISO C89
-configure:3455: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:3462: $? = 0
-configure:3485: result: none needed
-configure:3505: checking dependency style of gcc
-configure:3596: result: none
-configure:3617: checking how to run the C preprocessor
-configure:3657: gcc -E -I/usr/include/qdbm conftest.c
-configure:3664: $? = 0
-configure:3695: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
-configure:3702: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| /* end confdefs.h. */
-| #include <ac_nonexistent.h>
-configure:3735: result: gcc -E
-configure:3764: gcc -E -I/usr/include/qdbm conftest.c
-configure:3771: $? = 0
-configure:3802: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
-configure:3809: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| /* end confdefs.h. */
-| #include <ac_nonexistent.h>
-configure:3849: checking for grep that handles long lines and -e
-configure:3909: result: /bin/grep
-configure:3914: checking for egrep
-configure:3978: result: /bin/grep -E
-configure:3983: checking for ANSI C header files
-configure:4013: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4020: $? = 0
-configure:4119: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4123: $? = 0
-configure:4129: ./conftest
-configure:4133: $? = 0
-configure:4151: result: yes
-configure:4175: checking for sys/types.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for sys/stat.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for stdlib.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for string.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for memory.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for strings.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for inttypes.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for stdint.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4175: checking for unistd.h
-configure:4196: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4203: $? = 0
-configure:4220: result: yes
-configure:4245: checking minix/config.h usability
-configure:4262: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:53:26: error: minix/config.h: No such file or directory
-configure:4269: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| #include <minix/config.h>
-configure:4283: result: no
-configure:4287: checking minix/config.h presence
-configure:4302: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:20:26: error: minix/config.h: No such file or directory
-configure:4309: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| /* end confdefs.h. */
-| #include <minix/config.h>
-configure:4323: result: no
-configure:4351: checking for minix/config.h
-configure:4358: result: no
-configure:4389: checking whether it is safe to define __EXTENSIONS__
-configure:4417: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:4424: $? = 0
-configure:4439: result: yes
-configure:4472: checking build system type
-configure:4490: result: i486-pc-linux-gnu
-configure:4512: checking host system type
-configure:4527: result: i486-pc-linux-gnu
-configure:4550: checking for prefix
-configure:4557: result: /usr
-configure:4608: checking for gcc
-configure:4635: result: gcc
-configure:4867: checking for C compiler version
-configure:4875: gcc --version >&5
-gcc (Debian 4.3.3-5) 4.3.3
-Copyright (C) 2008 Free Software Foundation, Inc.
-This is free software; see the source for copying conditions. There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
-configure:4879: $? = 0
-configure:4886: gcc -v >&5
-Using built-in specs.
-Target: i486-linux-gnu
-Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-5' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
-Thread model: posix
-gcc version 4.3.3 (Debian 4.3.3-5)
-configure:4890: $? = 0
-configure:4897: gcc -V >&5
-gcc: '-V' option must have argument
-configure:4901: $? = 1
-configure:4904: checking whether we are using the GNU C compiler
-configure:4957: result: yes
-configure:4966: checking whether gcc accepts -g
-configure:5104: result: yes
-configure:5121: checking for gcc option to accept ISO C89
-configure:5225: result: none needed
-configure:5245: checking dependency style of gcc
-configure:5336: result: none
-configure:5351: checking for library containing strerror
-configure:5392: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:5399: $? = 0
-configure:5430: result: none required
-configure:5438: checking for function prototypes
-configure:5441: result: yes
-configure:5471: checking for string.h
-configure:5478: result: yes
-configure:5623: checking how to run the C preprocessor
-configure:5741: result: gcc -E
-configure:5770: gcc -E -I/usr/include/qdbm conftest.c
-configure:5777: $? = 0
-configure:5808: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:28:28: error: ac_nonexistent.h: No such file or directory
-configure:5815: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| /* end confdefs.h. */
-| #include <ac_nonexistent.h>
-configure:5854: checking whether make sets $(MAKE)
-configure:5876: result: yes
-configure:5899: checking for a BSD-compatible install
-configure:5967: result: /usr/bin/install -c
-configure:6021: checking for ranlib
-configure:6037: found /usr/bin/ranlib
-configure:6048: result: ranlib
-configure:6113: checking for ar
-configure:6129: found /usr/bin/ar
-configure:6140: result: ar
-configure:6163: checking for inline
-configure:6189: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:6196: $? = 0
-configure:6214: result: inline
-configure:6233: checking for an ANSI C-conforming const
-configure:6308: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:57: warning: 't' is used uninitialized in this function
-conftest.c:73: warning: 'b' may be used uninitialized in this function
-conftest.c:79: warning: 'cs[0]' is used uninitialized in this function
-configure:6315: $? = 0
-configure:6330: result: yes
-configure:6341: checking whether byte ordering is bigendian
-configure:6366: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:29: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'a'
-configure:6373: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| /* end confdefs.h. */
-| #ifndef __APPLE_CC__
-| not a universal capable compiler
-| #endif
-| typedef int dummy;
-|
-configure:6423: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:6430: $? = 0
-configure:6462: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:35: error: 'not' undeclared (first use in this function)
-conftest.c:35: error: (Each undeclared identifier is reported only once
-conftest.c:35: error: for each function it appears in.)
-conftest.c:35: error: expected ';' before 'big'
-configure:6469: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| /* end confdefs.h. */
-| #include <sys/types.h>
-| #include <sys/param.h>
-|
-| int
-| main ()
-| {
-| #if BYTE_ORDER != BIG_ENDIAN
-| not big endian
-| #endif
-|
-| ;
-| return 0;
-| }
-configure:6721: result: no
-configure:6754: checking for special C compiler options needed for large files
-configure:6849: result: no
-configure:6855: checking for _FILE_OFFSET_BITS value needed for large files
-configure:6890: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:34: warning: left shift count >= width of type
-conftest.c:34: warning: left shift count >= width of type
-conftest.c:36: error: size of array 'off_t_is_large' is negative
-configure:6897: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| /* end confdefs.h. */
-| #include <sys/types.h>
-| /* Check that off_t can represent 2**63 - 1 correctly.
-| We can't simply define LARGE_OFF_T to be 9223372036854775807,
-| since some C++ compilers masquerading as C compilers
-| incorrectly reject 9223372036854775807. */
-| #define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62))
-| int off_t_is_large[(LARGE_OFF_T % 2147483629 == 721
-| && LARGE_OFF_T % 2147483647 == 1)
-| ? 1 : -1];
-| int
-| main ()
-| {
-|
-| ;
-| return 0;
-| }
-configure:6941: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:6948: $? = 0
-configure:6966: result: 64
-configure:7103: checking for _LARGEFILE_SOURCE value needed for large files
-configure:7132: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:7139: $? = 0
-configure:7212: result: no
-configure:7239: checking size of off_t
-configure:7544: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:7548: $? = 0
-configure:7554: ./conftest
-configure:7558: $? = 0
-configure:7584: result: 8
-configure:7597: checking for dbx
-configure:7628: result: no
-configure:7638: checking for gdb
-configure:7656: found /usr/bin/gdb
-configure:7669: result: /usr/bin/gdb
-configure:7679: checking for sdb
-configure:7710: result: no
-configure:7759: checking for inttypes.h
-configure:7766: result: yes
-configure:7900: checking for uint32_t
-configure:7928: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:7935: $? = 0
-configure:7962: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:68: error: expected expression before ')' token
-configure:7969: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((uint32_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:7992: result: yes
-configure:8006: checking size of short
-configure:8311: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:8315: $? = 0
-configure:8321: ./conftest
-configure:8325: $? = 0
-configure:8351: result: 2
-configure:8365: checking size of int
-configure:8670: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:8674: $? = 0
-configure:8680: ./conftest
-configure:8684: $? = 0
-configure:8710: result: 4
-configure:8724: checking size of long
-configure:9029: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:9033: $? = 0
-configure:9039: ./conftest
-configure:9043: $? = 0
-configure:9069: result: 4
-configure:9083: checking size of long long
-configure:9388: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:9392: $? = 0
-configure:9398: ./conftest
-configure:9402: $? = 0
-configure:9428: result: 8
-configure:9442: checking for sendmail
-configure:9461: found /usr/sbin/sendmail
-configure:9474: result: /usr/sbin/sendmail
-configure:9490: checking whether to build with GPGME support
-configure:9502: result: yes
-configure:9517: checking for gpgme-config
-configure:9535: found /usr/bin/gpgme-config
-configure:9548: result: /usr/bin/gpgme-config
-configure:9576: checking for GPGME - version >= 1.0.0
-configure:9617: result: yes
-configure:9648: checking for GPGME - version >= 1.1.1
-configure:9689: result: yes
-configure:9716: checking for GPGME - version >= 1.0.0
-configure:9757: result: yes
-configure:9850: checking for ispell
-configure:9881: result: no
-configure:10172: checking for initscr
-configure:10228: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-/tmp/cc6dCEoQ.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/conftest.c:78: undefined reference to `initscr'
-collect2: ld returned 1 exit status
-configure:10235: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| /* end confdefs.h. */
-| /* Define initscr to an innocuous variant, in case <limits.h> declares initscr.
-| For example, HP-UX 11i <limits.h> declares gettimeofday. */
-| #define initscr innocuous_initscr
-|
-| /* System header to define __stub macros and hopefully few prototypes,
-| which can conflict with char initscr (); below.
-| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
-| <limits.h> exists even on freestanding compilers. */
-|
-| #ifdef __STDC__
-| # include <limits.h>
-| #else
-| # include <assert.h>
-| #endif
-|
-| #undef initscr
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char initscr ();
-| /* The GNU C library defines this for functions which it implements
-| to always fail with ENOSYS. Some functions are actually named
-| something starting with __ and the normal name is an alias. */
-| #if defined __stub_initscr || defined __stub___initscr
-| choke me
-| #endif
-|
-| int
-| main ()
-| {
-| return initscr ();
-| ;
-| return 0;
-| }
-configure:10255: result: no
-configure:10265: checking for waddnwstr in -lncurses
-configure:10300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncurses >&5
-/tmp/ccgvJgd3.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/conftest.c:55: undefined reference to `waddnwstr'
-collect2: ld returned 1 exit status
-configure:10307: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| /* end confdefs.h. */
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char waddnwstr ();
-| int
-| main ()
-| {
-| return waddnwstr ();
-| ;
-| return 0;
-| }
-configure:10330: result: no
-configure:10265: checking for waddnwstr in -lncursesw
-configure:10300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncursesw >&5
-configure:10307: $? = 0
-configure:10330: result: yes
-configure:10340: checking for initscr in -lncursesw
-configure:10375: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c -lncursesw >&5
-configure:10382: $? = 0
-configure:10405: result: yes
-configure:10429: checking ncursesw/ncurses.h usability
-configure:10446: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:10453: $? = 0
-configure:10467: result: yes
-configure:10471: checking ncursesw/ncurses.h presence
-configure:10486: gcc -E -I/usr/include/qdbm conftest.c
-configure:10493: $? = 0
-configure:10507: result: yes
-configure:10535: checking for ncursesw/ncurses.h
-configure:10544: result: yes
-configure:11615: checking for start_color declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:50: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for typeahead declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:51: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for bkgdset declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for curs_set declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:53: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for meta declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:54: error: conflicting types for 'meta'
-conftest.c:54: note: an argument type that has a default promotion can't match an empty parameter name list declaration
-/usr/include/ncursesw/ncurses.h:604: error: previous declaration of 'meta' was here
-configure:11650: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| /* end confdefs.h. */
-| #include <ncursesw/ncurses.h>
-| int
-| main ()
-| {
-| #ifndef meta
-| extern int meta();
-| #endif
-| ;
-| return 0;
-| }
-configure:11714: result: yes
-configure:11615: checking for use_default_colors declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:55: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11615: checking for resizeterm declaration
-configure:11643: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11650: $? = 0
-configure:11679: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:56: warning: unused variable 'p'
-configure:11686: $? = 0
-configure:11714: result: yes
-configure:11745: checking for ANSI C header files
-configure:11913: result: yes
-configure:11943: checking stdarg.h usability
-configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11967: $? = 0
-configure:11981: result: yes
-configure:11985: checking stdarg.h presence
-configure:12000: gcc -E -I/usr/include/qdbm conftest.c
-configure:12007: $? = 0
-configure:12021: result: yes
-configure:12049: checking for stdarg.h
-configure:12058: result: yes
-configure:11943: checking sys/ioctl.h usability
-configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11967: $? = 0
-configure:11981: result: yes
-configure:11985: checking sys/ioctl.h presence
-configure:12000: gcc -E -I/usr/include/qdbm conftest.c
-configure:12007: $? = 0
-configure:12021: result: yes
-configure:12049: checking for sys/ioctl.h
-configure:12058: result: yes
-configure:11943: checking ioctl.h usability
-configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:89:19: error: ioctl.h: No such file or directory
-configure:11967: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| #include <ioctl.h>
-configure:11981: result: no
-configure:11985: checking ioctl.h presence
-configure:12000: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:56:19: error: ioctl.h: No such file or directory
-configure:12007: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| /* end confdefs.h. */
-| #include <ioctl.h>
-configure:12021: result: no
-configure:12049: checking for ioctl.h
-configure:12058: result: no
-configure:11943: checking sysexits.h usability
-configure:11960: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:11967: $? = 0
-configure:11981: result: yes
-configure:11985: checking sysexits.h presence
-configure:12000: gcc -E -I/usr/include/qdbm conftest.c
-configure:12007: $? = 0
-configure:12021: result: yes
-configure:12049: checking for sysexits.h
-configure:12058: result: yes
-configure:12090: checking sys/time.h usability
-configure:12107: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12114: $? = 0
-configure:12128: result: yes
-configure:12132: checking sys/time.h presence
-configure:12147: gcc -E -I/usr/include/qdbm conftest.c
-configure:12154: $? = 0
-configure:12168: result: yes
-configure:12196: checking for sys/time.h
-configure:12205: result: yes
-configure:12090: checking sys/resource.h usability
-configure:12107: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12114: $? = 0
-configure:12128: result: yes
-configure:12132: checking sys/resource.h presence
-configure:12147: gcc -E -I/usr/include/qdbm conftest.c
-configure:12154: $? = 0
-configure:12168: result: yes
-configure:12196: checking for sys/resource.h
-configure:12205: result: yes
-configure:12236: checking unix.h usability
-configure:12253: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:92:18: error: unix.h: No such file or directory
-configure:12260: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| #include <unix.h>
-configure:12274: result: no
-configure:12278: checking unix.h presence
-configure:12293: gcc -E -I/usr/include/qdbm conftest.c
-conftest.c:59:18: error: unix.h: No such file or directory
-configure:12300: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| /* end confdefs.h. */
-| #include <unix.h>
-configure:12314: result: no
-configure:12342: checking for unix.h
-configure:12351: result: no
-configure:12372: checking for setrlimit
-configure:12428: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12435: $? = 0
-configure:12457: result: yes
-configure:12372: checking for getsid
-configure:12428: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12435: $? = 0
-configure:12457: result: yes
-configure:12470: checking return type of signal handlers
-configure:12498: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:67: error: void value not ignored as it ought to be
-configure:12505: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| /* end confdefs.h. */
-| #include <sys/types.h>
-| #include <signal.h>
-|
-| int
-| main ()
-| {
-| return *(signal (0, 0)) (0) == 1;
-| ;
-| return 0;
-| }
-configure:12520: result: void
-configure:12529: checking for sig_atomic_t in signal.h
-configure:12563: result: yes, non volatile
-configure:12696: checking whether sys_siglist is declared
-configure:12731: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12738: $? = 0
-configure:12753: result: yes
-configure:12773: checking for pid_t
-configure:12801: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12808: $? = 0
-configure:12835: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:100: error: expected expression before ')' token
-configure:12842: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((pid_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:12865: result: yes
-configure:12877: checking for ssize_t
-configure:12905: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:12912: $? = 0
-configure:12939: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:100: error: expected expression before ')' token
-configure:12946: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((ssize_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:12969: result: yes
-configure:12990: checking for fgetpos
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:12990: checking for memmove
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:88: warning: conflicting types for built-in function 'memmove'
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:12990: checking for setegid
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:12990: checking for srand48
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:12990: checking for strerror
-configure:13046: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13053: $? = 0
-configure:13075: result: yes
-configure:13096: checking for setenv
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13096: checking for strcasecmp
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:93: warning: conflicting types for built-in function 'strcasecmp'
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13096: checking for strdup
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:94: warning: conflicting types for built-in function 'strdup'
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13096: checking for strsep
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13096: checking for strtok_r
-configure:13152: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13159: $? = 0
-configure:13181: result: yes
-configure:13202: checking for getopt
-configure:13258: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13265: $? = 0
-configure:13285: result: yes
-configure:13305: checking getopt.h usability
-configure:13322: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13329: $? = 0
-configure:13343: result: yes
-configure:13347: checking getopt.h presence
-configure:13362: gcc -E -I/usr/include/qdbm conftest.c
-configure:13369: $? = 0
-configure:13383: result: yes
-configure:13411: checking for getopt.h
-configure:13420: result: yes
-configure:13438: checking for snprintf
-configure:13494: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:98: warning: conflicting types for built-in function 'snprintf'
-configure:13501: $? = 0
-configure:13521: result: yes
-configure:13529: checking for vsnprintf
-configure:13585: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:98: warning: conflicting types for built-in function 'vsnprintf'
-configure:13592: $? = 0
-configure:13612: result: yes
-configure:13621: checking whether your system's snprintf is C99 compliant
-configure:13651: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13655: $? = 0
-configure:13661: ./conftest
-configure:13665: $? = 0
-configure:13682: result: yes
-configure:13688: checking whether your system's vsnprintf is C99 compliant
-configure:13728: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13732: $? = 0
-configure:13738: ./conftest
-configure:13742: $? = 0
-configure:13759: result: yes
-configure:13787: checking for va_copy
-configure:13810: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:81: warning: 'ap2' is used uninitialized in this function
-configure:13817: $? = 0
-configure:13825: result: va_copy
-configure:13903: checking for ftruncate
-configure:13959: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:13966: $? = 0
-configure:13988: result: yes
-configure:14081: checking for strftime
-configure:14137: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:101: warning: conflicting types for built-in function 'strftime'
-configure:14144: $? = 0
-configure:14166: result: yes
-configure:14259: checking for fchdir
-configure:14315: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14322: $? = 0
-configure:14344: result: yes
-configure:14368: checking for regcomp
-configure:14424: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14431: $? = 0
-configure:14453: result: yes
-configure:14471: checking whether your system's regexp library is completely broken
-configure:14496: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-conftest.c:84: warning: return type defaults to 'int'
-configure:14500: $? = 0
-configure:14506: ./conftest
-configure:14510: $? = 0
-configure:14527: result: no
-configure:14614: checking if /var/mail is world writable
-configure:14647: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14651: $? = 0
-configure:14657: ./conftest
-configure:14661: $? = 1
-configure: program exited with status 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| /* end confdefs.h. */
-| #include <sys/types.h>
-| #include <sys/stat.h>
-| #include <stdlib.h>
-|
-| int main (int argc, char **argv)
-| {
-| struct stat s;
-|
-| stat ("/var/mail", &s);
-| if (s.st_mode & S_IWOTH) exit (0);
-| exit (1);
-| }
-configure:14678: result: no
-configure:14690: checking if /var/mail is group writable
-configure:14723: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14727: $? = 0
-configure:14733: ./conftest
-configure:14737: $? = 0
-configure:14754: result: yes
-configure:14799: checking where to put the documentation
-configure:14809: result: /usr/share/doc
-configure:14923: checking sys/select.h usability
-configure:14940: gcc -c -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:14947: $? = 0
-configure:14961: result: yes
-configure:14965: checking sys/select.h presence
-configure:14980: gcc -E -I/usr/include/qdbm conftest.c
-configure:14987: $? = 0
-configure:15001: result: yes
-configure:15029: checking for sys/select.h
-configure:15038: result: yes
-configure:15053: checking for socklen_t
-configure:15066: result: yes
-configure:15079: checking for gethostent
-configure:15135: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:15142: $? = 0
-configure:15162: result: yes
-configure:15244: checking for setsockopt
-configure:15300: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:15307: $? = 0
-configure:15327: result: yes
-configure:15413: checking for getaddrinfo
-configure:15469: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm conftest.c >&5
-configure:15476: $? = 0
-configure:15498: result: yes
-configure:15545: checking for krb5-config
-configure:15563: found /usr/bin/krb5-config
-configure:15576: result: /usr/bin/krb5-config
-configure:15833: checking GSSAPI implementation
-configure:15835: result: MIT
-configure:16370: checking for pkg-config
-configure:16388: found /usr/bin/pkg-config
-configure:16400: result: /usr/bin/pkg-config
-configure:16425: checking pkg-config is at least version 0.9.0
-configure:16428: result: yes
-configure:16439: checking for GNUTLS
-configure:16447: $PKG_CONFIG --exists --print-errors "gnutls"
-configure:16450: $? = 0
-configure:16465: $PKG_CONFIG --exists --print-errors "gnutls"
-configure:16468: $? = 0
-configure:16510: result: yes
-configure:16562: checking for sasl_client_init in -lsasl2
-configure:16597: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm conftest.c -lsasl2 >&5
-configure:16604: $? = 0
-configure:16625: result: yes
-configure:16704: checking whether struct dirent defines d_ino
-configure:16728: gcc -o conftest -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm conftest.c >&5
-configure:16735: $? = 0
-configure:16761: result: yes
-configure:17433: checking for gdbm_open
-configure:17461: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c -lgdbm >&5
-configure:17468: $? = 0
-configure:17489: result: yes
-configure:17650: checking for off_t
-configure:17678: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:17685: $? = 0
-configure:17712: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:139: error: expected expression before ')' token
-configure:17719: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((off_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:17742: result: yes
-configure:17754: checking for size_t
-configure:17782: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:17789: $? = 0
-configure:17816: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:139: error: expected expression before ')' token
-configure:17823: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| /* end confdefs.h. */
-| #include <stdio.h>
-| #ifdef HAVE_SYS_TYPES_H
-| # include <sys/types.h>
-| #endif
-| #ifdef HAVE_SYS_STAT_H
-| # include <sys/stat.h>
-| #endif
-| #ifdef STDC_HEADERS
-| # include <stdlib.h>
-| # include <stddef.h>
-| #else
-| # ifdef HAVE_STDLIB_H
-| # include <stdlib.h>
-| # endif
-| #endif
-| #ifdef HAVE_STRING_H
-| # if !defined STDC_HEADERS && defined HAVE_MEMORY_H
-| # include <memory.h>
-| # endif
-| # include <string.h>
-| #endif
-| #ifdef HAVE_STRINGS_H
-| # include <strings.h>
-| #endif
-| #ifdef HAVE_INTTYPES_H
-| # include <inttypes.h>
-| #endif
-| #ifdef HAVE_STDINT_H
-| # include <stdint.h>
-| #endif
-| #ifdef HAVE_UNISTD_H
-| # include <unistd.h>
-| #endif
-| int
-| main ()
-| {
-| if (sizeof ((size_t)))
-| return 0;
-| ;
-| return 0;
-| }
-configure:17846: result: yes
-configure:17860: checking for working alloca.h
-configure:17887: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:17894: $? = 0
-configure:17914: result: yes
-configure:17924: checking for alloca
-configure:17971: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:17978: $? = 0
-configure:17998: result: yes
-configure:18241: checking for stdlib.h
-configure:18248: result: yes
-configure:18241: checking for unistd.h
-configure:18248: result: yes
-configure:18386: checking for getpagesize
-configure:18442: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18449: $? = 0
-configure:18471: result: yes
-configure:18483: checking for working mmap
-configure:18630: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18634: $? = 0
-configure:18640: ./conftest
-configure:18644: $? = 0
-configure:18661: result: yes
-configure:18673: checking whether we are using the GNU C Library 2.1 or newer
-configure:18704: result: yes
-configure:18737: checking argz.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking argz.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for argz.h
-configure:18852: result: yes
-configure:18737: checking limits.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking limits.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for limits.h
-configure:18852: result: yes
-configure:18737: checking locale.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking locale.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for locale.h
-configure:18852: result: yes
-configure:18737: checking nl_types.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking nl_types.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for nl_types.h
-configure:18852: result: yes
-configure:18737: checking malloc.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking malloc.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for malloc.h
-configure:18852: result: yes
-configure:18737: checking stddef.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking stddef.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for stddef.h
-configure:18852: result: yes
-configure:18726: checking for stdlib.h
-configure:18733: result: yes
-configure:18726: checking for string.h
-configure:18733: result: yes
-configure:18726: checking for unistd.h
-configure:18733: result: yes
-configure:18737: checking sys/param.h usability
-configure:18754: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:18761: $? = 0
-configure:18775: result: yes
-configure:18779: checking sys/param.h presence
-configure:18794: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:18801: $? = 0
-configure:18815: result: yes
-configure:18843: checking for sys/param.h
-configure:18852: result: yes
-configure:18893: checking for feof_unlocked
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for fgets_unlocked
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for getcwd
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for getegid
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for geteuid
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for getgid
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for getuid
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for mempcpy
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c:149: warning: conflicting types for built-in function 'mempcpy'
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for munmap
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for putenv
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for setenv
-configure:18978: result: yes
-configure:18893: checking for setlocale
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for stpcpy
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c:154: warning: conflicting types for built-in function 'stpcpy'
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for strchr
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c:155: warning: conflicting types for built-in function 'strchr'
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for strcasecmp
-configure:18978: result: yes
-configure:18893: checking for strdup
-configure:18978: result: yes
-configure:18893: checking for strtoul
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for tsearch
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for __argz_count
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for __argz_stringify
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:18893: checking for __argz_next
-configure:18949: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:18956: $? = 0
-configure:18978: result: yes
-configure:19005: checking for iconv
-configure:19037: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:19044: $? = 0
-configure:19121: result: yes
-configure:19129: checking for iconv declaration
-configure:19168: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:19175: $? = 0
-configure:19194: result:
- extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
-configure:19210: checking for nl_langinfo and CODESET
-configure:19236: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:146: warning: unused variable 'cs'
-configure:19243: $? = 0
-configure:19264: result: yes
-configure:19275: checking for LC_MESSAGES
-configure:19301: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:19308: $? = 0
-configure:19328: result: yes
-configure:19338: checking whether NLS is requested
-configure:19347: result: yes
-configure:19361: checking whether included gettext is requested
-configure:19371: result: no
-configure:19391: checking libintl.h usability
-configure:19408: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:19415: $? = 0
-configure:19429: result: yes
-configure:19433: checking libintl.h presence
-configure:19448: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:19455: $? = 0
-configure:19469: result: yes
-configure:19497: checking for libintl.h
-configure:19504: result: yes
-configure:19509: checking for GNU gettext in libc
-configure:19537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:19544: $? = 0
-configure:19564: result: yes
-configure:19649: checking for dcgettext
-configure:19705: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c:169: warning: conflicting types for built-in function 'dcgettext'
-configure:19712: $? = 0
-configure:19734: result: yes
-configure:19750: checking for msgfmt
-configure:19777: result: /usr/bin/msgfmt
-configure:19786: checking for gmsgfmt
-configure:19817: result: /usr/bin/msgfmt
-configure:19828: checking for xgettext
-configure:19855: result: /usr/bin/xgettext
-configure:20032: checking for bison
-configure:20048: found /usr/bin/bison
-configure:20059: result: bison
-configure:20073: checking version of bison
-configure:20082: result: 2.4.1, ok
-configure:20121: checking for catalogs to be installed
-configure:20141: result: de eu ru it es uk fr pl nl cs id sk ko el zh_TW zh_CN pt_BR eo gl sv da lt tr ja hu et ca bg ga
-configure:20185: checking iconv.h usability
-configure:20202: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c >&5
-configure:20209: $? = 0
-configure:20223: result: yes
-configure:20227: checking iconv.h presence
-configure:20242: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include conftest.c
-configure:20249: $? = 0
-configure:20263: result: yes
-configure:20291: checking for iconv.h
-configure:20300: result: yes
-configure:20310: checking whether iconv.h defines iconv_t
-configure:20323: result: yes
-configure:20341: checking whether this iconv is good enough
-configure:20379: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-configure:20383: $? = 0
-configure:20389: ./conftest
-configure:20393: $? = 0
-configure:20411: result: yes
-configure:20419: checking whether iconv is non-transcribing
-configure:20458: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -L/lib conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:162: warning: passing argument 2 of 'iconv' from incompatible pointer type
-configure:20462: $? = 0
-configure:20468: ./conftest
-configure:20472: $? = 0
-configure:20490: result: no
-configure:20519: checking for bind_textdomain_codeset
-configure:20575: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c >&5
-configure:20582: $? = 0
-configure:20604: result: yes
-configure:20647: checking for library containing stringprep_check_version
-configure:20688: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c >&5
-/tmp/cclhZCVk.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/conftest.c:162: undefined reference to `stringprep_check_version'
-collect2: ld returned 1 exit status
-configure:20695: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| #define HAVE_ALLOCA_H 1
-| #define HAVE_ALLOCA 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_GETPAGESIZE 1
-| #define HAVE_MMAP 1
-| #define HAVE_ARGZ_H 1
-| #define HAVE_LIMITS_H 1
-| #define HAVE_LOCALE_H 1
-| #define HAVE_NL_TYPES_H 1
-| #define HAVE_MALLOC_H 1
-| #define HAVE_STDDEF_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_SYS_PARAM_H 1
-| #define HAVE_FEOF_UNLOCKED 1
-| #define HAVE_FGETS_UNLOCKED 1
-| #define HAVE_GETCWD 1
-| #define HAVE_GETEGID 1
-| #define HAVE_GETEUID 1
-| #define HAVE_GETGID 1
-| #define HAVE_GETUID 1
-| #define HAVE_MEMPCPY 1
-| #define HAVE_MUNMAP 1
-| #define HAVE_PUTENV 1
-| #define HAVE_SETENV 1
-| #define HAVE_SETLOCALE 1
-| #define HAVE_STPCPY 1
-| #define HAVE_STRCHR 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRTOUL 1
-| #define HAVE_TSEARCH 1
-| #define HAVE___ARGZ_COUNT 1
-| #define HAVE___ARGZ_STRINGIFY 1
-| #define HAVE___ARGZ_NEXT 1
-| #define HAVE_ICONV 1
-| #define ICONV_CONST
-| #define HAVE_LANGINFO_CODESET 1
-| #define HAVE_LC_MESSAGES 1
-| #define ENABLE_NLS 1
-| #define HAVE_GETTEXT 1
-| #define HAVE_DCGETTEXT 1
-| #define HAVE_ICONV_H 1
-| #define HAVE_ICONV_T_DEF 1
-| #define ICONV_NONTRANS 0
-| #define HAVE_BIND_TEXTDOMAIN_CODESET 1
-| /* end confdefs.h. */
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char stringprep_check_version ();
-| int
-| main ()
-| {
-| return stringprep_check_version ();
-| ;
-| return 0;
-| }
-configure:20688: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-configure:20695: $? = 0
-configure:20726: result: -lidn
-configure:20746: checking for idna_to_unicode_utf8_from_utf8
-configure:20802: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-/tmp/ccwjYYVI.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/conftest.c:186: undefined reference to `idna_to_unicode_utf8_from_utf8'
-collect2: ld returned 1 exit status
-configure:20809: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| #define HAVE_ALLOCA_H 1
-| #define HAVE_ALLOCA 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_GETPAGESIZE 1
-| #define HAVE_MMAP 1
-| #define HAVE_ARGZ_H 1
-| #define HAVE_LIMITS_H 1
-| #define HAVE_LOCALE_H 1
-| #define HAVE_NL_TYPES_H 1
-| #define HAVE_MALLOC_H 1
-| #define HAVE_STDDEF_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_SYS_PARAM_H 1
-| #define HAVE_FEOF_UNLOCKED 1
-| #define HAVE_FGETS_UNLOCKED 1
-| #define HAVE_GETCWD 1
-| #define HAVE_GETEGID 1
-| #define HAVE_GETEUID 1
-| #define HAVE_GETGID 1
-| #define HAVE_GETUID 1
-| #define HAVE_MEMPCPY 1
-| #define HAVE_MUNMAP 1
-| #define HAVE_PUTENV 1
-| #define HAVE_SETENV 1
-| #define HAVE_SETLOCALE 1
-| #define HAVE_STPCPY 1
-| #define HAVE_STRCHR 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRTOUL 1
-| #define HAVE_TSEARCH 1
-| #define HAVE___ARGZ_COUNT 1
-| #define HAVE___ARGZ_STRINGIFY 1
-| #define HAVE___ARGZ_NEXT 1
-| #define HAVE_ICONV 1
-| #define ICONV_CONST
-| #define HAVE_LANGINFO_CODESET 1
-| #define HAVE_LC_MESSAGES 1
-| #define ENABLE_NLS 1
-| #define HAVE_GETTEXT 1
-| #define HAVE_DCGETTEXT 1
-| #define HAVE_ICONV_H 1
-| #define HAVE_ICONV_T_DEF 1
-| #define ICONV_NONTRANS 0
-| #define HAVE_BIND_TEXTDOMAIN_CODESET 1
-| #define HAVE_LIBIDN 1
-| /* end confdefs.h. */
-| /* Define idna_to_unicode_utf8_from_utf8 to an innocuous variant, in case <limits.h> declares idna_to_unicode_utf8_from_utf8.
-| For example, HP-UX 11i <limits.h> declares gettimeofday. */
-| #define idna_to_unicode_utf8_from_utf8 innocuous_idna_to_unicode_utf8_from_utf8
-|
-| /* System header to define __stub macros and hopefully few prototypes,
-| which can conflict with char idna_to_unicode_utf8_from_utf8 (); below.
-| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
-| <limits.h> exists even on freestanding compilers. */
-|
-| #ifdef __STDC__
-| # include <limits.h>
-| #else
-| # include <assert.h>
-| #endif
-|
-| #undef idna_to_unicode_utf8_from_utf8
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char idna_to_unicode_utf8_from_utf8 ();
-| /* The GNU C library defines this for functions which it implements
-| to always fail with ENOSYS. Some functions are actually named
-| something starting with __ and the normal name is an alias. */
-| #if defined __stub_idna_to_unicode_utf8_from_utf8 || defined __stub___idna_to_unicode_utf8_from_utf8
-| choke me
-| #endif
-|
-| int
-| main ()
-| {
-| return idna_to_unicode_utf8_from_utf8 ();
-| ;
-| return 0;
-| }
-configure:20831: result: no
-configure:20746: checking for idna_to_unicode_8z8z
-configure:20802: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-configure:20809: $? = 0
-configure:20831: result: yes
-configure:20848: checking for idna_to_ascii_from_utf8
-configure:20904: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-/tmp/ccc7C3Fd.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/conftest.c:187: undefined reference to `idna_to_ascii_from_utf8'
-collect2: ld returned 1 exit status
-configure:20911: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| #define HAVE_ALLOCA_H 1
-| #define HAVE_ALLOCA 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_GETPAGESIZE 1
-| #define HAVE_MMAP 1
-| #define HAVE_ARGZ_H 1
-| #define HAVE_LIMITS_H 1
-| #define HAVE_LOCALE_H 1
-| #define HAVE_NL_TYPES_H 1
-| #define HAVE_MALLOC_H 1
-| #define HAVE_STDDEF_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_SYS_PARAM_H 1
-| #define HAVE_FEOF_UNLOCKED 1
-| #define HAVE_FGETS_UNLOCKED 1
-| #define HAVE_GETCWD 1
-| #define HAVE_GETEGID 1
-| #define HAVE_GETEUID 1
-| #define HAVE_GETGID 1
-| #define HAVE_GETUID 1
-| #define HAVE_MEMPCPY 1
-| #define HAVE_MUNMAP 1
-| #define HAVE_PUTENV 1
-| #define HAVE_SETENV 1
-| #define HAVE_SETLOCALE 1
-| #define HAVE_STPCPY 1
-| #define HAVE_STRCHR 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRTOUL 1
-| #define HAVE_TSEARCH 1
-| #define HAVE___ARGZ_COUNT 1
-| #define HAVE___ARGZ_STRINGIFY 1
-| #define HAVE___ARGZ_NEXT 1
-| #define HAVE_ICONV 1
-| #define ICONV_CONST
-| #define HAVE_LANGINFO_CODESET 1
-| #define HAVE_LC_MESSAGES 1
-| #define ENABLE_NLS 1
-| #define HAVE_GETTEXT 1
-| #define HAVE_DCGETTEXT 1
-| #define HAVE_ICONV_H 1
-| #define HAVE_ICONV_T_DEF 1
-| #define ICONV_NONTRANS 0
-| #define HAVE_BIND_TEXTDOMAIN_CODESET 1
-| #define HAVE_LIBIDN 1
-| #define HAVE_IDNA_TO_UNICODE_8Z8Z 1
-| /* end confdefs.h. */
-| /* Define idna_to_ascii_from_utf8 to an innocuous variant, in case <limits.h> declares idna_to_ascii_from_utf8.
-| For example, HP-UX 11i <limits.h> declares gettimeofday. */
-| #define idna_to_ascii_from_utf8 innocuous_idna_to_ascii_from_utf8
-|
-| /* System header to define __stub macros and hopefully few prototypes,
-| which can conflict with char idna_to_ascii_from_utf8 (); below.
-| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
-| <limits.h> exists even on freestanding compilers. */
-|
-| #ifdef __STDC__
-| # include <limits.h>
-| #else
-| # include <assert.h>
-| #endif
-|
-| #undef idna_to_ascii_from_utf8
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char idna_to_ascii_from_utf8 ();
-| /* The GNU C library defines this for functions which it implements
-| to always fail with ENOSYS. Some functions are actually named
-| something starting with __ and the normal name is an alias. */
-| #if defined __stub_idna_to_ascii_from_utf8 || defined __stub___idna_to_ascii_from_utf8
-| choke me
-| #endif
-|
-| int
-| main ()
-| {
-| return idna_to_ascii_from_utf8 ();
-| ;
-| return 0;
-| }
-configure:20933: result: no
-configure:20848: checking for idna_to_ascii_8z
-configure:20904: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-configure:20911: $? = 0
-configure:20933: result: yes
-configure:20950: checking for idna_to_ascii_lz
-configure:21006: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-configure:21013: $? = 0
-configure:21035: result: yes
-configure:20950: checking for idna_to_ascii_from_locale
-configure:21006: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-/tmp/cc03NfiA.o: In function `main':
-/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/conftest.c:189: undefined reference to `idna_to_ascii_from_locale'
-collect2: ld returned 1 exit status
-configure:21013: $? = 1
-configure: failed program was:
-| /* confdefs.h. */
-| #define PACKAGE_NAME ""
-| #define PACKAGE_TARNAME ""
-| #define PACKAGE_VERSION ""
-| #define PACKAGE_STRING ""
-| #define PACKAGE_BUGREPORT ""
-| #define PACKAGE "mutt"
-| #define VERSION "1.5.19"
-| #define STDC_HEADERS 1
-| #define HAVE_SYS_TYPES_H 1
-| #define HAVE_SYS_STAT_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_MEMORY_H 1
-| #define HAVE_STRINGS_H 1
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_STDINT_H 1
-| #define HAVE_UNISTD_H 1
-| #define __EXTENSIONS__ 1
-| #define _ALL_SOURCE 1
-| #define _GNU_SOURCE 1
-| #define _POSIX_PTHREAD_SEMANTICS 1
-| #define _TANDEM_SOURCE 1
-| #define PROTOTYPES 1
-| #define __PROTOTYPES 1
-| #define HAVE_STRING_H 1
-| #define _FILE_OFFSET_BITS 64
-| #define HAVE_FSEEKO 1
-| #define SIZEOF_OFF_T 8
-| #define HAVE_INTTYPES_H 1
-| #define HAVE_C99_INTTYPES 1
-| #define SIZEOF_SHORT 2
-| #define SIZEOF_INT 4
-| #define SIZEOF_LONG 4
-| #define SIZEOF_LONG_LONG 8
-| #define SENDMAIL "/usr/sbin/sendmail"
-| #define CRYPT_BACKEND_GPGME 1
-| #define HAVE_GPGME_PKA_TRUST 1
-| #define CRYPT_BACKEND_GPGME 1
-| #define CRYPT_BACKEND_CLASSIC_PGP 1
-| #define CRYPT_BACKEND_CLASSIC_SMIME 1
-| #define MIXMASTER "mixmaster"
-| #define HAVE_NCURSESW_NCURSES_H 1
-| #define HAVE_START_COLOR 1
-| #define HAVE_TYPEAHEAD 1
-| #define HAVE_BKGDSET 1
-| #define HAVE_CURS_SET 1
-| #define HAVE_META 1
-| #define HAVE_USE_DEFAULT_COLORS 1
-| #define HAVE_RESIZETERM 1
-| #define HAVE_COLOR 1
-| #define STDC_HEADERS 1
-| #define HAVE_STDARG_H 1
-| #define HAVE_SYS_IOCTL_H 1
-| #define HAVE_SYSEXITS_H 1
-| #define HAVE_SYS_TIME_H 1
-| #define HAVE_SYS_RESOURCE_H 1
-| #define HAVE_SETRLIMIT 1
-| #define HAVE_GETSID 1
-| #define RETSIGTYPE void
-| #define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-| #define HAVE_DECL_SYS_SIGLIST 1
-| #define HAVE_FGETPOS 1
-| #define HAVE_MEMMOVE 1
-| #define HAVE_SETEGID 1
-| #define HAVE_SRAND48 1
-| #define HAVE_STRERROR 1
-| #define HAVE_SETENV 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRSEP 1
-| #define HAVE_STRTOK_R 1
-| #define HAVE_GETOPT_H 1
-| #define HAVE_SNPRINTF 1
-| #define HAVE_VSNPRINTF 1
-| #define HAVE_FTRUNCATE 1
-| #define HAVE_STRFTIME 1
-| #define HAVE_FCHDIR 1
-| #define HAVE_REGCOMP 1
-| #define MAILPATH "/var/mail"
-| #define USE_DOTLOCK 1
-| #define USE_SETGID 1
-| #define DL_STANDALONE 1
-| #define USE_POP 1
-| #define USE_IMAP 1
-| #define USE_SMTP 1
-| #define HAVE_SYS_SELECT_H 1
-| #define HAVE_GETADDRINFO 1
-| #define USE_SOCKET 1
-| #define USE_GSS 1
-| #define USE_SSL 1
-| #define USE_SSL_GNUTLS 1
-| #define HAVE_LIBSASL2 1
-| #define USE_SASL 1
-| #define DEBUG 1
-| #define USE_FCNTL 1
-| #define HAVE_DIRENT_D_INO 1
-| #define USE_COMPRESSED 1
-| #define EXECSHELL "/bin/sh"
-| #define USE_HCACHE 1
-| #define HAVE_GDBM 1
-| #define HAVE_ALLOCA_H 1
-| #define HAVE_ALLOCA 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_GETPAGESIZE 1
-| #define HAVE_MMAP 1
-| #define HAVE_ARGZ_H 1
-| #define HAVE_LIMITS_H 1
-| #define HAVE_LOCALE_H 1
-| #define HAVE_NL_TYPES_H 1
-| #define HAVE_MALLOC_H 1
-| #define HAVE_STDDEF_H 1
-| #define HAVE_STDLIB_H 1
-| #define HAVE_STRING_H 1
-| #define HAVE_UNISTD_H 1
-| #define HAVE_SYS_PARAM_H 1
-| #define HAVE_FEOF_UNLOCKED 1
-| #define HAVE_FGETS_UNLOCKED 1
-| #define HAVE_GETCWD 1
-| #define HAVE_GETEGID 1
-| #define HAVE_GETEUID 1
-| #define HAVE_GETGID 1
-| #define HAVE_GETUID 1
-| #define HAVE_MEMPCPY 1
-| #define HAVE_MUNMAP 1
-| #define HAVE_PUTENV 1
-| #define HAVE_SETENV 1
-| #define HAVE_SETLOCALE 1
-| #define HAVE_STPCPY 1
-| #define HAVE_STRCHR 1
-| #define HAVE_STRCASECMP 1
-| #define HAVE_STRDUP 1
-| #define HAVE_STRTOUL 1
-| #define HAVE_TSEARCH 1
-| #define HAVE___ARGZ_COUNT 1
-| #define HAVE___ARGZ_STRINGIFY 1
-| #define HAVE___ARGZ_NEXT 1
-| #define HAVE_ICONV 1
-| #define ICONV_CONST
-| #define HAVE_LANGINFO_CODESET 1
-| #define HAVE_LC_MESSAGES 1
-| #define ENABLE_NLS 1
-| #define HAVE_GETTEXT 1
-| #define HAVE_DCGETTEXT 1
-| #define HAVE_ICONV_H 1
-| #define HAVE_ICONV_T_DEF 1
-| #define ICONV_NONTRANS 0
-| #define HAVE_BIND_TEXTDOMAIN_CODESET 1
-| #define HAVE_LIBIDN 1
-| #define HAVE_IDNA_TO_UNICODE_8Z8Z 1
-| #define HAVE_IDNA_TO_ASCII_8Z 1
-| #define HAVE_IDNA_TO_ASCII_LZ 1
-| /* end confdefs.h. */
-| /* Define idna_to_ascii_from_locale to an innocuous variant, in case <limits.h> declares idna_to_ascii_from_locale.
-| For example, HP-UX 11i <limits.h> declares gettimeofday. */
-| #define idna_to_ascii_from_locale innocuous_idna_to_ascii_from_locale
-|
-| /* System header to define __stub macros and hopefully few prototypes,
-| which can conflict with char idna_to_ascii_from_locale (); below.
-| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
-| <limits.h> exists even on freestanding compilers. */
-|
-| #ifdef __STDC__
-| # include <limits.h>
-| #else
-| # include <assert.h>
-| #endif
-|
-| #undef idna_to_ascii_from_locale
-|
-| /* Override any GCC internal prototype to avoid an error.
-| Use char because int might match the return type of a GCC
-| builtin and then its argument prototype would still apply. */
-| #ifdef __cplusplus
-| extern "C"
-| #endif
-| char idna_to_ascii_from_locale ();
-| /* The GNU C library defines this for functions which it implements
-| to always fail with ENOSYS. Some functions are actually named
-| something starting with __ and the normal name is an alias. */
-| #if defined __stub_idna_to_ascii_from_locale || defined __stub___idna_to_ascii_from_locale
-| choke me
-| #endif
-|
-| int
-| main ()
-| {
-| return idna_to_ascii_from_locale ();
-| ;
-| return 0;
-| }
-configure:21035: result: no
-configure:21067: checking wchar.h usability
-configure:21084: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-configure:21091: $? = 0
-configure:21105: result: yes
-configure:21109: checking wchar.h presence
-configure:21124: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c
-configure:21131: $? = 0
-configure:21145: result: yes
-configure:21173: checking for wchar.h
-configure:21182: result: yes
-configure:21198: checking for wchar_t
-configure:21230: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:166: warning: unused variable 'wc'
-configure:21237: $? = 0
-configure:21252: result: yes
-configure:21263: checking for wint_t
-configure:21295: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:166: warning: unused variable 'wc'
-configure:21302: $? = 0
-configure:21317: result: yes
-configure:21344: checking wctype.h usability
-configure:21361: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-configure:21368: $? = 0
-configure:21382: result: yes
-configure:21386: checking wctype.h presence
-configure:21401: gcc -E -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c
-configure:21408: $? = 0
-configure:21422: result: yes
-configure:21450: checking for wctype.h
-configure:21459: result: yes
-configure:21481: checking for iswalnum
-configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:180: warning: conflicting types for built-in function 'iswalnum'
-configure:21544: $? = 0
-configure:21566: result: yes
-configure:21481: checking for iswalpha
-configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:181: warning: conflicting types for built-in function 'iswalpha'
-configure:21544: $? = 0
-configure:21566: result: yes
-configure:21481: checking for iswcntrl
-configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:182: warning: conflicting types for built-in function 'iswcntrl'
-configure:21544: $? = 0
-configure:21566: result: yes
-configure:21481: checking for iswdigit
-configure:21537: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:183: warning: conflicting types for built-in function 'iswdigit'
-configure:21544: $? = 0
-configure:21566: result: yes
-configure:21587: checking for iswgraph
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:184: warning: conflicting types for built-in function 'iswgraph'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswlower
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:185: warning: conflicting types for built-in function 'iswlower'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswprint
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:186: warning: conflicting types for built-in function 'iswprint'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswpunct
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:187: warning: conflicting types for built-in function 'iswpunct'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswspace
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:188: warning: conflicting types for built-in function 'iswspace'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21587: checking for iswupper
-configure:21643: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:189: warning: conflicting types for built-in function 'iswupper'
-configure:21650: $? = 0
-configure:21672: result: yes
-configure:21690: checking for iswxdigit
-configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:190: warning: conflicting types for built-in function 'iswxdigit'
-configure:21753: $? = 0
-configure:21775: result: yes
-configure:21690: checking for towupper
-configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:191: warning: conflicting types for built-in function 'towupper'
-configure:21753: $? = 0
-configure:21775: result: yes
-configure:21690: checking for towlower
-configure:21746: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c:192: warning: conflicting types for built-in function 'towlower'
-configure:21753: $? = 0
-configure:21775: result: yes
-configure:21788: checking for mbstate_t
-configure:21820: gcc -c -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl conftest.c >&5
-conftest.c: In function 'main':
-conftest.c:180: warning: unused variable 's'
-configure:21827: $? = 0
-configure:21842: result: yes
-configure:21862: checking for wchar_t functions
-configure:21899: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c: In function 'main':
-conftest.c:184: warning: statement with no effect
-conftest.c:184: warning: statement with no effect
-conftest.c:184: warning: statement with no effect
-conftest.c:184: warning: statement with no effect
-conftest.c:185: warning: statement with no effect
-configure:21906: $? = 0
-configure:21926: result: yes
-configure:21941: checking for nl_langinfo and CODESET
-configure:21967: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c: In function 'main':
-conftest.c:175: warning: unused variable 'cs'
-configure:21974: $? = 0
-configure:21994: result: yes
-configure:22004: checking for nl_langinfo and YESEXPR
-configure:22030: gcc -o conftest -Wall -pedantic -Wno-long-long -Wall -g -O2 -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl -L/lib conftest.c -lidn >&5
-conftest.c: In function 'main':
-conftest.c:176: warning: unused variable 'cs'
-configure:22037: $? = 0
-configure:22057: result: yes
-configure:22070: checking for ospcat
-configure:22088: found /usr/bin/ospcat
-configure:22101: result: /usr/bin/ospcat
-configure:22111: checking for openjade docbook stylesheets
-configure:22126: result: not found: PDF documentation will not be built.
-configure:22309: creating ./config.status
-
-## ---------------------- ##
-## Running config.status. ##
-## ---------------------- ##
-
-This file was extended by config.status, which was
-generated by GNU Autoconf 2.63. Invocation command line was
-
- CONFIG_FILES =
- CONFIG_HEADERS =
- CONFIG_LINKS =
- CONFIG_COMMANDS =
- $ ./config.status
-
-on debian
-
-config.status:1011: creating Makefile
-config.status:1011: creating contrib/Makefile
-config.status:1011: creating doc/Makefile
-config.status:1011: creating imap/Makefile
-config.status:1011: creating intl/Makefile
-config.status:1011: creating m4/Makefile
-config.status:1011: creating po/Makefile.in
-config.status:1011: creating hcachever.sh
-config.status:1011: creating muttbug.sh
-config.status:1011: creating doc/instdoc.sh
-config.status:1011: creating config.h
-config.status:1278: executing depfiles commands
-config.status:1278: executing default-1 commands
-configure:23670: WARNING: unrecognized options: --with-sharedir, --enable-inodesort
-
-## ---------------- ##
-## Cache variables. ##
-## ---------------- ##
-
-ac_cv_build=i486-pc-linux-gnu
-ac_cv_c_bigendian=no
-ac_cv_c_compiler_gnu=yes
-ac_cv_c_const=yes
-ac_cv_c_inline=inline
-ac_cv_dirent_d_ino=yes
-ac_cv_env_CC_set=
-ac_cv_env_CC_value=
-ac_cv_env_CFLAGS_set=set
-ac_cv_env_CFLAGS_value='-Wall -g -O2'
-ac_cv_env_CPPFLAGS_set=set
-ac_cv_env_CPPFLAGS_value=-I/usr/include/qdbm
-ac_cv_env_CPP_set=
-ac_cv_env_CPP_value=
-ac_cv_env_GNUTLS_CFLAGS_set=
-ac_cv_env_GNUTLS_CFLAGS_value=
-ac_cv_env_GNUTLS_LIBS_set=
-ac_cv_env_GNUTLS_LIBS_value=
-ac_cv_env_LDFLAGS_set=set
-ac_cv_env_LDFLAGS_value=
-ac_cv_env_LIBS_set=
-ac_cv_env_LIBS_value=
-ac_cv_env_PKG_CONFIG_set=
-ac_cv_env_PKG_CONFIG_value=
-ac_cv_env_build_alias_set=set
-ac_cv_env_build_alias_value=i486-linux-gnu
-ac_cv_env_host_alias_set=
-ac_cv_env_host_alias_value=
-ac_cv_env_target_alias_set=
-ac_cv_env_target_alias_value=
-ac_cv_func___argz_count=yes
-ac_cv_func___argz_next=yes
-ac_cv_func___argz_stringify=yes
-ac_cv_func_alloca_works=yes
-ac_cv_func_bind_textdomain_codeset=yes
-ac_cv_func_dcgettext=yes
-ac_cv_func_decl_bkgdset=yes
-ac_cv_func_decl_curs_set=yes
-ac_cv_func_decl_meta=yes
-ac_cv_func_decl_resizeterm=yes
-ac_cv_func_decl_start_color=yes
-ac_cv_func_decl_typeahead=yes
-ac_cv_func_decl_use_default_colors=yes
-ac_cv_func_fchdir=yes
-ac_cv_func_feof_unlocked=yes
-ac_cv_func_fgetpos=yes
-ac_cv_func_fgets_unlocked=yes
-ac_cv_func_ftruncate=yes
-ac_cv_func_getaddrinfo=yes
-ac_cv_func_getcwd=yes
-ac_cv_func_getegid=yes
-ac_cv_func_geteuid=yes
-ac_cv_func_getgid=yes
-ac_cv_func_gethostent=yes
-ac_cv_func_getopt=yes
-ac_cv_func_getpagesize=yes
-ac_cv_func_getsid=yes
-ac_cv_func_getuid=yes
-ac_cv_func_idna_to_ascii_8z=yes
-ac_cv_func_idna_to_ascii_from_locale=no
-ac_cv_func_idna_to_ascii_from_utf8=no
-ac_cv_func_idna_to_ascii_lz=yes
-ac_cv_func_idna_to_unicode_8z8z=yes
-ac_cv_func_idna_to_unicode_utf8_from_utf8=no
-ac_cv_func_initscr=no
-ac_cv_func_iswalnum=yes
-ac_cv_func_iswalpha=yes
-ac_cv_func_iswcntrl=yes
-ac_cv_func_iswdigit=yes
-ac_cv_func_iswgraph=yes
-ac_cv_func_iswlower=yes
-ac_cv_func_iswprint=yes
-ac_cv_func_iswpunct=yes
-ac_cv_func_iswspace=yes
-ac_cv_func_iswupper=yes
-ac_cv_func_iswxdigit=yes
-ac_cv_func_memmove=yes
-ac_cv_func_mempcpy=yes
-ac_cv_func_mmap_fixed_mapped=yes
-ac_cv_func_munmap=yes
-ac_cv_func_putenv=yes
-ac_cv_func_regcomp=yes
-ac_cv_func_setegid=yes
-ac_cv_func_setenv=yes
-ac_cv_func_setlocale=yes
-ac_cv_func_setrlimit=yes
-ac_cv_func_setsockopt=yes
-ac_cv_func_snprintf=yes
-ac_cv_func_srand48=yes
-ac_cv_func_stpcpy=yes
-ac_cv_func_strcasecmp=yes
-ac_cv_func_strchr=yes
-ac_cv_func_strdup=yes
-ac_cv_func_strerror=yes
-ac_cv_func_strftime=yes
-ac_cv_func_strsep=yes
-ac_cv_func_strtok_r=yes
-ac_cv_func_strtoul=yes
-ac_cv_func_towlower=yes
-ac_cv_func_towupper=yes
-ac_cv_func_tsearch=yes
-ac_cv_func_vsnprintf=yes
-ac_cv_gdbmopen=yes
-ac_cv_gnu_library_2_1=yes
-ac_cv_have_decl_sys_siglist=yes
-ac_cv_header_argz_h=yes
-ac_cv_header_getopt_h=yes
-ac_cv_header_iconv_h=yes
-ac_cv_header_inttypes_h=yes
-ac_cv_header_ioctl_h=no
-ac_cv_header_libintl_h=yes
-ac_cv_header_limits_h=yes
-ac_cv_header_locale_h=yes
-ac_cv_header_malloc_h=yes
-ac_cv_header_memory_h=yes
-ac_cv_header_minix_config_h=no
-ac_cv_header_ncursesw_ncurses_h=yes
-ac_cv_header_nl_types_h=yes
-ac_cv_header_stdarg_h=yes
-ac_cv_header_stdc=yes
-ac_cv_header_stddef_h=yes
-ac_cv_header_stdint_h=yes
-ac_cv_header_stdlib_h=yes
-ac_cv_header_string_h=yes
-ac_cv_header_strings_h=yes
-ac_cv_header_sys_ioctl_h=yes
-ac_cv_header_sys_param_h=yes
-ac_cv_header_sys_resource_h=yes
-ac_cv_header_sys_select_h=yes
-ac_cv_header_sys_stat_h=yes
-ac_cv_header_sys_time_h=yes
-ac_cv_header_sys_types_h=yes
-ac_cv_header_sysexits_h=yes
-ac_cv_header_unistd_h=yes
-ac_cv_header_unix_h=no
-ac_cv_header_wchar_h=yes
-ac_cv_header_wctype_h=yes
-ac_cv_host=i486-pc-linux-gnu
-ac_cv_lib_ncurses___waddnwstr=no
-ac_cv_lib_ncursesw___initscr=yes
-ac_cv_lib_ncursesw___waddnwstr=yes
-ac_cv_lib_sasl2_sasl_client_init=yes
-ac_cv_objext=o
-ac_cv_path_DBX=no
-ac_cv_path_EGREP='/bin/grep -E'
-ac_cv_path_GDB=/usr/bin/gdb
-ac_cv_path_GMSGFMT=/usr/bin/msgfmt
-ac_cv_path_GPGME_CONFIG=/usr/bin/gpgme-config
-ac_cv_path_GREP=/bin/grep
-ac_cv_path_ISPELL=no
-ac_cv_path_KRB5CFGPATH=/usr/bin/krb5-config
-ac_cv_path_MSGFMT=/usr/bin/msgfmt
-ac_cv_path_OSPCAT=/usr/bin/ospcat
-ac_cv_path_SDB=no
-ac_cv_path_SENDMAIL=/usr/sbin/sendmail
-ac_cv_path_XGETTEXT=/usr/bin/xgettext
-ac_cv_path_ac_pt_PKG_CONFIG=/usr/bin/pkg-config
-ac_cv_path_install='/usr/bin/install -c'
-ac_cv_path_mkdir=/bin/mkdir
-ac_cv_prog_AWK=gawk
-ac_cv_prog_CPP='gcc -E'
-ac_cv_prog_INTLBISON=bison
-ac_cv_prog_ac_ct_AR=ar
-ac_cv_prog_ac_ct_CC=gcc
-ac_cv_prog_ac_ct_RANLIB=ranlib
-ac_cv_prog_cc_c89=
-ac_cv_prog_cc_g=yes
-ac_cv_prog_make_make_set=yes
-ac_cv_safe_to_define___extensions__=yes
-ac_cv_search_strerror='none required'
-ac_cv_search_stringprep_check_version=-lidn
-ac_cv_sizeof_int=4
-ac_cv_sizeof_long=4
-ac_cv_sizeof_long_long=8
-ac_cv_sizeof_off_t=8
-ac_cv_sizeof_short=2
-ac_cv_sys_file_offset_bits=64
-ac_cv_sys_largefile_CC=no
-ac_cv_sys_largefile_source=no
-ac_cv_type_off_t=yes
-ac_cv_type_pid_t=yes
-ac_cv_type_sig_atomic_t=yes
-ac_cv_type_signal=void
-ac_cv_type_size_t=yes
-ac_cv_type_ssize_t=yes
-ac_cv_type_uint32_t=yes
-ac_cv_working_alloca_h=yes
-am_cv_CC_dependencies_compiler_type=none
-am_cv_func_iconv=yes
-am_cv_langinfo_codeset=yes
-am_cv_lib_iconv=no
-am_cv_proto_iconv='extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);'
-am_cv_proto_iconv_arg1=
-am_cv_val_LC_MESSAGES=yes
-cf_cv_ncurses_header=ncursesw/ncurses.h
-gt_cv_func_gnugettext1_libc=yes
-mutt_cv_c99_snprintf=yes
-mutt_cv_c99_vsnprintf=yes
-mutt_cv_curses=/usr
-mutt_cv_docdir=/usr/share/doc
-mutt_cv_fcntl=yes
-mutt_cv_func_snprintf=yes
-mutt_cv_func_vsnprintf=yes
-mutt_cv_groupwrite=yes
-mutt_cv_iconv_good=yes
-mutt_cv_iconv_nontrans=no
-mutt_cv_langinfo_codeset=yes
-mutt_cv_langinfo_yesexpr=yes
-mutt_cv_mailpath=/var/mail
-mutt_cv_mbstate_t=yes
-mutt_cv_prefix=/usr
-mutt_cv_regex=no
-mutt_cv_regex_broken=no
-mutt_cv_setgid=yes
-mutt_cv_version=1.5.19
-mutt_cv_warnings=yes
-mutt_cv_wc_funcs=yes
-mutt_cv_wchar_t=yes
-mutt_cv_wint_t=yes
-mutt_cv_worldwrite=no
-nls_cv_force_use_gnu_gettext=no
-nls_cv_header_intl=
-nls_cv_header_libgt=
-nls_cv_use_gnu_gettext=no
-pkg_cv_GNUTLS_CFLAGS=' '
-pkg_cv_GNUTLS_LIBS='-lgnutls '
-
-## ----------------- ##
-## Output variables. ##
-## ----------------- ##
-
-ACLOCAL='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10'
-ALLOCA=''
-AMDEPBACKSLASH=''
-AMDEP_FALSE=''
-AMDEP_TRUE='#'
-AMTAR='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar'
-ANSI2KNR=''
-AR='ar'
-AUTOCONF='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf'
-AUTOHEADER='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader'
-AUTOMAKE='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10'
-AWK='gawk'
-BUILD_IMAP_FALSE='#'
-BUILD_IMAP_TRUE=''
-BUILD_INCLUDED_LIBINTL='no'
-CATALOGS=' de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo'
-CATOBJEXT='.gmo'
-CC='gcc'
-CCDEPMODE='depmode=none'
-CFLAGS='-Wall -pedantic -Wno-long-long -Wall -g -O2'
-CONFIG_STATUS_DEPENDENCIES='$(top_srcdir)/VERSION'
-CPP='gcc -E'
-CPPFLAGS='-I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl'
-CYGPATH_W='echo'
-DATADIRNAME='share'
-DBX='no'
-DEBUGGER='/usr/bin/gdb'
-DEFS='-DHAVE_CONFIG_H'
-DEPDIR='.deps'
-DOTLOCK_GROUP='mail'
-DOTLOCK_PERMISSION='2755'
-DOTLOCK_TARGET='mutt_dotlock$(EXEEXT)'
-DSLROOT=''
-ECHO_C=''
-ECHO_N='-n'
-ECHO_T=''
-EGREP='/bin/grep -E'
-EXEEXT=''
-GDB='/usr/bin/gdb'
-GENCAT='gencat'
-GLIBC21='yes'
-GMOFILES=' de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo'
-GMSGFMT='/usr/bin/msgfmt'
-GNUTLS_CFLAGS=' '
-GNUTLS_LIBS='-lgnutls '
-GPGME_CFLAGS=''
-GPGME_CONFIG='/usr/bin/gpgme-config'
-GPGME_LIBS='-lgpgme -lgpg-error'
-GREP='/bin/grep'
-INSTALL_DATA='${INSTALL} -m 644'
-INSTALL_PROGRAM='${INSTALL}'
-INSTALL_SCRIPT='${INSTALL}'
-INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
-INSTOBJEXT='.mo'
-INTLBISON='bison'
-INTLLIBS=''
-INTLOBJS=''
-INTL_LIBTOOL_SUFFIX_PREFIX=''
-ISPELL='no'
-KRB5CFGPATH='/usr/bin/krb5-config'
-LDFLAGS=' -L/lib'
-LIBICONV=''
-LIBIMAP='-Limap -limap'
-LIBIMAPDEPS='$(top_srcdir)/imap/imap.h imap/libimap.a'
-LIBOBJS=''
-LIBS='-lidn '
-LTLIBOBJS=''
-MAINT='#'
-MAINTAINER_MODE_FALSE=''
-MAINTAINER_MODE_TRUE='#'
-MAKEINFO='${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo'
-MKDIR_P='/bin/mkdir -p'
-MKINSTALLDIRS='../mkinstalldirs'
-MSGFMT='/usr/bin/msgfmt'
-MUTTLIBS=' -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm'
-MUTT_LIB_OBJECTS=' crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o'
-MUTT_MD5='mutt_md5'
-OBJEXT='o'
-OPS='$(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT '
-OSPCAT='/usr/bin/ospcat'
-PACKAGE='mutt'
-PACKAGE_BUGREPORT=''
-PACKAGE_NAME=''
-PACKAGE_STRING=''
-PACKAGE_TARNAME=''
-PACKAGE_VERSION=''
-PATH_SEPARATOR=':'
-PGPAUX_TARGET='pgpring$(EXEEXT) pgpewrap$(EXEEXT)'
-PKG_CONFIG='/usr/bin/pkg-config'
-POFILES=' de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po'
-POSUB='po'
-RANLIB='ranlib'
-SDB='no'
-SENDMAIL='/usr/sbin/sendmail'
-SET_MAKE=''
-SHELL='/bin/sh'
-SMIMEAUX_TARGET='smime_keys'
-STRIP=''
-U=''
-USE_GSS_FALSE='#'
-USE_GSS_TRUE=''
-USE_INCLUDED_LIBINTL='no'
-USE_NLS='yes'
-USE_SASL_FALSE='#'
-USE_SASL_TRUE=''
-USE_SSL_FALSE='#'
-USE_SSL_TRUE=''
-VERSION='1.5.19'
-XGETTEXT='/usr/bin/xgettext'
-ac_ct_CC='gcc'
-am__fastdepCC_FALSE=''
-am__fastdepCC_TRUE='#'
-am__include='include'
-am__isrc=' -I$(srcdir)'
-am__leading_dot='.'
-am__quote=''
-am__tar='${AMTAR} chof - "$$tardir"'
-am__untar='${AMTAR} xf -'
-bindir='${exec_prefix}/bin'
-build='i486-pc-linux-gnu'
-build_alias='i486-linux-gnu'
-build_cpu='i486'
-build_os='linux-gnu'
-build_vendor='pc'
-datadir='${datarootdir}'
-datarootdir='${prefix}/share'
-docdir='/usr/share/doc'
-dvidir='${docdir}'
-exec_prefix='${prefix}'
-host='i486-pc-linux-gnu'
-host_alias=''
-host_cpu='i486'
-host_os='linux-gnu'
-host_vendor='pc'
-htmldir='${docdir}'
-includedir='${prefix}/include'
-infodir='${datarootdir}/info'
-install_sh='$(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh'
-libdir='${exec_prefix}/lib'
-libexecdir='${exec_prefix}/libexec'
-localedir='${datarootdir}/locale'
-localstatedir='${prefix}/var'
-mandir='/usr/share/man'
-mkdir_p='/bin/mkdir -p'
-oldincludedir='/usr/include'
-pdfdir='${docdir}'
-prefix='/usr'
-program_transform_name='s,x,x,'
-psdir='${docdir}'
-sbindir='${exec_prefix}/sbin'
-sharedstatedir='${prefix}/com'
-sysconfdir='/etc'
-target_alias=''
-
-## ----------- ##
-## confdefs.h. ##
-## ----------- ##
-
-#define PACKAGE_NAME ""
-#define PACKAGE_TARNAME ""
-#define PACKAGE_VERSION ""
-#define PACKAGE_STRING ""
-#define PACKAGE_BUGREPORT ""
-#define PACKAGE "mutt"
-#define VERSION "1.5.19"
-#define STDC_HEADERS 1
-#define HAVE_SYS_TYPES_H 1
-#define HAVE_SYS_STAT_H 1
-#define HAVE_STDLIB_H 1
-#define HAVE_STRING_H 1
-#define HAVE_MEMORY_H 1
-#define HAVE_STRINGS_H 1
-#define HAVE_INTTYPES_H 1
-#define HAVE_STDINT_H 1
-#define HAVE_UNISTD_H 1
-#define __EXTENSIONS__ 1
-#define _ALL_SOURCE 1
-#define _GNU_SOURCE 1
-#define _POSIX_PTHREAD_SEMANTICS 1
-#define _TANDEM_SOURCE 1
-#define PROTOTYPES 1
-#define __PROTOTYPES 1
-#define HAVE_STRING_H 1
-#define _FILE_OFFSET_BITS 64
-#define HAVE_FSEEKO 1
-#define SIZEOF_OFF_T 8
-#define HAVE_INTTYPES_H 1
-#define HAVE_C99_INTTYPES 1
-#define SIZEOF_SHORT 2
-#define SIZEOF_INT 4
-#define SIZEOF_LONG 4
-#define SIZEOF_LONG_LONG 8
-#define SENDMAIL "/usr/sbin/sendmail"
-#define CRYPT_BACKEND_GPGME 1
-#define HAVE_GPGME_PKA_TRUST 1
-#define CRYPT_BACKEND_GPGME 1
-#define CRYPT_BACKEND_CLASSIC_PGP 1
-#define CRYPT_BACKEND_CLASSIC_SMIME 1
-#define MIXMASTER "mixmaster"
-#define HAVE_NCURSESW_NCURSES_H 1
-#define HAVE_START_COLOR 1
-#define HAVE_TYPEAHEAD 1
-#define HAVE_BKGDSET 1
-#define HAVE_CURS_SET 1
-#define HAVE_META 1
-#define HAVE_USE_DEFAULT_COLORS 1
-#define HAVE_RESIZETERM 1
-#define HAVE_COLOR 1
-#define STDC_HEADERS 1
-#define HAVE_STDARG_H 1
-#define HAVE_SYS_IOCTL_H 1
-#define HAVE_SYSEXITS_H 1
-#define HAVE_SYS_TIME_H 1
-#define HAVE_SYS_RESOURCE_H 1
-#define HAVE_SETRLIMIT 1
-#define HAVE_GETSID 1
-#define RETSIGTYPE void
-#define SIG_ATOMIC_VOLATILE_T volatile sig_atomic_t
-#define HAVE_DECL_SYS_SIGLIST 1
-#define HAVE_FGETPOS 1
-#define HAVE_MEMMOVE 1
-#define HAVE_SETEGID 1
-#define HAVE_SRAND48 1
-#define HAVE_STRERROR 1
-#define HAVE_SETENV 1
-#define HAVE_STRCASECMP 1
-#define HAVE_STRDUP 1
-#define HAVE_STRSEP 1
-#define HAVE_STRTOK_R 1
-#define HAVE_GETOPT_H 1
-#define HAVE_SNPRINTF 1
-#define HAVE_VSNPRINTF 1
-#define HAVE_FTRUNCATE 1
-#define HAVE_STRFTIME 1
-#define HAVE_FCHDIR 1
-#define HAVE_REGCOMP 1
-#define MAILPATH "/var/mail"
-#define USE_DOTLOCK 1
-#define USE_SETGID 1
-#define DL_STANDALONE 1
-#define USE_POP 1
-#define USE_IMAP 1
-#define USE_SMTP 1
-#define HAVE_SYS_SELECT_H 1
-#define HAVE_GETADDRINFO 1
-#define USE_SOCKET 1
-#define USE_GSS 1
-#define USE_SSL 1
-#define USE_SSL_GNUTLS 1
-#define HAVE_LIBSASL2 1
-#define USE_SASL 1
-#define DEBUG 1
-#define USE_FCNTL 1
-#define HAVE_DIRENT_D_INO 1
-#define USE_COMPRESSED 1
-#define EXECSHELL "/bin/sh"
-#define USE_HCACHE 1
-#define HAVE_GDBM 1
-#define HAVE_ALLOCA_H 1
-#define HAVE_ALLOCA 1
-#define HAVE_STDLIB_H 1
-#define HAVE_UNISTD_H 1
-#define HAVE_GETPAGESIZE 1
-#define HAVE_MMAP 1
-#define HAVE_ARGZ_H 1
-#define HAVE_LIMITS_H 1
-#define HAVE_LOCALE_H 1
-#define HAVE_NL_TYPES_H 1
-#define HAVE_MALLOC_H 1
-#define HAVE_STDDEF_H 1
-#define HAVE_STDLIB_H 1
-#define HAVE_STRING_H 1
-#define HAVE_UNISTD_H 1
-#define HAVE_SYS_PARAM_H 1
-#define HAVE_FEOF_UNLOCKED 1
-#define HAVE_FGETS_UNLOCKED 1
-#define HAVE_GETCWD 1
-#define HAVE_GETEGID 1
-#define HAVE_GETEUID 1
-#define HAVE_GETGID 1
-#define HAVE_GETUID 1
-#define HAVE_MEMPCPY 1
-#define HAVE_MUNMAP 1
-#define HAVE_PUTENV 1
-#define HAVE_SETENV 1
-#define HAVE_SETLOCALE 1
-#define HAVE_STPCPY 1
-#define HAVE_STRCHR 1
-#define HAVE_STRCASECMP 1
-#define HAVE_STRDUP 1
-#define HAVE_STRTOUL 1
-#define HAVE_TSEARCH 1
-#define HAVE___ARGZ_COUNT 1
-#define HAVE___ARGZ_STRINGIFY 1
-#define HAVE___ARGZ_NEXT 1
-#define HAVE_ICONV 1
-#define ICONV_CONST
-#define HAVE_LANGINFO_CODESET 1
-#define HAVE_LC_MESSAGES 1
-#define ENABLE_NLS 1
-#define HAVE_GETTEXT 1
-#define HAVE_DCGETTEXT 1
-#define HAVE_ICONV_H 1
-#define HAVE_ICONV_T_DEF 1
-#define ICONV_NONTRANS 0
-#define HAVE_BIND_TEXTDOMAIN_CODESET 1
-#define HAVE_LIBIDN 1
-#define HAVE_IDNA_TO_UNICODE_8Z8Z 1
-#define HAVE_IDNA_TO_ASCII_8Z 1
-#define HAVE_IDNA_TO_ASCII_LZ 1
-#define HAVE_WCHAR_H 1
-#define HAVE_WCTYPE_H 1
-#define HAVE_ISWALNUM 1
-#define HAVE_ISWALPHA 1
-#define HAVE_ISWCNTRL 1
-#define HAVE_ISWDIGIT 1
-#define HAVE_ISWGRAPH 1
-#define HAVE_ISWLOWER 1
-#define HAVE_ISWPRINT 1
-#define HAVE_ISWPUNCT 1
-#define HAVE_ISWSPACE 1
-#define HAVE_ISWUPPER 1
-#define HAVE_ISWXDIGIT 1
-#define HAVE_TOWUPPER 1
-#define HAVE_TOWLOWER 1
-#define HAVE_WC_FUNCS 1
-#define HAVE_LANGINFO_CODESET 1
-#define HAVE_LANGINFO_YESEXPR 1
-#define MAKEDOC_FULL 1
-
-configure: exit 0
+++ /dev/null
-#! /bin/sh
-# Generated by configure.
-# Run this file to recreate the current configuration.
-# Compiler output produced by configure, useful for debugging
-# configure, is in config.log if it exists.
-
-debug=false
-ac_cs_recheck=false
-ac_cs_silent=false
-SHELL=${CONFIG_SHELL-/bin/sh}
-## --------------------- ##
-## M4sh Initialization. ##
-## --------------------- ##
-
-# Be more Bourne compatible
-DUALCASE=1; export DUALCASE # for MKS sh
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
- emulate sh
- NULLCMD=:
- # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
- setopt NO_GLOB_SUBST
-else
- case `(set -o) 2>/dev/null` in
- *posix*) set -o posix ;;
-esac
-
-fi
-
-
-
-
-# PATH needs CR
-# Avoid depending upon Character Ranges.
-as_cr_letters='abcdefghijklmnopqrstuvwxyz'
-as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
-as_cr_Letters=$as_cr_letters$as_cr_LETTERS
-as_cr_digits='0123456789'
-as_cr_alnum=$as_cr_Letters$as_cr_digits
-
-as_nl='
-'
-export as_nl
-# Printing a long string crashes Solaris 7 /usr/bin/printf.
-as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
-if (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
- as_echo='printf %s\n'
- as_echo_n='printf %s'
-else
- if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
- as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
- as_echo_n='/usr/ucb/echo -n'
- else
- as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
- as_echo_n_body='eval
- arg=$1;
- case $arg in
- *"$as_nl"*)
- expr "X$arg" : "X\\(.*\\)$as_nl";
- arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
- esac;
- expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
- '
- export as_echo_n_body
- as_echo_n='sh -c $as_echo_n_body as_echo'
- fi
- export as_echo_body
- as_echo='sh -c $as_echo_body as_echo'
-fi
-
-# The user is always right.
-if test "${PATH_SEPARATOR+set}" != set; then
- PATH_SEPARATOR=:
- (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
- (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
- PATH_SEPARATOR=';'
- }
-fi
-
-# Support unset when possible.
-if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then
- as_unset=unset
-else
- as_unset=false
-fi
-
-
-# IFS
-# We need space, tab and new line, in precisely that order. Quoting is
-# there to prevent editors from complaining about space-tab.
-# (If _AS_PATH_WALK were called with IFS unset, it would disable word
-# splitting by setting IFS to empty value.)
-IFS=" "" $as_nl"
-
-# Find who we are. Look in the path if we contain no directory separator.
-case $0 in
- *[\\/]* ) as_myself=$0 ;;
- *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
-done
-IFS=$as_save_IFS
-
- ;;
-esac
-# We did not find ourselves, most probably we were run as `sh COMMAND'
-# in which case we are not to be found in the path.
-if test "x$as_myself" = x; then
- as_myself=$0
-fi
-if test ! -f "$as_myself"; then
- $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
- { (exit 1); exit 1; }
-fi
-
-# Work around bugs in pre-3.0 UWIN ksh.
-for as_var in ENV MAIL MAILPATH
-do ($as_unset $as_var) >/dev/null 2>&1 && $as_unset $as_var
-done
-PS1='$ '
-PS2='> '
-PS4='+ '
-
-# NLS nuisances.
-LC_ALL=C
-export LC_ALL
-LANGUAGE=C
-export LANGUAGE
-
-# Required to use basename.
-if expr a : '\(a\)' >/dev/null 2>&1 &&
- test "X`expr 00001 : '.*\(...\)'`" = X001; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
- as_basename=basename
-else
- as_basename=false
-fi
-
-
-# Name of the executable.
-as_me=`$as_basename -- "$0" ||
-$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X/"$0" |
- sed '/^.*\/\([^/][^/]*\)\/*$/{
- s//\1/
- q
- }
- /^X\/\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\/\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
-
-# CDPATH.
-$as_unset CDPATH
-
-
-
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x`expr $as_lineno_1 + 1`" = "x$as_lineno_2" || {
-
- # Create $as_me.lineno as a copy of $as_myself, but with $LINENO
- # uniformly replaced by the line number. The first 'sed' inserts a
- # line-number line after each line using $LINENO; the second 'sed'
- # does the real work. The second script uses 'N' to pair each
- # line-number line with the line containing $LINENO, and appends
- # trailing '-' during substitution so that $LINENO is not a special
- # case at line end.
- # (Raja R Harinath suggested sed '=', and Paul Eggert wrote the
- # scripts with optimization help from Paolo Bonzini. Blame Lee
- # E. McMahon (1931-1989) for sed's syntax. :-)
- sed -n '
- p
- /[$]LINENO/=
- ' <$as_myself |
- sed '
- s/[$]LINENO.*/&-/
- t lineno
- b
- :lineno
- N
- :loop
- s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
- t loop
- s/-\n.*//
- ' >$as_me.lineno &&
- chmod +x "$as_me.lineno" ||
- { $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2
- { (exit 1); exit 1; }; }
-
- # Don't try to exec as it changes $[0], causing all sort of problems
- # (the dirname of $[0] is not the place where we might find the
- # original and so on. Autoconf is especially sensitive to this).
- . "./$as_me.lineno"
- # Exit status is that of the last command.
- exit
-}
-
-
-if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
- as_dirname=dirname
-else
- as_dirname=false
-fi
-
-ECHO_C= ECHO_N= ECHO_T=
-case `echo -n x` in
--n*)
- case `echo 'x\c'` in
- *c*) ECHO_T=' ';; # ECHO_T is single tab character.
- *) ECHO_C='\c';;
- esac;;
-*)
- ECHO_N='-n';;
-esac
-if expr a : '\(a\)' >/dev/null 2>&1 &&
- test "X`expr 00001 : '.*\(...\)'`" = X001; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-rm -f conf$$ conf$$.exe conf$$.file
-if test -d conf$$.dir; then
- rm -f conf$$.dir/conf$$.file
-else
- rm -f conf$$.dir
- mkdir conf$$.dir 2>/dev/null
-fi
-if (echo >conf$$.file) 2>/dev/null; then
- if ln -s conf$$.file conf$$ 2>/dev/null; then
- as_ln_s='ln -s'
- # ... but there are two gotchas:
- # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
- # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
- # In both cases, we have to default to `cp -p'.
- ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
- as_ln_s='cp -p'
- elif ln conf$$.file conf$$ 2>/dev/null; then
- as_ln_s=ln
- else
- as_ln_s='cp -p'
- fi
-else
- as_ln_s='cp -p'
-fi
-rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
-rmdir conf$$.dir 2>/dev/null
-
-if mkdir -p . 2>/dev/null; then
- as_mkdir_p=:
-else
- test -d ./-p && rmdir ./-p
- as_mkdir_p=false
-fi
-
-if test -x / >/dev/null 2>&1; then
- as_test_x='test -x'
-else
- if ls -dL / >/dev/null 2>&1; then
- as_ls_L_option=L
- else
- as_ls_L_option=
- fi
- as_test_x='
- eval sh -c '\''
- if test -d "$1"; then
- test -d "$1/.";
- else
- case $1 in
- -*)set "./$1";;
- esac;
- case `ls -ld'$as_ls_L_option' "$1" 2>/dev/null` in
- ???[sx]*):;;*)false;;esac;fi
- '\'' sh
- '
-fi
-as_executable_p=$as_test_x
-
-# Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
-
-# Sed expression to map a string onto a valid variable name.
-as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
-
-
-exec 6>&1
-
-# Save the log message, to keep $[0] and so on meaningful, and to
-# report actual input values of CONFIG_FILES etc. instead of their
-# values after options handling.
-ac_log="
-This file was extended by $as_me, which was
-generated by GNU Autoconf 2.63. Invocation command line was
-
- CONFIG_FILES = $CONFIG_FILES
- CONFIG_HEADERS = $CONFIG_HEADERS
- CONFIG_LINKS = $CONFIG_LINKS
- CONFIG_COMMANDS = $CONFIG_COMMANDS
- $ $0 $@
-
-on `(hostname || uname -n) 2>/dev/null | sed 1q`
-"
-
-# Files that config.status was made for.
-config_files=" Makefile contrib/Makefile doc/Makefile imap/Makefile intl/Makefile m4/Makefile po/Makefile.in hcachever.sh muttbug.sh doc/instdoc.sh"
-config_headers=" config.h"
-config_commands=" depfiles default-1"
-
-ac_cs_usage="\
-\`$as_me' instantiates files from templates according to the
-current configuration.
-
-Usage: $0 [OPTION]... [FILE]...
-
- -h, --help print this help, then exit
- -V, --version print version number and configuration settings, then exit
- -q, --quiet, --silent
- do not print progress messages
- -d, --debug don't remove temporary files
- --recheck update $as_me by reconfiguring in the same conditions
- --file=FILE[:TEMPLATE]
- instantiate the configuration file FILE
- --header=FILE[:TEMPLATE]
- instantiate the configuration header FILE
-
-Configuration files:
-$config_files
-
-Configuration headers:
-$config_headers
-
-Configuration commands:
-$config_commands
-
-Report bugs to <bug-autoconf@gnu.org>."
-
-ac_cs_version="\
-config.status
-configured by ../configure, generated by GNU Autoconf 2.63,
- with options \"'--prefix=/usr' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-sharedir=/usr/share/mutt' '--with-docdir=/usr/share/doc' '--with-mailpath=/var/mail' '--disable-dependency-tracking' '--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-inodesort' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' '--without-qdbm' '--without-bdb' '--without-tokyocabinet' '--build' 'i486-linux-gnu' 'build_alias=i486-linux-gnu' 'CFLAGS=-Wall -g -O2' 'LDFLAGS=' 'CPPFLAGS=-I/usr/include/qdbm'\"
-
-Copyright (C) 2008 Free Software Foundation, Inc.
-This config.status script is free software; the Free Software Foundation
-gives unlimited permission to copy, distribute and modify it."
-
-ac_pwd='/home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu'
-srcdir='..'
-INSTALL='/usr/bin/install -c'
-MKDIR_P='/bin/mkdir -p'
-AWK='gawk'
-test -n "$AWK" || AWK=awk
-# The default lists apply if the user does not specify any file.
-ac_need_defaults=:
-while test $# != 0
-do
- case $1 in
- --*=*)
- ac_option=`expr "X$1" : 'X\([^=]*\)='`
- ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'`
- ac_shift=:
- ;;
- *)
- ac_option=$1
- ac_optarg=$2
- ac_shift=shift
- ;;
- esac
-
- case $ac_option in
- # Handling of the options.
- -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
- ac_cs_recheck=: ;;
- --version | --versio | --versi | --vers | --ver | --ve | --v | -V )
- $as_echo "$ac_cs_version"; exit ;;
- --debug | --debu | --deb | --de | --d | -d )
- debug=: ;;
- --file | --fil | --fi | --f )
- $ac_shift
- case $ac_optarg in
- *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
- esac
- CONFIG_FILES="$CONFIG_FILES '$ac_optarg'"
- ac_need_defaults=false;;
- --header | --heade | --head | --hea )
- $ac_shift
- case $ac_optarg in
- *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
- esac
- CONFIG_HEADERS="$CONFIG_HEADERS '$ac_optarg'"
- ac_need_defaults=false;;
- --he | --h)
- # Conflict between --help and --header
- { $as_echo "$as_me: error: ambiguous option: $1
-Try \`$0 --help' for more information." >&2
- { (exit 1); exit 1; }; };;
- --help | --hel | -h )
- $as_echo "$ac_cs_usage"; exit ;;
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil | --si | --s)
- ac_cs_silent=: ;;
-
- # This is an error.
- -*) { $as_echo "$as_me: error: unrecognized option: $1
-Try \`$0 --help' for more information." >&2
- { (exit 1); exit 1; }; } ;;
-
- *) ac_config_targets="$ac_config_targets $1"
- ac_need_defaults=false ;;
-
- esac
- shift
-done
-
-ac_configure_extra_args=
-
-if $ac_cs_silent; then
- exec 6>/dev/null
- ac_configure_extra_args="$ac_configure_extra_args --silent"
-fi
-
-if $ac_cs_recheck; then
- set X '/bin/sh' '../configure' '--prefix=/usr' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-sharedir=/usr/share/mutt' '--with-docdir=/usr/share/doc' '--with-mailpath=/var/mail' '--disable-dependency-tracking' '--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-inodesort' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' '--without-qdbm' '--without-bdb' '--without-tokyocabinet' '--build' 'i486-linux-gnu' 'build_alias=i486-linux-gnu' 'CFLAGS=-Wall -g -O2' 'LDFLAGS=' 'CPPFLAGS=-I/usr/include/qdbm' $ac_configure_extra_args --no-create --no-recursion
- shift
- $as_echo "running CONFIG_SHELL=/bin/sh $*" >&6
- CONFIG_SHELL='/bin/sh'
- export CONFIG_SHELL
- exec "$@"
-fi
-
-exec 5>>config.log
-{
- echo
- sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
-## Running $as_me. ##
-_ASBOX
- $as_echo "$ac_log"
-} >&5
-
-#
-# INIT-COMMANDS
-#
-AMDEP_TRUE="#" ac_aux_dir=".."
-
-
-
-# Handling of arguments.
-for ac_config_target in $ac_config_targets
-do
- case $ac_config_target in
- "config.h") CONFIG_HEADERS="$CONFIG_HEADERS config.h" ;;
- "depfiles") CONFIG_COMMANDS="$CONFIG_COMMANDS depfiles" ;;
- "default-1") CONFIG_COMMANDS="$CONFIG_COMMANDS default-1" ;;
- "Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;;
- "contrib/Makefile") CONFIG_FILES="$CONFIG_FILES contrib/Makefile" ;;
- "doc/Makefile") CONFIG_FILES="$CONFIG_FILES doc/Makefile" ;;
- "imap/Makefile") CONFIG_FILES="$CONFIG_FILES imap/Makefile" ;;
- "intl/Makefile") CONFIG_FILES="$CONFIG_FILES intl/Makefile" ;;
- "m4/Makefile") CONFIG_FILES="$CONFIG_FILES m4/Makefile" ;;
- "po/Makefile.in") CONFIG_FILES="$CONFIG_FILES po/Makefile.in" ;;
- "hcachever.sh") CONFIG_FILES="$CONFIG_FILES hcachever.sh" ;;
- "muttbug.sh") CONFIG_FILES="$CONFIG_FILES muttbug.sh" ;;
- "doc/instdoc.sh") CONFIG_FILES="$CONFIG_FILES doc/instdoc.sh" ;;
-
- *) { { $as_echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5
-$as_echo "$as_me: error: invalid argument: $ac_config_target" >&2;}
- { (exit 1); exit 1; }; };;
- esac
-done
-
-
-# If the user did not use the arguments to specify the items to instantiate,
-# then the envvar interface is used. Set only those that are not.
-# We use the long form for the default assignment because of an extremely
-# bizarre bug on SunOS 4.1.3.
-if $ac_need_defaults; then
- test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
- test "${CONFIG_HEADERS+set}" = set || CONFIG_HEADERS=$config_headers
- test "${CONFIG_COMMANDS+set}" = set || CONFIG_COMMANDS=$config_commands
-fi
-
-# Have a temporary directory for convenience. Make it in the build tree
-# simply because there is no reason against having it here, and in addition,
-# creating and moving files from /tmp can sometimes cause problems.
-# Hook for its removal unless debugging.
-# Note that there is a small window in which the directory will not be cleaned:
-# after its creation but before its name has been assigned to `$tmp'.
-$debug ||
-{
- tmp=
- trap 'exit_status=$?
- { test -z "$tmp" || test ! -d "$tmp" || rm -fr "$tmp"; } && exit $exit_status
-' 0
- trap '{ (exit 1); exit 1; }' 1 2 13 15
-}
-# Create a (secure) tmp directory for tmp files.
-
-{
- tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` &&
- test -n "$tmp" && test -d "$tmp"
-} ||
-{
- tmp=./conf$$-$RANDOM
- (umask 077 && mkdir "$tmp")
-} ||
-{
- $as_echo "$as_me: cannot create a temporary directory in ." >&2
- { (exit 1); exit 1; }
-}
-
-# Set up the scripts for CONFIG_FILES section.
-# No need to generate them if there are no CONFIG_FILES.
-# This happens for instance with `./config.status config.h'.
-if test -n "$CONFIG_FILES"; then
-
-
-ac_cr='\r'
-ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' </dev/null 2>/dev/null`
-if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then
- ac_cs_awk_cr='\\r'
-else
- ac_cs_awk_cr=$ac_cr
-fi
-
-echo 'BEGIN {' >"$tmp/subs1.awk" &&
-cat >>"$tmp/subs1.awk" <<\_ACAWK &&
-S["LTLIBOBJS"]=""
-S["DSLROOT"]=""
-S["OSPCAT"]="/usr/bin/ospcat"
-S["INTL_LIBTOOL_SUFFIX_PREFIX"]=""
-S["MKINSTALLDIRS"]="../mkinstalldirs"
-S["GENCAT"]="gencat"
-S["INSTOBJEXT"]=".mo"
-S["DATADIRNAME"]="share"
-S["POSUB"]="po"
-S["POFILES"]=" de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po "\
-"ja.po hu.po et.po ca.po bg.po ga.po"
-S["INTLOBJS"]=""
-S["INTLLIBS"]=""
-S["GMOFILES"]=" de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gm"\
-"o da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo"
-S["CATOBJEXT"]=".gmo"
-S["CATALOGS"]=" de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gm"\
-"o da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo"
-S["USE_INCLUDED_LIBINTL"]="no"
-S["BUILD_INCLUDED_LIBINTL"]="no"
-S["INTLBISON"]="bison"
-S["XGETTEXT"]="/usr/bin/xgettext"
-S["GMSGFMT"]="/usr/bin/msgfmt"
-S["MSGFMT"]="/usr/bin/msgfmt"
-S["USE_NLS"]="yes"
-S["LIBICONV"]=""
-S["GLIBC21"]="yes"
-S["ALLOCA"]=""
-S["LIBIMAPDEPS"]="$(top_srcdir)/imap/imap.h imap/libimap.a"
-S["LIBIMAP"]="-Limap -limap"
-S["MUTT_LIB_OBJECTS"]=" crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-"\
-"classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mut"\
-"t_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o"
-S["MUTTLIBS"]=" -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm"
-S["MUTT_MD5"]="mutt_md5"
-S["USE_SASL_FALSE"]="#"
-S["USE_SASL_TRUE"]=""
-S["USE_SSL_FALSE"]="#"
-S["USE_SSL_TRUE"]=""
-S["GNUTLS_LIBS"]="-lgnutls "
-S["GNUTLS_CFLAGS"]=" "
-S["PKG_CONFIG"]="/usr/bin/pkg-config"
-S["USE_GSS_FALSE"]="#"
-S["USE_GSS_TRUE"]=""
-S["KRB5CFGPATH"]="/usr/bin/krb5-config"
-S["BUILD_IMAP_FALSE"]="#"
-S["BUILD_IMAP_TRUE"]=""
-S["DOTLOCK_PERMISSION"]="2755"
-S["DOTLOCK_GROUP"]="mail"
-S["DOTLOCK_TARGET"]="mutt_dotlock$(EXEEXT)"
-S["LIBOBJS"]=""
-S["ISPELL"]="no"
-S["SMIMEAUX_TARGET"]="smime_keys"
-S["PGPAUX_TARGET"]="pgpring$(EXEEXT) pgpewrap$(EXEEXT)"
-S["OPS"]="$(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT "
-S["GPGME_LIBS"]="-lgpgme -lgpg-error"
-S["GPGME_CFLAGS"]=""
-S["GPGME_CONFIG"]="/usr/bin/gpgme-config"
-S["SENDMAIL"]="/usr/sbin/sendmail"
-S["DEBUGGER"]="/usr/bin/gdb"
-S["SDB"]="no"
-S["GDB"]="/usr/bin/gdb"
-S["DBX"]="no"
-S["AR"]="ar"
-S["RANLIB"]="ranlib"
-S["ANSI2KNR"]=""
-S["U"]=""
-S["host_os"]="linux-gnu"
-S["host_vendor"]="pc"
-S["host_cpu"]="i486"
-S["host"]="i486-pc-linux-gnu"
-S["build_os"]="linux-gnu"
-S["build_vendor"]="pc"
-S["build_cpu"]="i486"
-S["build"]="i486-pc-linux-gnu"
-S["EGREP"]="/bin/grep -E"
-S["GREP"]="/bin/grep"
-S["CPP"]="gcc -E"
-S["am__fastdepCC_FALSE"]=""
-S["am__fastdepCC_TRUE"]="#"
-S["CCDEPMODE"]="depmode=none"
-S["AMDEPBACKSLASH"]=""
-S["AMDEP_FALSE"]=""
-S["AMDEP_TRUE"]="#"
-S["am__quote"]=""
-S["am__include"]="include"
-S["DEPDIR"]=".deps"
-S["OBJEXT"]="o"
-S["EXEEXT"]=""
-S["ac_ct_CC"]="gcc"
-S["CPPFLAGS"]="-I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl"
-S["LDFLAGS"]=" -L/lib"
-S["CFLAGS"]="-Wall -pedantic -Wno-long-long -Wall -g -O2"
-S["CC"]="gcc"
-S["CONFIG_STATUS_DEPENDENCIES"]="$(top_srcdir)/VERSION"
-S["MAINT"]="#"
-S["MAINTAINER_MODE_FALSE"]=""
-S["MAINTAINER_MODE_TRUE"]="#"
-S["am__untar"]="${AMTAR} xf -"
-S["am__tar"]="${AMTAR} chof - \"$$tardir\""
-S["AMTAR"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar"
-S["am__leading_dot"]="."
-S["SET_MAKE"]=""
-S["AWK"]="gawk"
-S["mkdir_p"]="/bin/mkdir -p"
-S["MKDIR_P"]="/bin/mkdir -p"
-S["INSTALL_STRIP_PROGRAM"]="$(install_sh) -c -s"
-S["STRIP"]=""
-S["install_sh"]="$(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh"
-S["MAKEINFO"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo"
-S["AUTOHEADER"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader"
-S["AUTOMAKE"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10"
-S["AUTOCONF"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf"
-S["ACLOCAL"]="${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10"
-S["VERSION"]="1.5.19"
-S["PACKAGE"]="mutt"
-S["CYGPATH_W"]="echo"
-S["am__isrc"]=" -I$(srcdir)"
-S["INSTALL_DATA"]="${INSTALL} -m 644"
-S["INSTALL_SCRIPT"]="${INSTALL}"
-S["INSTALL_PROGRAM"]="${INSTALL}"
-S["target_alias"]=""
-S["host_alias"]=""
-S["build_alias"]="i486-linux-gnu"
-S["LIBS"]="-lidn "
-S["ECHO_T"]=""
-S["ECHO_N"]="-n"
-S["ECHO_C"]=""
-S["DEFS"]="-DHAVE_CONFIG_H"
-S["mandir"]="/usr/share/man"
-S["localedir"]="${datarootdir}/locale"
-S["libdir"]="${exec_prefix}/lib"
-S["psdir"]="${docdir}"
-S["pdfdir"]="${docdir}"
-S["dvidir"]="${docdir}"
-S["htmldir"]="${docdir}"
-S["infodir"]="${datarootdir}/info"
-S["docdir"]="/usr/share/doc"
-S["oldincludedir"]="/usr/include"
-S["includedir"]="${prefix}/include"
-S["localstatedir"]="${prefix}/var"
-S["sharedstatedir"]="${prefix}/com"
-S["sysconfdir"]="/etc"
-S["datadir"]="${datarootdir}"
-S["datarootdir"]="${prefix}/share"
-S["libexecdir"]="${exec_prefix}/libexec"
-S["sbindir"]="${exec_prefix}/sbin"
-S["bindir"]="${exec_prefix}/bin"
-S["program_transform_name"]="s,x,x,"
-S["prefix"]="/usr"
-S["exec_prefix"]="${prefix}"
-S["PACKAGE_BUGREPORT"]=""
-S["PACKAGE_STRING"]=""
-S["PACKAGE_VERSION"]=""
-S["PACKAGE_TARNAME"]=""
-S["PACKAGE_NAME"]=""
-S["PATH_SEPARATOR"]=":"
-S["SHELL"]="/bin/sh"
-_ACAWK
-cat >>"$tmp/subs1.awk" <<_ACAWK &&
- for (key in S) S_is_set[key] = 1
- FS = "\a"
-
-}
-{
- line = $ 0
- nfields = split(line, field, "@")
- substed = 0
- len = length(field[1])
- for (i = 2; i < nfields; i++) {
- key = field[i]
- keylen = length(key)
- if (S_is_set[key]) {
- value = S[key]
- line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3)
- len += length(value) + length(field[++i])
- substed = 1
- } else
- len += 1 + keylen
- }
-
- print line
-}
-
-_ACAWK
-if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then
- sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g"
-else
- cat
-fi < "$tmp/subs1.awk" > "$tmp/subs.awk" \
- || { { $as_echo "$as_me:$LINENO: error: could not setup config files machinery" >&5
-$as_echo "$as_me: error: could not setup config files machinery" >&2;}
- { (exit 1); exit 1; }; }
-fi # test -n "$CONFIG_FILES"
-
-# Set up the scripts for CONFIG_HEADERS section.
-# No need to generate them if there are no CONFIG_HEADERS.
-# This happens for instance with `./config.status Makefile'.
-if test -n "$CONFIG_HEADERS"; then
-cat >"$tmp/defines.awk" <<\_ACAWK ||
-BEGIN {
-D["PACKAGE_NAME"]=" \"\""
-D["PACKAGE_TARNAME"]=" \"\""
-D["PACKAGE_VERSION"]=" \"\""
-D["PACKAGE_STRING"]=" \"\""
-D["PACKAGE_BUGREPORT"]=" \"\""
-D["PACKAGE"]=" \"mutt\""
-D["VERSION"]=" \"1.5.19\""
-D["STDC_HEADERS"]=" 1"
-D["HAVE_SYS_TYPES_H"]=" 1"
-D["HAVE_SYS_STAT_H"]=" 1"
-D["HAVE_STDLIB_H"]=" 1"
-D["HAVE_STRING_H"]=" 1"
-D["HAVE_MEMORY_H"]=" 1"
-D["HAVE_STRINGS_H"]=" 1"
-D["HAVE_INTTYPES_H"]=" 1"
-D["HAVE_STDINT_H"]=" 1"
-D["HAVE_UNISTD_H"]=" 1"
-D["__EXTENSIONS__"]=" 1"
-D["_ALL_SOURCE"]=" 1"
-D["_GNU_SOURCE"]=" 1"
-D["_POSIX_PTHREAD_SEMANTICS"]=" 1"
-D["_TANDEM_SOURCE"]=" 1"
-D["PROTOTYPES"]=" 1"
-D["__PROTOTYPES"]=" 1"
-D["HAVE_STRING_H"]=" 1"
-D["_FILE_OFFSET_BITS"]=" 64"
-D["HAVE_FSEEKO"]=" 1"
-D["SIZEOF_OFF_T"]=" 8"
-D["HAVE_INTTYPES_H"]=" 1"
-D["HAVE_C99_INTTYPES"]=" 1"
-D["SIZEOF_SHORT"]=" 2"
-D["SIZEOF_INT"]=" 4"
-D["SIZEOF_LONG"]=" 4"
-D["SIZEOF_LONG_LONG"]=" 8"
-D["SENDMAIL"]=" \"/usr/sbin/sendmail\""
-D["CRYPT_BACKEND_GPGME"]=" 1"
-D["HAVE_GPGME_PKA_TRUST"]=" 1"
-D["CRYPT_BACKEND_GPGME"]=" 1"
-D["CRYPT_BACKEND_CLASSIC_PGP"]=" 1"
-D["CRYPT_BACKEND_CLASSIC_SMIME"]=" 1"
-D["MIXMASTER"]=" \"mixmaster\""
-D["HAVE_NCURSESW_NCURSES_H"]=" 1"
-D["HAVE_START_COLOR"]=" 1"
-D["HAVE_TYPEAHEAD"]=" 1"
-D["HAVE_BKGDSET"]=" 1"
-D["HAVE_CURS_SET"]=" 1"
-D["HAVE_META"]=" 1"
-D["HAVE_USE_DEFAULT_COLORS"]=" 1"
-D["HAVE_RESIZETERM"]=" 1"
-D["HAVE_COLOR"]=" 1"
-D["STDC_HEADERS"]=" 1"
-D["HAVE_STDARG_H"]=" 1"
-D["HAVE_SYS_IOCTL_H"]=" 1"
-D["HAVE_SYSEXITS_H"]=" 1"
-D["HAVE_SYS_TIME_H"]=" 1"
-D["HAVE_SYS_RESOURCE_H"]=" 1"
-D["HAVE_SETRLIMIT"]=" 1"
-D["HAVE_GETSID"]=" 1"
-D["RETSIGTYPE"]=" void"
-D["SIG_ATOMIC_VOLATILE_T"]=" volatile sig_atomic_t"
-D["HAVE_DECL_SYS_SIGLIST"]=" 1"
-D["HAVE_FGETPOS"]=" 1"
-D["HAVE_MEMMOVE"]=" 1"
-D["HAVE_SETEGID"]=" 1"
-D["HAVE_SRAND48"]=" 1"
-D["HAVE_STRERROR"]=" 1"
-D["HAVE_SETENV"]=" 1"
-D["HAVE_STRCASECMP"]=" 1"
-D["HAVE_STRDUP"]=" 1"
-D["HAVE_STRSEP"]=" 1"
-D["HAVE_STRTOK_R"]=" 1"
-D["HAVE_GETOPT_H"]=" 1"
-D["HAVE_SNPRINTF"]=" 1"
-D["HAVE_VSNPRINTF"]=" 1"
-D["HAVE_FTRUNCATE"]=" 1"
-D["HAVE_STRFTIME"]=" 1"
-D["HAVE_FCHDIR"]=" 1"
-D["HAVE_REGCOMP"]=" 1"
-D["MAILPATH"]=" \"/var/mail\""
-D["USE_DOTLOCK"]=" 1"
-D["USE_SETGID"]=" 1"
-D["DL_STANDALONE"]=" 1"
-D["USE_POP"]=" 1"
-D["USE_IMAP"]=" 1"
-D["USE_SMTP"]=" 1"
-D["HAVE_SYS_SELECT_H"]=" 1"
-D["HAVE_GETADDRINFO"]=" 1"
-D["USE_SOCKET"]=" 1"
-D["USE_GSS"]=" 1"
-D["USE_SSL"]=" 1"
-D["USE_SSL_GNUTLS"]=" 1"
-D["HAVE_LIBSASL2"]=" 1"
-D["USE_SASL"]=" 1"
-D["DEBUG"]=" 1"
-D["USE_FCNTL"]=" 1"
-D["HAVE_DIRENT_D_INO"]=" 1"
-D["USE_COMPRESSED"]=" 1"
-D["EXECSHELL"]=" \"/bin/sh\""
-D["USE_HCACHE"]=" 1"
-D["HAVE_GDBM"]=" 1"
-D["HAVE_ALLOCA_H"]=" 1"
-D["HAVE_ALLOCA"]=" 1"
-D["HAVE_STDLIB_H"]=" 1"
-D["HAVE_UNISTD_H"]=" 1"
-D["HAVE_GETPAGESIZE"]=" 1"
-D["HAVE_MMAP"]=" 1"
-D["HAVE_ARGZ_H"]=" 1"
-D["HAVE_LIMITS_H"]=" 1"
-D["HAVE_LOCALE_H"]=" 1"
-D["HAVE_NL_TYPES_H"]=" 1"
-D["HAVE_MALLOC_H"]=" 1"
-D["HAVE_STDDEF_H"]=" 1"
-D["HAVE_STDLIB_H"]=" 1"
-D["HAVE_STRING_H"]=" 1"
-D["HAVE_UNISTD_H"]=" 1"
-D["HAVE_SYS_PARAM_H"]=" 1"
-D["HAVE_FEOF_UNLOCKED"]=" 1"
-D["HAVE_FGETS_UNLOCKED"]=" 1"
-D["HAVE_GETCWD"]=" 1"
-D["HAVE_GETEGID"]=" 1"
-D["HAVE_GETEUID"]=" 1"
-D["HAVE_GETGID"]=" 1"
-D["HAVE_GETUID"]=" 1"
-D["HAVE_MEMPCPY"]=" 1"
-D["HAVE_MUNMAP"]=" 1"
-D["HAVE_PUTENV"]=" 1"
-D["HAVE_SETENV"]=" 1"
-D["HAVE_SETLOCALE"]=" 1"
-D["HAVE_STPCPY"]=" 1"
-D["HAVE_STRCHR"]=" 1"
-D["HAVE_STRCASECMP"]=" 1"
-D["HAVE_STRDUP"]=" 1"
-D["HAVE_STRTOUL"]=" 1"
-D["HAVE_TSEARCH"]=" 1"
-D["HAVE___ARGZ_COUNT"]=" 1"
-D["HAVE___ARGZ_STRINGIFY"]=" 1"
-D["HAVE___ARGZ_NEXT"]=" 1"
-D["HAVE_ICONV"]=" 1"
-D["ICONV_CONST"]=" "
-D["HAVE_LANGINFO_CODESET"]=" 1"
-D["HAVE_LC_MESSAGES"]=" 1"
-D["ENABLE_NLS"]=" 1"
-D["HAVE_GETTEXT"]=" 1"
-D["HAVE_DCGETTEXT"]=" 1"
-D["HAVE_ICONV_H"]=" 1"
-D["HAVE_ICONV_T_DEF"]=" 1"
-D["ICONV_NONTRANS"]=" 0"
-D["HAVE_BIND_TEXTDOMAIN_CODESET"]=" 1"
-D["HAVE_LIBIDN"]=" 1"
-D["HAVE_IDNA_TO_UNICODE_8Z8Z"]=" 1"
-D["HAVE_IDNA_TO_ASCII_8Z"]=" 1"
-D["HAVE_IDNA_TO_ASCII_LZ"]=" 1"
-D["HAVE_WCHAR_H"]=" 1"
-D["HAVE_WCTYPE_H"]=" 1"
-D["HAVE_ISWALNUM"]=" 1"
-D["HAVE_ISWALPHA"]=" 1"
-D["HAVE_ISWCNTRL"]=" 1"
-D["HAVE_ISWDIGIT"]=" 1"
-D["HAVE_ISWGRAPH"]=" 1"
-D["HAVE_ISWLOWER"]=" 1"
-D["HAVE_ISWPRINT"]=" 1"
-D["HAVE_ISWPUNCT"]=" 1"
-D["HAVE_ISWSPACE"]=" 1"
-D["HAVE_ISWUPPER"]=" 1"
-D["HAVE_ISWXDIGIT"]=" 1"
-D["HAVE_TOWUPPER"]=" 1"
-D["HAVE_TOWLOWER"]=" 1"
-D["HAVE_WC_FUNCS"]=" 1"
-D["HAVE_LANGINFO_CODESET"]=" 1"
-D["HAVE_LANGINFO_YESEXPR"]=" 1"
-D["MAKEDOC_FULL"]=" 1"
- for (key in D) D_is_set[key] = 1
- FS = "\a"
-}
-/^[\t ]*#[\t ]*(define|undef)[\t ]+[_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ][_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]*([\t (]|$)/ {
- line = $ 0
- split(line, arg, " ")
- if (arg[1] == "#") {
- defundef = arg[2]
- mac1 = arg[3]
- } else {
- defundef = substr(arg[1], 2)
- mac1 = arg[2]
- }
- split(mac1, mac2, "(") #)
- macro = mac2[1]
- prefix = substr(line, 1, index(line, defundef) - 1)
- if (D_is_set[macro]) {
- # Preserve the white space surrounding the "#".
- print prefix "define", macro P[macro] D[macro]
- next
- } else {
- # Replace #undef with comments. This is necessary, for example,
- # in the case of _POSIX_SOURCE, which is predefined and required
- # on some systems where configure will not decide to define it.
- if (defundef == "undef") {
- print "/*", prefix defundef, macro, "*/"
- next
- }
- }
-}
-{ print }
-_ACAWK
- { { $as_echo "$as_me:$LINENO: error: could not setup config headers machinery" >&5
-$as_echo "$as_me: error: could not setup config headers machinery" >&2;}
- { (exit 1); exit 1; }; }
-fi # test -n "$CONFIG_HEADERS"
-
-
-eval set X " :F $CONFIG_FILES :H $CONFIG_HEADERS :C $CONFIG_COMMANDS"
-shift
-for ac_tag
-do
- case $ac_tag in
- :[FHLC]) ac_mode=$ac_tag; continue;;
- esac
- case $ac_mode$ac_tag in
- :[FHL]*:*);;
- :L* | :C*:*) { { $as_echo "$as_me:$LINENO: error: invalid tag $ac_tag" >&5
-$as_echo "$as_me: error: invalid tag $ac_tag" >&2;}
- { (exit 1); exit 1; }; };;
- :[FH]-) ac_tag=-:-;;
- :[FH]*) ac_tag=$ac_tag:$ac_tag.in;;
- esac
- ac_save_IFS=$IFS
- IFS=:
- set x $ac_tag
- IFS=$ac_save_IFS
- shift
- ac_file=$1
- shift
-
- case $ac_mode in
- :L) ac_source=$1;;
- :[FH])
- ac_file_inputs=
- for ac_f
- do
- case $ac_f in
- -) ac_f="$tmp/stdin";;
- *) # Look for the file first in the build tree, then in the source tree
- # (if the path is not absolute). The absolute path cannot be DOS-style,
- # because $ac_f cannot contain `:'.
- test -f "$ac_f" ||
- case $ac_f in
- [\\/$]*) false;;
- *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";;
- esac ||
- { { $as_echo "$as_me:$LINENO: error: cannot find input file: $ac_f" >&5
-$as_echo "$as_me: error: cannot find input file: $ac_f" >&2;}
- { (exit 1); exit 1; }; };;
- esac
- case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac
- ac_file_inputs="$ac_file_inputs '$ac_f'"
- done
-
- # Let's still pretend it is `configure' which instantiates (i.e., don't
- # use $as_me), people would be surprised to read:
- # /* config.h. Generated by config.status. */
- configure_input='Generated from '`
- $as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g'
- `' by configure.'
- if test x"$ac_file" != x-; then
- configure_input="$ac_file. $configure_input"
- { $as_echo "$as_me:$LINENO: creating $ac_file" >&5
-$as_echo "$as_me: creating $ac_file" >&6;}
- fi
- # Neutralize special characters interpreted by sed in replacement strings.
- case $configure_input in #(
- *\&* | *\|* | *\\* )
- ac_sed_conf_input=`$as_echo "$configure_input" |
- sed 's/[\\\\&|]/\\\\&/g'`;; #(
- *) ac_sed_conf_input=$configure_input;;
- esac
-
- case $ac_tag in
- *:-:* | *:-) cat >"$tmp/stdin" \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; } ;;
- esac
- ;;
- esac
-
- ac_dir=`$as_dirname -- "$ac_file" ||
-$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$ac_file" : 'X\(//\)[^/]' \| \
- X"$ac_file" : 'X\(//\)$' \| \
- X"$ac_file" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$ac_file" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- { as_dir="$ac_dir"
- case $as_dir in #(
- -*) as_dir=./$as_dir;;
- esac
- test -d "$as_dir" || { $as_mkdir_p && mkdir -p "$as_dir"; } || {
- as_dirs=
- while :; do
- case $as_dir in #(
- *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
- *) as_qdir=$as_dir;;
- esac
- as_dirs="'$as_qdir' $as_dirs"
- as_dir=`$as_dirname -- "$as_dir" ||
-$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$as_dir" : 'X\(//\)[^/]' \| \
- X"$as_dir" : 'X\(//\)$' \| \
- X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$as_dir" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- test -d "$as_dir" && break
- done
- test -z "$as_dirs" || eval "mkdir $as_dirs"
- } || test -d "$as_dir" || { { $as_echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5
-$as_echo "$as_me: error: cannot create directory $as_dir" >&2;}
- { (exit 1); exit 1; }; }; }
- ac_builddir=.
-
-case "$ac_dir" in
-.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
-*)
- ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
- # A ".." for each directory in $ac_dir_suffix.
- ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
- case $ac_top_builddir_sub in
- "") ac_top_builddir_sub=. ac_top_build_prefix= ;;
- *) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
- esac ;;
-esac
-ac_abs_top_builddir=$ac_pwd
-ac_abs_builddir=$ac_pwd$ac_dir_suffix
-# for backward compatibility:
-ac_top_builddir=$ac_top_build_prefix
-
-case $srcdir in
- .) # We are building in place.
- ac_srcdir=.
- ac_top_srcdir=$ac_top_builddir_sub
- ac_abs_top_srcdir=$ac_pwd ;;
- [\\/]* | ?:[\\/]* ) # Absolute name.
- ac_srcdir=$srcdir$ac_dir_suffix;
- ac_top_srcdir=$srcdir
- ac_abs_top_srcdir=$srcdir ;;
- *) # Relative name.
- ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
- ac_top_srcdir=$ac_top_build_prefix$srcdir
- ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
-esac
-ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
-
-
- case $ac_mode in
- :F)
- #
- # CONFIG_FILE
- #
-
- case $INSTALL in
- [\\/$]* | ?:[\\/]* ) ac_INSTALL=$INSTALL ;;
- *) ac_INSTALL=$ac_top_build_prefix$INSTALL ;;
- esac
- ac_MKDIR_P=$MKDIR_P
- case $MKDIR_P in
- [\\/$]* | ?:[\\/]* ) ;;
- */*) ac_MKDIR_P=$ac_top_build_prefix$MKDIR_P ;;
- esac
-# If the template does not know about datarootdir, expand it.
-# FIXME: This hack should be removed a few years after 2.60.
-ac_datarootdir_hack=; ac_datarootdir_seen=
-
-ac_sed_dataroot='
-/datarootdir/ {
- p
- q
-}
-/@datadir@/p
-/@docdir@/p
-/@infodir@/p
-/@localedir@/p
-/@mandir@/p
-'
-case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in
-*datarootdir*) ac_datarootdir_seen=yes;;
-*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*)
- { $as_echo "$as_me:$LINENO: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5
-$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;}
- ac_datarootdir_hack='
- s&@datadir@&${datarootdir}&g
- s&@docdir@&/usr/share/doc&g
- s&@infodir@&${datarootdir}/info&g
- s&@localedir@&${datarootdir}/locale&g
- s&@mandir@&/usr/share/man&g
- s&\${datarootdir}&${prefix}/share&g' ;;
-esac
-ac_sed_extra="
-
-:t
-/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
-s|@configure_input@|$ac_sed_conf_input|;t t
-s&@top_builddir@&$ac_top_builddir_sub&;t t
-s&@top_build_prefix@&$ac_top_build_prefix&;t t
-s&@srcdir@&$ac_srcdir&;t t
-s&@abs_srcdir@&$ac_abs_srcdir&;t t
-s&@top_srcdir@&$ac_top_srcdir&;t t
-s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t
-s&@builddir@&$ac_builddir&;t t
-s&@abs_builddir@&$ac_abs_builddir&;t t
-s&@abs_top_builddir@&$ac_abs_top_builddir&;t t
-s&@INSTALL@&$ac_INSTALL&;t t
-s&@MKDIR_P@&$ac_MKDIR_P&;t t
-$ac_datarootdir_hack
-"
-eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$tmp/subs.awk" >$tmp/out \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; }
-
-test -z "$ac_datarootdir_hack$ac_datarootdir_seen" &&
- { ac_out=`sed -n '/\${datarootdir}/p' "$tmp/out"`; test -n "$ac_out"; } &&
- { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' "$tmp/out"`; test -z "$ac_out"; } &&
- { $as_echo "$as_me:$LINENO: WARNING: $ac_file contains a reference to the variable \`datarootdir'
-which seems to be undefined. Please make sure it is defined." >&5
-$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir'
-which seems to be undefined. Please make sure it is defined." >&2;}
-
- rm -f "$tmp/stdin"
- case $ac_file in
- -) cat "$tmp/out" && rm -f "$tmp/out";;
- *) rm -f "$ac_file" && mv "$tmp/out" "$ac_file";;
- esac \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; }
- ;;
- :H)
- #
- # CONFIG_HEADER
- #
- if test x"$ac_file" != x-; then
- {
- $as_echo "/* $configure_input */" \
- && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs"
- } >"$tmp/config.h" \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; }
- if diff "$ac_file" "$tmp/config.h" >/dev/null 2>&1; then
- { $as_echo "$as_me:$LINENO: $ac_file is unchanged" >&5
-$as_echo "$as_me: $ac_file is unchanged" >&6;}
- else
- rm -f "$ac_file"
- mv "$tmp/config.h" "$ac_file" \
- || { { $as_echo "$as_me:$LINENO: error: could not create $ac_file" >&5
-$as_echo "$as_me: error: could not create $ac_file" >&2;}
- { (exit 1); exit 1; }; }
- fi
- else
- $as_echo "/* $configure_input */" \
- && eval '$AWK -f "$tmp/defines.awk"' "$ac_file_inputs" \
- || { { $as_echo "$as_me:$LINENO: error: could not create -" >&5
-$as_echo "$as_me: error: could not create -" >&2;}
- { (exit 1); exit 1; }; }
- fi
-# Compute "$ac_file"'s index in $config_headers.
-_am_arg="$ac_file"
-_am_stamp_count=1
-for _am_header in $config_headers :; do
- case $_am_header in
- $_am_arg | $_am_arg:* )
- break ;;
- * )
- _am_stamp_count=`expr $_am_stamp_count + 1` ;;
- esac
-done
-echo "timestamp for $_am_arg" >`$as_dirname -- "$_am_arg" ||
-$as_expr X"$_am_arg" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$_am_arg" : 'X\(//\)[^/]' \| \
- X"$_am_arg" : 'X\(//\)$' \| \
- X"$_am_arg" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$_am_arg" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`/stamp-h$_am_stamp_count
- ;;
-
- :C) { $as_echo "$as_me:$LINENO: executing $ac_file commands" >&5
-$as_echo "$as_me: executing $ac_file commands" >&6;}
- ;;
- esac
-
-
- case $ac_file$ac_mode in
- "depfiles":C) test x"$AMDEP_TRUE" != x"" || for mf in $CONFIG_FILES; do
- # Strip MF so we end up with the name of the file.
- mf=`echo "$mf" | sed -e 's/:.*$//'`
- # Check whether this is an Automake generated Makefile or not.
- # We used to match only the files named `Makefile.in', but
- # some people rename them; so instead we look at the file content.
- # Grep'ing the first line is not enough: some people post-process
- # each Makefile.in and add a new line on top of each file to say so.
- # Grep'ing the whole file is not good either: AIX grep has a line
- # limit of 2048, but all sed's we know have understand at least 4000.
- if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then
- dirpart=`$as_dirname -- "$mf" ||
-$as_expr X"$mf" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$mf" : 'X\(//\)[^/]' \| \
- X"$mf" : 'X\(//\)$' \| \
- X"$mf" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$mf" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- else
- continue
- fi
- # Extract the definition of DEPDIR, am__include, and am__quote
- # from the Makefile without running `make'.
- DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"`
- test -z "$DEPDIR" && continue
- am__include=`sed -n 's/^am__include = //p' < "$mf"`
- test -z "am__include" && continue
- am__quote=`sed -n 's/^am__quote = //p' < "$mf"`
- # When using ansi2knr, U may be empty or an underscore; expand it
- U=`sed -n 's/^U = //p' < "$mf"`
- # Find all dependency output files, they are included files with
- # $(DEPDIR) in their names. We invoke sed twice because it is the
- # simplest approach to changing $(DEPDIR) to its actual value in the
- # expansion.
- for file in `sed -n "
- s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \
- sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do
- # Make sure the directory exists.
- test -f "$dirpart/$file" && continue
- fdir=`$as_dirname -- "$file" ||
-$as_expr X"$file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$file" : 'X\(//\)[^/]' \| \
- X"$file" : 'X\(//\)$' \| \
- X"$file" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$file" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- { as_dir=$dirpart/$fdir
- case $as_dir in #(
- -*) as_dir=./$as_dir;;
- esac
- test -d "$as_dir" || { $as_mkdir_p && mkdir -p "$as_dir"; } || {
- as_dirs=
- while :; do
- case $as_dir in #(
- *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
- *) as_qdir=$as_dir;;
- esac
- as_dirs="'$as_qdir' $as_dirs"
- as_dir=`$as_dirname -- "$as_dir" ||
-$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$as_dir" : 'X\(//\)[^/]' \| \
- X"$as_dir" : 'X\(//\)$' \| \
- X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
-$as_echo X"$as_dir" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
- s//\1/
- q
- }
- /^X\(\/\/\)[^/].*/{
- s//\1/
- q
- }
- /^X\(\/\/\)$/{
- s//\1/
- q
- }
- /^X\(\/\).*/{
- s//\1/
- q
- }
- s/.*/./; q'`
- test -d "$as_dir" && break
- done
- test -z "$as_dirs" || eval "mkdir $as_dirs"
- } || test -d "$as_dir" || { { $as_echo "$as_me:$LINENO: error: cannot create directory $as_dir" >&5
-$as_echo "$as_me: error: cannot create directory $as_dir" >&2;}
- { (exit 1); exit 1; }; }; }
- # echo "creating $dirpart/$file"
- echo '# dummy' > "$dirpart/$file"
- done
-done
- ;;
- "default-1":C) for ac_file in $CONFIG_FILES; do
- # Support "outfile[:infile[:infile...]]"
- case "$ac_file" in
- *:*) ac_file=`echo "$ac_file"|sed 's%:.*%%'` ;;
- esac
- # PO directories have a Makefile.in generated from Makefile.in.in.
- case "$ac_file" in */Makefile.in)
- # Adjust a relative srcdir.
- ac_dir=`echo "$ac_file"|sed 's%/[^/][^/]*$%%'`
- ac_dir_suffix="/`echo "$ac_dir"|sed 's%^\./%%'`"
- ac_dots=`echo "$ac_dir_suffix"|sed 's%/[^/]*%../%g'`
- # In autoconf-2.13 it is called $ac_given_srcdir.
- # In autoconf-2.50 it is called $srcdir.
- test -n "$ac_given_srcdir" || ac_given_srcdir="$srcdir"
- case "$ac_given_srcdir" in
- .) top_srcdir=`echo $ac_dots|sed 's%/$%%'` ;;
- /*) top_srcdir="$ac_given_srcdir" ;;
- *) top_srcdir="$ac_dots$ac_given_srcdir" ;;
- esac
- if test -f "$ac_given_srcdir/$ac_dir/POTFILES.in"; then
- rm -f "$ac_dir/POTFILES"
- test -n "$as_me" && echo "$as_me: creating $ac_dir/POTFILES" || echo "creating $ac_dir/POTFILES"
- sed -e "/^#/d" -e "/^[ ]*\$/d" -e "s,.*, $top_srcdir/& \\\\," -e "\$s/\(.*\) \\\\/\1/" < "$ac_given_srcdir/$ac_dir/POTFILES.in" > "$ac_dir/POTFILES"
- test -n "$as_me" && echo "$as_me: creating $ac_dir/Makefile" || echo "creating $ac_dir/Makefile"
- sed -e "/POTFILES =/r $ac_dir/POTFILES" "$ac_dir/Makefile.in" > "$ac_dir/Makefile"
- fi
- ;;
- esac
- done ;;
-
- esac
-done # for ac_tag
-
-
-{ (exit 0); exit 0; }
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# contrib/Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-
-# $Id$
-VPATH = ../../contrib
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES =
-SOURCES =
-DIST_SOURCES =
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DHAVE_CONFIG_H
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/contrib
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/../contrib
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ../../contrib
-sysconfdir = /etc
-target_alias =
-top_build_prefix = ../
-top_builddir = ..
-top_srcdir = ../..
-subdir = contrib
-SAMPLES = Mush.rc Pine.rc gpg.rc pgp2.rc pgp5.rc pgp6.rc Tin.rc \
- sample.muttrc sample.mailcap sample.muttrc-tlr \
- colors.default colors.linux smime.rc \
- ca-bundle.crt smime_keys_test.pl mutt_xtitle
-
-EXTRA_DIST = language.txt language50.txt \
- patch.slang-1.2.2.keypad.1 \
- $(SAMPLES) \
- iconv/README \
- iconv/make.sh
-
-distdir = ../$(PACKAGE)-$(VERSION)/$(subdir)
-all: all-am
-
-.SUFFIXES:
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu contrib/Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --gnu contrib/Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-tags: TAGS
-TAGS:
-
-ctags: CTAGS
-CTAGS:
-
-
-distdir: $(DISTFILES)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
- $(MAKE) $(AM_MAKEFLAGS) \
- top_distdir="$(top_distdir)" distdir="$(distdir)" \
- dist-hook
-check-am: all-am
-check: check-am
-all-am: Makefile
-installdirs:
-install: install-am
-install-exec: install-exec-am
-install-data: install-data-am
-uninstall: uninstall-am
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-am
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
-clean: clean-am
-
-clean-am: clean-generic mostlyclean-am
-
-distclean: distclean-am
- -rm -f Makefile
-distclean-am: clean-am distclean-generic
-
-dvi: dvi-am
-
-dvi-am:
-
-html: html-am
-
-info: info-am
-
-info-am:
-
-install-data-am: install-data-local
-
-install-dvi: install-dvi-am
-
-install-exec-am:
-
-install-html: install-html-am
-
-install-info: install-info-am
-
-install-man:
-
-install-pdf: install-pdf-am
-
-install-ps: install-ps-am
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-am
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-am
-
-mostlyclean-am: mostlyclean-generic
-
-pdf: pdf-am
-
-pdf-am:
-
-ps: ps-am
-
-ps-am:
-
-uninstall-am: uninstall-local
-
-.MAKE: install-am install-strip
-
-.PHONY: all all-am check check-am clean clean-generic dist-hook \
- distclean distclean-generic distdir dvi dvi-am html html-am \
- info info-am install install-am install-data install-data-am \
- install-data-local install-dvi install-dvi-am install-exec \
- install-exec-am install-html install-html-am install-info \
- install-info-am install-man install-pdf install-pdf-am \
- install-ps install-ps-am install-strip installcheck \
- installcheck-am installdirs maintainer-clean \
- maintainer-clean-generic mostlyclean mostlyclean-generic pdf \
- pdf-am ps ps-am uninstall uninstall-am uninstall-local
-
-
-install-data-local:
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(docdir)/samples $(DESTDIR)$(docdir)/samples/iconv
- for f in $(SAMPLES) ; do \
- $(INSTALL) -m 644 $(srcdir)/$$f $(DESTDIR)$(docdir)/samples ; \
- done
- for f in $(srcdir)/iconv/*.rc ; do \
- $(INSTALL) -m 644 $$f $(DESTDIR)$(docdir)/samples/iconv ; \
- done
-
-uninstall-local:
- for f in $(SAMPLES) ; do \
- rm -f $(DESTDIR)$(docdir)/samples/$$f ; \
- done
- -rm -rf $(DESTDIR)$(docdir)/samples/iconv
- -rmdir $(DESTDIR)$(docdir)/samples
- -rmdir $(DESTDIR)$(docdir)
-dist-hook: Makefile $(DISTFILES)
- mkdir -p $(distdir)/iconv
- for file in $(srcdir)/iconv/*.rc ; do \
- ln $$file $(distdir)/iconv 2> /dev/null \
- || cp -p $$file $(distdir)/iconv ; \
- done
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# doc/Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-
-VPATH = ../../doc
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-noinst_PROGRAMS = makedoc$(EXEEXT)
-DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in \
- $(srcdir)/instdoc.sh.in TODO
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES = instdoc.sh
-PROGRAMS = $(noinst_PROGRAMS)
-makedoc_SOURCES = makedoc.c
-makedoc_OBJECTS = makedoc.$(OBJEXT)
-makedoc_LDADD = $(LDADD)
-DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)
-depcomp = $(SHELL) $(top_srcdir)/depcomp
-am__depfiles_maybe = depfiles
-COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
- $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
-CCLD = $(CC)
-LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
-SOURCES = makedoc.c
-DIST_SOURCES = makedoc.c
-ETAGS = etags
-CTAGS = ctags
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DSYSCONFDIR=\"$(sysconfdir)\" -DBINDIR=\"$(bindir)\" -DHAVE_CONFIG_H=1
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/doc
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/../doc
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ../../doc
-sysconfdir = /etc
-target_alias =
-top_build_prefix = ../
-top_builddir = ..
-top_srcdir = ../..
-subdir = doc
-AM_CPPFLAGS = -I. -I.. -I$(includedir) -I$(top_srcdir)
-MAKEDOC_CPP = $(CPP) $(AM_CPPFLAGS) $(DEFS) $(CPPFLAGS) -D_MAKEDOC -C
-EXTRA_DIST = dotlock.man \
- smime_keys.man \
- muttbug.man \
- mutt.man \
- PGP-Notes.txt \
- applying-patches.txt \
- devel-notes.txt \
- gen-map-doc \
- muttrc.man.head \
- muttrc.man.tail \
- mbox.man \
- mmdf.man \
- manual.xml.head \
- manual.xml.tail \
- instdoc.sh.in \
- patch-notes.txt \
- smime-notes.txt \
- Muttrc Muttrc.head stamp-doc-rc \
- makedoc.c makedoc-defs.h \
- mutt.css mutt.xsl html.xsl chunk.xsl $(BUILT_DISTFILES)
-
-HTML_DOCFILES = manual.html index.html intro.html gettingstarted.html \
- configuration.html mimesupport.html advancedusage.html \
- optionalfeatures.html tuning.html reference.html miscellany.html
-
-BUILT_DISTFILES = stamp-doc-xml stamp-doc-chunked manual.txt $(HTML_DOCFILES)
-srcdir_DOCFILES = PGP-Notes.txt applying-patches.txt \
- devel-notes.txt patch-notes.txt smime-notes.txt
-
-topsrcdir_DOCFILES = COPYRIGHT GPL INSTALL ChangeLog \
- README NEWS TODO README.SECURITY README.SSL
-
-DISTCLEANFILES = manual.txt manual.html manual.xml manual.pdf html \
- instdoc Muttrc
-
-EDIT = sed -e 's,@sysconfdir\@,$(sysconfdir),g' \
- -e 's,@bindir\@,$(bindir),g' \
- -e 's,@docdir\@,$(docdir),g'
-
-all: all-am
-
-.SUFFIXES:
-.SUFFIXES: .c .o .obj
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu doc/Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --gnu doc/Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-instdoc.sh: $(top_builddir)/config.status $(srcdir)/instdoc.sh.in
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
-
-clean-noinstPROGRAMS:
- -test -z "$(noinst_PROGRAMS)" || rm -f $(noinst_PROGRAMS)
-makedoc$(EXEEXT): $(makedoc_OBJECTS) $(makedoc_DEPENDENCIES)
- @rm -f makedoc$(EXEEXT)
- $(LINK) $(makedoc_OBJECTS) $(makedoc_LDADD) $(LIBS)
-
-mostlyclean-compile:
- -rm -f *.$(OBJEXT)
-
-distclean-compile:
- -rm -f *.tab.c
-
-#include ./$(DEPDIR)/makedoc.Po
-
-.c.o:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c $<
-
-.c.obj:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'`
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c `$(CYGPATH_W) '$<'`
-
-ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- mkid -fID $$unique
-tags: TAGS
-
-TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- here=`pwd`; \
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
- test -n "$$unique" || unique=$$empty_fix; \
- $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
- $$tags $$unique; \
- fi
-ctags: CTAGS
-CTAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- test -z "$(CTAGS_ARGS)$$tags$$unique" \
- || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
- $$tags $$unique
-
-GTAGS:
- here=`$(am__cd) $(top_builddir) && pwd` \
- && cd $(top_srcdir) \
- && gtags -i $(GTAGS_ARGS) $$here
-
-distclean-tags:
- -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
-distdir: $(DISTFILES)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
-check-am: all-am
-check: check-am
-all-am: Makefile $(PROGRAMS)
-installdirs:
-install: install-am
-install-exec: install-exec-am
-install-data: install-data-am
-uninstall: uninstall-am
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-am
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
- -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
-clean: clean-am
-
-clean-am: clean-generic clean-local clean-noinstPROGRAMS \
- mostlyclean-am
-
-distclean: distclean-am
- -rm -rf ./$(DEPDIR)
- -rm -f Makefile
-distclean-am: clean-am distclean-compile distclean-generic \
- distclean-tags
-
-dvi: dvi-am
-
-dvi-am:
-
-html: html-am
-
-info: info-am
-
-info-am:
-
-install-data-am: install-data-local
-
-install-dvi: install-dvi-am
-
-install-exec-am:
-
-install-html: install-html-am
-
-install-info: install-info-am
-
-install-man:
-
-install-pdf: install-pdf-am
-
-install-ps: install-ps-am
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-am
- -rm -rf ./$(DEPDIR)
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-am
-
-mostlyclean-am: mostlyclean-compile mostlyclean-generic
-
-pdf: pdf-am
-
-pdf-am:
-
-ps: ps-am
-
-ps-am:
-
-uninstall-am: uninstall-local
-
-.MAKE: install-am install-strip
-
-.PHONY: CTAGS GTAGS all all-am check check-am clean clean-generic \
- clean-local clean-noinstPROGRAMS ctags distclean \
- distclean-compile distclean-generic distclean-tags distdir dvi \
- dvi-am html html-am info info-am install install-am \
- install-data install-data-am install-data-local install-dvi \
- install-dvi-am install-exec install-exec-am install-html \
- install-html-am install-info install-info-am install-man \
- install-pdf install-pdf-am install-ps install-ps-am \
- install-strip installcheck installcheck-am installdirs \
- maintainer-clean maintainer-clean-generic mostlyclean \
- mostlyclean-compile mostlyclean-generic pdf pdf-am ps ps-am \
- tags uninstall uninstall-am uninstall-local
-
-
-all: makedoc-all
-
-makedoc-all: mutt.1 smime_keys.1 muttrc.man manual.html stamp-doc-rc stamp-doc-chunked manual.txt
-
-install-data-local: makedoc-all instdoc
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(mandir)/man1
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(mandir)/man5
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(sysconfdir)
- ./instdoc mutt.1 $(DESTDIR)$(mandir)/man1/mutt.1
- ./instdoc smime_keys.1 $(DESTDIR)$(mandir)/man1/smime_keys.1
- ./instdoc $(srcdir)/muttbug.man $(DESTDIR)$(mandir)/man1/flea.1
- ./instdoc $(srcdir)/muttbug.man $(DESTDIR)$(mandir)/man1/muttbug.1
- test xmutt_dotlock$(EXEEXT) = x || ./instdoc $(srcdir)/dotlock.man \
- $(DESTDIR)$(mandir)/man1/mutt_dotlock.1
- ./instdoc muttrc.man $(DESTDIR)$(mandir)/man5/muttrc.5
- ./instdoc $(srcdir)/mbox.man $(DESTDIR)$(mandir)/man5/mbox.5
- ./instdoc $(srcdir)/mmdf.man $(DESTDIR)$(mandir)/man5/mmdf.5
- $(top_srcdir)/mkinstalldirs $(DESTDIR)$(docdir)
- for f in $(topsrcdir_DOCFILES) ; do \
- $(INSTALL) -m 644 $(top_srcdir)/$$f $(DESTDIR)$(docdir) ; \
- done
- for f in $(srcdir_DOCFILES) ; do \
- $(INSTALL) -m 644 $(srcdir)/$$f $(DESTDIR)$(docdir) ; \
- done
- -$(INSTALL) -m 644 manual.txt $(DESTDIR)$(docdir)
- -for f in $(HTML_DOCFILES) ; do \
- $(INSTALL) -m 644 $$f $(DESTDIR)$(docdir) ; \
- done
- $(INSTALL) -m 644 Muttrc $(DESTDIR)$(sysconfdir)/Muttrc.dist
- -if [ -f $(DESTDIR)$(pkgdatadir)/Muttrc ] ; then \
- mv $(DESTDIR)$(pkgdatadir)/Muttrc* $(DESTDIR)$(sysconfdir) ; \
- elif [ -f $(DESTDIR)$(pkgdatadir)/../Muttrc ] ; then \
- mv $(DESTDIR)$(pkgdatadir)/../Muttrc* $(DESTDIR)$(sysconfdir) ; \
- elif [ ! -f $(DESTDIR)$(sysconfdir)/Muttrc ] ; then \
- $(INSTALL) -m 644 Muttrc $(DESTDIR)$(sysconfdir) ; \
- fi
-
-uninstall-local:
- for f in mutt.1 mutt_dotlock.1 flea.1 muttbug.1 smime_keys.1; do \
- rm -f $(DESTDIR)$(mandir)/man1/$$f ; \
- done
- for f in muttrc.5 mbox.5 mmdf.5 ; do \
- rm -f $(DESTDIR)$(mandir)/man5/$$f ; \
- done
- for f in $(srcdir_DOCFILES) $(topsrcdir_DOCFILES) $(HTML_DOCFILES) ; \
- do \
- rm -f $(DESTDIR)$(docdir)/$$f ; \
- done
- -rm -f $(DESTDIR)$(docdir)/manual.txt
- for i in Muttrc ; do \
- if cmp -s $(DESTDIR)$(sysconfdir)/$$i.dist $(DESTDIR)$(sysconfdir)/$$i ; then \
- rm $(DESTDIR)$(sysconfdir)/$$i ; \
- fi ; \
- rm $(DESTDIR)$(sysconfdir)/$${i}.dist ; \
- done
-
-check:
-manual.txt: manual.html
- links.main -dump $< > $@ || links -dump $< > $@ || \
- LC_ALL=C lynx -dump -nolist -with_backspaces manual.html > $@ || \
- LC_ALL=C w3m -dump manual.html > $@ || \
- LC_ALL=C elinks -dump -no-numbering -no-references manual.html | sed -e 's,\\001, ,g' > $@
-
-Muttrc: stamp-doc-rc
-
-stamp-doc-rc: $(top_srcdir)/init.h makedoc$(EXEEXT) $(srcdir)/Muttrc.head
- -rm -f Muttrc stamp-doc-rc
- sed -e 's,[@]docdir[@],$(docdir),' $(srcdir)/Muttrc.head > Muttrc
- $(CPP) $(AM_CPPFLAGS) $(DEFS) $(CPPFLAGS) -D_MAKEDOC -C \
- $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -c >> Muttrc
- touch stamp-doc-rc
-
-manual.html: $(srcdir)/html.xsl $(srcdir)/mutt.xsl stamp-doc-xml $(srcdir)/mutt.css
- xsltproc --nonet -o $@ $(srcdir)/html.xsl manual.xml
-
-stamp-doc-chunked: $(srcdir)/chunk.xsl $(srcdir)/mutt.xsl stamp-doc-xml $(srcdir)/mutt.css
- xsltproc --nonet $(srcdir)/chunk.xsl manual.xml
- touch stamp-doc-chunked
-
-$(HTML_DOCFILES): stamp-doc-chunked
-
-manual.pdf: manual.tex
- -if test -f manual.tex; then pdfjadetex manual.tex; fi
-
-manual.tex: stamp-doc-xml
- -if test -n "$(DSLROOT)"; then \
- openjade -t tex -D $(DSLROOT) -d print/docbook.dsl dtds/decls/xml.dcl manual.xml; \
- fi
-
-validate: stamp-doc-xml
- xmllint --noout --noblanks --postvalid manual.xml
-
-spellcheck:
- -aspell -l en --mode sgml -c manual.xml.head && \
- -aspell -l en --mode nroff -c muttrc.man.head
-
-clean-local:
- rm -f *~ *.html *.orig *.rej stamp-doc-* *.ps mutt.1 smime_keys.1 muttrc.man
- rm -f *.aux *.log *.tex *.out
-
-instdoc: instdoc.sh
- cat instdoc.sh > instdoc
- chmod a+x instdoc
-
-update-doc: stamp-doc-xml stamp-doc-chunked stamp-doc-rc manual.txt manual.html
-
-muttrc.man: makedoc$(EXEEXT) $(top_srcdir)/init.h muttrc.man.head muttrc.man.tail
- $(MAKEDOC_CPP) $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -m | \
- cat $(srcdir)/muttrc.man.head - $(srcdir)/muttrc.man.tail\
- > muttrc.man
-
-mutt.1: $(srcdir)/mutt.man
- $(EDIT) $(srcdir)/mutt.man > $@
-
-smime_keys.1: $(srcdir)/smime_keys.man
- $(EDIT) $(srcdir)/smime_keys.man > $@
-
-stamp-doc-xml: makedoc$(EXEEXT) $(top_srcdir)/init.h \
- manual.xml.head $(top_srcdir)/functions.h $(top_srcdir)/OPS* manual.xml.tail \
- $(srcdir)/gen-map-doc $(top_srcdir)/VERSION $(top_srcdir)/ChangeLog
- ( date=`head -n 1 $(top_srcdir)/ChangeLog | LC_ALL=C cut -d ' ' -f 1` && \
- sed -e "s/@VERSION\@/`cat $(top_srcdir)/VERSION` ($$date)/" $(srcdir)/manual.xml.head && \
- $(MAKEDOC_CPP) $(top_srcdir)/init.h | ./makedoc$(EXEEXT) -s && \
- $(MAKEDOC_CPP) $(top_srcdir)/functions.h | \
- perl $(srcdir)/gen-map-doc $(srcdir)/manual.xml.tail $(top_srcdir)/OPS* \
- ) > manual.xml
- touch stamp-doc-xml
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-#
-# System configuration file for Mutt
-#
-
-# Default list of header fields to weed when displaying.
-# Ignore all lines by default...
-ignore *
-
-# ... then allow these through.
-unignore from: subject to cc date x-mailer x-url user-agent
-
-# Display the fields in this order
-hdr_order date from to cc subject
-
-# emacs-like bindings
-bind editor "\e<delete>" kill-word
-bind editor "\e<backspace>" kill-word
-
-# map delete-char to a sane value
-bind editor <delete> delete-char
-
-# some people actually like these settings
-#set pager_stop
-#bind pager <up> previous-line
-#bind pager <down> next-line
-
-# Specifies how to sort messages in the index menu.
-set sort=threads
-
-# Uncomment if your MTA does not strip Bcc: headers.
-# (exim4 and postfix strip them, exim(3) does not.)
-#unset write_bcc
-# Postfix and qmail use Delivered-To for detecting loops
-unset bounce_delivered
-
-set mixmaster="mixmaster-filter"
-
-# System-wide CA file managed by the ca-certificates package
-set ssl_ca_certificates_file="/etc/ssl/certs/ca-certificates.crt"
-
-# imitate the old search-body function
-macro index \eb "<search>~b " "search in message bodies"
-
-# simulate the old url menu
-macro index,pager,attach,compose \cb "\
-<enter-command> set my_pipe_decode=\$pipe_decode pipe_decode<Enter>\
-<pipe-message> urlview<Enter>\
-<enter-command> set pipe_decode=\$my_pipe_decode; unset my_pipe_decode<Enter>" \
-"call urlview to extract URLs out of a message"
-
-# Show documentation when pressing F1
-macro generic,pager <F1> "<shell-escape> zcat /usr/share/doc/mutt/manual.txt.gz | sensible-pager<enter>" "show Mutt documentation"
-
-# show the incoming mailboxes list (just like "mutt -y") and back when pressing "y"
-macro index,pager y "<change-folder>?<toggle-mailboxes>" "show incoming mailboxes list"
-bind browser y exit
-
-# Use folders which match on \\.gz$ as gzipped folders:
-# open-hook \\.gz$ "gzip -cd %f > %t"
-# close-hook \\.gz$ "gzip -c %t > %f"
-# append-hook \\.gz$ "gzip -c %t >> %f"
-
-# If Mutt is unable to determine your site's domain name correctly, you can
-# set the default here. (better: fix /etc/mailname)
-#
-# set hostname=cs.hmc.edu
-
-# If your sendmail supports the -B8BITMIME flag, enable the following
-#
-# set use_8bitmime
-
-# Use mime.types to look up handlers for application/octet-stream. Can
-# be undone with unmime_lookup.
-mime_lookup application/octet-stream
-
-##
-## *** DEFAULT SETTINGS FOR THE ATTACHMENTS PATCH ***
-##
-
-##
-## Please see the manual (section "attachments") for detailed
-## documentation of the "attachments" command.
-##
-## 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
-
-# enable mime lookup by extension
-mime_lookup application/octet-stream
-
-##
-## More settings
-##
-
-
-# set abort_nosubject=ask-yes
-#
-# Name: abort_nosubject
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# If set to yes, when composing messages and no subject is given
-# at the subject prompt, composition will be aborted. If set to
-# no, composing messages with no subject given at the subject
-# prompt will never be aborted.
-#
-#
-# set abort_unmodified=yes
-#
-# Name: abort_unmodified
-# Type: quadoption
-# Default: yes
-#
-#
-# If set to yes, composition will automatically abort after
-# editing the message body if no changes are made to the file (this
-# check only happens after the first edit of the file). When set
-# to no, composition will never be aborted.
-#
-#
-# set alias_file="~/.muttrc"
-#
-# Name: alias_file
-# Type: path
-# Default: "~/.muttrc"
-#
-#
-# The default file in which to save aliases created by the
-# <create-alias> function. Entries added to this file are
-# encoded in the character set specified by $config_charset if it
-# is set or the current character set otherwise.
-#
-# Note: Mutt will not automatically source this file; you must
-# explicitly use the ``source'' command for it to be executed in case
-# this option points to a dedicated alias file.
-#
-# The default for this option is the currently used muttrc file, or
-# ``~/.muttrc'' if no user muttrc was found.
-#
-#
-# set alias_format="%4n %2f %t %-10a %r"
-#
-# Name: alias_format
-# Type: string
-# Default: "%4n %2f %t %-10a %r"
-#
-#
-# Specifies the format of the data displayed for the ``alias'' menu. The
-# following printf(3)-style sequences are available:
-# %a alias name
-# %f flags - currently, a ``d'' for an alias marked for deletion
-# %n index number
-# %r address which alias expands to
-# %t character which indicates if the alias is tagged for inclusion
-#
-#
-# set allow_8bit=yes
-#
-# Name: allow_8bit
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether 8-bit data is converted to 7-bit using either Quoted-
-# Printable or Base64 encoding when sending mail.
-#
-#
-# set allow_ansi=no
-#
-# Name: allow_ansi
-# Type: boolean
-# Default: no
-#
-#
-# Controls whether ANSI color codes in messages (and color tags in
-# rich text messages) are to be interpreted.
-# Messages containing these codes are rare, but if this option is set,
-# their text will be colored accordingly. Note that this may override
-# your color choices, and even present a security problem, since a
-# message could include a line like
-# [-- PGP output follows ...
-#
-# and give it the same color as your attachment color (see also
-# $crypt_timestamp).
-#
-#
-# set arrow_cursor=no
-#
-# Name: arrow_cursor
-# Type: boolean
-# Default: no
-#
-#
-# When set, an arrow (``->'') will be used to indicate the current entry
-# in menus instead of highlighting the whole line. On slow network or modem
-# links this will make response faster because there is less that has to
-# be redrawn on the screen when moving to the next or previous entries
-# in the menu.
-#
-#
-# set ascii_chars=no
-#
-# Name: ascii_chars
-# Type: boolean
-# Default: no
-#
-#
-# If set, Mutt will use plain ASCII characters when displaying thread
-# and attachment trees, instead of the default ACS characters.
-#
-#
-# set askbcc=no
-#
-# Name: askbcc
-# Type: boolean
-# Default: no
-#
-#
-# If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
-# before editing an outgoing message.
-#
-#
-# set askcc=no
-#
-# Name: askcc
-# Type: boolean
-# Default: no
-#
-#
-# If set, Mutt will prompt you for carbon-copy (Cc) recipients before
-# editing the body of an outgoing message.
-#
-#
-# set assumed_charset=""
-#
-# Name: assumed_charset
-# Type: string
-# Default: ""
-#
-#
-# This variable is a colon-separated list of character encoding
-# schemes for messages without character encoding indication.
-# Header field values and message body content without character encoding
-# indication would be assumed that they are written in one of this list.
-# By default, all the header fields and message body without any charset
-# indication are assumed to be in ``us-ascii''.
-#
-# For example, Japanese users might prefer this:
-# set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-#
-# However, only the first content is valid for the message body.
-#
-#
-# set attach_charset=""
-#
-# Name: attach_charset
-# Type: string
-# Default: ""
-#
-#
-# This variable is a colon-separated list of character encoding
-# schemes for text file attachments. Mutt uses this setting to guess
-# which encoding files being attached are encoded in to convert them to
-# a proper character set given in $send_charset.
-#
-# If unset, the value of $charset will be used instead.
-# For example, the following configuration would work for Japanese
-# text handling:
-# set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-#
-# Note: for Japanese users, ``iso-2022-*'' must be put at the head
-# of the value as shown above if included.
-#
-#
-# set attach_format="%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
-#
-# Name: attach_format
-# Type: string
-# Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
-#
-#
-# This variable describes the format of the ``attachment'' menu. The
-# following printf(3)-style sequences are understood:
-# %C charset
-# %c requires charset conversion (``n'' or ``c'')
-# %D deleted flag
-# %d description
-# %e MIME content-transfer-encoding
-# %f filename
-# %I disposition (``I'' for inline, ``A'' for attachment)
-# %m major MIME type
-# %M MIME subtype
-# %n attachment number
-# %Q ``Q'', if MIME part qualifies for attachment counting
-# %s size
-# %t tagged flag
-# %T graphic tree characters
-# %u unlink (=to delete) flag
-# %X number of qualifying MIME parts in this part and its children
-# (please see the ``attachments'' section for possible speed effects)
-# %>X right justify the rest of the string and pad with character ``X''
-# %|X pad to the end of the line with character ``X''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# For an explanation of ``soft-fill'', see the $index_format documentation.
-#
-#
-# set attach_sep="\n"
-#
-# Name: attach_sep
-# Type: string
-# Default: "\n"
-#
-#
-# The separator to add between attachments when operating (saving,
-# printing, piping, etc) on a list of tagged attachments.
-#
-#
-# set attach_split=yes
-#
-# Name: attach_split
-# Type: boolean
-# Default: yes
-#
-#
-# If this variable is unset, when operating (saving, printing, piping,
-# etc) on a list of tagged attachments, Mutt 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 will operate on the attachments one by one.
-#
-#
-# set attribution="On %d, %n wrote:"
-#
-# Name: attribution
-# Type: string
-# Default: "On %d, %n wrote:"
-#
-#
-# This is the string that will precede a message which has been included
-# in a reply. For a full listing of defined printf(3)-like sequences see
-# the section on $index_format.
-#
-#
-# set autoedit=no
-#
-# Name: autoedit
-# Type: boolean
-# Default: no
-#
-#
-# When set along with $edit_headers, Mutt will skip the initial
-# send-menu (prompting for subject and recipients) and allow you to
-# immediately begin editing the body of your
-# message. The send-menu may still be accessed once you have finished
-# editing the body of your message.
-#
-# Also see $fast_reply.
-#
-#
-# set auto_tag=no
-#
-# Name: auto_tag
-# Type: boolean
-# Default: no
-#
-#
-# When set, functions in the index menu which affect a message
-# will be applied to all tagged messages (if there are any). When
-# unset, you must first use the <tag-prefix> function (bound to ``;''
-# by default) to make the next function apply to all tagged messages.
-#
-#
-# set beep=yes
-#
-# Name: beep
-# Type: boolean
-# Default: yes
-#
-#
-# When this variable is set, mutt will beep when an error occurs.
-#
-#
-# set beep_new=no
-#
-# Name: beep_new
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, mutt will beep whenever it prints a message
-# notifying you of new mail. This is independent of the setting of the
-# $beep variable.
-#
-#
-# set bounce=ask-yes
-#
-# Name: bounce
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# Controls whether you will be asked to confirm bouncing messages.
-# If set to yes you don't get asked if you want to bounce a
-# message. Setting this variable to no is not generally useful,
-# and thus not recommended, because you are unable to bounce messages.
-#
-#
-# set bounce_delivered=yes
-#
-# Name: bounce_delivered
-# Type: boolean
-# Default: yes
-#
-#
-# When this variable is set, mutt will include Delivered-To headers when
-# bouncing messages. Postfix users may wish to unset this variable.
-#
-# Note: On Debian systems, this option is unset by default in
-# /etc/Muttrc.
-#
-#
-# set braille_friendly=no
-#
-# Name: braille_friendly
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, mutt will place the cursor at the beginning
-# of the current line in menus, even when the $arrow_cursor variable
-# is unset, making it easier for blind persons using Braille displays to
-# follow these menus. The option is unset by default because many
-# visual terminals don't permit making the cursor invisible.
-#
-#
-# set check_mbox_size=no
-#
-# Name: check_mbox_size
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, mutt will use file size attribute instead of
-# access time when checking for new mail in mbox and mmdf folders.
-#
-# This variable is unset by default and should only be enabled when
-# new mail detection for these folder types is unreliable or doesn't work.
-#
-# Note that enabling this variable should happen before any ``mailboxes''
-# directives occur in configuration files regarding mbox or mmdf folders
-# because mutt needs to determine the initial new mail status of such a
-# mailbox by performing a fast mailbox scan when it is defined.
-# Afterwards the new mail status is tracked by file size changes.
-#
-#
-# set charset=""
-#
-# Name: charset
-# Type: string
-# Default: ""
-#
-#
-# Character set your terminal uses to display and enter textual data.
-# It is also the fallback for $send_charset.
-#
-# Upon startup Mutt tries to derive this value from environment variables
-# such as $LC_CTYPE or $LANG.
-#
-# Note: It should only be set in case Mutt isn't abled to determine the
-# character set used correctly.
-#
-#
-# set check_new=yes
-#
-# Name: check_new
-# Type: boolean
-# Default: yes
-#
-#
-# Note: this option only affects maildir and MH style
-# mailboxes.
-#
-# When set, Mutt 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
-# this variable is unset, no check for new mail is performed
-# while the mailbox is open.
-#
-#
-# set collapse_unread=yes
-#
-# Name: collapse_unread
-# Type: boolean
-# Default: yes
-#
-#
-# When unset, Mutt will not collapse a thread if it contains any
-# unread messages.
-#
-#
-# set uncollapse_jump=no
-#
-# Name: uncollapse_jump
-# Type: boolean
-# Default: no
-#
-#
-# When set, Mutt will jump to the next unread message, if any,
-# when the current thread is uncollapsed.
-#
-#
-# set compose_format="-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-"
-#
-# Name: compose_format
-# Type: string
-# Default: "-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-"
-#
-#
-# Controls the format of the status line displayed in the ``compose''
-# menu. This string is similar to $status_format, but has its own
-# set of printf(3)-like sequences:
-# %a total number of attachments
-# %h local hostname
-# %l approximate size (in bytes) of the current message
-# %v Mutt version string
-#
-#
-# See the text describing the $status_format option for more
-# information on how to set $compose_format.
-#
-#
-# set config_charset=""
-#
-# Name: config_charset
-# Type: string
-# Default: ""
-#
-#
-# When defined, Mutt will recode commands in rc files from this
-# encoding to the current character set as specified by $charset
-# and aliases written to $alias_file from the current character set.
-#
-# Please note that if setting $charset it must be done before
-# setting $config_charset.
-#
-# Recoding should be avoided as it may render unconvertable
-# characters as question marks which can lead to undesired
-# side effects (for example in regular expressions).
-#
-#
-# set confirmappend=yes
-#
-# Name: confirmappend
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will prompt for confirmation when appending messages to
-# an existing mailbox.
-#
-#
-# set confirmcreate=yes
-#
-# Name: confirmcreate
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will prompt for confirmation when saving messages to a
-# mailbox which does not yet exist before creating it.
-#
-#
-# set connect_timeout=30
-#
-# Name: connect_timeout
-# Type: number
-# Default: 30
-#
-#
-# Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-# many seconds if the connection is not able to be established. A negative
-# value causes Mutt to wait indefinitely for the connection attempt to succeed.
-#
-#
-# set content_type="text/plain"
-#
-# Name: content_type
-# Type: string
-# Default: "text/plain"
-#
-#
-# Sets the default Content-Type for the body of newly composed messages.
-#
-#
-# set copy=yes
-#
-# Name: copy
-# Type: quadoption
-# Default: yes
-#
-#
-# 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''.
-#
-#
-# set crypt_use_gpgme=no
-#
-# Name: crypt_use_gpgme
-# Type: boolean
-# Default: no
-#
-#
-# This variable controls the use of the GPGME-enabled crypto backends.
-# If it is set and Mutt was built with gpgme support, the gpgme code for
-# S/MIME and PGP will be used instead of the classic code. Note that
-# you need to set this option in .muttrc; it won't have any effect when
-# used interactively.
-#
-#
-# set crypt_use_pka=no
-#
-# Name: crypt_use_pka
-# Type: boolean
-# Default: no
-#
-#
-# Controls whether mutt uses PKA
-# (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
-# verification (only supported by the GPGME backend).
-#
-#
-# set crypt_autopgp=yes
-#
-# Name: crypt_autopgp
-# Type: boolean
-# Default: yes
-#
-#
-# This variable controls whether or not mutt may automatically enable
-# PGP encryption/signing for messages. See also $crypt_autoencrypt,
-# $crypt_replyencrypt,
-# $crypt_autosign, $crypt_replysign and $smime_is_default.
-#
-#
-# set crypt_autosmime=yes
-#
-# Name: crypt_autosmime
-# Type: boolean
-# Default: yes
-#
-#
-# This variable controls whether or not mutt may automatically enable
-# S/MIME encryption/signing for messages. See also $crypt_autoencrypt,
-# $crypt_replyencrypt,
-# $crypt_autosign, $crypt_replysign and $smime_is_default.
-#
-#
-# set date_format="!%a, %b %d, %Y at %I:%M:%S%p %Z"
-#
-# Name: date_format
-# Type: string
-# Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
-#
-#
-# This variable controls the format of the date printed by the ``%d''
-# sequence in $index_format. This is passed to the strftime(3)
-# function to process the date, see the man page for the proper syntax.
-#
-# 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).
-#
-#
-# set default_hook="~f %s !~P | (~P ~C %s)"
-#
-# Name: default_hook
-# Type: string
-# Default: "~f %s !~P | (~P ~C %s)"
-#
-#
-# This variable controls how ``message-hook'', ``reply-hook'', ``send-hook'',
-# ``send2-hook'', ``save-hook'', and ``fcc-hook'' 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.
-#
-#
-# set delete=ask-yes
-#
-# Name: delete
-# 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.
-#
-#
-# set delete_untag=yes
-#
-# Name: delete_untag
-# Type: boolean
-# Default: yes
-#
-#
-# If this option is set, mutt 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.
-#
-#
-# set digest_collapse=yes
-#
-# Name: digest_collapse
-# Type: boolean
-# Default: yes
-#
-#
-# If this option is set, mutt'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.
-#
-#
-# set display_filter=""
-#
-# Name: display_filter
-# Type: path
-# 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.
-#
-#
-# set dotlock_program="/usr/bin/mutt_dotlock"
-#
-# Name: dotlock_program
-# Type: path
-# Default: "/usr/bin/mutt_dotlock"
-#
-#
-# Contains the path of the mutt_dotlock(8) binary to be used by
-# mutt.
-#
-#
-# set dsn_notify=""
-#
-# Name: dsn_notify
-# Type: string
-# Default: ""
-#
-#
-# 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.
-#
-# Example:
-# set dsn_notify="failure,delay"
-#
-# Note: when using $sendmail for delivery, you should not enable
-# this unless you are either using Sendmail 8.8.x or greater or a MTA
-# providing a sendmail(1)-compatible interface supporting the -N option
-# for DSN. For SMTP delivery, DSN support is autodetected so that it
-# depends on the server whether DSN will be used or not.
-#
-#
-# set dsn_return=""
-#
-# Name: dsn_return
-# Type: string
-# Default: ""
-#
-#
-# 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.
-#
-# Example:
-# set dsn_return=hdrs
-#
-# Note: when using $sendmail for delivery, you should not enable
-# this unless you are either using Sendmail 8.8.x or greater or a MTA
-# providing a sendmail(1)-compatible interface supporting the -R option
-# for DSN. For SMTP delivery, DSN support is autodetected so that it
-# depends on the server whether DSN will be used or not.
-#
-#
-# set duplicate_threads=yes
-#
-# Name: duplicate_threads
-# Type: boolean
-# Default: yes
-#
-#
-# This variable controls whether mutt, when $sort is set to threads, threads
-# messages with the same Message-Id together. If it is set, it will indicate
-# that it thinks they are duplicates of each other with an equals sign
-# in the thread tree.
-#
-#
-# set edit_headers=no
-#
-# Name: edit_headers
-# Type: boolean
-# Default: no
-#
-#
-# This option allows you to edit the header of your outgoing messages
-# along with the body of your message.
-#
-# Note that changes made to the References: and Date: headers are
-# ignored for interoperability reasons.
-#
-#
-# set editor=""
-#
-# Name: editor
-# Type: path
-# Default: ""
-#
-#
-# This variable specifies which editor is used by mutt.
-# It defaults to the value of the $VISUAL, or $EDITOR, environment
-# variable, or to the string ``/usr/bin/editor'' if neither of those are set.
-#
-#
-# set encode_from=no
-#
-# Name: encode_from
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will quoted-printable encode messages when
-# they contain the string ``From '' (note the trailing space) in the beginning of a line.
-# This is useful to avoid the tampering certain mail delivery and transport
-# agents tend to do with messages (in order to prevent tools from
-# misinterpreting the line as a mbox message separator).
-#
-#
-# set envelope_from_address=""
-#
-# Name: envelope_from_address
-# Type: e-mail address
-# Default: ""
-#
-#
-# Manually sets the envelope sender for outgoing messages.
-# This value is ignored if $use_envelope_from is unset.
-#
-#
-# set escape="~"
-#
-# Name: escape
-# Type: string
-# Default: "~"
-#
-#
-# Escape character to use for functions in the builtin editor.
-#
-#
-# set fast_reply=no
-#
-# Name: fast_reply
-# Type: boolean
-# Default: no
-#
-#
-# 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.
-#
-# Note: this variable has no effect when the $autoedit
-# variable is set.
-#
-#
-# set fcc_attach=yes
-#
-# Name: fcc_attach
-# Type: boolean
-# Default: yes
-#
-#
-# This variable controls whether or not attachments on outgoing messages
-# are saved along with the main body of your message.
-#
-#
-# set fcc_clear=no
-#
-# Name: fcc_clear
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, FCCs will be stored unencrypted and
-# unsigned, even when the actual message is encrypted and/or
-# signed.
-# (PGP only)
-#
-#
-# set folder="~/Mail"
-#
-# Name: folder
-# Type: path
-# Default: "~/Mail"
-#
-#
-# 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
-# when handling the ``mailboxes'' command.
-#
-#
-# set folder_format="%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
-#
-# Name: folder_format
-# Type: string
-# Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
-#
-#
-# 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:
-# %C current file number
-# %d date/time folder was last modified
-# %f filename
-# %F file permissions
-# %g group name (or numeric gid, if missing)
-# %l number of hard links
-# %N N if folder has new mail, blank otherwise
-# %s size in bytes
-# %t ``*'' 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''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# For an explanation of ``soft-fill'', see the $index_format documentation.
-#
-#
-# set followup_to=yes
-#
-# Name: followup_to
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether or not the ``Mail-Followup-To:'' header field is
-# generated when sending mail. When set, Mutt will generate this
-# field when you are replying to a known mailing list, specified with
-# the ``subscribe'' or ``lists'' commands.
-#
-# This field has two purposes. First, preventing you from
-# receiving duplicate copies of replies to messages which you send
-# to mailing lists, and 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.
-#
-#
-# set force_name=no
-#
-# Name: force_name
-# Type: boolean
-# Default: no
-#
-#
-# This variable is similar to $save_name, except that Mutt 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.
-#
-#
-# set forward_decode=yes
-#
-# Name: forward_decode
-# Type: boolean
-# Default: yes
-#
-#
-# 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.
-#
-#
-# set forward_edit=yes
-#
-# Name: 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''.
-#
-#
-# set forward_format="[%a: %s]"
-#
-# Name: forward_format
-# 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.
-#
-#
-# set forward_quote=no
-#
-# Name: 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.
-#
-#
-# set from=""
-#
-# Name: from
-# Type: e-mail address
-# Default: ""
-#
-#
-# When set, this variable contains a default from address. It
-# can be overridden using ``my_hdr'' (including from a ``send-hook'') and
-# $reverse_name. This variable is ignored if $use_from is unset.
-#
-# This setting defaults to the contents of the environment variable $EMAIL.
-#
-#
-# set gecos_mask="^[^,]*"
-#
-# Name: gecos_mask
-# Type: regular expression
-# Default: "^[^,]*"
-#
-#
-# A regular expression used by mutt to parse the GECOS field of a password
-# entry when expanding the alias. The default value
-# will return the string up to the first ``,'' encountered.
-# If the GECOS field contains a string like ``lastname, firstname'' then you
-# should set it to ``.*''.
-#
-# This can be useful if you see the following behavior: you address an e-mail
-# to user ID ``stevef'' whose full name is ``Steve Franklin''. If mutt 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 will expand
-# ``Franklin'' to ``Franklin, Steve''.
-#
-#
-# set hdrs=yes
-#
-# Name: 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.
-#
-#
-# set header=no
-#
-# Name: header
-# Type: boolean
-# Default: no
-#
-#
-# When set, this variable causes Mutt to include the header
-# of the message you are replying to into the edit buffer.
-# The $weed setting applies.
-#
-#
-# set help=yes
-#
-# Name: 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 is
-# running. Since this variable is primarily aimed at new users, neither
-# of these should present a major problem.
-#
-#
-# set hidden_host=no
-#
-# Name: hidden_host
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt 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-IDs, and it will not lead to the
-# cut-off of first-level domains.
-#
-#
-# set hide_limited=no
-#
-# Name: hide_limited
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will not show the presence of messages that are hidden
-# by limiting, in the thread tree.
-#
-#
-# set hide_missing=yes
-#
-# Name: hide_missing
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will not show the presence of missing messages in the
-# thread tree.
-#
-#
-# set hide_thread_subject=yes
-#
-# Name: hide_thread_subject
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will not show the subject of messages in the thread
-# tree that have the same subject as their parent or closest previously
-# displayed sibling.
-#
-#
-# set hide_top_limited=no
-#
-# Name: hide_top_limited
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt 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_limited is set, this option will have no effect.
-#
-#
-# set hide_top_missing=yes
-#
-# Name: hide_top_missing
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will not show the presence of missing messages at the
-# top of threads in the thread tree. Note that when $hide_missing is
-# set, this option will have no effect.
-#
-#
-# set history=10
-#
-# Name: history
-# Type: number
-# Default: 10
-#
-#
-# This variable controls the size (in number of strings remembered) of
-# the string history buffer per category. The buffer is cleared each time the
-# variable is set.
-#
-#
-# set history_file="~/.mutthistory"
-#
-# Name: history_file
-# Type: path
-# Default: "~/.mutthistory"
-#
-#
-# The file in which Mutt will save its history.
-#
-#
-# set honor_followup_to=yes
-#
-# Name: honor_followup_to
-# Type: quadoption
-# Default: yes
-#
-#
-# This variable controls whether or not a Mail-Followup-To header is
-# honored when group-replying to a message.
-#
-#
-# set hostname=""
-#
-# Name: hostname
-# Type: string
-# Default: ""
-#
-#
-# Specifies the fully-qualified hostname of the system mutt is running on
-# containing the host's name and the DNS domain it belongs to. It is used
-# as the domain part (after ``@'') for local email addresses as well as
-# Message-Id headers.
-#
-# Its value is determined at startup as follows: If the node's name
-# as returned by the uname(3) function contains the hostname and the
-# domain, these are used to construct $hostname. If there is no
-# domain part returned, Mutt will look for a ``domain'' or ``search''
-# line in /etc/resolv.conf to determine the domain. Optionally, Mutt
-# can be compiled with a fixed domain name in which case a detected
-# one is not used.
-#
-# Also see $use_domain and $hidden_host.
-#
-# Note: On Debian systems, the default for this variable is obtained
-# from /etc/mailname when Mutt starts.
-#
-#
-# set ignore_linear_white_space=no
-#
-# Name: ignore_linear_white_space
-# Type: boolean
-# Default: no
-#
-#
-# This option replaces linear-white-space between encoded-word
-# and text to a single space to prevent the display of MIME-encoded
-# ``Subject:'' field from being divided into multiple lines.
-#
-#
-# set ignore_list_reply_to=no
-#
-# Name: ignore_list_reply_to
-# Type: boolean
-# Default: no
-#
-#
-# Affects the behaviour of the <reply> function when replying to
-# messages from mailing lists (as defined by the ``subscribe'' or
-# ``lists'' commands). When set, if the ``Reply-To:'' field is
-# set to the same value as the ``To:'' field, Mutt assumes that the
-# ``Reply-To:'' 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.
-#
-#
-# set imap_authenticators=""
-#
-# Name: imap_authenticators
-# Type: string
-# Default: ""
-#
-#
-# This is a colon-delimited list of authentication methods mutt may
-# attempt to use to log in to an IMAP server, in the order mutt should
-# try them. Authentication methods are either ``login'' or the right
-# side of an IMAP ``AUTH=xxx'' capability string, eg ``digest-md5'', ``gssapi''
-# or ``cram-md5''. This option is case-insensitive. If it's
-# unset (the default) mutt will try all available methods,
-# in order from most-secure to least-secure.
-#
-# Example:
-# set imap_authenticators="gssapi:cram-md5:login"
-#
-# Note: Mutt will only fall back to other authentication methods if
-# the previous methods are unavailable. If a method is available but
-# authentication fails, mutt will not connect to the IMAP server.
-#
-#
-# set imap_check_subscribed=no
-#
-# Name: imap_check_subscribed
-# 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 just as if you had issued individual ``mailboxes''
-# commands.
-#
-#
-# set imap_delim_chars="/."
-#
-# Name: imap_delim_chars
-# Type: string
-# Default: "/."
-#
-#
-# 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.
-#
-#
-# set imap_headers=""
-#
-# Name: imap_headers
-# Type: string
-# Default: ""
-#
-#
-# Mutt 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:'', ``List-Post:'', ``X-Label:'') from IMAP
-# servers before displaying the index menu. You may want to add more
-# headers for spam detection.
-#
-# Note: This is a space separated list, items should be uppercase
-# and not contain the colon, e.g. ``X-BOGOSITY X-SPAM-STATUS'' for the
-# ``X-Bogosity:'' and ``X-Spam-Status:'' header fields.
-#
-#
-# set imap_idle=no
-#
-# Name: imap_idle
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will attempt to use the IMAP IDLE extension
-# to check for new mail in the current mailbox. Some servers
-# (dovecot was the inspiration for this option) react badly
-# to mutt's implementation. If your connection seems to freeze
-# up periodically, try unsetting this.
-#
-#
-# set imap_keepalive=900
-#
-# Name: imap_keepalive
-# Type: number
-# Default: 900
-#
-#
-# This variable specifies the maximum amount of time in seconds that mutt
-# will wait before polling open IMAP connections, to prevent the server
-# from closing them before mutt 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.
-#
-#
-# set imap_list_subscribed=no
-#
-# Name: imap_list_subscribed
-# Type: boolean
-# Default: no
-#
-#
-# 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.
-#
-#
-# set imap_login=""
-#
-# Name: imap_login
-# Type: string
-# Default: ""
-#
-#
-# Your login name on the IMAP server.
-#
-# This variable defaults to the value of $imap_user.
-#
-#
-# set imap_pass=""
-#
-# Name: imap_pass
-# Type: string
-# Default: ""
-#
-#
-# Specifies the password for your IMAP account. If unset, Mutt will
-# prompt you for your password when you invoke the <fetch-mail> function
-# or try to open an IMAP folder.
-#
-# Warning: you should only use this option when you are on a
-# fairly secure machine, because the superuser can read your muttrc even
-# if you are the only one who can read the file.
-#
-#
-# set imap_passive=yes
-#
-# Name: imap_passive
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will not open new IMAP connections to check for new
-# mail. Mutt 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 invocation, or if opening the connection
-# is slow.
-#
-#
-# set imap_peek=yes
-#
-# Name: imap_peek
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt 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.
-#
-#
-# set imap_pipeline_depth=15
-#
-# Name: imap_pipeline_depth
-# Type: number
-# Default: 15
-#
-#
-# Controls the number of IMAP commands that may be queued up before they
-# are sent to the server. A deeper pipeline reduces the amount of time
-# mutt must wait for the server, and can make IMAP servers feel much
-# more responsive. But not all servers correctly handle pipelined commands,
-# so if you have problems you might want to try setting this variable to 0.
-#
-# Note: Changes to this variable have no effect on open connections.
-#
-#
-# set imap_servernoise=yes
-#
-# Name: imap_servernoise
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt 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.
-#
-#
-# set imap_user=""
-#
-# Name: imap_user
-# Type: string
-# Default: ""
-#
-#
-# 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.
-#
-#
-# set implicit_autoview=no
-#
-# Name: implicit_autoview
-# Type: boolean
-# Default: no
-#
-#
-# If set to ``yes'', mutt 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 will
-# use the viewer defined in that entry to convert the body part to text
-# form.
-#
-#
-# set include=ask-yes
-#
-# Name: 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.
-#
-#
-# set include_onlyfirst=no
-#
-# Name: include_onlyfirst
-# Type: boolean
-# Default: no
-#
-#
-# Controls whether or not Mutt includes only the first attachment
-# of the message you are replying.
-#
-#
-# set indent_string="> "
-#
-# Name: 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.
-#
-# This option is a format string, please see the description of
-# $index_format for supported printf(3)-style sequences.
-#
-# Because for format=lowed style messages the quoting mechanism
-# is strictly defined, this setting is ignored if $text_flowed is
-# set.
-#
-#
-# set index_format="%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"
-#
-# Name: 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 details).
-# The following sequences are defined in Mutt:
-# %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 sender (address + real name), either From: or Return-Path:
-# %F author name, or recipient name if the message is from you
-# %H spam attribute(s) of this message
-# %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 original save folder where mutt would formerly have
-# stashed the message: list name or recipient name
-# if not sent to a list
-# %P progress indicator for the builtin pager (how much of the file has been displayed)
-# %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
-# %X number of attachments
-# (please see the ``attachments'' section for possible speed effects)
-# %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(3); 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(3); a leading bang disables locales
-# %(fmt) the local date and time when the message was received.
-# ``fmt'' is expanded by the library function strftime(3);
-# a leading bang disables locales
-# %<fmt> the current local time. ``fmt'' is expanded by the library
-# function strftime(3); 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''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# ``Soft-fill'' deserves some explanation: Normal right-justification
-# will print everything to the left of the ``%>'', displaying padding and
-# whatever lies to the right only if there's room. By contrast,
-# soft-fill gives priority to the right-hand side, guaranteeing space
-# to display it and showing padding only if there's still room. If
-# necessary, soft-fill will eat text leftwards to make room for
-# rightward text.
-#
-# Note that these expandos are supported in
-# ``save-hook'', ``fcc-hook'' and ``fcc-save-hook'', too.
-#
-#
-# set ispell="ispell"
-#
-# Name: ispell
-# Type: path
-# Default: "ispell"
-#
-#
-# How to invoke ispell (GNU's spell-checking software).
-#
-#
-# set keep_flagged=no
-#
-# Name: 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.
-#
-#
-# set locale="C"
-#
-# Name: 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 environment variable $LC_TIME.
-#
-#
-# set mail_check=5
-#
-# Name: mail_check
-# Type: number
-# Default: 5
-#
-#
-# This variable configures how often (in seconds) mutt should look for
-# new mail. Also see the $timeout variable.
-#
-#
-# set mailcap_path=""
-#
-# Name: mailcap_path
-# Type: string
-# Default: ""
-#
-#
-# This variable specifies which files to consult when attempting to
-# display MIME bodies not directly supported by Mutt.
-#
-#
-# set mailcap_sanitize=yes
-#
-# Name: mailcap_sanitize
-# Type: boolean
-# Default: yes
-#
-#
-# If set, mutt 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!
-#
-#
-# set maildir_mtime=no
-#
-# Name: maildir_mtime
-# Type: boolean
-# Default: no
-#
-#
-# If set, the sort-by-date option in the browser will sort maildirs
-# smartly, not using the mtime of the maildir itself but that of the
-# newest message in the new subdirectory, making the sorting by
-# reverse date much more useful. People with maildirs over NFS may
-# wish to leave this option unset.
-#
-#
-# set header_cache=""
-#
-# Name: header_cache
-# Type: path
-# Default: ""
-#
-#
-# This variable points to the header cache database.
-# If pointing to a directory Mutt will contain a header cache
-# database file per folder, if pointing to a file that file will
-# be a single global header cache. By default it is unset so no header
-# caching will be used.
-#
-# Header caching can greatly improve speed when opening POP, IMAP
-# MH or Maildir folders, see ``caching'' for details.
-#
-#
-# set maildir_header_cache_verify=yes
-#
-# Name: maildir_header_cache_verify
-# Type: boolean
-# Default: yes
-#
-#
-# Check for Maildir unaware programs other than mutt having modified maildir
-# files when the header cache is in use. This incurs one stat(2) per
-# message every time the folder is opened (which can be very slow for NFS
-# folders).
-#
-#
-# set header_cache_pagesize="16384"
-#
-# Name: header_cache_pagesize
-# Type: string
-# Default: "16384"
-#
-#
-# When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-# this option changes the database page size. Too large or too small
-# values can waste space, memory, or CPU time. The default should be more
-# or less optimal for most use cases.
-#
-#
-# set maildir_trash=no
-#
-# Name: maildir_trash
-# Type: boolean
-# Default: no
-#
-#
-# If set, messages marked as deleted will be saved with the maildir
-# trashed flag instead of unlinked. Note: this only applies
-# to maildir-style mailboxes. Setting it will have no effect on other
-# mailbox types.
-#
-#
-# set mark_old=yes
-#
-# Name: mark_old
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether or not mutt marks new unread
-# messages as old if you exit a mailbox without reading them.
-# With this option set, the next time you start mutt, the messages
-# will show up with an ``O'' next to them in the index menu,
-# indicating that they are old.
-#
-#
-# set markers=yes
-#
-# Name: 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.
-#
-#
-# set mask="!^\\.[^.]"
-#
-# Name: 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.
-#
-#
-# set mbox="~/mbox"
-#
-# Name: mbox
-# Type: path
-# Default: "~/mbox"
-#
-#
-# This specifies the folder into which read mail in your $spoolfile
-# folder will be appended.
-#
-# Also see the $move variable.
-#
-#
-# set mbox_type=mbox
-#
-# Name: 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''.
-#
-#
-# set metoo=no
-#
-# Name: metoo
-# Type: boolean
-# Default: no
-#
-#
-# If unset, Mutt will remove your address (see the ``alternates''
-# command) from the list of recipients when replying to a message.
-#
-#
-# set menu_context=0
-#
-# Name: 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.)
-#
-#
-# set menu_move_off=yes
-#
-# Name: 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.
-#
-#
-# set menu_scroll=no
-#
-# Name: 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).
-#
-#
-# set meta_key=no
-#
-# Name: meta_key
-# Type: boolean
-# Default: no
-#
-#
-# If set, forces Mutt 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''.
-#
-#
-# set mh_purge=no
-#
-# Name: mh_purge
-# Type: boolean
-# Default: no
-#
-#
-# When unset, mutt will mimic mh's behaviour and rename deleted messages
-# to ,<old file name> in mh folders instead of really deleting
-# them. This leaves the message on disk but makes programs reading the folder
-# ignore it. If the variable is set, the message files will simply be
-# deleted.
-#
-# This option is similar to $maildir_trash for Maildir folders.
-#
-#
-# set mh_seq_flagged="flagged"
-#
-# Name: mh_seq_flagged
-# Type: string
-# Default: "flagged"
-#
-#
-# The name of the MH sequence used for flagged messages.
-#
-#
-# set mh_seq_replied="replied"
-#
-# Name: mh_seq_replied
-# Type: string
-# Default: "replied"
-#
-#
-# The name of the MH sequence used to tag replied messages.
-#
-#
-# set mh_seq_unseen="unseen"
-#
-# Name: mh_seq_unseen
-# Type: string
-# Default: "unseen"
-#
-#
-# The name of the MH sequence used for unseen messages.
-#
-#
-# set mime_forward=no
-#
-# Name: mime_forward
-# Type: quadoption
-# Default: no
-#
-#
-# When set, the message you are forwarding will be attached as a
-# separate message/rfc822 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.
-#
-#
-# set mime_forward_decode=no
-#
-# Name: 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.
-#
-#
-# set mime_forward_rest=yes
-#
-# Name: mime_forward_rest
-# Type: quadoption
-# Default: yes
-#
-#
-# When forwarding multiple attachments of a MIME message from the attachment
-# menu, attachments which cannot be decoded in a reasonable manner will
-# be attached to the newly composed message if this option is set.
-#
-#
-# set mix_entry_format="%4n %c %-16s %a"
-#
-# Name: mix_entry_format
-# Type: string
-# Default: "%4n %c %-16s %a"
-#
-#
-# 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.
-#
-#
-# set mixmaster="mixmaster"
-#
-# Name: mixmaster
-# Type: path
-# Default: "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.
-#
-# Note: On Debian systems, this option is set by default to
-# ``mixmaster-filter'' in /etc/Muttrc.
-#
-#
-# set move=no
-#
-# Name: move
-# Type: quadoption
-# Default: no
-#
-#
-# Controls whether or not Mutt will move read messages
-# from your spool mailbox to your $mbox mailbox, or as a result of
-# a ``mbox-hook'' command.
-#
-#
-# set message_cachedir=""
-#
-# Name: message_cachedir
-# Type: path
-# Default: ""
-#
-#
-# Set this to a directory and mutt will cache copies of messages from
-# your IMAP and POP servers here. You are free to remove entries at any
-# time.
-#
-# When setting this variable to a directory, mutt needs to fetch every
-# remote message only once and can perform regular expression searches
-# as fast as for local folders.
-#
-# Also see the $message_cache_clean variable.
-#
-#
-# set message_cache_clean=no
-#
-# Name: message_cache_clean
-# Type: boolean
-# Default: no
-#
-#
-# If set, mutt will clean out obsolete entries from the message cache when
-# the mailbox is synchronized. You probably only want to set it
-# every once in a while, since it can be a little slow
-# (especially for large folders).
-#
-#
-# set message_format="%s"
-#
-# Name: 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.
-#
-#
-# set narrow_tree=no
-#
-# Name: narrow_tree
-# Type: boolean
-# Default: no
-#
-#
-# This variable, when set, makes the thread tree narrower, allowing
-# deeper threads to fit on the screen.
-#
-#
-# set net_inc=10
-#
-# Name: 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, $write_inc and $net_inc.
-#
-#
-# set pager="builtin"
-#
-# Name: pager
-# Type: path
-# Default: "builtin"
-#
-#
-# This variable specifies which pager you would like to use to view
-# messages. The value ``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 functions
-# directly from the pager, and screen resizes cause lines longer than
-# the screen width to be badly formatted in the help menu.
-#
-#
-# set pager_context=0
-#
-# Name: 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 will display the line after the last one on the screen
-# at the top of the next page (0 lines of context).
-#
-#
-# set pager_format="-%Z- %C/%m: %-20.20n %s%* -- (%P)"
-#
-# Name: pager_format
-# Type: string
-# Default: "-%Z- %C/%m: %-20.20n %s%* -- (%P)"
-#
-#
-# 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.
-#
-#
-# set pager_index_lines=0
-#
-# Name: 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 setting 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.
-#
-#
-# set pager_stop=no
-#
-# Name: 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.
-#
-#
-# set crypt_autosign=no
-#
-# Name: crypt_autosign
-# Type: boolean
-# Default: no
-#
-#
-# Setting this variable will cause Mutt 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 instead of the pgp menu.
-# (Crypto only)
-#
-#
-# set crypt_autoencrypt=no
-#
-# Name: crypt_autoencrypt
-# Type: boolean
-# Default: no
-#
-#
-# Setting this variable will cause Mutt 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 instead.
-# (Crypto only)
-#
-#
-# set pgp_ignore_subkeys=yes
-#
-# Name: pgp_ignore_subkeys
-# Type: boolean
-# Default: yes
-#
-#
-# Setting this variable will cause Mutt 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)
-#
-#
-# set crypt_replyencrypt=yes
-#
-# Name: crypt_replyencrypt
-# Type: boolean
-# Default: yes
-#
-#
-# If set, automatically PGP or OpenSSL encrypt replies to messages which are
-# encrypted.
-# (Crypto only)
-#
-#
-# set crypt_replysign=no
-#
-# Name: crypt_replysign
-# Type: boolean
-# Default: no
-#
-#
-# If set, automatically PGP or OpenSSL sign replies to messages which are
-# signed.
-#
-# Note: this does not work on messages that are encrypted
-# and signed!
-# (Crypto only)
-#
-#
-# set crypt_replysignencrypted=no
-#
-# Name: crypt_replysignencrypted
-# Type: boolean
-# Default: no
-#
-#
-# 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 is not able
-# to find out whether an encrypted message is also signed.
-# (Crypto only)
-#
-#
-# set crypt_timestamp=yes
-#
-# Name: crypt_timestamp
-# Type: boolean
-# Default: yes
-#
-#
-# If set, mutt 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)
-#
-#
-# set pgp_use_gpg_agent=no
-#
-# Name: pgp_use_gpg_agent
-# Type: boolean
-# Default: no
-#
-#
-# If set, mutt will use a possibly-running gpg-agent(1) process.
-# (PGP only)
-#
-#
-# set crypt_verify_sig=yes
-#
-# Name: crypt_verify_sig
-# Type: quadoption
-# Default: yes
-#
-#
-# If ``yes'', always attempt to verify PGP or S/MIME signatures.
-# If ``ask-*'', ask whether or not to verify the signature.
-# If \Fi``no'', never attempt to verify cryptographic signatures.
-# (Crypto only)
-#
-#
-# set smime_is_default=no
-#
-# Name: smime_is_default
-# Type: boolean
-# Default: no
-#
-#
-# The default behaviour of mutt 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 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)
-#
-#
-# set smime_ask_cert_label=yes
-#
-# Name: 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)
-#
-#
-# set smime_decrypt_use_default_key=yes
-#
-# Name: smime_decrypt_use_default_key
-# Type: boolean
-# Default: yes
-#
-#
-# If set (default) this tells mutt to use the default key for decryption. Otherwise,
-# if managing multiple certificate-key-pairs, mutt 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)
-#
-#
-# set pgp_entry_format="%4n %t%f %4l/0x%k %-4a %2c %u"
-#
-# Name: 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)
-#
-#
-# set pgp_good_sign=""
-#
-# Name: 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)
-#
-#
-# set pgp_check_exit=yes
-#
-# Name: pgp_check_exit
-# Type: boolean
-# Default: yes
-#
-#
-# If set, mutt 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)
-#
-#
-# set pgp_long_ids=no
-#
-# Name: pgp_long_ids
-# Type: boolean
-# Default: no
-#
-#
-# If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs.
-# (PGP only)
-#
-#
-# set pgp_retainable_sigs=no
-#
-# Name: 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)
-#
-#
-# set pgp_autoinline=no
-#
-# Name: pgp_autoinline
-# Type: boolean
-# Default: no
-#
-#
-# This option controls whether Mutt 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 might automatically use PGP/MIME for messages
-# which consist of more than a single MIME part. Mutt can be
-# configured to ask before sending PGP/MIME messages when inline
-# (traditional) would not work.
-#
-# Also see the $pgp_mime_auto variable.
-#
-# Also note that using the old-style PGP message format is strongly
-# deprecated.
-# (PGP only)
-#
-#
-# set pgp_replyinline=no
-#
-# Name: pgp_replyinline
-# Type: boolean
-# Default: no
-#
-#
-# Setting this variable will cause Mutt 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
-# internals for previously checked/flagged messages.
-#
-# Note that Mutt might automatically use PGP/MIME for messages
-# which consist of more than a single MIME part. Mutt can be
-# configured to ask before sending PGP/MIME messages when inline
-# (traditional) would not work.
-#
-# Also see the $pgp_mime_auto variable.
-#
-# Also note that using the old-style PGP message format is strongly
-# deprecated.
-# (PGP only)
-#
-#
-# set pgp_show_unusable=yes
-#
-# Name: pgp_show_unusable
-# Type: boolean
-# Default: yes
-#
-#
-# If set, mutt 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)
-#
-#
-# set pgp_sign_as=""
-#
-# Name: 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)
-#
-#
-# set pgp_strict_enc=yes
-#
-# Name: pgp_strict_enc
-# Type: boolean
-# Default: yes
-#
-#
-# If set, Mutt 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)
-#
-#
-# set pgp_timeout=300
-#
-# Name: pgp_timeout
-# Type: number
-# Default: 300
-#
-#
-# The number of seconds after which a cached passphrase will expire if
-# not used.
-# (PGP only)
-#
-#
-# set pgp_sort_keys=address
-#
-# Name: pgp_sort_keys
-# Type: sort order
-# Default: address
-#
-#
-# Specifies how the entries in the pgp 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)
-#
-#
-# set pgp_mime_auto=ask-yes
-#
-# Name: pgp_mime_auto
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# This option controls whether Mutt 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 strongly
-# deprecated.
-# (PGP only)
-#
-#
-# set pgp_auto_decode=no
-#
-# Name: pgp_auto_decode
-# Type: boolean
-# Default: no
-#
-#
-# If set, mutt 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 will automatically
-# check the message for traditional pgp.
-#
-#
-# set pgp_mime_signature_filename="signature.asc"
-#
-# Name: pgp_mime_signature_filename
-# Type: string
-# Default: "signature.asc"
-#
-#
-# This option sets the filename used for signature parts in PGP/MIME
-# signed messages.
-#
-#
-# set pgp_mime_signature_description="Digital signature"
-#
-# Name: pgp_mime_signature_description
-# Type: string
-# Default: "Digital signature"
-#
-#
-# This option sets the Content-Description used for signature parts in
-# PGP/MIME signed messages.
-#
-#
-# set pgp_decode_command=""
-#
-# Name: 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 and gpg sample configuration files in
-# the samples/ subdirectory which has been installed on your system
-# alongside the documentation.
-# (PGP only)
-#
-#
-# set pgp_getkeys_command=""
-#
-# Name: pgp_getkeys_command
-# Type: string
-# Default: ""
-#
-#
-# This command is invoked whenever mutt will need public key information.
-# Of the sequences supported by $pgp_decode_command, %r is the only
-# printf(3)-like sequence used with this format.
-# (PGP only)
-#
-#
-# set pgp_verify_command=""
-#
-# Name: pgp_verify_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to verify PGP signatures.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_decrypt_command=""
-#
-# Name: pgp_decrypt_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to decrypt a PGP encrypted message.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_clearsign_command=""
-#
-# Name: pgp_clearsign_command
-# Type: string
-# Default: ""
-#
-#
-# This format is used to create an old-style ``clearsigned'' PGP
-# message. Note that the use of this format is strongly
-# deprecated.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_sign_command=""
-#
-# Name: pgp_sign_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to create the detached PGP signature for a
-# multipart/signed PGP/MIME body part.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_encrypt_sign_command=""
-#
-# Name: pgp_encrypt_sign_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to both sign and encrypt a body part.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_encrypt_only_command=""
-#
-# Name: pgp_encrypt_only_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to encrypt a body part without signing it.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_import_command=""
-#
-# Name: pgp_import_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to import a key from a message into
-# the user's public key ring.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_export_command=""
-#
-# Name: pgp_export_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to export a public key from the user's
-# key ring.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_verify_key_command=""
-#
-# Name: pgp_verify_key_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to verify key information from the key selection
-# menu.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_list_secring_command=""
-#
-# Name: 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.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set pgp_list_pubring_command=""
-#
-# Name: 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.
-#
-# This is a format string, see the $pgp_decode_command command for
-# possible printf(3)-like sequences.
-# (PGP only)
-#
-#
-# set forward_decrypt=yes
-#
-# Name: forward_decrypt
-# 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)
-#
-#
-# set smime_timeout=300
-#
-# Name: smime_timeout
-# Type: number
-# Default: 300
-#
-#
-# The number of seconds after which a cached passphrase will expire if
-# not used.
-# (S/MIME only)
-#
-#
-# set smime_encrypt_with=""
-#
-# Name: 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'', ``rc2-128''.
-# If unset, ``3des'' (TripleDES) is used.
-# (S/MIME only)
-#
-#
-# set smime_keys=""
-#
-# Name: smime_keys
-# Type: path
-# Default: ""
-#
-#
-# Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-# storage and 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 option points to the location of the private keys.
-# (S/MIME only)
-#
-#
-# set smime_ca_location=""
-#
-# Name: 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)
-#
-# Note: On Debian systems, this defaults to the first existing file in
-# the following list: ~/.smime/ca-certificates.crt ~/.smime/ca-bundle.crt
-# /etc/ssl/certs/ca-certificates.crt.
-#
-#
-# set smime_certificates=""
-#
-# Name: smime_certificates
-# Type: path
-# Default: ""
-#
-#
-# Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-# the location of the certificates.
-# (S/MIME only)
-#
-#
-# set smime_decrypt_command=""
-#
-# Name: 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)
-#
-#
-# set smime_verify_command=""
-#
-# Name: smime_verify_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to verify S/MIME signatures of type multipart/signed.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_verify_opaque_command=""
-#
-# Name: smime_verify_opaque_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to verify S/MIME signatures of type
-# application/x-pkcs7-mime.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_sign_command=""
-#
-# Name: 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.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_sign_opaque_command=""
-#
-# Name: 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.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_encrypt_command=""
-#
-# Name: smime_encrypt_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to create encrypted S/MIME messages.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_pk7out_command=""
-#
-# Name: 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).
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_get_cert_command=""
-#
-# Name: smime_get_cert_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to extract X509 certificates from a PKCS7 structure.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_get_signer_cert_command=""
-#
-# Name: 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:'' field.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_import_cert_command=""
-#
-# Name: smime_import_cert_command
-# Type: string
-# Default: ""
-#
-#
-# This command is used to import a certificate via smime_keys.
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_get_cert_email_command=""
-#
-# Name: 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).
-#
-# This is a format string, see the $smime_decrypt_command command for
-# possible printf(3)-like sequences.
-# (S/MIME only)
-#
-#
-# set smime_default_key=""
-#
-# Name: 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)
-#
-#
-# set ssl_client_cert=""
-#
-# Name: ssl_client_cert
-# Type: path
-# Default: ""
-#
-#
-# The file containing a client certificate and its associated private
-# key.
-#
-#
-# set ssl_force_tls=no
-#
-# Name: ssl_force_tls
-# Type: boolean
-# Default: no
-#
-#
-# If this variable is set, Mutt 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.
-#
-#
-# set ssl_starttls=yes
-#
-# Name: ssl_starttls
-# Type: quadoption
-# Default: yes
-#
-#
-# If set (the default), mutt will attempt to use STARTTLS on servers
-# advertising the capability. When unset, mutt will not attempt to
-# use STARTTLS regardless of the server's capabilities.
-#
-#
-# set certificate_file="~/.mutt_certificates"
-#
-# Name: certificate_file
-# Type: path
-# Default: "~/.mutt_certificates"
-#
-#
-# This variable specifies the file where the certificates you trust
-# are saved. When an unknown certificate is encountered, you are asked
-# if you accept it or not. If you accept it, the certificate can also
-# be saved in this file and further connections are automatically
-# accepted.
-#
-# You can also manually add CA certificates in this file. Any server
-# certificate that is signed with one of these CA certificates is
-# also automatically accepted.
-#
-# Example:
-# set certificate_file=~/.mutt/certificates
-#
-#
-# set ssl_use_sslv3=yes
-#
-# Name: ssl_use_sslv3
-# Type: boolean
-# Default: yes
-#
-#
-# This variable specifies whether to attempt to use SSLv3 in the
-# SSL authentication process.
-#
-#
-# set ssl_use_tlsv1=yes
-#
-# Name: ssl_use_tlsv1
-# Type: boolean
-# Default: yes
-#
-#
-# This variable specifies whether to attempt to use TLSv1 in the
-# SSL authentication process.
-#
-#
-# set ssl_min_dh_prime_bits=0
-#
-# Name: ssl_min_dh_prime_bits
-# Type: number
-# Default: 0
-#
-#
-# 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.
-#
-#
-# set ssl_ca_certificates_file=""
-#
-# Name: 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 is also automatically accepted.
-#
-# Example:
-# set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-#
-# Note: On Debian systems, this variable defaults to the example
-# mentioned. This file is managed by the ``ca-certificates'' package.
-#
-#
-# set pipe_split=no
-#
-# Name: pipe_split
-# Type: boolean
-# Default: no
-#
-#
-# Used in connection with the <pipe-message> function following
-# <tag-prefix>. If this variable is unset, when piping a list of
-# tagged messages Mutt will concatenate the messages and will pipe them
-# all concatenated. When set, Mutt 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.
-#
-#
-# set pipe_decode=no
-#
-# Name: pipe_decode
-# Type: boolean
-# Default: no
-#
-#
-# Used in connection with the <pipe-message> command. When unset,
-# Mutt will pipe the messages without any preprocessing. When set, Mutt
-# will weed headers and will attempt to decode the messages
-# first.
-#
-#
-# set pipe_sep="\n"
-#
-# Name: pipe_sep
-# Type: string
-# Default: "\n"
-#
-#
-# The separator to add between messages when piping a list of tagged
-# messages to an external Unix command.
-#
-#
-# set pop_authenticators=""
-#
-# Name: pop_authenticators
-# Type: string
-# Default: ""
-#
-#
-# This is a colon-delimited list of authentication methods mutt may
-# attempt to use to log in to an POP server, in the order mutt should
-# try them. Authentication methods are either ``user'', ``apop'' or any
-# SASL mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''.
-# This option is case-insensitive. If this option is unset
-# (the default) mutt will try all available methods, in order from
-# most-secure to least-secure.
-#
-# Example:
-# set pop_authenticators="digest-md5:apop:user"
-#
-#
-# set pop_auth_try_all=yes
-#
-# Name: pop_auth_try_all
-# Type: boolean
-# Default: yes
-#
-#
-# If set, Mutt will try all available authentication methods.
-# When unset, Mutt will only fall back to other authentication
-# methods if the previous methods are unavailable. If a method is
-# available but authentication fails, Mutt will not connect to the POP server.
-#
-#
-# set pop_checkinterval=60
-#
-# Name: pop_checkinterval
-# Type: number
-# Default: 60
-#
-#
-# This variable configures how often (in seconds) mutt should look for
-# new mail in the currently selected mailbox if it is a POP mailbox.
-#
-#
-# set pop_delete=ask-no
-#
-# Name: pop_delete
-# Type: quadoption
-# Default: ask-no
-#
-#
-# If set, Mutt will delete successfully downloaded messages from the POP
-# server when using the <fetch-mail> function. When unset, Mutt will
-# download messages but also leave them on the POP server.
-#
-#
-# set pop_host=""
-#
-# Name: pop_host
-# Type: string
-# Default: ""
-#
-#
-# The name of your POP server for the <fetch-mail> function. You
-# can also specify an alternative port, username and password, ie:
-# [pop[s]://][username[:password]@]popserver[:port]
-#
-# where ``[...]'' denotes an optional part.
-#
-#
-# set pop_last=no
-#
-# Name: pop_last
-# Type: boolean
-# Default: no
-#
-#
-# If this variable is set, mutt will try to use the ``LAST'' POP command
-# for retrieving only unread messages from the POP server when using
-# the <fetch-mail> function.
-#
-#
-# set pop_reconnect=ask-yes
-#
-# Name: pop_reconnect
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# Controls whether or not Mutt will try to reconnect to the POP server if
-# the connection is lost.
-#
-#
-# set pop_user=""
-#
-# Name: pop_user
-# Type: string
-# Default: ""
-#
-#
-# Your login name on the POP server.
-#
-# This variable defaults to your user name on the local machine.
-#
-#
-# set pop_pass=""
-#
-# Name: pop_pass
-# Type: string
-# Default: ""
-#
-#
-# Specifies the password for your POP account. If unset, Mutt will
-# prompt you for your password when you open a POP mailbox.
-#
-# Warning: you should only use this option when you are on a
-# fairly secure machine, because the superuser can read your muttrc
-# even if you are the only one who can read the file.
-#
-#
-# set post_indent_string=""
-#
-# Name: post_indent_string
-# Type: string
-# Default: ""
-#
-#
-# Similar to the $attribution variable, Mutt will append this
-# string after the inclusion of a message which is being replied to.
-#
-#
-# set postpone=ask-yes
-#
-# Name: postpone
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# Controls whether or not messages are saved in the $postponed
-# mailbox when you elect not to send immediately.
-#
-# Also see the $recall variable.
-#
-#
-# set postponed="~/postponed"
-#
-# Name: postponed
-# Type: path
-# Default: "~/postponed"
-#
-#
-# Mutt allows you to indefinitely ``postpone sending a message'' which
-# you are editing. When you choose to postpone a message, Mutt saves it
-# in the mailbox specified by this variable.
-#
-# Also see the $postpone variable.
-#
-#
-# set preconnect=""
-#
-# Name: preconnect
-# Type: string
-# Default: ""
-#
-#
-# If set, a shell command to be executed if mutt 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 gives up opening the server. Example:
-# set 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.
-#
-# When set, Mutt uses the tunnel for all remote connections.
-# Please see ``account-hook'' in the manual for how to use different
-# tunnel commands per connection.
-#
-#
-# set print=ask-no
-#
-# Name: print
-# Type: quadoption
-# Default: ask-no
-#
-#
-# Controls whether or not Mutt really prints messages.
-# This is set to ``ask-no'' by default, because some people
-# accidentally hit ``p'' often.
-#
-#
-# set print_command="lpr"
-#
-# Name: print_command
-# Type: path
-# Default: "lpr"
-#
-#
-# This specifies the command pipe that should be used to print messages.
-#
-#
-# set print_decode=yes
-#
-# Name: 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.
-#
-#
-# set print_split=no
-#
-# Name: 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.
-#
-#
-# set prompt_after=yes
-#
-# Name: prompt_after
-# Type: boolean
-# Default: yes
-#
-#
-# If you use an external $pager, setting this variable will
-# cause Mutt to prompt you for a command when the pager exits rather
-# than returning to the index menu. If unset, Mutt will return to the
-# index menu when the external pager exits.
-#
-#
-# set query_command=""
-#
-# Name: query_command
-# Type: path
-# Default: ""
-#
-#
-# This specifies the command that mutt 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.
-#
-#
-# set query_format="%4c %t %-25.25a %-25.25n %?e?(%e)?"
-#
-# Name: query_format
-# Type: string
-# Default: "%4c %t %-25.25a %-25.25n %?e?(%e)?"
-#
-#
-# This variable describes the format of the ``query'' menu. The
-# following printf(3)-style sequences are understood:
-# %a destination address
-# %c current entry number
-# %e extra information *
-# %n destination name
-# %t ``*'' if current entry is tagged, a space otherwise
-# %>X right justify the rest of the string and pad with ``X''
-# %|X pad to the end of the line with ``X''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# For an explanation of ``soft-fill'', see the $index_format documentation.
-#
-# * = can be optionally printed if nonzero, see the $status_format documentation.
-#
-#
-# set quit=yes
-#
-# Name: quit
-# Type: quadoption
-# Default: yes
-#
-#
-# This variable controls whether ``quit'' and ``exit'' actually quit
-# from mutt. If this option is set, they do quit, if it is unset, 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.
-#
-#
-# set quote_regexp="^([ \t]*[|>:}#])+"
-#
-# Name: 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. Quoted text may be filtered
-# out using the <toggle-quoted> command, or colored according to the
-# ``color quoted'' family of directives.
-#
-# Higher levels of quoting may be colored differently (``color quoted1'',
-# ``color quoted2'', etc.). The quoting level is determined by removing
-# the last character from the matched text and recursively reapplying
-# the regular expression until it fails to produce a match.
-#
-# Match detection may be overridden by the $smileys regular expression.
-#
-#
-# set read_inc=10
-#
-# Name: read_inc
-# Type: number
-# Default: 10
-#
-#
-# If set to a value greater than 0, Mutt will display which message it
-# is currently on when reading a mailbox or when performing search actions
-# such as search and limit. The message is printed after
-# this many messages have been read or searched (e.g., if set to 25, Mutt will
-# print a message when it is at message 25, and then again when it gets
-# to message 50). This variable is meant to indicate progress when
-# reading or searching 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, $net_inc and $time_inc variables and the
-# ``tuning'' section of the manual for performance considerations.
-#
-#
-# set read_only=no
-#
-# Name: read_only
-# Type: boolean
-# Default: no
-#
-#
-# If set, all folders are opened in read-only mode.
-#
-#
-# set realname=""
-#
-# Name: 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 that this
-# variable will not be used when the user has set a real name
-# in the $from variable.
-#
-#
-# set recall=ask-yes
-#
-# Name: recall
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# Controls whether or not Mutt recalls postponed messages
-# when composing a new message.
-#
-# Setting this variable to is not generally useful, and thus not
-# recommended.
-#
-# Also see $postponed variable.
-#
-#
-# set record="~/sent"
-#
-# Name: record
-# Type: path
-# Default: "~/sent"
-#
-#
-# 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:'' 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.
-#
-#
-# set reply_regexp="^(re([\\[0-9\\]+])*|aw):[ \t]*"
-#
-# Name: 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:".
-#
-#
-# set reply_self=no
-#
-# Name: reply_self
-# Type: boolean
-# Default: no
-#
-#
-# If unset and you are replying to a message sent by you, Mutt will
-# assume that you want to reply to the recipients of that message rather
-# than to yourself.
-#
-# Also see the ``alternates'' command.
-#
-#
-# set reply_to=ask-yes
-#
-# Name: reply_to
-# Type: quadoption
-# Default: ask-yes
-#
-#
-# If set, when replying to a message, Mutt will use the address listed
-# in the Reply-to: header 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.
-#
-#
-# set resolve=yes
-#
-# Name: 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.
-#
-#
-# set reverse_alias=no
-#
-# Name: reverse_alias
-# Type: boolean
-# Default: no
-#
-#
-# This variable controls whether or not Mutt 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.
-#
-#
-# set reverse_name=no
-#
-# Name: 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.
-#
-# Also see the ``alternates'' command.
-#
-#
-# set reverse_realname=yes
-#
-# Name: reverse_realname
-# Type: boolean
-# Default: yes
-#
-#
-# This variable fine-tunes the behaviour of the $reverse_name feature.
-# When it is set, mutt will use the address from incoming messages as-is,
-# possibly including eventual real names. When it is unset, mutt will
-# override any such real names with the setting of the $realname variable.
-#
-#
-# set rfc2047_parameters=no
-#
-# Name: rfc2047_parameters
-# Type: boolean
-# Default: no
-#
-#
-# When this variable is set, Mutt will decode RFC2047-encoded MIME
-# parameters. You want to set this variable when mutt suggests you
-# to save attachments to files named like:
-# =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-#
-# When this variable is set interactively, the change won't be
-# active until you change folders.
-#
-# Note that this use of RFC2047'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 generates this kind of encoding. Instead, mutt will
-# unconditionally use the encoding specified in RFC2231.
-#
-#
-# set save_address=no
-#
-# Name: save_address
-# Type: boolean
-# Default: no
-#
-#
-# If set, mutt 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.
-#
-#
-# set save_empty=yes
-#
-# Name: 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 does not
-# delete MH and Maildir directories.
-#
-#
-# set save_history=0
-#
-# Name: save_history
-# Type: number
-# Default: 0
-#
-#
-# This variable controls the size of the history (per category) saved in the
-# $history_file file.
-#
-#
-# set save_name=no
-#
-# Name: 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.
-#
-#
-# set score=yes
-#
-# Name: 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 related are used.
-#
-#
-# set score_threshold_delete=-1
-#
-# Name: 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. Since
-# mutt scores are always greater than or equal to zero, the default setting
-# of this variable will never mark a message for deletion.
-#
-#
-# set score_threshold_flag=9999
-#
-# Name: 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".
-#
-#
-# set score_threshold_read=-1
-#
-# Name: 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. Since
-# mutt scores are always greater than or equal to zero, the default setting
-# of this variable will never mark a message read.
-#
-#
-# set send_charset="us-ascii:iso-8859-1:utf-8"
-#
-# Name: send_charset
-# Type: string
-# Default: "us-ascii:iso-8859-1:utf-8"
-#
-#
-# A colon-delimited list of character sets for outgoing messages. Mutt 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''.
-#
-# In case the text cannot be converted into one of these exactly,
-# mutt uses $charset as a fallback.
-#
-#
-# set sendmail="/usr/sbin/sendmail -oem -oi"
-#
-# Name: sendmail
-# Type: path
-# Default: "/usr/sbin/sendmail -oem -oi"
-#
-#
-# Specifies the program and arguments used to deliver mail sent by Mutt.
-# Mutt expects that the specified program interprets additional
-# arguments as recipient addresses.
-#
-#
-# set sendmail_wait=0
-#
-# Name: 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 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.
-#
-#
-# set shell=""
-#
-# Name: shell
-# Type: path
-# Default: ""
-#
-#
-# Command to use when spawning a subshell. By default, the user's login
-# shell from /etc/passwd is used.
-#
-#
-# set sig_dashes=yes
-#
-# Name: sig_dashes
-# Type: boolean
-# Default: yes
-#
-#
-# If set, a line containing ``-- '' (note the trailing 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 has the ability to highlight
-# the signature in a different color in the builtin pager.
-#
-#
-# set sig_on_top=no
-#
-# Name: 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.
-#
-#
-# set signature="~/.signature"
-#
-# Name: 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 standard output.
-#
-#
-# set simple_search="~f %s | ~s %s"
-#
-# Name: simple_search
-# Type: string
-# Default: "~f %s | ~s %s"
-#
-#
-# Specifies how Mutt should expand a simple search into a real search
-# pattern. A simple search is one that does not contain any of the ``~'' pattern
-# operators. See ``patterns'' for more information on search patterns.
-#
-# For example, if you simply type ``joe'' at a search or limit prompt, Mutt
-# will automatically expand it to the value specified by this variable by
-# replacing ``%s'' with the supplied string.
-# For the default value, ``joe'' would be expanded to: ``~f joe | ~s joe''.
-#
-#
-# set smart_wrap=yes
-#
-# Name: 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.
-#
-#
-# set smileys="(>From )|(:[-^]?[][)(><}{|/DP])"
-#
-# Name: smileys
-# Type: regular expression
-# Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
-#
-#
-# The pager uses this variable to catch some common false
-# positives of $quote_regexp, most notably smileys and not consider
-# a line quoted text if it also matches $smileys. This mostly
-# happens at the beginning of a line.
-#
-#
-# set sleep_time=1
-#
-# Name: 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.
-#
-#
-# set smtp_authenticators=""
-#
-# Name: smtp_authenticators
-# Type: string
-# Default: ""
-#
-#
-# This is a colon-delimited list of authentication methods mutt may
-# attempt to use to log in to an SMTP server, in the order mutt should
-# try them. Authentication methods are any SASL mechanism, eg
-# ``digest-md5'', ``gssapi'' or ``cram-md5''.
-# This option is case-insensitive. If it is ``unset''
-# (the default) mutt will try all available methods, in order from
-# most-secure to least-secure.
-#
-# Example:
-# set smtp_authenticators="digest-md5:cram-md5"
-#
-#
-# set smtp_pass=""
-#
-# Name: smtp_pass
-# Type: string
-# Default: ""
-#
-#
-# Specifies the password for your SMTP account. If unset, Mutt will
-# prompt you for your password when you first send mail via SMTP.
-# See $smtp_url to configure mutt to send mail via SMTP.
-#
-# Warning: you should only use this option when you are on a
-# fairly secure machine, because the superuser can read your muttrc even
-# if you are the only one who can read the file.
-#
-#
-# set smtp_url=""
-#
-# Name: smtp_url
-# Type: string
-# Default: ""
-#
-#
-# Defines the SMTP smarthost where sent messages should relayed for
-# delivery. This should take the form of an SMTP URL, eg:
-# smtp[s]://[user[:pass]@]host[:port]/
-#
-# \.\.\. where ``[...]'' denotes an optional part.
-# Setting this variable overrides the value of the $sendmail
-# variable.
-#
-#
-# set sort=date
-#
-# Name: 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'').
-#
-# Note: On Debian systems, this option is set by default to
-# ``threads'' in /etc/Muttrc.
-#
-#
-# set sort_alias=alias
-#
-# Name: 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)
-#
-#
-# set sort_aux=date
-#
-# Name: 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 will just use ``date-sent''). You can also
-# specify the ``last-'' prefix in addition to the ``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).
-#
-#
-# set sort_browser=alpha
-#
-# Name: 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'').
-#
-#
-# set sort_re=yes
-#
-# Name: 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 uses to thread messages by subject. With $sort_re set, mutt 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_re unset, mutt will attach
-# the message whether or not this is the case, as long as the
-# non-$reply_regexp parts of both messages are identical.
-#
-#
-# set spam_separator=","
-#
-# Name: spam_separator
-# Type: string
-# Default: ","
-#
-#
-# This variable 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 this variable's value as a
-# separator.
-#
-#
-# set spoolfile=""
-#
-# Name: spoolfile
-# Type: path
-# Default: ""
-#
-#
-# If your spool mailbox is in a non-default place where Mutt cannot find
-# it, you can specify its location with this variable. Mutt will
-# automatically set this variable to the value of the environment
-# variable $MAIL if it is not set.
-#
-#
-# set status_chars="-*%A"
-#
-# Name: 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).
-#
-#
-# set status_format="-%r-Mutt: %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)---"
-#
-# Name: status_format
-# Type: string
-# Default: "-%r-Mutt: %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 *
-# %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 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''
-# %*X soft-fill with character ``X'' as pad
-#
-#
-# For an explanation of ``soft-fill'', see the $index_format documentation.
-#
-# * = 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_string may 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.?
-#
-# You can also switch between two strings using the following construct:
-#
-# %?<sequence_char>?<if_string>&<else_string>?
-#
-# If the value of sequence_char is non-zero, if_string will
-# be expanded, otherwise else_string will be expanded.
-#
-# You can 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
-# will replace any dots in the expansion by underscores. This might be helpful
-# with IMAP folders that don't like dots in folder names.
-#
-#
-# set status_on_top=no
-#
-# Name: 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. If $help
-# is set, too it'll be placed at the bottom.
-#
-#
-# set strict_threads=no
-#
-# Name: strict_threads
-# Type: boolean
-# Default: no
-#
-#
-# If set, threading will only make use of the ``In-Reply-To'' and
-# ``References:'' 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 subjects like ``hi'' which will get grouped together. See also
-# $sort_re for a less drastic way of controlling this
-# behaviour.
-#
-#
-# set suspend=yes
-#
-# Name: suspend
-# Type: boolean
-# Default: yes
-#
-#
-# When unset, mutt won't stop when the user presses the terminal's
-# susp key, usually ``^Z''. This is useful if you run mutt
-# inside an xterm using a command like ``xterm -e mutt''.
-#
-#
-# set text_flowed=no
-#
-# Name: text_flowed
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will generate ``format=flowed'' bodies with a content type
-# of ``text/plain; format=flowed''.
-# 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.
-#
-#
-# set thread_received=no
-#
-# Name: thread_received
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt uses the date received rather than the date sent
-# to thread messages by subject.
-#
-#
-# set thorough_search=no
-#
-# Name: thorough_search
-# Type: boolean
-# Default: no
-#
-#
-# Affects the ~b and ~h search operations described in
-# section ``patterns''. If set, the headers and body/attachments of
-# messages to be searched are decoded before searching. If unset,
-# messages are searched as they appear in the folder.
-#
-# Users searching attachments or for non-ASCII characters should set
-# this value because decoding also includes MIME parsing/decoding and possible
-# character set conversions. Otherwise mutt will attempt to match against the
-# raw message received (for example quoted-printable encoded or with encoded
-# headers) which may lead to incorrect search results.
-#
-#
-# set tilde=no
-#
-# Name: tilde
-# Type: boolean
-# Default: no
-#
-#
-# When set, the internal-pager will pad blank lines to the bottom of the
-# screen with a tilde (``~'').
-#
-#
-# set time_inc=0
-#
-# Name: time_inc
-# Type: number
-# Default: 0
-#
-#
-# Along with $read_inc, $write_inc, and $net_inc, this
-# variable controls the frequency with which progress updates are
-# displayed. It suppresses updates less than $time_inc milliseconds
-# apart. This can improve throughput on systems with slow terminals,
-# or when running mutt on a remote system.
-#
-# Also see the ``tuning'' section of the manual for performance considerations.
-#
-#
-# set timeout=600
-#
-# Name: timeout
-# Type: number
-# Default: 600
-#
-#
-# When Mutt is waiting for user input either idleing in menus or
-# in an interactive prompt, Mutt would block until input is
-# present. Depending on the context, this would prevent certain
-# operations from working, like checking for new mail or keeping
-# an IMAP connection alive.
-#
-# This variable controls how many seconds Mutt will at most wait
-# until it aborts waiting for input, performs these operations and
-# continues to wait for input.
-#
-# A value of zero or less will cause Mutt to never time out.
-#
-#
-# set tmpdir=""
-#
-# Name: tmpdir
-# Type: path
-# Default: ""
-#
-#
-# This variable allows you to specify where Mutt 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.
-#
-#
-# set to_chars=" +TCFL"
-#
-# Name: 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. The second is used when you are the only
-# recipient of the message. The third is when your address
-# appears in the ``To:'' header field, but you are not the only recipient of
-# the message. 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 subscribe to.
-#
-#
-# set trash=""
-#
-# Name: 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 you have a way to clean the trash.
-#
-#
-# set tunnel=""
-#
-# Name: tunnel
-# Type: string
-# Default: ""
-#
-#
-# Setting this variable will cause mutt 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/SMTP server. Example:
-# set 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.
-#
-#
-# set use_8bitmime=no
-#
-# Name: 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 you may not be able to send mail.
-#
-# When set, Mutt will invoke $sendmail with the -B8BITMIME
-# flag when sending 8-bit messages to enable ESMTP negotiation.
-#
-#
-# set use_domain=yes
-#
-# Name: use_domain
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will qualify all local addresses (ones without the
-# ``@host'' portion) with the value of $hostname. If unset, no
-# addresses will be qualified.
-#
-#
-# set use_envelope_from=no
-#
-# Name: use_envelope_from
-# Type: boolean
-# Default: no
-#
-#
-# When set, mutt will set the envelope sender of the message.
-# If $envelope_from_address is set, it will be used as the sender
-# address. If unset, mutt will attempt to derive the sender from the
-# ``From:'' header.
-#
-# Note that this information is passed to sendmail command using the
-# -f command line switch. Therefore setting this option is not useful
-# if the $sendmail variable already contains -f or if the
-# executable pointed to by $sendmail doesn't support the -f switch.
-#
-#
-# set use_from=yes
-#
-# Name: use_from
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt 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.
-#
-#
-# set use_idn=yes
-#
-# Name: use_idn
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will show you international domain names decoded.
-# Note: You can use IDNs for addresses even if this is unset.
-# This variable only affects decoding.
-#
-#
-# set use_ipv6=yes
-#
-# Name: use_ipv6
-# Type: boolean
-# Default: yes
-#
-#
-# When set, Mutt will look for IPv6 addresses of hosts it tries to
-# contact. If this option is unset, Mutt will restrict itself to IPv4 addresses.
-# Normally, the default should work.
-#
-#
-# set user_agent=yes
-#
-# Name: user_agent
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will add a ``User-Agent:'' header to outgoing
-# messages, indicating which version of mutt was used for composing
-# them.
-#
-#
-# set visual=""
-#
-# Name: visual
-# Type: path
-# Default: ""
-#
-#
-# Specifies the visual editor to invoke when the ``~v'' command is
-# given in the builtin editor.
-#
-#
-# set wait_key=yes
-#
-# Name: wait_key
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether Mutt will ask you to press a key after an external command
-# has been invoked by these functions: <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 will always ask for a key. When unset, Mutt will wait
-# for a key only if the external command returned a non-zero status.
-#
-#
-# set weed=yes
-#
-# Name: weed
-# Type: boolean
-# Default: yes
-#
-#
-# When set, mutt will weed headers when displaying, forwarding,
-# printing, or replying to messages.
-#
-#
-# set wrap=0
-#
-# Name: wrap
-# Type: number
-# Default: 0
-#
-#
-# When set to a positive value, mutt will wrap text at $wrap characters.
-# When set to a negative value, mutt will wrap text so that there are $wrap
-# characters of empty space on the right side of the terminal.
-#
-#
-# set wrap_search=yes
-#
-# Name: wrap_search
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether searches wrap around the end.
-#
-# When set, searches will wrap around the first (or last) item. When
-# unset, incremental searches will not wrap.
-#
-#
-# set wrapmargin=0
-#
-# Name: wrapmargin
-# Type: number
-# Default: 0
-#
-#
-# (DEPRECATED) Equivalent to setting $wrap with a negative value.
-#
-#
-# set write_inc=10
-#
-# Name: 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, $net_inc and $time_inc variables and the
-# ``tuning'' section of the manual for performance considerations.
-#
-#
-# set write_bcc=yes
-#
-# Name: write_bcc
-# Type: boolean
-# Default: yes
-#
-#
-# Controls whether mutt writes out the ``Bcc:'' header when preparing
-# messages to be sent. Exim users may wish to unset this. If mutt
-# is set to deliver directly via SMTP (see $smtp_url), this
-# option does nothing: mutt will never write out the ``Bcc:'' header
-# in this case.
-#
-# Note: On Debian systems, exim4 and postfix strip BCC headers by
-# default. The above warning applies to exim3 users, see /etc/Muttrc.
-#
-#
-# set xterm_icon="M%?n?AIL&ail?"
-#
-# Name: xterm_icon
-# Type: string
-# Default: "M%?n?AIL&ail?"
-#
-#
-# Controls the format of the icon title, as long as xterm_set_titles
-# is enabled. This string is identical in formatting to the one used by
-# ``$status_format''.
-#
-#
-# set xterm_set_titles=no
-#
-# Name: xterm_set_titles
-# Type: boolean
-# Default: no
-#
-#
-# Controls whether mutt sets the xterm title bar and icon name
-# (as long as you are in an appropriate terminal).
-#
-#
-# set xterm_title="Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?"
-#
-# Name: xterm_title
-# Type: string
-# Default: "Mutt 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''.
-#
-#
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. Advanced Usage</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="configuration.html" title="Chapter 3. Configuration" /><link rel="next" href="mimesupport.html" title="Chapter 5. Mutt's MIME Support" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Advanced Usage</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="configuration.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="mimesupport.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="advancedusage"></a>Chapter 4. Advanced Usage</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="advancedusage.html#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="regexp"></a>1. Regular Expressions</h2></div></div></div><p>
-All string patterns in Mutt including those in more complex
-<a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> must be specified
-using regular expressions (regexp) in the “<span class="quote">POSIX extended</span>” 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.
-</p><p>
-The search is case sensitive if the pattern contains at least one upper
-case letter, and case insensitive otherwise.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that “<span class="quote">\</span>”
-must be quoted if used for a regular expression in an initialization
-command: “<span class="quote">\\</span>”.
-</p></div><p>
-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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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 <a class="xref" href="configuration.html#muttrc-syntax" title="2. Syntax of Initialization Files">Syntax of Initialization Files</a>
-for more information on " and ' delimiter processing. To match a
-literal " or ' you must preface it with \ (backslash).
-</p></div><p>
-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.
-</p><p>
-The period “<span class="quote">.</span>” matches any single character. The caret “<span class="quote">^</span>” and
-the dollar sign “<span class="quote">$</span>” are metacharacters that respectively match
-the empty string at the beginning and end of a line.
-</p><p>
-A list of characters enclosed by “<span class="quote">[</span>” and “<span class="quote">]</span>” matches any
-single character in that list; if the first character of the list
-is a caret “<span class="quote">^</span>” then it matches any character <span class="bold"><strong>not</strong></span> in the
-list. For example, the regular expression <span class="bold"><strong>[0123456789]</strong></span>
-matches any single digit. A range of ASCII characters may be specified
-by giving the first and last characters, separated by a hyphen
-“<span class="quote">-</span>”. Most metacharacters lose their special meaning inside
-lists. To include a literal “<span class="quote">]</span>” place it first in the list.
-Similarly, to include a literal “<span class="quote">^</span>” place it anywhere but first.
-Finally, to include a literal hyphen “<span class="quote">-</span>” place it last.
-</p><p>
-Certain named classes of characters are predefined. Character classes
-consist of “<span class="quote">[:</span>”, a keyword denoting the class, and “<span class="quote">:]</span>”.
-The following classes are defined by the POSIX standard in
-<a class="xref" href="advancedusage.html#posix-regex-char-classes" title="Table 4.1. POSIX regular expression character classes">Table 4.1, “POSIX regular expression character classes”</a>
-</p><div class="table"><a id="posix-regex-char-classes"></a><p class="title"><b>Table 4.1. POSIX regular expression character classes</b></p><div class="table-contents"><table summary="POSIX regular expression character classes" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Character class</th><th>Description</th></tr></thead><tbody><tr><td>[:alnum:]</td><td>Alphanumeric characters</td></tr><tr><td>[:alpha:]</td><td>Alphabetic characters</td></tr><tr><td>[:blank:]</td><td>Space or tab characters</td></tr><tr><td>[:cntrl:]</td><td>Control characters</td></tr><tr><td>[:digit:]</td><td>Numeric characters</td></tr><tr><td>[:graph:]</td><td>Characters that are both printable and visible. (A space is printable, but not visible, while an “<span class="quote">a</span>” is both)</td></tr><tr><td>[:lower:]</td><td>Lower-case alphabetic characters</td></tr><tr><td>[:print:]</td><td>Printable characters (characters that are not control characters)</td></tr><tr><td>[:punct:]</td><td>Punctuation characters (characters that are not letter, digits, control characters, or space characters)</td></tr><tr><td>[:space:]</td><td>Space characters (such as space, tab and formfeed, to name a few)</td></tr><tr><td>[:upper:]</td><td>Upper-case alphabetic characters</td></tr><tr><td>[:xdigit:]</td><td>Characters that are hexadecimal digits</td></tr></tbody></table></div></div><br class="table-break" /><p>
-A character class is only valid in a regular expression inside the
-brackets of a character list.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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, <span class="bold"><strong>[[:digit:]]</strong></span> is equivalent to
-<span class="bold"><strong>[0-9]</strong></span>.
-</p></div><p>
-Two additional special sequences can appear in character lists. These
-apply to non-ASCII character sets, which can have single symbols (called
-collating elements) that are represented with more than one character,
-as well as several characters that are equivalent for collating or
-sorting purposes:
-</p><div class="variablelist"><dl><dt><span class="term">Collating Symbols</span></dt><dd><p>
-A collating symbol is a multi-character collating element enclosed in
-“<span class="quote">[.</span>” and “<span class="quote">.]</span>”. For example, if “<span class="quote">ch</span>” is a collating
-element, then <span class="bold"><strong>[[.ch.]]</strong></span> is a regexp that matches
-this collating element, while <span class="bold"><strong>[ch]</strong></span> is a regexp that
-matches either “<span class="quote">c</span>” or “<span class="quote">h</span>”.
-</p></dd><dt><span class="term">Equivalence Classes</span></dt><dd><p>
-An equivalence class is a locale-specific name for a list of
-characters that are equivalent. The name is enclosed in “<span class="quote">[=</span>”
-and “<span class="quote">=]</span>”. For example, the name “<span class="quote">e</span>” might be used to
-represent all of “<span class="quote">è</span>” “<span class="quote">é</span>” and “<span class="quote">e</span>”. In this case,
-<span class="bold"><strong>[[=e=]]</strong></span> is a regexp that matches any of
-“<span class="quote">è</span>”, “<span class="quote">é</span>” and “<span class="quote">e</span>”.
-</p></dd></dl></div><p>
-A regular expression matching a single character may be followed by one
-of several repetition operators described in <a class="xref" href="advancedusage.html#regex-repeat" title="Table 4.2. Regular expression repetition operators">Table 4.2, “Regular expression repetition operators”</a>.
-</p><div class="table"><a id="regex-repeat"></a><p class="title"><b>Table 4.2. Regular expression repetition operators</b></p><div class="table-contents"><table summary="Regular expression repetition operators" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Operator</th><th>Description</th></tr></thead><tbody><tr><td>?</td><td>The preceding item is optional and matched at most once</td></tr><tr><td>*</td><td>The preceding item will be matched zero or more times</td></tr><tr><td>+</td><td>The preceding item will be matched one or more times</td></tr><tr><td>{n}</td><td>The preceding item is matched exactly <span class="emphasis"><em>n</em></span> times</td></tr><tr><td>{n,}</td><td>The preceding item is matched <span class="emphasis"><em>n</em></span> or more times</td></tr><tr><td>{,m}</td><td>The preceding item is matched at most <span class="emphasis"><em>m</em></span> times</td></tr><tr><td>{n,m}</td><td>The preceding item is matched at least <span class="emphasis"><em>n</em></span> times, but no more than <span class="emphasis"><em>m</em></span> times</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Two regular expressions may be concatenated; the resulting regular
-expression matches any string formed by concatenating two substrings
-that respectively match the concatenated subexpressions.
-</p><p>
-Two regular expressions may be joined by the infix operator “<span class="quote">|</span>”;
-the resulting regular expression matches any string matching either
-subexpression.
-</p><p>
-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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you compile Mutt with the GNU <span class="emphasis"><em>rx</em></span> package, the
-following operators may also be used in regular expressions as described in <a class="xref" href="advancedusage.html#regex-gnu-ext" title="Table 4.3. GNU regular expression extensions">Table 4.3, “GNU regular expression extensions”</a>.
-</p></div><div class="table"><a id="regex-gnu-ext"></a><p class="title"><b>Table 4.3. GNU regular expression extensions</b></p><div class="table-contents"><table summary="GNU regular expression extensions" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Expression</th><th>Description</th></tr></thead><tbody><tr><td>\\y</td><td>Matches the empty string at either the beginning or the end of a word</td></tr><tr><td>\\B</td><td>Matches the empty string within a word</td></tr><tr><td>\\<</td><td>Matches the empty string at the beginning of a word</td></tr><tr><td>\\></td><td>Matches the empty string at the end of a word</td></tr><tr><td>\\w</td><td>Matches any word-constituent character (letter, digit, or underscore)</td></tr><tr><td>\\W</td><td>Matches any character that is not word-constituent</td></tr><tr><td>\\`</td><td>Matches the empty string at the beginning of a buffer (string)</td></tr><tr><td>\\'</td><td>Matches the empty string at the end of a buffer</td></tr></tbody></table></div></div><br class="table-break" /><p>
-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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="patterns"></a>2. Patterns: Searching, Limiting and Tagging</h2></div></div></div><p>
-Many of Mutt's commands allow you to specify a pattern to match
-(<code class="literal">limit</code>, <code class="literal">tag-pattern</code>,
-<code class="literal">delete-pattern</code>, etc.). <a class="xref" href="advancedusage.html#tab-patterns" title="Table 4.4. Pattern modifiers">Table 4.4, “Pattern modifiers”</a>
-shows several ways to select messages.
-</p><div class="table"><a id="tab-patterns"></a><p class="title"><b>Table 4.4. Pattern modifiers</b></p><div class="table-contents"><table summary="Pattern modifiers" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Pattern modifier</th><th>Description</th></tr></thead><tbody><tr><td>~A</td><td>all messages</td></tr><tr><td>~b <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message body</td></tr><tr><td>=b <span class="emphasis"><em>STRING</em></span></td><td>messages which contain <span class="emphasis"><em>STRING</em></span> in the message body. If IMAP is enabled, searches for <span class="emphasis"><em>STRING</em></span> on the server, rather than downloading each message and searching it locally.</td></tr><tr><td>~B <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the whole message</td></tr><tr><td>~c <span class="emphasis"><em>EXPR</em></span></td><td>messages carbon-copied to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%c <span class="emphasis"><em>GROUP</em></span></td><td>messages carbon-copied to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~C <span class="emphasis"><em>EXPR</em></span></td><td>messages either to: or cc: <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%C <span class="emphasis"><em>GROUP</em></span></td><td>messages either to: or cc: to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~d [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-sent</span>” in a Date range</td></tr><tr><td>~D</td><td>deleted messages</td></tr><tr><td>~e <span class="emphasis"><em>EXPR</em></span></td><td>messages which contains <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>%e <span class="emphasis"><em>GROUP</em></span></td><td>messages which contain a member of <span class="emphasis"><em>GROUP</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>~E</td><td>expired messages</td></tr><tr><td>~F</td><td>flagged messages</td></tr><tr><td>~f <span class="emphasis"><em>EXPR</em></span></td><td>messages originating from <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%f <span class="emphasis"><em>GROUP</em></span></td><td>messages originating from any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~g</td><td>cryptographically signed messages</td></tr><tr><td>~G</td><td>cryptographically encrypted messages</td></tr><tr><td>~h <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message header</td></tr><tr><td>~H <span class="emphasis"><em>EXPR</em></span></td><td>messages with a spam attribute matching <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~i <span class="emphasis"><em>EXPR</em></span></td><td>messages which match <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Message-ID</span>” field</td></tr><tr><td>~k</td><td>messages which contain PGP key material</td></tr><tr><td>~L <span class="emphasis"><em>EXPR</em></span></td><td>messages either originated or received by <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%L <span class="emphasis"><em>GROUP</em></span></td><td>message either originated or received by any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~l</td><td>messages addressed to a known mailing list</td></tr><tr><td>~m [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~n [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a score in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~N</td><td>new messages</td></tr><tr><td>~O</td><td>old messages</td></tr><tr><td>~p</td><td>messages addressed to you (consults alternates)</td></tr><tr><td>~P</td><td>messages from you (consults alternates)</td></tr><tr><td>~Q</td><td>messages which have been replied to</td></tr><tr><td>~r [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-received</span>” in a Date range</td></tr><tr><td>~R</td><td>read messages</td></tr><tr><td>~s <span class="emphasis"><em>EXPR</em></span></td><td>messages having <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Subject</span>” field.</td></tr><tr><td>~S</td><td>superseded messages</td></tr><tr><td>~t <span class="emphasis"><em>EXPR</em></span></td><td>messages addressed to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~T</td><td>tagged messages</td></tr><tr><td>~u</td><td>messages addressed to a subscribed mailing list</td></tr><tr><td>~U</td><td>unread messages</td></tr><tr><td>~v</td><td>messages part of a collapsed thread.</td></tr><tr><td>~V</td><td>cryptographically verified messages</td></tr><tr><td>~x <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">References</span>” field</td></tr><tr><td>~X [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> attachments *)</td></tr><tr><td>~y <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">X-Label</span>” field</td></tr><tr><td>~z [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a size in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~=</td><td>duplicated messages (see <a class="link" href="reference.html#duplicate-threads" title="3.49. duplicate_threads">$duplicate_threads</a>)</td></tr><tr><td>~$</td><td>unreferenced messages (requires threaded view)</td></tr><tr><td>~(<span class="emphasis"><em>PATTERN</em></span>)</td><td>messages in threads
-containing messages matching <span class="emphasis"><em>PATTERN</em></span>, e.g. all
-threads containing messages from you: ~(~P)</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Where <span class="emphasis"><em>EXPR</em></span> is a
-<a class="link" href="advancedusage.html#regexp" title="1. Regular Expressions">regular expression</a>. Special attention has to be
-made when using regular expressions inside of patterns. Specifically,
-Mutt's parser for these patterns will strip one level of backslash (“<span class="quote">\</span>”),
-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 (“<span class="quote">\\</span>”). You can force mutt to treat <span class="emphasis"><em>EXPR</em></span> as a simple string
-instead of a regular expression by using = instead of ˜ in the
-pattern name. For example, <code class="literal">=b *.*</code> will find all messages that contain
-the literal string “<span class="quote">*.*</span>”. Simple string matches are less powerful than
-regular expressions but can be considerably faster. This is especially
-true for IMAP folders, because string matches can be performed on the
-server instead of by fetching every message. IMAP treats <code class="literal">=h</code> specially:
-it must be of the form "header: substring" and will not partially
-match header names. The substring part may be omitted if you simply
-wish to find messages containing a particular header without regard to
-its value.
-</p><p>
-*) The forms “<span class="quote"><[<span class="emphasis"><em>MAX</em></span>]</span>”, “<span class="quote">>[<span class="emphasis"><em>MIN</em></span>]</span>”,
-“<span class="quote">[<span class="emphasis"><em>MIN</em></span>]-</span>” and “<span class="quote">-[<span class="emphasis"><em>MAX</em></span>]</span>”
-are allowed, too.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="patterns-modifier"></a>2.1. Pattern Modifier</h3></div></div></div><div class="note"><h3 class="title">Note</h3><p>
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
-match if there is at least one match in the whole list. If you want to
-make sure that all elements of that list match, you need to prefix your
-pattern with “<span class="quote">^</span>”.
-This example matches all mails which only has recipients from Germany.
-</p></div><pre class="screen">
-^~C \.de$
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-patterns"></a>2.2. Simple Patterns</h3></div></div></div><p>
-Mutt supports two versions of so called “<span class="quote">simple searches</span>” which are
-issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
-one of these characters: “<span class="quote">˜</span>”, “<span class="quote">=</span>” or “<span class="quote">%</span>”). If the query is
-supposed to contain one of these special characters, they must be escaped
-by prepending a backslash (“<span class="quote">\</span>”).
-</p><p>
-The first type is by checking whether the query string equals
-a keyword case-insensitively from <a class="xref" href="advancedusage.html#tab-simplesearch-keywords" title="Table 4.5. Simple search keywords">Table 4.5, “Simple search keywords”</a>:
-If that is the case, Mutt will use the shown pattern modifier instead.
-If a keyword would conflict with your search keyword, you need to turn
-it into a regular expression to avoid matching the keyword table. For
-example, if you want to find all messages matching “<span class="quote">flag</span>”
-(using <a class="link" href="reference.html#simple-search" title="3.263. simple_search">$simple_search</a>)
-but don't want to match flagged messages, simply search for
-“<span class="quote"><code class="literal">[f]lag</code></span>”.
-</p><div class="table"><a id="tab-simplesearch-keywords"></a><p class="title"><b>Table 4.5. Simple search keywords</b></p><div class="table-contents"><table summary="Simple search keywords" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Keyword</th><th>Pattern modifier</th></tr></thead><tbody><tr><td>all</td><td>~A</td></tr><tr><td>.</td><td>~A</td></tr><tr><td>^</td><td>~A</td></tr><tr><td>del</td><td>~D</td></tr><tr><td>flag</td><td>~F</td></tr><tr><td>new</td><td>~N</td></tr><tr><td>old</td><td>~O</td></tr><tr><td>repl</td><td>~Q</td></tr><tr><td>read</td><td>~R</td></tr><tr><td>tag</td><td>~T</td></tr><tr><td>unread</td><td>~U</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The second type of simple search is to build a complex search
-pattern using <a class="link" href="reference.html#simple-search" title="3.263. simple_search">$simple_search</a>
-as a template. Mutt will insert your query properly quoted and search
-for the composed complex query.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="complex-patterns"></a>2.3. Complex Patterns</h3></div></div></div><p>
-Logical AND is performed by specifying more than one criterion. For
-example:
-</p><pre class="screen">
-~t mutt ~f elkins
-</pre><p>
-would select messages which contain the word “<span class="quote">mutt</span>” in the list of
-recipients <span class="bold"><strong>and</strong></span> that have the word “<span class="quote">elkins</span>” in the “<span class="quote">From</span>” header
-field.
-</p><p>
-Mutt also recognizes the following operators to create more complex search
-patterns:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-! -- logical NOT operator
-</p></li><li><p>
-| -- logical OR operator
-</p></li><li><p>
-() -- logical grouping operator
-</p></li></ul></div><p>
-Here is an example illustrating a complex search pattern. This pattern will
-select all messages which do not contain “<span class="quote">mutt</span>” in the “<span class="quote">To</span>” or “<span class="quote">Cc</span>”
-field and which are from “<span class="quote">elkins</span>”.
-</p><div class="example"><a id="ex-pattern-bool"></a><p class="title"><b>Example 4.1. Using boolean operators in patterns</b></p><div class="example-contents"><pre class="screen">
-!(~t mutt|~c mutt) ~f elkins
-</pre></div></div><br class="example-break" /><p>
-Here is an example using white space in the regular expression (note
-the ' and " delimiters). For this to match, the mail's subject must
-match the “<span class="quote">^Junk +From +Me$</span>” and it must be from either “<span class="quote">Jim +Somebody</span>”
-or “<span class="quote">Ed +SomeoneElse</span>”:
-</p><pre class="screen">
- '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
-</pre><div class="note"><h3 class="title">Note</h3><p>
-If a regular expression contains parenthesis, or a vertical bar
-("|"), you <span class="bold"><strong>must</strong></span> enclose the expression in double or single quotes since
-those characters are also used to separate different parts of Mutt's
-pattern language. For example: <code class="literal">~f "me@(mutt\.org|cs\.hmc\.edu)"</code>
-</p></div><p>
-Without the quotes, the parenthesis wouldn't end.
-This would be separated to two OR'd patterns: <span class="emphasis"><em>˜f me@(mutt\.org</em></span>
-and <span class="emphasis"><em>cs\.hmc\.edu)</em></span>. They are never what you want.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-patterns"></a>2.4. Searching by Date</h3></div></div></div><p>
-Mutt supports two types of dates, <span class="emphasis"><em>absolute</em></span> and <span class="emphasis"><em>relative</em></span>.
-</p><p>
-<span class="bold"><strong>Absolute</strong></span>. Dates <span class="bold"><strong>must</strong></span> be in DD/MM/YY format (month and year are
-optional, defaulting to the current month and year). An example of a valid
-range of dates is:
-</p><pre class="screen">
-Limit to messages matching: ~d 20/1/95-31/10
-</pre><p>
-If you omit the minimum (first) date, and just specify “<span class="quote">-DD/MM/YY</span>”, all
-messages <span class="emphasis"><em>before</em></span> the given date will be selected. If you omit the maximum
-(second) date, and specify “<span class="quote">DD/MM/YY-</span>”, all messages <span class="emphasis"><em>after</em></span> the given
-date will be selected. If you specify a single date with no dash (“<span class="quote">-</span>”),
-only messages sent on the given date will be selected.
-</p><p>
-<span class="bold"><strong>Error Margins</strong></span>. You can add error margins to absolute dates.
-An error margin is a sign (+ or -), followed by a digit, followed by
-one of the units in <a class="xref" href="advancedusage.html#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>. As a special case, you can replace the
-sign by a “<span class="quote">*</span>” character, which is equivalent to giving identical plus and minus error margins.
-</p><div class="table"><a id="tab-date-units"></a><p class="title"><b>Table 4.6. Date units</b></p><div class="table-contents"><table summary="Date units" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Unit</th><th>Description</th></tr></thead><tbody><tr><td>y</td><td>Years</td></tr><tr><td>m</td><td>Months</td></tr><tr><td>w</td><td>Weeks</td></tr><tr><td>d</td><td>Days</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Example: To select any messages two weeks around January 15, 2001,
-you'd use the following pattern:
-</p><pre class="screen">
-Limit to messages matching: ~d 15/1/2001*2w
-</pre><p>
-<span class="bold"><strong>Relative</strong></span>. This type of date is relative to the current date, and may
-be specified as:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-><span class="emphasis"><em>offset</em></span> (messages older than <span class="emphasis"><em>offset</em></span> units)
-</p></li><li><p>
-<<span class="emphasis"><em>offset</em></span> (messages newer than <span class="emphasis"><em>offset</em></span> units)
-</p></li><li><p>
-=<span class="emphasis"><em>offset</em></span> (messages exactly <span class="emphasis"><em>offset</em></span> units old)
-</p></li></ul></div><p>
-<span class="emphasis"><em>offset</em></span> is specified as a positive number with one of the units from <a class="xref" href="advancedusage.html#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>.
-</p><p>
-Example: to select messages less than 1 month old, you would use
-</p><pre class="screen">
-Limit to messages matching: ~d <1m
-</pre><div class="note"><h3 class="title">Note</h3><p>
-All dates used when searching are relative to the
-<span class="bold"><strong>local</strong></span> time zone, so unless you change the setting of your <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> to include a
-<code class="literal">%[...]</code> format, these are <span class="bold"><strong>not</strong></span> the dates shown
-in the main index.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tags"></a>3. Using Tags</h2></div></div></div><p>
-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 <code class="literal"><tag-pattern></code> function, which is bound to
-“<span class="quote">shift-T</span>” by default. Or you can select individual messages by
-hand using the <code class="literal"><tag-message></code> function, which is bound to “<span class="quote">t</span>” by
-default. See <a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> for Mutt's pattern
-matching syntax.
-</p><p>
-Once you have tagged the desired messages, you can use the
-“<span class="quote">tag-prefix</span>” operator, which is the “<span class="quote">;</span>” (semicolon) key by default.
-When the “<span class="quote">tag-prefix</span>” operator is used, the <span class="bold"><strong>next</strong></span> operation will
-be applied to all tagged messages if that operation can be used in that
-manner. If the <a class="link" href="reference.html#auto-tag" title="3.18. auto_tag">$auto_tag</a>
-variable is set, the next operation applies to the tagged messages
-automatically, without requiring the “<span class="quote">tag-prefix</span>”.
-</p><p>
-In <a class="link" href="configuration.html#macro" title="8. Keyboard macros">macros</a> or <a class="link" href="configuration.html#push" title="22. Adding key sequences to the keyboard buffer">push</a> commands,
-you can use the “<span class="quote">tag-prefix-cond</span>” operator. If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the “<span class="quote">end-cond</span>”
-operator; after this operator the rest of the macro will be executed as
-normal.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="hooks"></a>4. Using Hooks</h2></div></div></div><p>
-A <span class="emphasis"><em>hook</em></span> is a concept found in many other programs 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 world, a <span class="emphasis"><em>hook</em></span>
-consists of a <a class="link" href="advancedusage.html#regexp" title="1. Regular Expressions">regular expression</a> or
-<a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">pattern</a> along with a
-configuration option/command. See
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="link" href="configuration.html#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#message-hook" title="20. Change settings before formatting a message">message-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
-</p></li><li><p>
-<a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a>
-</p></li></ul></div><p>
-
-for specific details on each type of <span class="emphasis"><em>hook</em></span> available.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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:
-</p></div><div class="example"><a id="ex-send-hook-my-hdr"></a><p class="title"><b>Example 4.2. Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></b></p><div class="example-contents"><pre class="screen">
-send-hook . 'unmy_hdr From:'
-send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-</pre></div></div><br class="example-break" /><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pattern-hook"></a>4.1. Message Matching in Hooks</h3></div></div></div><p>
-Hooks that act upon messages (<code class="literal">message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook</code>) are evaluated in a
-slightly different manner. For the other
-types of hooks, a <a class="link" href="advancedusage.html#regexp" title="1. Regular Expressions">regular expression</a> 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.
-</p><p>
-Mutt allows the use of the <a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">search pattern</a>
-language for matching messages in hook commands. This works in
-exactly the same way as it would when <span class="emphasis"><em>limiting</em></span> or
-<span class="emphasis"><em>searching</em></span> 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.).
-</p><p>
-For example, if you wanted to set your return address based upon sending
-mail to a specific address, you could do something like:
-</p><pre class="screen">
-send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
-</pre><p>
-which would execute the given command when sending mail to
-<span class="emphasis"><em>me@cs.hmc.edu</em></span>.
-</p><p>
-However, it is not required that you write the pattern to match using the
-full searching language. You can still specify a simple <span class="emphasis"><em>regular
-expression</em></span> like the other hooks, in which case Mutt will translate your
-pattern into the full language, using the translation specified by the
-<a class="link" href="reference.html#default-hook" title="3.41. default_hook">$default_hook</a> variable. The
-pattern is translated at the time the hook is declared, so the value of
-<a class="link" href="reference.html#default-hook" title="3.41. default_hook">$default_hook</a> that is in effect
-at that time will be used.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="query"></a>5. External Address Queries</h2></div></div></div><p>
-Mutt 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 <a class="link" href="reference.html#query-command" title="3.231. query_command">$query_command</a> variable, you specify the wrapper
-command to use. For example:
-</p><pre class="screen">
-set query_command = "mutt_ldap_query.pl '%s'"
-</pre><p>
-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 then
-some other optional information. On error, or if there are no matching
-addresses, return a non-zero exit code and a one line error message.
-</p><p>
-An example multiple response output:
-</p><pre class="screen">
-Searching database ... 20 entries ... 3 matching:
-me@cs.hmc.edu Michael Elkins mutt dude
-blong@fiction.net Brandon Long mutt and more
-roessler@does-not-exist.org Thomas Roessler mutt pgp
-</pre><p>
-There are two mechanisms for accessing the query function of mutt. One
-is to do a query from the index menu using the <code class="literal"><query></code> 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 addresses
-to mail, start a new query, or have a new query appended to the current
-responses.
-</p><p>
-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 <code class="literal"><complete-query></code> 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 query
-menu. At the query menu, you can select one or more addresses to be
-added to the prompt.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailbox-formats"></a>6. Mailbox Formats</h2></div></div></div><p>
-Mutt 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 new
-mailboxes, Mutt uses the default specified with the <a class="link" href="reference.html#mbox-type" title="3.117. mbox_type">$mbox_type</a> variable.
-</p><p>
-<span class="bold"><strong>mbox</strong></span>. 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:
-</p><pre class="screen">
-From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-</pre><p>
-to denote the start of a new message (this is often referred to as the
-“<span class="quote">From_</span>” line).
-</p><p>
-<span class="bold"><strong>MMDF</strong></span>. This is a variant of the <span class="emphasis"><em>mbox</em></span> format. Each message is
-surrounded by lines containing “<span class="quote">^A^A^A^A</span>” (four control-A's).
-</p><p>
-<span class="bold"><strong>MH</strong></span>. A radical departure from <span class="emphasis"><em>mbox</em></span> and <span class="emphasis"><em>MMDF</em></span>, 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 displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
-detects this type of mailbox by looking for either <code class="literal">.mh_sequences</code>
-or <code class="literal">.xmhcache</code> (needed to distinguish normal directories from MH
-mailboxes).
-</p><p>
-<span class="bold"><strong>Maildir</strong></span>. The newest of the mailbox formats, used by the Qmail MTA (a
-replacement for sendmail). Similar to <span class="emphasis"><em>MH</em></span>, except that it adds three
-subdirectories of the mailbox: <span class="emphasis"><em>tmp</em></span>, <span class="emphasis"><em>new</em></span> and <span class="emphasis"><em>cur</em></span>. Filenames
-for the messages are chosen in such a way they are unique, even when two
-programs are writing the mailbox over NFS, which means that no file locking
-is needed.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="shortcuts"></a>7. Mailbox Shortcuts</h2></div></div></div><p>
-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.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-! -- refers to your <a class="link" href="reference.html#spoolfile" title="3.276. spoolfile">$spoolfile</a> (incoming) mailbox
-</p></li><li><p>
-> -- refers to your <a class="link" href="reference.html#mbox" title="3.116. mbox">$mbox</a> file
-</p></li><li><p>
-< -- refers to your <a class="link" href="reference.html#record" title="3.239. record">$record</a> file
-</p></li><li><p>
-^ -- refers to the current mailbox
-</p></li><li><p>
-- or !! -- refers to the file you've last visited
-</p></li><li><p>
-˜ -- refers to your home directory
-</p></li><li><p>
-= or + -- refers to your <a class="link" href="reference.html#folder" title="3.58. folder">$folder</a> directory
-</p></li><li><p>
-@<span class="emphasis"><em>alias</em></span> -- refers to the <a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">default save folder</a> as determined by the address of the alias
-</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-lists"></a>8. Handling Mailing Lists</h2></div></div></div><p>
-Mutt 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 <a class="link" href="configuration.html#lists" title="12. Mailing lists">lists and subscribe</a> commands in your muttrc.
-</p><p>
-Now that Mutt 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 <span class="emphasis"><em>index</em></span> menu display. This is useful to distinguish between
-personal and list mail in the same mailbox. In the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable, the escape “<span class="quote">%L</span>”
-will return the string “<span class="quote">To <list></span>” when “<span class="quote">list</span>” appears in the
-“<span class="quote">To</span>” field, and “<span class="quote">Cc <list></span>” when it appears in the “<span class="quote">Cc</span>”
-field (otherwise it returns the name of the author).
-</p><p>
-Often times the “<span class="quote">To</span>” and “<span class="quote">Cc</span>” fields in mailing list messages
-tend to get quite large. Most people do not bother to remove the
-author of the message they reply to from the list, resulting in
-two or more copies being sent to that person. The <code class="literal"><list-reply></code>
-function, which by default is bound to “<span class="quote">L</span>” in the <span class="emphasis"><em>index</em></span> menu
-and <span class="emphasis"><em>pager</em></span>, helps reduce the clutter by only replying to the
-known mailing list addresses instead of all recipients (except as
-specified by <code class="literal">Mail-Followup-To</code>, see below).
-</p><p>
-Mutt also supports the <code class="literal">Mail-Followup-To</code> header. When you send
-a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the <a class="link" href="reference.html#followup-to" title="3.60. followup_to">$followup_to</a> 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 “<span class="quote">followups</span>”) 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.
-</p><p>
-Conversely, when group-replying or list-replying to a message which
-has a <code class="literal">Mail-Followup-To</code> header, mutt will respect this header if
-the <a class="link" href="reference.html#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a> 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 <code class="literal">Mail-Followup-To</code>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-When header editing is enabled, you can create a
-<code class="literal">Mail-Followup-To</code> header manually. Mutt will only auto-generate
-this header if it doesn't exist when you send the message.
-</p></div><p>
-The other method some mailing list admins use is to generate a
-“<span class="quote">Reply-To</span>” 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 “<span class="quote">Reply-To</span>”
-field. Mutt uses the <a class="link" href="reference.html#reply-to" title="3.242. reply_to">$reply_to</a>
-variable to help decide which address to use. If set to <span class="emphasis"><em>ask-yes</em></span> or
-<span class="emphasis"><em>ask-no</em></span>, you will be
-prompted as to whether or not you would like to use the address given in
-the “<span class="quote">Reply-To</span>” field, or reply directly to the address given in the
-“<span class="quote">From</span>” field. When set to <span class="emphasis"><em>yes</em></span>, the “<span class="quote">Reply-To</span>” field will be used when
-present.
-</p><p>
-The “<span class="quote">X-Label:</span>” header field can be used to further identify mailing
-lists or list subject matter (or just to annotate messages
-individually). The <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable's “<span class="quote">%y</span>” and
-“<span class="quote">%Y</span>” escapes can be used to expand “<span class="quote">X-Label:</span>” fields in the
-index, and Mutt's pattern-matcher can match regular expressions to
-“<span class="quote">X-Label:</span>” fields with the “<span class="quote">˜y</span>” selector. “<span class="quote">X-Label:</span>” is not a
-standard message header field, but it can easily be inserted by procmail
-and other mail filtering agents.
-</p><p>
-Lastly, Mutt has the ability to <a class="link" href="reference.html#sort" title="3.270. sort">sort</a> the mailbox into
-<a class="link" href="gettingstarted.html#threads" title="4.3. Threaded Mode">threads</a>. 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 dealing
-with large volume mailing lists easier because you can easily delete
-uninteresting threads and quickly find topics of value.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="handling-folders"></a>9. Handling multiple folders</h2></div></div></div><p>
-Mutt supports setups with multiple folders, allowing all of them to
-be monitored for new mail (see <a class="xref" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">Section 14, “Monitoring incoming mail”</a> for details).
-</p><p>
-When in the index menu and being idle (also see
-<a class="link" href="reference.html#timeout" title="3.287. timeout">$timeout</a>), Mutt periodically checks
-for new mail in all folders which have been configured via the
-<code class="literal">mailboxes</code> command. The interval depends on the folder
-type: for local/IMAP folders it consults
-<a class="link" href="reference.html#mail-check" title="3.105. mail_check">$mail_check</a> and
-<a class="link" href="reference.html#pop-checkinterval" title="3.215. pop_checkinterval">$pop_checkinterval</a>
-for POP folders.
-</p><p>
-Outside the index menu the directory browser supports checking
-for new mail using the <code class="literal"><check-new></code> function which is
-unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the <code class="literal">mailboxes</code> command,
-and indicate which contain new messages. Mutt will automatically enter this
-mode when invoked from the command line with the <code class="literal">-y</code> option.
-</p><p>
-For the pager, index and directory browser menus, Mutt contains the
-<code class="literal"><buffy-list></code> function (bound to “<span class="quote">.</span>” by default)
-which will print a list of folders with new mail in the command line at
-the bottom of the screen.
-</p><p>
-For the index, by default Mutt displays the number of mailboxes with new
-mail in the status bar, please refer to the
-<a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>
-variable for details.
-</p><p>
-When changing folders, Mutt fills the prompt with the first folder from
-the mailboxes list containing new mail (if any), pressing
-<span class="emphasis"><em>space</em></span> will cycle through folders with new mail.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing-threads"></a>10. Editing threads</h2></div></div></div><p>
-Mutt 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.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="link-threads"></a>10.1. Linking threads</h3></div></div></div><p>
-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 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 <code class="literal"><link-threads></code> function (bound to & by default). The
-reply will then be connected to this "parent" message.
-</p><p>
-You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="break-threads"></a>10.2. Breaking threads</h3></div></div></div><p>
-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 <code class="literal"><break-thread></code> function (bound
-by default to #), which will turn the subthread starting from the
-current message into a whole different thread.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="dsn"></a>11. Delivery Status Notification (DSN) Support</h2></div></div></div><p>
-RFC1894 defines a set of MIME content types for relaying information
-about the status of electronic mail messages. These can be thought of as
-“<span class="quote">return receipts.</span>”
-</p><p>
-To support DSN, there are two variables. <a class="link" href="reference.html#dsn-notify" title="3.47. dsn_notify">$dsn_notify</a> is used to request receipts for
-different results (such as failed message, message delivered, etc.).
-<a class="link" href="reference.html#dsn-return" title="3.48. dsn_return">$dsn_return</a> requests how much
-of your message should be returned with the receipt (headers or full
-message).
-</p><p>
-When using <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a> for mail
-delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA
-supporting DSN command line options compatible to Sendmail: The -N and -R
-options can be used by the mail client to make requests as to what type of
-status messages should be returned. Please consider your MTA documentation
-whether DSN is supported.
-</p><p>
-For SMTP delivery using <a class="link" href="reference.html#smtp-url" title="3.269. smtp_url">$smtp_url</a>, it depends on the
-capabilities announced by the server whether mutt will attempt to
-request DSN or not.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="urlview"></a>12. Start a WWW Browser on URLs</h2></div></div></div><p>
-If a message contains URLs, 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
-<a class="ulink" href="ftp://ftp.mutt.org/mutt/contrib/" target="_top">ftp://ftp.mutt.org/mutt/contrib/</a>
-and the configuration commands:
-</p><pre class="screen">
-macro index \cb |urlview\n
-macro pager \cb |urlview\n
-</pre></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="configuration.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="mimesupport.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. Mutt's MIME Support</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. Configuration</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="gettingstarted.html" title="Chapter 2. Getting Started" /><link rel="next" href="advancedusage.html" title="Chapter 4. Advanced Usage" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="gettingstarted.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="advancedusage.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="configuration"></a>Chapter 3. Configuration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="configuration.html#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="configuration.html#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="configuration.html#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="configuration.html#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="configuration.html#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="configuration.html#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="configuration.html#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="configuration.html#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="configuration.html#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="configuration.html#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="configuration.html#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="configuration.html#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="configuration.html#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="configuration.html#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="configuration.html#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="configuration.html#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="configuration.html#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="configuration.html#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="configuration.html#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="configuration.html#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="configuration.html#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="configuration.html#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="configuration.html#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="configuration.html#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="configuration.html#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="configuration.html#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="configuration.html#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="configuration.html#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="configuration.html#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="configuration.html#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="configuration.html#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="configuration.html#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="configuration.html#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="configuration.html#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="configuration-files"></a>1. Location of initialization files</h2></div></div></div><p>
-While the default configuration (or “<span class="quote">preferences</span>”) make Mutt
-usable right out of the box, it is often desirable to tailor Mutt to
-suit your own tastes. When Mutt is first invoked, it will attempt to
-read the “<span class="quote">system</span>” configuration file (defaults set by your local
-system administrator), unless the “<span class="quote">-n</span>” <a class="link" href="reference.html#commandline" title="1. Command line options">command line</a> option is specified. This file is typically
-<code class="literal">/usr/local/share/mutt/Muttrc</code> or <code class="literal">/etc/Muttrc</code>. Mutt
-will next look for a file named <code class="literal">.muttrc</code> in your home
-directory. If this file does not exist and your home directory has
-a subdirectory named <code class="literal">.mutt</code>, mutt try to load a file named
-<code class="literal">.mutt/muttrc</code>.
-</p><p>
-<code class="literal">.muttrc</code> is the file where you will usually place your <a class="link" href="reference.html#commands" title="2. Configuration Commands">commands</a> to configure Mutt.
-</p><p>
-In addition, mutt supports version specific configuration files that are
-parsed instead of the default files as explained above. For instance, if
-your system has a <code class="literal">Muttrc-0.88</code> file in the system configuration
-directory, and you are running version 0.88 of mutt, this file will be
-sourced instead of the <code class="literal">Muttrc</code> file. The same is true of the user
-configuration file, if you have a file <code class="literal">.muttrc-0.88.6</code> in your home
-directory, when you run mutt version 0.88.6, it will source this file
-instead of the default <code class="literal">.muttrc</code> file. The version number is the
-same which is visible using the “<span class="quote">-v</span>” <a class="link" href="reference.html#commandline" title="1. Command line options">command line</a> switch or using the <code class="literal">show-version</code> key (default:
-V) from the index menu.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttrc-syntax"></a>2. Syntax of Initialization Files</h2></div></div></div><p>
-An initialization file consists of a series of <a class="link" href="reference.html#commands" title="2. Configuration Commands">commands</a>. Each line of the file may contain one or more commands.
-When multiple commands are used, they must be separated by a semicolon
-(;).
-</p><div class="example"><a id="ex-rc-multiple-cmds"></a><p class="title"><b>Example 3.1. Multiple configuration commands per line</b></p><div class="example-contents"><pre class="screen">
-set realname='Mutt user' ; ignore x-
-</pre></div></div><br class="example-break" /><p>
-The hash mark, or pound sign
-(“<span class="quote">#</span>”), is used as a “<span class="quote">comment</span>” 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,
-</p><div class="example"><a id="ex-ec-comment"></a><p class="title"><b>Example 3.2. Commenting configuration files</b></p><div class="example-contents"><pre class="screen">
-my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
-</pre></div></div><br class="example-break" /><p>
-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, backticks are evaluated inside of double
-quotes, but <span class="bold"><strong>not</strong></span> for single quotes.
-</p><p>
-\ quotes the next character, just as in shells such as bash and zsh.
-For example, if want to put quotes “<span class="quote">"</span>” inside of a string, you can use
-“<span class="quote">\</span>” to force the next character to be a literal instead of interpreted
-character.
-</p><div class="example"><a id="ex-rc-quote"></a><p class="title"><b>Example 3.3. Escaping quotes in congfiguration files</b></p><div class="example-contents"><pre class="screen">
-set realname="Michael \"MuttDude\" Elkins"
-</pre></div></div><br class="example-break" /><p>
-“<span class="quote">\\</span>” means to insert a literal “<span class="quote">\</span>” into the line.
-“<span class="quote">\n</span>” and “<span class="quote">\r</span>” have their usual C meanings of linefeed and
-carriage-return, respectively.
-</p><p>
-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.
-</p><p>
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command in
-backticks (``). For example,
-</p><div class="example"><a id="ex-rc-backtick"></a><p class="title"><b>Example 3.4. Using external command's output in configuration files</b></p><div class="example-contents"><pre class="screen">
-my_hdr X-Operating-System: `uname -a`
-</pre></div></div><br class="example-break" /><p>
-The output of the Unix command “<span class="quote">uname -a</span>” will be substituted before the
-line is parsed.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Since initialization files are line oriented, only
-the first line of output from the Unix command will be substituted.
-</p></div><p>
-Both environment variables and mutt variables can be accessed by
-prepending “<span class="quote">$</span>” to the name of the variable. For example,
-</p><div class="example"><a id="ex-rc-env"></a><p class="title"><b>Example 3.5. Using environment variables in configuration files</b></p><div class="example-contents"><pre class="screen">
-set record=+sent_on_$HOSTNAME
-</pre></div></div><br class="example-break" /><p>
-will cause mutt to save outgoing messages to a folder named
-“<span class="quote">sent_on_kremvax</span>” if the environment variable HOSTNAME is set to
-“<span class="quote">kremvax.</span>” (See <a class="link" href="reference.html#record" title="3.239. record">$record</a> for
-details.)
-</p><p>
-Mutt expands the variable when it is assigned, not when it is used. If
-the value of a variable on the right-hand side of an assignment
-changes after the assignment, the variable on the left-hand side will
-not be affected.
-</p><p>
-The commands understood by mutt are explained in the next paragraphs.
-For a complete list, see the <a class="link" href="reference.html#commands" title="2. Configuration Commands">command reference</a>.
-</p><p>
-All configuration files are expected to be in the current locale as
-specified by the <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> variable
-which doesn't have a default value since it's determined by Mutt at startup.
-If a configuration file is not encoded in the same character set the
-<a class="link" href="reference.html#config-charset" title="3.30. config_charset">$config_charset</a>
-variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
-</p><p>
-This mechanism should be avoided if possible as it has the
-following implications:
-</p><div class="itemizedlist"><ul type="disc"><li><p>These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.</p></li><li><p>If $config_charset is set, it should be set
-in each configuration file because the value is global and <span class="emphasis"><em>not</em></span>
-per configuration file.</p></li><li><p>Because Mutt first recodes a line before it attempts to parse it,
-a conversion introducing question marks or other characters as
-part of errors (unconvertable characters, transliteration) may introduce syntax
-errors or silently change the meaning of certain tokens (e.g. inserting
-question marks into regular expressions).</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="addrgroup"></a>3. Address groups</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">group</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div><div class="cmdsynopsis"><p><code class="command">ungroup</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div><p>
-<code class="literal">group</code> is used to directly add either addresses or
-regular expressions to the specified group or groups. The different
-categories of arguments to the <code class="literal">group</code> command can be
-in any order. The flags <code class="literal">-rx</code> and
-<code class="literal">-addr</code> specify what the following strings (that cannot
-begin with a hyphen) should be interpreted as: either a regular
-expression or an email address, respectively.
-</p><p>
-These address groups can also be created implicitly by the
-<a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">alias</a>, <a class="link" href="configuration.html#lists" title="12. Mailing lists">lists</a>,
-<a class="link" href="configuration.html#lists" title="12. Mailing lists">subscribe</a> and
-<a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a> commands by specifying the
-optional <code class="literal">-group</code> option.
-</p><p>
-Once defined, these address groups can be used in
-<a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> to search for and limit the
-display to messages matching a group.
-</p><p>
-<code class="literal">ungroup</code> is used to remove addresses or regular
-expressions from the specified group or groups. The syntax is similar to
-the <code class="literal">group</code> command, however the special character
-<code class="literal">*</code> can be used to empty a group of all of its
-contents.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alias"></a>4. Defining/Using aliases</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alias</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>address</code></em>
- [
-<em class="replaceable"><code>address</code></em>
-...]</p></div><p>
-It's usually very cumbersome to remember or type out the address of someone
-you are communicating with. Mutt allows you to create “<span class="quote">aliases</span>” which map
-a short string to a full address.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you want to create an alias for more than
-one address, you <span class="bold"><strong>must</strong></span> separate the addresses with a comma (“<span class="quote">,</span>”).
-</p></div><p>
-The optional <code class="literal">-group</code> argument to
-<code class="literal">alias</code> causes the aliased address(es) to be added to
-the named <span class="emphasis"><em>group</em></span>.
-</p><p>
-To remove an alias or aliases (“<span class="quote">*</span>” means all aliases):
-</p><div class="cmdsynopsis"><p><code class="command">unalias</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>key</code></em>
-... }</p></div><pre class="screen">
-alias muttdude me@cs.hmc.edu (Michael Elkins)
-alias theguys manny, moe, jack
-</pre><p>
-Unlike other mailers, Mutt doesn't require aliases to be defined
-in a special file. The <code class="literal">alias</code> command can appear anywhere in
-a configuration file, as long as this file is <a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">sourced</a>. Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
-</p><p>
-On the other hand, the <a class="link" href="gettingstarted.html#create-alias"><code class="literal"><create-alias></code></a>
-function can use only one file, the one pointed to by the <a class="link" href="reference.html#alias-file" title="3.3. alias_file">$alias_file</a> variable (which is
-<code class="literal">˜/.muttrc</code> by default). This file is not special either,
-in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly <a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a> this file too.
-</p><p>
-For example:
-</p><div class="example"><a id="ex-alias-external"></a><p class="title"><b>Example 3.6. Configuring external alias files</b></p><div class="example-contents"><pre class="screen">
-source /usr/local/share/Mutt.aliases
-source ~/.mail_aliases
-set alias_file=~/.mail_aliases
-</pre></div></div><br class="example-break" /><p>
-To use aliases, you merely use the alias at any place in mutt where mutt
-prompts for addresses, such as the <span class="emphasis"><em>To:</em></span> or <span class="emphasis"><em>Cc:</em></span> prompt. You can
-also enter aliases in your editor at the appropriate headers if you have the
-<a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable set.
-</p><p>
-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.
-</p><p>
-In the alias menu, you can select as many aliases as you want with the
-<code class="literal">select-entry</code> key (default: <Return>), and use the
-<span class="emphasis"><em>exit</em></span> key (default: q) to return to the address prompt.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="bind"></a>5. Changing the default key bindings</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">bind</code>
-<em class="replaceable"><code>map</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>function</code></em>
- </p></div><p>
-This command allows you to change the default key bindings (operation
-invoked when pressing a key).
-</p><p>
-<span class="emphasis"><em>map</em></span> specifies in which menu the binding belongs. Multiple maps may
-be specified by separating them with commas (no additional whitespace is
-allowed). The currently defined maps are:
-</p><a id="maps"></a><div class="variablelist"><dl><dt><span class="term">generic</span></dt><dd><p>
-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 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.
-</p></dd><dt><span class="term">alias</span></dt><dd><p>
-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).
-</p></dd><dt><span class="term">attach</span></dt><dd><p>
-The attachment menu is used to access the attachments on received messages.
-</p></dd><dt><span class="term">browser</span></dt><dd><p>
-The browser is used for both browsing the local directory structure, and for
-listing all of your incoming mailboxes.
-</p></dd><dt><span class="term">editor</span></dt><dd><p>
-The editor is the line-based editor the user enters text data.
-</p></dd><dt><span class="term">index</span></dt><dd><p>
-The index is the list of messages contained in a mailbox.
-</p></dd><dt><span class="term">compose</span></dt><dd><p>
-The compose menu is the screen used when sending a new message.
-</p></dd><dt><span class="term">pager</span></dt><dd><p>
-The pager is the mode used to display message/attachment data, and help
-listings.
-</p></dd><dt><span class="term">pgp</span></dt><dd><p>
-The pgp menu is used to select the OpenPGP keys used to encrypt outgoing
-messages.
-</p></dd><dt><span class="term">smime</span></dt><dd><p>
-The smime menu is used to select the OpenSSL certificates used to encrypt outgoing
-messages.
-</p></dd><dt><span class="term">postpone</span></dt><dd><p>
-The postpone menu is similar to the index menu, except is used when
-recalling a message the user was composing, but saved until later.
-</p></dd><dt><span class="term">query</span></dt><dd><p>
-The query menu is the browser for results returned by
-<a class="link" href="reference.html#query-command" title="3.231. query_command">$query_command</a>.
-</p></dd><dt><span class="term">mix</span></dt><dd><p>
-The mixmaster screen is used to select remailer options for outgoing
-messages (if Mutt is compiled with Mixmaster support).
-</p></dd></dl></div><p>
-<span class="emphasis"><em>key</em></span> is the key (or key sequence) you wish to bind. To specify a
-control character, use the sequence <span class="emphasis"><em>\Cx</em></span>, where <span class="emphasis"><em>x</em></span> is the
-letter of the control character (for example, to specify control-A use
-“<span class="quote">\Ca</span>”). Note that the case of <span class="emphasis"><em>x</em></span> as well as <span class="emphasis"><em>\C</em></span> is
-ignored, so that <span class="emphasis"><em>\CA</em></span>, <span class="emphasis"><em>\Ca</em></span>, <span class="emphasis"><em>\cA</em></span> and <span class="emphasis"><em>\ca</em></span> are all
-equivalent. An alternative form is to specify the key as a three digit
-octal number prefixed with a “<span class="quote">\</span>” (for example <span class="emphasis"><em>\177</em></span> is
-equivalent to <span class="emphasis"><em>\c?</em></span>). In addition, <span class="emphasis"><em>key</em></span> may
-be a symbolic name as shown in <a class="xref" href="configuration.html#tab-key-names" title="Table 3.1. Symbolic key names">Table 3.1, “Symbolic key names”</a>.
-</p><div class="table"><a id="tab-key-names"></a><p class="title"><b>Table 3.1. Symbolic key names</b></p><div class="table-contents"><table summary="Symbolic key names" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Symbolic name</th><th>Meaning</th></tr></thead><tbody><tr><td>\t</td><td>tab</td></tr><tr><td><tab></td><td>tab</td></tr><tr><td><backtab></td><td>backtab / shift-tab</td></tr><tr><td>\r</td><td>carriage return</td></tr><tr><td>\n</td><td>newline</td></tr><tr><td>\e</td><td>escape</td></tr><tr><td><esc></td><td>escape</td></tr><tr><td><up></td><td>up arrow</td></tr><tr><td><down></td><td>down arrow</td></tr><tr><td><left></td><td>left arrow</td></tr><tr><td><right></td><td>right arrow</td></tr><tr><td><pageup></td><td>Page Up</td></tr><tr><td><pagedown></td><td>Page Down</td></tr><tr><td><backspace></td><td>Backspace</td></tr><tr><td><delete></td><td>Delete</td></tr><tr><td><insert></td><td>Insert</td></tr><tr><td><enter></td><td>Enter</td></tr><tr><td><return></td><td>Return</td></tr><tr><td><home></td><td>Home</td></tr><tr><td><end></td><td>End</td></tr><tr><td><space></td><td>Space bar</td></tr><tr><td><f1></td><td>function key 1</td></tr><tr><td><f10></td><td>function key 10</td></tr></tbody></table></div></div><br class="table-break" /><p>
-<span class="emphasis"><em>key</em></span> does not need to be enclosed in quotes unless it contains a
-space (“<span class="quote"> </span>”) or semi-colon (“<span class="quote">;</span>”).
-</p><p>
-<span class="emphasis"><em>function</em></span> specifies which action to take when <span class="emphasis"><em>key</em></span> is pressed.
-For a complete list of functions, see the <a class="link" href="reference.html#functions" title="4. Functions">reference</a>. The special function <code class="literal"><noop></code> unbinds the specified key
-sequence.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="charset-hook"></a>6. Defining aliases for character sets </h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">charset-hook</code>
-<em class="replaceable"><code>alias</code></em>
-
-<em class="replaceable"><code>charset</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">iconv-hook</code>
-<em class="replaceable"><code>charset</code></em>
-
-<em class="replaceable"><code>local-charset</code></em>
- </p></div><p>
-The <code class="literal">charset-hook</code> 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.
-</p><p>
-The <code class="literal">iconv-hook</code> 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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="folder-hook"></a>7. Setting variables based upon mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">folder-hook</code>
-<em class="replaceable"><code>[!]regexp</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-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. <span class="emphasis"><em>regexp</em></span> is a regular expression specifying
-in which mailboxes to execute <span class="emphasis"><em>command</em></span> before loading. If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you use the “<span class="quote">!</span>” shortcut for <a class="link" href="reference.html#spoolfile" title="3.276. spoolfile">$spoolfile</a> at the beginning of the pattern, you must place it
-inside of double or single quotes in order to distinguish it from the
-logical <span class="emphasis"><em>not</em></span> operator for the expression.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-Settings are <span class="emphasis"><em>not</em></span> restored when you leave the mailbox.
-For example, a command action to perform is to change the sorting method
-based upon the mailbox being read:
-</p></div><pre class="screen">
-folder-hook mutt set sort=threads
-</pre><p>
-However, the sorting method is not restored to its previous value when
-reading a different mailbox. To specify a <span class="emphasis"><em>default</em></span> command, use the
-pattern “<span class="quote">.</span>” before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
-The following example will set the <a class="link" href="reference.html#sort" title="3.270. sort">sort</a> variable
-to <code class="literal">date-sent</code> for all folders but to <code class="literal">threads</code>
-for all folders containing “<span class="quote">mutt</span>” in their name.
-</p><div class="example"><a id="ex-folder-sorting"></a><p class="title"><b>Example 3.7. Setting sort method based on mailbox name</b></p><div class="example-contents"><pre class="screen">
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="macro"></a>8. Keyboard macros</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">macro</code>
-<em class="replaceable"><code>menu</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>sequence</code></em>
- [
-<em class="replaceable"><code>description</code></em>
-]</p></div><p>
-Macros are useful when you would like a single key to perform a series of
-actions. When you press <span class="emphasis"><em>key</em></span> in menu <span class="emphasis"><em>menu</em></span>, Mutt will behave as if
-you had typed <span class="emphasis"><em>sequence</em></span>. So if you have a common sequence of commands
-you type, you can create a macro to execute those commands with a single
-key or fewer keys.
-</p><p>
-<span class="emphasis"><em>menu</em></span> is the <a class="link" href="configuration.html#maps">map</a> which the macro will be bound in.
-Multiple maps may be specified by separating multiple menu arguments by
-commas. Whitespace may not be used in between the menu arguments and the
-commas separating them.
-</p><p>
-<span class="emphasis"><em>key</em></span> and <span class="emphasis"><em>sequence</em></span> are expanded by the same rules as the
-<a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">key bindings</a> with some additions. The
-first is that control characters in <span class="emphasis"><em>sequence</em></span> can also be specified
-as <span class="emphasis"><em>^x</em></span>. In order to get a caret (“<span class="quote">^</span>”) you need to use
-<span class="emphasis"><em>^^</em></span>. Secondly, to specify a certain key such as <span class="emphasis"><em>up</em></span>
-or to invoke a function directly, you can use the format
-<span class="emphasis"><em><key name></em></span> and <span class="emphasis"><em><function name></em></span>. For a listing of key
-names see the section on <a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">key bindings</a>. Functions
-are listed in the <a class="link" href="reference.html#functions" title="4. Functions">reference</a>.
-</p><p>
-The advantage with using function names directly is that the macros will
-work regardless of the current key bindings, so they are not dependent on
-the user having particular key definitions. This makes them more robust
-and portable, and also facilitates defining of macros in files used by more
-than one user (e.g., the system Muttrc).
-</p><p>
-Optionally you can specify a descriptive text after <span class="emphasis"><em>sequence</em></span>,
-which is shown in the help screens.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Macro definitions (if any) listed in the help screen(s), are
-silently truncated at the screen width, and are not wrapped.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="color"></a>9. Using color and mono video attributes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">color</code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">color</code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">color</code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">uncolor</code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-If your terminal supports color, you can spice up Mutt by creating your own
-color scheme. To define the color of an object (type of information), you
-must specify both a foreground color <span class="bold"><strong>and</strong></span> a background color (it is not
-possible to only specify one or the other).
-</p><p>
-<span class="emphasis"><em>header</em></span> and <span class="emphasis"><em>body</em></span> match <span class="emphasis"><em>regexp</em></span>
-in the header/body of a message, <span class="emphasis"><em>index</em></span> matches <span class="emphasis"><em>pattern</em></span>
-(see <a class="xref" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">Section 2, “Patterns: Searching, Limiting and Tagging”</a>) in the message index.
-</p><p>
-<span class="emphasis"><em>object</em></span> can be one of:
-</p><div class="itemizedlist"><ul type="disc"><li><p>attachment</p></li><li><p>bold (hiliting bold patterns in the body of messages)</p></li><li><p>error (error messages printed by Mutt)</p></li><li><p>hdrdefault (default color of the message header in the pager)</p></li><li><p>indicator (arrow or bar used to indicate the current item in a menu)</p></li><li><p>markers (the “<span class="quote">+</span>” markers at the beginning of wrapped lines in the pager)</p></li><li><p>message (informational messages)</p></li><li><p>normal</p></li><li><p>quoted (text matching <a class="link" href="reference.html#quote-regexp" title="3.234. quote_regexp">$quote_regexp</a> in the body of a message)</p></li><li><p>quoted1, quoted2, ..., quoted<span class="bold"><strong>N</strong></span> (higher levels of quoting)</p></li><li><p>search (hiliting of words in the pager)</p></li><li><p>signature</p></li><li><p>status (mode lines used to display info about the mailbox or message)</p></li><li><p>tilde (the “<span class="quote">˜</span>” used to pad blank lines in the pager)</p></li><li><p>tree (thread tree drawn in the message index and attachment menu)</p></li><li><p>underline (hiliting underlined patterns in the body of messages)</p></li></ul></div><p>
-<span class="emphasis"><em>foreground</em></span> and <span class="emphasis"><em>background</em></span> can be one of the following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>white</p></li><li><p>black</p></li><li><p>green</p></li><li><p>magenta</p></li><li><p>blue</p></li><li><p>cyan</p></li><li><p>yellow</p></li><li><p>red</p></li><li><p>default</p></li><li><p>color<span class="emphasis"><em>x</em></span></p></li></ul></div><p>
-<span class="emphasis"><em>foreground</em></span> can optionally be prefixed with the keyword <code class="literal">bright</code> to make
-the foreground color boldfaced (e.g., <code class="literal">brightred</code>).
-</p><p>
-If your terminal supports it, the special keyword <span class="emphasis"><em>default</em></span> can be
-used as a transparent color. The value <span class="emphasis"><em>brightdefault</em></span> is also valid.
-If Mutt is linked against the <span class="emphasis"><em>S-Lang</em></span> library, you also need to set
-the <span class="emphasis"><em>COLORFGBG</em></span> environment variable to the default colors of your
-terminal for this to work; for example (for Bourne-like shells):
-</p><pre class="screen">
-set COLORFGBG="green;black"
-export COLORFGBG
-</pre><div class="note"><h3 class="title">Note</h3><p>
-The <span class="emphasis"><em>S-Lang</em></span> library requires you to use the <span class="emphasis"><em>lightgray</em></span>
-and <span class="emphasis"><em>brown</em></span> keywords instead of <span class="emphasis"><em>white</em></span> and <span class="emphasis"><em>yellow</em></span> when
-setting this variable.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-The uncolor command can be applied to the index object only. It
-removes entries from the list. You <span class="bold"><strong>must</strong></span> specify the same pattern
-specified in the color command for it to be removed. The pattern “<span class="quote">*</span>” is
-a special token which means to clear the color index list of all entries.
-</p></div><p>
-Mutt also recognizes the keywords <span class="emphasis"><em>color0</em></span>, <span class="emphasis"><em>color1</em></span>, …,
-<span class="emphasis"><em>color</em></span><span class="bold"><strong>N-1</strong></span> (<span class="bold"><strong>N</strong></span> 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 <span class="emphasis"><em>color2</em></span>
-for your xterm), since color names may then lose their normal meaning.
-</p><p>
-If your terminal does not support color, it is still possible change the video
-attributes through the use of the “<span class="quote">mono</span>” command:
-</p><a id="mono"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mono</code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>attribute</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">mono</code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">mono</code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unmono</code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-For <span class="emphasis"><em>object</em></span>, see the color command. <span class="emphasis"><em>attribute</em></span>
-can be one of the following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>none</p></li><li><p>bold</p></li><li><p>underline</p></li><li><p>reverse</p></li><li><p>standout</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ignore"></a>10. Message header display</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">ignore</code>
-<em class="replaceable"><code>pattern</code></em>
- [
-<em class="replaceable"><code>pattern</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unignore</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-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 in the pager.
-</p><p>
-You do not need to specify the full header field name. For example,
-“<span class="quote">ignore content-</span>” will ignore all header fields that begin with the pattern
-“<span class="quote">content-</span>”. “<span class="quote">ignore *</span>” will ignore all headers.
-</p><p>
-To remove a previously added token from the list, use the “<span class="quote">unignore</span>” command.
-The “<span class="quote">unignore</span>” command will make Mutt display headers with the given pattern.
-For example, if you do “<span class="quote">ignore x-</span>” it is possible to “<span class="quote">unignore x-mailer</span>”.
-</p><p>
-“<span class="quote">unignore *</span>” will remove all tokens from the ignore list.
-</p><p>
-For example:
-</p><div class="example"><a id="ex-header-weeding"></a><p class="title"><b>Example 3.8. Header weeding</b></p><div class="example-contents"><pre class="screen">
-# 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:
-</pre></div></div><br class="example-break" /><a id="hdr-order"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">hdr_order</code>
-<em class="replaceable"><code>header</code></em>
- [
-<em class="replaceable"><code>header</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unhdr_order</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>header</code></em>
-... }</p></div><p>
-With the <code class="literal">hdr_order</code> command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
-</p><p>
-“<span class="quote">unhdr_order *</span>” will clear all previous headers from the order list,
-thus removing the header order effects set by the system-wide startup file.
-</p><div class="example"><a id="ex-hdr-order"></a><p class="title"><b>Example 3.9. Configuring header display order</b></p><div class="example-contents"><pre class="screen">
-hdr_order From Date: From: To: Cc: Subject:
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternates"></a>11. Alternative addresses</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alternates</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unalternates</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><p>
-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 <a class="link" href="reference.html#reply-to" title="3.242. reply_to">$reply_to</a>.)
-</p><p>
-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 <code class="literal">alternates</code> command: It takes a list of regular
-expressions, each of which can identify an address under which you
-receive e-mail.
-</p><p>
-As addresses are matched using regular expressions and not exact strict
-comparisons, you should make sure you specify your addresses as precise
-as possible to avoid mismatches. For example, if you specify:
-</p><pre class="screen">
-alternates user@example
-</pre><p>
-mutt will consider “<span class="quote"><code class="literal">some-user@example</code></span>” as
-being your address, too which may not be desired. As a solution, in such
-cases addresses should be specified as:
-</p><pre class="screen">
-alternates '^user@example$'
-</pre><p>
-The <code class="literal">-group</code> flag causes all of the subsequent regular expressions
-to be added to the named group.
-</p><p>
-The <code class="literal">unalternates</code> command can be used to write exceptions to
-<code class="literal">alternates</code> patterns. If an address matches something in an
-<code class="literal">alternates</code> command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an <code class="literal">unalternates</code>
-command.
-</p><p>
-To remove a regular expression from the <code class="literal">alternates</code> list, use the
-<code class="literal">unalternates</code> command with exactly the same <span class="emphasis"><em>regexp</em></span>.
-Likewise, if the <span class="emphasis"><em>regexp</em></span> for an <code class="literal">alternates</code> command matches
-an entry on the <code class="literal">unalternates</code> list, that <code class="literal">unalternates</code>
-entry will be removed. If the <span class="emphasis"><em>regexp</em></span> for <code class="literal">unalternates</code>
-is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries</em></span> on <code class="literal">alternates</code> will be removed.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="lists"></a>12. Mailing lists</h2></div></div></div><a id="subscribe"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">lists</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unlists</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><div class="cmdsynopsis"><p><code class="command">subscribe</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unsubscribe</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><p>
-Mutt has a few nice features for <a class="link" href="advancedusage.html#using-lists" title="8. Handling Mailing Lists">handling mailing lists</a>. 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 <a class="link" href="gettingstarted.html#list-reply"><code class="literal"><list-reply></code></a> 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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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
-<a class="link" href="reference.html#followup-to" title="3.60. followup_to">$followup_to</a>
-configuration variable.
-</p></div><p>
-More precisely, Mutt 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 “<span class="quote">lists</span>”
-command. To mark it as subscribed, use “<span class="quote">subscribe</span>”.
-</p><p>
-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
-“<span class="quote">subscribe [0-9]*@bugs.guug.de</span>”. Often, it's sufficient to just
-give a portion of the list's e-mail address.
-</p><p>
-Specify as much of the address as you need to to remove ambiguity. For
-example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed to <span class="emphasis"><em>mutt-users@mutt.org</em></span>. So, to tell Mutt
-that this is a mailing list, you could add “<span class="quote">lists mutt-users@</span>” to your
-initialization file. To tell mutt that you are subscribed to it,
-add “<span class="quote">subscribe mutt-users</span>” to your initialization file instead.
-If you also happen to get mail from someone whose address is
-<span class="emphasis"><em>mutt-users@example.com</em></span>, you could use
-“<span class="quote">lists ^mutt-users@mutt\\.org$</span>”
-or “<span class="quote">subscribe ^mutt-users@mutt\\.org$</span>” to
-match only mail from the actual list.
-</p><p>
-The <code class="literal">-group</code> flag adds all of the subsequent regular expressions
-to the named group.
-</p><p>
-The “<span class="quote">unlists</span>” command is used to remove a token from the list of
-known and subscribed mailing-lists. Use “<span class="quote">unlists *</span>” to remove all
-tokens.
-</p><p>
-To remove a mailing list from the list of subscribed mailing lists,
-but keep it on the list of known mailing lists, use “<span class="quote">unsubscribe</span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mbox-hook"></a>13. Using Multiple spool mailboxes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mbox-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to move read messages from a specified mailbox to a
-different mailbox automatically when you quit or change folders.
-<span class="emphasis"><em>pattern</em></span> is a regular expression specifying the mailbox to treat as a
-“<span class="quote">spool</span>” mailbox and <span class="emphasis"><em>mailbox</em></span> specifies where mail should be saved when
-read.
-</p><p>
-Unlike some of the other <span class="emphasis"><em>hook</em></span> commands, only the <span class="emphasis"><em>first</em></span> matching
-pattern is used (it is not possible to save read mail in more than a single
-mailbox).
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailboxes"></a>14. Monitoring incoming mail</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mailboxes</code>
-<em class="replaceable"><code>mailbox</code></em>
- [
-<em class="replaceable"><code>mailbox</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unmailboxes</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mailbox</code></em>
-... }</p></div><p>
-This command specifies folders which can receive mail and
-which will be checked for new messages periodically.
-</p><p>
-<span class="emphasis"><em>folder</em></span> can either be a local file or directory
-(Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP
-support, <span class="emphasis"><em>folder</em></span> can also be a POP/IMAP folder
-URL. The URL syntax is described in <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>,
-POP and IMAP are described in <a class="xref" href="optionalfeatures.html#pop" title="3. POP3 Support">Section 3, “POP3 Support”</a> and <a class="xref" href="optionalfeatures.html#imap" title="4. IMAP Support">Section 4, “IMAP Support”</a>
-respectively.
-</p><p>
-Mutt provides a number of advanced features for handling (possibly many)
-folders and new mail within them, please refer to
-<a class="xref" href="advancedusage.html#handling-folders" title="9. Handling multiple folders">Section 9, “Handling multiple folders”</a> for details (including in what
-situations and how often Mutt checks for new mail).
-</p><p>
-The “<span class="quote">unmailboxes</span>” command is used to remove a token from the list
-of folders which receive mail. Use “<span class="quote">unmailboxes *</span>” to remove all
-tokens.
-</p><div class="note"><h3 class="title">Note</h3><p>
-The folders in the <code class="literal">mailboxes</code> command are resolved when
-the command is executed, so if these names contain <a class="link" href="advancedusage.html#shortcuts" title="7. Mailbox Shortcuts">shortcut characters</a> (such as “<span class="quote">=</span>” and “<span class="quote">!</span>”), any variable
-definition that affects these characters (like <a class="link" href="reference.html#folder" title="3.58. folder">$folder</a> and <a class="link" href="reference.html#spoolfile" title="3.276. spoolfile">$spoolfile</a>)
-should be set before the <code class="literal">mailboxes</code> command. If
-none of these shorcuts are used, a local path should be absolute as
-otherwise mutt tries to find it relative to the directory
-from where mutt was started which may not always be desired.
-</p></div><p>
-For Mbox and Mmdf folders, new mail is detected by comparing access and/or
-modification times of files: Mutt assumes a folder has new mail if it wasn't
-accessed after it was last modified. Utilities like <code class="literal">biff</code> or
-<code class="literal">frm</code> or any other program which accesses the mailbox might cause
-Mutt to never detect new mail for that mailbox if they do not properly reset the
-access time. Other possible causes of Mutt not detecting new mail in these folders
-are backup tools (updating access times) or filesystems mounted without
-access time update support.
-</p><p>
-In cases where new mail detection for Mbox or Mmdf folders appears to be
-unreliable, the
-<a class="link" href="reference.html#check-mbox-size" title="3.24. check_mbox_size">$check_mbox_size</a>
-option can be used to make Mutt track and consult file sizes for new
-mail detection instead.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="my-hdr"></a>15. User defined headers</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">my_hdr</code>
-<em class="replaceable"><code>string</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unmy_hdr</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>field</code></em>
-... }</p></div><p>
-The <code class="literal">my_hdr</code> command allows you to create your own header
-fields which will be added to every message you send.
-</p><p>
-For example, if you would like to add an “<span class="quote">Organization:</span>” header field to
-all of your outgoing messages, you can put the command
-</p><div class="example"><a id="ex-my-hdr"></a><p class="title"><b>Example 3.10. Defining custom headers</b></p><div class="example-contents"><pre class="screen">
-my_hdr Organization: A Really Big Company, Anytown, USA
-</pre></div></div><br class="example-break" /><p>
-in your <code class="literal">.muttrc</code>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Space characters are <span class="emphasis"><em>not</em></span> allowed between the keyword and
-the colon (“<span class="quote">:</span>”). The standard for electronic mail (RFC2822) says that
-space is illegal there, so Mutt enforces the rule.
-</p></div><p>
-If you would like to add a header field to a single message, you should
-either set the <a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable,
-or use the <code class="literal"><edit-headers></code> function (default: “<span class="quote">E</span>”) in the compose menu so
-that you can edit the header of your message along with the body.
-</p><p>
-To remove user defined header fields, use the <code class="literal">unmy_hdr</code>
-command. You may specify an asterisk (“<span class="quote">*</span>”) to remove all header
-fields, or the fields to remove. For example, to remove all “<span class="quote">To</span>” and
-“<span class="quote">Cc</span>” header fields, you could use:
-</p><pre class="screen">
-unmy_hdr to cc
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="save-hook"></a>16. Specify default save mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">save-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to override the default mailbox used when saving
-messages. <span class="emphasis"><em>mailbox</em></span> will be used as the default if the message
-matches <span class="emphasis"><em>pattern</em></span>, see <a class="xref" href="advancedusage.html#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information
-on the exact format.
-</p><p>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> to
-<span class="emphasis"><em>mailbox</em></span> after it was expanded.
-</p><p>
-Examples:
-</p><div class="example"><a id="ex-save-hook-exando"></a><p class="title"><b>Example 3.11. Using %-expandos in <code class="literal">save-hook</code></b></p><div class="example-contents"><pre class="screen">
-# default: save all to ~/Mail/<author name>
-save-hook . ~/Mail/%F
-
-# save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
-save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
-# save from aol.com to $folder/spam
-save-hook aol\\.com$ +spam
-</pre></div></div><br class="example-break" /><p>
-Also see the <a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-hook"></a>17. Specify default Fcc: mailbox when composing</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to save outgoing mail in a mailbox other than
-<a class="link" href="reference.html#record" title="3.239. record">$record</a>. Mutt searches the initial list of
-message recipients for the first matching <span class="emphasis"><em>regexp</em></span> and uses <span class="emphasis"><em>mailbox</em></span>
-as the default Fcc: mailbox. If no match is found the message will be saved
-to <a class="link" href="reference.html#record" title="3.239. record">$record</a> mailbox.
-</p><p>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> to
-<span class="emphasis"><em>mailbox</em></span> after it was expanded.
-</p><p>
-See <a class="xref" href="advancedusage.html#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information on the exact format of <span class="emphasis"><em>pattern</em></span>.
-</p><p>
-Example: <code class="literal">fcc-hook [@.]aol\\.com$ +spammers</code>
-</p><p>
-The above will save a copy of all messages going to the aol.com domain to
-the `+spammers' mailbox by default. Also see the <a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-save-hook"></a>18. Specify default save filename and default Fcc: mailbox at once</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-save-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is a shortcut, equivalent to doing both a <a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
-and a <a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a> with its arguments,
-including %-expansion on <span class="emphasis"><em>mailbox</em></span> according
-to <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="send-hook"></a>19. Change settings based upon message recipients</h2></div></div></div><a id="reply-hook"></a><a id="send2-hook"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">reply-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">send-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">send2-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-These commands can be used to execute arbitrary configuration commands based
-upon recipients of the message. <span class="emphasis"><em>pattern</em></span> is used to match
-the message, see <a class="xref" href="advancedusage.html#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for details. <span class="emphasis"><em>command</em></span>
-is executed when <span class="emphasis"><em>pattern</em></span> matches.
-</p><p>
-<code class="literal">reply-hook</code> is matched against the message you are <span class="emphasis"><em>replying to</em></span>,
-instead of the message you are <span class="emphasis"><em>sending</em></span>. <code class="literal">send-hook</code> is
-matched against all messages, both <span class="emphasis"><em>new</em></span>
-and <span class="emphasis"><em>replies</em></span>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-<code class="literal">reply-hook</code>s are matched <span class="bold"><strong>before</strong></span> the <code class="literal">send-hook</code>, <span class="bold"><strong>regardless</strong></span>
-of the order specified in the user's configuration file.
-</p></div><p>
-<code class="literal">send2-hook</code> is matched every time a message is changed, either
-by editing it, or by using the compose menu to change its recipients
-or subject. <code class="literal">send2-hook</code> is executed after <code class="literal">send-hook</code>, and
-can, e.g., be used to set parameters such as the <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a> variable depending on the message's sender
-address.
-</p><p>
-For each type of <code class="literal">send-hook</code> or <code class="literal">reply-hook</code>, when multiple matches
-occur, commands are executed in the order they are specified in the muttrc
-(for that type of hook).
-</p><p>
-Example: <code class="literal">send-hook mutt "set mime_forward signature=''"</code>
-</p><p>
-Another typical use for this command is to change the values of the
-<a class="link" href="reference.html#attribution" title="3.16. attribution">$attribution</a>, <a class="link" href="reference.html#signature" title="3.262. signature">$signature</a> and <a class="link" href="reference.html#locale" title="3.104. locale">$locale</a>
-variables in order to change the language of the attributions and
-signatures based upon the recipients.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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
-<code class="literal">my_hdr</code> 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.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="message-hook"></a>20. Change settings before formatting a message</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">message-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-This command can be used to execute arbitrary configuration commands
-before viewing or formatting a message based upon information about the message.
-<span class="emphasis"><em>command</em></span> is executed if the <span class="emphasis"><em>pattern</em></span> matches the message to be
-displayed. When multiple matches occur, commands are executed in the order
-they are specified in the muttrc.
-</p><p>
-See <a class="xref" href="advancedusage.html#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for
-information on the exact format of <span class="emphasis"><em>pattern</em></span>.
-</p><p>
-Example:
-</p><pre class="screen">
-message-hook ~A 'set pager=builtin'
-message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="crypt-hook"></a>21. Choosing the cryptographic key of the recipient</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">crypt-hook</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>keyid</code></em>
- </p></div><p>
-When encrypting messages with PGP/GnuPG 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 would
-normally use. The <code class="literal">crypt-hook</code> 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.
-</p><p>
-The meaning of <span class="emphasis"><em>keyid</em></span> 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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="push"></a>22. Adding key sequences to the keyboard buffer</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">push</code>
-<em class="replaceable"><code>string</code></em>
- </p></div><p>
-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 <a class="link" href="configuration.html#macro" title="8. Keyboard macros">macro</a> 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:
-</p><div class="example"><a id="ex-folder-hook-push"></a><p class="title"><b>Example 3.12. Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></b></p><div class="example-contents"><pre class="screen">
-folder-hook . 'push <collapse-all>'
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exec"></a>23. Executing functions</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">exec</code>
-<em class="replaceable"><code>function</code></em>
- [
-<em class="replaceable"><code>function</code></em>
-...]</p></div><p>
-This command can be used to execute any function. Functions are
-listed in the <a class="link" href="reference.html#functions" title="4. Functions">function reference</a>.
-“<span class="quote">exec function</span>” is equivalent to “<span class="quote">push <function></span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="score-command"></a>24. Message Scoring</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">score</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>value</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unscore</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-The <code class="literal">score</code> commands adds <span class="emphasis"><em>value</em></span> to a message's score if <span class="emphasis"><em>pattern</em></span>
-matches it. <span class="emphasis"><em>pattern</em></span> is a string in the format described in the <a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> section (note: For efficiency reasons, patterns
-which scan information not available in the index, such as <code class="literal">˜b</code>,
-<code class="literal">˜B</code> or <code class="literal">˜h</code>, may not be used). <span class="emphasis"><em>value</em></span> is a
-positive or negative integer. A message's final score is the sum total of all
-matching <code class="literal">score</code> entries. However, you may optionally prefix <span class="emphasis"><em>value</em></span> with
-an equal sign (=) to cause evaluation to stop at a particular entry if there is
-a match. Negative final scores are rounded up to 0.
-</p><p>
-The <code class="literal">unscore</code> command removes score entries from the list. You <span class="bold"><strong>must</strong></span>
-specify the same pattern specified in the <code class="literal">score</code> command for it to be
-removed. The pattern “<span class="quote">*</span>” is a special token which means to clear the list
-of all score entries.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="spam"></a>25. Spam detection</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">spam</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>format</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">nospam</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
- }</p></div><p>
-Mutt has generalized support for external spam-scoring filters.
-By defining your spam patterns with the <code class="literal">spam</code> and <code class="literal">nospam</code>
-commands, you can <span class="emphasis"><em>limit</em></span>, <span class="emphasis"><em>search</em></span>, and <span class="emphasis"><em>sort</em></span> 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 <code class="literal">%H</code> selector in the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable. (Tip: try <code class="literal">%?H?[%H] ?</code>
-to display spam tags only when they are defined for a given message.)
-</p><p>
-Your first step is to define your external filter's spam patterns using
-the <code class="literal">spam</code> command. <span class="emphasis"><em>pattern</em></span> 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 “<span class="quote">spam tag</span>” or
-“<span class="quote">spam attribute</span>” (unless it also matches a <code class="literal">nospam</code> pattern -- see
-below.) The appearance of this attribute is entirely up to you, and is
-governed by the <span class="emphasis"><em>format</em></span> parameter. <span class="emphasis"><em>format</em></span> can be any static
-text, but it also can include back-references from the <span class="emphasis"><em>pattern</em></span>
-expression. (A regular expression “<span class="quote">back-reference</span>” refers to a
-sub-expression contained within parentheses.) <code class="literal">%1</code> is replaced with
-the first back-reference in the regex, <code class="literal">%2</code> with the second, etc.
-</p><p>
-If you're using multiple spam filters, a message can have more than
-one spam-related header. You can define <code class="literal">spam</code> 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 <span class="emphasis"><em>format</em></span> strings joined
-together, with the value of $spam_separator separating
-them.
-</p><p>
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-define these spam settings:
-</p><div class="example"><a id="ex-spam"></a><p class="title"><b>Example 3.13. Configuring spam detection</b></p><div class="example-contents"><pre class="screen">
-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=", "
-</pre></div></div><br class="example-break" /><p>
-If I then received a message that DCC registered with “<span class="quote">many</span>” hits
-under the “<span class="quote">Fuz2</span>” checksum, and that PureMessage registered with a
-97% probability of being spam, that message's spam tag would read
-<code class="literal">90+/DCC-Fuz2, 97/PM</code>. (The four characters before “<span class="quote">=many</span>” in a
-DCC report indicate the checksum used -- in this case, “<span class="quote">Fuz2</span>”.)
-</p><p>
-If the $spam_separator variable is unset, then each
-spam pattern match supersedes the previous one. Instead of getting
-joined <span class="emphasis"><em>format</em></span> strings, you'll get only the last one to match.
-</p><p>
-The spam tag is what will be displayed in the index when you use
-<code class="literal">%H</code> in the <code class="literal">$index_format</code> variable. It's also the
-string that the <code class="literal">˜H</code> pattern-matching expression matches against for
-<code class="literal"><search></code> and <code class="literal"><limit></code> functions. And it's what sorting by spam
-attribute will use as a sort key.
-</p><p>
-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.
-</p><p>
-Generally, when you sort by spam tag, mutt will sort <span class="emphasis"><em>lexically</em></span> --
-that is, by ordering strings alphanumerically. 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
-<code class="literal">sort -n</code>.) A message with no spam attributes at all -- that is, one
-that didn't match <span class="emphasis"><em>any</em></span> of your <code class="literal">spam</code> patterns -- is sorted at
-lowest priority. Numbers are sorted next, beginning with 0 and ranging
-upward. Finally, non-numeric strings are sorted, with “<span class="quote">a</span>” taking lower
-priority than “<span class="quote">z</span>”. 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.
-</p><p>
-The <code class="literal">nospam</code> command can be used to write exceptions to <code class="literal">spam</code>
-patterns. If a header pattern matches something in a <code class="literal">spam</code> command,
-but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a <code class="literal">nospam</code> command.
-</p><p>
-If the <span class="emphasis"><em>pattern</em></span> given to <code class="literal">nospam</code> is exactly the same as the
-<span class="emphasis"><em>pattern</em></span> on an existing <code class="literal">spam</code> list entry, the effect will be to
-remove the entry from the spam list, instead of adding an exception.
-Likewise, if the <span class="emphasis"><em>pattern</em></span> for a <code class="literal">spam</code> command matches an entry
-on the <code class="literal">nospam</code> list, that <code class="literal">nospam</code> entry will be removed. If the
-<span class="emphasis"><em>pattern</em></span> for <code class="literal">nospam</code> is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries on both lists</em></span>
-will be removed. This might be the default action if you use <code class="literal">spam</code>
-and <code class="literal">nospam</code> in conjunction with a <code class="literal">folder-hook</code>.
-</p><p>
-You can have as many <code class="literal">spam</code> or <code class="literal">nospam</code> commands as you like.
-You can even do your own primitive spam detection within mutt -- for
-example, if you consider all mail from <code class="literal">MAILER-DAEMON</code> to be spam,
-you can use a <code class="literal">spam</code> command like this:
-</p><pre class="screen">
-spam "^From: .*MAILER-DAEMON" "999"
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="set"></a>26. Setting and Querying Variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-commands"></a>26.1. Commands</h3></div></div></div><p>
-The following commands are available to manipulate and query variables:
-</p><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">set</code> {
-[ <code class="option">no</code> | <code class="option">inv</code> ]
-<em class="replaceable"><code>variable</code></em>
- |
-<em class="replaceable"><code>variable=value</code></em>
- } [...]</p></div><div class="cmdsynopsis"><p><code class="command">toggle</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unset</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">reset</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><p>
-This command is used to set (and unset) <a class="link" href="reference.html#variables" title="3. Configuration variables">configuration variables</a>. There are four basic types of variables:
-boolean, number, string and quadoption. <span class="emphasis"><em>boolean</em></span> variables can be
-<span class="emphasis"><em>set</em></span> (true) or <span class="emphasis"><em>unset</em></span> (false). <span class="emphasis"><em>number</em></span> variables can be
-assigned a positive integer value.
-<span class="emphasis"><em>string</em></span> variables consist of any number of printable characters and
-must be enclosed in quotes if they contain spaces or tabs. You
-may also use the escape sequences “<span class="quote">\n</span>” and “<span class="quote">\t</span>” for newline and tab, respectively.
-<span class="emphasis"><em>quadoption</em></span> variables are used to control whether or not to be prompted
-for certain actions, or to specify a default action. A value of <span class="emphasis"><em>yes</em></span>
-will cause the action to be carried out automatically as if you had answered
-yes to the question. Similarly, a value of <span class="emphasis"><em>no</em></span> will cause the
-action to be carried out as if you had answered “<span class="quote">no.</span>” A value of
-<span class="emphasis"><em>ask-yes</em></span> will cause a prompt with a default answer of “<span class="quote">yes</span>” and
-<span class="emphasis"><em>ask-no</em></span> will provide a default answer of “<span class="quote">no.</span>”
-</p><p>
-Prefixing a variable with “<span class="quote">no</span>” will unset it. Example: <code class="literal">set noaskbcc</code>.
-</p><p>
-For <span class="emphasis"><em>boolean</em></span> variables, you may optionally prefix the variable name with
-<code class="literal">inv</code> to toggle the value (on or off). This is useful when writing
-macros. Example: <code class="literal">set invsmart_wrap</code>.
-</p><p>
-The <code class="literal">toggle</code> command automatically prepends the <code class="literal">inv</code> prefix to all
-specified variables.
-</p><p>
-The <code class="literal">unset</code> command automatically prepends the <code class="literal">no</code> prefix to all
-specified variables.
-</p><p>
-Using the <code class="literal"><enter-command></code> function in the <span class="emphasis"><em>index</em></span> menu, you can query the
-value of a variable by prefixing the name of the variable with a question
-mark:
-</p><pre class="screen">
-set ?allow_8bit
-</pre><p>
-The question mark is actually only required for boolean and quadoption
-variables.
-</p><p>
-The <code class="literal">reset</code> command resets all given variables to the compile time
-defaults (hopefully mentioned in this manual). If you use the command
-<code class="literal">set</code> and prefix the variable with “<span class="quote">&</span>” this has the same
-behavior as the reset command.
-</p><p>
-With the <code class="literal">reset</code> command there exists the special variable “<span class="quote">all</span>”,
-which allows you to reset all variables to their system defaults.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-myvar"></a>26.2. User-defined variables</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-intro"></a>26.2.1. Introduction</h4></div></div></div><p>
-Along with the variables listed in the
-<a class="link" href="reference.html#variables" title="3. Configuration variables">Configuration variables</a> section, mutt
-supports user-defined variables with names starting
-with <code class="literal">my_</code> as in, for
-example, <code class="literal">my_cfgdir</code>.
-</p><p>
-The <code class="literal">set</code> command either creates a
-custom <code class="literal">my_</code> variable or changes its
-value if it does exist already. The <code class="literal">unset</code> and <code class="literal">reset</code>
-commands remove the variable entirely.
-</p><p>
-Since user-defined variables are expanded in the same way that
-environment variables are (except for
-the <a class="link" href="gettingstarted.html#shell-escape">shell-escape</a> command and
-backtick expansion), this feature can be used to make configuration
-files more readable.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-examples"></a>26.2.2. Examples</h4></div></div></div><p>
-The following example defines and uses the variable <code class="literal">my_cfgdir</code>
-to abbreviate the calls of the <a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a> command:
-</p><div class="example"><a id="ex-myvar1"></a><p class="title"><b>Example 3.14. Using user-defined variables for config file readability</b></p><div class="example-contents"><pre class="screen">
-set my_cfgdir = $HOME/mutt/config
-
-source $my_cfgdir/hooks
-source $my_cfgdir/macros
-# more source commands...
-</pre></div></div><br class="example-break" /><p>
-A custom variable can also be used in macros to backup the current value
-of another variable. In the following example, the value of the
-<a class="link" href="reference.html#delete" title="3.42. delete">$delete</a> is changed temporarily
-while its original value is saved as <code class="literal">my_delete</code>.
-After the macro has executed all commands, the original value of <a class="link" href="reference.html#delete" title="3.42. delete">$delete</a> is restored.
-</p><div class="example"><a id="ex-myvar2"></a><p class="title"><b>Example 3.15. Using user-defined variables for backing up other config option values</b></p><div class="example-contents"><pre class="screen">
-macro pager ,x '\
-<enter-command>set my_delete=$delete<enter>\
-<enter-command>set delete=yes<enter>\
-...\
-<enter-command>set delete=$my_delete<enter>'
-</pre></div></div><br class="example-break" /><p>
-Since mutt expands such values already when parsing the configuration
-file(s), the value of <code class="literal">$my_delete</code> in the
-last example would be the value of <code class="literal">$delete</code> exactly
-as it was at that point during parsing the configuration file. If
-another statement would change the value for <code class="literal">$delete</code>
-later in the same or another file, it would have no effect on
-<code class="literal">$my_delete</code>. However, the expansion can
-be deferred to runtime, as shown in the next example, when escaping the
-dollar sign.
-</p><div class="example"><a id="ex-myvar3"></a><p class="title"><b>Example 3.16. Deferring user-defined variable expansion to runtime</b></p><div class="example-contents"><pre class="screen">
-macro pager <PageDown> "\
-<enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
-<next-page>\
-<enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
-<enter-command> unset my_old_pager_stop<Enter>"
-</pre></div></div><br class="example-break" /><p>
-Note that there is a space
-between <code class="literal"><enter-command></code> and
-the <code class="literal">set</code> configuration command, preventing mutt from
-recording the macro's commands into its history.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="source"></a>27. Reading initialization commands from another file</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">source</code>
-<em class="replaceable"><code>filename</code></em>
- </p></div><p>
-This command allows the inclusion of initialization commands
-from other files. For example, I place all of my aliases in
-<code class="literal">˜/.mail_aliases</code> so that I can make my
-<code class="literal">˜/.muttrc</code> readable and keep my aliases private.
-</p><p>
-If the filename begins with a tilde (“<span class="quote">˜</span>”), it will be expanded to the
-path of your home directory.
-</p><p>
-If the filename ends with a vertical bar (|), then <span class="emphasis"><em>filename</em></span> is
-considered to be an executable program from which to read input (eg.
-<code class="literal">source ˜/bin/myscript|</code>).
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ifdef"></a>28. Configuring features conditionnaly</h2></div></div></div><p>
-Usage: <code class="literal">ifdef</code> <span class="emphasis"><em>item</em></span> <span class="emphasis"><em>command</em></span>
-</p><p>
-This command allows to test if a feature has been compiled in, before
-actually executing the command. Item can be either the name of a
-function, variable, or command. Example:
-</p><p>
-</p><pre class="screen">
-ifdef imap_keepalive 'source ~/.mutt/imap_setup'
-</pre><p>
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="unhook"></a>29. Removing hooks</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">unhook</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>hook-type</code></em>
- }</p></div><p>
-This command permits you to flush hooks you have previously defined.
-You can either remove all hooks by giving the “<span class="quote">*</span>” character as an
-argument, or you can remove all hooks of a specific type by saying
-something like <code class="literal">unhook send-hook</code>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="formatstrings"></a>30. Format Strings</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-basics"></a>30.1. Basic usage</h3></div></div></div><p>
-Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
-<a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>,
-<a class="link" href="reference.html#pager-format" title="3.140. pager_format">$pager_format</a>,
-<a class="link" href="reference.html#status-format" title="3.278. status_format">$status_format</a>,
-and other “<span class="quote">*_format</span>” variables. These can be very straightforward,
-and it's quite possible you already know how to use them.
-</p><p>
-The most basic format string element is a percent symbol followed
-by another character. For example, <code class="literal">%s</code>
-represents a message's Subject: header in the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable. The
-“<span class="quote">expandos</span>” available are documented with each format variable, but
-there are general modifiers available with all formatting expandos,
-too. Those are our concern here.
-</p><p>
-Some of the modifiers are borrowed right out of C (though you might
-know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in <code class="literal">%-12.12s</code>. As with
-such programming languages, these modifiers allow you to specify the
-minimum and maximum size of the resulting string, as well as its
-justification. If the “<span class="quote">-</span>” sign follows the percent, the string will
-be left-justified instead of right-justified. If there's a number
-immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
-will be padded out with spaces. If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
-permitted to exceed that width, no matter its natural size. Each of
-these three elements is optional, so that all these are legal format
-strings:
-<code class="literal">%-12s</code>
-<code class="literal">%4c</code>
-<code class="literal">%.15F</code>
-<code class="literal">%-12.15L</code>
-</p><p>
-Mutt adds some other modifiers to format strings. If you use an equals
-symbol (<code class="literal">=</code>) as a numeric prefix (like the minus
-above), it will force the string to be centered within its minimum
-space range. For example, <code class="literal">%=14y</code> will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-<code class="literal">$index_format</code>. If the expansion
-results in a string less than 14 characters, it will be centered in a
-14-character space. If the X-Label for a message were "test", that
-expansion would look like “<span class="quote"> test </span>”.
-</p><p>
-There are two very little-known modifiers that affect the way that an
-expando is replaced. If there is an underline (“<span class="quote">_</span>”) character
-between any format modifiers (as above) and the expando letter, it will
-expands in all lower case. And if you use a colon (“<span class="quote">:</span>”), it will
-replace all decimal points with underlines.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-filters"></a>30.2. Filters</h3></div></div></div><p>
-Any format string ending in a vertical bar (“<span class="quote">|</span>”) will be
-expanded and piped through the first word in the string, using spaces
-as separator. The string returned will be used for display.
-If the returned string ends in %, it will be passed through
-the formatter a second time. This allows the filter to generate a
-replacement format string including % expandos.
-</p><p>
-All % expandos in a format string are expanded before the script
-is called so that:
-</p><div class="example"><a id="ex-fmtpipe"></a><p class="title"><b>Example 3.17. Using external filters in format strings</b></p><div class="example-contents"><pre class="screen">
-set status_format="script.sh '%r %f (%L)'|"
-</pre></div></div><br class="example-break" /><p>
-will make mutt expand <code class="literal">%r</code>,
-<code class="literal">%f</code> and <code class="literal">%L</code>
-before calling the script. The example also shows that arguments can be
-quoted: the script will receive the expanded string between the single quotes
-as the only argument.
-</p><p>
-A practical example is the <code class="literal">mutt_xtitle</code>
-script installed in the <code class="literal">samples</code>
-subdirectory of the mutt documentation: it can be used as filter for
-<code class="literal">$status_format</code> to set the current
-terminal's title, if supported.
-</p></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="gettingstarted.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="advancedusage.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Getting Started </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Advanced Usage</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Getting Started</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="intro.html" title="Chapter 1. Introduction" /><link rel="next" href="configuration.html" title="Chapter 3. Configuration" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Getting Started</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="intro.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="configuration.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="gettingstarted"></a>Chapter 2. Getting Started</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="gettingstarted.html#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#postponing-mail">7. Postponing Mail</a></span></dt></dl></div><p>
-This section is intended as a brief overview of how to use Mutt. There are
-many other features which are described elsewhere in the manual. There
-is even more information available in the Mutt FAQ and various web
-pages. See the <a class="ulink" href="http://www.mutt.org/" target="_top">Mutt homepage</a> for more details.
-</p><p>
-The keybindings described in this section are the defaults as distributed.
-Your local system administrator may have altered the defaults for your site.
-You can always type “<span class="quote">?</span>” in any menu to display the current bindings.
-</p><p>
-The first thing you need to do is invoke mutt, simply by typing <code class="literal">mutt</code>
-at the command line. There are various command-line options, see
-either the mutt man page or the <a class="link" href="reference.html#commandline" title="1. Command line options">reference</a>.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="core-concepts"></a>1. Core concepts</h2></div></div></div><p>
-Mutt is a text-based application which interacts with users through
-different menus which are mostly line-/entry-based or page-based. A
-line-based menu is the so-called “<span class="quote">index</span>” menu (listing all messages of
-the currently opened folder) or the “<span class="quote">alias</span>” menu (allowing you to
-select recipients from a list). Examples for page-based menus are the
-“<span class="quote">pager</span>” (showing one message at a time) or the “<span class="quote">help</span>” menu listing
-all available key bindings.
-</p><p>
-The user interface consists of a context sensitive help line at the top,
-the menu's contents followed by a context sensitive status line and
-finally the command line. The command line is used to display
-informational and error messages as well as for prompts and for entering
-interactive commands.
-</p><p>
-Because Mutt allows for customizing almost all key bindings, there are
-so-called “<span class="quote">functions</span>” which can be executed manually (using the
-command line) or in macros. Macros allow the user to bind a sequence of
-commands to a single key or a short key sequence instead of repeating a
-sequence of actions over and over.
-</p><p>
-Many commands (such as saving or copying a message to another folder)
-can be applied to a single message or a set of messages (so-called
-“<span class="quote">tagged</span>” messages). To help selecting messages, Mutt provides a rich
-set of message patterns (such as recipients, sender, body contents, date
-sent/received, etc.) which can be combined into complex expressions
-using the boolean <span class="emphasis"><em>and</em></span> and <span class="emphasis"><em>or</em></span>
-operations as well as negating. These patterns can also be used to (for
-example) search for messages or to limit the index to show only matching
-messages.
-</p><p>
-Mutt supports a “<span class="quote">hook</span>” concept which allows the user to execute
-arbitrary configuration commands and functions in certain situations
-such as entering a folder, starting a new message or replying to an
-existing one. These hooks can be used to highly customize Mutt's
-behaviour including managing multiple identities, customizing the
-display for a folder or even implementing auto-archiving based on a
-per-folder basis and much more.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="menus"></a>2. Moving Around in Menus</h2></div></div></div><p>
-The most important navigation keys common to all menus are shown in
-<a class="xref" href="gettingstarted.html#tab-keys-nav" title="Table 2.1. Most common navigation keys">Table 2.1, “Most common navigation keys”</a>.
-</p><div class="table"><a id="tab-keys-nav"></a><p class="title"><b>Table 2.1. Most common navigation keys</b></p><div class="table-contents"><table summary="Most common navigation keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>j or <Down></td><td><code class="literal"><next-entry></code></td><td>move to the next entry</td></tr><tr><td>k or <Up></td><td><code class="literal"><previous-entry></code></td><td>move to the previous entry</td></tr><tr><td>z or <PageDn></td><td><code class="literal"><page-down></code></td><td>go to the next page</td></tr><tr><td>Z or <PageUp></td><td><code class="literal"><page-up></code></td><td>go to the previous page</td></tr><tr><td>= or <Home></td><td><code class="literal"><first-entry></code></td><td>jump to the first entry</td></tr><tr><td>* or <End></td><td><code class="literal"><last-entry></code></td><td>jump to the last entry</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>exit the current menu</td></tr><tr><td>?</td><td><code class="literal"><help></code></td><td>list all keybindings for the current menu</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing"></a>3. Editing Input Fields</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-intro"></a>3.1. Introduction</h3></div></div></div><p>
-Mutt has a built-in line editor for inputting text, e.g. email
-addresses or filenames. The keys used to manipulate text input are
-very similar to those of Emacs. See <a class="xref" href="gettingstarted.html#tab-keys-editor" title="Table 2.2. Most common line editor keys">Table 2.2, “Most common line editor keys”</a> for a full
-reference of available functions, their default key bindings, and
-short descriptions.
-</p><div class="table"><a id="tab-keys-editor"></a><p class="title"><b>Table 2.2. Most common line editor keys</b></p><div class="table-contents"><table summary="Most common line editor keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^A or <Home></td><td><code class="literal"><bol></code></td><td>move to the start of the line</td></tr><tr><td>^B or <Left></td><td><code class="literal"><backward-char></code></td><td>move back one char</td></tr><tr><td>Esc B</td><td><code class="literal"><backward-word></code></td><td>move back one word</td></tr><tr><td>^D or <Delete></td><td><code class="literal"><delete-char></code></td><td>delete the char under the cursor</td></tr><tr><td>^E or <End></td><td><code class="literal"><eol></code></td><td>move to the end of the line</td></tr><tr><td>^F or <Right></td><td><code class="literal"><forward-char></code></td><td>move forward one char</td></tr><tr><td>Esc F</td><td><code class="literal"><forward-word></code></td><td>move forward one word</td></tr><tr><td><Tab></td><td><code class="literal"><complete></code></td><td>complete filename or alias</td></tr><tr><td>^T</td><td><code class="literal"><complete-query></code></td><td>complete address with query</td></tr><tr><td>^K</td><td><code class="literal"><kill-eol></code></td><td>delete to the end of the line</td></tr><tr><td>Esc d</td><td><code class="literal"><kill-eow></code></td><td>delete to the end of the word</td></tr><tr><td>^W</td><td><code class="literal"><kill-word></code></td><td>kill the word in front of the cursor</td></tr><tr><td>^U</td><td><code class="literal"><kill-line></code></td><td>delete entire line</td></tr><tr><td>^V</td><td><code class="literal"><quote-char></code></td><td>quote the next typed key</td></tr><tr><td><Up></td><td><code class="literal"><history-up></code></td><td>recall previous string from history</td></tr><tr><td><Down></td><td><code class="literal"><history-down></code></td><td>recall next string from history</td></tr><tr><td><BackSpace></td><td><code class="literal"><backspace></code></td><td>kill the char in front of the cursor</td></tr><tr><td>Esc u</td><td><code class="literal"><upcase-word></code></td><td>convert word to upper case</td></tr><tr><td>Esc l</td><td><code class="literal"><downcase-word></code></td><td>convert word to lower case</td></tr><tr><td>Esc c</td><td><code class="literal"><capitalize-word></code></td><td>capitalize the word</td></tr><tr><td>^G</td><td>n/a</td><td>abort</td></tr><tr><td><Return></td><td>n/a</td><td>finish editing</td></tr></tbody></table></div></div><br class="table-break" /><p>
-You can remap the <span class="emphasis"><em>editor</em></span> functions using the
-<a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">bind</a> command. For example, to make
-the <Delete> key delete the character in front of
-the cursor rather than under, you could use:
-</p><pre class="screen">
-bind editor <delete> backspace
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-history"></a>3.2. History</h3></div></div></div><p>
-Mutt maintains a history for the built-in editor. The number of items
-is controlled by the <a class="link" href="reference.html#history" title="3.77. history">$history</a>
-variable and can be made persistent using an external file specified
-using <a class="link" href="reference.html#history-file" title="3.78. history_file">$history_file</a>.
-You may cycle through them at an editor prompt by using the
-<code class="literal"><history-up></code> and/or
-<code class="literal"><history-down></code> commands.
-</p><p>
-Mutt maintains several distinct history lists, one for each of the
-following categories:
-</p><div class="itemizedlist"><ul type="disc"><li><p>muttrc commands</p></li><li><p>addresses and aliases</p></li><li><p>shell commands</p></li><li><p>filenames</p></li><li><p>patterns</p></li><li><p>everything else</p></li></ul></div><p>
-Mutt automatically filters out repeated items from the history. It
-also mimics the behavior of some shells by ignoring items starting
-with a space. The latter feature can be useful in macros to not clobber
-the history's valuable entries with unwanted entries.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="reading"></a>4. Reading Mail - The Index and Pager</h2></div></div></div><p>
-Similar to many other mail clients, there are two modes in which mail is
-read in Mutt. The first is the index of messages in the mailbox, which is
-called the “<span class="quote">index</span>” in Mutt. The second mode is the display of the
-message contents. This is called the “<span class="quote">pager.</span>”
-</p><p>
-The next few sections describe the functions provided in each of these
-modes.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-menu"></a>4.1. The Message Index</h3></div></div></div><p>
-Common keys used to navigate through and manage messages in the index
-are shown in <a class="xref" href="gettingstarted.html#tab-key-index" title="Table 2.3. Most common message index keys">Table 2.3, “Most common message index keys”</a>. How messages are presented
-in the index menu can be customized using the
-<a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable.
-</p><div class="table"><a id="tab-key-index"></a><p class="title"><b>Table 2.3. Most common message index keys</b></p><div class="table-contents"><table summary="Most common message index keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td>c</td><td>change to a different mailbox</td></tr><tr><td>Esc c</td><td>change to a folder in read-only mode</td></tr><tr><td>C</td><td>copy the current message to another mailbox</td></tr><tr><td>Esc C</td><td>decode a message and copy it to a folder</td></tr><tr><td>Esc s</td><td>decode a message and save it to a folder</td></tr><tr><td>D</td><td>delete messages matching a pattern</td></tr><tr><td>d</td><td>delete the current message</td></tr><tr><td>F</td><td>mark as important</td></tr><tr><td>l</td><td>show messages matching a pattern</td></tr><tr><td>N</td><td>mark message as new</td></tr><tr><td>o</td><td>change the current sort method</td></tr><tr><td>O</td><td>reverse sort the mailbox</td></tr><tr><td>q</td><td>save changes and exit</td></tr><tr><td>s</td><td>save-message</td></tr><tr><td>T</td><td>tag messages matching a pattern</td></tr><tr><td>t</td><td>toggle the tag on a message</td></tr><tr><td>Esc t</td><td>toggle tag on entire message thread</td></tr><tr><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td>u</td><td>undelete-message</td></tr><tr><td>v</td><td>view-attachments</td></tr><tr><td>x</td><td>abort changes and exit</td></tr><tr><td><Return></td><td>display-message</td></tr><tr><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td>@</td><td>show the author's full e-mail address</td></tr><tr><td>$</td><td>save changes to mailbox</td></tr><tr><td>/</td><td>search</td></tr><tr><td>Esc /</td><td>search-reverse</td></tr><tr><td>^L</td><td>clear and redraw the screen</td></tr><tr><td>^T</td><td>untag messages matching a pattern</td></tr></tbody></table></div></div><br class="table-break" /><p>
-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 “<span class="quote">flags</span>” in <a class="xref" href="gettingstarted.html#tab-msg-status-flags" title="Table 2.4. Message status flags">Table 2.4, “Message status flags”</a>
-may appear, some of which can be turned on or off using these functions:
-<code class="literal"><set-flag></code> and
-<code class="literal"><clear-flag></code>
-bound by default to “<span class="quote">w</span>” and “<span class="quote">W</span>” respectively.
-</p><p>
-Furthermore, the flags in <a class="xref" href="gettingstarted.html#tab-msg-recip-flags" title="Table 2.5. Message recipient flags">Table 2.5, “Message recipient flags”</a> reflect
-who the message is addressed to. They can be customized with the
-<a class="link" href="reference.html#to-chars" title="3.289. to_chars">$to_chars</a> variable.
-</p><div class="table"><a id="tab-msg-status-flags"></a><p class="title"><b>Table 2.4. Message status flags</b></p><div class="table-contents"><table summary="Message status flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>D</td><td>message is deleted (is marked for deletion)</td></tr><tr><td>d</td><td>message has attachments marked for deletion</td></tr><tr><td>K</td><td>contains a PGP public key</td></tr><tr><td>N</td><td>message is new</td></tr><tr><td>O</td><td>message is old</td></tr><tr><td>P</td><td>message is PGP encrypted</td></tr><tr><td>r</td><td>message has been replied to</td></tr><tr><td>S</td><td>message is signed, and the signature is successfully verified</td></tr><tr><td>s</td><td>message is signed</td></tr><tr><td>!</td><td>message is flagged</td></tr><tr><td>*</td><td>message is tagged</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-msg-recip-flags"></a><p class="title"><b>Table 2.5. Message recipient flags</b></p><div class="table-contents"><table summary="Message recipient flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>+</td><td>message is to you and you only</td></tr><tr><td>T</td><td>message is to you, but also to or cc'ed to others</td></tr><tr><td>C</td><td>message is cc'ed to you</td></tr><tr><td>F</td><td>message is from you</td></tr><tr><td>L</td><td>message is sent to a subscribed mailing list</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-menu"></a>4.2. The Pager</h3></div></div></div><p>
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program <span class="emphasis"><em>less</em></span> though not nearly as
-featureful.
-</p><div class="table"><a id="tab-key-pager"></a><p class="title"><b>Table 2.6. Most common pager keys</b></p><div class="table-contents"><table summary="Most common pager keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td><Return></td><td>go down one line</td></tr><tr><td><Space></td><td>display the next page (or next message if at the end of a message)</td></tr><tr><td>-</td><td>go back to the previous page</td></tr><tr><td>n</td><td>search for next match</td></tr><tr><td>S</td><td>skip beyond quoted text</td></tr><tr><td>T</td><td>toggle display of quoted text</td></tr><tr><td>?</td><td>show keybindings</td></tr><tr><td>/</td><td>regular expression search</td></tr><tr><td>Esc /</td><td>backward regular expression search</td></tr><tr><td>\</td><td>toggle highlighting of search matches</td></tr><tr><td>^</td><td>jump to the top of the message</td></tr></tbody></table></div></div><br class="table-break" /><p>
-In addition to key bindings in <a class="xref" href="gettingstarted.html#tab-key-pager" title="Table 2.6. Most common pager keys">Table 2.6, “Most common pager keys”</a>,
-many of the functions from the index menu are also available in
-the pager, such as <code class="literal"><delete-message></code> or <code class="literal"><copy-message></code>
-(this is one advantage over using an external pager to view messages).
-</p><p>
-Also, the internal pager supports a couple other advanced features. For
-one, it will accept and translate the “<span class="quote">standard</span>” nroff sequences for
-bold and underline. These sequences are a series of either the letter,
-backspace (^H), the letter again for bold or the letter, backspace,
-“<span class="quote">_</span>” for denoting underline. Mutt will attempt to display these
-in bold and underline respectively if your terminal supports them. If
-not, you can use the bold and underline <a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">color</a>
-objects to specify a color or mono attribute for them.
-</p><p>
-Additionally, the internal pager supports the ANSI escape sequences for
-character attributes. Mutt translates them into the correct color and
-character settings. The sequences Mutt supports are:
-</p><pre class="screen">
-\e[<span class="emphasis"><em>Ps</em></span>;<span class="emphasis"><em>Ps</em></span>;..<span class="emphasis"><em>Ps</em></span>;m
-</pre><p>
-where <span class="emphasis"><em>Ps</em></span> can be one of the codes shown in
-<a class="xref" href="gettingstarted.html#tab-ansi-esc" title="Table 2.7. ANSI escape sequences">Table 2.7, “ANSI escape sequences”</a>.
-</p><div class="table"><a id="tab-ansi-esc"></a><p class="title"><b>Table 2.7. ANSI escape sequences</b></p><div class="table-contents"><table summary="ANSI escape sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Escape code</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>All attributes off</td></tr><tr><td>1</td><td>Bold on</td></tr><tr><td>4</td><td>Underline on</td></tr><tr><td>5</td><td>Blink on</td></tr><tr><td>7</td><td>Reverse video on</td></tr><tr><td>3<span class="emphasis"><em><color></em></span></td><td>Foreground color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="gettingstarted.html#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr><tr><td>4<span class="emphasis"><em><color></em></span></td><td>Background color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="gettingstarted.html#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-color"></a><p class="title"><b>Table 2.8. Color sequences</b></p><div class="table-contents"><table summary="Color sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Color code</th><th>Color</th></tr></thead><tbody><tr><td>0</td><td>Black</td></tr><tr><td>1</td><td>Red</td></tr><tr><td>2</td><td>Green</td></tr><tr><td>3</td><td>Yellow</td></tr><tr><td>4</td><td>Blue</td></tr><tr><td>5</td><td>Magenta</td></tr><tr><td>6</td><td>Cyan</td></tr><tr><td>7</td><td>White</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Mutt uses these attributes for handling <code class="literal">text/enriched</code>
-messages, and they can also be used by an external
-<a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">autoview</a> script for highlighting
-purposes.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-Note that the search commands in the pager take regular expressions,
-which are not quite the same as the more
-complex <a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> used by the search
-command in the index. This is because the pager only performs simple
-text search, whereas the index provides boolean filtering on several
-aspects of messages.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="threads"></a>4.3. Threaded Mode</h3></div></div></div><p>
-When the mailbox is <a class="link" href="reference.html#sort" title="3.270. sort">sorted</a> by <span class="emphasis"><em>threads</em></span>, there are
-a few additional functions available in the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> modes
-as shown in <a class="xref" href="gettingstarted.html#tab-key-threads" title="Table 2.9. Most common thread mode keys">Table 2.9, “Most common thread mode keys”</a>.
-</p><div class="table"><a id="tab-key-threads"></a><p class="title"><b>Table 2.9. Most common thread mode keys</b></p><div class="table-contents"><table summary="Most common thread mode keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^D</td><td><code class="literal"><delete-thread></code></td><td>delete all messages in the current thread</td></tr><tr><td>^U</td><td><code class="literal"><undelete-thread></code></td><td>undelete all messages in the current thread</td></tr><tr><td>^N</td><td><code class="literal"><next-thread></code></td><td>jump to the start of the next thread</td></tr><tr><td>^P</td><td><code class="literal"><previous-thread></code></td><td>jump to the start of the previous thread</td></tr><tr><td>^R</td><td><code class="literal"><read-thread></code></td><td>mark the current thread as read</td></tr><tr><td>Esc d</td><td><code class="literal"><delete-subthread></code></td><td>delete all messages in the current subthread</td></tr><tr><td>Esc u</td><td><code class="literal"><undelete-subthread></code></td><td>undelete all messages in the current subthread</td></tr><tr><td>Esc n</td><td><code class="literal"><next-subthread></code></td><td>jump to the start of the next subthread</td></tr><tr><td>Esc p</td><td><code class="literal"><previous-subthread></code></td><td>jump to the start of the previous subthread</td></tr><tr><td>Esc r</td><td><code class="literal"><read-subthread></code></td><td>mark the current subthread as read</td></tr><tr><td>Esc t</td><td><code class="literal"><tag-thread></code></td><td>toggle the tag on the current thread</td></tr><tr><td>Esc v</td><td><code class="literal"><collapse-thread></code></td><td>toggle collapse for the current thread</td></tr><tr><td>Esc V</td><td><code class="literal"><collapse-all></code></td><td>toggle collapse for all threads</td></tr><tr><td>P</td><td><code class="literal"><parent-message></code></td><td>jump to parent message in thread</td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><h3 class="title">Note</h3><p>
-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 on
-the screen. See %M in <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>.
-For example, you could use "%?M?(#%03M)&(%4l)?" in <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> to optionally
-display the number of hidden messages if the thread is collapsed.
-</p></div><p>
-See also: <a class="link" href="reference.html#strict-threads" title="3.280. strict_threads">$strict_threads</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reading-misc"></a>4.4. Miscellaneous Functions</h3></div></div></div><p>
-In addition, the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span>
-menus have these interesting functions:
-</p><div class="variablelist"><dl><dt><span class="term">
-<code class="literal"><create-alias></code><a id="create-alias"></a> (default: a)
-</span></dt><dd><p>
-Creates a new alias based upon the current message (or prompts for a
-new one). Once editing is complete, an <a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">alias</a>
-command is added to the file specified by
-the <a class="link" href="reference.html#alias-file" title="3.3. alias_file">$alias_file</a> variable
-for future use
-</p><div class="note"><h3 class="title">Note</h3><p>
-Mutt does not read the <a class="link" href="reference.html#alias-file" title="3.3. alias_file">$alias_file</a>
-upon startup so you must explicitly <a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a> the file.
-</p></div></dd><dt><span class="term">
-<code class="literal"><check-traditional-pgp></code><a id="check-traditional-pgp"></a> (default: Esc P)
-</span></dt><dd><p>
-This function will search the current message for content signed or
-encrypted with PGP the “<span class="quote">traditional</span>” 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 <a class="link" href="gettingstarted.html#edit-type"><code class="literal"><edit-type></code></a> function's
-effect.
-</p></dd><dt><span class="term">
-<code class="literal"><edit></code><a id="edit"></a> (default: e)
-</span></dt><dd><p>
-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; if the message is unchanged it won't be replaced.
-</p></dd><dt><span class="term">
-<code class="literal"><edit-type></code><a id="edit-type"></a> (default:
-^E on the attachment menu, and in the pager and index menus;
-^T on the compose menu)
-</span></dt><dd><p>
-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 class="link" href="mimesupport.html#attach-menu" title="1.2. The Attachment Menu">attachment menu</a>, you can change any
-attachment's content type. These changes are not persistent, and get
-lost upon changing folders.
-</p><p>
-Note that this command is also available on the <a class="link" href="mimesupport.html#compose-menu" title="1.3. The Compose Menu">compose
-menu</a>. There, it's used to fine-tune the properties of attachments you are going
-to send.
-</p></dd><dt><span class="term">
-<code class="literal"><enter-command></code><a id="enter-command"></a> (default: “<span class="quote">:</span>”)
-</span></dt><dd><p>
-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 <a class="link" href="configuration.html#macro" title="8. Keyboard macros">macros</a> to change settings on the
-fly.
-</p></dd><dt><span class="term">
-<code class="literal"><extract-keys></code><a id="extract-keys"></a> (default: ^K)
-</span></dt><dd><p>
-This command extracts PGP public keys from the current or tagged
-message(s) and adds them to your PGP public key ring.
-</p></dd><dt><span class="term">
-<code class="literal"><forget-passphrase></code><a id="forget-passphrase"></a> (default:
-^F)
-</span></dt><dd><p>
-This command wipes the passphrase(s) from memory. It is useful, if
-you misspelled the passphrase.
-</p></dd><dt><span class="term">
-<code class="literal"><list-reply></code><a id="list-reply"></a> (default: L)
-</span></dt><dd><p>
-Reply to the current or tagged message(s) by extracting any addresses which
-match the regular expressions given by the <a class="link" href="configuration.html#lists" title="12. Mailing lists">lists or subscribe</a>
-commands, but also honor any <code class="literal">Mail-Followup-To</code> header(s) if the
-<a class="link" href="reference.html#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a>
-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.
-</p></dd><dt><span class="term">
-<code class="literal"><pipe-message></code><a id="pipe-message"></a> (default: |)
-</span></dt><dd><p>
-Asks for an external Unix command and pipes the current or
-tagged message(s) to it. The variables <a class="link" href="reference.html#pipe-decode" title="3.211. pipe_decode">$pipe_decode</a>, <a class="link" href="reference.html#pipe-split" title="3.210. pipe_split">$pipe_split</a>,
-<a class="link" href="reference.html#pipe-sep" title="3.212. pipe_sep">$pipe_sep</a> and <a class="link" href="reference.html#wait-key" title="3.300. wait_key">$wait_key</a> control the exact behavior of this function.
-</p></dd><dt><span class="term">
-<code class="literal"><resend-message></code><a id="resend-message"></a> (default: Esc e)
-</span></dt><dd><p>
-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 <a class="link" href="reference.html#weed" title="3.301. weed">$weed</a>
-variable.
-</p><p>
-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 <code class="literal">message/rfc822</code> body part.
-</p></dd><dt><span class="term">
-<code class="literal"><shell-escape></code><a id="shell-escape"></a> (default: !)
-</span></dt><dd><p>
-Asks for an external Unix command and executes it. The <a class="link" href="reference.html#wait-key" title="3.300. wait_key">$wait_key</a> can be used to control
-whether Mutt 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. If no command is given, an
-interactive shell is executed.
-</p></dd><dt><span class="term">
-<code class="literal"><toggle-quoted></code><a id="toggle-quoted"></a> (default: T)
-</span></dt><dd><p>
-The pager uses the <a class="link" href="reference.html#quote-regexp" title="3.234. quote_regexp">$quote_regexp</a> variable to detect quoted text when
-displaying the body of the message. This function toggles the display
-of the quoted material in the message. It is particularly useful when
-being interested in just the response and there is a large amount of
-quoted text in the way.
-</p></dd><dt><span class="term">
-<code class="literal"><skip-quoted></code><a id="skip-quoted"></a> (default: S)
-</span></dt><dd><p>
-This function will go to the next line of non-quoted text which comes
-after a line of quoted text in the internal pager.
-</p></dd></dl></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="sending"></a>5. Sending Mail</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-intro"></a>5.1. Introduction</h3></div></div></div><p>
-The bindings shown in <a class="xref" href="gettingstarted.html#tab-key-send" title="Table 2.10. Most common mail sending keys">Table 2.10, “Most common mail sending keys”</a> are available in the
-<span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> to start a new message.
-</p><div class="table"><a id="tab-key-send"></a><p class="title"><b>Table 2.10. Most common mail sending keys</b></p><div class="table-contents"><table summary="Most common mail sending keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>m</td><td><code class="literal"><compose></code></td><td>compose a new message</td></tr><tr><td>r</td><td><code class="literal"><reply></code></td><td>reply to sender</td></tr><tr><td>g</td><td><code class="literal"><group-reply></code></td><td>reply to all recipients</td></tr><tr><td>L</td><td><code class="literal"><list-reply></code></td><td>reply to mailing list address</td></tr><tr><td>f</td><td><code class="literal"><forward></code></td><td>forward message</td></tr><tr><td>b</td><td><code class="literal"><bounce></code></td><td>bounce (remail) message</td></tr><tr><td>Esc k</td><td><code class="literal"><mail-key></code></td><td>mail a PGP public key to someone</td></tr></tbody></table></div></div><br class="table-break" /><p>
-<span class="emphasis"><em>Bouncing</em></span> a message sends the message as-is to the recipient you
-specify. <span class="emphasis"><em>Forwarding</em></span> 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 “<span class="quote"><a class="link" href="gettingstarted.html#forwarding-mail" title="6. Forwarding and Bouncing Mail">Forwarding
-and Bouncing Mail</a>.</span>”
-</p><p>
-Mutt will then enter the <span class="emphasis"><em>compose</em></span> menu and prompt you for the
-recipients to place on the “<span class="quote">To:</span>” header field. Next, it will ask
-you for the “<span class="quote">Subject:</span>” field for the message, providing a default if
-you are replying to or forwarding a message. See also
-<a class="link" href="reference.html#askcc" title="3.10. askcc">$askcc</a>,
-<a class="link" href="reference.html#askbcc" title="3.9. askbcc">$askbcc</a>,
-<a class="link" href="reference.html#autoedit" title="3.17. autoedit">$autoedit</a>,
-<a class="link" href="reference.html#bounce" title="3.21. bounce">$bounce</a>,
-<a class="link" href="reference.html#fast-reply" title="3.55. fast_reply">$fast_reply</a>,
-and <a class="link" href="reference.html#include" title="3.98. include">$include</a>
-for changing how Mutt asks these questions.
-</p><p>
-Mutt will then automatically start your <a class="link" href="reference.html#editor" title="3.51. editor">$editor</a>
-on the message body. If the <a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a>
-variable is set, the headers will be at the top of the message in your editor.
-Any messages you are replying to will be added in sort order to the message,
-with appropriate <a class="link" href="reference.html#attribution" title="3.16. attribution">$attribution</a>,
-<a class="link" href="reference.html#indent-string" title="3.100. indent_string">$indent_string</a> and
-<a class="link" href="reference.html#post-indent-string" title="3.222. post_indent_string">$post_indent_string</a>.
-When forwarding a message, if the <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a>
-variable is unset, a copy of the forwarded message will be included. If
-you have specified a <a class="link" href="reference.html#signature" title="3.262. signature">$signature</a>, it
-will be appended to the message.
-</p><p>
-Once you have finished editing the body of your mail message, you are
-returned to the <span class="emphasis"><em>compose</em></span> menu providing the functions
-shown in <a class="xref" href="gettingstarted.html#tab-func-compose" title="Table 2.11. Most common compose menu keys">Table 2.11, “Most common compose menu keys”</a> to modify, send or postpone the
-message.
-</p><div class="table"><a id="tab-func-compose"></a><p class="title"><b>Table 2.11. Most common compose menu keys</b></p><div class="table-contents"><table summary="Most common compose menu keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>a</td><td><code class="literal"><attach-file></code></td><td>attach a file</td></tr><tr><td>A</td><td><code class="literal"><attach-message></code></td><td>attach message(s) to the message</td></tr><tr><td>Esc k</td><td><code class="literal"><attach-key></code></td><td>attach a PGP public key</td></tr><tr><td>d</td><td><code class="literal"><edit-description></code></td><td>edit description on attachment</td></tr><tr><td>D</td><td><code class="literal"><detach-file></code></td><td>detach a file</td></tr><tr><td>t</td><td><code class="literal"><edit-to></code></td><td>edit the To field</td></tr><tr><td>Esc f</td><td><code class="literal"><edit-from></code></td><td>edit the From field</td></tr><tr><td>r</td><td><code class="literal"><edit-reply-to></code></td><td>edit the Reply-To field</td></tr><tr><td>c</td><td><code class="literal"><edit-cc></code></td><td>edit the Cc field</td></tr><tr><td>b</td><td><code class="literal"><edit-bcc></code></td><td>edit the Bcc field</td></tr><tr><td>y</td><td><code class="literal"><send-message></code></td><td>send the message</td></tr><tr><td>s</td><td><code class="literal"><edit-subject></code></td><td>edit the Subject</td></tr><tr><td>S</td><td><code class="literal"><smime-menu></code></td><td>select S/MIME options</td></tr><tr><td>f</td><td><code class="literal"><edit-fcc></code></td><td>specify an “<span class="quote">Fcc</span>” mailbox</td></tr><tr><td>p</td><td><code class="literal"><pgp-menu></code></td><td>select PGP options</td></tr><tr><td>P</td><td><code class="literal"><postpone-message></code></td><td>postpone this message until later</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>quit (abort) sending the message</td></tr><tr><td>w</td><td><code class="literal"><write-fcc></code></td><td>write the message to a folder</td></tr><tr><td>i</td><td><code class="literal"><ispell></code></td><td>check spelling (if available on your system)</td></tr><tr><td>^F</td><td><code class="literal"><forget-passphrase></code></td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The compose menu is also used to edit the attachments for a message which can be either files
-or other messages. The <code class="literal"><attach-message></code> function to will prompt you for a folder to
-attach messages from. You can now tag messages in that folder and they
-will be attached to the message you are sending.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that certain
-operations like composing a new mail, replying, forwarding, etc. are
-not permitted when you are in that folder. The %r in
-<a class="link" href="reference.html#status-format" title="3.278. status_format">$status_format</a> will change to
-a “<span class="quote">A</span>” to indicate that you are in attach-message mode.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-header"></a>5.2. Editing the message header</h3></div></div></div><p>
-When editing the header because of <a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a>
-being set, there are a several pseudo headers available which
-will not be included in sent messages.
-</p><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="fcc-header"></a>5.2.1. Fcc: pseudo header</h4></div></div></div><p>
-If you specify
-
-<code class="literal">Fcc:</code> <span class="emphasis"><em>filename</em></span>
-
-as a header, Mutt will pick up <span class="emphasis"><em>filename</em></span>
-just as if you had used the <code class="literal"><edit-fcc></code> function in the <span class="emphasis"><em>compose</em></span> menu.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="attach-header"></a>5.2.2. Attach: pseudo header</h4></div></div></div><p>
-You can also attach files to your message by specifying
-
-<code class="literal">Attach:</code> <span class="emphasis"><em>filename</em></span> [ <span class="emphasis"><em>description</em></span> ]
-
-where <span class="emphasis"><em>filename</em></span> is the file to attach and <span class="emphasis"><em>description</em></span> is an
-optional string to use as the description of the attached file.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="pgp-header"></a>5.2.3. Pgp: pseudo header</h4></div></div></div><p>
-If you want to use PGP, you can specify
-</p><p>
-<code class="literal">Pgp:</code> [ <code class="literal">E</code> | <code class="literal">S</code> | <code class="literal">S</code><span class="emphasis"><em><id></em></span> ]
-
-</p><p>
-“<span class="quote">E</span>” selects encryption, “<span class="quote">S</span>” selects signing and
-“<span class="quote">S<id></span>” selects signing with the given key, setting
-<a class="link" href="reference.html#pgp-sign-as" title="3.163. pgp_sign_as">$pgp_sign_as</a>
-permanently.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="in-reply-to-header"></a>5.2.4. In-Reply-To: header</h4></div></div></div><p>
-When replying to messages, the <span class="emphasis"><em>In-Reply-To:</em></span> header contains the
-Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
-<span class="emphasis"><em>References:</em></span> field, which allows you to create a new message thread, for example
-to create a new message to a mailing list without having to enter the mailing list's address.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-crypto"></a>5.3. Sending cryptographically signed/encrypted messages</h3></div></div></div><p>
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
-through a key selection process when you try to send the message.
-Mutt 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.
-</p><p>
-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 <code class="literal">^G</code>. When you do so, mutt will
-return to the compose screen.
-</p><p>
-Once you have successfully finished the key selection, the message
-will be encrypted using the selected public keys when sent out.
-</p><p>
-Most fields of the entries in the key selection menu (see also <a class="link" href="reference.html#pgp-entry-format" title="3.155. pgp_entry_format">$pgp_entry_format</a>)
-have obvious meanings. But some explanations on the capabilities, flags,
-and validity fields are in order.
-</p><p>
-The flags sequence (%f) will expand to one of the flags in
-<a class="xref" href="gettingstarted.html#tab-pgp-menuflags" title="Table 2.12. PGP key menu flags">Table 2.12, “PGP key menu flags”</a>.
-</p><div class="table"><a id="tab-pgp-menuflags"></a><p class="title"><b>Table 2.12. PGP key menu flags</b></p><div class="table-contents"><table summary="PGP key menu flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>R</td><td>The key has been revoked and can't be used.</td></tr><tr><td>X</td><td>The key is expired and can't be used.</td></tr><tr><td>d</td><td>You have marked the key as disabled.</td></tr><tr><td>c</td><td>There are unknown critical self-signature packets.</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The capabilities field (%c) expands to a two-character sequence
-representing a key's capabilities. The first character gives
-the key's encryption capabilities: A minus sign (“<span class="quote">-</span>”) means
-that the key cannot be used for encryption. A dot (“<span class="quote">.</span>”) means that
-it's marked as a signature key in one of the user IDs, but may
-also be used for encryption. The letter “<span class="quote">e</span>” indicates that
-this key can be used for encryption.
-</p><p>
-The second character indicates the key's signing capabilities. Once
-again, a “<span class="quote">-</span>” implies “<span class="quote">not for signing</span>”, “<span class="quote">.</span>” implies
-that the key is marked as an encryption key in one of the user-ids, and
-“<span class="quote">s</span>” denotes a key which can be used for signing.
-</p><p>
-Finally, the validity field (%t) indicates how well-certified a user-id
-is. A question mark (“<span class="quote">?</span>”) indicates undefined validity, a minus
-character (“<span class="quote">-</span>”) marks an untrusted association, a space character
-means a partially trusted association, and a plus character (“<span class="quote">+</span>”)
-indicates complete validity.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-mixmaster"></a>5.4. Sending anonymous messages via mixmaster</h3></div></div></div><p>
-You may also have compiled 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.
-</p><p>
-To use it, you'll have to obey certain restrictions. Most
-important, you cannot use the <code class="literal">Cc</code> and <code class="literal">Bcc</code> headers. To tell
-Mutt to use mixmaster, you have to select a remailer chain, using
-the mix function on the compose menu.
-</p><p>
-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.
-</p><p>
-You can navigate in the chain using the <code class="literal"><chain-prev></code> and
-<code class="literal"><chain-next></code> functions, which are by default bound to the left
-and right arrows and to the <code class="literal">h</code> and <code class="literal">l</code> keys (think vi
-keyboard bindings). To insert a remailer at the current chain
-position, use the <code class="literal"><insert></code> function. To append a remailer behind
-the current chain position, use <code class="literal"><select-entry></code> or <code class="literal"><append></code>.
-You can also delete entries from the chain, using the corresponding
-function. Finally, to abandon your changes, leave the menu, or
-<code class="literal"><accept></code> them pressing (by default) the <code class="literal">Return</code> key.
-</p><p>
-Note that different remailers do have different capabilities,
-indicated in the %c entry of the remailer menu lines (see
-<a class="link" href="reference.html#mix-entry-format" title="3.130. mix_entry_format">$mix_entry_format</a>). Most important is
-the “<span class="quote">middleman</span>” capability, indicated by a capital “<span class="quote">M</span>”: 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ff"></a>5.5. Sending format=flowed messages</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-concept"></a>5.5.1. Concept</h4></div></div></div><p>
-<code class="literal">format=flowed</code>-style messages (or <code class="literal">f=f</code>
-for short) are <code class="literal">text/plain</code> messages that consist of paragraphs which a receiver's
-mail client may reformat to its own needs which mostly means to
-customize line lengths regardless of what the sender sent. Technically this is
-achieved by letting lines of a “<span class="quote">flowable</span>” paragraph end in spaces
-except for the last line.
-</p><p>
-While for text-mode clients like mutt it's the best way to assume only a
-standard 80x25 character cell terminal, it may be desired to let the
-receiver decide completely how to view a message.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-support"></a>5.5.2. Mutt support</h4></div></div></div><p>
-Mutt only supports setting the required <code class="literal">format=flowed</code>
-MIME parameter on outgoing messages if the <a class="link" href="reference.html#text-flowed" title="3.282. text_flowed">$text_flowed</a>
-variable is set, specifically it does not add the
-trailing spaces.
-</p><p>
-After editing the initial message text and before entering
-the compose menu, mutt properly space-stuffes the message.
-<span class="emphasis"><em>Space-stuffing</em></span> is required by RfC3676 defining
-<code class="literal">format=flowed</code> and means to prepend a space to:
-</p><div class="itemizedlist"><ul type="disc"><li><p>all lines starting with a space</p></li><li><p>lines starting with the word “<span class="quote"><code class="literal">From</code></span>”
-followed by space</p></li><li><p>all lines starting with “<span class="quote"><code class="literal">></code></span>” which
-is not intended to be a quote character</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
-Mutt only supports space-stuffing
-for the first two types of lines but not for the third: It is impossible to
-safely detect whether a leading <code class="literal">></code> character starts a
-quote or not. Furthermore, Mutt only applies space-stuffing
-<span class="emphasis"><em>once</em></span> after the initial edit is finished.
-</p></div><p>
-All leading spaces are to be removed by receiving clients to restore
-the original message prior to further processing.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-editor"></a>5.5.3. Editor considerations</h4></div></div></div><p>
-As mutt provides no additional features to compose <code class="literal">f=f</code>
-messages, it's completely up to the user and his editor to produce
-proper messages. Please consider your editor's documentation if you
-intend to send <code class="literal">f=f</code> messages.
-</p><p>
-Please note that when editing messages from the compose menu several
-times before really sending a mail, it's up to the user to ensure that
-the message is properly space-stuffed.
-</p><p>
-For example, <span class="emphasis"><em>vim</em></span> provides the <code class="literal">w</code>
-flag for its <code class="literal">formatoptions</code> setting to assist in
-creating <code class="literal">f=f</code> messages, see <code class="literal">:help
-fo-table</code> for details.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="forwarding-mail"></a>6. Forwarding and Bouncing Mail</h2></div></div></div><p>
-Bouncing and forwarding let you send an existing message to recipients
-that you specify. Bouncing a message sends a verbatim copy of a message
-to alternative addresses as if they were the message's original
-recipients specified in the Bcc header.
-Forwarding a message, on the other hand, allows you to modify the message
-before it is resent (for example, by adding your own comments). Bouncing
-is done using the <code class="literal"><bounce></code> function and forwarding
-using the <code class="literal"><forward></code> function bound to “<span class="quote">b</span>” and “<span class="quote">f</span>”
-respectively.
-</p><p>
-Forwarding can be done by including the original message in the new
-message's body (surrounded by indicating lines) or including it as a MIME
-attachment, depending on the value of the <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> variable. Decoding of attachments,
-like in the pager, can be controlled by the <a class="link" href="reference.html#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="reference.html#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> variables,
-respectively. The desired forwarding format may depend on the content,
-therefore <span class="emphasis"><em>$mime_forward</em></span> is a quadoption which, for
-example, can be set to “<span class="quote">ask-no</span>”.
-</p><p>
-The inclusion of headers is controlled by the current setting of the
-<a class="link" href="reference.html#weed" title="3.301. weed">$weed</a> variable, unless <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is set.
-</p><p>
-Editing the message to forward follows the same procedure as sending or
-replying to a message does.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="postponing-mail"></a>7. Postponing Mail</h2></div></div></div><p>
-At times it is desirable to delay sending a message that you have
-already begun to compose. When the <code class="literal"><postpone-message></code> function is
-used in the <span class="emphasis"><em>compose</em></span> menu, the body of your message and attachments
-are stored in the mailbox specified by the <a class="link" href="reference.html#postponed" title="3.224. postponed">$postponed</a> variable. This means that you can recall the
-message even if you exit Mutt and then restart it at a later time.
-</p><p>
-Once a message is postponed, there are several ways to resume it. From the
-command line you can use the “<span class="quote">-p</span>” option, or if you compose a new
-message from the <span class="emphasis"><em>index</em></span> or <span class="emphasis"><em>pager</em></span> you will be prompted if postponed
-messages exist. If multiple messages are currently postponed, the
-<span class="emphasis"><em>postponed</em></span> menu will pop up and you can select which message you would
-like to resume.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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.
-</p></div><p>
-See also the <a class="link" href="reference.html#postpone" title="3.223. postpone">$postpone</a> quad-option.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="intro.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="configuration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. Introduction </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Configuration</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Mutt E-Mail Client</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><meta name="description" content="All mail clients suck. This one just sucks less. -me, circa 1995" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="next" href="intro.html" title="Chapter 1. Introduction" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The Mutt E-Mail Client</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="intro.html">Next</a></td></tr></table><hr /></div><div class="book" lang="en" xml:lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="id2521827"></a>The Mutt E-Mail Client</h1></div><div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Elkins</span></h3><code class="email"><<a class="email" href="mailto:me@cs.hmc.edu">me@cs.hmc.edu</a>></code></div></div><div><p class="releaseinfo">version 1.5.19 (2009-01-05)</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
-“<span class="quote">All mail clients suck. This one just sucks less.</span>” -me, circa 1995
-</p></div></div></div><hr /></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="intro.html">1. Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="intro.html#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="intro.html#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="intro.html#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="intro.html#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="intro.html#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="intro.html#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="intro.html#copyright">7. Copyright</a></span></dt></dl></dd><dt><span class="chapter"><a href="gettingstarted.html">2. Getting Started</a></span></dt><dd><dl><dt><span class="sect1"><a href="gettingstarted.html#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="gettingstarted.html#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="gettingstarted.html#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="gettingstarted.html#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="gettingstarted.html#postponing-mail">7. Postponing Mail</a></span></dt></dl></dd><dt><span class="chapter"><a href="configuration.html">3. Configuration</a></span></dt><dd><dl><dt><span class="sect1"><a href="configuration.html#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="configuration.html#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="configuration.html#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="configuration.html#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="configuration.html#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="configuration.html#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="configuration.html#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="configuration.html#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="configuration.html#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="configuration.html#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="configuration.html#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="configuration.html#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="configuration.html#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="configuration.html#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="configuration.html#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="configuration.html#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="configuration.html#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="configuration.html#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="configuration.html#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="configuration.html#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="configuration.html#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="configuration.html#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="configuration.html#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="configuration.html#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="configuration.html#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="configuration.html#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="configuration.html#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="configuration.html#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="configuration.html#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="configuration.html#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="configuration.html#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="configuration.html#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="configuration.html#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="configuration.html#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="advancedusage.html">4. Advanced Usage</a></span></dt><dd><dl><dt><span class="sect1"><a href="advancedusage.html#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="advancedusage.html#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="advancedusage.html#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="advancedusage.html#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="advancedusage.html#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></dd><dt><span class="chapter"><a href="mimesupport.html">5. Mutt's MIME Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="mimesupport.html#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="mimesupport.html#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="mimesupport.html#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="mimesupport.html#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="mimesupport.html#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="mimesupport.html#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#mime-lookup">7. MIME Lookup</a></span></dt></dl></dd><dt><span class="chapter"><a href="optionalfeatures.html">6. Optional features</a></span></dt><dd><dl><dt><span class="sect1"><a href="optionalfeatures.html#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#exact-address">8. Exact address generation</a></span></dt></dl></dd><dt><span class="chapter"><a href="tuning.html">7. Performance tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="tuning.html#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="tuning.html#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="tuning.html#tuning-search">3. Searching and limiting</a></span></dt></dl></dd><dt><span class="chapter"><a href="reference.html">8. Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="reference.html#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="reference.html#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="reference.html#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="reference.html#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="reference.html#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="reference.html#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="reference.html#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="reference.html#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="reference.html#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="reference.html#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="reference.html#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="reference.html#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="reference.html#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="reference.html#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="reference.html#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="reference.html#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="reference.html#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="reference.html#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="reference.html#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="reference.html#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="reference.html#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="reference.html#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="reference.html#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="reference.html#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="reference.html#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="reference.html#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="reference.html#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="reference.html#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="reference.html#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="reference.html#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="reference.html#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="reference.html#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="reference.html#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="reference.html#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="reference.html#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="reference.html#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="reference.html#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="reference.html#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="reference.html#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="reference.html#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="reference.html#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="reference.html#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="reference.html#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="reference.html#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="reference.html#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="reference.html#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="reference.html#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="reference.html#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="reference.html#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="reference.html#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="reference.html#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="reference.html#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="reference.html#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="reference.html#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="reference.html#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="reference.html#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="reference.html#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="reference.html#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="reference.html#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="reference.html#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="reference.html#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="reference.html#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="reference.html#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="reference.html#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="reference.html#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="reference.html#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="reference.html#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="reference.html#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="reference.html#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="reference.html#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="reference.html#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="reference.html#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="reference.html#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="reference.html#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="reference.html#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="reference.html#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="reference.html#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="reference.html#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="reference.html#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="reference.html#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="reference.html#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="reference.html#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="reference.html#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="reference.html#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="reference.html#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="reference.html#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="reference.html#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="reference.html#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="reference.html#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="reference.html#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="reference.html#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="reference.html#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="reference.html#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-use-gpg-agent">3.150. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-verify-sig">3.151. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-is-default">3.152. smime_is_default</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-ask-cert-label">3.153. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-decrypt-use-default-key">3.154. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-entry-format">3.155. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-good-sign">3.156. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-check-exit">3.157. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-long-ids">3.158. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-retainable-sigs">3.159. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-autoinline">3.160. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-replyinline">3.161. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-show-unusable">3.162. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sign-as">3.163. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-strict-enc">3.164. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-timeout">3.165. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sort-keys">3.166. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-auto">3.167. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-auto-decode">3.168. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-signature-filename">3.169. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-signature-description">3.170. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-decode-command">3.171. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-getkeys-command">3.172. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-verify-command">3.173. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-decrypt-command">3.174. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-clearsign-command">3.175. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sign-command">3.176. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-encrypt-sign-command">3.177. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-encrypt-only-command">3.178. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-import-command">3.179. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-export-command">3.180. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-verify-key-command">3.181. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-list-secring-command">3.182. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-list-pubring-command">3.183. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-decrypt">3.184. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-timeout">3.185. smime_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-encrypt-with">3.186. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-keys">3.187. smime_keys</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-ca-location">3.188. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-certificates">3.189. smime_certificates</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-decrypt-command">3.190. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-verify-command">3.191. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-verify-opaque-command">3.192. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-sign-command">3.193. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-sign-opaque-command">3.194. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-encrypt-command">3.195. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-pk7out-command">3.196. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-cert-command">3.197. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-signer-cert-command">3.198. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-import-cert-command">3.199. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-cert-email-command">3.200. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-default-key">3.201. smime_default_key</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-client-cert">3.202. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-force-tls">3.203. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-starttls">3.204. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="reference.html#certificate-file">3.205. certificate_file</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-use-sslv3">3.206. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-use-tlsv1">3.207. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-min-dh-prime-bits">3.208. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-ca-certificates-file">3.209. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-split">3.210. pipe_split</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-decode">3.211. pipe_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-sep">3.212. pipe_sep</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-authenticators">3.213. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-auth-try-all">3.214. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-checkinterval">3.215. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-delete">3.216. pop_delete</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-host">3.217. pop_host</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-last">3.218. pop_last</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-reconnect">3.219. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-user">3.220. pop_user</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-pass">3.221. pop_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#post-indent-string">3.222. post_indent_string</a></span></dt><dt><span class="sect2"><a href="reference.html#postpone">3.223. postpone</a></span></dt><dt><span class="sect2"><a href="reference.html#postponed">3.224. postponed</a></span></dt><dt><span class="sect2"><a href="reference.html#preconnect">3.225. preconnect</a></span></dt><dt><span class="sect2"><a href="reference.html#print">3.226. print</a></span></dt><dt><span class="sect2"><a href="reference.html#print-command">3.227. print_command</a></span></dt><dt><span class="sect2"><a href="reference.html#print-decode">3.228. print_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#print-split">3.229. print_split</a></span></dt><dt><span class="sect2"><a href="reference.html#prompt-after">3.230. prompt_after</a></span></dt><dt><span class="sect2"><a href="reference.html#query-command">3.231. query_command</a></span></dt><dt><span class="sect2"><a href="reference.html#query-format">3.232. query_format</a></span></dt><dt><span class="sect2"><a href="reference.html#quit">3.233. quit</a></span></dt><dt><span class="sect2"><a href="reference.html#quote-regexp">3.234. quote_regexp</a></span></dt><dt><span class="sect2"><a href="reference.html#read-inc">3.235. read_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#read-only">3.236. read_only</a></span></dt><dt><span class="sect2"><a href="reference.html#realname">3.237. realname</a></span></dt><dt><span class="sect2"><a href="reference.html#recall">3.238. recall</a></span></dt><dt><span class="sect2"><a href="reference.html#record">3.239. record</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-regexp">3.240. reply_regexp</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-self">3.241. reply_self</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-to">3.242. reply_to</a></span></dt><dt><span class="sect2"><a href="reference.html#resolve">3.243. resolve</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-alias">3.244. reverse_alias</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-name">3.245. reverse_name</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-realname">3.246. reverse_realname</a></span></dt><dt><span class="sect2"><a href="reference.html#rfc2047-parameters">3.247. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="reference.html#save-address">3.248. save_address</a></span></dt><dt><span class="sect2"><a href="reference.html#save-empty">3.249. save_empty</a></span></dt><dt><span class="sect2"><a href="reference.html#save-history">3.250. save_history</a></span></dt><dt><span class="sect2"><a href="reference.html#save-name">3.251. save_name</a></span></dt><dt><span class="sect2"><a href="reference.html#score">3.252. score</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-delete">3.253. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-flag">3.254. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-read">3.255. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="reference.html#send-charset">3.256. send_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#sendmail">3.257. sendmail</a></span></dt><dt><span class="sect2"><a href="reference.html#sendmail-wait">3.258. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="reference.html#shell">3.259. shell</a></span></dt><dt><span class="sect2"><a href="reference.html#sig-dashes">3.260. sig_dashes</a></span></dt><dt><span class="sect2"><a href="reference.html#sig-on-top">3.261. sig_on_top</a></span></dt><dt><span class="sect2"><a href="reference.html#signature">3.262. signature</a></span></dt><dt><span class="sect2"><a href="reference.html#simple-search">3.263. simple_search</a></span></dt><dt><span class="sect2"><a href="reference.html#smart-wrap">3.264. smart_wrap</a></span></dt><dt><span class="sect2"><a href="reference.html#smileys">3.265. smileys</a></span></dt><dt><span class="sect2"><a href="reference.html#sleep-time">3.266. sleep_time</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-authenticators">3.267. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-pass">3.268. smtp_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-url">3.269. smtp_url</a></span></dt><dt><span class="sect2"><a href="reference.html#sort">3.270. sort</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-alias">3.271. sort_alias</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-aux">3.272. sort_aux</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-browser">3.273. sort_browser</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-re">3.274. sort_re</a></span></dt><dt><span class="sect2"><a href="reference.html#spam-separator">3.275. spam_separator</a></span></dt><dt><span class="sect2"><a href="reference.html#spoolfile">3.276. spoolfile</a></span></dt><dt><span class="sect2"><a href="reference.html#status-chars">3.277. status_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#status-format">3.278. status_format</a></span></dt><dt><span class="sect2"><a href="reference.html#status-on-top">3.279. status_on_top</a></span></dt><dt><span class="sect2"><a href="reference.html#strict-threads">3.280. strict_threads</a></span></dt><dt><span class="sect2"><a href="reference.html#suspend">3.281. suspend</a></span></dt><dt><span class="sect2"><a href="reference.html#text-flowed">3.282. text_flowed</a></span></dt><dt><span class="sect2"><a href="reference.html#thread-received">3.283. thread_received</a></span></dt><dt><span class="sect2"><a href="reference.html#thorough-search">3.284. thorough_search</a></span></dt><dt><span class="sect2"><a href="reference.html#tilde">3.285. tilde</a></span></dt><dt><span class="sect2"><a href="reference.html#time-inc">3.286. time_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#timeout">3.287. timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#tmpdir">3.288. tmpdir</a></span></dt><dt><span class="sect2"><a href="reference.html#to-chars">3.289. to_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#trash">3.290. trash</a></span></dt><dt><span class="sect2"><a href="reference.html#tunnel">3.291. tunnel</a></span></dt><dt><span class="sect2"><a href="reference.html#use-8bitmime">3.292. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="reference.html#use-domain">3.293. use_domain</a></span></dt><dt><span class="sect2"><a href="reference.html#use-envelope-from">3.294. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="reference.html#use-from">3.295. use_from</a></span></dt><dt><span class="sect2"><a href="reference.html#use-idn">3.296. use_idn</a></span></dt><dt><span class="sect2"><a href="reference.html#use-ipv6">3.297. use_ipv6</a></span></dt><dt><span class="sect2"><a href="reference.html#user-agent">3.298. user_agent</a></span></dt><dt><span class="sect2"><a href="reference.html#visual">3.299. visual</a></span></dt><dt><span class="sect2"><a href="reference.html#wait-key">3.300. wait_key</a></span></dt><dt><span class="sect2"><a href="reference.html#weed">3.301. weed</a></span></dt><dt><span class="sect2"><a href="reference.html#wrap">3.302. wrap</a></span></dt><dt><span class="sect2"><a href="reference.html#wrap-search">3.303. wrap_search</a></span></dt><dt><span class="sect2"><a href="reference.html#wrapmargin">3.304. wrapmargin</a></span></dt><dt><span class="sect2"><a href="reference.html#write-inc">3.305. write_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#write-bcc">3.306. write_bcc</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-icon">3.307. xterm_icon</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-set-titles">3.308. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-title">3.309. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="reference.html#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="reference.html#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="reference.html#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="reference.html#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="reference.html#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="reference.html#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="reference.html#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="reference.html#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="reference.html#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="reference.html#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="reference.html#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="reference.html#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="reference.html#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="miscellany.html">9. Miscellany</a></span></dt><dd><dl><dt><span class="sect1"><a href="miscellany.html#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="miscellany.html#about">2. About this document</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1.1. <a href="intro.html#tab-typo">Typographical conventions for special terms</a></dt><dt>2.1. <a href="gettingstarted.html#tab-keys-nav">Most common navigation keys</a></dt><dt>2.2. <a href="gettingstarted.html#tab-keys-editor">Most common line editor keys</a></dt><dt>2.3. <a href="gettingstarted.html#tab-key-index">Most common message index keys</a></dt><dt>2.4. <a href="gettingstarted.html#tab-msg-status-flags">Message status flags</a></dt><dt>2.5. <a href="gettingstarted.html#tab-msg-recip-flags">Message recipient flags</a></dt><dt>2.6. <a href="gettingstarted.html#tab-key-pager">Most common pager keys</a></dt><dt>2.7. <a href="gettingstarted.html#tab-ansi-esc">ANSI escape sequences</a></dt><dt>2.8. <a href="gettingstarted.html#tab-color">Color sequences</a></dt><dt>2.9. <a href="gettingstarted.html#tab-key-threads">Most common thread mode keys</a></dt><dt>2.10. <a href="gettingstarted.html#tab-key-send">Most common mail sending keys</a></dt><dt>2.11. <a href="gettingstarted.html#tab-func-compose">Most common compose menu keys</a></dt><dt>2.12. <a href="gettingstarted.html#tab-pgp-menuflags">PGP key menu flags</a></dt><dt>3.1. <a href="configuration.html#tab-key-names">Symbolic key names</a></dt><dt>4.1. <a href="advancedusage.html#posix-regex-char-classes">POSIX regular expression character classes</a></dt><dt>4.2. <a href="advancedusage.html#regex-repeat">Regular expression repetition operators</a></dt><dt>4.3. <a href="advancedusage.html#regex-gnu-ext">GNU regular expression extensions</a></dt><dt>4.4. <a href="advancedusage.html#tab-patterns">Pattern modifiers</a></dt><dt>4.5. <a href="advancedusage.html#tab-simplesearch-keywords">Simple search keywords</a></dt><dt>4.6. <a href="advancedusage.html#tab-date-units">Date units</a></dt><dt>8.1. <a href="reference.html#tab-commandline-options">Command line options</a></dt><dt>8.2. <a href="reference.html#generic_table">Default generic function bindings</a></dt><dt>8.3. <a href="reference.html#index_table">Default index function bindings</a></dt><dt>8.4. <a href="reference.html#pager_table">Default pager function bindings</a></dt><dt>8.5. <a href="reference.html#alias_table">Default alias function bindings</a></dt><dt>8.6. <a href="reference.html#query_table">Default query function bindings</a></dt><dt>8.7. <a href="reference.html#attach_table">Default attach function bindings</a></dt><dt>8.8. <a href="reference.html#compose_table">Default compose function bindings</a></dt><dt>8.9. <a href="reference.html#postpone_table">Default postpone function bindings</a></dt><dt>8.10. <a href="reference.html#browser_table">Default browser function bindings</a></dt><dt>8.11. <a href="reference.html#pgp_table">Default pgp function bindings</a></dt><dt>8.12. <a href="reference.html#smime_table">Default smime function bindings</a></dt><dt>8.13. <a href="reference.html#mix_table">Default mix function bindings</a></dt><dt>8.14. <a href="reference.html#editor_table">Default editor function bindings</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>3.1. <a href="configuration.html#ex-rc-multiple-cmds">Multiple configuration commands per line</a></dt><dt>3.2. <a href="configuration.html#ex-ec-comment">Commenting configuration files</a></dt><dt>3.3. <a href="configuration.html#ex-rc-quote">Escaping quotes in congfiguration files</a></dt><dt>3.4. <a href="configuration.html#ex-rc-backtick">Using external command's output in configuration files</a></dt><dt>3.5. <a href="configuration.html#ex-rc-env">Using environment variables in configuration files</a></dt><dt>3.6. <a href="configuration.html#ex-alias-external">Configuring external alias files</a></dt><dt>3.7. <a href="configuration.html#ex-folder-sorting">Setting sort method based on mailbox name</a></dt><dt>3.8. <a href="configuration.html#ex-header-weeding">Header weeding</a></dt><dt>3.9. <a href="configuration.html#ex-hdr-order">Configuring header display order</a></dt><dt>3.10. <a href="configuration.html#ex-my-hdr">Defining custom headers</a></dt><dt>3.11. <a href="configuration.html#ex-save-hook-exando">Using %-expandos in <code class="literal">save-hook</code></a></dt><dt>3.12. <a href="configuration.html#ex-folder-hook-push">Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></a></dt><dt>3.13. <a href="configuration.html#ex-spam">Configuring spam detection</a></dt><dt>3.14. <a href="configuration.html#ex-myvar1">Using user-defined variables for config file readability</a></dt><dt>3.15. <a href="configuration.html#ex-myvar2">Using user-defined variables for backing up other config option values</a></dt><dt>3.16. <a href="configuration.html#ex-myvar3">Deferring user-defined variable expansion to runtime</a></dt><dt>3.17. <a href="configuration.html#ex-fmtpipe">Using external filters in format strings</a></dt><dt>4.1. <a href="advancedusage.html#ex-pattern-bool">Using boolean operators in patterns</a></dt><dt>4.2. <a href="advancedusage.html#ex-send-hook-my-hdr">Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></a></dt><dt>5.1. <a href="mimesupport.html#ex-attach-count">Attachment counting</a></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="compressedfolders"></a>1. Compressed folders Support (OPTIONAL)</h2></div></div></div><p>
-If Mutt was compiled with compressed folders support (by running the
-<span class="emphasis"><em>configure</em></span> script with the
-<span class="emphasis"><em>--enable-compressed</em></span> flag), Mutt can open folders
-stored in an arbitrary format, provided that the user has a script to
-convert from/to this format to one of the accepted.
-
-The most common use is to open compressed archived folders e.g. with
-gzip.
-
-In addition, the user can provide a script that gets a folder in an
-accepted format and appends its context to the folder in the
-user-defined format, which may be faster than converting the entire
-folder to the accepted format, appending to it and converting back to
-the user-defined format.
-
-There are three hooks defined (<a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a>, <a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> and <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>) which define commands to
-uncompress and compress a folder and to append messages to an existing
-compressed folder respectively.
-
-For example:
-
-</p><pre class="screen">
-open-hook \\.gz$ "gzip -cd %f > %t"
-close-hook \\.gz$ "gzip -c %t > %f"
-append-hook \\.gz$ "gzip -c %t >> %f"
-</pre><p>
-
-You do not have to specify all of the commands. If you omit <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>, the folder will be open and
-closed again each time you will add to it. If you omit <a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> (or give empty command) , the
-folder will be open in the mode. If you specify <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> though you'll be able to
-append to the folder.
-
-Note that Mutt 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
-<a class="link" href="reference.html#save-empty" title="3.249. save_empty">$save_empty</a>, so that
-the compressed file will be removed if you delete all of the messages.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="open-hook"></a>1.1. Open a compressed mailbox for reading</h3></div></div></div><p>
-Usage: <code class="literal">open-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-The <span class="emphasis"><em>command</em></span> is the command that can be used for
-opening the folders whose names match <span class="emphasis"><em>regexp</em></span>.
-
-The <span class="emphasis"><em>command</em></span> string is the printf-like format
-string, and it should accept two parameters: %f, which is
-replaced with the (compressed) folder name, and %t which is
-replaced with the name of the temporary folder to which to write.
-
-%f and %t can be repeated any number of times in the
-command string, and all of the entries are replaced with the
-appropriate folder name. In addition, %% is replaced by
-%, as in printf, and any other %anything is left as is.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the original compressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-open-hook \\.gz$ "gzip -cd %f > %t"
-</pre><p>
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="close-hook"></a>1.2. Write a compressed mailbox</h3></div></div></div><p>
-Usage: <code class="literal">close-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-This is used to close the folder that was open with the <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command after some changes were
-made to it.
-
-The <span class="emphasis"><em>command</em></span> string is the command that can be
-used for closing the folders whose names match
-<span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. Temporary folder in this
-case is the folder previously produced by the <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-close-hook \\.gz$ "gzip -c %t > %f"
-</pre><p>
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type, and the file can only be open in the
-read-only mode.
-
-<a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is not called when you
-exit from the folder if the folder was not changed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="append-hook"></a>1.3. Append a message to a compressed mailbox</h3></div></div></div><p>
-Usage: <code class="literal">append-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-This command is used for saving to an existing compressed folder. The
-<span class="emphasis"><em>command</em></span> is the command that can be used for
-appending to the folders whose names match
-<span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. The temporary folder in
-this case contains the messages that are being appended.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-append-hook \\.gz$ "gzip -c %t >> %f"
-</pre><p>
-
-When <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> 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 (<a class="link" href="reference.html#mbox-type" title="3.117. mbox_type">$mbox_type</a>) type is always
-supposed (i.e. this is the format used for the temporary folder).
-
-If the file does not exist when you save to it, <a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is called, and not <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>. <a class="link" href="index.html#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> is only for appending to
-existing folders.
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type. In this case, the folder will be open and
-closed again (using <a class="link" href="index.html#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> and
-<a class="link" href="index.html#close-hook" title="1.2. Write a compressed mailbox">close-hook</a>respectively) each time you
-will add to it.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id2655950"></a>1.4. Encrypted folders</h3></div></div></div><p>
-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 use
-the following hooks:
-
-</p><pre class="screen">
-open-hook \\.pgp$ "pgp -f < %f > %t"
-close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-</pre><p>
-
-Please note, that PGP does not support appending to an encrypted
-folder, so there is no append-hook defined.
-
-If you are using GnuPG instead of PGP, you may use the following hooks
-instead:
-
-</p><pre class="screen">
-open-hook \\.gpg$ "gpg --decrypt < %f > %t"
-close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
-</pre><p>
-
-<span class="bold"><strong>Note:</strong></span> the folder is temporary stored
-decrypted in the /tmp directory, where it can be read by your system
-administrator. So think about the security aspects of this.
-</p></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="intro.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html>
+++ /dev/null
-#!/bin/sh --
-
-prefix=/usr
-exec_prefix=${prefix}
-bindir=${exec_prefix}/bin
-libdir=${exec_prefix}/lib
-mandir=/usr/share/man
-srcdir=../../doc
-datarootdir=${prefix}/share
-docdir=/usr/share/doc
-includedir=${prefix}/include
-top_srcdir=../..
-top_builddir=..
-
-SOURCE="$1"
-TARGET="$2"
-
-
-rm -f "$TARGET"
-
-sed -e "s;/usr/local/bin/;$bindir/;g" \
- -e "s;/usr/local/doc/mutt/;$docdir/;g" \
- "$SOURCE" > $TARGET
-
-chmod 644 "$TARGET"
+++ /dev/null
-#!/bin/sh --
-
-prefix=/usr
-exec_prefix=${prefix}
-bindir=${exec_prefix}/bin
-libdir=${exec_prefix}/lib
-mandir=/usr/share/man
-srcdir=../../doc
-datarootdir=${prefix}/share
-docdir=/usr/share/doc
-includedir=${prefix}/include
-top_srcdir=../..
-top_builddir=..
-
-SOURCE="$1"
-TARGET="$2"
-
-
-rm -f "$TARGET"
-
-sed -e "s;/usr/local/bin/;$bindir/;g" \
- -e "s;/usr/local/doc/mutt/;$docdir/;g" \
- "$SOURCE" > $TARGET
-
-chmod 644 "$TARGET"
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Introduction</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="index.html" title="The Mutt E-Mail Client" /><link rel="next" href="gettingstarted.html" title="Chapter 2. Getting Started" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. Introduction</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="gettingstarted.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="intro.html#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="intro.html#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="intro.html#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="intro.html#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="intro.html#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="intro.html#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="intro.html#copyright">7. Copyright</a></span></dt></dl></div><p>
-<span class="bold"><strong>Mutt</strong></span> is a small but very powerful text-based MIME mail client. Mutt 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.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="homepage"></a>1. Mutt Home Page</h2></div></div></div><p>
-The official homepage can be found at
-<a class="ulink" href="http://www.mutt.org/" target="_top">http://www.mutt.org/</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttlists"></a>2. Mailing Lists</h2></div></div></div><p>
-To subscribe to one of the following mailing lists, send a message with the
-word <span class="emphasis"><em>subscribe</em></span> in the body to
-<code class="literal">list-name</code><span class="emphasis"><em>-request</em></span><code class="literal">@mutt.org</code>.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-announce-request@mutt.org">mutt-announce-request@mutt.org</a>></code> -- low traffic list for announcements
-</p></li><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-users-request@mutt.org">mutt-users-request@mutt.org</a>></code> -- help, bug reports and feature requests
-</p></li><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-dev-request@mutt.org">mutt-dev-request@mutt.org</a>></code> -- development mailing list
-</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
-All messages posted to
-<span class="emphasis"><em>mutt-announce</em></span> are automatically forwarded to
-<span class="emphasis"><em>mutt-users</em></span>, so you do not need to be subscribed to
-both lists.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="distribution"></a>3. Software Distribution Sites</h2></div></div></div><p>
-Mutt releases can be downloaded from
-<a class="ulink" href="ftp://ftp.mutt.org/mutt/" target="_top">ftp://ftp.mutt.org/mutt/</a>.
-For a list of mirror sites, please refer to
-<a class="ulink" href="http://www.mutt.org/download.html" target="_top">http://www.mutt.org/download.html</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="irc"></a>4. Mutt online resources</h2></div></div></div><div class="variablelist"><dl><dt><span class="term">Bug Tracking System</span></dt><dd><p>
-The official mutt bug tracking system can be found at
-<a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a>
-</p></dd><dt><span class="term">Wiki</span></dt><dd><p>
-An (unofficial) wiki can be found
-at <a class="ulink" href="http://wiki.mutt.org/" target="_top">http://wiki.mutt.org/</a>.
-</p></dd><dt><span class="term">IRC</span></dt><dd><p>
-For the IRC user community, visit channel <span class="emphasis"><em>#mutt</em></span> on
-<a class="ulink" href="http://www.freenode.net/" target="_top">irc.freenode.net</a>.
-</p></dd><dt><span class="term">USENET</span></dt><dd><p>
-For USENET, see the newsgroup <a class="ulink" href="news:comp.mail.mutt" target="_top">comp.mail.mutt</a>.
-</p></dd></dl></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="contrib"></a>5. Contributing to Mutt</h2></div></div></div><p>
-There are various ways to contribute to the Mutt project.
-</p><p>
-Especially for new users it may be helpful to meet other new and
-experienced users to chat about Mutt, talk about problems and share
-tricks.
-</p><p>
-Since translations of Mutt into other languages are highly appreciated,
-the mutt developers always look for skilled translators that help
-improve and continue to maintain stale translations.
-</p><p>
-For contributing code patches for new features and bug fixes, please
-refer to the developer pages at
-<a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a> for more details.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="typo"></a>6. Typograhical conventions</h2></div></div></div><p>
-This section lists typographical conventions followed throughout this
-manual. See table <a class="xref" href="intro.html#tab-typo" title="Table 1.1. Typographical conventions for special terms">Table 1.1, “Typographical conventions for special terms”</a> for typographical
-conventions for special terms.
-</p><div class="table"><a id="tab-typo"></a><p class="title"><b>Table 1.1. Typographical conventions for special terms</b></p><div class="table-contents"><table summary="Typographical conventions for special terms" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Item</th><th>Refers to...</th></tr></thead><tbody><tr><td><code class="literal">printf(3)</code></td><td>UNIX manual pages, execute <code class="literal">man 3 printf</code></td></tr><tr><td><code class="literal"><PageUp></code></td><td>named keys</td></tr><tr><td><code class="literal"><create-alias></code></td><td>named Mutt function</td></tr><tr><td><code class="literal">^G</code></td><td>Control+G key combination</td></tr><tr><td><code class="literal">$mail_check</code></td><td>Mutt configuration option</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Examples are presented as:
-</p><pre class="screen">
-mutt -v
-</pre><p>
-Within command synopsis, curly brackets (“<span class="quote">{}</span>”) denote a set
-of options of which one is mandatory, square brackets
-(“<span class="quote">[]</span>”) denote optional arguments, three dots
-denote that the argument may be repeated arbitrary times.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="copyright"></a>7. Copyright</h2></div></div></div><p>
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins
-<code class="email"><<a class="email" href="mailto:me@mutt.org">me@mutt.org</a>></code> and others.
-</p><p>
-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.
-</p><p>
-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.
-</p><p>
-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.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="gettingstarted.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">The Mutt E-Mail Client </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Getting Started</td></tr></table></div></body></html>
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Mutt E-Mail Client</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><meta name="description" content="All mail clients suck. This one just sucks less. -me, circa 1995" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="book" lang="en" xml:lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="id2949875"></a>The Mutt E-Mail Client</h1></div><div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Elkins</span></h3><code class="email"><<a class="email" href="mailto:me@cs.hmc.edu">me@cs.hmc.edu</a>></code></div></div><div><p class="releaseinfo">version 1.5.19 (2009-01-05)</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
-“<span class="quote">All mail clients suck. This one just sucks less.</span>” -me, circa 1995
-</p></div></div></div><hr /></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1. Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="#copyright">7. Copyright</a></span></dt></dl></dd><dt><span class="chapter"><a href="#gettingstarted">2. Getting Started</a></span></dt><dd><dl><dt><span class="sect1"><a href="#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="#postponing-mail">7. Postponing Mail</a></span></dt></dl></dd><dt><span class="chapter"><a href="#configuration">3. Configuration</a></span></dt><dd><dl><dt><span class="sect1"><a href="#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#advancedusage">4. Advanced Usage</a></span></dt><dd><dl><dt><span class="sect1"><a href="#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#mimesupport">5. Mutt's MIME Support</a></span></dt><dd><dl><dt><span class="sect1"><a href="#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="#mime-lookup">7. MIME Lookup</a></span></dt></dl></dd><dt><span class="chapter"><a href="#optionalfeatures">6. Optional features</a></span></dt><dd><dl><dt><span class="sect1"><a href="#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="#exact-address">8. Exact address generation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#tuning">7. Performance tuning</a></span></dt><dd><dl><dt><span class="sect1"><a href="#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="#tuning-search">3. Searching and limiting</a></span></dt></dl></dd><dt><span class="chapter"><a href="#reference">8. Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="#pgp-use-gpg-agent">3.150. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="#crypt-verify-sig">3.151. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="#smime-is-default">3.152. smime_is_default</a></span></dt><dt><span class="sect2"><a href="#smime-ask-cert-label">3.153. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-use-default-key">3.154. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="#pgp-entry-format">3.155. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="#pgp-good-sign">3.156. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="#pgp-check-exit">3.157. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="#pgp-long-ids">3.158. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="#pgp-retainable-sigs">3.159. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="#pgp-autoinline">3.160. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="#pgp-replyinline">3.161. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="#pgp-show-unusable">3.162. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-as">3.163. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="#pgp-strict-enc">3.164. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="#pgp-timeout">3.165. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="#pgp-sort-keys">3.166. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-auto">3.167. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="#pgp-auto-decode">3.168. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-filename">3.169. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-description">3.170. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="#pgp-decode-command">3.171. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="#pgp-getkeys-command">3.172. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-command">3.173. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="#pgp-decrypt-command">3.174. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#pgp-clearsign-command">3.175. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-command">3.176. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-sign-command">3.177. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-only-command">3.178. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="#pgp-import-command">3.179. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="#pgp-export-command">3.180. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-key-command">3.181. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-secring-command">3.182. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-pubring-command">3.183. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="#forward-decrypt">3.184. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="#smime-timeout">3.185. smime_timeout</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-with">3.186. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="#smime-keys">3.187. smime_keys</a></span></dt><dt><span class="sect2"><a href="#smime-ca-location">3.188. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="#smime-certificates">3.189. smime_certificates</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-command">3.190. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-command">3.191. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-opaque-command">3.192. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-command">3.193. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-opaque-command">3.194. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-command">3.195. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-pk7out-command">3.196. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-command">3.197. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-signer-cert-command">3.198. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-import-cert-command">3.199. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-email-command">3.200. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="#smime-default-key">3.201. smime_default_key</a></span></dt><dt><span class="sect2"><a href="#ssl-client-cert">3.202. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="#ssl-force-tls">3.203. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="#ssl-starttls">3.204. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="#certificate-file">3.205. certificate_file</a></span></dt><dt><span class="sect2"><a href="#ssl-use-sslv3">3.206. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="#ssl-use-tlsv1">3.207. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="#ssl-min-dh-prime-bits">3.208. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="#ssl-ca-certificates-file">3.209. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="#pipe-split">3.210. pipe_split</a></span></dt><dt><span class="sect2"><a href="#pipe-decode">3.211. pipe_decode</a></span></dt><dt><span class="sect2"><a href="#pipe-sep">3.212. pipe_sep</a></span></dt><dt><span class="sect2"><a href="#pop-authenticators">3.213. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="#pop-auth-try-all">3.214. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="#pop-checkinterval">3.215. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="#pop-delete">3.216. pop_delete</a></span></dt><dt><span class="sect2"><a href="#pop-host">3.217. pop_host</a></span></dt><dt><span class="sect2"><a href="#pop-last">3.218. pop_last</a></span></dt><dt><span class="sect2"><a href="#pop-reconnect">3.219. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="#pop-user">3.220. pop_user</a></span></dt><dt><span class="sect2"><a href="#pop-pass">3.221. pop_pass</a></span></dt><dt><span class="sect2"><a href="#post-indent-string">3.222. post_indent_string</a></span></dt><dt><span class="sect2"><a href="#postpone">3.223. postpone</a></span></dt><dt><span class="sect2"><a href="#postponed">3.224. postponed</a></span></dt><dt><span class="sect2"><a href="#preconnect">3.225. preconnect</a></span></dt><dt><span class="sect2"><a href="#print">3.226. print</a></span></dt><dt><span class="sect2"><a href="#print-command">3.227. print_command</a></span></dt><dt><span class="sect2"><a href="#print-decode">3.228. print_decode</a></span></dt><dt><span class="sect2"><a href="#print-split">3.229. print_split</a></span></dt><dt><span class="sect2"><a href="#prompt-after">3.230. prompt_after</a></span></dt><dt><span class="sect2"><a href="#query-command">3.231. query_command</a></span></dt><dt><span class="sect2"><a href="#query-format">3.232. query_format</a></span></dt><dt><span class="sect2"><a href="#quit">3.233. quit</a></span></dt><dt><span class="sect2"><a href="#quote-regexp">3.234. quote_regexp</a></span></dt><dt><span class="sect2"><a href="#read-inc">3.235. read_inc</a></span></dt><dt><span class="sect2"><a href="#read-only">3.236. read_only</a></span></dt><dt><span class="sect2"><a href="#realname">3.237. realname</a></span></dt><dt><span class="sect2"><a href="#recall">3.238. recall</a></span></dt><dt><span class="sect2"><a href="#record">3.239. record</a></span></dt><dt><span class="sect2"><a href="#reply-regexp">3.240. reply_regexp</a></span></dt><dt><span class="sect2"><a href="#reply-self">3.241. reply_self</a></span></dt><dt><span class="sect2"><a href="#reply-to">3.242. reply_to</a></span></dt><dt><span class="sect2"><a href="#resolve">3.243. resolve</a></span></dt><dt><span class="sect2"><a href="#reverse-alias">3.244. reverse_alias</a></span></dt><dt><span class="sect2"><a href="#reverse-name">3.245. reverse_name</a></span></dt><dt><span class="sect2"><a href="#reverse-realname">3.246. reverse_realname</a></span></dt><dt><span class="sect2"><a href="#rfc2047-parameters">3.247. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="#save-address">3.248. save_address</a></span></dt><dt><span class="sect2"><a href="#save-empty">3.249. save_empty</a></span></dt><dt><span class="sect2"><a href="#save-history">3.250. save_history</a></span></dt><dt><span class="sect2"><a href="#save-name">3.251. save_name</a></span></dt><dt><span class="sect2"><a href="#score">3.252. score</a></span></dt><dt><span class="sect2"><a href="#score-threshold-delete">3.253. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="#score-threshold-flag">3.254. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="#score-threshold-read">3.255. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="#send-charset">3.256. send_charset</a></span></dt><dt><span class="sect2"><a href="#sendmail">3.257. sendmail</a></span></dt><dt><span class="sect2"><a href="#sendmail-wait">3.258. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="#shell">3.259. shell</a></span></dt><dt><span class="sect2"><a href="#sig-dashes">3.260. sig_dashes</a></span></dt><dt><span class="sect2"><a href="#sig-on-top">3.261. sig_on_top</a></span></dt><dt><span class="sect2"><a href="#signature">3.262. signature</a></span></dt><dt><span class="sect2"><a href="#simple-search">3.263. simple_search</a></span></dt><dt><span class="sect2"><a href="#smart-wrap">3.264. smart_wrap</a></span></dt><dt><span class="sect2"><a href="#smileys">3.265. smileys</a></span></dt><dt><span class="sect2"><a href="#sleep-time">3.266. sleep_time</a></span></dt><dt><span class="sect2"><a href="#smtp-authenticators">3.267. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="#smtp-pass">3.268. smtp_pass</a></span></dt><dt><span class="sect2"><a href="#smtp-url">3.269. smtp_url</a></span></dt><dt><span class="sect2"><a href="#sort">3.270. sort</a></span></dt><dt><span class="sect2"><a href="#sort-alias">3.271. sort_alias</a></span></dt><dt><span class="sect2"><a href="#sort-aux">3.272. sort_aux</a></span></dt><dt><span class="sect2"><a href="#sort-browser">3.273. sort_browser</a></span></dt><dt><span class="sect2"><a href="#sort-re">3.274. sort_re</a></span></dt><dt><span class="sect2"><a href="#spam-separator">3.275. spam_separator</a></span></dt><dt><span class="sect2"><a href="#spoolfile">3.276. spoolfile</a></span></dt><dt><span class="sect2"><a href="#status-chars">3.277. status_chars</a></span></dt><dt><span class="sect2"><a href="#status-format">3.278. status_format</a></span></dt><dt><span class="sect2"><a href="#status-on-top">3.279. status_on_top</a></span></dt><dt><span class="sect2"><a href="#strict-threads">3.280. strict_threads</a></span></dt><dt><span class="sect2"><a href="#suspend">3.281. suspend</a></span></dt><dt><span class="sect2"><a href="#text-flowed">3.282. text_flowed</a></span></dt><dt><span class="sect2"><a href="#thread-received">3.283. thread_received</a></span></dt><dt><span class="sect2"><a href="#thorough-search">3.284. thorough_search</a></span></dt><dt><span class="sect2"><a href="#tilde">3.285. tilde</a></span></dt><dt><span class="sect2"><a href="#time-inc">3.286. time_inc</a></span></dt><dt><span class="sect2"><a href="#timeout">3.287. timeout</a></span></dt><dt><span class="sect2"><a href="#tmpdir">3.288. tmpdir</a></span></dt><dt><span class="sect2"><a href="#to-chars">3.289. to_chars</a></span></dt><dt><span class="sect2"><a href="#trash">3.290. trash</a></span></dt><dt><span class="sect2"><a href="#tunnel">3.291. tunnel</a></span></dt><dt><span class="sect2"><a href="#use-8bitmime">3.292. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="#use-domain">3.293. use_domain</a></span></dt><dt><span class="sect2"><a href="#use-envelope-from">3.294. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="#use-from">3.295. use_from</a></span></dt><dt><span class="sect2"><a href="#use-idn">3.296. use_idn</a></span></dt><dt><span class="sect2"><a href="#use-ipv6">3.297. use_ipv6</a></span></dt><dt><span class="sect2"><a href="#user-agent">3.298. user_agent</a></span></dt><dt><span class="sect2"><a href="#visual">3.299. visual</a></span></dt><dt><span class="sect2"><a href="#wait-key">3.300. wait_key</a></span></dt><dt><span class="sect2"><a href="#weed">3.301. weed</a></span></dt><dt><span class="sect2"><a href="#wrap">3.302. wrap</a></span></dt><dt><span class="sect2"><a href="#wrap-search">3.303. wrap_search</a></span></dt><dt><span class="sect2"><a href="#wrapmargin">3.304. wrapmargin</a></span></dt><dt><span class="sect2"><a href="#write-inc">3.305. write_inc</a></span></dt><dt><span class="sect2"><a href="#write-bcc">3.306. write_bcc</a></span></dt><dt><span class="sect2"><a href="#xterm-icon">3.307. xterm_icon</a></span></dt><dt><span class="sect2"><a href="#xterm-set-titles">3.308. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="#xterm-title">3.309. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#miscellany">9. Miscellany</a></span></dt><dd><dl><dt><span class="sect1"><a href="#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="#about">2. About this document</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>1.1. <a href="#tab-typo">Typographical conventions for special terms</a></dt><dt>2.1. <a href="#tab-keys-nav">Most common navigation keys</a></dt><dt>2.2. <a href="#tab-keys-editor">Most common line editor keys</a></dt><dt>2.3. <a href="#tab-key-index">Most common message index keys</a></dt><dt>2.4. <a href="#tab-msg-status-flags">Message status flags</a></dt><dt>2.5. <a href="#tab-msg-recip-flags">Message recipient flags</a></dt><dt>2.6. <a href="#tab-key-pager">Most common pager keys</a></dt><dt>2.7. <a href="#tab-ansi-esc">ANSI escape sequences</a></dt><dt>2.8. <a href="#tab-color">Color sequences</a></dt><dt>2.9. <a href="#tab-key-threads">Most common thread mode keys</a></dt><dt>2.10. <a href="#tab-key-send">Most common mail sending keys</a></dt><dt>2.11. <a href="#tab-func-compose">Most common compose menu keys</a></dt><dt>2.12. <a href="#tab-pgp-menuflags">PGP key menu flags</a></dt><dt>3.1. <a href="#tab-key-names">Symbolic key names</a></dt><dt>4.1. <a href="#posix-regex-char-classes">POSIX regular expression character classes</a></dt><dt>4.2. <a href="#regex-repeat">Regular expression repetition operators</a></dt><dt>4.3. <a href="#regex-gnu-ext">GNU regular expression extensions</a></dt><dt>4.4. <a href="#tab-patterns">Pattern modifiers</a></dt><dt>4.5. <a href="#tab-simplesearch-keywords">Simple search keywords</a></dt><dt>4.6. <a href="#tab-date-units">Date units</a></dt><dt>8.1. <a href="#tab-commandline-options">Command line options</a></dt><dt>8.2. <a href="#generic_table">Default generic function bindings</a></dt><dt>8.3. <a href="#index_table">Default index function bindings</a></dt><dt>8.4. <a href="#pager_table">Default pager function bindings</a></dt><dt>8.5. <a href="#alias_table">Default alias function bindings</a></dt><dt>8.6. <a href="#query_table">Default query function bindings</a></dt><dt>8.7. <a href="#attach_table">Default attach function bindings</a></dt><dt>8.8. <a href="#compose_table">Default compose function bindings</a></dt><dt>8.9. <a href="#postpone_table">Default postpone function bindings</a></dt><dt>8.10. <a href="#browser_table">Default browser function bindings</a></dt><dt>8.11. <a href="#pgp_table">Default pgp function bindings</a></dt><dt>8.12. <a href="#smime_table">Default smime function bindings</a></dt><dt>8.13. <a href="#mix_table">Default mix function bindings</a></dt><dt>8.14. <a href="#editor_table">Default editor function bindings</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>3.1. <a href="#ex-rc-multiple-cmds">Multiple configuration commands per line</a></dt><dt>3.2. <a href="#ex-ec-comment">Commenting configuration files</a></dt><dt>3.3. <a href="#ex-rc-quote">Escaping quotes in congfiguration files</a></dt><dt>3.4. <a href="#ex-rc-backtick">Using external command's output in configuration files</a></dt><dt>3.5. <a href="#ex-rc-env">Using environment variables in configuration files</a></dt><dt>3.6. <a href="#ex-alias-external">Configuring external alias files</a></dt><dt>3.7. <a href="#ex-folder-sorting">Setting sort method based on mailbox name</a></dt><dt>3.8. <a href="#ex-header-weeding">Header weeding</a></dt><dt>3.9. <a href="#ex-hdr-order">Configuring header display order</a></dt><dt>3.10. <a href="#ex-my-hdr">Defining custom headers</a></dt><dt>3.11. <a href="#ex-save-hook-exando">Using %-expandos in <code class="literal">save-hook</code></a></dt><dt>3.12. <a href="#ex-folder-hook-push">Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></a></dt><dt>3.13. <a href="#ex-spam">Configuring spam detection</a></dt><dt>3.14. <a href="#ex-myvar1">Using user-defined variables for config file readability</a></dt><dt>3.15. <a href="#ex-myvar2">Using user-defined variables for backing up other config option values</a></dt><dt>3.16. <a href="#ex-myvar3">Deferring user-defined variable expansion to runtime</a></dt><dt>3.17. <a href="#ex-fmtpipe">Using external filters in format strings</a></dt><dt>4.1. <a href="#ex-pattern-bool">Using boolean operators in patterns</a></dt><dt>4.2. <a href="#ex-send-hook-my-hdr">Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></a></dt><dt>5.1. <a href="#ex-attach-count">Attachment counting</a></dt></dl></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="intro"></a>Chapter 1. Introduction</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#homepage">1. Mutt Home Page</a></span></dt><dt><span class="sect1"><a href="#muttlists">2. Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#distribution">3. Software Distribution Sites</a></span></dt><dt><span class="sect1"><a href="#irc">4. Mutt online resources</a></span></dt><dt><span class="sect1"><a href="#contrib">5. Contributing to Mutt</a></span></dt><dt><span class="sect1"><a href="#typo">6. Typograhical conventions</a></span></dt><dt><span class="sect1"><a href="#copyright">7. Copyright</a></span></dt></dl></div><p>
-<span class="bold"><strong>Mutt</strong></span> is a small but very powerful text-based MIME mail client. Mutt 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.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="homepage"></a>1. Mutt Home Page</h2></div></div></div><p>
-The official homepage can be found at
-<a class="ulink" href="http://www.mutt.org/" target="_top">http://www.mutt.org/</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttlists"></a>2. Mailing Lists</h2></div></div></div><p>
-To subscribe to one of the following mailing lists, send a message with the
-word <span class="emphasis"><em>subscribe</em></span> in the body to
-<code class="literal">list-name</code><span class="emphasis"><em>-request</em></span><code class="literal">@mutt.org</code>.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-announce-request@mutt.org">mutt-announce-request@mutt.org</a>></code> -- low traffic list for announcements
-</p></li><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-users-request@mutt.org">mutt-users-request@mutt.org</a>></code> -- help, bug reports and feature requests
-</p></li><li><p>
-<code class="email"><<a class="email" href="mailto:mutt-dev-request@mutt.org">mutt-dev-request@mutt.org</a>></code> -- development mailing list
-</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
-All messages posted to
-<span class="emphasis"><em>mutt-announce</em></span> are automatically forwarded to
-<span class="emphasis"><em>mutt-users</em></span>, so you do not need to be subscribed to
-both lists.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="distribution"></a>3. Software Distribution Sites</h2></div></div></div><p>
-Mutt releases can be downloaded from
-<a class="ulink" href="ftp://ftp.mutt.org/mutt/" target="_top">ftp://ftp.mutt.org/mutt/</a>.
-For a list of mirror sites, please refer to
-<a class="ulink" href="http://www.mutt.org/download.html" target="_top">http://www.mutt.org/download.html</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="irc"></a>4. Mutt online resources</h2></div></div></div><div class="variablelist"><dl><dt><span class="term">Bug Tracking System</span></dt><dd><p>
-The official mutt bug tracking system can be found at
-<a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a>
-</p></dd><dt><span class="term">Wiki</span></dt><dd><p>
-An (unofficial) wiki can be found
-at <a class="ulink" href="http://wiki.mutt.org/" target="_top">http://wiki.mutt.org/</a>.
-</p></dd><dt><span class="term">IRC</span></dt><dd><p>
-For the IRC user community, visit channel <span class="emphasis"><em>#mutt</em></span> on
-<a class="ulink" href="http://www.freenode.net/" target="_top">irc.freenode.net</a>.
-</p></dd><dt><span class="term">USENET</span></dt><dd><p>
-For USENET, see the newsgroup <a class="ulink" href="news:comp.mail.mutt" target="_top">comp.mail.mutt</a>.
-</p></dd></dl></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="contrib"></a>5. Contributing to Mutt</h2></div></div></div><p>
-There are various ways to contribute to the Mutt project.
-</p><p>
-Especially for new users it may be helpful to meet other new and
-experienced users to chat about Mutt, talk about problems and share
-tricks.
-</p><p>
-Since translations of Mutt into other languages are highly appreciated,
-the mutt developers always look for skilled translators that help
-improve and continue to maintain stale translations.
-</p><p>
-For contributing code patches for new features and bug fixes, please
-refer to the developer pages at
-<a class="ulink" href="http://dev.mutt.org/" target="_top">http://dev.mutt.org/</a> for more details.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="typo"></a>6. Typograhical conventions</h2></div></div></div><p>
-This section lists typographical conventions followed throughout this
-manual. See table <a class="xref" href="#tab-typo" title="Table 1.1. Typographical conventions for special terms">Table 1.1, “Typographical conventions for special terms”</a> for typographical
-conventions for special terms.
-</p><div class="table"><a id="tab-typo"></a><p class="title"><b>Table 1.1. Typographical conventions for special terms</b></p><div class="table-contents"><table summary="Typographical conventions for special terms" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Item</th><th>Refers to...</th></tr></thead><tbody><tr><td><code class="literal">printf(3)</code></td><td>UNIX manual pages, execute <code class="literal">man 3 printf</code></td></tr><tr><td><code class="literal"><PageUp></code></td><td>named keys</td></tr><tr><td><code class="literal"><create-alias></code></td><td>named Mutt function</td></tr><tr><td><code class="literal">^G</code></td><td>Control+G key combination</td></tr><tr><td><code class="literal">$mail_check</code></td><td>Mutt configuration option</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Examples are presented as:
-</p><pre class="screen">
-mutt -v
-</pre><p>
-Within command synopsis, curly brackets (“<span class="quote">{}</span>”) denote a set
-of options of which one is mandatory, square brackets
-(“<span class="quote">[]</span>”) denote optional arguments, three dots
-denote that the argument may be repeated arbitrary times.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="copyright"></a>7. Copyright</h2></div></div></div><p>
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins
-<code class="email"><<a class="email" href="mailto:me@mutt.org">me@mutt.org</a>></code> and others.
-</p><p>
-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.
-</p><p>
-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.
-</p><p>
-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.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="gettingstarted"></a>Chapter 2. Getting Started</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#core-concepts">1. Core concepts</a></span></dt><dt><span class="sect1"><a href="#menus">2. Moving Around in Menus</a></span></dt><dt><span class="sect1"><a href="#editing">3. Editing Input Fields</a></span></dt><dd><dl><dt><span class="sect2"><a href="#editing-intro">3.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#editing-history">3.2. History</a></span></dt></dl></dd><dt><span class="sect1"><a href="#reading">4. Reading Mail - The Index and Pager</a></span></dt><dd><dl><dt><span class="sect2"><a href="#index-menu">4.1. The Message Index</a></span></dt><dt><span class="sect2"><a href="#pager-menu">4.2. The Pager</a></span></dt><dt><span class="sect2"><a href="#threads">4.3. Threaded Mode</a></span></dt><dt><span class="sect2"><a href="#reading-misc">4.4. Miscellaneous Functions</a></span></dt></dl></dd><dt><span class="sect1"><a href="#sending">5. Sending Mail</a></span></dt><dd><dl><dt><span class="sect2"><a href="#sending-intro">5.1. Introduction</a></span></dt><dt><span class="sect2"><a href="#edit-header">5.2. Editing the message header</a></span></dt><dt><span class="sect2"><a href="#sending-crypto">5.3. Sending cryptographically signed/encrypted messages</a></span></dt><dt><span class="sect2"><a href="#sending-mixmaster">5.4. Sending anonymous messages via mixmaster</a></span></dt><dt><span class="sect2"><a href="#ff">5.5. Sending format=flowed messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="#forwarding-mail">6. Forwarding and Bouncing Mail</a></span></dt><dt><span class="sect1"><a href="#postponing-mail">7. Postponing Mail</a></span></dt></dl></div><p>
-This section is intended as a brief overview of how to use Mutt. There are
-many other features which are described elsewhere in the manual. There
-is even more information available in the Mutt FAQ and various web
-pages. See the <a class="ulink" href="http://www.mutt.org/" target="_top">Mutt homepage</a> for more details.
-</p><p>
-The keybindings described in this section are the defaults as distributed.
-Your local system administrator may have altered the defaults for your site.
-You can always type “<span class="quote">?</span>” in any menu to display the current bindings.
-</p><p>
-The first thing you need to do is invoke mutt, simply by typing <code class="literal">mutt</code>
-at the command line. There are various command-line options, see
-either the mutt man page or the <a class="link" href="#commandline" title="1. Command line options">reference</a>.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="core-concepts"></a>1. Core concepts</h2></div></div></div><p>
-Mutt is a text-based application which interacts with users through
-different menus which are mostly line-/entry-based or page-based. A
-line-based menu is the so-called “<span class="quote">index</span>” menu (listing all messages of
-the currently opened folder) or the “<span class="quote">alias</span>” menu (allowing you to
-select recipients from a list). Examples for page-based menus are the
-“<span class="quote">pager</span>” (showing one message at a time) or the “<span class="quote">help</span>” menu listing
-all available key bindings.
-</p><p>
-The user interface consists of a context sensitive help line at the top,
-the menu's contents followed by a context sensitive status line and
-finally the command line. The command line is used to display
-informational and error messages as well as for prompts and for entering
-interactive commands.
-</p><p>
-Because Mutt allows for customizing almost all key bindings, there are
-so-called “<span class="quote">functions</span>” which can be executed manually (using the
-command line) or in macros. Macros allow the user to bind a sequence of
-commands to a single key or a short key sequence instead of repeating a
-sequence of actions over and over.
-</p><p>
-Many commands (such as saving or copying a message to another folder)
-can be applied to a single message or a set of messages (so-called
-“<span class="quote">tagged</span>” messages). To help selecting messages, Mutt provides a rich
-set of message patterns (such as recipients, sender, body contents, date
-sent/received, etc.) which can be combined into complex expressions
-using the boolean <span class="emphasis"><em>and</em></span> and <span class="emphasis"><em>or</em></span>
-operations as well as negating. These patterns can also be used to (for
-example) search for messages or to limit the index to show only matching
-messages.
-</p><p>
-Mutt supports a “<span class="quote">hook</span>” concept which allows the user to execute
-arbitrary configuration commands and functions in certain situations
-such as entering a folder, starting a new message or replying to an
-existing one. These hooks can be used to highly customize Mutt's
-behaviour including managing multiple identities, customizing the
-display for a folder or even implementing auto-archiving based on a
-per-folder basis and much more.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="menus"></a>2. Moving Around in Menus</h2></div></div></div><p>
-The most important navigation keys common to all menus are shown in
-<a class="xref" href="#tab-keys-nav" title="Table 2.1. Most common navigation keys">Table 2.1, “Most common navigation keys”</a>.
-</p><div class="table"><a id="tab-keys-nav"></a><p class="title"><b>Table 2.1. Most common navigation keys</b></p><div class="table-contents"><table summary="Most common navigation keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>j or <Down></td><td><code class="literal"><next-entry></code></td><td>move to the next entry</td></tr><tr><td>k or <Up></td><td><code class="literal"><previous-entry></code></td><td>move to the previous entry</td></tr><tr><td>z or <PageDn></td><td><code class="literal"><page-down></code></td><td>go to the next page</td></tr><tr><td>Z or <PageUp></td><td><code class="literal"><page-up></code></td><td>go to the previous page</td></tr><tr><td>= or <Home></td><td><code class="literal"><first-entry></code></td><td>jump to the first entry</td></tr><tr><td>* or <End></td><td><code class="literal"><last-entry></code></td><td>jump to the last entry</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>exit the current menu</td></tr><tr><td>?</td><td><code class="literal"><help></code></td><td>list all keybindings for the current menu</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing"></a>3. Editing Input Fields</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-intro"></a>3.1. Introduction</h3></div></div></div><p>
-Mutt has a built-in line editor for inputting text, e.g. email
-addresses or filenames. The keys used to manipulate text input are
-very similar to those of Emacs. See <a class="xref" href="#tab-keys-editor" title="Table 2.2. Most common line editor keys">Table 2.2, “Most common line editor keys”</a> for a full
-reference of available functions, their default key bindings, and
-short descriptions.
-</p><div class="table"><a id="tab-keys-editor"></a><p class="title"><b>Table 2.2. Most common line editor keys</b></p><div class="table-contents"><table summary="Most common line editor keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^A or <Home></td><td><code class="literal"><bol></code></td><td>move to the start of the line</td></tr><tr><td>^B or <Left></td><td><code class="literal"><backward-char></code></td><td>move back one char</td></tr><tr><td>Esc B</td><td><code class="literal"><backward-word></code></td><td>move back one word</td></tr><tr><td>^D or <Delete></td><td><code class="literal"><delete-char></code></td><td>delete the char under the cursor</td></tr><tr><td>^E or <End></td><td><code class="literal"><eol></code></td><td>move to the end of the line</td></tr><tr><td>^F or <Right></td><td><code class="literal"><forward-char></code></td><td>move forward one char</td></tr><tr><td>Esc F</td><td><code class="literal"><forward-word></code></td><td>move forward one word</td></tr><tr><td><Tab></td><td><code class="literal"><complete></code></td><td>complete filename or alias</td></tr><tr><td>^T</td><td><code class="literal"><complete-query></code></td><td>complete address with query</td></tr><tr><td>^K</td><td><code class="literal"><kill-eol></code></td><td>delete to the end of the line</td></tr><tr><td>Esc d</td><td><code class="literal"><kill-eow></code></td><td>delete to the end of the word</td></tr><tr><td>^W</td><td><code class="literal"><kill-word></code></td><td>kill the word in front of the cursor</td></tr><tr><td>^U</td><td><code class="literal"><kill-line></code></td><td>delete entire line</td></tr><tr><td>^V</td><td><code class="literal"><quote-char></code></td><td>quote the next typed key</td></tr><tr><td><Up></td><td><code class="literal"><history-up></code></td><td>recall previous string from history</td></tr><tr><td><Down></td><td><code class="literal"><history-down></code></td><td>recall next string from history</td></tr><tr><td><BackSpace></td><td><code class="literal"><backspace></code></td><td>kill the char in front of the cursor</td></tr><tr><td>Esc u</td><td><code class="literal"><upcase-word></code></td><td>convert word to upper case</td></tr><tr><td>Esc l</td><td><code class="literal"><downcase-word></code></td><td>convert word to lower case</td></tr><tr><td>Esc c</td><td><code class="literal"><capitalize-word></code></td><td>capitalize the word</td></tr><tr><td>^G</td><td>n/a</td><td>abort</td></tr><tr><td><Return></td><td>n/a</td><td>finish editing</td></tr></tbody></table></div></div><br class="table-break" /><p>
-You can remap the <span class="emphasis"><em>editor</em></span> functions using the
-<a class="link" href="#bind" title="5. Changing the default key bindings">bind</a> command. For example, to make
-the <Delete> key delete the character in front of
-the cursor rather than under, you could use:
-</p><pre class="screen">
-bind editor <delete> backspace
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editing-history"></a>3.2. History</h3></div></div></div><p>
-Mutt maintains a history for the built-in editor. The number of items
-is controlled by the <a class="link" href="#history" title="3.77. history">$history</a>
-variable and can be made persistent using an external file specified
-using <a class="link" href="#history-file" title="3.78. history_file">$history_file</a>.
-You may cycle through them at an editor prompt by using the
-<code class="literal"><history-up></code> and/or
-<code class="literal"><history-down></code> commands.
-</p><p>
-Mutt maintains several distinct history lists, one for each of the
-following categories:
-</p><div class="itemizedlist"><ul type="disc"><li><p>muttrc commands</p></li><li><p>addresses and aliases</p></li><li><p>shell commands</p></li><li><p>filenames</p></li><li><p>patterns</p></li><li><p>everything else</p></li></ul></div><p>
-Mutt automatically filters out repeated items from the history. It
-also mimics the behavior of some shells by ignoring items starting
-with a space. The latter feature can be useful in macros to not clobber
-the history's valuable entries with unwanted entries.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="reading"></a>4. Reading Mail - The Index and Pager</h2></div></div></div><p>
-Similar to many other mail clients, there are two modes in which mail is
-read in Mutt. The first is the index of messages in the mailbox, which is
-called the “<span class="quote">index</span>” in Mutt. The second mode is the display of the
-message contents. This is called the “<span class="quote">pager.</span>”
-</p><p>
-The next few sections describe the functions provided in each of these
-modes.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-menu"></a>4.1. The Message Index</h3></div></div></div><p>
-Common keys used to navigate through and manage messages in the index
-are shown in <a class="xref" href="#tab-key-index" title="Table 2.3. Most common message index keys">Table 2.3, “Most common message index keys”</a>. How messages are presented
-in the index menu can be customized using the
-<a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable.
-</p><div class="table"><a id="tab-key-index"></a><p class="title"><b>Table 2.3. Most common message index keys</b></p><div class="table-contents"><table summary="Most common message index keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td>c</td><td>change to a different mailbox</td></tr><tr><td>Esc c</td><td>change to a folder in read-only mode</td></tr><tr><td>C</td><td>copy the current message to another mailbox</td></tr><tr><td>Esc C</td><td>decode a message and copy it to a folder</td></tr><tr><td>Esc s</td><td>decode a message and save it to a folder</td></tr><tr><td>D</td><td>delete messages matching a pattern</td></tr><tr><td>d</td><td>delete the current message</td></tr><tr><td>F</td><td>mark as important</td></tr><tr><td>l</td><td>show messages matching a pattern</td></tr><tr><td>N</td><td>mark message as new</td></tr><tr><td>o</td><td>change the current sort method</td></tr><tr><td>O</td><td>reverse sort the mailbox</td></tr><tr><td>q</td><td>save changes and exit</td></tr><tr><td>s</td><td>save-message</td></tr><tr><td>T</td><td>tag messages matching a pattern</td></tr><tr><td>t</td><td>toggle the tag on a message</td></tr><tr><td>Esc t</td><td>toggle tag on entire message thread</td></tr><tr><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td>u</td><td>undelete-message</td></tr><tr><td>v</td><td>view-attachments</td></tr><tr><td>x</td><td>abort changes and exit</td></tr><tr><td><Return></td><td>display-message</td></tr><tr><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td>@</td><td>show the author's full e-mail address</td></tr><tr><td>$</td><td>save changes to mailbox</td></tr><tr><td>/</td><td>search</td></tr><tr><td>Esc /</td><td>search-reverse</td></tr><tr><td>^L</td><td>clear and redraw the screen</td></tr><tr><td>^T</td><td>untag messages matching a pattern</td></tr></tbody></table></div></div><br class="table-break" /><p>
-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 “<span class="quote">flags</span>” in <a class="xref" href="#tab-msg-status-flags" title="Table 2.4. Message status flags">Table 2.4, “Message status flags”</a>
-may appear, some of which can be turned on or off using these functions:
-<code class="literal"><set-flag></code> and
-<code class="literal"><clear-flag></code>
-bound by default to “<span class="quote">w</span>” and “<span class="quote">W</span>” respectively.
-</p><p>
-Furthermore, the flags in <a class="xref" href="#tab-msg-recip-flags" title="Table 2.5. Message recipient flags">Table 2.5, “Message recipient flags”</a> reflect
-who the message is addressed to. They can be customized with the
-<a class="link" href="#to-chars" title="3.289. to_chars">$to_chars</a> variable.
-</p><div class="table"><a id="tab-msg-status-flags"></a><p class="title"><b>Table 2.4. Message status flags</b></p><div class="table-contents"><table summary="Message status flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>D</td><td>message is deleted (is marked for deletion)</td></tr><tr><td>d</td><td>message has attachments marked for deletion</td></tr><tr><td>K</td><td>contains a PGP public key</td></tr><tr><td>N</td><td>message is new</td></tr><tr><td>O</td><td>message is old</td></tr><tr><td>P</td><td>message is PGP encrypted</td></tr><tr><td>r</td><td>message has been replied to</td></tr><tr><td>S</td><td>message is signed, and the signature is successfully verified</td></tr><tr><td>s</td><td>message is signed</td></tr><tr><td>!</td><td>message is flagged</td></tr><tr><td>*</td><td>message is tagged</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-msg-recip-flags"></a><p class="title"><b>Table 2.5. Message recipient flags</b></p><div class="table-contents"><table summary="Message recipient flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>+</td><td>message is to you and you only</td></tr><tr><td>T</td><td>message is to you, but also to or cc'ed to others</td></tr><tr><td>C</td><td>message is cc'ed to you</td></tr><tr><td>F</td><td>message is from you</td></tr><tr><td>L</td><td>message is sent to a subscribed mailing list</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-menu"></a>4.2. The Pager</h3></div></div></div><p>
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program <span class="emphasis"><em>less</em></span> though not nearly as
-featureful.
-</p><div class="table"><a id="tab-key-pager"></a><p class="title"><b>Table 2.6. Most common pager keys</b></p><div class="table-contents"><table summary="Most common pager keys" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Key</th><th>Description</th></tr></thead><tbody><tr><td><Return></td><td>go down one line</td></tr><tr><td><Space></td><td>display the next page (or next message if at the end of a message)</td></tr><tr><td>-</td><td>go back to the previous page</td></tr><tr><td>n</td><td>search for next match</td></tr><tr><td>S</td><td>skip beyond quoted text</td></tr><tr><td>T</td><td>toggle display of quoted text</td></tr><tr><td>?</td><td>show keybindings</td></tr><tr><td>/</td><td>regular expression search</td></tr><tr><td>Esc /</td><td>backward regular expression search</td></tr><tr><td>\</td><td>toggle highlighting of search matches</td></tr><tr><td>^</td><td>jump to the top of the message</td></tr></tbody></table></div></div><br class="table-break" /><p>
-In addition to key bindings in <a class="xref" href="#tab-key-pager" title="Table 2.6. Most common pager keys">Table 2.6, “Most common pager keys”</a>,
-many of the functions from the index menu are also available in
-the pager, such as <code class="literal"><delete-message></code> or <code class="literal"><copy-message></code>
-(this is one advantage over using an external pager to view messages).
-</p><p>
-Also, the internal pager supports a couple other advanced features. For
-one, it will accept and translate the “<span class="quote">standard</span>” nroff sequences for
-bold and underline. These sequences are a series of either the letter,
-backspace (^H), the letter again for bold or the letter, backspace,
-“<span class="quote">_</span>” for denoting underline. Mutt will attempt to display these
-in bold and underline respectively if your terminal supports them. If
-not, you can use the bold and underline <a class="link" href="#color" title="9. Using color and mono video attributes">color</a>
-objects to specify a color or mono attribute for them.
-</p><p>
-Additionally, the internal pager supports the ANSI escape sequences for
-character attributes. Mutt translates them into the correct color and
-character settings. The sequences Mutt supports are:
-</p><pre class="screen">
-\e[<span class="emphasis"><em>Ps</em></span>;<span class="emphasis"><em>Ps</em></span>;..<span class="emphasis"><em>Ps</em></span>;m
-</pre><p>
-where <span class="emphasis"><em>Ps</em></span> can be one of the codes shown in
-<a class="xref" href="#tab-ansi-esc" title="Table 2.7. ANSI escape sequences">Table 2.7, “ANSI escape sequences”</a>.
-</p><div class="table"><a id="tab-ansi-esc"></a><p class="title"><b>Table 2.7. ANSI escape sequences</b></p><div class="table-contents"><table summary="ANSI escape sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Escape code</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>All attributes off</td></tr><tr><td>1</td><td>Bold on</td></tr><tr><td>4</td><td>Underline on</td></tr><tr><td>5</td><td>Blink on</td></tr><tr><td>7</td><td>Reverse video on</td></tr><tr><td>3<span class="emphasis"><em><color></em></span></td><td>Foreground color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr><tr><td>4<span class="emphasis"><em><color></em></span></td><td>Background color is <span class="emphasis"><em><color></em></span> (see <a class="xref" href="#tab-color" title="Table 2.8. Color sequences">Table 2.8, “Color sequences”</a>)</td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><a id="tab-color"></a><p class="title"><b>Table 2.8. Color sequences</b></p><div class="table-contents"><table summary="Color sequences" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Color code</th><th>Color</th></tr></thead><tbody><tr><td>0</td><td>Black</td></tr><tr><td>1</td><td>Red</td></tr><tr><td>2</td><td>Green</td></tr><tr><td>3</td><td>Yellow</td></tr><tr><td>4</td><td>Blue</td></tr><tr><td>5</td><td>Magenta</td></tr><tr><td>6</td><td>Cyan</td></tr><tr><td>7</td><td>White</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Mutt uses these attributes for handling <code class="literal">text/enriched</code>
-messages, and they can also be used by an external
-<a class="link" href="#auto-view" title="4. MIME Autoview">autoview</a> script for highlighting
-purposes.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-Note that the search commands in the pager take regular expressions,
-which are not quite the same as the more
-complex <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> used by the search
-command in the index. This is because the pager only performs simple
-text search, whereas the index provides boolean filtering on several
-aspects of messages.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="threads"></a>4.3. Threaded Mode</h3></div></div></div><p>
-When the mailbox is <a class="link" href="#sort" title="3.270. sort">sorted</a> by <span class="emphasis"><em>threads</em></span>, there are
-a few additional functions available in the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> modes
-as shown in <a class="xref" href="#tab-key-threads" title="Table 2.9. Most common thread mode keys">Table 2.9, “Most common thread mode keys”</a>.
-</p><div class="table"><a id="tab-key-threads"></a><p class="title"><b>Table 2.9. Most common thread mode keys</b></p><div class="table-contents"><table summary="Most common thread mode keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>^D</td><td><code class="literal"><delete-thread></code></td><td>delete all messages in the current thread</td></tr><tr><td>^U</td><td><code class="literal"><undelete-thread></code></td><td>undelete all messages in the current thread</td></tr><tr><td>^N</td><td><code class="literal"><next-thread></code></td><td>jump to the start of the next thread</td></tr><tr><td>^P</td><td><code class="literal"><previous-thread></code></td><td>jump to the start of the previous thread</td></tr><tr><td>^R</td><td><code class="literal"><read-thread></code></td><td>mark the current thread as read</td></tr><tr><td>Esc d</td><td><code class="literal"><delete-subthread></code></td><td>delete all messages in the current subthread</td></tr><tr><td>Esc u</td><td><code class="literal"><undelete-subthread></code></td><td>undelete all messages in the current subthread</td></tr><tr><td>Esc n</td><td><code class="literal"><next-subthread></code></td><td>jump to the start of the next subthread</td></tr><tr><td>Esc p</td><td><code class="literal"><previous-subthread></code></td><td>jump to the start of the previous subthread</td></tr><tr><td>Esc r</td><td><code class="literal"><read-subthread></code></td><td>mark the current subthread as read</td></tr><tr><td>Esc t</td><td><code class="literal"><tag-thread></code></td><td>toggle the tag on the current thread</td></tr><tr><td>Esc v</td><td><code class="literal"><collapse-thread></code></td><td>toggle collapse for the current thread</td></tr><tr><td>Esc V</td><td><code class="literal"><collapse-all></code></td><td>toggle collapse for all threads</td></tr><tr><td>P</td><td><code class="literal"><parent-message></code></td><td>jump to parent message in thread</td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><h3 class="title">Note</h3><p>
-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 on
-the screen. See %M in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
-For example, you could use "%?M?(#%03M)&(%4l)?" in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to optionally
-display the number of hidden messages if the thread is collapsed.
-</p></div><p>
-See also: <a class="link" href="#strict-threads" title="3.280. strict_threads">$strict_threads</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reading-misc"></a>4.4. Miscellaneous Functions</h3></div></div></div><p>
-In addition, the <span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span>
-menus have these interesting functions:
-</p><div class="variablelist"><dl><dt><span class="term">
-<code class="literal"><create-alias></code><a id="create-alias"></a> (default: a)
-</span></dt><dd><p>
-Creates a new alias based upon the current message (or prompts for a
-new one). Once editing is complete, an <a class="link" href="#alias" title="4. Defining/Using aliases">alias</a>
-command is added to the file specified by
-the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> variable
-for future use
-</p><div class="note"><h3 class="title">Note</h3><p>
-Mutt does not read the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a>
-upon startup so you must explicitly <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> the file.
-</p></div></dd><dt><span class="term">
-<code class="literal"><check-traditional-pgp></code><a id="check-traditional-pgp"></a> (default: Esc P)
-</span></dt><dd><p>
-This function will search the current message for content signed or
-encrypted with PGP the “<span class="quote">traditional</span>” 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 <a class="link" href="#edit-type"><code class="literal"><edit-type></code></a> function's
-effect.
-</p></dd><dt><span class="term">
-<code class="literal"><edit></code><a id="edit"></a> (default: e)
-</span></dt><dd><p>
-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; if the message is unchanged it won't be replaced.
-</p></dd><dt><span class="term">
-<code class="literal"><edit-type></code><a id="edit-type"></a> (default:
-^E on the attachment menu, and in the pager and index menus;
-^T on the compose menu)
-</span></dt><dd><p>
-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 class="link" href="#attach-menu" title="1.2. The Attachment Menu">attachment menu</a>, you can change any
-attachment's content type. These changes are not persistent, and get
-lost upon changing folders.
-</p><p>
-Note that this command is also available on the <a class="link" href="#compose-menu" title="1.3. The Compose Menu">compose
-menu</a>. There, it's used to fine-tune the properties of attachments you are going
-to send.
-</p></dd><dt><span class="term">
-<code class="literal"><enter-command></code><a id="enter-command"></a> (default: “<span class="quote">:</span>”)
-</span></dt><dd><p>
-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 <a class="link" href="#macro" title="8. Keyboard macros">macros</a> to change settings on the
-fly.
-</p></dd><dt><span class="term">
-<code class="literal"><extract-keys></code><a id="extract-keys"></a> (default: ^K)
-</span></dt><dd><p>
-This command extracts PGP public keys from the current or tagged
-message(s) and adds them to your PGP public key ring.
-</p></dd><dt><span class="term">
-<code class="literal"><forget-passphrase></code><a id="forget-passphrase"></a> (default:
-^F)
-</span></dt><dd><p>
-This command wipes the passphrase(s) from memory. It is useful, if
-you misspelled the passphrase.
-</p></dd><dt><span class="term">
-<code class="literal"><list-reply></code><a id="list-reply"></a> (default: L)
-</span></dt><dd><p>
-Reply to the current or tagged message(s) by extracting any addresses which
-match the regular expressions given by the <a class="link" href="#lists" title="12. Mailing lists">lists or subscribe</a>
-commands, but also honor any <code class="literal">Mail-Followup-To</code> header(s) if the
-<a class="link" href="#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a>
-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.
-</p></dd><dt><span class="term">
-<code class="literal"><pipe-message></code><a id="pipe-message"></a> (default: |)
-</span></dt><dd><p>
-Asks for an external Unix command and pipes the current or
-tagged message(s) to it. The variables <a class="link" href="#pipe-decode" title="3.211. pipe_decode">$pipe_decode</a>, <a class="link" href="#pipe-split" title="3.210. pipe_split">$pipe_split</a>,
-<a class="link" href="#pipe-sep" title="3.212. pipe_sep">$pipe_sep</a> and <a class="link" href="#wait-key" title="3.300. wait_key">$wait_key</a> control the exact behavior of this function.
-</p></dd><dt><span class="term">
-<code class="literal"><resend-message></code><a id="resend-message"></a> (default: Esc e)
-</span></dt><dd><p>
-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 <a class="link" href="#weed" title="3.301. weed">$weed</a>
-variable.
-</p><p>
-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 <code class="literal">message/rfc822</code> body part.
-</p></dd><dt><span class="term">
-<code class="literal"><shell-escape></code><a id="shell-escape"></a> (default: !)
-</span></dt><dd><p>
-Asks for an external Unix command and executes it. The <a class="link" href="#wait-key" title="3.300. wait_key">$wait_key</a> can be used to control
-whether Mutt 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. If no command is given, an
-interactive shell is executed.
-</p></dd><dt><span class="term">
-<code class="literal"><toggle-quoted></code><a id="toggle-quoted"></a> (default: T)
-</span></dt><dd><p>
-The pager uses the <a class="link" href="#quote-regexp" title="3.234. quote_regexp">$quote_regexp</a> variable to detect quoted text when
-displaying the body of the message. This function toggles the display
-of the quoted material in the message. It is particularly useful when
-being interested in just the response and there is a large amount of
-quoted text in the way.
-</p></dd><dt><span class="term">
-<code class="literal"><skip-quoted></code><a id="skip-quoted"></a> (default: S)
-</span></dt><dd><p>
-This function will go to the next line of non-quoted text which comes
-after a line of quoted text in the internal pager.
-</p></dd></dl></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="sending"></a>5. Sending Mail</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-intro"></a>5.1. Introduction</h3></div></div></div><p>
-The bindings shown in <a class="xref" href="#tab-key-send" title="Table 2.10. Most common mail sending keys">Table 2.10, “Most common mail sending keys”</a> are available in the
-<span class="emphasis"><em>index</em></span> and <span class="emphasis"><em>pager</em></span> to start a new message.
-</p><div class="table"><a id="tab-key-send"></a><p class="title"><b>Table 2.10. Most common mail sending keys</b></p><div class="table-contents"><table summary="Most common mail sending keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>m</td><td><code class="literal"><compose></code></td><td>compose a new message</td></tr><tr><td>r</td><td><code class="literal"><reply></code></td><td>reply to sender</td></tr><tr><td>g</td><td><code class="literal"><group-reply></code></td><td>reply to all recipients</td></tr><tr><td>L</td><td><code class="literal"><list-reply></code></td><td>reply to mailing list address</td></tr><tr><td>f</td><td><code class="literal"><forward></code></td><td>forward message</td></tr><tr><td>b</td><td><code class="literal"><bounce></code></td><td>bounce (remail) message</td></tr><tr><td>Esc k</td><td><code class="literal"><mail-key></code></td><td>mail a PGP public key to someone</td></tr></tbody></table></div></div><br class="table-break" /><p>
-<span class="emphasis"><em>Bouncing</em></span> a message sends the message as-is to the recipient you
-specify. <span class="emphasis"><em>Forwarding</em></span> 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 “<span class="quote"><a class="link" href="#forwarding-mail" title="6. Forwarding and Bouncing Mail">Forwarding
-and Bouncing Mail</a>.</span>”
-</p><p>
-Mutt will then enter the <span class="emphasis"><em>compose</em></span> menu and prompt you for the
-recipients to place on the “<span class="quote">To:</span>” header field. Next, it will ask
-you for the “<span class="quote">Subject:</span>” field for the message, providing a default if
-you are replying to or forwarding a message. See also
-<a class="link" href="#askcc" title="3.10. askcc">$askcc</a>,
-<a class="link" href="#askbcc" title="3.9. askbcc">$askbcc</a>,
-<a class="link" href="#autoedit" title="3.17. autoedit">$autoedit</a>,
-<a class="link" href="#bounce" title="3.21. bounce">$bounce</a>,
-<a class="link" href="#fast-reply" title="3.55. fast_reply">$fast_reply</a>,
-and <a class="link" href="#include" title="3.98. include">$include</a>
-for changing how Mutt asks these questions.
-</p><p>
-Mutt will then automatically start your <a class="link" href="#editor" title="3.51. editor">$editor</a>
-on the message body. If the <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>
-variable is set, the headers will be at the top of the message in your editor.
-Any messages you are replying to will be added in sort order to the message,
-with appropriate <a class="link" href="#attribution" title="3.16. attribution">$attribution</a>,
-<a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a> and
-<a class="link" href="#post-indent-string" title="3.222. post_indent_string">$post_indent_string</a>.
-When forwarding a message, if the <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a>
-variable is unset, a copy of the forwarded message will be included. If
-you have specified a <a class="link" href="#signature" title="3.262. signature">$signature</a>, it
-will be appended to the message.
-</p><p>
-Once you have finished editing the body of your mail message, you are
-returned to the <span class="emphasis"><em>compose</em></span> menu providing the functions
-shown in <a class="xref" href="#tab-func-compose" title="Table 2.11. Most common compose menu keys">Table 2.11, “Most common compose menu keys”</a> to modify, send or postpone the
-message.
-</p><div class="table"><a id="tab-func-compose"></a><p class="title"><b>Table 2.11. Most common compose menu keys</b></p><div class="table-contents"><table summary="Most common compose menu keys" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Key</th><th>Function</th><th>Description</th></tr></thead><tbody><tr><td>a</td><td><code class="literal"><attach-file></code></td><td>attach a file</td></tr><tr><td>A</td><td><code class="literal"><attach-message></code></td><td>attach message(s) to the message</td></tr><tr><td>Esc k</td><td><code class="literal"><attach-key></code></td><td>attach a PGP public key</td></tr><tr><td>d</td><td><code class="literal"><edit-description></code></td><td>edit description on attachment</td></tr><tr><td>D</td><td><code class="literal"><detach-file></code></td><td>detach a file</td></tr><tr><td>t</td><td><code class="literal"><edit-to></code></td><td>edit the To field</td></tr><tr><td>Esc f</td><td><code class="literal"><edit-from></code></td><td>edit the From field</td></tr><tr><td>r</td><td><code class="literal"><edit-reply-to></code></td><td>edit the Reply-To field</td></tr><tr><td>c</td><td><code class="literal"><edit-cc></code></td><td>edit the Cc field</td></tr><tr><td>b</td><td><code class="literal"><edit-bcc></code></td><td>edit the Bcc field</td></tr><tr><td>y</td><td><code class="literal"><send-message></code></td><td>send the message</td></tr><tr><td>s</td><td><code class="literal"><edit-subject></code></td><td>edit the Subject</td></tr><tr><td>S</td><td><code class="literal"><smime-menu></code></td><td>select S/MIME options</td></tr><tr><td>f</td><td><code class="literal"><edit-fcc></code></td><td>specify an “<span class="quote">Fcc</span>” mailbox</td></tr><tr><td>p</td><td><code class="literal"><pgp-menu></code></td><td>select PGP options</td></tr><tr><td>P</td><td><code class="literal"><postpone-message></code></td><td>postpone this message until later</td></tr><tr><td>q</td><td><code class="literal"><quit></code></td><td>quit (abort) sending the message</td></tr><tr><td>w</td><td><code class="literal"><write-fcc></code></td><td>write the message to a folder</td></tr><tr><td>i</td><td><code class="literal"><ispell></code></td><td>check spelling (if available on your system)</td></tr><tr><td>^F</td><td><code class="literal"><forget-passphrase></code></td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The compose menu is also used to edit the attachments for a message which can be either files
-or other messages. The <code class="literal"><attach-message></code> function to will prompt you for a folder to
-attach messages from. You can now tag messages in that folder and they
-will be attached to the message you are sending.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that certain
-operations like composing a new mail, replying, forwarding, etc. are
-not permitted when you are in that folder. The %r in
-<a class="link" href="#status-format" title="3.278. status_format">$status_format</a> will change to
-a “<span class="quote">A</span>” to indicate that you are in attach-message mode.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-header"></a>5.2. Editing the message header</h3></div></div></div><p>
-When editing the header because of <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>
-being set, there are a several pseudo headers available which
-will not be included in sent messages.
-</p><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="fcc-header"></a>5.2.1. Fcc: pseudo header</h4></div></div></div><p>
-If you specify
-
-<code class="literal">Fcc:</code> <span class="emphasis"><em>filename</em></span>
-
-as a header, Mutt will pick up <span class="emphasis"><em>filename</em></span>
-just as if you had used the <code class="literal"><edit-fcc></code> function in the <span class="emphasis"><em>compose</em></span> menu.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="attach-header"></a>5.2.2. Attach: pseudo header</h4></div></div></div><p>
-You can also attach files to your message by specifying
-
-<code class="literal">Attach:</code> <span class="emphasis"><em>filename</em></span> [ <span class="emphasis"><em>description</em></span> ]
-
-where <span class="emphasis"><em>filename</em></span> is the file to attach and <span class="emphasis"><em>description</em></span> is an
-optional string to use as the description of the attached file.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="pgp-header"></a>5.2.3. Pgp: pseudo header</h4></div></div></div><p>
-If you want to use PGP, you can specify
-</p><p>
-<code class="literal">Pgp:</code> [ <code class="literal">E</code> | <code class="literal">S</code> | <code class="literal">S</code><span class="emphasis"><em><id></em></span> ]
-
-</p><p>
-“<span class="quote">E</span>” selects encryption, “<span class="quote">S</span>” selects signing and
-“<span class="quote">S<id></span>” selects signing with the given key, setting
-<a class="link" href="#pgp-sign-as" title="3.163. pgp_sign_as">$pgp_sign_as</a>
-permanently.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="in-reply-to-header"></a>5.2.4. In-Reply-To: header</h4></div></div></div><p>
-When replying to messages, the <span class="emphasis"><em>In-Reply-To:</em></span> header contains the
-Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
-<span class="emphasis"><em>References:</em></span> field, which allows you to create a new message thread, for example
-to create a new message to a mailing list without having to enter the mailing list's address.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-crypto"></a>5.3. Sending cryptographically signed/encrypted messages</h3></div></div></div><p>
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
-through a key selection process when you try to send the message.
-Mutt 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.
-</p><p>
-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 <code class="literal">^G</code>. When you do so, mutt will
-return to the compose screen.
-</p><p>
-Once you have successfully finished the key selection, the message
-will be encrypted using the selected public keys when sent out.
-</p><p>
-Most fields of the entries in the key selection menu (see also <a class="link" href="#pgp-entry-format" title="3.155. pgp_entry_format">$pgp_entry_format</a>)
-have obvious meanings. But some explanations on the capabilities, flags,
-and validity fields are in order.
-</p><p>
-The flags sequence (%f) will expand to one of the flags in
-<a class="xref" href="#tab-pgp-menuflags" title="Table 2.12. PGP key menu flags">Table 2.12, “PGP key menu flags”</a>.
-</p><div class="table"><a id="tab-pgp-menuflags"></a><p class="title"><b>Table 2.12. PGP key menu flags</b></p><div class="table-contents"><table summary="PGP key menu flags" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Flag</th><th>Description</th></tr></thead><tbody><tr><td>R</td><td>The key has been revoked and can't be used.</td></tr><tr><td>X</td><td>The key is expired and can't be used.</td></tr><tr><td>d</td><td>You have marked the key as disabled.</td></tr><tr><td>c</td><td>There are unknown critical self-signature packets.</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The capabilities field (%c) expands to a two-character sequence
-representing a key's capabilities. The first character gives
-the key's encryption capabilities: A minus sign (“<span class="quote">-</span>”) means
-that the key cannot be used for encryption. A dot (“<span class="quote">.</span>”) means that
-it's marked as a signature key in one of the user IDs, but may
-also be used for encryption. The letter “<span class="quote">e</span>” indicates that
-this key can be used for encryption.
-</p><p>
-The second character indicates the key's signing capabilities. Once
-again, a “<span class="quote">-</span>” implies “<span class="quote">not for signing</span>”, “<span class="quote">.</span>” implies
-that the key is marked as an encryption key in one of the user-ids, and
-“<span class="quote">s</span>” denotes a key which can be used for signing.
-</p><p>
-Finally, the validity field (%t) indicates how well-certified a user-id
-is. A question mark (“<span class="quote">?</span>”) indicates undefined validity, a minus
-character (“<span class="quote">-</span>”) marks an untrusted association, a space character
-means a partially trusted association, and a plus character (“<span class="quote">+</span>”)
-indicates complete validity.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sending-mixmaster"></a>5.4. Sending anonymous messages via mixmaster</h3></div></div></div><p>
-You may also have compiled 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.
-</p><p>
-To use it, you'll have to obey certain restrictions. Most
-important, you cannot use the <code class="literal">Cc</code> and <code class="literal">Bcc</code> headers. To tell
-Mutt to use mixmaster, you have to select a remailer chain, using
-the mix function on the compose menu.
-</p><p>
-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.
-</p><p>
-You can navigate in the chain using the <code class="literal"><chain-prev></code> and
-<code class="literal"><chain-next></code> functions, which are by default bound to the left
-and right arrows and to the <code class="literal">h</code> and <code class="literal">l</code> keys (think vi
-keyboard bindings). To insert a remailer at the current chain
-position, use the <code class="literal"><insert></code> function. To append a remailer behind
-the current chain position, use <code class="literal"><select-entry></code> or <code class="literal"><append></code>.
-You can also delete entries from the chain, using the corresponding
-function. Finally, to abandon your changes, leave the menu, or
-<code class="literal"><accept></code> them pressing (by default) the <code class="literal">Return</code> key.
-</p><p>
-Note that different remailers do have different capabilities,
-indicated in the %c entry of the remailer menu lines (see
-<a class="link" href="#mix-entry-format" title="3.130. mix_entry_format">$mix_entry_format</a>). Most important is
-the “<span class="quote">middleman</span>” capability, indicated by a capital “<span class="quote">M</span>”: 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ff"></a>5.5. Sending format=flowed messages</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-concept"></a>5.5.1. Concept</h4></div></div></div><p>
-<code class="literal">format=flowed</code>-style messages (or <code class="literal">f=f</code>
-for short) are <code class="literal">text/plain</code> messages that consist of paragraphs which a receiver's
-mail client may reformat to its own needs which mostly means to
-customize line lengths regardless of what the sender sent. Technically this is
-achieved by letting lines of a “<span class="quote">flowable</span>” paragraph end in spaces
-except for the last line.
-</p><p>
-While for text-mode clients like mutt it's the best way to assume only a
-standard 80x25 character cell terminal, it may be desired to let the
-receiver decide completely how to view a message.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-support"></a>5.5.2. Mutt support</h4></div></div></div><p>
-Mutt only supports setting the required <code class="literal">format=flowed</code>
-MIME parameter on outgoing messages if the <a class="link" href="#text-flowed" title="3.282. text_flowed">$text_flowed</a>
-variable is set, specifically it does not add the
-trailing spaces.
-</p><p>
-After editing the initial message text and before entering
-the compose menu, mutt properly space-stuffes the message.
-<span class="emphasis"><em>Space-stuffing</em></span> is required by RfC3676 defining
-<code class="literal">format=flowed</code> and means to prepend a space to:
-</p><div class="itemizedlist"><ul type="disc"><li><p>all lines starting with a space</p></li><li><p>lines starting with the word “<span class="quote"><code class="literal">From</code></span>”
-followed by space</p></li><li><p>all lines starting with “<span class="quote"><code class="literal">></code></span>” which
-is not intended to be a quote character</p></li></ul></div><div class="note"><h3 class="title">Note</h3><p>
-Mutt only supports space-stuffing
-for the first two types of lines but not for the third: It is impossible to
-safely detect whether a leading <code class="literal">></code> character starts a
-quote or not. Furthermore, Mutt only applies space-stuffing
-<span class="emphasis"><em>once</em></span> after the initial edit is finished.
-</p></div><p>
-All leading spaces are to be removed by receiving clients to restore
-the original message prior to further processing.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="ff-editor"></a>5.5.3. Editor considerations</h4></div></div></div><p>
-As mutt provides no additional features to compose <code class="literal">f=f</code>
-messages, it's completely up to the user and his editor to produce
-proper messages. Please consider your editor's documentation if you
-intend to send <code class="literal">f=f</code> messages.
-</p><p>
-Please note that when editing messages from the compose menu several
-times before really sending a mail, it's up to the user to ensure that
-the message is properly space-stuffed.
-</p><p>
-For example, <span class="emphasis"><em>vim</em></span> provides the <code class="literal">w</code>
-flag for its <code class="literal">formatoptions</code> setting to assist in
-creating <code class="literal">f=f</code> messages, see <code class="literal">:help
-fo-table</code> for details.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="forwarding-mail"></a>6. Forwarding and Bouncing Mail</h2></div></div></div><p>
-Bouncing and forwarding let you send an existing message to recipients
-that you specify. Bouncing a message sends a verbatim copy of a message
-to alternative addresses as if they were the message's original
-recipients specified in the Bcc header.
-Forwarding a message, on the other hand, allows you to modify the message
-before it is resent (for example, by adding your own comments). Bouncing
-is done using the <code class="literal"><bounce></code> function and forwarding
-using the <code class="literal"><forward></code> function bound to “<span class="quote">b</span>” and “<span class="quote">f</span>”
-respectively.
-</p><p>
-Forwarding can be done by including the original message in the new
-message's body (surrounded by indicating lines) or including it as a MIME
-attachment, depending on the value of the <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> variable. Decoding of attachments,
-like in the pager, can be controlled by the <a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> variables,
-respectively. The desired forwarding format may depend on the content,
-therefore <span class="emphasis"><em>$mime_forward</em></span> is a quadoption which, for
-example, can be set to “<span class="quote">ask-no</span>”.
-</p><p>
-The inclusion of headers is controlled by the current setting of the
-<a class="link" href="#weed" title="3.301. weed">$weed</a> variable, unless <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is set.
-</p><p>
-Editing the message to forward follows the same procedure as sending or
-replying to a message does.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="postponing-mail"></a>7. Postponing Mail</h2></div></div></div><p>
-At times it is desirable to delay sending a message that you have
-already begun to compose. When the <code class="literal"><postpone-message></code> function is
-used in the <span class="emphasis"><em>compose</em></span> menu, the body of your message and attachments
-are stored in the mailbox specified by the <a class="link" href="#postponed" title="3.224. postponed">$postponed</a> variable. This means that you can recall the
-message even if you exit Mutt and then restart it at a later time.
-</p><p>
-Once a message is postponed, there are several ways to resume it. From the
-command line you can use the “<span class="quote">-p</span>” option, or if you compose a new
-message from the <span class="emphasis"><em>index</em></span> or <span class="emphasis"><em>pager</em></span> you will be prompted if postponed
-messages exist. If multiple messages are currently postponed, the
-<span class="emphasis"><em>postponed</em></span> menu will pop up and you can select which message you would
-like to resume.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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.
-</p></div><p>
-See also the <a class="link" href="#postpone" title="3.223. postpone">$postpone</a> quad-option.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="configuration"></a>Chapter 3. Configuration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#configuration-files">1. Location of initialization files</a></span></dt><dt><span class="sect1"><a href="#muttrc-syntax">2. Syntax of Initialization Files</a></span></dt><dt><span class="sect1"><a href="#addrgroup">3. Address groups</a></span></dt><dt><span class="sect1"><a href="#alias">4. Defining/Using aliases</a></span></dt><dt><span class="sect1"><a href="#bind">5. Changing the default key bindings</a></span></dt><dt><span class="sect1"><a href="#charset-hook">6. Defining aliases for character sets </a></span></dt><dt><span class="sect1"><a href="#folder-hook">7. Setting variables based upon mailbox</a></span></dt><dt><span class="sect1"><a href="#macro">8. Keyboard macros</a></span></dt><dt><span class="sect1"><a href="#color">9. Using color and mono video attributes</a></span></dt><dt><span class="sect1"><a href="#ignore">10. Message header display</a></span></dt><dt><span class="sect1"><a href="#alternates">11. Alternative addresses</a></span></dt><dt><span class="sect1"><a href="#lists">12. Mailing lists</a></span></dt><dt><span class="sect1"><a href="#mbox-hook">13. Using Multiple spool mailboxes</a></span></dt><dt><span class="sect1"><a href="#mailboxes">14. Monitoring incoming mail</a></span></dt><dt><span class="sect1"><a href="#my-hdr">15. User defined headers</a></span></dt><dt><span class="sect1"><a href="#save-hook">16. Specify default save mailbox</a></span></dt><dt><span class="sect1"><a href="#fcc-hook">17. Specify default Fcc: mailbox when composing</a></span></dt><dt><span class="sect1"><a href="#fcc-save-hook">18. Specify default save filename and default Fcc: mailbox at once</a></span></dt><dt><span class="sect1"><a href="#send-hook">19. Change settings based upon message recipients</a></span></dt><dt><span class="sect1"><a href="#message-hook">20. Change settings before formatting a message</a></span></dt><dt><span class="sect1"><a href="#crypt-hook">21. Choosing the cryptographic key of the recipient</a></span></dt><dt><span class="sect1"><a href="#push">22. Adding key sequences to the keyboard buffer</a></span></dt><dt><span class="sect1"><a href="#exec">23. Executing functions</a></span></dt><dt><span class="sect1"><a href="#score-command">24. Message Scoring</a></span></dt><dt><span class="sect1"><a href="#spam">25. Spam detection</a></span></dt><dt><span class="sect1"><a href="#set">26. Setting and Querying Variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#set-commands">26.1. Commands</a></span></dt><dt><span class="sect2"><a href="#set-myvar">26.2. User-defined variables</a></span></dt></dl></dd><dt><span class="sect1"><a href="#source">27. Reading initialization commands from another file</a></span></dt><dt><span class="sect1"><a href="#ifdef">28. Configuring features conditionnaly</a></span></dt><dt><span class="sect1"><a href="#unhook">29. Removing hooks</a></span></dt><dt><span class="sect1"><a href="#formatstrings">30. Format Strings</a></span></dt><dd><dl><dt><span class="sect2"><a href="#formatstrings-basics">30.1. Basic usage</a></span></dt><dt><span class="sect2"><a href="#formatstrings-filters">30.2. Filters</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="configuration-files"></a>1. Location of initialization files</h2></div></div></div><p>
-While the default configuration (or “<span class="quote">preferences</span>”) make Mutt
-usable right out of the box, it is often desirable to tailor Mutt to
-suit your own tastes. When Mutt is first invoked, it will attempt to
-read the “<span class="quote">system</span>” configuration file (defaults set by your local
-system administrator), unless the “<span class="quote">-n</span>” <a class="link" href="#commandline" title="1. Command line options">command line</a> option is specified. This file is typically
-<code class="literal">/usr/local/share/mutt/Muttrc</code> or <code class="literal">/etc/Muttrc</code>. Mutt
-will next look for a file named <code class="literal">.muttrc</code> in your home
-directory. If this file does not exist and your home directory has
-a subdirectory named <code class="literal">.mutt</code>, mutt try to load a file named
-<code class="literal">.mutt/muttrc</code>.
-</p><p>
-<code class="literal">.muttrc</code> is the file where you will usually place your <a class="link" href="#commands" title="2. Configuration Commands">commands</a> to configure Mutt.
-</p><p>
-In addition, mutt supports version specific configuration files that are
-parsed instead of the default files as explained above. For instance, if
-your system has a <code class="literal">Muttrc-0.88</code> file in the system configuration
-directory, and you are running version 0.88 of mutt, this file will be
-sourced instead of the <code class="literal">Muttrc</code> file. The same is true of the user
-configuration file, if you have a file <code class="literal">.muttrc-0.88.6</code> in your home
-directory, when you run mutt version 0.88.6, it will source this file
-instead of the default <code class="literal">.muttrc</code> file. The version number is the
-same which is visible using the “<span class="quote">-v</span>” <a class="link" href="#commandline" title="1. Command line options">command line</a> switch or using the <code class="literal">show-version</code> key (default:
-V) from the index menu.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="muttrc-syntax"></a>2. Syntax of Initialization Files</h2></div></div></div><p>
-An initialization file consists of a series of <a class="link" href="#commands" title="2. Configuration Commands">commands</a>. Each line of the file may contain one or more commands.
-When multiple commands are used, they must be separated by a semicolon
-(;).
-</p><div class="example"><a id="ex-rc-multiple-cmds"></a><p class="title"><b>Example 3.1. Multiple configuration commands per line</b></p><div class="example-contents"><pre class="screen">
-set realname='Mutt user' ; ignore x-
-</pre></div></div><br class="example-break" /><p>
-The hash mark, or pound sign
-(“<span class="quote">#</span>”), is used as a “<span class="quote">comment</span>” 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,
-</p><div class="example"><a id="ex-ec-comment"></a><p class="title"><b>Example 3.2. Commenting configuration files</b></p><div class="example-contents"><pre class="screen">
-my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
-</pre></div></div><br class="example-break" /><p>
-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, backticks are evaluated inside of double
-quotes, but <span class="bold"><strong>not</strong></span> for single quotes.
-</p><p>
-\ quotes the next character, just as in shells such as bash and zsh.
-For example, if want to put quotes “<span class="quote">"</span>” inside of a string, you can use
-“<span class="quote">\</span>” to force the next character to be a literal instead of interpreted
-character.
-</p><div class="example"><a id="ex-rc-quote"></a><p class="title"><b>Example 3.3. Escaping quotes in congfiguration files</b></p><div class="example-contents"><pre class="screen">
-set realname="Michael \"MuttDude\" Elkins"
-</pre></div></div><br class="example-break" /><p>
-“<span class="quote">\\</span>” means to insert a literal “<span class="quote">\</span>” into the line.
-“<span class="quote">\n</span>” and “<span class="quote">\r</span>” have their usual C meanings of linefeed and
-carriage-return, respectively.
-</p><p>
-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.
-</p><p>
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command in
-backticks (``). For example,
-</p><div class="example"><a id="ex-rc-backtick"></a><p class="title"><b>Example 3.4. Using external command's output in configuration files</b></p><div class="example-contents"><pre class="screen">
-my_hdr X-Operating-System: `uname -a`
-</pre></div></div><br class="example-break" /><p>
-The output of the Unix command “<span class="quote">uname -a</span>” will be substituted before the
-line is parsed.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Since initialization files are line oriented, only
-the first line of output from the Unix command will be substituted.
-</p></div><p>
-Both environment variables and mutt variables can be accessed by
-prepending “<span class="quote">$</span>” to the name of the variable. For example,
-</p><div class="example"><a id="ex-rc-env"></a><p class="title"><b>Example 3.5. Using environment variables in configuration files</b></p><div class="example-contents"><pre class="screen">
-set record=+sent_on_$HOSTNAME
-</pre></div></div><br class="example-break" /><p>
-will cause mutt to save outgoing messages to a folder named
-“<span class="quote">sent_on_kremvax</span>” if the environment variable HOSTNAME is set to
-“<span class="quote">kremvax.</span>” (See <a class="link" href="#record" title="3.239. record">$record</a> for
-details.)
-</p><p>
-Mutt expands the variable when it is assigned, not when it is used. If
-the value of a variable on the right-hand side of an assignment
-changes after the assignment, the variable on the left-hand side will
-not be affected.
-</p><p>
-The commands understood by mutt are explained in the next paragraphs.
-For a complete list, see the <a class="link" href="#commands" title="2. Configuration Commands">command reference</a>.
-</p><p>
-All configuration files are expected to be in the current locale as
-specified by the <a class="link" href="#charset" title="3.25. charset">$charset</a> variable
-which doesn't have a default value since it's determined by Mutt at startup.
-If a configuration file is not encoded in the same character set the
-<a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a>
-variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
-</p><p>
-This mechanism should be avoided if possible as it has the
-following implications:
-</p><div class="itemizedlist"><ul type="disc"><li><p>These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.</p></li><li><p>If $config_charset is set, it should be set
-in each configuration file because the value is global and <span class="emphasis"><em>not</em></span>
-per configuration file.</p></li><li><p>Because Mutt first recodes a line before it attempts to parse it,
-a conversion introducing question marks or other characters as
-part of errors (unconvertable characters, transliteration) may introduce syntax
-errors or silently change the meaning of certain tokens (e.g. inserting
-question marks into regular expressions).</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="addrgroup"></a>3. Address groups</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">group</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div><div class="cmdsynopsis"><p><code class="command">ungroup</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div><p>
-<code class="literal">group</code> is used to directly add either addresses or
-regular expressions to the specified group or groups. The different
-categories of arguments to the <code class="literal">group</code> command can be
-in any order. The flags <code class="literal">-rx</code> and
-<code class="literal">-addr</code> specify what the following strings (that cannot
-begin with a hyphen) should be interpreted as: either a regular
-expression or an email address, respectively.
-</p><p>
-These address groups can also be created implicitly by the
-<a class="link" href="#alias" title="4. Defining/Using aliases">alias</a>, <a class="link" href="#lists" title="12. Mailing lists">lists</a>,
-<a class="link" href="#lists" title="12. Mailing lists">subscribe</a> and
-<a class="link" href="#alternates" title="11. Alternative addresses">alternates</a> commands by specifying the
-optional <code class="literal">-group</code> option.
-</p><p>
-Once defined, these address groups can be used in
-<a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> to search for and limit the
-display to messages matching a group.
-</p><p>
-<code class="literal">ungroup</code> is used to remove addresses or regular
-expressions from the specified group or groups. The syntax is similar to
-the <code class="literal">group</code> command, however the special character
-<code class="literal">*</code> can be used to empty a group of all of its
-contents.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alias"></a>4. Defining/Using aliases</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alias</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>address</code></em>
- [
-<em class="replaceable"><code>address</code></em>
-...]</p></div><p>
-It's usually very cumbersome to remember or type out the address of someone
-you are communicating with. Mutt allows you to create “<span class="quote">aliases</span>” which map
-a short string to a full address.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you want to create an alias for more than
-one address, you <span class="bold"><strong>must</strong></span> separate the addresses with a comma (“<span class="quote">,</span>”).
-</p></div><p>
-The optional <code class="literal">-group</code> argument to
-<code class="literal">alias</code> causes the aliased address(es) to be added to
-the named <span class="emphasis"><em>group</em></span>.
-</p><p>
-To remove an alias or aliases (“<span class="quote">*</span>” means all aliases):
-</p><div class="cmdsynopsis"><p><code class="command">unalias</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>key</code></em>
-... }</p></div><pre class="screen">
-alias muttdude me@cs.hmc.edu (Michael Elkins)
-alias theguys manny, moe, jack
-</pre><p>
-Unlike other mailers, Mutt doesn't require aliases to be defined
-in a special file. The <code class="literal">alias</code> command can appear anywhere in
-a configuration file, as long as this file is <a class="link" href="#source" title="27. Reading initialization commands from another file">sourced</a>. Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
-</p><p>
-On the other hand, the <a class="link" href="#create-alias"><code class="literal"><create-alias></code></a>
-function can use only one file, the one pointed to by the <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> variable (which is
-<code class="literal">˜/.muttrc</code> by default). This file is not special either,
-in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> this file too.
-</p><p>
-For example:
-</p><div class="example"><a id="ex-alias-external"></a><p class="title"><b>Example 3.6. Configuring external alias files</b></p><div class="example-contents"><pre class="screen">
-source /usr/local/share/Mutt.aliases
-source ~/.mail_aliases
-set alias_file=~/.mail_aliases
-</pre></div></div><br class="example-break" /><p>
-To use aliases, you merely use the alias at any place in mutt where mutt
-prompts for addresses, such as the <span class="emphasis"><em>To:</em></span> or <span class="emphasis"><em>Cc:</em></span> prompt. You can
-also enter aliases in your editor at the appropriate headers if you have the
-<a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable set.
-</p><p>
-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.
-</p><p>
-In the alias menu, you can select as many aliases as you want with the
-<code class="literal">select-entry</code> key (default: <Return>), and use the
-<span class="emphasis"><em>exit</em></span> key (default: q) to return to the address prompt.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="bind"></a>5. Changing the default key bindings</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">bind</code>
-<em class="replaceable"><code>map</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>function</code></em>
- </p></div><p>
-This command allows you to change the default key bindings (operation
-invoked when pressing a key).
-</p><p>
-<span class="emphasis"><em>map</em></span> specifies in which menu the binding belongs. Multiple maps may
-be specified by separating them with commas (no additional whitespace is
-allowed). The currently defined maps are:
-</p><a id="maps"></a><div class="variablelist"><dl><dt><span class="term">generic</span></dt><dd><p>
-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 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.
-</p></dd><dt><span class="term">alias</span></dt><dd><p>
-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).
-</p></dd><dt><span class="term">attach</span></dt><dd><p>
-The attachment menu is used to access the attachments on received messages.
-</p></dd><dt><span class="term">browser</span></dt><dd><p>
-The browser is used for both browsing the local directory structure, and for
-listing all of your incoming mailboxes.
-</p></dd><dt><span class="term">editor</span></dt><dd><p>
-The editor is the line-based editor the user enters text data.
-</p></dd><dt><span class="term">index</span></dt><dd><p>
-The index is the list of messages contained in a mailbox.
-</p></dd><dt><span class="term">compose</span></dt><dd><p>
-The compose menu is the screen used when sending a new message.
-</p></dd><dt><span class="term">pager</span></dt><dd><p>
-The pager is the mode used to display message/attachment data, and help
-listings.
-</p></dd><dt><span class="term">pgp</span></dt><dd><p>
-The pgp menu is used to select the OpenPGP keys used to encrypt outgoing
-messages.
-</p></dd><dt><span class="term">smime</span></dt><dd><p>
-The smime menu is used to select the OpenSSL certificates used to encrypt outgoing
-messages.
-</p></dd><dt><span class="term">postpone</span></dt><dd><p>
-The postpone menu is similar to the index menu, except is used when
-recalling a message the user was composing, but saved until later.
-</p></dd><dt><span class="term">query</span></dt><dd><p>
-The query menu is the browser for results returned by
-<a class="link" href="#query-command" title="3.231. query_command">$query_command</a>.
-</p></dd><dt><span class="term">mix</span></dt><dd><p>
-The mixmaster screen is used to select remailer options for outgoing
-messages (if Mutt is compiled with Mixmaster support).
-</p></dd></dl></div><p>
-<span class="emphasis"><em>key</em></span> is the key (or key sequence) you wish to bind. To specify a
-control character, use the sequence <span class="emphasis"><em>\Cx</em></span>, where <span class="emphasis"><em>x</em></span> is the
-letter of the control character (for example, to specify control-A use
-“<span class="quote">\Ca</span>”). Note that the case of <span class="emphasis"><em>x</em></span> as well as <span class="emphasis"><em>\C</em></span> is
-ignored, so that <span class="emphasis"><em>\CA</em></span>, <span class="emphasis"><em>\Ca</em></span>, <span class="emphasis"><em>\cA</em></span> and <span class="emphasis"><em>\ca</em></span> are all
-equivalent. An alternative form is to specify the key as a three digit
-octal number prefixed with a “<span class="quote">\</span>” (for example <span class="emphasis"><em>\177</em></span> is
-equivalent to <span class="emphasis"><em>\c?</em></span>). In addition, <span class="emphasis"><em>key</em></span> may
-be a symbolic name as shown in <a class="xref" href="#tab-key-names" title="Table 3.1. Symbolic key names">Table 3.1, “Symbolic key names”</a>.
-</p><div class="table"><a id="tab-key-names"></a><p class="title"><b>Table 3.1. Symbolic key names</b></p><div class="table-contents"><table summary="Symbolic key names" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Symbolic name</th><th>Meaning</th></tr></thead><tbody><tr><td>\t</td><td>tab</td></tr><tr><td><tab></td><td>tab</td></tr><tr><td><backtab></td><td>backtab / shift-tab</td></tr><tr><td>\r</td><td>carriage return</td></tr><tr><td>\n</td><td>newline</td></tr><tr><td>\e</td><td>escape</td></tr><tr><td><esc></td><td>escape</td></tr><tr><td><up></td><td>up arrow</td></tr><tr><td><down></td><td>down arrow</td></tr><tr><td><left></td><td>left arrow</td></tr><tr><td><right></td><td>right arrow</td></tr><tr><td><pageup></td><td>Page Up</td></tr><tr><td><pagedown></td><td>Page Down</td></tr><tr><td><backspace></td><td>Backspace</td></tr><tr><td><delete></td><td>Delete</td></tr><tr><td><insert></td><td>Insert</td></tr><tr><td><enter></td><td>Enter</td></tr><tr><td><return></td><td>Return</td></tr><tr><td><home></td><td>Home</td></tr><tr><td><end></td><td>End</td></tr><tr><td><space></td><td>Space bar</td></tr><tr><td><f1></td><td>function key 1</td></tr><tr><td><f10></td><td>function key 10</td></tr></tbody></table></div></div><br class="table-break" /><p>
-<span class="emphasis"><em>key</em></span> does not need to be enclosed in quotes unless it contains a
-space (“<span class="quote"> </span>”) or semi-colon (“<span class="quote">;</span>”).
-</p><p>
-<span class="emphasis"><em>function</em></span> specifies which action to take when <span class="emphasis"><em>key</em></span> is pressed.
-For a complete list of functions, see the <a class="link" href="#functions" title="4. Functions">reference</a>. The special function <code class="literal"><noop></code> unbinds the specified key
-sequence.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="charset-hook"></a>6. Defining aliases for character sets </h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">charset-hook</code>
-<em class="replaceable"><code>alias</code></em>
-
-<em class="replaceable"><code>charset</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">iconv-hook</code>
-<em class="replaceable"><code>charset</code></em>
-
-<em class="replaceable"><code>local-charset</code></em>
- </p></div><p>
-The <code class="literal">charset-hook</code> 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.
-</p><p>
-The <code class="literal">iconv-hook</code> 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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="folder-hook"></a>7. Setting variables based upon mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">folder-hook</code>
-<em class="replaceable"><code>[!]regexp</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-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. <span class="emphasis"><em>regexp</em></span> is a regular expression specifying
-in which mailboxes to execute <span class="emphasis"><em>command</em></span> before loading. If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you use the “<span class="quote">!</span>” shortcut for <a class="link" href="#spoolfile" title="3.276. spoolfile">$spoolfile</a> at the beginning of the pattern, you must place it
-inside of double or single quotes in order to distinguish it from the
-logical <span class="emphasis"><em>not</em></span> operator for the expression.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-Settings are <span class="emphasis"><em>not</em></span> restored when you leave the mailbox.
-For example, a command action to perform is to change the sorting method
-based upon the mailbox being read:
-</p></div><pre class="screen">
-folder-hook mutt set sort=threads
-</pre><p>
-However, the sorting method is not restored to its previous value when
-reading a different mailbox. To specify a <span class="emphasis"><em>default</em></span> command, use the
-pattern “<span class="quote">.</span>” before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
-The following example will set the <a class="link" href="#sort" title="3.270. sort">sort</a> variable
-to <code class="literal">date-sent</code> for all folders but to <code class="literal">threads</code>
-for all folders containing “<span class="quote">mutt</span>” in their name.
-</p><div class="example"><a id="ex-folder-sorting"></a><p class="title"><b>Example 3.7. Setting sort method based on mailbox name</b></p><div class="example-contents"><pre class="screen">
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="macro"></a>8. Keyboard macros</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">macro</code>
-<em class="replaceable"><code>menu</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>sequence</code></em>
- [
-<em class="replaceable"><code>description</code></em>
-]</p></div><p>
-Macros are useful when you would like a single key to perform a series of
-actions. When you press <span class="emphasis"><em>key</em></span> in menu <span class="emphasis"><em>menu</em></span>, Mutt will behave as if
-you had typed <span class="emphasis"><em>sequence</em></span>. So if you have a common sequence of commands
-you type, you can create a macro to execute those commands with a single
-key or fewer keys.
-</p><p>
-<span class="emphasis"><em>menu</em></span> is the <a class="link" href="#maps">map</a> which the macro will be bound in.
-Multiple maps may be specified by separating multiple menu arguments by
-commas. Whitespace may not be used in between the menu arguments and the
-commas separating them.
-</p><p>
-<span class="emphasis"><em>key</em></span> and <span class="emphasis"><em>sequence</em></span> are expanded by the same rules as the
-<a class="link" href="#bind" title="5. Changing the default key bindings">key bindings</a> with some additions. The
-first is that control characters in <span class="emphasis"><em>sequence</em></span> can also be specified
-as <span class="emphasis"><em>^x</em></span>. In order to get a caret (“<span class="quote">^</span>”) you need to use
-<span class="emphasis"><em>^^</em></span>. Secondly, to specify a certain key such as <span class="emphasis"><em>up</em></span>
-or to invoke a function directly, you can use the format
-<span class="emphasis"><em><key name></em></span> and <span class="emphasis"><em><function name></em></span>. For a listing of key
-names see the section on <a class="link" href="#bind" title="5. Changing the default key bindings">key bindings</a>. Functions
-are listed in the <a class="link" href="#functions" title="4. Functions">reference</a>.
-</p><p>
-The advantage with using function names directly is that the macros will
-work regardless of the current key bindings, so they are not dependent on
-the user having particular key definitions. This makes them more robust
-and portable, and also facilitates defining of macros in files used by more
-than one user (e.g., the system Muttrc).
-</p><p>
-Optionally you can specify a descriptive text after <span class="emphasis"><em>sequence</em></span>,
-which is shown in the help screens.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Macro definitions (if any) listed in the help screen(s), are
-silently truncated at the screen width, and are not wrapped.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="color"></a>9. Using color and mono video attributes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">color</code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">color</code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">color</code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">uncolor</code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-If your terminal supports color, you can spice up Mutt by creating your own
-color scheme. To define the color of an object (type of information), you
-must specify both a foreground color <span class="bold"><strong>and</strong></span> a background color (it is not
-possible to only specify one or the other).
-</p><p>
-<span class="emphasis"><em>header</em></span> and <span class="emphasis"><em>body</em></span> match <span class="emphasis"><em>regexp</em></span>
-in the header/body of a message, <span class="emphasis"><em>index</em></span> matches <span class="emphasis"><em>pattern</em></span>
-(see <a class="xref" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">Section 2, “Patterns: Searching, Limiting and Tagging”</a>) in the message index.
-</p><p>
-<span class="emphasis"><em>object</em></span> can be one of:
-</p><div class="itemizedlist"><ul type="disc"><li><p>attachment</p></li><li><p>bold (hiliting bold patterns in the body of messages)</p></li><li><p>error (error messages printed by Mutt)</p></li><li><p>hdrdefault (default color of the message header in the pager)</p></li><li><p>indicator (arrow or bar used to indicate the current item in a menu)</p></li><li><p>markers (the “<span class="quote">+</span>” markers at the beginning of wrapped lines in the pager)</p></li><li><p>message (informational messages)</p></li><li><p>normal</p></li><li><p>quoted (text matching <a class="link" href="#quote-regexp" title="3.234. quote_regexp">$quote_regexp</a> in the body of a message)</p></li><li><p>quoted1, quoted2, ..., quoted<span class="bold"><strong>N</strong></span> (higher levels of quoting)</p></li><li><p>search (hiliting of words in the pager)</p></li><li><p>signature</p></li><li><p>status (mode lines used to display info about the mailbox or message)</p></li><li><p>tilde (the “<span class="quote">˜</span>” used to pad blank lines in the pager)</p></li><li><p>tree (thread tree drawn in the message index and attachment menu)</p></li><li><p>underline (hiliting underlined patterns in the body of messages)</p></li></ul></div><p>
-<span class="emphasis"><em>foreground</em></span> and <span class="emphasis"><em>background</em></span> can be one of the following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>white</p></li><li><p>black</p></li><li><p>green</p></li><li><p>magenta</p></li><li><p>blue</p></li><li><p>cyan</p></li><li><p>yellow</p></li><li><p>red</p></li><li><p>default</p></li><li><p>color<span class="emphasis"><em>x</em></span></p></li></ul></div><p>
-<span class="emphasis"><em>foreground</em></span> can optionally be prefixed with the keyword <code class="literal">bright</code> to make
-the foreground color boldfaced (e.g., <code class="literal">brightred</code>).
-</p><p>
-If your terminal supports it, the special keyword <span class="emphasis"><em>default</em></span> can be
-used as a transparent color. The value <span class="emphasis"><em>brightdefault</em></span> is also valid.
-If Mutt is linked against the <span class="emphasis"><em>S-Lang</em></span> library, you also need to set
-the <span class="emphasis"><em>COLORFGBG</em></span> environment variable to the default colors of your
-terminal for this to work; for example (for Bourne-like shells):
-</p><pre class="screen">
-set COLORFGBG="green;black"
-export COLORFGBG
-</pre><div class="note"><h3 class="title">Note</h3><p>
-The <span class="emphasis"><em>S-Lang</em></span> library requires you to use the <span class="emphasis"><em>lightgray</em></span>
-and <span class="emphasis"><em>brown</em></span> keywords instead of <span class="emphasis"><em>white</em></span> and <span class="emphasis"><em>yellow</em></span> when
-setting this variable.
-</p></div><div class="note"><h3 class="title">Note</h3><p>
-The uncolor command can be applied to the index object only. It
-removes entries from the list. You <span class="bold"><strong>must</strong></span> specify the same pattern
-specified in the color command for it to be removed. The pattern “<span class="quote">*</span>” is
-a special token which means to clear the color index list of all entries.
-</p></div><p>
-Mutt also recognizes the keywords <span class="emphasis"><em>color0</em></span>, <span class="emphasis"><em>color1</em></span>, …,
-<span class="emphasis"><em>color</em></span><span class="bold"><strong>N-1</strong></span> (<span class="bold"><strong>N</strong></span> 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 <span class="emphasis"><em>color2</em></span>
-for your xterm), since color names may then lose their normal meaning.
-</p><p>
-If your terminal does not support color, it is still possible change the video
-attributes through the use of the “<span class="quote">mono</span>” command:
-</p><a id="mono"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mono</code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>attribute</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">mono</code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">mono</code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unmono</code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-For <span class="emphasis"><em>object</em></span>, see the color command. <span class="emphasis"><em>attribute</em></span>
-can be one of the following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>none</p></li><li><p>bold</p></li><li><p>underline</p></li><li><p>reverse</p></li><li><p>standout</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ignore"></a>10. Message header display</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">ignore</code>
-<em class="replaceable"><code>pattern</code></em>
- [
-<em class="replaceable"><code>pattern</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unignore</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-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 in the pager.
-</p><p>
-You do not need to specify the full header field name. For example,
-“<span class="quote">ignore content-</span>” will ignore all header fields that begin with the pattern
-“<span class="quote">content-</span>”. “<span class="quote">ignore *</span>” will ignore all headers.
-</p><p>
-To remove a previously added token from the list, use the “<span class="quote">unignore</span>” command.
-The “<span class="quote">unignore</span>” command will make Mutt display headers with the given pattern.
-For example, if you do “<span class="quote">ignore x-</span>” it is possible to “<span class="quote">unignore x-mailer</span>”.
-</p><p>
-“<span class="quote">unignore *</span>” will remove all tokens from the ignore list.
-</p><p>
-For example:
-</p><div class="example"><a id="ex-header-weeding"></a><p class="title"><b>Example 3.8. Header weeding</b></p><div class="example-contents"><pre class="screen">
-# 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:
-</pre></div></div><br class="example-break" /><a id="hdr-order"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">hdr_order</code>
-<em class="replaceable"><code>header</code></em>
- [
-<em class="replaceable"><code>header</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unhdr_order</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>header</code></em>
-... }</p></div><p>
-With the <code class="literal">hdr_order</code> command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
-</p><p>
-“<span class="quote">unhdr_order *</span>” will clear all previous headers from the order list,
-thus removing the header order effects set by the system-wide startup file.
-</p><div class="example"><a id="ex-hdr-order"></a><p class="title"><b>Example 3.9. Configuring header display order</b></p><div class="example-contents"><pre class="screen">
-hdr_order From Date: From: To: Cc: Subject:
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternates"></a>11. Alternative addresses</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">alternates</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unalternates</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><p>
-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 <a class="link" href="#reply-to" title="3.242. reply_to">$reply_to</a>.)
-</p><p>
-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 <code class="literal">alternates</code> command: It takes a list of regular
-expressions, each of which can identify an address under which you
-receive e-mail.
-</p><p>
-As addresses are matched using regular expressions and not exact strict
-comparisons, you should make sure you specify your addresses as precise
-as possible to avoid mismatches. For example, if you specify:
-</p><pre class="screen">
-alternates user@example
-</pre><p>
-mutt will consider “<span class="quote"><code class="literal">some-user@example</code></span>” as
-being your address, too which may not be desired. As a solution, in such
-cases addresses should be specified as:
-</p><pre class="screen">
-alternates '^user@example$'
-</pre><p>
-The <code class="literal">-group</code> flag causes all of the subsequent regular expressions
-to be added to the named group.
-</p><p>
-The <code class="literal">unalternates</code> command can be used to write exceptions to
-<code class="literal">alternates</code> patterns. If an address matches something in an
-<code class="literal">alternates</code> command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an <code class="literal">unalternates</code>
-command.
-</p><p>
-To remove a regular expression from the <code class="literal">alternates</code> list, use the
-<code class="literal">unalternates</code> command with exactly the same <span class="emphasis"><em>regexp</em></span>.
-Likewise, if the <span class="emphasis"><em>regexp</em></span> for an <code class="literal">alternates</code> command matches
-an entry on the <code class="literal">unalternates</code> list, that <code class="literal">unalternates</code>
-entry will be removed. If the <span class="emphasis"><em>regexp</em></span> for <code class="literal">unalternates</code>
-is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries</em></span> on <code class="literal">alternates</code> will be removed.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="lists"></a>12. Mailing lists</h2></div></div></div><a id="subscribe"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">lists</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unlists</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><div class="cmdsynopsis"><p><code class="command">subscribe</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unsubscribe</code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div><p>
-Mutt has a few nice features for <a class="link" href="#using-lists" title="8. Handling Mailing Lists">handling mailing lists</a>. 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 <a class="link" href="#list-reply"><code class="literal"><list-reply></code></a> 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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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
-<a class="link" href="#followup-to" title="3.60. followup_to">$followup_to</a>
-configuration variable.
-</p></div><p>
-More precisely, Mutt 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 “<span class="quote">lists</span>”
-command. To mark it as subscribed, use “<span class="quote">subscribe</span>”.
-</p><p>
-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
-“<span class="quote">subscribe [0-9]*@bugs.guug.de</span>”. Often, it's sufficient to just
-give a portion of the list's e-mail address.
-</p><p>
-Specify as much of the address as you need to to remove ambiguity. For
-example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed to <span class="emphasis"><em>mutt-users@mutt.org</em></span>. So, to tell Mutt
-that this is a mailing list, you could add “<span class="quote">lists mutt-users@</span>” to your
-initialization file. To tell mutt that you are subscribed to it,
-add “<span class="quote">subscribe mutt-users</span>” to your initialization file instead.
-If you also happen to get mail from someone whose address is
-<span class="emphasis"><em>mutt-users@example.com</em></span>, you could use
-“<span class="quote">lists ^mutt-users@mutt\\.org$</span>”
-or “<span class="quote">subscribe ^mutt-users@mutt\\.org$</span>” to
-match only mail from the actual list.
-</p><p>
-The <code class="literal">-group</code> flag adds all of the subsequent regular expressions
-to the named group.
-</p><p>
-The “<span class="quote">unlists</span>” command is used to remove a token from the list of
-known and subscribed mailing-lists. Use “<span class="quote">unlists *</span>” to remove all
-tokens.
-</p><p>
-To remove a mailing list from the list of subscribed mailing lists,
-but keep it on the list of known mailing lists, use “<span class="quote">unsubscribe</span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mbox-hook"></a>13. Using Multiple spool mailboxes</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mbox-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to move read messages from a specified mailbox to a
-different mailbox automatically when you quit or change folders.
-<span class="emphasis"><em>pattern</em></span> is a regular expression specifying the mailbox to treat as a
-“<span class="quote">spool</span>” mailbox and <span class="emphasis"><em>mailbox</em></span> specifies where mail should be saved when
-read.
-</p><p>
-Unlike some of the other <span class="emphasis"><em>hook</em></span> commands, only the <span class="emphasis"><em>first</em></span> matching
-pattern is used (it is not possible to save read mail in more than a single
-mailbox).
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailboxes"></a>14. Monitoring incoming mail</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">mailboxes</code>
-<em class="replaceable"><code>mailbox</code></em>
- [
-<em class="replaceable"><code>mailbox</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unmailboxes</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mailbox</code></em>
-... }</p></div><p>
-This command specifies folders which can receive mail and
-which will be checked for new messages periodically.
-</p><p>
-<span class="emphasis"><em>folder</em></span> can either be a local file or directory
-(Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP
-support, <span class="emphasis"><em>folder</em></span> can also be a POP/IMAP folder
-URL. The URL syntax is described in <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>,
-POP and IMAP are described in <a class="xref" href="#pop" title="3. POP3 Support">Section 3, “POP3 Support”</a> and <a class="xref" href="#imap" title="4. IMAP Support">Section 4, “IMAP Support”</a>
-respectively.
-</p><p>
-Mutt provides a number of advanced features for handling (possibly many)
-folders and new mail within them, please refer to
-<a class="xref" href="#handling-folders" title="9. Handling multiple folders">Section 9, “Handling multiple folders”</a> for details (including in what
-situations and how often Mutt checks for new mail).
-</p><p>
-The “<span class="quote">unmailboxes</span>” command is used to remove a token from the list
-of folders which receive mail. Use “<span class="quote">unmailboxes *</span>” to remove all
-tokens.
-</p><div class="note"><h3 class="title">Note</h3><p>
-The folders in the <code class="literal">mailboxes</code> command are resolved when
-the command is executed, so if these names contain <a class="link" href="#shortcuts" title="7. Mailbox Shortcuts">shortcut characters</a> (such as “<span class="quote">=</span>” and “<span class="quote">!</span>”), any variable
-definition that affects these characters (like <a class="link" href="#folder" title="3.58. folder">$folder</a> and <a class="link" href="#spoolfile" title="3.276. spoolfile">$spoolfile</a>)
-should be set before the <code class="literal">mailboxes</code> command. If
-none of these shorcuts are used, a local path should be absolute as
-otherwise mutt tries to find it relative to the directory
-from where mutt was started which may not always be desired.
-</p></div><p>
-For Mbox and Mmdf folders, new mail is detected by comparing access and/or
-modification times of files: Mutt assumes a folder has new mail if it wasn't
-accessed after it was last modified. Utilities like <code class="literal">biff</code> or
-<code class="literal">frm</code> or any other program which accesses the mailbox might cause
-Mutt to never detect new mail for that mailbox if they do not properly reset the
-access time. Other possible causes of Mutt not detecting new mail in these folders
-are backup tools (updating access times) or filesystems mounted without
-access time update support.
-</p><p>
-In cases where new mail detection for Mbox or Mmdf folders appears to be
-unreliable, the
-<a class="link" href="#check-mbox-size" title="3.24. check_mbox_size">$check_mbox_size</a>
-option can be used to make Mutt track and consult file sizes for new
-mail detection instead.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="my-hdr"></a>15. User defined headers</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">my_hdr</code>
-<em class="replaceable"><code>string</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unmy_hdr</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>field</code></em>
-... }</p></div><p>
-The <code class="literal">my_hdr</code> command allows you to create your own header
-fields which will be added to every message you send.
-</p><p>
-For example, if you would like to add an “<span class="quote">Organization:</span>” header field to
-all of your outgoing messages, you can put the command
-</p><div class="example"><a id="ex-my-hdr"></a><p class="title"><b>Example 3.10. Defining custom headers</b></p><div class="example-contents"><pre class="screen">
-my_hdr Organization: A Really Big Company, Anytown, USA
-</pre></div></div><br class="example-break" /><p>
-in your <code class="literal">.muttrc</code>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Space characters are <span class="emphasis"><em>not</em></span> allowed between the keyword and
-the colon (“<span class="quote">:</span>”). The standard for electronic mail (RFC2822) says that
-space is illegal there, so Mutt enforces the rule.
-</p></div><p>
-If you would like to add a header field to a single message, you should
-either set the <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a> variable,
-or use the <code class="literal"><edit-headers></code> function (default: “<span class="quote">E</span>”) in the compose menu so
-that you can edit the header of your message along with the body.
-</p><p>
-To remove user defined header fields, use the <code class="literal">unmy_hdr</code>
-command. You may specify an asterisk (“<span class="quote">*</span>”) to remove all header
-fields, or the fields to remove. For example, to remove all “<span class="quote">To</span>” and
-“<span class="quote">Cc</span>” header fields, you could use:
-</p><pre class="screen">
-unmy_hdr to cc
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="save-hook"></a>16. Specify default save mailbox</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">save-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to override the default mailbox used when saving
-messages. <span class="emphasis"><em>mailbox</em></span> will be used as the default if the message
-matches <span class="emphasis"><em>pattern</em></span>, see <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information
-on the exact format.
-</p><p>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to
-<span class="emphasis"><em>mailbox</em></span> after it was expanded.
-</p><p>
-Examples:
-</p><div class="example"><a id="ex-save-hook-exando"></a><p class="title"><b>Example 3.11. Using %-expandos in <code class="literal">save-hook</code></b></p><div class="example-contents"><pre class="screen">
-# default: save all to ~/Mail/<author name>
-save-hook . ~/Mail/%F
-
-# save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
-save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
-# save from aol.com to $folder/spam
-save-hook aol\\.com$ +spam
-</pre></div></div><br class="example-break" /><p>
-Also see the <a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-hook"></a>17. Specify default Fcc: mailbox when composing</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is used to save outgoing mail in a mailbox other than
-<a class="link" href="#record" title="3.239. record">$record</a>. Mutt searches the initial list of
-message recipients for the first matching <span class="emphasis"><em>regexp</em></span> and uses <span class="emphasis"><em>mailbox</em></span>
-as the default Fcc: mailbox. If no match is found the message will be saved
-to <a class="link" href="#record" title="3.239. record">$record</a> mailbox.
-</p><p>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to
-<span class="emphasis"><em>mailbox</em></span> after it was expanded.
-</p><p>
-See <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for information on the exact format of <span class="emphasis"><em>pattern</em></span>.
-</p><p>
-Example: <code class="literal">fcc-hook [@.]aol\\.com$ +spammers</code>
-</p><p>
-The above will save a copy of all messages going to the aol.com domain to
-the `+spammers' mailbox by default. Also see the <a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="fcc-save-hook"></a>18. Specify default save filename and default Fcc: mailbox at once</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">fcc-save-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div><p>
-This command is a shortcut, equivalent to doing both a <a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
-and a <a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a> with its arguments,
-including %-expansion on <span class="emphasis"><em>mailbox</em></span> according
-to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="send-hook"></a>19. Change settings based upon message recipients</h2></div></div></div><a id="reply-hook"></a><a id="send2-hook"></a><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">reply-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">send-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">send2-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-These commands can be used to execute arbitrary configuration commands based
-upon recipients of the message. <span class="emphasis"><em>pattern</em></span> is used to match
-the message, see <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for details. <span class="emphasis"><em>command</em></span>
-is executed when <span class="emphasis"><em>pattern</em></span> matches.
-</p><p>
-<code class="literal">reply-hook</code> is matched against the message you are <span class="emphasis"><em>replying to</em></span>,
-instead of the message you are <span class="emphasis"><em>sending</em></span>. <code class="literal">send-hook</code> is
-matched against all messages, both <span class="emphasis"><em>new</em></span>
-and <span class="emphasis"><em>replies</em></span>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-<code class="literal">reply-hook</code>s are matched <span class="bold"><strong>before</strong></span> the <code class="literal">send-hook</code>, <span class="bold"><strong>regardless</strong></span>
-of the order specified in the user's configuration file.
-</p></div><p>
-<code class="literal">send2-hook</code> is matched every time a message is changed, either
-by editing it, or by using the compose menu to change its recipients
-or subject. <code class="literal">send2-hook</code> is executed after <code class="literal">send-hook</code>, and
-can, e.g., be used to set parameters such as the <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a> variable depending on the message's sender
-address.
-</p><p>
-For each type of <code class="literal">send-hook</code> or <code class="literal">reply-hook</code>, when multiple matches
-occur, commands are executed in the order they are specified in the muttrc
-(for that type of hook).
-</p><p>
-Example: <code class="literal">send-hook mutt "set mime_forward signature=''"</code>
-</p><p>
-Another typical use for this command is to change the values of the
-<a class="link" href="#attribution" title="3.16. attribution">$attribution</a>, <a class="link" href="#signature" title="3.262. signature">$signature</a> and <a class="link" href="#locale" title="3.104. locale">$locale</a>
-variables in order to change the language of the attributions and
-signatures based upon the recipients.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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
-<code class="literal">my_hdr</code> 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.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="message-hook"></a>20. Change settings before formatting a message</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">message-hook</code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div><p>
-This command can be used to execute arbitrary configuration commands
-before viewing or formatting a message based upon information about the message.
-<span class="emphasis"><em>command</em></span> is executed if the <span class="emphasis"><em>pattern</em></span> matches the message to be
-displayed. When multiple matches occur, commands are executed in the order
-they are specified in the muttrc.
-</p><p>
-See <a class="xref" href="#pattern-hook" title="4.1. Message Matching in Hooks">Message Matching in Hooks</a> for
-information on the exact format of <span class="emphasis"><em>pattern</em></span>.
-</p><p>
-Example:
-</p><pre class="screen">
-message-hook ~A 'set pager=builtin'
-message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="crypt-hook"></a>21. Choosing the cryptographic key of the recipient</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">crypt-hook</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>keyid</code></em>
- </p></div><p>
-When encrypting messages with PGP/GnuPG 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 would
-normally use. The <code class="literal">crypt-hook</code> 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.
-</p><p>
-The meaning of <span class="emphasis"><em>keyid</em></span> 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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="push"></a>22. Adding key sequences to the keyboard buffer</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">push</code>
-<em class="replaceable"><code>string</code></em>
- </p></div><p>
-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 <a class="link" href="#macro" title="8. Keyboard macros">macro</a> 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:
-</p><div class="example"><a id="ex-folder-hook-push"></a><p class="title"><b>Example 3.12. Embedding <code class="literal">push</code> in <code class="literal">folder-hook</code></b></p><div class="example-contents"><pre class="screen">
-folder-hook . 'push <collapse-all>'
-</pre></div></div><br class="example-break" /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exec"></a>23. Executing functions</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">exec</code>
-<em class="replaceable"><code>function</code></em>
- [
-<em class="replaceable"><code>function</code></em>
-...]</p></div><p>
-This command can be used to execute any function. Functions are
-listed in the <a class="link" href="#functions" title="4. Functions">function reference</a>.
-“<span class="quote">exec function</span>” is equivalent to “<span class="quote">push <function></span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="score-command"></a>24. Message Scoring</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">score</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>value</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">unscore</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div><p>
-The <code class="literal">score</code> commands adds <span class="emphasis"><em>value</em></span> to a message's score if <span class="emphasis"><em>pattern</em></span>
-matches it. <span class="emphasis"><em>pattern</em></span> is a string in the format described in the <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> section (note: For efficiency reasons, patterns
-which scan information not available in the index, such as <code class="literal">˜b</code>,
-<code class="literal">˜B</code> or <code class="literal">˜h</code>, may not be used). <span class="emphasis"><em>value</em></span> is a
-positive or negative integer. A message's final score is the sum total of all
-matching <code class="literal">score</code> entries. However, you may optionally prefix <span class="emphasis"><em>value</em></span> with
-an equal sign (=) to cause evaluation to stop at a particular entry if there is
-a match. Negative final scores are rounded up to 0.
-</p><p>
-The <code class="literal">unscore</code> command removes score entries from the list. You <span class="bold"><strong>must</strong></span>
-specify the same pattern specified in the <code class="literal">score</code> command for it to be
-removed. The pattern “<span class="quote">*</span>” is a special token which means to clear the list
-of all score entries.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="spam"></a>25. Spam detection</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">spam</code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>format</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command">nospam</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
- }</p></div><p>
-Mutt has generalized support for external spam-scoring filters.
-By defining your spam patterns with the <code class="literal">spam</code> and <code class="literal">nospam</code>
-commands, you can <span class="emphasis"><em>limit</em></span>, <span class="emphasis"><em>search</em></span>, and <span class="emphasis"><em>sort</em></span> 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 <code class="literal">%H</code> selector in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable. (Tip: try <code class="literal">%?H?[%H] ?</code>
-to display spam tags only when they are defined for a given message.)
-</p><p>
-Your first step is to define your external filter's spam patterns using
-the <code class="literal">spam</code> command. <span class="emphasis"><em>pattern</em></span> 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 “<span class="quote">spam tag</span>” or
-“<span class="quote">spam attribute</span>” (unless it also matches a <code class="literal">nospam</code> pattern -- see
-below.) The appearance of this attribute is entirely up to you, and is
-governed by the <span class="emphasis"><em>format</em></span> parameter. <span class="emphasis"><em>format</em></span> can be any static
-text, but it also can include back-references from the <span class="emphasis"><em>pattern</em></span>
-expression. (A regular expression “<span class="quote">back-reference</span>” refers to a
-sub-expression contained within parentheses.) <code class="literal">%1</code> is replaced with
-the first back-reference in the regex, <code class="literal">%2</code> with the second, etc.
-</p><p>
-If you're using multiple spam filters, a message can have more than
-one spam-related header. You can define <code class="literal">spam</code> 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 <span class="emphasis"><em>format</em></span> strings joined
-together, with the value of $spam_separator separating
-them.
-</p><p>
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-define these spam settings:
-</p><div class="example"><a id="ex-spam"></a><p class="title"><b>Example 3.13. Configuring spam detection</b></p><div class="example-contents"><pre class="screen">
-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=", "
-</pre></div></div><br class="example-break" /><p>
-If I then received a message that DCC registered with “<span class="quote">many</span>” hits
-under the “<span class="quote">Fuz2</span>” checksum, and that PureMessage registered with a
-97% probability of being spam, that message's spam tag would read
-<code class="literal">90+/DCC-Fuz2, 97/PM</code>. (The four characters before “<span class="quote">=many</span>” in a
-DCC report indicate the checksum used -- in this case, “<span class="quote">Fuz2</span>”.)
-</p><p>
-If the $spam_separator variable is unset, then each
-spam pattern match supersedes the previous one. Instead of getting
-joined <span class="emphasis"><em>format</em></span> strings, you'll get only the last one to match.
-</p><p>
-The spam tag is what will be displayed in the index when you use
-<code class="literal">%H</code> in the <code class="literal">$index_format</code> variable. It's also the
-string that the <code class="literal">˜H</code> pattern-matching expression matches against for
-<code class="literal"><search></code> and <code class="literal"><limit></code> functions. And it's what sorting by spam
-attribute will use as a sort key.
-</p><p>
-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.
-</p><p>
-Generally, when you sort by spam tag, mutt will sort <span class="emphasis"><em>lexically</em></span> --
-that is, by ordering strings alphanumerically. 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
-<code class="literal">sort -n</code>.) A message with no spam attributes at all -- that is, one
-that didn't match <span class="emphasis"><em>any</em></span> of your <code class="literal">spam</code> patterns -- is sorted at
-lowest priority. Numbers are sorted next, beginning with 0 and ranging
-upward. Finally, non-numeric strings are sorted, with “<span class="quote">a</span>” taking lower
-priority than “<span class="quote">z</span>”. 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.
-</p><p>
-The <code class="literal">nospam</code> command can be used to write exceptions to <code class="literal">spam</code>
-patterns. If a header pattern matches something in a <code class="literal">spam</code> command,
-but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a <code class="literal">nospam</code> command.
-</p><p>
-If the <span class="emphasis"><em>pattern</em></span> given to <code class="literal">nospam</code> is exactly the same as the
-<span class="emphasis"><em>pattern</em></span> on an existing <code class="literal">spam</code> list entry, the effect will be to
-remove the entry from the spam list, instead of adding an exception.
-Likewise, if the <span class="emphasis"><em>pattern</em></span> for a <code class="literal">spam</code> command matches an entry
-on the <code class="literal">nospam</code> list, that <code class="literal">nospam</code> entry will be removed. If the
-<span class="emphasis"><em>pattern</em></span> for <code class="literal">nospam</code> is “<span class="quote">*</span>”, <span class="emphasis"><em>all entries on both lists</em></span>
-will be removed. This might be the default action if you use <code class="literal">spam</code>
-and <code class="literal">nospam</code> in conjunction with a <code class="literal">folder-hook</code>.
-</p><p>
-You can have as many <code class="literal">spam</code> or <code class="literal">nospam</code> commands as you like.
-You can even do your own primitive spam detection within mutt -- for
-example, if you consider all mail from <code class="literal">MAILER-DAEMON</code> to be spam,
-you can use a <code class="literal">spam</code> command like this:
-</p><pre class="screen">
-spam "^From: .*MAILER-DAEMON" "999"
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="set"></a>26. Setting and Querying Variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-commands"></a>26.1. Commands</h3></div></div></div><p>
-The following commands are available to manipulate and query variables:
-</p><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">set</code> {
-[ <code class="option">no</code> | <code class="option">inv</code> ]
-<em class="replaceable"><code>variable</code></em>
- |
-<em class="replaceable"><code>variable=value</code></em>
- } [...]</p></div><div class="cmdsynopsis"><p><code class="command">toggle</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">unset</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><div class="cmdsynopsis"><p><code class="command">reset</code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div><p>
-This command is used to set (and unset) <a class="link" href="#variables" title="3. Configuration variables">configuration variables</a>. There are four basic types of variables:
-boolean, number, string and quadoption. <span class="emphasis"><em>boolean</em></span> variables can be
-<span class="emphasis"><em>set</em></span> (true) or <span class="emphasis"><em>unset</em></span> (false). <span class="emphasis"><em>number</em></span> variables can be
-assigned a positive integer value.
-<span class="emphasis"><em>string</em></span> variables consist of any number of printable characters and
-must be enclosed in quotes if they contain spaces or tabs. You
-may also use the escape sequences “<span class="quote">\n</span>” and “<span class="quote">\t</span>” for newline and tab, respectively.
-<span class="emphasis"><em>quadoption</em></span> variables are used to control whether or not to be prompted
-for certain actions, or to specify a default action. A value of <span class="emphasis"><em>yes</em></span>
-will cause the action to be carried out automatically as if you had answered
-yes to the question. Similarly, a value of <span class="emphasis"><em>no</em></span> will cause the
-action to be carried out as if you had answered “<span class="quote">no.</span>” A value of
-<span class="emphasis"><em>ask-yes</em></span> will cause a prompt with a default answer of “<span class="quote">yes</span>” and
-<span class="emphasis"><em>ask-no</em></span> will provide a default answer of “<span class="quote">no.</span>”
-</p><p>
-Prefixing a variable with “<span class="quote">no</span>” will unset it. Example: <code class="literal">set noaskbcc</code>.
-</p><p>
-For <span class="emphasis"><em>boolean</em></span> variables, you may optionally prefix the variable name with
-<code class="literal">inv</code> to toggle the value (on or off). This is useful when writing
-macros. Example: <code class="literal">set invsmart_wrap</code>.
-</p><p>
-The <code class="literal">toggle</code> command automatically prepends the <code class="literal">inv</code> prefix to all
-specified variables.
-</p><p>
-The <code class="literal">unset</code> command automatically prepends the <code class="literal">no</code> prefix to all
-specified variables.
-</p><p>
-Using the <code class="literal"><enter-command></code> function in the <span class="emphasis"><em>index</em></span> menu, you can query the
-value of a variable by prefixing the name of the variable with a question
-mark:
-</p><pre class="screen">
-set ?allow_8bit
-</pre><p>
-The question mark is actually only required for boolean and quadoption
-variables.
-</p><p>
-The <code class="literal">reset</code> command resets all given variables to the compile time
-defaults (hopefully mentioned in this manual). If you use the command
-<code class="literal">set</code> and prefix the variable with “<span class="quote">&</span>” this has the same
-behavior as the reset command.
-</p><p>
-With the <code class="literal">reset</code> command there exists the special variable “<span class="quote">all</span>”,
-which allows you to reset all variables to their system defaults.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="set-myvar"></a>26.2. User-defined variables</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-intro"></a>26.2.1. Introduction</h4></div></div></div><p>
-Along with the variables listed in the
-<a class="link" href="#variables" title="3. Configuration variables">Configuration variables</a> section, mutt
-supports user-defined variables with names starting
-with <code class="literal">my_</code> as in, for
-example, <code class="literal">my_cfgdir</code>.
-</p><p>
-The <code class="literal">set</code> command either creates a
-custom <code class="literal">my_</code> variable or changes its
-value if it does exist already. The <code class="literal">unset</code> and <code class="literal">reset</code>
-commands remove the variable entirely.
-</p><p>
-Since user-defined variables are expanded in the same way that
-environment variables are (except for
-the <a class="link" href="#shell-escape">shell-escape</a> command and
-backtick expansion), this feature can be used to make configuration
-files more readable.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="set-myvar-examples"></a>26.2.2. Examples</h4></div></div></div><p>
-The following example defines and uses the variable <code class="literal">my_cfgdir</code>
-to abbreviate the calls of the <a class="link" href="#source" title="27. Reading initialization commands from another file">source</a> command:
-</p><div class="example"><a id="ex-myvar1"></a><p class="title"><b>Example 3.14. Using user-defined variables for config file readability</b></p><div class="example-contents"><pre class="screen">
-set my_cfgdir = $HOME/mutt/config
-
-source $my_cfgdir/hooks
-source $my_cfgdir/macros
-# more source commands...
-</pre></div></div><br class="example-break" /><p>
-A custom variable can also be used in macros to backup the current value
-of another variable. In the following example, the value of the
-<a class="link" href="#delete" title="3.42. delete">$delete</a> is changed temporarily
-while its original value is saved as <code class="literal">my_delete</code>.
-After the macro has executed all commands, the original value of <a class="link" href="#delete" title="3.42. delete">$delete</a> is restored.
-</p><div class="example"><a id="ex-myvar2"></a><p class="title"><b>Example 3.15. Using user-defined variables for backing up other config option values</b></p><div class="example-contents"><pre class="screen">
-macro pager ,x '\
-<enter-command>set my_delete=$delete<enter>\
-<enter-command>set delete=yes<enter>\
-...\
-<enter-command>set delete=$my_delete<enter>'
-</pre></div></div><br class="example-break" /><p>
-Since mutt expands such values already when parsing the configuration
-file(s), the value of <code class="literal">$my_delete</code> in the
-last example would be the value of <code class="literal">$delete</code> exactly
-as it was at that point during parsing the configuration file. If
-another statement would change the value for <code class="literal">$delete</code>
-later in the same or another file, it would have no effect on
-<code class="literal">$my_delete</code>. However, the expansion can
-be deferred to runtime, as shown in the next example, when escaping the
-dollar sign.
-</p><div class="example"><a id="ex-myvar3"></a><p class="title"><b>Example 3.16. Deferring user-defined variable expansion to runtime</b></p><div class="example-contents"><pre class="screen">
-macro pager <PageDown> "\
-<enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
-<next-page>\
-<enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
-<enter-command> unset my_old_pager_stop<Enter>"
-</pre></div></div><br class="example-break" /><p>
-Note that there is a space
-between <code class="literal"><enter-command></code> and
-the <code class="literal">set</code> configuration command, preventing mutt from
-recording the macro's commands into its history.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="source"></a>27. Reading initialization commands from another file</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">source</code>
-<em class="replaceable"><code>filename</code></em>
- </p></div><p>
-This command allows the inclusion of initialization commands
-from other files. For example, I place all of my aliases in
-<code class="literal">˜/.mail_aliases</code> so that I can make my
-<code class="literal">˜/.muttrc</code> readable and keep my aliases private.
-</p><p>
-If the filename begins with a tilde (“<span class="quote">˜</span>”), it will be expanded to the
-path of your home directory.
-</p><p>
-If the filename ends with a vertical bar (|), then <span class="emphasis"><em>filename</em></span> is
-considered to be an executable program from which to read input (eg.
-<code class="literal">source ˜/bin/myscript|</code>).
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ifdef"></a>28. Configuring features conditionnaly</h2></div></div></div><p>
-Usage: <code class="literal">ifdef</code> <span class="emphasis"><em>item</em></span> <span class="emphasis"><em>command</em></span>
-</p><p>
-This command allows to test if a feature has been compiled in, before
-actually executing the command. Item can be either the name of a
-function, variable, or command. Example:
-</p><p>
-</p><pre class="screen">
-ifdef imap_keepalive 'source ~/.mutt/imap_setup'
-</pre><p>
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="unhook"></a>29. Removing hooks</h2></div></div></div><p>Usage:</p><div class="cmdsynopsis"><p><code class="command">unhook</code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>hook-type</code></em>
- }</p></div><p>
-This command permits you to flush hooks you have previously defined.
-You can either remove all hooks by giving the “<span class="quote">*</span>” character as an
-argument, or you can remove all hooks of a specific type by saying
-something like <code class="literal">unhook send-hook</code>.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="formatstrings"></a>30. Format Strings</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-basics"></a>30.1. Basic usage</h3></div></div></div><p>
-Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
-<a class="link" href="#index-format" title="3.101. index_format">$index_format</a>,
-<a class="link" href="#pager-format" title="3.140. pager_format">$pager_format</a>,
-<a class="link" href="#status-format" title="3.278. status_format">$status_format</a>,
-and other “<span class="quote">*_format</span>” variables. These can be very straightforward,
-and it's quite possible you already know how to use them.
-</p><p>
-The most basic format string element is a percent symbol followed
-by another character. For example, <code class="literal">%s</code>
-represents a message's Subject: header in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable. The
-“<span class="quote">expandos</span>” available are documented with each format variable, but
-there are general modifiers available with all formatting expandos,
-too. Those are our concern here.
-</p><p>
-Some of the modifiers are borrowed right out of C (though you might
-know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in <code class="literal">%-12.12s</code>. As with
-such programming languages, these modifiers allow you to specify the
-minimum and maximum size of the resulting string, as well as its
-justification. If the “<span class="quote">-</span>” sign follows the percent, the string will
-be left-justified instead of right-justified. If there's a number
-immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
-will be padded out with spaces. If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
-permitted to exceed that width, no matter its natural size. Each of
-these three elements is optional, so that all these are legal format
-strings:
-<code class="literal">%-12s</code>
-<code class="literal">%4c</code>
-<code class="literal">%.15F</code>
-<code class="literal">%-12.15L</code>
-</p><p>
-Mutt adds some other modifiers to format strings. If you use an equals
-symbol (<code class="literal">=</code>) as a numeric prefix (like the minus
-above), it will force the string to be centered within its minimum
-space range. For example, <code class="literal">%=14y</code> will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-<code class="literal">$index_format</code>. If the expansion
-results in a string less than 14 characters, it will be centered in a
-14-character space. If the X-Label for a message were "test", that
-expansion would look like “<span class="quote"> test </span>”.
-</p><p>
-There are two very little-known modifiers that affect the way that an
-expando is replaced. If there is an underline (“<span class="quote">_</span>”) character
-between any format modifiers (as above) and the expando letter, it will
-expands in all lower case. And if you use a colon (“<span class="quote">:</span>”), it will
-replace all decimal points with underlines.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="formatstrings-filters"></a>30.2. Filters</h3></div></div></div><p>
-Any format string ending in a vertical bar (“<span class="quote">|</span>”) will be
-expanded and piped through the first word in the string, using spaces
-as separator. The string returned will be used for display.
-If the returned string ends in %, it will be passed through
-the formatter a second time. This allows the filter to generate a
-replacement format string including % expandos.
-</p><p>
-All % expandos in a format string are expanded before the script
-is called so that:
-</p><div class="example"><a id="ex-fmtpipe"></a><p class="title"><b>Example 3.17. Using external filters in format strings</b></p><div class="example-contents"><pre class="screen">
-set status_format="script.sh '%r %f (%L)'|"
-</pre></div></div><br class="example-break" /><p>
-will make mutt expand <code class="literal">%r</code>,
-<code class="literal">%f</code> and <code class="literal">%L</code>
-before calling the script. The example also shows that arguments can be
-quoted: the script will receive the expanded string between the single quotes
-as the only argument.
-</p><p>
-A practical example is the <code class="literal">mutt_xtitle</code>
-script installed in the <code class="literal">samples</code>
-subdirectory of the mutt documentation: it can be used as filter for
-<code class="literal">$status_format</code> to set the current
-terminal's title, if supported.
-</p></div></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="advancedusage"></a>Chapter 4. Advanced Usage</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#regexp">1. Regular Expressions</a></span></dt><dt><span class="sect1"><a href="#patterns">2. Patterns: Searching, Limiting and Tagging</a></span></dt><dd><dl><dt><span class="sect2"><a href="#patterns-modifier">2.1. Pattern Modifier</a></span></dt><dt><span class="sect2"><a href="#simple-patterns">2.2. Simple Patterns</a></span></dt><dt><span class="sect2"><a href="#complex-patterns">2.3. Complex Patterns</a></span></dt><dt><span class="sect2"><a href="#date-patterns">2.4. Searching by Date</a></span></dt></dl></dd><dt><span class="sect1"><a href="#tags">3. Using Tags</a></span></dt><dt><span class="sect1"><a href="#hooks">4. Using Hooks</a></span></dt><dd><dl><dt><span class="sect2"><a href="#pattern-hook">4.1. Message Matching in Hooks</a></span></dt></dl></dd><dt><span class="sect1"><a href="#query">5. External Address Queries</a></span></dt><dt><span class="sect1"><a href="#mailbox-formats">6. Mailbox Formats</a></span></dt><dt><span class="sect1"><a href="#shortcuts">7. Mailbox Shortcuts</a></span></dt><dt><span class="sect1"><a href="#using-lists">8. Handling Mailing Lists</a></span></dt><dt><span class="sect1"><a href="#handling-folders">9. Handling multiple folders</a></span></dt><dt><span class="sect1"><a href="#editing-threads">10. Editing threads</a></span></dt><dd><dl><dt><span class="sect2"><a href="#link-threads">10.1. Linking threads</a></span></dt><dt><span class="sect2"><a href="#break-threads">10.2. Breaking threads</a></span></dt></dl></dd><dt><span class="sect1"><a href="#dsn">11. Delivery Status Notification (DSN) Support</a></span></dt><dt><span class="sect1"><a href="#urlview">12. Start a WWW Browser on URLs</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="regexp"></a>1. Regular Expressions</h2></div></div></div><p>
-All string patterns in Mutt including those in more complex
-<a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> must be specified
-using regular expressions (regexp) in the “<span class="quote">POSIX extended</span>” 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.
-</p><p>
-The search is case sensitive if the pattern contains at least one upper
-case letter, and case insensitive otherwise.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that “<span class="quote">\</span>”
-must be quoted if used for a regular expression in an initialization
-command: “<span class="quote">\\</span>”.
-</p></div><p>
-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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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 <a class="xref" href="#muttrc-syntax" title="2. Syntax of Initialization Files">Syntax of Initialization Files</a>
-for more information on " and ' delimiter processing. To match a
-literal " or ' you must preface it with \ (backslash).
-</p></div><p>
-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.
-</p><p>
-The period “<span class="quote">.</span>” matches any single character. The caret “<span class="quote">^</span>” and
-the dollar sign “<span class="quote">$</span>” are metacharacters that respectively match
-the empty string at the beginning and end of a line.
-</p><p>
-A list of characters enclosed by “<span class="quote">[</span>” and “<span class="quote">]</span>” matches any
-single character in that list; if the first character of the list
-is a caret “<span class="quote">^</span>” then it matches any character <span class="bold"><strong>not</strong></span> in the
-list. For example, the regular expression <span class="bold"><strong>[0123456789]</strong></span>
-matches any single digit. A range of ASCII characters may be specified
-by giving the first and last characters, separated by a hyphen
-“<span class="quote">-</span>”. Most metacharacters lose their special meaning inside
-lists. To include a literal “<span class="quote">]</span>” place it first in the list.
-Similarly, to include a literal “<span class="quote">^</span>” place it anywhere but first.
-Finally, to include a literal hyphen “<span class="quote">-</span>” place it last.
-</p><p>
-Certain named classes of characters are predefined. Character classes
-consist of “<span class="quote">[:</span>”, a keyword denoting the class, and “<span class="quote">:]</span>”.
-The following classes are defined by the POSIX standard in
-<a class="xref" href="#posix-regex-char-classes" title="Table 4.1. POSIX regular expression character classes">Table 4.1, “POSIX regular expression character classes”</a>
-</p><div class="table"><a id="posix-regex-char-classes"></a><p class="title"><b>Table 4.1. POSIX regular expression character classes</b></p><div class="table-contents"><table summary="POSIX regular expression character classes" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Character class</th><th>Description</th></tr></thead><tbody><tr><td>[:alnum:]</td><td>Alphanumeric characters</td></tr><tr><td>[:alpha:]</td><td>Alphabetic characters</td></tr><tr><td>[:blank:]</td><td>Space or tab characters</td></tr><tr><td>[:cntrl:]</td><td>Control characters</td></tr><tr><td>[:digit:]</td><td>Numeric characters</td></tr><tr><td>[:graph:]</td><td>Characters that are both printable and visible. (A space is printable, but not visible, while an “<span class="quote">a</span>” is both)</td></tr><tr><td>[:lower:]</td><td>Lower-case alphabetic characters</td></tr><tr><td>[:print:]</td><td>Printable characters (characters that are not control characters)</td></tr><tr><td>[:punct:]</td><td>Punctuation characters (characters that are not letter, digits, control characters, or space characters)</td></tr><tr><td>[:space:]</td><td>Space characters (such as space, tab and formfeed, to name a few)</td></tr><tr><td>[:upper:]</td><td>Upper-case alphabetic characters</td></tr><tr><td>[:xdigit:]</td><td>Characters that are hexadecimal digits</td></tr></tbody></table></div></div><br class="table-break" /><p>
-A character class is only valid in a regular expression inside the
-brackets of a character list.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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, <span class="bold"><strong>[[:digit:]]</strong></span> is equivalent to
-<span class="bold"><strong>[0-9]</strong></span>.
-</p></div><p>
-Two additional special sequences can appear in character lists. These
-apply to non-ASCII character sets, which can have single symbols (called
-collating elements) that are represented with more than one character,
-as well as several characters that are equivalent for collating or
-sorting purposes:
-</p><div class="variablelist"><dl><dt><span class="term">Collating Symbols</span></dt><dd><p>
-A collating symbol is a multi-character collating element enclosed in
-“<span class="quote">[.</span>” and “<span class="quote">.]</span>”. For example, if “<span class="quote">ch</span>” is a collating
-element, then <span class="bold"><strong>[[.ch.]]</strong></span> is a regexp that matches
-this collating element, while <span class="bold"><strong>[ch]</strong></span> is a regexp that
-matches either “<span class="quote">c</span>” or “<span class="quote">h</span>”.
-</p></dd><dt><span class="term">Equivalence Classes</span></dt><dd><p>
-An equivalence class is a locale-specific name for a list of
-characters that are equivalent. The name is enclosed in “<span class="quote">[=</span>”
-and “<span class="quote">=]</span>”. For example, the name “<span class="quote">e</span>” might be used to
-represent all of “<span class="quote">è</span>” “<span class="quote">é</span>” and “<span class="quote">e</span>”. In this case,
-<span class="bold"><strong>[[=e=]]</strong></span> is a regexp that matches any of
-“<span class="quote">è</span>”, “<span class="quote">é</span>” and “<span class="quote">e</span>”.
-</p></dd></dl></div><p>
-A regular expression matching a single character may be followed by one
-of several repetition operators described in <a class="xref" href="#regex-repeat" title="Table 4.2. Regular expression repetition operators">Table 4.2, “Regular expression repetition operators”</a>.
-</p><div class="table"><a id="regex-repeat"></a><p class="title"><b>Table 4.2. Regular expression repetition operators</b></p><div class="table-contents"><table summary="Regular expression repetition operators" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Operator</th><th>Description</th></tr></thead><tbody><tr><td>?</td><td>The preceding item is optional and matched at most once</td></tr><tr><td>*</td><td>The preceding item will be matched zero or more times</td></tr><tr><td>+</td><td>The preceding item will be matched one or more times</td></tr><tr><td>{n}</td><td>The preceding item is matched exactly <span class="emphasis"><em>n</em></span> times</td></tr><tr><td>{n,}</td><td>The preceding item is matched <span class="emphasis"><em>n</em></span> or more times</td></tr><tr><td>{,m}</td><td>The preceding item is matched at most <span class="emphasis"><em>m</em></span> times</td></tr><tr><td>{n,m}</td><td>The preceding item is matched at least <span class="emphasis"><em>n</em></span> times, but no more than <span class="emphasis"><em>m</em></span> times</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Two regular expressions may be concatenated; the resulting regular
-expression matches any string formed by concatenating two substrings
-that respectively match the concatenated subexpressions.
-</p><p>
-Two regular expressions may be joined by the infix operator “<span class="quote">|</span>”;
-the resulting regular expression matches any string matching either
-subexpression.
-</p><p>
-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.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you compile Mutt with the GNU <span class="emphasis"><em>rx</em></span> package, the
-following operators may also be used in regular expressions as described in <a class="xref" href="#regex-gnu-ext" title="Table 4.3. GNU regular expression extensions">Table 4.3, “GNU regular expression extensions”</a>.
-</p></div><div class="table"><a id="regex-gnu-ext"></a><p class="title"><b>Table 4.3. GNU regular expression extensions</b></p><div class="table-contents"><table summary="GNU regular expression extensions" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Expression</th><th>Description</th></tr></thead><tbody><tr><td>\\y</td><td>Matches the empty string at either the beginning or the end of a word</td></tr><tr><td>\\B</td><td>Matches the empty string within a word</td></tr><tr><td>\\<</td><td>Matches the empty string at the beginning of a word</td></tr><tr><td>\\></td><td>Matches the empty string at the end of a word</td></tr><tr><td>\\w</td><td>Matches any word-constituent character (letter, digit, or underscore)</td></tr><tr><td>\\W</td><td>Matches any character that is not word-constituent</td></tr><tr><td>\\`</td><td>Matches the empty string at the beginning of a buffer (string)</td></tr><tr><td>\\'</td><td>Matches the empty string at the end of a buffer</td></tr></tbody></table></div></div><br class="table-break" /><p>
-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.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="patterns"></a>2. Patterns: Searching, Limiting and Tagging</h2></div></div></div><p>
-Many of Mutt's commands allow you to specify a pattern to match
-(<code class="literal">limit</code>, <code class="literal">tag-pattern</code>,
-<code class="literal">delete-pattern</code>, etc.). <a class="xref" href="#tab-patterns" title="Table 4.4. Pattern modifiers">Table 4.4, “Pattern modifiers”</a>
-shows several ways to select messages.
-</p><div class="table"><a id="tab-patterns"></a><p class="title"><b>Table 4.4. Pattern modifiers</b></p><div class="table-contents"><table summary="Pattern modifiers" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Pattern modifier</th><th>Description</th></tr></thead><tbody><tr><td>~A</td><td>all messages</td></tr><tr><td>~b <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message body</td></tr><tr><td>=b <span class="emphasis"><em>STRING</em></span></td><td>messages which contain <span class="emphasis"><em>STRING</em></span> in the message body. If IMAP is enabled, searches for <span class="emphasis"><em>STRING</em></span> on the server, rather than downloading each message and searching it locally.</td></tr><tr><td>~B <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the whole message</td></tr><tr><td>~c <span class="emphasis"><em>EXPR</em></span></td><td>messages carbon-copied to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%c <span class="emphasis"><em>GROUP</em></span></td><td>messages carbon-copied to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~C <span class="emphasis"><em>EXPR</em></span></td><td>messages either to: or cc: <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%C <span class="emphasis"><em>GROUP</em></span></td><td>messages either to: or cc: to any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~d [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-sent</span>” in a Date range</td></tr><tr><td>~D</td><td>deleted messages</td></tr><tr><td>~e <span class="emphasis"><em>EXPR</em></span></td><td>messages which contains <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>%e <span class="emphasis"><em>GROUP</em></span></td><td>messages which contain a member of <span class="emphasis"><em>GROUP</em></span> in the “<span class="quote">Sender</span>” field</td></tr><tr><td>~E</td><td>expired messages</td></tr><tr><td>~F</td><td>flagged messages</td></tr><tr><td>~f <span class="emphasis"><em>EXPR</em></span></td><td>messages originating from <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%f <span class="emphasis"><em>GROUP</em></span></td><td>messages originating from any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~g</td><td>cryptographically signed messages</td></tr><tr><td>~G</td><td>cryptographically encrypted messages</td></tr><tr><td>~h <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the message header</td></tr><tr><td>~H <span class="emphasis"><em>EXPR</em></span></td><td>messages with a spam attribute matching <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~i <span class="emphasis"><em>EXPR</em></span></td><td>messages which match <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Message-ID</span>” field</td></tr><tr><td>~k</td><td>messages which contain PGP key material</td></tr><tr><td>~L <span class="emphasis"><em>EXPR</em></span></td><td>messages either originated or received by <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>%L <span class="emphasis"><em>GROUP</em></span></td><td>message either originated or received by any member of <span class="emphasis"><em>GROUP</em></span></td></tr><tr><td>~l</td><td>messages addressed to a known mailing list</td></tr><tr><td>~m [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~n [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a score in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~N</td><td>new messages</td></tr><tr><td>~O</td><td>old messages</td></tr><tr><td>~p</td><td>messages addressed to you (consults alternates)</td></tr><tr><td>~P</td><td>messages from you (consults alternates)</td></tr><tr><td>~Q</td><td>messages which have been replied to</td></tr><tr><td>~r [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with “<span class="quote">date-received</span>” in a Date range</td></tr><tr><td>~R</td><td>read messages</td></tr><tr><td>~s <span class="emphasis"><em>EXPR</em></span></td><td>messages having <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">Subject</span>” field.</td></tr><tr><td>~S</td><td>superseded messages</td></tr><tr><td>~t <span class="emphasis"><em>EXPR</em></span></td><td>messages addressed to <span class="emphasis"><em>EXPR</em></span></td></tr><tr><td>~T</td><td>tagged messages</td></tr><tr><td>~u</td><td>messages addressed to a subscribed mailing list</td></tr><tr><td>~U</td><td>unread messages</td></tr><tr><td>~v</td><td>messages part of a collapsed thread.</td></tr><tr><td>~V</td><td>cryptographically verified messages</td></tr><tr><td>~x <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">References</span>” field</td></tr><tr><td>~X [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> attachments *)</td></tr><tr><td>~y <span class="emphasis"><em>EXPR</em></span></td><td>messages which contain <span class="emphasis"><em>EXPR</em></span> in the “<span class="quote">X-Label</span>” field</td></tr><tr><td>~z [<span class="emphasis"><em>MIN</em></span>]-[<span class="emphasis"><em>MAX</em></span>]</td><td>messages with a size in the range <span class="emphasis"><em>MIN</em></span> to <span class="emphasis"><em>MAX</em></span> *)</td></tr><tr><td>~=</td><td>duplicated messages (see <a class="link" href="#duplicate-threads" title="3.49. duplicate_threads">$duplicate_threads</a>)</td></tr><tr><td>~$</td><td>unreferenced messages (requires threaded view)</td></tr><tr><td>~(<span class="emphasis"><em>PATTERN</em></span>)</td><td>messages in threads
-containing messages matching <span class="emphasis"><em>PATTERN</em></span>, e.g. all
-threads containing messages from you: ~(~P)</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Where <span class="emphasis"><em>EXPR</em></span> is a
-<a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a>. Special attention has to be
-made when using regular expressions inside of patterns. Specifically,
-Mutt's parser for these patterns will strip one level of backslash (“<span class="quote">\</span>”),
-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 (“<span class="quote">\\</span>”). You can force mutt to treat <span class="emphasis"><em>EXPR</em></span> as a simple string
-instead of a regular expression by using = instead of ˜ in the
-pattern name. For example, <code class="literal">=b *.*</code> will find all messages that contain
-the literal string “<span class="quote">*.*</span>”. Simple string matches are less powerful than
-regular expressions but can be considerably faster. This is especially
-true for IMAP folders, because string matches can be performed on the
-server instead of by fetching every message. IMAP treats <code class="literal">=h</code> specially:
-it must be of the form "header: substring" and will not partially
-match header names. The substring part may be omitted if you simply
-wish to find messages containing a particular header without regard to
-its value.
-</p><p>
-*) The forms “<span class="quote"><[<span class="emphasis"><em>MAX</em></span>]</span>”, “<span class="quote">>[<span class="emphasis"><em>MIN</em></span>]</span>”,
-“<span class="quote">[<span class="emphasis"><em>MIN</em></span>]-</span>” and “<span class="quote">-[<span class="emphasis"><em>MAX</em></span>]</span>”
-are allowed, too.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="patterns-modifier"></a>2.1. Pattern Modifier</h3></div></div></div><div class="note"><h3 class="title">Note</h3><p>
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
-match if there is at least one match in the whole list. If you want to
-make sure that all elements of that list match, you need to prefix your
-pattern with “<span class="quote">^</span>”.
-This example matches all mails which only has recipients from Germany.
-</p></div><pre class="screen">
-^~C \.de$
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-patterns"></a>2.2. Simple Patterns</h3></div></div></div><p>
-Mutt supports two versions of so called “<span class="quote">simple searches</span>” which are
-issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
-one of these characters: “<span class="quote">˜</span>”, “<span class="quote">=</span>” or “<span class="quote">%</span>”). If the query is
-supposed to contain one of these special characters, they must be escaped
-by prepending a backslash (“<span class="quote">\</span>”).
-</p><p>
-The first type is by checking whether the query string equals
-a keyword case-insensitively from <a class="xref" href="#tab-simplesearch-keywords" title="Table 4.5. Simple search keywords">Table 4.5, “Simple search keywords”</a>:
-If that is the case, Mutt will use the shown pattern modifier instead.
-If a keyword would conflict with your search keyword, you need to turn
-it into a regular expression to avoid matching the keyword table. For
-example, if you want to find all messages matching “<span class="quote">flag</span>”
-(using <a class="link" href="#simple-search" title="3.263. simple_search">$simple_search</a>)
-but don't want to match flagged messages, simply search for
-“<span class="quote"><code class="literal">[f]lag</code></span>”.
-</p><div class="table"><a id="tab-simplesearch-keywords"></a><p class="title"><b>Table 4.5. Simple search keywords</b></p><div class="table-contents"><table summary="Simple search keywords" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Keyword</th><th>Pattern modifier</th></tr></thead><tbody><tr><td>all</td><td>~A</td></tr><tr><td>.</td><td>~A</td></tr><tr><td>^</td><td>~A</td></tr><tr><td>del</td><td>~D</td></tr><tr><td>flag</td><td>~F</td></tr><tr><td>new</td><td>~N</td></tr><tr><td>old</td><td>~O</td></tr><tr><td>repl</td><td>~Q</td></tr><tr><td>read</td><td>~R</td></tr><tr><td>tag</td><td>~T</td></tr><tr><td>unread</td><td>~U</td></tr></tbody></table></div></div><br class="table-break" /><p>
-The second type of simple search is to build a complex search
-pattern using <a class="link" href="#simple-search" title="3.263. simple_search">$simple_search</a>
-as a template. Mutt will insert your query properly quoted and search
-for the composed complex query.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="complex-patterns"></a>2.3. Complex Patterns</h3></div></div></div><p>
-Logical AND is performed by specifying more than one criterion. For
-example:
-</p><pre class="screen">
-~t mutt ~f elkins
-</pre><p>
-would select messages which contain the word “<span class="quote">mutt</span>” in the list of
-recipients <span class="bold"><strong>and</strong></span> that have the word “<span class="quote">elkins</span>” in the “<span class="quote">From</span>” header
-field.
-</p><p>
-Mutt also recognizes the following operators to create more complex search
-patterns:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-! -- logical NOT operator
-</p></li><li><p>
-| -- logical OR operator
-</p></li><li><p>
-() -- logical grouping operator
-</p></li></ul></div><p>
-Here is an example illustrating a complex search pattern. This pattern will
-select all messages which do not contain “<span class="quote">mutt</span>” in the “<span class="quote">To</span>” or “<span class="quote">Cc</span>”
-field and which are from “<span class="quote">elkins</span>”.
-</p><div class="example"><a id="ex-pattern-bool"></a><p class="title"><b>Example 4.1. Using boolean operators in patterns</b></p><div class="example-contents"><pre class="screen">
-!(~t mutt|~c mutt) ~f elkins
-</pre></div></div><br class="example-break" /><p>
-Here is an example using white space in the regular expression (note
-the ' and " delimiters). For this to match, the mail's subject must
-match the “<span class="quote">^Junk +From +Me$</span>” and it must be from either “<span class="quote">Jim +Somebody</span>”
-or “<span class="quote">Ed +SomeoneElse</span>”:
-</p><pre class="screen">
- '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
-</pre><div class="note"><h3 class="title">Note</h3><p>
-If a regular expression contains parenthesis, or a vertical bar
-("|"), you <span class="bold"><strong>must</strong></span> enclose the expression in double or single quotes since
-those characters are also used to separate different parts of Mutt's
-pattern language. For example: <code class="literal">~f "me@(mutt\.org|cs\.hmc\.edu)"</code>
-</p></div><p>
-Without the quotes, the parenthesis wouldn't end.
-This would be separated to two OR'd patterns: <span class="emphasis"><em>˜f me@(mutt\.org</em></span>
-and <span class="emphasis"><em>cs\.hmc\.edu)</em></span>. They are never what you want.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-patterns"></a>2.4. Searching by Date</h3></div></div></div><p>
-Mutt supports two types of dates, <span class="emphasis"><em>absolute</em></span> and <span class="emphasis"><em>relative</em></span>.
-</p><p>
-<span class="bold"><strong>Absolute</strong></span>. Dates <span class="bold"><strong>must</strong></span> be in DD/MM/YY format (month and year are
-optional, defaulting to the current month and year). An example of a valid
-range of dates is:
-</p><pre class="screen">
-Limit to messages matching: ~d 20/1/95-31/10
-</pre><p>
-If you omit the minimum (first) date, and just specify “<span class="quote">-DD/MM/YY</span>”, all
-messages <span class="emphasis"><em>before</em></span> the given date will be selected. If you omit the maximum
-(second) date, and specify “<span class="quote">DD/MM/YY-</span>”, all messages <span class="emphasis"><em>after</em></span> the given
-date will be selected. If you specify a single date with no dash (“<span class="quote">-</span>”),
-only messages sent on the given date will be selected.
-</p><p>
-<span class="bold"><strong>Error Margins</strong></span>. You can add error margins to absolute dates.
-An error margin is a sign (+ or -), followed by a digit, followed by
-one of the units in <a class="xref" href="#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>. As a special case, you can replace the
-sign by a “<span class="quote">*</span>” character, which is equivalent to giving identical plus and minus error margins.
-</p><div class="table"><a id="tab-date-units"></a><p class="title"><b>Table 4.6. Date units</b></p><div class="table-contents"><table summary="Date units" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Unit</th><th>Description</th></tr></thead><tbody><tr><td>y</td><td>Years</td></tr><tr><td>m</td><td>Months</td></tr><tr><td>w</td><td>Weeks</td></tr><tr><td>d</td><td>Days</td></tr></tbody></table></div></div><br class="table-break" /><p>
-Example: To select any messages two weeks around January 15, 2001,
-you'd use the following pattern:
-</p><pre class="screen">
-Limit to messages matching: ~d 15/1/2001*2w
-</pre><p>
-<span class="bold"><strong>Relative</strong></span>. This type of date is relative to the current date, and may
-be specified as:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-><span class="emphasis"><em>offset</em></span> (messages older than <span class="emphasis"><em>offset</em></span> units)
-</p></li><li><p>
-<<span class="emphasis"><em>offset</em></span> (messages newer than <span class="emphasis"><em>offset</em></span> units)
-</p></li><li><p>
-=<span class="emphasis"><em>offset</em></span> (messages exactly <span class="emphasis"><em>offset</em></span> units old)
-</p></li></ul></div><p>
-<span class="emphasis"><em>offset</em></span> is specified as a positive number with one of the units from <a class="xref" href="#tab-date-units" title="Table 4.6. Date units">Table 4.6, “Date units”</a>.
-</p><p>
-Example: to select messages less than 1 month old, you would use
-</p><pre class="screen">
-Limit to messages matching: ~d <1m
-</pre><div class="note"><h3 class="title">Note</h3><p>
-All dates used when searching are relative to the
-<span class="bold"><strong>local</strong></span> time zone, so unless you change the setting of your <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> to include a
-<code class="literal">%[...]</code> format, these are <span class="bold"><strong>not</strong></span> the dates shown
-in the main index.
-</p></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tags"></a>3. Using Tags</h2></div></div></div><p>
-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 <code class="literal"><tag-pattern></code> function, which is bound to
-“<span class="quote">shift-T</span>” by default. Or you can select individual messages by
-hand using the <code class="literal"><tag-message></code> function, which is bound to “<span class="quote">t</span>” by
-default. See <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a> for Mutt's pattern
-matching syntax.
-</p><p>
-Once you have tagged the desired messages, you can use the
-“<span class="quote">tag-prefix</span>” operator, which is the “<span class="quote">;</span>” (semicolon) key by default.
-When the “<span class="quote">tag-prefix</span>” operator is used, the <span class="bold"><strong>next</strong></span> operation will
-be applied to all tagged messages if that operation can be used in that
-manner. If the <a class="link" href="#auto-tag" title="3.18. auto_tag">$auto_tag</a>
-variable is set, the next operation applies to the tagged messages
-automatically, without requiring the “<span class="quote">tag-prefix</span>”.
-</p><p>
-In <a class="link" href="#macro" title="8. Keyboard macros">macros</a> or <a class="link" href="#push" title="22. Adding key sequences to the keyboard buffer">push</a> commands,
-you can use the “<span class="quote">tag-prefix-cond</span>” operator. If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the “<span class="quote">end-cond</span>”
-operator; after this operator the rest of the macro will be executed as
-normal.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="hooks"></a>4. Using Hooks</h2></div></div></div><p>
-A <span class="emphasis"><em>hook</em></span> is a concept found in many other programs 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 world, a <span class="emphasis"><em>hook</em></span>
-consists of a <a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a> or
-<a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">pattern</a> along with a
-configuration option/command. See
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a>
-</p></li><li><p>
-<a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a>
-</p></li><li><p>
-<a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a>
-</p></li><li><p>
-<a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a>
-</p></li><li><p>
-<a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a>
-</p></li><li><p>
-<a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a>
-</p></li><li><p>
-<a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a>
-</p></li></ul></div><p>
-
-for specific details on each type of <span class="emphasis"><em>hook</em></span> available.
-</p><div class="note"><h3 class="title">Note</h3><p>
-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:
-</p></div><div class="example"><a id="ex-send-hook-my-hdr"></a><p class="title"><b>Example 4.2. Combining <code class="literal">send-hook</code> and <code class="literal">my_hdr</code></b></p><div class="example-contents"><pre class="screen">
-send-hook . 'unmy_hdr From:'
-send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-</pre></div></div><br class="example-break" /><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pattern-hook"></a>4.1. Message Matching in Hooks</h3></div></div></div><p>
-Hooks that act upon messages (<code class="literal">message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook</code>) are evaluated in a
-slightly different manner. For the other
-types of hooks, a <a class="link" href="#regexp" title="1. Regular Expressions">regular expression</a> 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.
-</p><p>
-Mutt allows the use of the <a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">search pattern</a>
-language for matching messages in hook commands. This works in
-exactly the same way as it would when <span class="emphasis"><em>limiting</em></span> or
-<span class="emphasis"><em>searching</em></span> 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.).
-</p><p>
-For example, if you wanted to set your return address based upon sending
-mail to a specific address, you could do something like:
-</p><pre class="screen">
-send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
-</pre><p>
-which would execute the given command when sending mail to
-<span class="emphasis"><em>me@cs.hmc.edu</em></span>.
-</p><p>
-However, it is not required that you write the pattern to match using the
-full searching language. You can still specify a simple <span class="emphasis"><em>regular
-expression</em></span> like the other hooks, in which case Mutt will translate your
-pattern into the full language, using the translation specified by the
-<a class="link" href="#default-hook" title="3.41. default_hook">$default_hook</a> variable. The
-pattern is translated at the time the hook is declared, so the value of
-<a class="link" href="#default-hook" title="3.41. default_hook">$default_hook</a> that is in effect
-at that time will be used.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="query"></a>5. External Address Queries</h2></div></div></div><p>
-Mutt 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 <a class="link" href="#query-command" title="3.231. query_command">$query_command</a> variable, you specify the wrapper
-command to use. For example:
-</p><pre class="screen">
-set query_command = "mutt_ldap_query.pl '%s'"
-</pre><p>
-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 then
-some other optional information. On error, or if there are no matching
-addresses, return a non-zero exit code and a one line error message.
-</p><p>
-An example multiple response output:
-</p><pre class="screen">
-Searching database ... 20 entries ... 3 matching:
-me@cs.hmc.edu Michael Elkins mutt dude
-blong@fiction.net Brandon Long mutt and more
-roessler@does-not-exist.org Thomas Roessler mutt pgp
-</pre><p>
-There are two mechanisms for accessing the query function of mutt. One
-is to do a query from the index menu using the <code class="literal"><query></code> 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 addresses
-to mail, start a new query, or have a new query appended to the current
-responses.
-</p><p>
-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 <code class="literal"><complete-query></code> 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 query
-menu. At the query menu, you can select one or more addresses to be
-added to the prompt.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailbox-formats"></a>6. Mailbox Formats</h2></div></div></div><p>
-Mutt 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 new
-mailboxes, Mutt uses the default specified with the <a class="link" href="#mbox-type" title="3.117. mbox_type">$mbox_type</a> variable.
-</p><p>
-<span class="bold"><strong>mbox</strong></span>. 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:
-</p><pre class="screen">
-From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-</pre><p>
-to denote the start of a new message (this is often referred to as the
-“<span class="quote">From_</span>” line).
-</p><p>
-<span class="bold"><strong>MMDF</strong></span>. This is a variant of the <span class="emphasis"><em>mbox</em></span> format. Each message is
-surrounded by lines containing “<span class="quote">^A^A^A^A</span>” (four control-A's).
-</p><p>
-<span class="bold"><strong>MH</strong></span>. A radical departure from <span class="emphasis"><em>mbox</em></span> and <span class="emphasis"><em>MMDF</em></span>, 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 displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
-detects this type of mailbox by looking for either <code class="literal">.mh_sequences</code>
-or <code class="literal">.xmhcache</code> (needed to distinguish normal directories from MH
-mailboxes).
-</p><p>
-<span class="bold"><strong>Maildir</strong></span>. The newest of the mailbox formats, used by the Qmail MTA (a
-replacement for sendmail). Similar to <span class="emphasis"><em>MH</em></span>, except that it adds three
-subdirectories of the mailbox: <span class="emphasis"><em>tmp</em></span>, <span class="emphasis"><em>new</em></span> and <span class="emphasis"><em>cur</em></span>. Filenames
-for the messages are chosen in such a way they are unique, even when two
-programs are writing the mailbox over NFS, which means that no file locking
-is needed.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="shortcuts"></a>7. Mailbox Shortcuts</h2></div></div></div><p>
-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.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-! -- refers to your <a class="link" href="#spoolfile" title="3.276. spoolfile">$spoolfile</a> (incoming) mailbox
-</p></li><li><p>
-> -- refers to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> file
-</p></li><li><p>
-< -- refers to your <a class="link" href="#record" title="3.239. record">$record</a> file
-</p></li><li><p>
-^ -- refers to the current mailbox
-</p></li><li><p>
-- or !! -- refers to the file you've last visited
-</p></li><li><p>
-˜ -- refers to your home directory
-</p></li><li><p>
-= or + -- refers to your <a class="link" href="#folder" title="3.58. folder">$folder</a> directory
-</p></li><li><p>
-@<span class="emphasis"><em>alias</em></span> -- refers to the <a class="link" href="#save-hook" title="16. Specify default save mailbox">default save folder</a> as determined by the address of the alias
-</p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-lists"></a>8. Handling Mailing Lists</h2></div></div></div><p>
-Mutt 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 <a class="link" href="#lists" title="12. Mailing lists">lists and subscribe</a> commands in your muttrc.
-</p><p>
-Now that Mutt 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 <span class="emphasis"><em>index</em></span> menu display. This is useful to distinguish between
-personal and list mail in the same mailbox. In the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable, the escape “<span class="quote">%L</span>”
-will return the string “<span class="quote">To <list></span>” when “<span class="quote">list</span>” appears in the
-“<span class="quote">To</span>” field, and “<span class="quote">Cc <list></span>” when it appears in the “<span class="quote">Cc</span>”
-field (otherwise it returns the name of the author).
-</p><p>
-Often times the “<span class="quote">To</span>” and “<span class="quote">Cc</span>” fields in mailing list messages
-tend to get quite large. Most people do not bother to remove the
-author of the message they reply to from the list, resulting in
-two or more copies being sent to that person. The <code class="literal"><list-reply></code>
-function, which by default is bound to “<span class="quote">L</span>” in the <span class="emphasis"><em>index</em></span> menu
-and <span class="emphasis"><em>pager</em></span>, helps reduce the clutter by only replying to the
-known mailing list addresses instead of all recipients (except as
-specified by <code class="literal">Mail-Followup-To</code>, see below).
-</p><p>
-Mutt also supports the <code class="literal">Mail-Followup-To</code> header. When you send
-a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the <a class="link" href="#followup-to" title="3.60. followup_to">$followup_to</a> 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 “<span class="quote">followups</span>”) 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.
-</p><p>
-Conversely, when group-replying or list-replying to a message which
-has a <code class="literal">Mail-Followup-To</code> header, mutt will respect this header if
-the <a class="link" href="#honor-followup-to" title="3.79. honor_followup_to">$honor_followup_to</a> 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 <code class="literal">Mail-Followup-To</code>.
-</p><div class="note"><h3 class="title">Note</h3><p>
-When header editing is enabled, you can create a
-<code class="literal">Mail-Followup-To</code> header manually. Mutt will only auto-generate
-this header if it doesn't exist when you send the message.
-</p></div><p>
-The other method some mailing list admins use is to generate a
-“<span class="quote">Reply-To</span>” 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 “<span class="quote">Reply-To</span>”
-field. Mutt uses the <a class="link" href="#reply-to" title="3.242. reply_to">$reply_to</a>
-variable to help decide which address to use. If set to <span class="emphasis"><em>ask-yes</em></span> or
-<span class="emphasis"><em>ask-no</em></span>, you will be
-prompted as to whether or not you would like to use the address given in
-the “<span class="quote">Reply-To</span>” field, or reply directly to the address given in the
-“<span class="quote">From</span>” field. When set to <span class="emphasis"><em>yes</em></span>, the “<span class="quote">Reply-To</span>” field will be used when
-present.
-</p><p>
-The “<span class="quote">X-Label:</span>” header field can be used to further identify mailing
-lists or list subject matter (or just to annotate messages
-individually). The <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable's “<span class="quote">%y</span>” and
-“<span class="quote">%Y</span>” escapes can be used to expand “<span class="quote">X-Label:</span>” fields in the
-index, and Mutt's pattern-matcher can match regular expressions to
-“<span class="quote">X-Label:</span>” fields with the “<span class="quote">˜y</span>” selector. “<span class="quote">X-Label:</span>” is not a
-standard message header field, but it can easily be inserted by procmail
-and other mail filtering agents.
-</p><p>
-Lastly, Mutt has the ability to <a class="link" href="#sort" title="3.270. sort">sort</a> the mailbox into
-<a class="link" href="#threads" title="4.3. Threaded Mode">threads</a>. 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 dealing
-with large volume mailing lists easier because you can easily delete
-uninteresting threads and quickly find topics of value.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="handling-folders"></a>9. Handling multiple folders</h2></div></div></div><p>
-Mutt supports setups with multiple folders, allowing all of them to
-be monitored for new mail (see <a class="xref" href="#mailboxes" title="14. Monitoring incoming mail">Section 14, “Monitoring incoming mail”</a> for details).
-</p><p>
-When in the index menu and being idle (also see
-<a class="link" href="#timeout" title="3.287. timeout">$timeout</a>), Mutt periodically checks
-for new mail in all folders which have been configured via the
-<code class="literal">mailboxes</code> command. The interval depends on the folder
-type: for local/IMAP folders it consults
-<a class="link" href="#mail-check" title="3.105. mail_check">$mail_check</a> and
-<a class="link" href="#pop-checkinterval" title="3.215. pop_checkinterval">$pop_checkinterval</a>
-for POP folders.
-</p><p>
-Outside the index menu the directory browser supports checking
-for new mail using the <code class="literal"><check-new></code> function which is
-unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the <code class="literal">mailboxes</code> command,
-and indicate which contain new messages. Mutt will automatically enter this
-mode when invoked from the command line with the <code class="literal">-y</code> option.
-</p><p>
-For the pager, index and directory browser menus, Mutt contains the
-<code class="literal"><buffy-list></code> function (bound to “<span class="quote">.</span>” by default)
-which will print a list of folders with new mail in the command line at
-the bottom of the screen.
-</p><p>
-For the index, by default Mutt displays the number of mailboxes with new
-mail in the status bar, please refer to the
-<a class="link" href="#index-format" title="3.101. index_format">$index_format</a>
-variable for details.
-</p><p>
-When changing folders, Mutt fills the prompt with the first folder from
-the mailboxes list containing new mail (if any), pressing
-<span class="emphasis"><em>space</em></span> will cycle through folders with new mail.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="editing-threads"></a>10. Editing threads</h2></div></div></div><p>
-Mutt 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.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="link-threads"></a>10.1. Linking threads</h3></div></div></div><p>
-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 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 <code class="literal"><link-threads></code> function (bound to & by default). The
-reply will then be connected to this "parent" message.
-</p><p>
-You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="break-threads"></a>10.2. Breaking threads</h3></div></div></div><p>
-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 <code class="literal"><break-thread></code> function (bound
-by default to #), which will turn the subthread starting from the
-current message into a whole different thread.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="dsn"></a>11. Delivery Status Notification (DSN) Support</h2></div></div></div><p>
-RFC1894 defines a set of MIME content types for relaying information
-about the status of electronic mail messages. These can be thought of as
-“<span class="quote">return receipts.</span>”
-</p><p>
-To support DSN, there are two variables. <a class="link" href="#dsn-notify" title="3.47. dsn_notify">$dsn_notify</a> is used to request receipts for
-different results (such as failed message, message delivered, etc.).
-<a class="link" href="#dsn-return" title="3.48. dsn_return">$dsn_return</a> requests how much
-of your message should be returned with the receipt (headers or full
-message).
-</p><p>
-When using <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a> for mail
-delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA
-supporting DSN command line options compatible to Sendmail: The -N and -R
-options can be used by the mail client to make requests as to what type of
-status messages should be returned. Please consider your MTA documentation
-whether DSN is supported.
-</p><p>
-For SMTP delivery using <a class="link" href="#smtp-url" title="3.269. smtp_url">$smtp_url</a>, it depends on the
-capabilities announced by the server whether mutt will attempt to
-request DSN or not.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="urlview"></a>12. Start a WWW Browser on URLs</h2></div></div></div><p>
-If a message contains URLs, 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
-<a class="ulink" href="ftp://ftp.mutt.org/mutt/contrib/" target="_top">ftp://ftp.mutt.org/mutt/contrib/</a>
-and the configuration commands:
-</p><pre class="screen">
-macro index \cb |urlview\n
-macro pager \cb |urlview\n
-</pre></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="compressedfolders"></a>1. Compressed folders Support (OPTIONAL)</h2></div></div></div><p>
-If Mutt was compiled with compressed folders support (by running the
-<span class="emphasis"><em>configure</em></span> script with the
-<span class="emphasis"><em>--enable-compressed</em></span> flag), Mutt can open folders
-stored in an arbitrary format, provided that the user has a script to
-convert from/to this format to one of the accepted.
-
-The most common use is to open compressed archived folders e.g. with
-gzip.
-
-In addition, the user can provide a script that gets a folder in an
-accepted format and appends its context to the folder in the
-user-defined format, which may be faster than converting the entire
-folder to the accepted format, appending to it and converting back to
-the user-defined format.
-
-There are three hooks defined (<a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a>, <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> and <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>) which define commands to
-uncompress and compress a folder and to append messages to an existing
-compressed folder respectively.
-
-For example:
-
-</p><pre class="screen">
-open-hook \\.gz$ "gzip -cd %f > %t"
-close-hook \\.gz$ "gzip -c %t > %f"
-append-hook \\.gz$ "gzip -c %t >> %f"
-</pre><p>
-
-You do not have to specify all of the commands. If you omit <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>, the folder will be open and
-closed again each time you will add to it. If you omit <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> (or give empty command) , the
-folder will be open in the mode. If you specify <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> though you'll be able to
-append to the folder.
-
-Note that Mutt 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
-<a class="link" href="#save-empty" title="3.249. save_empty">$save_empty</a>, so that
-the compressed file will be removed if you delete all of the messages.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="open-hook"></a>1.1. Open a compressed mailbox for reading</h3></div></div></div><p>
-Usage: <code class="literal">open-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-The <span class="emphasis"><em>command</em></span> is the command that can be used for
-opening the folders whose names match <span class="emphasis"><em>regexp</em></span>.
-
-The <span class="emphasis"><em>command</em></span> string is the printf-like format
-string, and it should accept two parameters: %f, which is
-replaced with the (compressed) folder name, and %t which is
-replaced with the name of the temporary folder to which to write.
-
-%f and %t can be repeated any number of times in the
-command string, and all of the entries are replaced with the
-appropriate folder name. In addition, %% is replaced by
-%, as in printf, and any other %anything is left as is.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the original compressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-open-hook \\.gz$ "gzip -cd %f > %t"
-</pre><p>
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="close-hook"></a>1.2. Write a compressed mailbox</h3></div></div></div><p>
-Usage: <code class="literal">close-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-This is used to close the folder that was open with the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command after some changes were
-made to it.
-
-The <span class="emphasis"><em>command</em></span> string is the command that can be
-used for closing the folders whose names match
-<span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. Temporary folder in this
-case is the folder previously produced by the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-close-hook \\.gz$ "gzip -c %t > %f"
-</pre><p>
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type, and the file can only be open in the
-read-only mode.
-
-<a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is not called when you
-exit from the folder if the folder was not changed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="append-hook"></a>1.3. Append a message to a compressed mailbox</h3></div></div></div><p>
-Usage: <code class="literal">append-hook</code> <span class="emphasis"><em>regexp</em></span> "<span class="emphasis"><em>command</em></span>"
-
-This command is used for saving to an existing compressed folder. The
-<span class="emphasis"><em>command</em></span> is the command that can be used for
-appending to the folders whose names match
-<span class="emphasis"><em>regexp</em></span>. It has the same format as in the <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> command. The temporary folder in
-this case contains the messages that are being appended.
-
-The <span class="emphasis"><em>command</em></span> should <span class="bold"><strong>not</strong></span> remove the decompressed file. The
-<span class="emphasis"><em>command</em></span> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-</p><pre class="screen">
-append-hook \\.gz$ "gzip -c %t >> %f"
-</pre><p>
-
-When <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> 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 (<a class="link" href="#mbox-type" title="3.117. mbox_type">$mbox_type</a>) type is always
-supposed (i.e. this is the format used for the temporary folder).
-
-If the file does not exist when you save to it, <a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a> is called, and not <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a>. <a class="link" href="#append-hook" title="1.3. Append a message to a compressed mailbox">append-hook</a> is only for appending to
-existing folders.
-
-If the <span class="emphasis"><em>command</em></span> is empty, this operation is
-disabled for this file type. In this case, the folder will be open and
-closed again (using <a class="link" href="#open-hook" title="1.1. Open a compressed mailbox for reading">open-hook</a> and
-<a class="link" href="#close-hook" title="1.2. Write a compressed mailbox">close-hook</a>respectively) each time you
-will add to it.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="id3067480"></a>1.4. Encrypted folders</h3></div></div></div><p>
-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 use
-the following hooks:
-
-</p><pre class="screen">
-open-hook \\.pgp$ "pgp -f < %f > %t"
-close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-</pre><p>
-
-Please note, that PGP does not support appending to an encrypted
-folder, so there is no append-hook defined.
-
-If you are using GnuPG instead of PGP, you may use the following hooks
-instead:
-
-</p><pre class="screen">
-open-hook \\.gpg$ "gpg --decrypt < %f > %t"
-close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
-</pre><p>
-
-<span class="bold"><strong>Note:</strong></span> the folder is temporary stored
-decrypted in the /tmp directory, where it can be read by your system
-administrator. So think about the security aspects of this.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="mimesupport"></a>Chapter 5. Mutt's MIME Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="#mime-lookup">7. MIME Lookup</a></span></dt></dl></div><p>
-Quite a bit of effort has been made to make Mutt 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 for MIME, there are two extra
-types of configuration files which Mutt uses. One is the
-<code class="literal">mime.types</code> file, which contains the mapping of file extensions to
-IANA MIME types. The other is the <code class="literal">mailcap</code> file, which specifies
-the external commands to use for handling specific MIME types.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-mime"></a>1. Using MIME in Mutt</h2></div></div></div><p>
-There are three areas/menus in Mutt which deal with MIME, they are the
-pager (while viewing a message), the attachment menu and the compose
-menu.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-pager"></a>1.1. Viewing MIME messages in the pager</h3></div></div></div><p>
-When you select a message from the index and view it in the pager, Mutt
-decodes the message to a text representation. Mutt internally supports
-a number of MIME types, including <code class="literal">text/plain, text/enriched,
-message/rfc822, and message/news</code>. In addition, the export
-controlled version of Mutt recognizes a variety of PGP MIME types,
-including PGP/MIME and application/pgp.
-</p><p>
-Mutt will denote attachments with a couple lines describing them.
-These lines are of the form:
-</p><pre class="screen">
-[-- Attachment #1: Description --]
-[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-</pre><p>
-Where the <code class="literal">Description</code> is the description or filename given for the
-attachment, and the <code class="literal">Encoding</code> is one of
-<code class="literal">7bit/8bit/quoted-printable/base64/binary</code>.
-</p><p>
-If Mutt cannot deal with a MIME type, it will display a message like:
-</p><pre class="screen">
-[-- image/gif is unsupported (use 'v' to view this part) --]
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-menu"></a>1.2. The Attachment Menu</h3></div></div></div><p>
-The default binding for <code class="literal">view-attachments</code> is `v', which displays the
-attachment menu for a message. The attachment menu displays a list of
-the 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 “<span class="quote">tag-prefix</span>” 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.
-</p><p>
-Finally, you can apply the usual message-related functions (like
-<a class="link" href="#resend-message"><code class="literal"><resend-message></code></a>, and the
-<code class="literal"><reply></code> and <code class="literal"><forward></code>
-functions) to attachments of type <code class="literal">message/rfc822</code>.
-</p><p>
-See the help on the attachment menu for more information.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-menu"></a>1.3. The Compose Menu</h3></div></div></div><p>
-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.
-</p><p>
-Attachments appear as follows:
-</p><pre class="screen">
-- 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>
-</pre><p>
-The '-' denotes that Mutt will delete the file after sending (or
-postponing, or canceling) the message. It can be toggled with the
-<code class="literal">toggle-unlink</code> command (default: u). The next field is the MIME
-content-type, and can be changed with the <code class="literal">edit-type</code> 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 <code class="literal">edit-encoding</code> 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 <code class="literal">rename-file</code> command (default: R).
-The final field is the description of the attachment, and can be
-changed with the <code class="literal">edit-description</code> command (default: d).
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-types"></a>2. MIME Type configuration with <code class="literal">mime.types</code></h2></div></div></div><p>
-When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at <code class="literal">${HOME}/.mime.types</code>, and then
-the system mime.types file at <code class="literal">/usr/local/share/mutt/mime.types</code> or
-<code class="literal">/etc/mime.types</code>
-</p><p>
-The mime.types file consist of lines containing a MIME type and a space
-separated list of extensions. For example:
-</p><pre class="screen">
-application/postscript ps eps
-application/pgp pgp
-audio/x-aiff aif aifc aiff
-</pre><p>
-A sample <code class="literal">mime.types</code> file comes with the Mutt distribution, and
-should contain most of the MIME types you are likely to use.
-</p><p>
-If Mutt 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 will assume that the file is plain text, and mark it
-as <code class="literal">text/plain</code>. If the file contains binary information, then Mutt will
-mark it as <code class="literal">application/octet-stream</code>. You can change the MIME
-type that Mutt assigns to an attachment by using the <code class="literal">edit-type</code>
-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 recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
-major mime types, such as the chemical type that is widely used in the
-molecular modeling community to pass molecular data in various forms to
-various molecular viewers. Non-recognized mime types should only be used
-if the recipient of the message is likely to be expecting such attachments.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailcap"></a>3. MIME Viewer configuration with <code class="literal">mailcap</code></h2></div></div></div><p>
-Mutt supports RFC 1524 MIME Configuration, in particular the Unix
-specific format specified in Appendix A of RFC 1524. 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.
-</p><p>
-In order to handle various MIME types that Mutt can not handle
-internally, Mutt parses a series of external configuration files to
-find an external handler. The default search string for these files
-is a colon delimited list containing the following files:
-</p><div class="orderedlist"><ol type="1"><li><p><code class="literal">$HOME/.mailcap</code></p></li><li><p><code class="literal">$PKGDATADIR/mailcap</code></p></li><li><p><code class="literal">$SYSCONFDIR/mailcap</code></p></li><li><p><code class="literal">/etc/mailcap</code></p></li><li><p><code class="literal">/usr/etc/mailcap</code></p></li><li><p><code class="literal">/usr/local/etc/mailcap</code></p></li></ol></div><p>
-where <code class="literal">$HOME</code> is your home directory. The
-<code class="literal">$PKGDATADIR</code> and the
-<code class="literal">$SYSCONFDIR</code> directories depend on where mutt
-is installed: the former is the default for shared data, the
-latter for system configuration files.
-</p><p>
-The default search path can be obtained by running the following
-command:
-</p><pre class="screen">
-mutt -nF /dev/null -Q mailcap_path
-</pre><p>
-In particular, the metamail distribution will install a mailcap file,
-usually as <code class="literal">/usr/local/etc/mailcap</code>, which contains some baseline
-entries.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-basics"></a>3.1. The Basics of the mailcap file</h3></div></div></div><p>
-A mailcap file consists of a series of lines which are comments, blank,
-or definitions.
-</p><p>
-A comment line consists of a # character followed by anything you want.
-</p><p>
-A blank line is blank.
-</p><p>
-A definition line consists of a content type, a view command, and any
-number of optional fields. Each field of a definition line is divided
-by a semicolon ';' character.
-</p><p>
-The content type is specified in the MIME standard type/subtype method.
-For example,
-<code class="literal">text/plain, text/html, image/gif, </code>
-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, <code class="literal">image/*</code>, or
-<code class="literal">video,</code> will match all image types and video types,
-respectively.
-</p><p>
-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 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 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.
-</p><p>
-So, in the simplest form, you can send a text/plain message to the
-external pager more on stdin:
-</p><pre class="screen">
-text/plain; more
-</pre><p>
-Or, you could send the message as a file:
-</p><pre class="screen">
-text/plain; more %s
-</pre><p>
-Perhaps you would like to use lynx to interactively view a text/html
-message:
-</p><pre class="screen">
-text/html; lynx %s
-</pre><p>
-In this case, lynx does not support viewing a file from stdin, so you
-must use the %s syntax.
-</p><div class="note"><h3 class="title">Note</h3><p>
-<span class="emphasis"><em>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.</em></span>
-</p></div><p>
-On the other hand, maybe you don't want to use lynx interactively, you
-just want to have it convert the text/html to text/plain, then you can
-use:
-</p><pre class="screen">
-text/html; lynx -dump %s | more
-</pre><p>
-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:
-</p><pre class="screen">
-text/html; lynx %s
-text/*; more
-</pre><p>
-This is the simplest form of a mailcap file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="secure-mailcap"></a>3.2. Secure use of mailcap</h3></div></div></div><p>
-The interpretation of shell meta-characters embedded in MIME parameters
-can lead to security problems in general. Mutt tries to quote parameters
-in expansion of %s syntaxes properly, and avoids risky characters by
-substituting them, see the <a class="link" href="#mailcap-sanitize" title="3.107. mailcap_sanitize">$mailcap_sanitize</a> variable.
-</p><p>
-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:
-</p><p>
-<span class="emphasis"><em>Keep the %-expandos away from shell quoting.</em></span>
-Don't quote them with single or double quotes. Mutt 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 behavior with quotes introduces new leaks - there is no
-alternative to correct quoting in the first place.
-</p><p>
-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 <code class="literal">$charset</code> inside the backtick expansion is safe,
-since it is not itself subject to any further expansion):
-</p><pre class="screen">
-text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="advanced-mailcap"></a>3.3. Advanced mailcap Usage</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="optional-mailcap-fields"></a>3.3.1. Optional Fields</h4></div></div></div><p>
-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 recognizes the following optional fields:
-</p><div class="variablelist"><dl><dt><span class="term">copiousoutput</span></dt><dd><p>
-This flag tells Mutt that the command passes possibly large amounts of
-text on stdout. This causes Mutt 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 assumes that the command
-is interactive. One could use this to replace the pipe to <code class="literal">more</code>
-in the <code class="literal">lynx -dump</code> example in the Basic section:
-</p><pre class="screen">
-text/html; lynx -dump %s ; copiousoutput
-</pre><p>
-This will cause lynx to format the text/html output as text/plain
-and Mutt will use your standard pager to display the results.
-</p></dd><dt><span class="term">needsterminal</span></dt><dd><p>
-Mutt uses this flag when viewing attachments with <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, in order to decide whether it should honor the setting
-of the <a class="link" href="#wait-key" title="3.300. wait_key">$wait_key</a> variable or
-not. When an attachment is viewed using an interactive program, and the
-corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag, Mutt will use
-<a class="link" href="#wait-key" title="3.300. wait_key">$wait_key</a> and the exit status
-of 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.
-</p></dd><dt><span class="term">compose=<command></span></dt><dd><p>
-This flag specifies the command to use to create a new attachment of a
-specific MIME type. Mutt supports this from the compose menu.
-</p></dd><dt><span class="term">composetyped=<command></span></dt><dd><p>
-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 supports this from the compose menu.
-</p></dd><dt><span class="term">print=<command></span></dt><dd><p>
-This flag specifies the command to use to print a specific MIME type.
-Mutt supports this from the attachment and compose menus.
-</p></dd><dt><span class="term">edit=<command></span></dt><dd><p>
-This flag specifies the command to use to edit a specific MIME type.
-Mutt supports this from the compose menu, and also uses it to compose
-new attachments. Mutt will default to the defined editor for text
-attachments.
-</p></dd><dt><span class="term">nametemplate=<template></span></dt><dd><p>
-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 <code class="literal">text/html</code> if the file ends in <code class="literal">.html</code>.
-So, you would specify lynx as a <code class="literal">text/html</code> viewer with a line in
-the mailcap file like:
-</p><pre class="screen">
-text/html; lynx %s; nametemplate=%s.html
-</pre></dd><dt><span class="term">test=<command></span></dt><dd><p>
-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 uses this entry. If the command returns non-zero,
-then the test failed, and Mutt continues searching for the right entry.
-Note that the content-type must match before Mutt performs the test.
-For example:
-</p><pre class="screen">
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s
-</pre><p>
-In this example, Mutt 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 will call netscape to display the
-text/html object. If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
-</p></dd></dl></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-search-order"></a>3.3.2. Search Order</h4></div></div></div><p>
-When searching for an entry in the mailcap file, Mutt will search for
-the most useful entry for its purpose. For instance, if you are
-attempting to print an <code class="literal">image/gif</code>, and you have the following
-entries in your mailcap file, Mutt will search for an entry with the
-print command:
-</p><pre class="screen">
-image/*; xv %s
-image/gif; ; print= anytopnm %s | pnmtops | lpr; \
- nametemplate=%s.gif
-</pre><p>
-Mutt will skip the <code class="literal">image/*</code> entry and use the <code class="literal">image/gif</code>
-entry with the print command.
-</p><p>
-In addition, you can use this with <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>
-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.
-</p><pre class="screen">
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s; nametemplate=%s.html
-text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
-</pre><p>
-For <a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, Mutt 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 will use the second entry
-for interactive viewing.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-command-expansion"></a>3.3.3. Command Expansion</h4></div></div></div><p>
-The various commands defined in the mailcap files are passed to the
-<code class="literal">/bin/sh</code> shell using the system() function. Before the
-command is passed to <code class="literal">/bin/sh -c</code>, it is parsed to expand
-various special parameters with information from Mutt. The keywords
-Mutt expands are:
-</p><div class="variablelist"><dl><dt><span class="term">%s</span></dt><dd><p>
-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 to not pass the body of the message
-to the view/print/edit program on stdin.
-</p></dd><dt><span class="term">%t</span></dt><dd><p>
-Mutt 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 <code class="literal">text/html</code> or
-<code class="literal">image/gif</code>.
-</p></dd><dt><span class="term">%{<parameter>}</span></dt><dd><p>
-Mutt 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:
-</p><pre class="screen">
-Content-Type: text/plain; charset=iso-8859-1
-</pre><p>
-then Mutt 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.
-</p></dd><dt><span class="term">\%</span></dt><dd><p>
-This will be replaced by a %
-</p></dd></dl></div><p>
-Mutt 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.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-example"></a>3.4. Example mailcap files</h3></div></div></div><p>
-This mailcap file is fairly simple and standard:
-</p><pre class="screen">
-# I'm always running X :)
-video/*; xanim %s > /dev/null
-image/*; xv %s > /dev/null
-
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html; netscape -remote 'openURL(%s)'
-</pre><p>
-This mailcap file shows quite a number of examples:
-</p><pre class="screen">
-# Use xanim to view all videos Xanim produces a header on startup,
-# send that to /dev/null so I don't see it
-video/*; xanim %s > /dev/null
-
-# Send html to a running netscape by remote
-text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
-
-# If I'm not running netscape but I am running X, start netscape on the
-# object
-text/html; netscape %s; test=RunningX
-
-# Else use lynx to view it as text
-text/html; lynx %s
-
-# This version would convert the text/html to text/plain
-text/html; lynx -dump %s; copiousoutput
-
-# I use enscript to print text in two columns to a page
-text/*; more %s; print=enscript -2Gr %s
-
-# Netscape adds a flag to tell itself to view jpegs internally
-image/jpeg;xv %s; x-mozilla-flags=internal
-
-# Use xv to view images if I'm running X
-# In addition, this uses the \ to extend the line and set my editor
-# for images
-image/*;xv %s; test=RunningX; \
- edit=xpaint %s
-
-# Convert images to text using the netpbm tools
-image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
-pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
-# Send excel spreadsheets to my NT box
-application/ms-excel; open.pl %s
-</pre></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="auto-view"></a>4. MIME Autoview</h2></div></div></div><p>
-In addition to explicitly telling Mutt to view an attachment with the
-MIME viewer defined in the mailcap file, Mutt has support for
-automatically viewing MIME attachments while in the pager.
-</p><p>
-To work, you must define a viewer in the mailcap file which uses the
-<code class="literal">copiousoutput</code> 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.
-</p><p>
-You then use the <code class="literal">auto_view</code> muttrc command to list the
-content-types that you wish to view automatically.
-</p><p>
-For instance, if you set auto_view to:
-</p><pre class="screen">
-auto_view text/html application/x-gunzip \
- application/postscript image/gif application/x-tar-gz
-</pre><p>
-Mutt could use the following mailcap entries to automatically view
-attachments of these types.
-</p><pre class="screen">
-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
-</pre><p>
-“<span class="quote">unauto_view</span>” 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.
-“<span class="quote">unauto_view *</span>” will remove all previous entries.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternative-order"></a>5. MIME Multipart/Alternative</h2></div></div></div><p>
-Mutt 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 types
-is preferred. The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
-</p><pre class="screen">
-alternative_order text/enriched text/plain text application/postscript image/*
-</pre><p>
-Next, mutt will check if any of the types have a defined
-<a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a>, and use that. Failing
-that, Mutt will look for any text type. As a last attempt, mutt will
-look for any type it knows how to handle.
-</p><p>
-To remove a MIME type from the <code class="literal">alternative_order</code> list, use the
-<code class="literal">unalternative_order</code> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="attachments"></a>6. Attachment Searching and Counting</h2></div></div></div><p>
-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.
-</p><p>
-In order to provide this information, mutt needs to fully MIME-parse
-all messages affected first. This can slow down operation especially for
-remote mail folders such as IMAP because all messages have to be
-downloaded first regardless whether the user really wants to view them
-or not.
-</p><p>
-The syntax is:
-</p><pre class="screen">
-attachments {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments ?
-</pre><p>
-Disposition is the attachment's Content-disposition type -- either
-<code class="literal">inline</code> or <code class="literal">attachment</code>.
-You can abbreviate this to <code class="literal">I</code> or <code class="literal">A</code>.
-</p><p>
-Disposition is prefixed by either a + symbol or 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.
-</p><p>
-Mime-type is, unsurprisingly, the MIME type of the attachment you want
-to affect. A MIME type is always of the format <code class="literal">major/minor</code>, where
-<code class="literal">major</code> describes the broad category of document you're looking at, and
-<code class="literal">minor</code> describes the specific type within that category. The major
-part of mime-type must be literal text (or the special token “<span class="quote"><code class="literal">*</code></span>”), but
-the minor part may be a regular expression. (Therefore, “<span class="quote"><code class="literal">*/.*</code></span>” matches
-any MIME type.)
-</p><p>
-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.
-</p><p>
-Some examples might help to illustrate. The examples that are not
-commented out define the default configuration of the lists.
-</p><div class="example"><a id="ex-attach-count"></a><p class="title"><b>Example 5.1. Attachment counting</b></p><div class="example-contents"><pre class="screen">
-## 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
-</pre></div></div><br class="example-break" /><p>
-Entering the command “<span class="quote"><code class="literal">attachments ?</code></span>”
-as a command will list your current settings in Muttrc format, so that
-it can be pasted elsewhere.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-lookup"></a>7. MIME Lookup</h2></div></div></div><p>
-Mutt's mime_lookup list specifies a list of mime-types that should not
-be treated according to their mailcap entry. This option is designed to
-deal 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:
-</p><pre class="screen">
-mime_lookup application/octet-stream application/X-Lotus-Manuscript
-</pre><p>
-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.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="optionalfeatures"></a>Chapter 6. Optional features</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="#exact-address">8. Exact address generation</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="optionalfeatures-notes"></a>1. General notes</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compile-time-features"></a>1.1. Enabling/disabling features</h3></div></div></div><p>
-Mutt supports several of optional features which can be enabled or
-disabled at compile-time by giving the <span class="emphasis"><em>configure</em></span> script
-certain arguments. These are listed in the “<span class="quote">Optional features</span>” section of
-the <span class="emphasis"><em>configure --help</em></span> output.
-</p><p>
-Which features are enabled or disabled can later be determined from the
-output of <code class="literal">mutt -v</code>. If a compile option starts with
-“<span class="quote">+</span>” it is enabled and disabled if prefixed with “<span class="quote">-</span>”. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
-OpenSSL, <code class="literal">mutt -v</code> would contain:
-</p><pre class="screen">
--USE_SSL_OPENSSL +USE_SSL_GNUTLS</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="url-syntax"></a>1.2. URL syntax</h3></div></div></div><p>
-Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
-to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in <code class="literal">[]</code> means it is optional and
-may be omitted):
-</p><pre class="screen">
-proto[s]://[username[:password]@]server[:port]/[path]
-</pre><p>
-<code class="literal">proto</code> is the communication protocol:
-<code class="literal">imap</code> for IMAP, <code class="literal">pop</code> for POP3 and
-<code class="literal">smtp</code> for SMTP. If “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”
-is appended, mutt will attempt to establish an encrypted communication
-using SSL or TLS. If no explicit port is given, mutt will use the
-system's default for the given protocol.
-</p><p>
-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the <code class="literal">pop_user</code> or
-<code class="literal">imap_user</code> variables. It may contain the “<span class="quote">@</span>” symbol
-being used by many mail systems as part of the login name. A password can be
-given, too but is not recommended if the URL is specified in a configuration
-file on disk.
-</p><p>
-The optional path is only relevant for IMAP.
-</p><p>
-For IMAP for example, you can select an alternative port by specifying it with the
-server: <code class="literal">imap://imapserver:port/INBOX</code>. You can also specify different
-username for each folder: <code class="literal">imap://username@imapserver[:port]/INBOX</code>
-or <code class="literal">imap://username2@imapserver[:port]/path/to/folder</code>.
-Replacing <code class="literal">imap://</code> by <code class="literal">imaps://</code>
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ssl"></a>2. SSL/TLS Support</h2></div></div></div><p>
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
-compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
-by running the <span class="emphasis"><em>configure</em></span> script with the
-<span class="emphasis"><em>--enable-ssl=...</em></span> option for OpenSSL or
-<span class="emphasis"><em>--enable-gnutls=...</em></span> for GnuTLS). Mutt can then
-attempt to encrypt communication with remote servers if these protocols
-are suffixed with “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="pop"></a>3. POP3 Support</h2></div></div></div><p>
-If Mutt was compiled with POP3 support (by running the <span class="emphasis"><em>configure</em></span>
-script with the <span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work
-with mailboxes located on a remote POP3 server and fetch mail for local
-browsing.
-</p><p>
-Remote POP3 servers can be accessed using URLs with the <code class="literal">pop</code> protocol
-for unencrypted and <code class="literal">pops</code> for encrypted
-communication, see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details.
-</p><p>
-Polling for new mail is more expensive over POP3 than locally. For this
-reason the frequency at which Mutt will check for mail remotely can be
-controlled by the
-<a class="link" href="#pop-checkinterval" title="3.215. pop_checkinterval">$pop_checkinterval</a>
-variable, which defaults to every 60 seconds.
-</p><a id="fetch-mail"></a><p>
-Another way to access your POP3 mail is the <code class="literal"><fetch-mail$</code> function
-(default: G). It allows to connect to <a class="link" href="#pop-host" title="3.217. pop_host">$pop_host</a>, fetch all your new mail and place it in the
-local <a class="link" href="#spoolfile" title="3.276. spoolfile">$spoolfile</a>. After this
-point, Mutt runs exactly as if the mail had always been local.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you only need to fetch all messages to a
-local mailbox you should consider using a specialized program, such as
-<code class="literal">fetchmail</code>, <code class="literal">getmail</code> or similar.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="imap"></a>4. IMAP Support</h2></div></div></div><p>
-If Mutt was compiled with IMAP support (by running the <span class="emphasis"><em>configure</em></span>
-script with the <span class="emphasis"><em>--enable-imap</em></span> flag), it has the ability to work
-with folders located on a remote IMAP server.
-</p><p>
-You can access the remote inbox by selecting the folder by its URL
-(see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details) using the
-<code class="literal">imap</code> or <code class="literal">imaps</code> protocol.
-Alternatively, a pine-compatible notation is also supported, ie
-<code class="literal">{[username@]imapserver[:port][/ssl]}path/to/folder</code>
-</p><p>
-Note that not all servers use “<span class="quote">/</span>” as the hierarchy separator. Mutt should
-correctly notice which separator is being used by the server and convert
-paths accordingly.
-</p><p>
-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
-<span class="emphasis"><em>toggle-subscribed</em></span> command. See also the
-<a class="link" href="#imap-list-subscribed" title="3.89. imap_list_subscribed">$imap_list_subscribed</a> variable.
-</p><p>
-Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
-want to carefully tune the
-<a class="link" href="#mail-check" title="3.105. mail_check">$mail_check</a>
-and
-<a class="link" href="#timeout" title="3.287. timeout">$timeout</a>
-variables. Personally I use
-</p><pre class="screen">
-set mail_check=90
-set timeout=15
-</pre><p>
-with relatively good results over my slow modem line.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that if you are using mbox as the mail store on UW servers prior to
-v12.250, the server has been reported to disconnect a client if another client
-selects the same folder.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-browser"></a>4.1. The Folder Browser</h3></div></div></div><p>
-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:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-In lieu 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.
-</p></li><li><p>
-For the case where an entry can contain both messages and
-subfolders, the selection key (bound to <code class="literal">enter</code> by default)
-will choose to descend into the subfolder view. If you wish to view
-the messages in that folder, you must use <code class="literal">view-file</code> instead
-(bound to <code class="literal">space</code> by default).
-</p></li><li><p>
-You can create, delete and rename mailboxes with the
-<code class="literal">create-mailbox</code>, <code class="literal">delete-mailbox</code>, and
-<code class="literal">rename-mailbox</code> commands (default bindings: <code class="literal">C</code>,
-<code class="literal">d</code> and <code class="literal">r</code>, respectively). You may also
-<code class="literal">subscribe</code> and <code class="literal">unsubscribe</code> to mailboxes (normally
-these are bound to <code class="literal">s</code> and <code class="literal">u</code>, respectively).
-</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authentication"></a>4.2. Authentication</h3></div></div></div><p>
-Mutt 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".
-</p><p>
-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 library
-installed on your system and compile mutt with the <span class="emphasis"><em>--with-sasl</em></span> flag.
-</p><p>
-Mutt will try whichever methods are compiled in and available on the server,
-in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-</p><p>
-There are a few variables which control authentication:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="link" href="#imap-user" title="3.96. imap_user">$imap_user</a> - 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 (ie by using a mailbox name of the form
-<code class="literal">{user@host}</code>).
-</p></li><li><p>
-<a class="link" href="#imap-pass" title="3.91. imap_pass">$imap_pass</a> - a
-password which you may preset, used by all authentication methods where
-a password is needed.
-</p></li><li><p>
-<a class="link" href="#imap-authenticators" title="3.83. imap_authenticators">$imap_authenticators</a> - 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).
-</p></li></ul></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="smtp"></a>5. SMTP Support</h2></div></div></div><p>
-Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
-was configured and built with <code class="literal">--enable-smtp</code>.
-</p><p>
-If the configuration variable
-<a class="link" href="#smtp-url" title="3.269. smtp_url">$smtp_url</a> is set, mutt
-will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a>.
-</p><p>
-For details on the URL syntax, please see <a class="xref" href="#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>.
-</p><p>
-The built-in SMTP support supports encryption (the <code class="literal">smtps</code> protocol
-using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
-for SASL are specified in <a class="link" href="#smtp-authenticators" title="3.267. smtp_authenticators">$smtp_authenticators</a>
-defaulting to an empty list which makes mutt try all available methods
-from most-secure to least-secure.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="account-hook"></a>6. Managing multiple accounts</h2></div></div></div><p>
-If you happen to have accounts on multiple IMAP, POP and/or SMTP 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 which includes (for example) polling for new mail, storing Fcc
-messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
-as passwords or tunnel commands but not settings such as sender
-address or name (because in general it should be considered unpredictable
-which account-hook was last used).
-</p><p>
-Some examples:
-</p><pre class="screen">
-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"'
-account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="caching"></a>7. Local caching</h2></div></div></div><p>
-Mutt contains two types of local caching: <span class="emphasis"><em>(1)</em></span>
-the so-called “<span class="quote">header caching</span>” and <span class="emphasis"><em>(2)</em></span> the
-so-called “<span class="quote">body caching</span>” which are both described in this section.
-</p><p>
-Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
-support as these use it (body caching requires no external library).
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-caching"></a>7.1. Header caching</h3></div></div></div><p>
-Mutt provides optional support for caching message headers for the
-following types of folders: IMAP, POP, Maildir and MH. Header caching
-greatly improves speed because for remote folders, headers
-usually only need to be downloaded once. For Maildir and MH, reading the
-headers from a single file is much faster than looking at possibly
-thousands of single files (since Maildir and MH use one file per message.)
-</p><p>
-Header caching can be enabled via the configure script and the
-<span class="emphasis"><em>--enable-hcache</em></span> option. It's not turned on
-by default because external database libraries are required: one
-of tokyocabinet, qdbm, gdbm or bdb must be present.
-</p><p>
-If enabled, <a class="link" href="#header-cache" title="3.109. header_cache">$header_cache</a> can be
-used to either point to a file or a directory. If set to point to
-a file, one database file for all folders will be used (which may
-result in lower performance), but one file per folder if it points
-to a directory.
-</p><p>
-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-</p><pre class="screen">
-$ printf '%s' '/path/to/folder' | md5sum
-</pre><p>
-The <code class="literal">md5sum</code> command may also be
-named <code class="literal">md5</code>, depending on your operating system.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="body-caching"></a>7.2. Body caching</h3></div></div></div><p>
-Both cache methods can be combined using the same directory for storage
-(and for IMAP/POP even provide meaningful file names) which simplifies
-manual maintenance tasks.
-</p><p>
-In addition to caching message headers only, mutt can also cache
-whole message bodies. This results in faster display of messages
-for POP and IMAP folders because messages usually have to be
-downloaded only once.
-</p><p>
-For configuration, the variable <a class="link" href="#message-cachedir" title="3.133. message_cachedir">$message_cachedir</a> must point to a
-directory. There, mutt will create a hierarchy of subdirectories
-named like: <code class="literal">proto:user@hostname</code> where
-<code class="literal">proto</code> is either “<span class="quote">pop</span>” or “<span class="quote">imap.</span>” Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-</p><p>
-All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maint-cache"></a>7.3. Maintenance</h3></div></div></div><p>
-Mutt does not (yet) support maintenance features for header cache
-database files so that files have to be removed in case they grow too
-big. It depends on the database library used for header caching whether
-disk space freed by removing messages is re-used.
-</p><p>
-For body caches, mutt can keep the local cache in sync with the
-remote mailbox if the
-<a class="link" href="#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a>
-variable is set. Cleaning means to remove messages from the cache which
-are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
-delete messages (Mutt itself removes deleted messages from the cache
-when syncing a mailbox). As cleaning can take a noticeable amount of time,
-it should not be set in general but only occasionally.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exact-address"></a>8. Exact address generation</h2></div></div></div><p>
-Mutt supports the “<span class="quote">Name <user@host></span>” address syntax for reading and
-writing messages, the older “<span class="quote">user@host (Name)</span>” syntax is only supported when
-reading messages. The <span class="emphasis"><em>--enable-exact-address</em></span>
-switch can be given to configure to build it with write-support
-for the latter syntax. <code class="literal">EXACT_ADDRESS</code> in the output of
-<code class="literal">mutt -v</code> indicates whether it's supported.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="tuning"></a>Chapter 7. Performance tuning</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="#tuning-search">3. Searching and limiting</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-mailboxes"></a>1. Reading and writing mailboxes</h2></div></div></div><p>
-Mutt's performance when reading mailboxes can be improved in two ways:
-</p><div class="orderedlist"><ol type="1"><li><p>
-For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
-performance can be greatly improved using
-<a class="link" href="#header-caching" title="7.1. Header caching">header caching</a>.
-Using a single database per folder may further increase
-performance.
-</p></li><li><p>
-Mutt provides the <a class="link" href="#read-inc" title="3.235. read_inc">$read_inc</a>
-and <a class="link" href="#write-inc" title="3.305. write_inc">$write_inc</a>
-variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
-time on updating the progress counter than it spends on
-actually reading/writing folders.
-</p><p>
-For example, when opening a maildir folder with a few
-thousand messages, the default value for
-<a class="link" href="#read-inc" title="3.235. read_inc">$read_inc</a>
-may be too low. It can be tuned on on a folder-basis using
-<a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hooks</a>:
-</p><pre class="screen">
-# use very high $read_inc to speed up reading hcache'd maildirs
-folder-hook . 'set read_inc=1000'
-# use lower value for reading slower remote IMAP folders
-folder-hook ^imap 'set read_inc=100'
-# use even lower value for reading even slower remote POP folders
-folder-hook ^pop 'set read_inc=1'</pre></li></ol></div><p>These settings work on a per-message basis. However, as messages may
-greatly differ in size and certain operations are much faster than others,
-even per-folder settings of the increment variables may not be
-desirable as they produce either too few or too much progress updates.
-Thus, Mutt allows to limit the number of progress updates per second it'll
-actually send to the terminal using the
-<a class="link" href="#time-inc" title="3.286. time_inc">$time_inc</a> variable.</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-messages"></a>2. Reading messages from remote folders</h2></div></div></div><p>
-Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
-limited number of recently viewed messages (usually 10) per
-session (so that it will be gone for the next session.)
-</p><p>
-To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
-<a class="link" href="#body-caching" title="7.2. Body caching">body caching</a> for details.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-search"></a>3. Searching and limiting</h2></div></div></div><p>
-When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
-searches. For regular expressions, patterns are prefixed with
-“<span class="quote">˜</span>” and with “<span class="quote">=</span>” for string searches.
-</p><p>
-Even though a regular expression search is fast, it's several times
-slower than a pure string search which is noticeable especially on large
-folders. As a consequence, a string search should be used instead of a
-regular expression search if the user already knows enough about the
-search pattern.
-</p><p>
-For example, when limiting a large folder to all messages sent to or by
-an author, it's much faster to search for the initial part of an e-mail
-address via <code class="literal">=Luser@</code> instead of
-<code class="literal">˜Luser@</code>. This is especially true for searching
-message bodies since a larger amount of input has to be searched.
-</p><p>
-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
-</p></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="reference"></a>Chapter 8. Reference</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="#pgp-use-gpg-agent">3.150. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="#crypt-verify-sig">3.151. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="#smime-is-default">3.152. smime_is_default</a></span></dt><dt><span class="sect2"><a href="#smime-ask-cert-label">3.153. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-use-default-key">3.154. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="#pgp-entry-format">3.155. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="#pgp-good-sign">3.156. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="#pgp-check-exit">3.157. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="#pgp-long-ids">3.158. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="#pgp-retainable-sigs">3.159. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="#pgp-autoinline">3.160. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="#pgp-replyinline">3.161. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="#pgp-show-unusable">3.162. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-as">3.163. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="#pgp-strict-enc">3.164. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="#pgp-timeout">3.165. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="#pgp-sort-keys">3.166. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-auto">3.167. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="#pgp-auto-decode">3.168. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-filename">3.169. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="#pgp-mime-signature-description">3.170. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="#pgp-decode-command">3.171. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="#pgp-getkeys-command">3.172. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-command">3.173. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="#pgp-decrypt-command">3.174. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#pgp-clearsign-command">3.175. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-sign-command">3.176. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-sign-command">3.177. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="#pgp-encrypt-only-command">3.178. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="#pgp-import-command">3.179. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="#pgp-export-command">3.180. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="#pgp-verify-key-command">3.181. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-secring-command">3.182. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="#pgp-list-pubring-command">3.183. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="#forward-decrypt">3.184. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="#smime-timeout">3.185. smime_timeout</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-with">3.186. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="#smime-keys">3.187. smime_keys</a></span></dt><dt><span class="sect2"><a href="#smime-ca-location">3.188. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="#smime-certificates">3.189. smime_certificates</a></span></dt><dt><span class="sect2"><a href="#smime-decrypt-command">3.190. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-command">3.191. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="#smime-verify-opaque-command">3.192. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-command">3.193. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="#smime-sign-opaque-command">3.194. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="#smime-encrypt-command">3.195. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="#smime-pk7out-command">3.196. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-command">3.197. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-signer-cert-command">3.198. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-import-cert-command">3.199. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="#smime-get-cert-email-command">3.200. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="#smime-default-key">3.201. smime_default_key</a></span></dt><dt><span class="sect2"><a href="#ssl-client-cert">3.202. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="#ssl-force-tls">3.203. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="#ssl-starttls">3.204. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="#certificate-file">3.205. certificate_file</a></span></dt><dt><span class="sect2"><a href="#ssl-use-sslv3">3.206. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="#ssl-use-tlsv1">3.207. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="#ssl-min-dh-prime-bits">3.208. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="#ssl-ca-certificates-file">3.209. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="#pipe-split">3.210. pipe_split</a></span></dt><dt><span class="sect2"><a href="#pipe-decode">3.211. pipe_decode</a></span></dt><dt><span class="sect2"><a href="#pipe-sep">3.212. pipe_sep</a></span></dt><dt><span class="sect2"><a href="#pop-authenticators">3.213. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="#pop-auth-try-all">3.214. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="#pop-checkinterval">3.215. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="#pop-delete">3.216. pop_delete</a></span></dt><dt><span class="sect2"><a href="#pop-host">3.217. pop_host</a></span></dt><dt><span class="sect2"><a href="#pop-last">3.218. pop_last</a></span></dt><dt><span class="sect2"><a href="#pop-reconnect">3.219. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="#pop-user">3.220. pop_user</a></span></dt><dt><span class="sect2"><a href="#pop-pass">3.221. pop_pass</a></span></dt><dt><span class="sect2"><a href="#post-indent-string">3.222. post_indent_string</a></span></dt><dt><span class="sect2"><a href="#postpone">3.223. postpone</a></span></dt><dt><span class="sect2"><a href="#postponed">3.224. postponed</a></span></dt><dt><span class="sect2"><a href="#preconnect">3.225. preconnect</a></span></dt><dt><span class="sect2"><a href="#print">3.226. print</a></span></dt><dt><span class="sect2"><a href="#print-command">3.227. print_command</a></span></dt><dt><span class="sect2"><a href="#print-decode">3.228. print_decode</a></span></dt><dt><span class="sect2"><a href="#print-split">3.229. print_split</a></span></dt><dt><span class="sect2"><a href="#prompt-after">3.230. prompt_after</a></span></dt><dt><span class="sect2"><a href="#query-command">3.231. query_command</a></span></dt><dt><span class="sect2"><a href="#query-format">3.232. query_format</a></span></dt><dt><span class="sect2"><a href="#quit">3.233. quit</a></span></dt><dt><span class="sect2"><a href="#quote-regexp">3.234. quote_regexp</a></span></dt><dt><span class="sect2"><a href="#read-inc">3.235. read_inc</a></span></dt><dt><span class="sect2"><a href="#read-only">3.236. read_only</a></span></dt><dt><span class="sect2"><a href="#realname">3.237. realname</a></span></dt><dt><span class="sect2"><a href="#recall">3.238. recall</a></span></dt><dt><span class="sect2"><a href="#record">3.239. record</a></span></dt><dt><span class="sect2"><a href="#reply-regexp">3.240. reply_regexp</a></span></dt><dt><span class="sect2"><a href="#reply-self">3.241. reply_self</a></span></dt><dt><span class="sect2"><a href="#reply-to">3.242. reply_to</a></span></dt><dt><span class="sect2"><a href="#resolve">3.243. resolve</a></span></dt><dt><span class="sect2"><a href="#reverse-alias">3.244. reverse_alias</a></span></dt><dt><span class="sect2"><a href="#reverse-name">3.245. reverse_name</a></span></dt><dt><span class="sect2"><a href="#reverse-realname">3.246. reverse_realname</a></span></dt><dt><span class="sect2"><a href="#rfc2047-parameters">3.247. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="#save-address">3.248. save_address</a></span></dt><dt><span class="sect2"><a href="#save-empty">3.249. save_empty</a></span></dt><dt><span class="sect2"><a href="#save-history">3.250. save_history</a></span></dt><dt><span class="sect2"><a href="#save-name">3.251. save_name</a></span></dt><dt><span class="sect2"><a href="#score">3.252. score</a></span></dt><dt><span class="sect2"><a href="#score-threshold-delete">3.253. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="#score-threshold-flag">3.254. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="#score-threshold-read">3.255. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="#send-charset">3.256. send_charset</a></span></dt><dt><span class="sect2"><a href="#sendmail">3.257. sendmail</a></span></dt><dt><span class="sect2"><a href="#sendmail-wait">3.258. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="#shell">3.259. shell</a></span></dt><dt><span class="sect2"><a href="#sig-dashes">3.260. sig_dashes</a></span></dt><dt><span class="sect2"><a href="#sig-on-top">3.261. sig_on_top</a></span></dt><dt><span class="sect2"><a href="#signature">3.262. signature</a></span></dt><dt><span class="sect2"><a href="#simple-search">3.263. simple_search</a></span></dt><dt><span class="sect2"><a href="#smart-wrap">3.264. smart_wrap</a></span></dt><dt><span class="sect2"><a href="#smileys">3.265. smileys</a></span></dt><dt><span class="sect2"><a href="#sleep-time">3.266. sleep_time</a></span></dt><dt><span class="sect2"><a href="#smtp-authenticators">3.267. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="#smtp-pass">3.268. smtp_pass</a></span></dt><dt><span class="sect2"><a href="#smtp-url">3.269. smtp_url</a></span></dt><dt><span class="sect2"><a href="#sort">3.270. sort</a></span></dt><dt><span class="sect2"><a href="#sort-alias">3.271. sort_alias</a></span></dt><dt><span class="sect2"><a href="#sort-aux">3.272. sort_aux</a></span></dt><dt><span class="sect2"><a href="#sort-browser">3.273. sort_browser</a></span></dt><dt><span class="sect2"><a href="#sort-re">3.274. sort_re</a></span></dt><dt><span class="sect2"><a href="#spam-separator">3.275. spam_separator</a></span></dt><dt><span class="sect2"><a href="#spoolfile">3.276. spoolfile</a></span></dt><dt><span class="sect2"><a href="#status-chars">3.277. status_chars</a></span></dt><dt><span class="sect2"><a href="#status-format">3.278. status_format</a></span></dt><dt><span class="sect2"><a href="#status-on-top">3.279. status_on_top</a></span></dt><dt><span class="sect2"><a href="#strict-threads">3.280. strict_threads</a></span></dt><dt><span class="sect2"><a href="#suspend">3.281. suspend</a></span></dt><dt><span class="sect2"><a href="#text-flowed">3.282. text_flowed</a></span></dt><dt><span class="sect2"><a href="#thread-received">3.283. thread_received</a></span></dt><dt><span class="sect2"><a href="#thorough-search">3.284. thorough_search</a></span></dt><dt><span class="sect2"><a href="#tilde">3.285. tilde</a></span></dt><dt><span class="sect2"><a href="#time-inc">3.286. time_inc</a></span></dt><dt><span class="sect2"><a href="#timeout">3.287. timeout</a></span></dt><dt><span class="sect2"><a href="#tmpdir">3.288. tmpdir</a></span></dt><dt><span class="sect2"><a href="#to-chars">3.289. to_chars</a></span></dt><dt><span class="sect2"><a href="#trash">3.290. trash</a></span></dt><dt><span class="sect2"><a href="#tunnel">3.291. tunnel</a></span></dt><dt><span class="sect2"><a href="#use-8bitmime">3.292. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="#use-domain">3.293. use_domain</a></span></dt><dt><span class="sect2"><a href="#use-envelope-from">3.294. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="#use-from">3.295. use_from</a></span></dt><dt><span class="sect2"><a href="#use-idn">3.296. use_idn</a></span></dt><dt><span class="sect2"><a href="#use-ipv6">3.297. use_ipv6</a></span></dt><dt><span class="sect2"><a href="#user-agent">3.298. user_agent</a></span></dt><dt><span class="sect2"><a href="#visual">3.299. visual</a></span></dt><dt><span class="sect2"><a href="#wait-key">3.300. wait_key</a></span></dt><dt><span class="sect2"><a href="#weed">3.301. weed</a></span></dt><dt><span class="sect2"><a href="#wrap">3.302. wrap</a></span></dt><dt><span class="sect2"><a href="#wrap-search">3.303. wrap_search</a></span></dt><dt><span class="sect2"><a href="#wrapmargin">3.304. wrapmargin</a></span></dt><dt><span class="sect2"><a href="#write-inc">3.305. write_inc</a></span></dt><dt><span class="sect2"><a href="#write-bcc">3.306. write_bcc</a></span></dt><dt><span class="sect2"><a href="#xterm-icon">3.307. xterm_icon</a></span></dt><dt><span class="sect2"><a href="#xterm-set-titles">3.308. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="#xterm-title">3.309. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commandline"></a>1. Command line options</h2></div></div></div><p>
-Running <code class="literal">mutt</code> with no arguments will make Mutt attempt to read your spool
-mailbox. However, it is possible to read other mailboxes and
-to send messages from the command line as well.
-</p><div class="table"><a id="tab-commandline-options"></a><p class="title"><b>Table 8.1. Command line options</b></p><div class="table-contents"><table summary="Command line options" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td>-A</td><td>expand an alias</td></tr><tr><td>-a</td><td>attach a file to a message</td></tr><tr><td>-b</td><td>specify a blind carbon-copy (BCC) address</td></tr><tr><td>-c</td><td>specify a carbon-copy (Cc) address</td></tr><tr><td>-D</td><td>print the value of all mutt variables to stdout</td></tr><tr><td>-e</td><td>specify a config command to be run after initialization files are read</td></tr><tr><td>-f</td><td>specify a mailbox to load</td></tr><tr><td>-F</td><td>specify an alternate file to read initialization commands</td></tr><tr><td>-h</td><td>print help on command line options</td></tr><tr><td>-H</td><td>specify a draft file from which to read a header and body</td></tr><tr><td>-i</td><td>specify a file to include in a message composition</td></tr><tr><td>-m</td><td>specify a default mailbox type</td></tr><tr><td>-n</td><td>do not read the system Muttrc</td></tr><tr><td>-p</td><td>recall a postponed message</td></tr><tr><td>-Q</td><td>query a configuration variable</td></tr><tr><td>-R</td><td>open mailbox in read-only mode</td></tr><tr><td>-s</td><td>specify a subject (enclose in quotes if it contains spaces)</td></tr><tr><td>-v</td><td>show version number and compile-time definitions</td></tr><tr><td>-x</td><td>simulate the mailx(1) compose mode</td></tr><tr><td>-y</td><td>show a menu containing the files specified by the mailboxes command</td></tr><tr><td>-z</td><td>exit immediately if there are no messages in the mailbox</td></tr><tr><td>-Z</td><td>open the first folder with new message,exit immediately if none</td></tr></tbody></table></div></div><br class="table-break" /><p>
-To read messages in a mailbox
-</p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-nz</code>] [<code class="option">-F</code>
-<em class="replaceable"><code>muttrc</code></em>
-] [<code class="option">-m</code>
-<em class="replaceable"><code>type</code></em>
-] [<code class="option">-f</code>
-<em class="replaceable"><code>mailbox</code></em>
-]</p></div><p>
-To compose a new message
-</p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-n</code>] [<code class="option">-F</code>
-<em class="replaceable"><code>muttrc</code></em>
-] [<code class="option">-c</code>
-<em class="replaceable"><code>address</code></em>
-] [<code class="option">-i</code>
-<em class="replaceable"><code>filename</code></em>
-] [<code class="option">-s</code>
-<em class="replaceable"><code>subject</code></em>
-] [
-<code class="option">-a</code>
-<em class="replaceable"><code>file</code></em>
- [...]
---
-]
-<em class="replaceable"><code>address</code></em>
-... </p></div><p>
-Mutt also supports a “<span class="quote">batch</span>” mode to send prepared messages. Simply redirect
-input from the file you wish to send. For example,
-</p><p>
-<code class="literal">mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat</code>
-</p><p>
-This command will send a message to “<span class="quote">professor@bigschool.edu</span>” with a subject
-of “<span class="quote">data set for run #2</span>”. In the body of the message will be the contents
-of the file “<span class="quote">˜/run2.dat</span>”.
-</p><p>
-All files passed with -a <span class="emphasis"><em>file</em></span> will be attached as a MIME
-part to the message. To attach several files, use “<span class="quote">--</span>” to separate files and
-recipient addresses: <code class="literal">mutt -a *.png -- some@one.org</code>
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commands"></a>2. Configuration Commands</h2></div></div></div><p>
-The following are the commands understood by mutt.
-</p><div class="itemizedlist"><ul type="disc"><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#account-hook" title="6. Managing multiple accounts">account-hook</a></code>
-<em class="replaceable"><code>pattern</code></em>
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alias" title="4. Defining/Using aliases">alias</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>address</code></em>
- [
-<em class="replaceable"><code>address</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alias" title="4. Defining/Using aliases">unalias</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>key</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternates" title="11. Alternative addresses">unalternates</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternative-order" title="5. MIME Multipart/Alternative">alternative-order</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#alternative-order" title="5. MIME Multipart/Alternative">unalternative-order</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#auto-view" title="4. MIME Autoview">auto-view</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#auto-view" title="4. MIME Autoview">unauto-view</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#bind" title="5. Changing the default key bindings">bind</a></code>
-<em class="replaceable"><code>map</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>function</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#charset-hook" title="6. Defining aliases for character sets">charset-hook</a></code>
-<em class="replaceable"><code>alias</code></em>
-
-<em class="replaceable"><code>charset</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#charset-hook" title="6. Defining aliases for character sets">iconv-hook</a></code>
-<em class="replaceable"><code>charset</code></em>
-
-<em class="replaceable"><code>local-charset</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">color</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#color" title="9. Using color and mono video attributes">uncolor</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>pattern</code></em>
-... </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#exec" title="23. Executing functions">exec</a></code>
-<em class="replaceable"><code>function</code></em>
- [
-<em class="replaceable"><code>function</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a></code>
-<em class="replaceable"><code>[!]regexp</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#addrgroup" title="3. Address groups">group</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#addrgroup" title="3. Address groups">ungroup</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#hdr-order">hdr_order</a></code>
-<em class="replaceable"><code>header</code></em>
- [
-<em class="replaceable"><code>header</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#hdr-order">unhdr_order</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>header</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#ignore" title="10. Message header display">ignore</a></code>
-<em class="replaceable"><code>pattern</code></em>
- [
-<em class="replaceable"><code>pattern</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#ignore" title="10. Message header display">unignore</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#lists" title="12. Mailing lists">lists</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#lists" title="12. Mailing lists">unlists</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#macro" title="8. Keyboard macros">macro</a></code>
-<em class="replaceable"><code>menu</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>sequence</code></em>
- [
-<em class="replaceable"><code>description</code></em>
-]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></code>
-<em class="replaceable"><code>mailbox</code></em>
- [
-<em class="replaceable"><code>mailbox</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">unmailboxes</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mailbox</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mime-lookup" title="7. MIME Lookup">mime-lookup</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mime-lookup" title="7. MIME Lookup">unmime-lookup</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>attribute</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">mono</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#mono">unmono</a></code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></code>
-<em class="replaceable"><code>string</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#my-hdr" title="15. User defined headers">unmy_hdr</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>field</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#crypt-hook" title="21. Choosing the cryptographic key of the recipient">crypt-hook</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>keyid</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#push" title="22. Adding key sequences to the keyboard buffer">push</a></code>
-<em class="replaceable"><code>string</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">reset</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#score" title="3.252. score">score</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>value</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#score" title="3.252. score">unscore</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#reply-hook">reply-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#send2-hook">send2-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">set</a></code> {
-[ <code class="option">no</code> | <code class="option">inv</code> ]
-<em class="replaceable"><code>variable</code></em>
- |
-<em class="replaceable"><code>variable=value</code></em>
- } [...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">unset</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#source" title="27. Reading initialization commands from another file">source</a></code>
-<em class="replaceable"><code>filename</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#spam" title="25. Spam detection">spam</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>format</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#spam" title="25. Spam detection">nospam</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
- }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#subscribe">subscribe</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#subscribe">unsubscribe</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#set" title="26. Setting and Querying Variables">toggle</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="#unhook" title="29. Removing hooks">unhook</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>hook-type</code></em>
- }</p></div></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="variables"></a>3. Configuration variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-nosubject"></a>3.1. abort_nosubject</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-If set to <span class="emphasis"><em>yes</em></span>, when composing messages and no subject is given
-at the subject prompt, composition will be aborted. If set to
-<span class="emphasis"><em>no</em></span>, composing messages with no subject given at the subject
-prompt will never be aborted.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-unmodified"></a>3.2. abort_unmodified</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If set to <span class="emphasis"><em>yes</em></span>, composition will automatically abort after
-editing the message body if no changes are made to the file (this
-check only happens after the <span class="emphasis"><em>first</em></span> edit of the file). When set
-to <span class="emphasis"><em>no</em></span>, composition will never be aborted.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-file"></a>3.3. alias_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.muttrc</code></span>”</p></div><p>
-The default file in which to save aliases created by the
-<code class="literal"><a class="link" href="#create-alias"><create-alias></a></code> function. Entries added to this file are
-encoded in the character set specified by <a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a> if it
-is <span class="emphasis"><em>set</em></span> or the current character set otherwise.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> Mutt will not automatically source this file; you must
-explicitly use the “<span class="quote"><a class="link" href="#source" title="27. Reading initialization commands from another file">source</a></span>” command for it to be executed in case
-this option points to a dedicated alias file.
-</p><p>
-The default for this option is the currently used muttrc file, or
-“<span class="quote">˜/.muttrc</span>” if no user muttrc was found.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-format"></a>3.4. alias_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %2f %t %-10a %r</code></span>”</p></div><p>
-Specifies the format of the data displayed for the “<span class="quote"><a class="link" href="#alias" title="4. Defining/Using aliases">alias</a></span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are available:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>alias name
-</p></dd><dt><span class="term">%f </span></dt><dd><p>flags - currently, a “<span class="quote">d</span>” for an alias marked for deletion
-</p></dd><dt><span class="term">%n </span></dt><dd><p>index number
-</p></dd><dt><span class="term">%r </span></dt><dd><p>address which alias expands to
-</p></dd><dt><span class="term">%t </span></dt><dd><p>character which indicates if the alias is tagged for inclusion
-</p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-8bit"></a>3.5. allow_8bit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether 8-bit data is converted to 7-bit using either Quoted-
-Printable or Base64 encoding when sending mail.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-ansi"></a>3.6. allow_ansi</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <span class="emphasis"><em>set</em></span>,
-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
-
-</p><pre class="screen">
-[-- PGP output follows ...
-
-</pre><p>
-and give it the same color as your attachment color (see also
-<a class="link" href="#crypt-timestamp" title="3.149. crypt_timestamp">$crypt_timestamp</a>).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="arrow-cursor"></a>3.7. arrow_cursor</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, an arrow (“<span class="quote">-></span>”) 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ascii-chars"></a>3.8. ascii_chars</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will use plain ASCII characters when displaying thread
-and attachment trees, instead of the default <span class="emphasis"><em>ACS</em></span> characters.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askbcc"></a>3.9. askbcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
-before editing an outgoing message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askcc"></a>3.10. askcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for carbon-copy (Cc) recipients before
-editing the body of an outgoing message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="assumed-charset"></a>3.11. assumed_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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 “<span class="quote">us-ascii</span>”.
-</p><p>
-For example, Japanese users might prefer this:
-
-</p><pre class="screen">
-set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</pre><p>
-However, only the first content is valid for the message body.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-charset"></a>3.12. attach_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable is a colon-separated list of character encoding
-schemes for text file attachments. Mutt uses this setting to guess
-which encoding files being attached are encoded in to convert them to
-a proper character set given in <a class="link" href="#send-charset" title="3.256. send_charset">$send_charset</a>.
-</p><p>
-If <span class="emphasis"><em>unset</em></span>, the value of <a class="link" href="#charset" title="3.25. charset">$charset</a> will be used instead.
-For example, the following configuration would work for Japanese
-text handling:
-
-</p><pre class="screen">
-set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</pre><p>
-Note: for Japanese users, “<span class="quote">iso-2022-*</span>” must be put at the head
-of the value as shown above if included.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-format"></a>3.13. attach_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] </code></span>”</p></div><p>
-This variable describes the format of the “<span class="quote">attachment</span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are understood:
-
-</p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>charset
-</p></dd><dt><span class="term">%c </span></dt><dd><p>requires charset conversion (“<span class="quote">n</span>” or “<span class="quote">c</span>”)
-</p></dd><dt><span class="term">%D </span></dt><dd><p>deleted flag
-</p></dd><dt><span class="term">%d </span></dt><dd><p>description
-</p></dd><dt><span class="term">%e </span></dt><dd><p>MIME content-transfer-encoding
-</p></dd><dt><span class="term">%f </span></dt><dd><p>filename
-</p></dd><dt><span class="term">%I </span></dt><dd><p>disposition (“<span class="quote">I</span>” for inline, “<span class="quote">A</span>” for attachment)
-</p></dd><dt><span class="term">%m </span></dt><dd><p>major MIME type
-</p></dd><dt><span class="term">%M </span></dt><dd><p>MIME subtype
-</p></dd><dt><span class="term">%n </span></dt><dd><p>attachment number
-</p></dd><dt><span class="term">%Q </span></dt><dd><p>“<span class="quote">Q</span>”, if MIME part qualifies for attachment counting
-</p></dd><dt><span class="term">%s </span></dt><dd><p>size
-</p></dd><dt><span class="term">%t </span></dt><dd><p>tagged flag
-</p></dd><dt><span class="term">%T </span></dt><dd><p>graphic tree characters
-</p></dd><dt><span class="term">%u </span></dt><dd><p>unlink (=to delete) flag
-</p></dd><dt><span class="term">%X </span></dt><dd><p>number of qualifying MIME parts in this part and its children
-(please see the “<span class="quote"><a class="link" href="#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-sep"></a>3.14. attach_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
-The separator to add between attachments when operating (saving,
-printing, piping, etc) on a list of tagged attachments.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-split"></a>3.15. attach_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this variable is <span class="emphasis"><em>unset</em></span>, when operating (saving, printing, piping,
-etc) on a list of tagged attachments, Mutt will concatenate the
-attachments and will operate on them as a single attachment. The
-<a class="link" href="#attach-sep" title="3.14. attach_sep">$attach_sep</a> separator is added after each attachment. When <span class="emphasis"><em>set</em></span>,
-Mutt will operate on the attachments one by one.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attribution"></a>3.16. attribution</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">On %d, %n wrote:</code></span>”</p></div><p>
-This is the string that will precede a message which has been included
-in a reply. For a full listing of defined <code class="literal">printf(3)</code>-like sequences see
-the section on <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="autoedit"></a>3.17. autoedit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span> along with <a class="link" href="#edit-headers" title="3.50. edit_headers">$edit_headers</a>, Mutt will skip the initial
-send-menu (prompting for subject and recipients) 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.
-</p><p>
-Also see <a class="link" href="#fast-reply" title="3.55. fast_reply">$fast_reply</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="auto-tag"></a>3.18. auto_tag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, functions in the <span class="emphasis"><em>index</em></span> menu which affect a message
-will be applied to all tagged messages (if there are any). When
-unset, you must first use the <code class="literal"><tag-prefix></code> function (bound to “<span class="quote">;</span>”
-by default) to make the next function apply to all tagged messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep"></a>3.19. beep</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep when an error occurs.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep-new"></a>3.20. beep_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep whenever it prints a message
-notifying you of new mail. This is independent of the setting of the
-<a class="link" href="#beep" title="3.19. beep">$beep</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce"></a>3.21. bounce</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether you will be asked to confirm bouncing messages.
-If set to <span class="emphasis"><em>yes</em></span> you don't get asked if you want to bounce a
-message. Setting this variable to <span class="emphasis"><em>no</em></span> is not generally useful,
-and thus not recommended, because you are unable to bounce messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce-delivered"></a>3.22. bounce_delivered</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will include Delivered-To headers when
-bouncing messages. Postfix users may wish to <span class="emphasis"><em>unset</em></span> this variable.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is unset by default in
-/etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="braille-friendly"></a>3.23. braille_friendly</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will place the cursor at the beginning
-of the current line in menus, even when the <a class="link" href="#arrow-cursor" title="3.7. arrow_cursor">$arrow_cursor</a> variable
-is <span class="emphasis"><em>unset</em></span>, making it easier for blind persons using Braille displays to
-follow these menus. The option is <span class="emphasis"><em>unset</em></span> by default because many
-visual terminals don't permit making the cursor invisible.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-mbox-size"></a>3.24. check_mbox_size</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
-</p><p>
-This variable is <span class="emphasis"><em>unset</em></span> by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
-</p><p>
-Note that enabling this variable should happen before any “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="charset"></a>3.25. charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Character set your terminal uses to display and enter textual data.
-It is also the fallback for <a class="link" href="#send-charset" title="3.256. send_charset">$send_charset</a>.
-</p><p>
-Upon startup Mutt tries to derive this value from environment variables
-such as <code class="literal">$LC_CTYPE</code> or <code class="literal">$LANG</code>.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> It should only be set in case Mutt isn't abled to determine the
-character set used correctly.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-new"></a>3.26. check_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-<span class="bold"><strong>Note:</strong></span> this option only affects <span class="emphasis"><em>maildir</em></span> and <span class="emphasis"><em>MH</em></span> style
-mailboxes.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt 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
-this variable is <span class="emphasis"><em>unset</em></span>, no check for new mail is performed
-while the mailbox is open.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="collapse-unread"></a>3.27. collapse_unread</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, Mutt will not collapse a thread if it contains any
-unread messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="uncollapse-jump"></a>3.28. uncollapse_jump</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will jump to the next unread message, if any,
-when the current thread is <span class="emphasis"><em>un</em></span>collapsed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-format"></a>3.29. compose_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-</code></span>”</p></div><p>
-Controls the format of the status line displayed in the “<span class="quote">compose</span>”
-menu. This string is similar to <a class="link" href="#status-format" title="3.278. status_format">$status_format</a>, but has its own
-set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>total number of attachments
-</p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
-</p></dd><dt><span class="term">%l </span></dt><dd><p>approximate size (in bytes) of the current message
-</p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
-</p></dd></dl></div><p>
-See the text describing the <a class="link" href="#status-format" title="3.278. status_format">$status_format</a> option for more
-information on how to set <a class="link" href="#compose-format" title="3.29. compose_format">$compose_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="config-charset"></a>3.30. config_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-When defined, Mutt will recode commands in rc files from this
-encoding to the current character set as specified by <a class="link" href="#charset" title="3.25. charset">$charset</a>
-and aliases written to <a class="link" href="#alias-file" title="3.3. alias_file">$alias_file</a> from the current character set.
-</p><p>
-Please note that if setting <a class="link" href="#charset" title="3.25. charset">$charset</a> it must be done before
-setting <a class="link" href="#config-charset" title="3.30. config_charset">$config_charset</a>.
-</p><p>
-Recoding should be avoided as it may render unconvertable
-characters as question marks which can lead to undesired
-side effects (for example in regular expressions).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmappend"></a>3.31. confirmappend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when appending messages to
-an existing mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmcreate"></a>3.32. confirmcreate</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when saving messages to a
-mailbox which does not yet exist before creating it.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="connect-timeout"></a>3.33. connect_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 30</p></div><p>
-Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-many seconds if the connection is not able to be established. A negative
-value causes Mutt to wait indefinitely for the connection attempt to succeed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="content-type"></a>3.34. content_type</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">text/plain</code></span>”</p></div><p>
-Sets the default Content-Type for the body of newly composed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="copy"></a>3.35. copy</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether or not copies of your outgoing messages
-will be saved for later references. Also see <a class="link" href="#record" title="3.239. record">$record</a>,
-<a class="link" href="#save-name" title="3.251. save_name">$save_name</a>, <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> and “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-gpgme"></a>3.36. crypt_use_gpgme</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls the use of the GPGME-enabled crypto backends.
-If it is <span class="emphasis"><em>set</em></span> and Mutt was built with gpgme support, the gpgme code for
-S/MIME and PGP will be used instead of the classic code. Note that
-you need to set this option in .muttrc; it won't have any effect when
-used interactively.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-pka"></a>3.37. crypt_use_pka</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether mutt uses PKA
-(see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
-verification (only supported by the GPGME backend).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autopgp"></a>3.38. crypt_autopgp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages. See also <a class="link" href="#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
-<a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
-<a class="link" href="#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="#smime-is-default" title="3.152. smime_is_default">$smime_is_default</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosmime"></a>3.39. crypt_autosmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also <a class="link" href="#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
-<a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
-<a class="link" href="#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="#smime-is-default" title="3.152. smime_is_default">$smime_is_default</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-format"></a>3.40. date_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">!%a, %b %d, %Y at %I:%M:%S%p %Z</code></span>”</p></div><p>
-This variable controls the format of the date printed by the “<span class="quote">%d</span>”
-sequence in <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>. This is passed to the <code class="literal">strftime(3)</code>
-function to process the date, see the man page for the proper syntax.
-</p><p>
-Unless the first character in the string is a bang (“<span class="quote">!</span>”), the month
-and week day names are expanded according to the locale specified in
-the variable <a class="link" href="#locale" title="3.104. locale">$locale</a>. 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 <span class="emphasis"><em>C</em></span> locale (that is in US
-English).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="default-hook"></a>3.41. default_hook</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜f %s !˜P | (˜P ˜C %s)</code></span>”</p></div><p>
-This variable controls how “<span class="quote"><a class="link" href="#message-hook" title="20. Change settings before formatting a message">message-hook</a></span>”, “<span class="quote"><a class="link" href="#reply-hook">reply-hook</a></span>”, “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”,
-“<span class="quote"><a class="link" href="#send2-hook">send2-hook</a></span>”, “<span class="quote"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, and “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” 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.
-</p><p>
-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
-“<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”) and is to or cc'ed to a user matching the given
-regular expression.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete"></a>3.42. delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not messages are really deleted when closing or
-synchronizing a mailbox. If set to <span class="emphasis"><em>yes</em></span>, messages marked for
-deleting will automatically be purged without prompting. If set to
-<span class="emphasis"><em>no</em></span>, messages marked for deletion will be kept in the mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete-untag"></a>3.43. delete_untag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this option is <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="digest-collapse"></a>3.44. digest_collapse</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this option is <span class="emphasis"><em>set</em></span>, mutt's received-attachments menu will not show the subparts of
-individual messages in a multipart/digest. To see these subparts, press “<span class="quote">v</span>” on that menu.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="display-filter"></a>3.45. display_filter</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-When set, specifies a command used to filter messages. When a message
-is viewed it is passed as standard input to <a class="link" href="#display-filter" title="3.45. display_filter">$display_filter</a>, and the
-filtered message is read from the standard output.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dotlock-program"></a>3.46. dotlock_program</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">/usr/bin/mutt_dotlock</code></span>”</p></div><p>
-Contains the path of the <code class="literal">mutt_dotlock(8)</code> binary to be used by
-mutt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-notify"></a>3.47. dsn_notify</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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: <span class="emphasis"><em>never</em></span>, to never request notification,
-<span class="emphasis"><em>failure</em></span>, to request notification on transmission failure,
-<span class="emphasis"><em>delay</em></span>, to be notified of message delays, <span class="emphasis"><em>success</em></span>, to be
-notified of successful transmission.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set dsn_notify="failure,delay"
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> when using <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-N</code> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-return"></a>3.48. dsn_return</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable controls how much of your message is returned in DSN
-messages. It may be set to either <span class="emphasis"><em>hdrs</em></span> to return just the
-message header, or <span class="emphasis"><em>full</em></span> to return the full message.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set dsn_return=hdrs
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> when using <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-R</code> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="duplicate-threads"></a>3.49. duplicate_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether mutt, when <a class="link" href="#sort" title="3.270. sort">$sort</a> is set to <span class="emphasis"><em>threads</em></span>, threads
-messages with the same Message-Id together. If it is <span class="emphasis"><em>set</em></span>, it will indicate
-that it thinks they are duplicates of each other with an equals sign
-in the thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-headers"></a>3.50. edit_headers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option allows you to edit the header of your outgoing messages
-along with the body of your message.
-</p><p>
-<span class="bold"><strong>Note</strong></span> that changes made to the References: and Date: headers are
-ignored for interoperability reasons.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor"></a>3.51. editor</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable specifies which editor is used by mutt.
-It defaults to the value of the <code class="literal">$VISUAL</code>, or <code class="literal">$EDITOR</code>, environment
-variable, or to the string “<span class="quote">/usr/bin/editor</span>” if neither of those are set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="encode-from"></a>3.52. encode_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will quoted-printable encode messages when
-they contain the string “<span class="quote">From </span>” (note the trailing space) in the beginning of a line.
-This is useful to avoid the tampering certain mail delivery and transport
-agents tend to do with messages (in order to prevent tools from
-misinterpreting the line as a mbox message separator).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="envelope-from-address"></a>3.53. envelope_from_address</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
-Default: (empty)</p></div><p>
-Manually sets the <span class="emphasis"><em>envelope</em></span> sender for outgoing messages.
-This value is ignored if <a class="link" href="#use-envelope-from" title="3.294. use_envelope_from">$use_envelope_from</a> is <span class="emphasis"><em>unset</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="escape"></a>3.54. escape</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜</code></span>”</p></div><p>
-Escape character to use for functions in the builtin editor.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fast-reply"></a>3.55. fast_reply</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, 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><p>
-<span class="bold"><strong>Note:</strong></span> this variable has no effect when the <a class="link" href="#autoedit" title="3.17. autoedit">$autoedit</a>
-variable is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-attach"></a>3.56. fcc_attach</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not attachments on outgoing messages
-are saved along with the main body of your message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-clear"></a>3.57. fcc_clear</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, FCCs will be stored unencrypted and
-unsigned, even when the actual message is encrypted and/or
-signed.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder"></a>3.58. folder</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/Mail</code></span>”</p></div><p>
-Specifies the default location of your mailboxes. A “<span class="quote">+</span>” or “<span class="quote">=</span>” 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 <span class="emphasis"><em>before</em></span>
-you use “<span class="quote">+</span>” or “<span class="quote">=</span>” for any other variables since expansion takes place
-when handling the “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder-format"></a>3.59. folder_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f</code></span>”</p></div><p>
-This variable allows you to customize the file browser display to your
-personal taste. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but has
-its own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>current file number
-</p></dd><dt><span class="term">%d </span></dt><dd><p>date/time folder was last modified
-</p></dd><dt><span class="term">%f </span></dt><dd><p>filename
-</p></dd><dt><span class="term">%F </span></dt><dd><p>file permissions
-</p></dd><dt><span class="term">%g </span></dt><dd><p>group name (or numeric gid, if missing)
-</p></dd><dt><span class="term">%l </span></dt><dd><p>number of hard links
-</p></dd><dt><span class="term">%N </span></dt><dd><p>N if folder has new mail, blank otherwise
-</p></dd><dt><span class="term">%s </span></dt><dd><p>size in bytes
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if the file is tagged, blank otherwise
-</p></dd><dt><span class="term">%u </span></dt><dd><p>owner name (or numeric uid, if missing)
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="followup-to"></a>3.60. followup_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether or not the “<span class="quote">Mail-Followup-To:</span>” header field is
-generated when sending mail. When <span class="emphasis"><em>set</em></span>, Mutt will generate this
-field when you are replying to a known mailing list, specified with
-the “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” or “<span class="quote"><a class="link" href="#lists" title="12. Mailing lists">lists</a></span>” commands.
-</p><p>
-This field has two purposes. First, preventing you from
-receiving duplicate copies of replies to messages which you send
-to mailing lists, and second, ensuring that you do get a reply
-separately for any messages sent to known lists to which you are
-not subscribed.
-</p><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="force-name"></a>3.61. force_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable is similar to <a class="link" href="#save-name" title="3.251. save_name">$save_name</a>, except that Mutt 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.
-</p><p>
-Also see the <a class="link" href="#record" title="3.239. record">$record</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decode"></a>3.62. forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
-forwarding a message. The message header is also RFC2047 decoded.
-This variable is only used, if <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>,
-otherwise <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is used instead.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-edit"></a>3.63. forward_edit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-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 “<span class="quote">no</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-format"></a>3.64. forward_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">[%a: %s]</code></span>”</p></div><p>
-This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-quote"></a>3.65. forward_quote</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, forwarded messages included in the main body of the
-message (when <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>) will be quoted using
-<a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="from"></a>3.66. from</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
-Default: (empty)</p></div><p>
-When <span class="emphasis"><em>set</em></span>, this variable contains a default from address. It
-can be overridden using “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>” (including from a “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”) and
-<a class="link" href="#reverse-name" title="3.245. reverse_name">$reverse_name</a>. This variable is ignored if <a class="link" href="#use-from" title="3.295. use_from">$use_from</a> is <span class="emphasis"><em>unset</em></span>.
-</p><p>
-This setting defaults to the contents of the environment variable <code class="literal">$EMAIL</code>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="gecos-mask"></a>3.67. gecos_mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^[^,]*</code></span>”</p></div><p>
-A regular expression used by mutt to parse the GECOS field of a password
-entry when expanding the alias. The default value
-will return the string up to the first “<span class="quote">,</span>” encountered.
-If the GECOS field contains a string like “<span class="quote">lastname, firstname</span>” then you
-should set it to “<span class="quote"><code class="literal">.*</code></span>”.
-</p><p>
-This can be useful if you see the following behavior: you address an e-mail
-to user ID “<span class="quote">stevef</span>” whose full name is “<span class="quote">Steve Franklin</span>”. If mutt expands
-“<span class="quote">stevef</span>” to “<span class="quote">"Franklin" stevef@foo.bar</span>” then you should set the <a class="link" href="#gecos-mask" title="3.67. gecos_mask">$gecos_mask</a> to
-a regular expression that will match the whole name so mutt will expand
-“<span class="quote">Franklin</span>” to “<span class="quote">Franklin, Steve</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hdrs"></a>3.68. hdrs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, the header fields normally added by the “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command are not created. This variable <span class="emphasis"><em>must</em></span> be unset before
-composing a new message or replying in order to take effect. If <span class="emphasis"><em>set</em></span>,
-the user defined header fields are added to every new message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header"></a>3.69. header</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, this variable causes Mutt to include the header
-of the message you are replying to into the edit buffer.
-The <a class="link" href="#weed" title="3.301. weed">$weed</a> setting applies.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="help"></a>3.70. help</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, help lines describing the bindings for the major functions
-provided by each menu are displayed on the first line of the screen.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> 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 is
-running. Since this variable is primarily aimed at new users, neither
-of these should present a major problem.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hidden-host"></a>3.71. hidden_host</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will skip the host name part of <a class="link" href="#hostname" title="3.80. hostname">$hostname</a> variable
-when adding the domain part to addresses. This variable does not
-affect the generation of Message-IDs, and it will not lead to the
-cut-off of first-level domains.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-limited"></a>3.72. hide_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
-by limiting, in the thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-missing"></a>3.73. hide_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages in the
-thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-thread-subject"></a>3.74. hide_thread_subject</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the subject of messages in the thread
-tree that have the same subject as their parent or closest previously
-displayed sibling.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-limited"></a>3.75. hide_top_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
-by limiting, at the top of threads in the thread tree. Note that when
-<a class="link" href="#hide-limited" title="3.72. hide_limited">$hide_limited</a> is <span class="emphasis"><em>set</em></span>, this option will have no effect.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-missing"></a>3.76. hide_top_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages at the
-top of threads in the thread tree. Note that when <a class="link" href="#hide-missing" title="3.73. hide_missing">$hide_missing</a> is
-<span class="emphasis"><em>set</em></span>, this option will have no effect.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history"></a>3.77. history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-This variable controls the size (in number of strings remembered) of
-the string history buffer per category. The buffer is cleared each time the
-variable is set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history-file"></a>3.78. history_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.mutthistory</code></span>”</p></div><p>
-The file in which Mutt will save its history.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="honor-followup-to"></a>3.79. honor_followup_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether or not a Mail-Followup-To header is
-honored when group-replying to a message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hostname"></a>3.80. hostname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the fully-qualified hostname of the system mutt is running on
-containing the host's name and the DNS domain it belongs to. It is used
-as the domain part (after “<span class="quote">@</span>”) for local email addresses as well as
-Message-Id headers.
-</p><p>
-Its value is determined at startup as follows: If the node's name
-as returned by the <code class="literal">uname(3)</code> function contains the hostname and the
-domain, these are used to construct <a class="link" href="#hostname" title="3.80. hostname">$hostname</a>. If there is no
-domain part returned, Mutt will look for a “<span class="quote">domain</span>” or “<span class="quote">search</span>”
-line in <code class="literal">/etc/resolv.conf</code> to determine the domain. Optionally, Mutt
-can be compiled with a fixed domain name in which case a detected
-one is not used.
-</p><p>
-Also see <a class="link" href="#use-domain" title="3.293. use_domain">$use_domain</a> and <a class="link" href="#hidden-host" title="3.71. hidden_host">$hidden_host</a>.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, the default for this variable is obtained
-from /etc/mailname when Mutt starts.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-linear-white-space"></a>3.81. ignore_linear_white_space</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option replaces linear-white-space between encoded-word
-and text to a single space to prevent the display of MIME-encoded
-“<span class="quote">Subject:</span>” field from being divided into multiple lines.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-list-reply-to"></a>3.82. ignore_list_reply_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Affects the behaviour of the <code class="literal"><reply></code> function when replying to
-messages from mailing lists (as defined by the “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” or
-“<span class="quote"><a class="link" href="#lists" title="12. Mailing lists">lists</a></span>” commands). When <span class="emphasis"><em>set</em></span>, if the “<span class="quote">Reply-To:</span>” field is
-set to the same value as the “<span class="quote">To:</span>” field, Mutt assumes that the
-“<span class="quote">Reply-To:</span>” 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 <span class="emphasis"><em>set</em></span>, use the <code class="literal"><a class="link" href="#list-reply"><list-reply></a></code>
-function; <code class="literal"><group-reply></code> will reply to both the sender and the
-list.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authenticators"></a>3.83. imap_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an IMAP server, in the order mutt should
-try them. Authentication methods are either “<span class="quote">login</span>” or the right
-side of an IMAP “<span class="quote">AUTH=xxx</span>” capability string, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>”
-or “<span class="quote">cram-md5</span>”. This option is case-insensitive. If it's
-<span class="emphasis"><em>unset</em></span> (the default) mutt will try all available methods,
-in order from most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set imap_authenticators="gssapi:cram-md5:login"
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> Mutt will only fall back to other authentication methods if
-the previous methods are unavailable. If a method is available but
-authentication fails, mutt will not connect to the IMAP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-check-subscribed"></a>3.84. imap_check_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, 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 just as if you had issued individual “<span class="quote"><a class="link" href="#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
-commands.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-delim-chars"></a>3.85. imap_delim_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">/.</code></span>”</p></div><p>
-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 “<span class="quote">=</span>” shortcut for your <span class="emphasis"><em>folder</em></span> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-headers"></a>3.86. imap_headers</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Mutt requests these header fields in addition to the default headers
-(“<span class="quote">Date:</span>”, “<span class="quote">From:</span>”, “<span class="quote">Subject:</span>”, “<span class="quote">To:</span>”, “<span class="quote">Cc:</span>”, “<span class="quote">Message-Id:</span>”,
-“<span class="quote">References:</span>”, “<span class="quote">Content-Type:</span>”, “<span class="quote">Content-Description:</span>”, “<span class="quote">In-Reply-To:</span>”,
-“<span class="quote">Reply-To:</span>”, “<span class="quote">Lines:</span>”, “<span class="quote">List-Post:</span>”, “<span class="quote">X-Label:</span>”) from IMAP
-servers before displaying the index menu. You may want to add more
-headers for spam detection.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> This is a space separated list, items should be uppercase
-and not contain the colon, e.g. “<span class="quote">X-BOGOSITY X-SPAM-STATUS</span>” for the
-“<span class="quote">X-Bogosity:</span>” and “<span class="quote">X-Spam-Status:</span>” header fields.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-idle"></a>3.87. imap_idle</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will attempt to use the IMAP IDLE extension
-to check for new mail in the current mailbox. Some servers
-(dovecot was the inspiration for this option) react badly
-to mutt's implementation. If your connection seems to freeze
-up periodically, try unsetting this.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-keepalive"></a>3.88. imap_keepalive</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 900</p></div><p>
-This variable specifies the maximum amount of time in seconds that mutt
-will wait before polling open IMAP connections, to prevent the server
-from closing them before mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-list-subscribed"></a>3.89. imap_list_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <code class="literal"><toggle-subscribed></code> function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-login"></a>3.90. imap_login</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Your login name on the IMAP server.
-</p><p>
-This variable defaults to the value of <a class="link" href="#imap-user" title="3.96. imap_user">$imap_user</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pass"></a>3.91. imap_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your IMAP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you invoke the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function
-or try to open an IMAP folder.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-passive"></a>3.92. imap_passive</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not open new IMAP connections to check for new
-mail. Mutt 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 invocation, or if opening the connection
-is slow.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-peek"></a>3.93. imap_peek</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pipeline-depth"></a>3.94. imap_pipeline_depth</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 15</p></div><p>
-Controls the number of IMAP commands that may be queued up before they
-are sent to the server. A deeper pipeline reduces the amount of time
-mutt must wait for the server, and can make IMAP servers feel much
-more responsive. But not all servers correctly handle pipelined commands,
-so if you have problems you might want to try setting this variable to 0.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> Changes to this variable have no effect on open connections.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-servernoise"></a>3.95. imap_servernoise</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-user"></a>3.96. imap_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-The name of the user whose mail you intend to access on the IMAP
-server.
-</p><p>
-This variable defaults to your user name on the local machine.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="implicit-autoview"></a>3.97. implicit_autoview</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If set to “<span class="quote">yes</span>”, mutt will look for a mailcap entry with the
-“<span class="quote"><code class="literal">copiousoutput</code></span>” flag set for <span class="emphasis"><em>every</em></span> MIME attachment it doesn't have
-an internal viewer defined for. If such an entry is found, mutt will
-use the viewer defined in that entry to convert the body part to text
-form.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include"></a>3.98. include</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not a copy of the message(s) you are replying to
-is included in your reply.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include-onlyfirst"></a>3.99. include_onlyfirst</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether or not Mutt includes only the first attachment
-of the message you are replying.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="indent-string"></a>3.100. indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">> </code></span>”</p></div><p>
-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.
-</p><p>
-This option is a format string, please see the description of
-<a class="link" href="#index-format" title="3.101. index_format">$index_format</a> for supported <code class="literal">printf(3)</code>-style sequences.
-</p><p>
-Because for <code class="literal">format=lowed</code> style messages the quoting mechanism
-is strictly defined, this setting is ignored if <a class="link" href="#text-flowed" title="3.282. text_flowed">$text_flowed</a> is
-<span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-format"></a>3.101. index_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s</code></span>”</p></div><p>
-This variable allows you to customize the message index display to
-your personal taste.
-</p><p>
-“<span class="quote">Format strings</span>” are similar to the strings used in the C
-function <code class="literal">printf(3)</code> to format output (see the man page for more details).
-The following sequences are defined in Mutt:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>address of the author
-</p></dd><dt><span class="term">%A </span></dt><dd><p>reply-to address (if present; otherwise: address of author)
-</p></dd><dt><span class="term">%b </span></dt><dd><p>filename of the original message folder (think mailbox)
-</p></dd><dt><span class="term">%B </span></dt><dd><p>the list to which the letter was sent, or else the folder name (%b).
-</p></dd><dt><span class="term">%c </span></dt><dd><p>number of characters (bytes) in the message
-</p></dd><dt><span class="term">%C </span></dt><dd><p>current message number
-</p></dd><dt><span class="term">%d </span></dt><dd><p>date and time of the message in the format specified by
-<a class="link" href="#date-format" title="3.40. date_format">$date_format</a> converted to sender's time zone
-</p></dd><dt><span class="term">%D </span></dt><dd><p>date and time of the message in the format specified by
-<a class="link" href="#date-format" title="3.40. date_format">$date_format</a> converted to the local time zone
-</p></dd><dt><span class="term">%e </span></dt><dd><p>current message number in thread
-</p></dd><dt><span class="term">%E </span></dt><dd><p>number of messages in current thread
-</p></dd><dt><span class="term">%f </span></dt><dd><p>sender (address + real name), either From: or Return-Path:
-</p></dd><dt><span class="term">%F </span></dt><dd><p>author name, or recipient name if the message is from you
-</p></dd><dt><span class="term">%H </span></dt><dd><p>spam attribute(s) of this message
-</p></dd><dt><span class="term">%i </span></dt><dd><p>message-id of the current message
-</p></dd><dt><span class="term">%l </span></dt><dd><p>number of lines in the message (does not work with maildir,
-mh, and possibly IMAP folders)
-</p></dd><dt><span class="term">%L </span></dt><dd><p>If an address in the “<span class="quote">To:</span>” or “<span class="quote">Cc:</span>” header field matches an address
-defined by the users “<span class="quote"><a class="link" href="#subscribe">subscribe</a></span>” command, this displays
-"To <list-name>", otherwise the same as %F.
-</p></dd><dt><span class="term">%m </span></dt><dd><p>total number of message in the mailbox
-</p></dd><dt><span class="term">%M </span></dt><dd><p>number of hidden messages if the thread is collapsed.
-</p></dd><dt><span class="term">%N </span></dt><dd><p>message score
-</p></dd><dt><span class="term">%n </span></dt><dd><p>author's real name (or address if missing)
-</p></dd><dt><span class="term">%O </span></dt><dd><p>original save folder where mutt would formerly have
-stashed the message: list name or recipient name
-if not sent to a list
-</p></dd><dt><span class="term">%P </span></dt><dd><p>progress indicator for the builtin pager (how much of the file has been displayed)
-</p></dd><dt><span class="term">%s </span></dt><dd><p>subject of the message
-</p></dd><dt><span class="term">%S </span></dt><dd><p>status of the message (“<span class="quote">N</span>”/“<span class="quote">D</span>”/“<span class="quote">d</span>”/“<span class="quote">!</span>”/“<span class="quote">r</span>”/*)
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">To:</span>” field (recipients)
-</p></dd><dt><span class="term">%T </span></dt><dd><p>the appropriate character from the <a class="link" href="#to-chars" title="3.289. to_chars">$to_chars</a> string
-</p></dd><dt><span class="term">%u </span></dt><dd><p>user (login) name of the author
-</p></dd><dt><span class="term">%v </span></dt><dd><p>first name of the author, or the recipient if the message is from you
-</p></dd><dt><span class="term">%X </span></dt><dd><p>number of attachments
-(please see the “<span class="quote"><a class="link" href="#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
-</p></dd><dt><span class="term">%y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present
-</p></dd><dt><span class="term">%Y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present, and <span class="emphasis"><em>(1)</em></span> not at part of a thread tree,
-<span class="emphasis"><em>(2)</em></span> at the top of a thread, or <span class="emphasis"><em>(3)</em></span> “<span class="quote">X-Label:</span>” is different from
-preceding message's “<span class="quote">X-Label:</span>”.
-</p></dd><dt><span class="term">%Z </span></dt><dd><p>message status flags
-</p></dd><dt><span class="term">%{fmt} </span></dt><dd><p>the date and time of the message is converted to sender's
-time zone, and “<span class="quote">fmt</span>” is expanded by the library function
-<code class="literal">strftime(3)</code>; a leading bang disables locales
-</p></dd><dt><span class="term">%[fmt] </span></dt><dd><p>the date and time of the message is converted to the local
-time zone, and “<span class="quote">fmt</span>” is expanded by the library function
-<code class="literal">strftime(3)</code>; a leading bang disables locales
-</p></dd><dt><span class="term">%(fmt) </span></dt><dd><p>the local date and time when the message was received.
-“<span class="quote">fmt</span>” is expanded by the library function <code class="literal">strftime(3)</code>;
-a leading bang disables locales
-</p></dd><dt><span class="term">%<fmt> </span></dt><dd><p>the current local time. “<span class="quote">fmt</span>” is expanded by the library
-function <code class="literal">strftime(3)</code>; a leading bang disables locales.
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-“<span class="quote">Soft-fill</span>” deserves some explanation: Normal right-justification
-will print everything to the left of the “<span class="quote">%></span>”, displaying padding and
-whatever lies to the right only if there's room. By contrast,
-soft-fill gives priority to the right-hand side, guaranteeing space
-to display it and showing padding only if there's still room. If
-necessary, soft-fill will eat text leftwards to make room for
-rightward text.
-</p><p>
-Note that these expandos are supported in
-“<span class="quote"><a class="link" href="#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” and “<span class="quote"><a class="link" href="#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></span>”, too.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ispell"></a>3.102. ispell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">ispell</code></span>”</p></div><p>
-How to invoke ispell (GNU's spell-checking software).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="keep-flagged"></a>3.103. keep_flagged</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, read messages marked as flagged will not be moved
-from your spool mailbox to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
-a “<span class="quote"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="locale"></a>3.104. locale</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">C</code></span>”</p></div><p>
-The locale used by <code class="literal">strftime(3)</code> to format dates. Legal values are
-the strings your system accepts for the locale environment variable <code class="literal">$LC_TIME</code>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mail-check"></a>3.105. mail_check</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 5</p></div><p>
-This variable configures how often (in seconds) mutt should look for
-new mail. Also see the <a class="link" href="#timeout" title="3.287. timeout">$timeout</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-path"></a>3.106. mailcap_path</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable specifies which files to consult when attempting to
-display MIME bodies not directly supported by Mutt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-sanitize"></a>3.107. mailcap_sanitize</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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.
-</p><p>
-<span class="bold"><strong>DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
-DOING!</strong></span>
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-mtime"></a>3.108. maildir_mtime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If set, the sort-by-date option in the browser will sort maildirs
-smartly, not using the mtime of the maildir itself but that of the
-newest message in the new subdirectory, making the sorting by
-reverse date much more useful. People with maildirs over NFS may
-wish to leave this option unset.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache"></a>3.109. header_cache</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is <span class="emphasis"><em>unset</em></span> so no header
-caching will be used.
-</p><p>
-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see “<span class="quote"><a class="link" href="#caching" title="7. Local caching">caching</a></span>” for details.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-header-cache-verify"></a>3.110. maildir_header_cache_verify</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Check for Maildir unaware programs other than mutt having modified maildir
-files when the header cache is in use. This incurs one <code class="literal">stat(2)</code> per
-message every time the folder is opened (which can be very slow for NFS
-folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache-pagesize"></a>3.111. header_cache_pagesize</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">16384</code></span>”</p></div><p>
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-trash"></a>3.112. maildir_trash</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, messages marked as deleted will be saved with the maildir
-trashed flag instead of unlinked. <span class="bold"><strong>Note:</strong></span> this only applies
-to maildir-style mailboxes. Setting it will have no effect on other
-mailbox types.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mark-old"></a>3.113. mark_old</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether or not mutt marks <span class="emphasis"><em>new</em></span> <span class="bold"><strong>unread</strong></span>
-messages as <span class="emphasis"><em>old</em></span> if you exit a mailbox without reading them.
-With this option <span class="emphasis"><em>set</em></span>, the next time you start mutt, the messages
-will show up with an “<span class="quote">O</span>” next to them in the index menu,
-indicating that they are old.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="markers"></a>3.114. markers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the display of wrapped lines in the internal pager. If set, a
-“<span class="quote">+</span>” marker is displayed at the beginning of wrapped lines.
-</p><p>
-Also see the <a class="link" href="#smart-wrap" title="3.264. smart_wrap">$smart_wrap</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mask"></a>3.115. mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">!^\.[^.]</code></span>”</p></div><p>
-A regular expression used in the file browser, optionally preceded by
-the <span class="emphasis"><em>not</em></span> operator “<span class="quote">!</span>”. Only files whose names match this mask
-will be shown. The match is always case-sensitive.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox"></a>3.116. mbox</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/mbox</code></span>”</p></div><p>
-This specifies the folder into which read mail in your <a class="link" href="#spoolfile" title="3.276. spoolfile">$spoolfile</a>
-folder will be appended.
-</p><p>
-Also see the <a class="link" href="#move" title="3.132. move">$move</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox-type"></a>3.117. mbox_type</h3></div></div></div><div class="literallayout"><p>Type: folder magic<br />
-Default: mbox</p></div><p>
-The default mailbox type used when creating new folders. May be any of
-“<span class="quote">mbox</span>”, “<span class="quote">MMDF</span>”, “<span class="quote">MH</span>” and “<span class="quote">Maildir</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="metoo"></a>3.118. metoo</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>unset</em></span>, Mutt will remove your address (see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”
-command) from the list of recipients when replying to a message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-context"></a>3.119. menu_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to <a class="link" href="#pager-context" title="3.139. pager_context">$pager_context</a>.)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-move-off"></a>3.120. menu_move_off</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, the bottom entry of menus will never scroll up past
-the bottom of the screen, unless there are less entries than lines.
-When <span class="emphasis"><em>set</em></span>, the bottom entry may move off the bottom.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-scroll"></a>3.121. menu_scroll</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, menus will be scrolled up or down one line when you
-attempt to move across a screen boundary. If <span class="emphasis"><em>unset</em></span>, the screen
-is cleared and the next or previous page of the menu is displayed
-(useful for slow links to avoid many redraws).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="meta-key"></a>3.122. meta_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, forces Mutt 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 <code class="literal">0xf8</code>, then this is treated as if the user had
-pressed Esc then “<span class="quote">x</span>”. This is because the result of removing the
-high bit from <code class="literal">0xf8</code> is <code class="literal">0x78</code>, which is the ASCII character
-“<span class="quote">x</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-purge"></a>3.123. mh_purge</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mutt will mimic mh's behaviour and rename deleted messages
-to <span class="emphasis"><em>,<old file name></em></span> in mh folders instead of really deleting
-them. This leaves the message on disk but makes programs reading the folder
-ignore it. If the variable is <span class="emphasis"><em>set</em></span>, the message files will simply be
-deleted.
-</p><p>
-This option is similar to <a class="link" href="#maildir-trash" title="3.112. maildir_trash">$maildir_trash</a> for Maildir folders.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-flagged"></a>3.124. mh_seq_flagged</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">flagged</code></span>”</p></div><p>
-The name of the MH sequence used for flagged messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-replied"></a>3.125. mh_seq_replied</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">replied</code></span>”</p></div><p>
-The name of the MH sequence used to tag replied messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-unseen"></a>3.126. mh_seq_unseen</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">unseen</code></span>”</p></div><p>
-The name of the MH sequence used for unseen messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward"></a>3.127. mime_forward</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the message you are forwarding will be attached as a
-separate <code class="literal">message/rfc822</code> 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 “<span class="quote">ask-no</span>” or “<span class="quote">ask-yes</span>”.
-</p><p>
-Also see <a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-decode"></a>3.128. mime_forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
-forwarding a message while <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span>. Otherwise
-<a class="link" href="#forward-decode" title="3.62. forward_decode">$forward_decode</a> is used instead.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-rest"></a>3.129. mime_forward_rest</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-When forwarding multiple attachments of a MIME message from the attachment
-menu, attachments which cannot be decoded in a reasonable manner will
-be attached to the newly composed message if this option is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix-entry-format"></a>3.130. mix_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %c %-16s %a</code></span>”</p></div><p>
-This variable describes the format of a remailer line on the mixmaster
-chain selection screen. The following <code class="literal">printf(3)</code>-like sequences are
-supported:
-
-</p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>The running number on the menu.
-</p></dd><dt><span class="term">%c </span></dt><dd><p>Remailer capabilities.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>The remailer's short name.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The remailer's e-mail address.
-</p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mixmaster"></a>3.131. mixmaster</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">mixmaster</code></span>”</p></div><p>
-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.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
-“<span class="quote">mixmaster-filter</span>” in /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="move"></a>3.132. move</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: no</p></div><p>
-Controls whether or not Mutt will move read messages
-from your spool mailbox to your <a class="link" href="#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
-a “<span class="quote"><a class="link" href="#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cachedir"></a>3.133. message_cachedir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-</p><p>
-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-</p><p>
-Also see the <a class="link" href="#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cache-clean"></a>3.134. message_cache_clean</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-format"></a>3.135. message_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%s</code></span>”</p></div><p>
-This is the string displayed in the “<span class="quote">attachment</span>” menu for
-attachments of type <code class="literal">message/rfc822</code>. For a full listing of defined
-<code class="literal">printf(3)</code>-like sequences see the section on <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="narrow-tree"></a>3.136. narrow_tree</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable, when <span class="emphasis"><em>set</em></span>, makes the thread tree narrower, allowing
-deeper threads to fit on the screen.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="net-inc"></a>3.137. net_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-Operations that expect to transfer a large amount of data over the
-network will update their progress every <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> kilobytes.
-If set to 0, no progress messages will be displayed.
-</p><p>
-See also <a class="link" href="#read-inc" title="3.235. read_inc">$read_inc</a>, <a class="link" href="#write-inc" title="3.305. write_inc">$write_inc</a> and <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager"></a>3.138. pager</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">builtin</code></span>”</p></div><p>
-This variable specifies which pager you would like to use to view
-messages. The value “<span class="quote">builtin</span>” means to use the builtin pager, otherwise this
-variable should specify the pathname of the external pager you would
-like to use.
-</p><p>
-Using an external pager may have some disadvantages: Additional
-keystrokes are necessary because you can't call mutt functions
-directly from the pager, and screen resizes cause lines longer than
-the screen width to be badly formatted in the help menu.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-context"></a>3.139. pager_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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 will display the line after the last one on the screen
-at the top of the next page (0 lines of context).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-format"></a>3.140. pager_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-%Z- %C/%m: %-20.20n %s%* -- (%P)</code></span>”</p></div><p>
-This variable controls the format of the one-line message “<span class="quote">status</span>”
-displayed before each message in either the internal or an external
-pager. The valid sequences are listed in the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>
-section.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-index-lines"></a>3.141. pager_index_lines</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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 setting 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 <a class="link" href="#pager-index-lines" title="3.141. pager_index_lines">$pager_index_lines</a>, then the index will only use as
-many lines as it needs.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-stop"></a>3.142. pager_stop</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the internal-pager will <span class="bold"><strong>not</strong></span> move to the next message
-when you are at the end of a message and invoke the <code class="literal"><next-page></code>
-function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosign"></a>3.143. crypt_autosign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt 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 <a class="link" href="#smime-is-default" title="3.152. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autoencrypt"></a>3.144. crypt_autoencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages. This is probably only useful in
-connection to the “<span class="quote"><a class="link" href="#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>” command. It can be overridden
-by use of the pgp menu, when encryption is not required or
-signing is requested as well. If <a class="link" href="#smime-is-default" title="3.152. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-ignore-subkeys"></a>3.145. pgp_ignore_subkeys</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities. <span class="emphasis"><em>Unset</em></span> this
-if you want to play interesting key selection games.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replyencrypt"></a>3.146. crypt_replyencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysign"></a>3.147. crypt_replysign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages which are
-signed.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> this does not work on messages that are encrypted
-<span class="emphasis"><em>and</em></span> signed!
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysignencrypted"></a>3.148. crypt_replysignencrypted</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages
-which are encrypted. This makes sense in combination with
-<a class="link" href="#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>, because it allows you to sign all
-messages which are automatically encrypted. This works around
-the problem noted in <a class="link" href="#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a>, that mutt is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-timestamp"></a>3.149. crypt_timestamp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 <span class="emphasis"><em>unset</em></span> this setting.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-use-gpg-agent"></a>3.150. pgp_use_gpg_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will use a possibly-running <code class="literal">gpg-agent(1)</code> process.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-verify-sig"></a>3.151. crypt_verify_sig</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>“<span class="quote">yes</span>”</em></span>, always attempt to verify PGP or S/MIME signatures.
-If <span class="emphasis"><em>“<span class="quote">ask-*</span>”</em></span>, ask whether or not to verify the signature.
-If \Fi“<span class="quote">no</span>”, never attempt to verify cryptographic signatures.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-is-default"></a>3.152. smime_is_default</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-The default behaviour of mutt is to use PGP on all auto-sign/encryption
-operations. To override and to use OpenSSL instead this must be <span class="emphasis"><em>set</em></span>.
-However, this has no effect while replying, since mutt will automatically
-select the same application that was used to sign/encrypt the original
-message. (Note that this variable can be overridden by unsetting <a class="link" href="#crypt-autosmime" title="3.39. crypt_autosmime">$crypt_autosmime</a>.)
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ask-cert-label"></a>3.153. smime_ask_cert_label</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-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
-<span class="emphasis"><em>set</em></span> by default.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-use-default-key"></a>3.154. smime_decrypt_use_default_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span> (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate-key-pairs, mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-entry-format"></a>3.155. pgp_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %t%f %4l/0x%k %-4a %2c %u</code></span>”</p></div><p>
-This variable allows you to customize the PGP key selection menu to
-your personal taste. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but
-has its own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>number
-</p></dd><dt><span class="term">%k </span></dt><dd><p>key id
-</p></dd><dt><span class="term">%u </span></dt><dd><p>user id
-</p></dd><dt><span class="term">%a </span></dt><dd><p>algorithm
-</p></dd><dt><span class="term">%l </span></dt><dd><p>key length
-</p></dd><dt><span class="term">%f </span></dt><dd><p>flags
-</p></dd><dt><span class="term">%c </span></dt><dd><p>capabilities
-</p></dd><dt><span class="term">%t </span></dt><dd><p>trust/validity of the key-uid association
-</p></dd><dt><span class="term">%[<s>] </span></dt><dd><p>date of the key where <s> is an <code class="literal">strftime(3)</code> expression
-</p></dd></dl></div><p>
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-good-sign"></a>3.156. pgp_good_sign</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: (empty)</p></div><p>
-If you assign a text to this variable, then a PGP signature is only
-considered verified if the output from <a class="link" href="#pgp-verify-command" title="3.173. pgp_verify_command">$pgp_verify_command</a> contains
-the text. Use this variable if the exit code from the command is 0
-even for bad signatures.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-check-exit"></a>3.157. pgp_check_exit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-long-ids"></a>3.158. pgp_long_ids</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, use 64 bit PGP key IDs, if <span class="emphasis"><em>unset</em></span> use the normal 32 bit key IDs.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-retainable-sigs"></a>3.159. pgp_retainable_sigs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, signed and encrypted messages will consist of nested
-<code class="literal">multipart/signed</code> and <code class="literal">multipart/encrypted</code> body parts.
-</p><p>
-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (<code class="literal">multipart/encrypted</code>) can be easily
-removed, while the inner <code class="literal">multipart/signed</code> part is retained.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-autoinline"></a>3.160. pgp_autoinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option controls whether Mutt 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.
-</p><p>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</p><p>
-Also see the <a class="link" href="#pgp-mime-auto" title="3.167. pgp_mime_auto">$pgp_mime_auto</a> variable.
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-replyinline"></a>3.161. pgp_replyinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt 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
-internals for previously checked/flagged messages.
-</p><p>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</p><p>
-Also see the <a class="link" href="#pgp-mime-auto" title="3.167. pgp_mime_auto">$pgp_mime_auto</a> variable.
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-show-unusable"></a>3.162. pgp_show_unusable</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 “<span class="quote">disabled</span>” by the user.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-as"></a>3.163. pgp_sign_as</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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. <code class="literal">0x00112233</code>).
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-strict-enc"></a>3.164. pgp_strict_enc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-timeout"></a>3.165. pgp_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 300</p></div><p>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sort-keys"></a>3.166. pgp_sort_keys</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: address</p></div><p>
-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-
-</p><div class="variablelist"><dl><dt><span class="term">address </span></dt><dd><p>sort alphabetically by user id
-</p></dd><dt><span class="term">keyid </span></dt><dd><p>sort alphabetically by key id
-</p></dd><dt><span class="term">date </span></dt><dd><p>sort by key creation date
-</p></dd><dt><span class="term">trust </span></dt><dd><p>sort by the trust of the key
-</p></dd></dl></div><p>
-If you prefer reverse order of the above values, prefix it with
-“<span class="quote">reverse-</span>”.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-auto"></a>3.167. pgp_mime_auto</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-auto-decode"></a>3.168. pgp_auto_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 <code class="literal"><a class="link" href="#check-traditional-pgp"><check-traditional-pgp></a></code> function, mutt will automatically
-check the message for traditional pgp.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-filename"></a>3.169. pgp_mime_signature_filename</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">signature.asc</code></span>”</p></div><p>
-This option sets the filename used for signature parts in PGP/MIME
-signed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-description"></a>3.170. pgp_mime_signature_description</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">Digital signature</code></span>”</p></div><p>
-This option sets the Content-Description used for signature parts in
-PGP/MIME signed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decode-command"></a>3.171. pgp_decode_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format strings specifies a command which is used to decode
-application/pgp attachments.
-</p><p>
-The PGP command formats have their own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%p </span></dt><dd><p>Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-string otherwise. Note: This may be used with a %? construct.
-</p></dd><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
- of a <code class="literal">multipart/signed</code> attachment when verifying it.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The value of <a class="link" href="#pgp-sign-as" title="3.163. pgp_sign_as">$pgp_sign_as</a>.
-</p></dd><dt><span class="term">%r </span></dt><dd><p>One or more key IDs.
-</p></dd></dl></div><p>
-For examples on how to configure these formats for the various versions
-of PGP which are floating around, see the pgp and gpg sample configuration files in
-the <code class="literal">samples/</code> subdirectory which has been installed on your system
-alongside the documentation.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-getkeys-command"></a>3.172. pgp_getkeys_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a>, %r is the only
-<code class="literal">printf(3)</code>-like sequence used with this format.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-command"></a>3.173. pgp_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify PGP signatures.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decrypt-command"></a>3.174. pgp_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to decrypt a PGP encrypted message.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-clearsign-command"></a>3.175. pgp_clearsign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format is used to create an old-style “<span class="quote">clearsigned</span>” PGP
-message. Note that the use of this format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-command"></a>3.176. pgp_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to create the detached PGP signature for a
-<code class="literal">multipart/signed</code> PGP/MIME body part.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-sign-command"></a>3.177. pgp_encrypt_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to both sign and encrypt a body part.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-only-command"></a>3.178. pgp_encrypt_only_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to encrypt a body part without signing it.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-import-command"></a>3.179. pgp_import_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to import a key from a message into
-the user's public key ring.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-export-command"></a>3.180. pgp_export_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to export a public key from the user's
-key ring.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-key-command"></a>3.181. pgp_verify_key_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify key information from the key selection
-menu.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-secring-command"></a>3.182. pgp_list_secring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to list the secret key ring's contents. The
-output format must be analogous to the one used by:
-
-</p><pre class="screen">
-gpg --list-keys --with-colons.
-
-</pre><p>
-This format is also generated by the <code class="literal">pgpring</code> utility which comes
-with mutt.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-pubring-command"></a>3.183. pgp_list_pubring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to list the public key ring's contents. The
-output format must be analogous to the one used by
-
-</p><pre class="screen">
-gpg --list-keys --with-colons.
-
-</pre><p>
-This format is also generated by the <code class="literal">pgpring</code> utility which comes
-with mutt.
-</p><p>
-This is a format string, see the <a class="link" href="#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decrypt"></a>3.184. forward_decrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the handling of encrypted messages when forwarding a message.
-When <span class="emphasis"><em>set</em></span>, the outer layer of encryption is stripped off. This
-variable is only used if <a class="link" href="#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span> and
-<a class="link" href="#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is <span class="emphasis"><em>unset</em></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-timeout"></a>3.185. smime_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 300</p></div><p>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-with"></a>3.186. smime_encrypt_with</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This sets the algorithm that should be used for encryption.
-Valid choices are “<span class="quote">des</span>”, “<span class="quote">des3</span>”, “<span class="quote">rc2-40</span>”, “<span class="quote">rc2-64</span>”, “<span class="quote">rc2-128</span>”.
-If <span class="emphasis"><em>unset</em></span>, “<span class="quote">3des</span>” (TripleDES) is used.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-keys"></a>3.187. smime_keys</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and 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 option points to the location of the private keys.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ca-location"></a>3.188. smime_ca_location</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this defaults to the first existing file in
-the following list: ˜/.smime/ca-certificates.crt ˜/.smime/ca-bundle.crt
-/etc/ssl/certs/ca-certificates.crt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-certificates"></a>3.189. smime_certificates</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-the location of the certificates.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-command"></a>3.190. smime_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format string specifies a command which is used to decrypt
-<code class="literal">application/x-pkcs7-mime</code> attachments.
-</p><p>
-The OpenSSL command formats have their own set of <code class="literal">printf(3)</code>-like sequences
-similar to PGP's:
-
-</p><div class="variablelist"><dl><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
- of a <code class="literal">multipart/signed</code> attachment when verifying it.
-</p></dd><dt><span class="term">%k </span></dt><dd><p>The key-pair specified with <a class="link" href="#smime-default-key" title="3.201. smime_default_key">$smime_default_key</a>
-</p></dd><dt><span class="term">%c </span></dt><dd><p>One or more certificate IDs.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The algorithm used for encryption.
-</p></dd><dt><span class="term">%C </span></dt><dd><p>CA location: Depending on whether <a class="link" href="#smime-ca-location" title="3.188. smime_ca_location">$smime_ca_location</a>
- points to a directory or file, this expands to
- “<span class="quote">-CApath <a class="link" href="#smime-ca-location" title="3.188. smime_ca_location">$smime_ca_location</a></span>” or “<span class="quote">-CAfile <a class="link" href="#smime-ca-location" title="3.188. smime_ca_location">$smime_ca_location</a></span>”.
-</p></dd></dl></div><p>
-For examples on how to configure these formats, see the <code class="literal">smime.rc</code> in
-the <code class="literal">samples/</code> subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-command"></a>3.191. smime_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify S/MIME signatures of type <code class="literal">multipart/signed</code>.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-opaque-command"></a>3.192. smime_verify_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify S/MIME signatures of type
-<code class="literal">application/x-pkcs7-mime</code>.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-command"></a>3.193. smime_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to created S/MIME signatures of type
-<code class="literal">multipart/signed</code>, which can be read by all mail clients.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-opaque-command"></a>3.194. smime_sign_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to created S/MIME signatures of type
-<code class="literal">application/x-pkcs7-signature</code>, which can only be handled by mail
-clients supporting the S/MIME extension.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-command"></a>3.195. smime_encrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to create encrypted S/MIME messages.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-pk7out-command"></a>3.196. smime_pk7out_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-command"></a>3.197. smime_get_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to extract X509 certificates from a PKCS7 structure.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-signer-cert-command"></a>3.198. smime_get_signer_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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 “<span class="quote">From:</span>” field.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-import-cert-command"></a>3.199. smime_import_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to import a certificate via smime_keys.
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-email-command"></a>3.200. smime_get_cert_email_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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).
-</p><p>
-This is a format string, see the <a class="link" href="#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-default-key"></a>3.201. smime_default_key</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-client-cert"></a>3.202. ssl_client_cert</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-The file containing a client certificate and its associated private
-key.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-force-tls"></a>3.203. ssl_force_tls</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If this variable is <span class="emphasis"><em>set</em></span>, Mutt 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 <a class="link" href="#ssl-starttls" title="3.204. ssl_starttls">$ssl_starttls</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-starttls"></a>3.204. ssl_starttls</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span> (the default), mutt will attempt to use <code class="literal">STARTTLS</code> on servers
-advertising the capability. When <span class="emphasis"><em>unset</em></span>, mutt will not attempt to
-use <code class="literal">STARTTLS</code> regardless of the server's capabilities.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="certificate-file"></a>3.205. certificate_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.mutt_certificates</code></span>”</p></div><p>
-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.
-</p><p>
-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set certificate_file=~/.mutt/certificates
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-sslv3"></a>3.206. ssl_use_sslv3</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-tlsv1"></a>3.207. ssl_use_tlsv1</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-min-dh-prime-bits"></a>3.208. ssl_min_dh_prime_bits</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-ca-certificates-file"></a>3.209. ssl_ca_certificates_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this variable defaults to the example
-mentioned. This file is managed by the “<span class="quote">ca-certificates</span>” package.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-split"></a>3.210. pipe_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><pipe-message></code> function following
-<code class="literal"><tag-prefix></code>. If this variable is <span class="emphasis"><em>unset</em></span>, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated. When <span class="emphasis"><em>set</em></span>, Mutt will pipe the messages one by one.
-In both cases the messages are piped in the current sorted order,
-and the <a class="link" href="#pipe-sep" title="3.212. pipe_sep">$pipe_sep</a> separator is added after each message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-decode"></a>3.211. pipe_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><pipe-message></code> command. When <span class="emphasis"><em>unset</em></span>,
-Mutt will pipe the messages without any preprocessing. When <span class="emphasis"><em>set</em></span>, Mutt
-will weed headers and will attempt to decode the messages
-first.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-sep"></a>3.212. pipe_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
-The separator to add between messages when piping a list of tagged
-messages to an external Unix command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-authenticators"></a>3.213. pop_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an POP server, in the order mutt should
-try them. Authentication methods are either “<span class="quote">user</span>”, “<span class="quote">apop</span>” or any
-SASL mechanism, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
-This option is case-insensitive. If this option is <span class="emphasis"><em>unset</em></span>
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set pop_authenticators="digest-md5:apop:user"
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-auth-try-all"></a>3.214. pop_auth_try_all</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will try all available authentication methods.
-When <span class="emphasis"><em>unset</em></span>, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-checkinterval"></a>3.215. pop_checkinterval</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 60</p></div><p>
-This variable configures how often (in seconds) mutt should look for
-new mail in the currently selected mailbox if it is a POP mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-delete"></a>3.216. pop_delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will delete successfully downloaded messages from the POP
-server when using the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function. When <span class="emphasis"><em>unset</em></span>, Mutt will
-download messages but also leave them on the POP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-host"></a>3.217. pop_host</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-The name of your POP server for the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function. You
-can also specify an alternative port, username and password, ie:
-
-</p><pre class="screen">
-[pop[s]://][username[:password]@]popserver[:port]
-
-</pre><p>
-where “<span class="quote">[...]</span>” denotes an optional part.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-last"></a>3.218. pop_last</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If this variable is <span class="emphasis"><em>set</em></span>, mutt will try to use the “<span class="quote"><code class="literal">LAST</code></span>” POP command
-for retrieving only unread messages from the POP server when using
-the <code class="literal"><a class="link" href="#fetch-mail"><fetch-mail></a></code> function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-reconnect"></a>3.219. pop_reconnect</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-user"></a>3.220. pop_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Your login name on the POP server.
-</p><p>
-This variable defaults to your user name on the local machine.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-pass"></a>3.221. pop_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your POP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you open a POP mailbox.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc
-even if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="post-indent-string"></a>3.222. post_indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Similar to the <a class="link" href="#attribution" title="3.16. attribution">$attribution</a> variable, Mutt will append this
-string after the inclusion of a message which is being replied to.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone"></a>3.223. postpone</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not messages are saved in the <a class="link" href="#postponed" title="3.224. postponed">$postponed</a>
-mailbox when you elect not to send immediately.
-</p><p>
-Also see the <a class="link" href="#recall" title="3.238. recall">$recall</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postponed"></a>3.224. postponed</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/postponed</code></span>”</p></div><p>
-Mutt allows you to indefinitely “<span class="quote"><a class="link" href="#postpone" title="3.223. postpone">postpone</a> sending a message</span>” which
-you are editing. When you choose to postpone a message, Mutt saves it
-in the mailbox specified by this variable.
-</p><p>
-Also see the <a class="link" href="#postpone" title="3.223. postpone">$postpone</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="preconnect"></a>3.225. preconnect</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-If <span class="emphasis"><em>set</em></span>, a shell command to be executed if mutt fails to establish
-a connection to the server. This is useful for setting up secure
-connections, e.g. with <code class="literal">ssh(1)</code>. If the command returns a nonzero
-status, mutt gives up opening the server. Example:
-
-</p><pre class="screen">
-set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
-sleep 20 < /dev/null > /dev/null"
-
-</pre><p>
-Mailbox “<span class="quote">foo</span>” on “<span class="quote">mailhost.net</span>” can now be reached
-as “<span class="quote">{localhost:1234}foo</span>”.
-</p><p>
-Note: For this example to work, you must be able to log in to the
-remote machine without having to enter a password.
-</p><p>
-When set, Mutt uses the tunnel for all remote connections.
-Please see “<span class="quote"><a class="link" href="#account-hook" title="6. Managing multiple accounts">account-hook</a></span>” in the manual for how to use different
-tunnel commands per connection.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print"></a>3.226. print</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-no</p></div><p>
-Controls whether or not Mutt really prints messages.
-This is set to “<span class="quote">ask-no</span>” by default, because some people
-accidentally hit “<span class="quote">p</span>” often.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-command"></a>3.227. print_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">lpr</code></span>”</p></div><p>
-This specifies the command pipe that should be used to print messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-decode"></a>3.228. print_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Used in connection with the <code class="literal"><print-message></code> command. If this
-option is <span class="emphasis"><em>set</em></span>, the message is decoded before it is passed to the
-external command specified by <a class="link" href="#print-command" title="3.227. print_command">$print_command</a>. If this option
-is <span class="emphasis"><em>unset</em></span>, 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-split"></a>3.229. print_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><print-message></code> command. If this option
-is <span class="emphasis"><em>set</em></span>, the command specified by <a class="link" href="#print-command" title="3.227. print_command">$print_command</a> is executed once for
-each message which is to be printed. If this option is <span class="emphasis"><em>unset</em></span>,
-the command specified by <a class="link" href="#print-command" title="3.227. print_command">$print_command</a> is executed only once, and
-all the messages are concatenated, with a form feed as the message
-separator.
-</p><p>
-Those who use the <code class="literal">enscript</code>(1) program's mail-printing mode will
-most likely want to <span class="emphasis"><em>set</em></span> this option.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="prompt-after"></a>3.230. prompt_after</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If you use an <span class="emphasis"><em>external</em></span> <a class="link" href="#pager" title="3.138. pager">$pager</a>, setting this variable will
-cause Mutt to prompt you for a command when the pager exits rather
-than returning to the index menu. If <span class="emphasis"><em>unset</em></span>, Mutt will return to the
-index menu when the external pager exits.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-command"></a>3.231. query_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This specifies the command that mutt will use to make external address
-queries. The string should contain a “<span class="quote">%s</span>”, which will be substituted
-with the query string the user types. See “<span class="quote"><a class="link" href="#query" title="5. External Address Queries">query</a></span>” for more
-information.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-format"></a>3.232. query_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4c %t %-25.25a %-25.25n %?e?(%e)?</code></span>”</p></div><p>
-This variable describes the format of the “<span class="quote">query</span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are understood:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>destination address
-</p></dd><dt><span class="term">%c </span></dt><dd><p>current entry number
-</p></dd><dt><span class="term">%e </span></dt><dd><p>extra information *
-</p></dd><dt><span class="term">%n </span></dt><dd><p>destination name
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if current entry is tagged, a space otherwise
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p><p>
-* = can be optionally printed if nonzero, see the <a class="link" href="#status-format" title="3.278. status_format">$status_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quit"></a>3.233. quit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether “<span class="quote">quit</span>” and “<span class="quote">exit</span>” actually quit
-from mutt. If this option is <span class="emphasis"><em>set</em></span>, they do quit, if it is <span class="emphasis"><em>unset</em></span>, they
-have no effect, and if it is set to <span class="emphasis"><em>ask-yes</em></span> or <span class="emphasis"><em>ask-no</em></span>, you are
-prompted for confirmation when you try to quit.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quote-regexp"></a>3.234. quote_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^([ \t]*[|>:}#])+</code></span>”</p></div><p>
-A regular expression used in the internal pager to determine quoted
-sections of text in the body of a message. Quoted text may be filtered
-out using the <code class="literal"><toggle-quoted></code> command, or colored according to the
-“<span class="quote">color quoted</span>” family of directives.
-</p><p>
-Higher levels of quoting may be colored differently (“<span class="quote">color quoted1</span>”,
-“<span class="quote">color quoted2</span>”, etc.). The quoting level is determined by removing
-the last character from the matched text and recursively reapplying
-the regular expression until it fails to produce a match.
-</p><p>
-Match detection may be overridden by the <a class="link" href="#smileys" title="3.265. smileys">$smileys</a> regular expression.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-inc"></a>3.235. read_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-If set to a value greater than 0, Mutt will display which message it
-is currently on when reading a mailbox or when performing search actions
-such as search and limit. The message is printed after
-this many messages have been read or searched (e.g., if set to 25, Mutt will
-print a message when it is at message 25, and then again when it gets
-to message 50). This variable is meant to indicate progress when
-reading or searching large mailboxes which may take some time.
-When set to 0, only a single message will appear before the reading
-the mailbox.
-</p><p>
-Also see the <a class="link" href="#write-inc" title="3.305. write_inc">$write_inc</a>, <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="#time-inc" title="3.286. time_inc">$time_inc</a> variables and the
-“<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-only"></a>3.236. read_only</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, all folders are opened in read-only mode.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="realname"></a>3.237. realname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable specifies what “<span class="quote">real</span>” or “<span class="quote">personal</span>” name should be used
-when sending messages.
-</p><p>
-By default, this is the GECOS field from <code class="literal">/etc/passwd</code>. Note that this
-variable will <span class="emphasis"><em>not</em></span> be used when the user has set a real name
-in the <a class="link" href="#from" title="3.66. from">$from</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="recall"></a>3.238. recall</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not Mutt recalls postponed messages
-when composing a new message.
-</p><p>
-<span class="emphasis"><em>Setting</em></span> this variable to is not generally useful, and thus not
-recommended.
-</p><p>
-Also see <a class="link" href="#postponed" title="3.224. postponed">$postponed</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="record"></a>3.239. record</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/sent</code></span>”</p></div><p>
-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 “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command to create a “<span class="quote">Bcc:</span>” field with your email address in it.)
-</p><p>
-The value of <span class="emphasis"><em><a class="link" href="#record" title="3.239. record">$record</a></em></span> is overridden by the <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> and
-<a class="link" href="#save-name" title="3.251. save_name">$save_name</a> variables, and the “<span class="quote"><a class="link" href="#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-regexp"></a>3.240. reply_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^(re([\[0-9\]+])*|aw):[ \t]*</code></span>”</p></div><p>
-A regular expression used to recognize reply messages when threading
-and replying. The default value corresponds to the English "Re:" and
-the German "Aw:".
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-self"></a>3.241. reply_self</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>unset</em></span> and you are replying to a message sent by you, Mutt will
-assume that you want to reply to the recipients of that message rather
-than to yourself.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-to"></a>3.242. reply_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, when replying to a message, Mutt will use the address listed
-in the Reply-to: header as the recipient of the reply. If <span class="emphasis"><em>unset</em></span>,
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="resolve"></a>3.243. resolve</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the cursor will be automatically advanced to the next
-(possibly undeleted) message whenever a command that modifies the
-current message is executed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-alias"></a>3.244. reverse_alias</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls whether or not Mutt will display the “<span class="quote">personal</span>”
-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:
-
-</p><pre class="screen">
-alias juser abd30425@somewhere.net (Joe User)
-
-</pre><p>
-and then you receive mail which contains the following header:
-
-</p><pre class="screen">
-From: abd30425@somewhere.net
-
-</pre><p>
-It would be displayed in the index menu as “<span class="quote">Joe User</span>” instead of
-“<span class="quote">abd30425@somewhere.net.</span>” This is useful when the person's e-mail
-address is not human friendly.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-name"></a>3.245. reverse_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <span class="emphasis"><em>set</em></span>, the default <span class="emphasis"><em>From:</em></span> line of
-the reply messages is built using the address where you received the
-messages you are replying to <span class="bold"><strong>if</strong></span> that address matches your
-“<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”. If the variable is <span class="emphasis"><em>unset</em></span>, or the address that would be
-used doesn't match your “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>”, the <span class="emphasis"><em>From:</em></span> line will use
-your address on the current machine.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="#alternates" title="11. Alternative addresses">alternates</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-realname"></a>3.246. reverse_realname</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable fine-tunes the behaviour of the <a class="link" href="#reverse-name" title="3.245. reverse_name">$reverse_name</a> feature.
-When it is <span class="emphasis"><em>set</em></span>, mutt will use the address from incoming messages as-is,
-possibly including eventual real names. When it is <span class="emphasis"><em>unset</em></span>, mutt will
-override any such real names with the setting of the <a class="link" href="#realname" title="3.237. realname">$realname</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="rfc2047-parameters"></a>3.247. rfc2047_parameters</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, Mutt will decode RFC2047-encoded MIME
-parameters. You want to set this variable when mutt suggests you
-to save attachments to files named like:
-
-</p><pre class="screen">
-=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-</pre><p>
-When this variable is <span class="emphasis"><em>set</em></span> interactively, the change won't be
-active until you change folders.
-</p><p>
-Note that this use of RFC2047's encoding is explicitly
-prohibited by the standard, but nevertheless encountered in the
-wild.
-</p><p>
-Also note that setting this parameter will <span class="emphasis"><em>not</em></span> have the effect
-that mutt <span class="emphasis"><em>generates</em></span> this kind of encoding. Instead, mutt will
-unconditionally use the encoding specified in RFC2231.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-address"></a>3.248. save_address</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If <a class="link" href="#save-name" title="3.251. save_name">$save_name</a> or <a class="link" href="#force-name" title="3.61. force_name">$force_name</a>
-is <span class="emphasis"><em>set</em></span> too, the selection of the Fcc folder will be changed as well.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-empty"></a>3.249. save_empty</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mailboxes which contain no saved messages will be removed
-when closed (the exception is <a class="link" href="#spoolfile" title="3.276. spoolfile">$spoolfile</a> which is never removed).
-If <span class="emphasis"><em>set</em></span>, mailboxes are never removed.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> This only applies to mbox and MMDF folders, Mutt does not
-delete MH and Maildir directories.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-history"></a>3.250. save_history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-This variable controls the size of the history (per category) saved in the
-<a class="link" href="#history-file" title="3.78. history_file">$history_file</a> file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-name"></a>3.251. save_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls how copies of outgoing messages are saved.
-When <span class="emphasis"><em>set</em></span>, 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 <a class="link" href="#folder" title="3.58. folder">$folder</a> directory with the <span class="emphasis"><em>username</em></span> 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
-<a class="link" href="#record" title="3.239. record">$record</a> mailbox.
-</p><p>
-Also see the <a class="link" href="#force-name" title="3.61. force_name">$force_name</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score"></a>3.252. score</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>unset</em></span>, scoring is turned off. This can
-be useful to selectively disable scoring for certain folders when the
-<a class="link" href="#score-threshold-delete" title="3.253. score_threshold_delete">$score_threshold_delete</a> variable and related are used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-delete"></a>3.253. score_threshold_delete</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: -1</p></div><p>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked for deletion by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message for deletion.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-flag"></a>3.254. score_threshold_flag</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 9999</p></div><p>
-Messages which have been assigned a score greater than or equal to this
-variable's value are automatically marked "flagged".
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-read"></a>3.255. score_threshold_read</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: -1</p></div><p>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked as read by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message read.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="send-charset"></a>3.256. send_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">us-ascii:iso-8859-1:utf-8</code></span>”</p></div><p>
-A colon-delimited list of character sets for outgoing messages. Mutt will use the
-first character set into which the text can be converted exactly.
-If your <a class="link" href="#charset" title="3.25. charset">$charset</a> is not “<span class="quote">iso-8859-1</span>” and recipients may not
-understand “<span class="quote">UTF-8</span>”, it is advisable to include in the list an
-appropriate widely used standard character set (such as
-“<span class="quote">iso-8859-2</span>”, “<span class="quote">koi8-r</span>” or “<span class="quote">iso-2022-jp</span>”) either instead of or after
-“<span class="quote">iso-8859-1</span>”.
-</p><p>
-In case the text cannot be converted into one of these exactly,
-mutt uses <a class="link" href="#charset" title="3.25. charset">$charset</a> as a fallback.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail"></a>3.257. sendmail</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">/usr/sbin/sendmail -oem -oi</code></span>”</p></div><p>
-Specifies the program and arguments used to deliver mail sent by Mutt.
-Mutt expects that the specified program interprets additional
-arguments as recipient addresses.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail-wait"></a>3.258. sendmail_wait</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-Specifies the number of seconds to wait for the <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a> process
-to finish before giving up and putting delivery in the background.
-</p><p>
-Mutt interprets the value of this variable as follows:
-
-</p><div class="variablelist"><dl><dt><span class="term">>0 </span></dt><dd><p>number of seconds to wait for sendmail to finish before continuing
-</p></dd><dt><span class="term">0 </span></dt><dd><p>wait forever for sendmail to finish
-</p></dd><dt><span class="term"><0 </span></dt><dd><p>always put sendmail in the background without waiting
-</p></dd></dl></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="shell"></a>3.259. shell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Command to use when spawning a subshell. By default, the user's login
-shell from <code class="literal">/etc/passwd</code> is used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-dashes"></a>3.260. sig_dashes</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, a line containing “<span class="quote">-- </span>” (note the trailing space) will be inserted before your
-<a class="link" href="#signature" title="3.262. signature">$signature</a>. It is <span class="bold"><strong>strongly</strong></span> recommended that you not <span class="emphasis"><em>unset</em></span>
-this variable unless your signature contains just your name. The
-reason for this is because many software packages use “<span class="quote">-- \n</span>” to
-detect your signature. For example, Mutt has the ability to highlight
-the signature in a different color in the builtin pager.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-on-top"></a>3.261. sig_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, the signature will be included before any quoted or forwarded
-text. It is <span class="bold"><strong>strongly</strong></span> 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="signature"></a>3.262. signature</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.signature</code></span>”</p></div><p>
-Specifies the filename of your signature, which is appended to all
-outgoing messages. If the filename ends with a pipe (“<span class="quote">|</span>”), it is
-assumed that filename is a shell command and input should be read from
-its standard output.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-search"></a>3.263. simple_search</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜f %s | ˜s %s</code></span>”</p></div><p>
-Specifies how Mutt should expand a simple search into a real search
-pattern. A simple search is one that does not contain any of the “<span class="quote">˜</span>” pattern
-operators. See “<span class="quote"><a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>” for more information on search patterns.
-</p><p>
-For example, if you simply type “<span class="quote">joe</span>” at a search or limit prompt, Mutt
-will automatically expand it to the value specified by this variable by
-replacing “<span class="quote">%s</span>” with the supplied string.
-For the default value, “<span class="quote">joe</span>” would be expanded to: “<span class="quote">˜f joe | ˜s joe</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smart-wrap"></a>3.264. smart_wrap</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the display of lines longer than the screen width in the
-internal pager. If <span class="emphasis"><em>set</em></span>, long lines are wrapped at a word boundary. If
-<span class="emphasis"><em>unset</em></span>, lines are simply wrapped at the screen edge. Also see the
-<a class="link" href="#markers" title="3.114. markers">$markers</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smileys"></a>3.265. smileys</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">(>From )|(:[-^]?[][)(><}{|/DP])</code></span>”</p></div><p>
-The <span class="emphasis"><em>pager</em></span> uses this variable to catch some common false
-positives of <a class="link" href="#quote-regexp" title="3.234. quote_regexp">$quote_regexp</a>, most notably smileys and not consider
-a line quoted text if it also matches <a class="link" href="#smileys" title="3.265. smileys">$smileys</a>. This mostly
-happens at the beginning of a line.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sleep-time"></a>3.266. sleep_time</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 1</p></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-authenticators"></a>3.267. smtp_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an SMTP server, in the order mutt should
-try them. Authentication methods are any SASL mechanism, eg
-“<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
-This option is case-insensitive. If it is “<span class="quote">unset</span>”
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set smtp_authenticators="digest-md5:cram-md5"
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-pass"></a>3.268. smtp_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your SMTP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you first send mail via SMTP.
-See <a class="link" href="#smtp-url" title="3.269. smtp_url">$smtp_url</a> to configure mutt to send mail via SMTP.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-url"></a>3.269. smtp_url</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Defines the SMTP smarthost where sent messages should relayed for
-delivery. This should take the form of an SMTP URL, eg:
-
-</p><pre class="screen">
-smtp[s]://[user[:pass]@]host[:port]/
-
-</pre><p>
-\.\.\. where “<span class="quote">[...]</span>” denotes an optional part.
-Setting this variable overrides the value of the <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a>
-variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort"></a>3.270. sort</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: date</p></div><p>
-Specifies how to sort messages in the “<span class="quote">index</span>” menu. Valid values
-are:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>date or date-sent
-</p></li><li><p>date-received
-</p></li><li><p>from
-</p></li><li><p>mailbox-order (unsorted)
-</p></li><li><p>score
-</p></li><li><p>size
-</p></li><li><p>spam
-</p></li><li><p>subject
-</p></li><li><p>threads
-</p></li><li><p>to
-</p></li></ul></div><p>
-You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
-order (example: “<span class="quote"><code class="literal">set sort=reverse-date-sent</code></span>”).
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
-“<span class="quote">threads</span>” in /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-alias"></a>3.271. sort_alias</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: alias</p></div><p>
-Specifies how the entries in the “<span class="quote">alias</span>” menu are sorted. The
-following are legal values:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>address (sort alphabetically by email address)
-</p></li><li><p>alias (sort alphabetically by alias name)
-</p></li><li><p>unsorted (leave in order specified in .muttrc)
-</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-aux"></a>3.272. sort_aux</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: date</p></div><p>
-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 <a class="link" href="#sort" title="3.270. sort">$sort</a> can, except
-“<span class="quote">threads</span>” (in that case, mutt will just use “<span class="quote">date-sent</span>”). You can also
-specify the “<span class="quote">last-</span>” prefix in addition to the “<span class="quote">reverse-</span>” prefix, but “<span class="quote">last-</span>”
-must come after “<span class="quote">reverse-</span>”. The “<span class="quote">last-</span>” prefix causes messages to be
-sorted against its siblings by which has the last descendant, using
-the rest of <a class="link" href="#sort-aux" title="3.272. sort_aux">$sort_aux</a> as an ordering. For instance,
-
-</p><pre class="screen">
-set sort_aux=last-date-received
-
-</pre><p>
-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 “<span class="quote"><code class="literal">set sort=reverse-threads</code></span>”.)
-</p><p>
-Note: For reversed <a class="link" href="#sort" title="3.270. sort">$sort</a>
-order <a class="link" href="#sort-aux" title="3.272. sort_aux">$sort_aux</a> is reversed again (which is not the right thing to do,
-but kept to not break any existing configuration setting).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-browser"></a>3.273. sort_browser</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: alpha</p></div><p>
-Specifies how to sort entries in the file browser. By default, the
-entries are sorted alphabetically. Valid values:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>alpha (alphabetically)
-</p></li><li><p>date
-</p></li><li><p>size
-</p></li><li><p>unsorted
-</p></li></ul></div><p>
-You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
-order (example: “<span class="quote"><code class="literal">set sort_browser=reverse-date</code></span>”).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-re"></a>3.274. sort_re</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable is only useful when sorting by threads with
-<a class="link" href="#strict-threads" title="3.280. strict_threads">$strict_threads</a> <span class="emphasis"><em>unset</em></span>. In that case, it changes the heuristic
-mutt uses to thread messages by subject. With <a class="link" href="#sort-re" title="3.274. sort_re">$sort_re</a> <span class="emphasis"><em>set</em></span>, mutt 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 <a class="link" href="#reply-regexp" title="3.240. reply_regexp">$reply_regexp</a>. With <a class="link" href="#sort-re" title="3.274. sort_re">$sort_re</a> <span class="emphasis"><em>unset</em></span>, mutt will attach
-the message whether or not this is the case, as long as the
-non-<a class="link" href="#reply-regexp" title="3.240. reply_regexp">$reply_regexp</a> parts of both messages are identical.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spam-separator"></a>3.275. spam_separator</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">,</code></span>”</p></div><p>
-This variable controls what happens when multiple spam headers
-are matched: if <span class="emphasis"><em>unset</em></span>, each successive header will overwrite any
-previous matches value for the spam label. If <span class="emphasis"><em>set</em></span>, each successive
-match will append to the previous, using this variable's value as a
-separator.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spoolfile"></a>3.276. spoolfile</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-If your spool mailbox is in a non-default place where Mutt cannot find
-it, you can specify its location with this variable. Mutt will
-automatically set this variable to the value of the environment
-variable <code class="literal">$MAIL</code> if it is not set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-chars"></a>3.277. status_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-*%A</code></span>”</p></div><p>
-Controls the characters used by the “<span class="quote">%r</span>” indicator in
-<a class="link" href="#status-format" title="3.278. status_format">$status_format</a>. 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 <code class="literal"><toggle-write></code> operation, bound by default to “<span class="quote">%</span>”). 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).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-format"></a>3.278. status_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-%r-Mutt: %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)---</code></span>”</p></div><p>
-Controls the format of the status line displayed in the “<span class="quote">index</span>”
-menu. This string is similar to <a class="link" href="#index-format" title="3.101. index_format">$index_format</a>, but has its own
-set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%b </span></dt><dd><p>number of mailboxes with new mail *
-</p></dd><dt><span class="term">%d </span></dt><dd><p>number of deleted messages *
-</p></dd><dt><span class="term">%f </span></dt><dd><p>the full pathname of the current mailbox
-</p></dd><dt><span class="term">%F </span></dt><dd><p>number of flagged messages *
-</p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
-</p></dd><dt><span class="term">%l </span></dt><dd><p>size (in bytes) of the current mailbox *
-</p></dd><dt><span class="term">%L </span></dt><dd><p>size (in bytes) of the messages shown
-(i.e., which match the current limit) *
-</p></dd><dt><span class="term">%m </span></dt><dd><p>the number of messages in the mailbox *
-</p></dd><dt><span class="term">%M </span></dt><dd><p>the number of messages shown (i.e., which match the current limit) *
-</p></dd><dt><span class="term">%n </span></dt><dd><p>number of new messages in the mailbox *
-</p></dd><dt><span class="term">%o </span></dt><dd><p>number of old unread messages *
-</p></dd><dt><span class="term">%p </span></dt><dd><p>number of postponed messages *
-</p></dd><dt><span class="term">%P </span></dt><dd><p>percentage of the way through the index
-</p></dd><dt><span class="term">%r </span></dt><dd><p>modified/read-only/won't-write/attach-message indicator,
-according to <a class="link" href="#status-chars" title="3.277. status_chars">$status_chars</a>
-</p></dd><dt><span class="term">%s </span></dt><dd><p>current sorting mode (<a class="link" href="#sort" title="3.270. sort">$sort</a>)
-</p></dd><dt><span class="term">%S </span></dt><dd><p>current aux sorting method (<a class="link" href="#sort-aux" title="3.272. sort_aux">$sort_aux</a>)
-</p></dd><dt><span class="term">%t </span></dt><dd><p>number of tagged messages *
-</p></dd><dt><span class="term">%u </span></dt><dd><p>number of unread messages *
-</p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
-</p></dd><dt><span class="term">%V </span></dt><dd><p>currently active limit pattern, if any *
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p><p>
-* = can be optionally printed if nonzero
-</p><p>
-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:
-</p><p>
-<code class="literal">%?<sequence_char>?<optional_string>?</code>
-</p><p>
-where <span class="emphasis"><em>sequence_char</em></span> is a character from the table above, and
-<span class="emphasis"><em>optional_string</em></span> is the string you would like printed if
-<span class="emphasis"><em>sequence_char</em></span> is nonzero. <span class="emphasis"><em>optional_string</em></span> <span class="bold"><strong>may</strong></span> contain
-other sequences as well as normal text, but you may <span class="bold"><strong>not</strong></span> nest
-optional strings.
-</p><p>
-Here is an example illustrating how to optionally print the number of
-new messages in a mailbox:
-</p><p>
-<code class="literal">%?n?%n new messages.?</code>
-</p><p>
-You can also switch between two strings using the following construct:
-</p><p>
-<code class="literal">%?<sequence_char>?<if_string>&<else_string>?</code>
-</p><p>
-If the value of <span class="emphasis"><em>sequence_char</em></span> is non-zero, <span class="emphasis"><em>if_string</em></span> will
-be expanded, otherwise <span class="emphasis"><em>else_string</em></span> will be expanded.
-</p><p>
-You can force the result of any <code class="literal">printf(3)</code>-like sequence to be lowercase
-by prefixing the sequence character with an underscore (“<span class="quote">_</span>”) sign.
-For example, if you want to display the local hostname in lowercase,
-you would use: “<span class="quote"><code class="literal">%_h</code></span>”.
-</p><p>
-If you prefix the sequence character with a colon (“<span class="quote">:</span>”) character, mutt
-will replace any dots in the expansion by underscores. This might be helpful
-with IMAP folders that don't like dots in folder names.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-on-top"></a>3.279. status_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable causes the “<span class="quote">status bar</span>” to be displayed on
-the first line of the screen rather than near the bottom. If <a class="link" href="#help" title="3.70. help">$help</a>
-is <span class="emphasis"><em>set</em></span>, too it'll be placed at the bottom.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="strict-threads"></a>3.280. strict_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, threading will only make use of the “<span class="quote">In-Reply-To</span>” and
-“<span class="quote">References:</span>” fields when you <a class="link" href="#sort" title="3.270. sort">$sort</a> by message threads. By
-default, messages with the same subject are grouped together in
-“<span class="quote">pseudo threads.</span>”. This may not always be desirable, such as in a
-personal mailbox where you might have several unrelated messages with
-the subjects like “<span class="quote">hi</span>” which will get grouped together. See also
-<a class="link" href="#sort-re" title="3.274. sort_re">$sort_re</a> for a less drastic way of controlling this
-behaviour.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="suspend"></a>3.281. suspend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mutt won't stop when the user presses the terminal's
-<span class="emphasis"><em>susp</em></span> key, usually “<span class="quote">^Z</span>”. This is useful if you run mutt
-inside an xterm using a command like “<span class="quote"><code class="literal">xterm -e mutt</code></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="text-flowed"></a>3.282. text_flowed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will generate “<span class="quote">format=flowed</span>” bodies with a content type
-of “<span class="quote"><code class="literal">text/plain; format=flowed</code></span>”.
-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.
-</p><p>
-Note that <a class="link" href="#indent-string" title="3.100. indent_string">$indent_string</a> is ignored when this option is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thread-received"></a>3.283. thread_received</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt uses the date received rather than the date sent
-to thread messages by subject.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thorough-search"></a>3.284. thorough_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Affects the <code class="literal">˜b</code> and <code class="literal">˜h</code> search operations described in
-section “<span class="quote"><a class="link" href="#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>”. If <span class="emphasis"><em>set</em></span>, the headers and body/attachments of
-messages to be searched are decoded before searching. If <span class="emphasis"><em>unset</em></span>,
-messages are searched as they appear in the folder.
-</p><p>
-Users searching attachments or for non-ASCII characters should <span class="emphasis"><em>set</em></span>
-this value because decoding also includes MIME parsing/decoding and possible
-character set conversions. Otherwise mutt will attempt to match against the
-raw message received (for example quoted-printable encoded or with encoded
-headers) which may lead to incorrect search results.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tilde"></a>3.285. tilde</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the internal-pager will pad blank lines to the bottom of the
-screen with a tilde (“<span class="quote">˜</span>”).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="time-inc"></a>3.286. time_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-Along with <a class="link" href="#read-inc" title="3.235. read_inc">$read_inc</a>, <a class="link" href="#write-inc" title="3.305. write_inc">$write_inc</a>, and <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a>, this
-variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than <a class="link" href="#time-inc" title="3.286. time_inc">$time_inc</a> milliseconds
-apart. This can improve throughput on systems with slow terminals,
-or when running mutt on a remote system.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="timeout"></a>3.287. timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 600</p></div><p>
-When Mutt is waiting for user input either idleing in menus or
-in an interactive prompt, Mutt would block until input is
-present. Depending on the context, this would prevent certain
-operations from working, like checking for new mail or keeping
-an IMAP connection alive.
-</p><p>
-This variable controls how many seconds Mutt will at most wait
-until it aborts waiting for input, performs these operations and
-continues to wait for input.
-</p><p>
-A value of zero or less will cause Mutt to never time out.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tmpdir"></a>3.288. tmpdir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable allows you to specify where Mutt will place its
-temporary files needed for displaying and composing messages. If
-this variable is not set, the environment variable <code class="literal">$TMPDIR</code> is
-used. If <code class="literal">$TMPDIR</code> is not set then “<span class="quote"><code class="literal">/tmp</code></span>” is used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="to-chars"></a>3.289. to_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal"> +TCFL</code></span>”</p></div><p>
-Controls the character used to indicate mail addressed to you. The
-first character is the one used when the mail is <span class="emphasis"><em>not</em></span> addressed to your
-address. The second is used when you are the only
-recipient of the message. The third is when your address
-appears in the “<span class="quote">To:</span>” header field, but you are not the only recipient of
-the message. The fourth character is used when your
-address is specified in the “<span class="quote">Cc:</span>” header field, but you are not the only
-recipient. The fifth character is used to indicate mail that was sent
-by <span class="emphasis"><em>you</em></span>. The sixth character is used to indicate when a mail
-was sent to a mailing-list you subscribe to.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="trash"></a>3.290. trash</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-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.
-</p><p>
-NOTE: When you delete a message in the trash folder, it is really
-deleted, so that you have a way to clean the trash.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tunnel"></a>3.291. tunnel</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Setting this variable will cause mutt 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/SMTP server. Example:
-
-</p><pre class="screen">
-set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-
-</pre><p>
-Note: For this example to work you must be able to log in to the remote
-machine without having to enter a password.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-8bitmime"></a>3.292. use_8bitmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-<span class="bold"><strong>Warning:</strong></span> do not set this variable unless you are using a version
-of sendmail which supports the <code class="literal">-B8BITMIME</code> flag (such as sendmail
-8.8.x) or you may not be able to send mail.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will invoke <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a> with the <code class="literal">-B8BITMIME</code>
-flag when sending 8-bit messages to enable ESMTP negotiation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-domain"></a>3.293. use_domain</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will qualify all local addresses (ones without the
-“<span class="quote">@host</span>” portion) with the value of <a class="link" href="#hostname" title="3.80. hostname">$hostname</a>. If <span class="emphasis"><em>unset</em></span>, no
-addresses will be qualified.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-envelope-from"></a>3.294. use_envelope_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will set the <span class="emphasis"><em>envelope</em></span> sender of the message.
-If <a class="link" href="#envelope-from-address" title="3.53. envelope_from_address">$envelope_from_address</a> is <span class="emphasis"><em>set</em></span>, it will be used as the sender
-address. If <span class="emphasis"><em>unset</em></span>, mutt will attempt to derive the sender from the
-“<span class="quote">From:</span>” header.
-</p><p>
-Note that this information is passed to sendmail command using the
-<code class="literal">-f</code> command line switch. Therefore setting this option is not useful
-if the <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a> variable already contains <code class="literal">-f</code> or if the
-executable pointed to by <a class="link" href="#sendmail" title="3.257. sendmail">$sendmail</a> doesn't support the <code class="literal">-f</code> switch.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-from"></a>3.295. use_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will generate the “<span class="quote">From:</span>” header field when
-sending messages. If <span class="emphasis"><em>unset</em></span>, no “<span class="quote">From:</span>” header field will be
-generated unless the user explicitly sets one using the “<span class="quote"><a class="link" href="#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-idn"></a>3.296. use_idn</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will show you international domain names decoded.
-Note: You can use IDNs for addresses even if this is <span class="emphasis"><em>unset</em></span>.
-This variable only affects decoding.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-ipv6"></a>3.297. use_ipv6</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will look for IPv6 addresses of hosts it tries to
-contact. If this option is <span class="emphasis"><em>unset</em></span>, Mutt will restrict itself to IPv4 addresses.
-Normally, the default should work.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="user-agent"></a>3.298. user_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will add a “<span class="quote">User-Agent:</span>” header to outgoing
-messages, indicating which version of mutt was used for composing
-them.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="visual"></a>3.299. visual</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Specifies the visual editor to invoke when the “<span class="quote"><code class="literal">˜v</code></span>” command is
-given in the builtin editor.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wait-key"></a>3.300. wait_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether Mutt will ask you to press a key after an external command
-has been invoked by these functions: <code class="literal"><shell-escape></code>,
-<code class="literal"><pipe-message></code>, <code class="literal"><pipe-entry></code>, <code class="literal"><print-message></code>,
-and <code class="literal"><print-entry></code> commands.
-</p><p>
-It is also used when viewing attachments with “<span class="quote"><a class="link" href="#auto-view" title="4. MIME Autoview">auto_view</a></span>”, provided
-that the corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag,
-and the external program is interactive.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will always ask for a key. When <span class="emphasis"><em>unset</em></span>, Mutt will wait
-for a key only if the external command returned a non-zero status.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="weed"></a>3.301. weed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will weed headers when displaying, forwarding,
-printing, or replying to messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap"></a>3.302. wrap</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-When set to a positive value, mutt will wrap text at <a class="link" href="#wrap" title="3.302. wrap">$wrap</a> characters.
-When set to a negative value, mutt will wrap text so that there are <a class="link" href="#wrap" title="3.302. wrap">$wrap</a>
-characters of empty space on the right side of the terminal.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap-search"></a>3.303. wrap_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether searches wrap around the end.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, searches will wrap around the first (or last) item. When
-<span class="emphasis"><em>unset</em></span>, incremental searches will not wrap.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrapmargin"></a>3.304. wrapmargin</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-(DEPRECATED) Equivalent to setting <a class="link" href="#wrap" title="3.302. wrap">$wrap</a> with a negative value.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-inc"></a>3.305. write_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-When writing a mailbox, a message will be printed every
-<a class="link" href="#write-inc" title="3.305. write_inc">$write_inc</a> messages to indicate progress. If set to 0, only a
-single message will be displayed before writing a mailbox.
-</p><p>
-Also see the <a class="link" href="#read-inc" title="3.235. read_inc">$read_inc</a>, <a class="link" href="#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="#time-inc" title="3.286. time_inc">$time_inc</a> variables and the
-“<span class="quote"><a class="link" href="#tuning" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-bcc"></a>3.306. write_bcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether mutt writes out the “<span class="quote">Bcc:</span>” header when preparing
-messages to be sent. Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see <a class="link" href="#smtp-url" title="3.269. smtp_url">$smtp_url</a>), this
-option does nothing: mutt will never write out the “<span class="quote">Bcc:</span>” header
-in this case.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, exim4 and postfix strip BCC headers by
-default. The above warning applies to exim3 users, see /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-icon"></a>3.307. xterm_icon</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">M%?n?AIL&ail?</code></span>”</p></div><p>
-Controls the format of the icon title, as long as xterm_set_titles
-is enabled. This string is identical in formatting to the one used by
-“<span class="quote"><a class="link" href="#status-format" title="3.278. status_format">$status_format</a></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-set-titles"></a>3.308. xterm_set_titles</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether mutt sets the xterm title bar and icon name
-(as long as you are in an appropriate terminal).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-title"></a>3.309. xterm_title</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?</code></span>”</p></div><p>
-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 “<span class="quote"><a class="link" href="#status-format" title="3.278. status_format">$status_format</a></span>”.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="functions"></a>4. Functions</h2></div></div></div><p>
-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 <a class="link" href="#bind" title="5. Changing the default key bindings">bind</a>
-command.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="generic_map"></a>4.1. generic menu</h3></div></div></div><p>
-The <span class="emphasis"><em>generic</em></span> menu is not a real menu, but specifies common functions
-(such as movement) available in all menus except for <span class="emphasis"><em>pager</em></span> and
-<span class="emphasis"><em>editor</em></span>. Changing settings for this menu will affect the default
-bindings for all menus (except as noted).
-</p><div class="table"><a id="generic_table"></a><p class="title"><b>Table 8.2. Default generic function bindings</b></p><div class="table-contents"><table summary="Default generic function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><top-page></code></td><td>H</td><td>move to the top of the page</td></tr><tr><td><code class="literal"><next-entry></code></td><td>j</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>k</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><bottom-page></code></td><td>L</td><td>move to the bottom of the page</td></tr><tr><td><code class="literal"><refresh></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><middle-page></code></td><td>M</td><td>move to the middle of the page</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><tag-entry></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><next-page></code></td><td>z</td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>Z</td><td>move to the previous page</td></tr><tr><td><code class="literal"><last-entry></code></td><td>*</td><td>move to the last entry</td></tr><tr><td><code class="literal"><first-entry></code></td><td>=</td><td>move to the first entry</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><next-line></code></td><td>></td><td>scroll down one line</td></tr><tr><td><code class="literal"><previous-line></code></td><td><</td><td>scroll up one line</td></tr><tr><td><code class="literal"><half-up></code></td><td>[</td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td>]</td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><tag-prefix></code></td><td>;</td><td>apply next function to tagged messages</td></tr><tr><td><code class="literal"><tag-prefix-cond></code></td><td> </td><td>apply next function ONLY to tagged messages</td></tr><tr><td><code class="literal"><end-cond></code></td><td> </td><td>end of conditional execution (noop)</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><select-entry></code></td><td><Return></td><td>select the current entry</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><current-top></code></td><td> </td><td>move entry to top of screen</td></tr><tr><td><code class="literal"><current-middle></code></td><td> </td><td>move entry to middle of screen</td></tr><tr><td><code class="literal"><current-bottom></code></td><td> </td><td>move entry to bottom of screen</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index_map"></a>4.2. index menu</h3></div></div></div><div class="table"><a id="index_table"></a><p class="title"><b>Table 8.3. Default index function bindings</b></p><div class="table-contents"><table summary="Default index function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><collapse-thread></code></td><td>Esc v</td><td>collapse/uncollapse current thread</td></tr><tr><td><code class="literal"><collapse-all></code></td><td>Esc V</td><td>collapse/uncollapse all threads</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-pattern></code></td><td>D</td><td>delete messages matching a pattern</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><fetch-mail></code></td><td>G</td><td>retrieve mail from POP server</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><limit></code></td><td>l</td><td>show only messages matching a pattern</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><toggle-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><toggle-write></code></td><td>%</td><td>toggle whether the mailbox will be rewritten</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><quit></code></td><td>q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><show-limit></code></td><td>Esc l</td><td>show currently active limit pattern</td></tr><tr><td><code class="literal"><sort-mailbox></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><tag-pattern></code></td><td>T</td><td>tag messages matching a pattern</td></tr><tr><td><code class="literal"><tag-subthread></code></td><td> </td><td>tag the current subthread</td></tr><tr><td><code class="literal"><tag-thread></code></td><td>Esc t</td><td>tag the current thread</td></tr><tr><td><code class="literal"><untag-pattern></code></td><td>^T</td><td>untag messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-pattern></code></td><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><set-flag></code></td><td>w</td><td>set a status flag on a message</td></tr><tr><td><code class="literal"><clear-flag></code></td><td>W</td><td>clear a status flag from a message</td></tr><tr><td><code class="literal"><display-message></code></td><td><Return></td><td>display a message</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><next-new-then-unread></code></td><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-new-then-unread></code></td><td>Esc <Tab></td><td>jump to the previous new or unread message</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager_map"></a>4.3. pager menu</h3></div></div></div><div class="table"><a id="pager_table"></a><p class="title"><b>Table 8.4. Default pager function bindings</b></p><div class="table-contents"><table summary="Default pager function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><next-entry></code></td><td>J</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>K</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><redraw-screen></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><mark-as-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><quit></code></td><td>Q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><skip-quoted></code></td><td>S</td><td>skip beyond quoted text</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><tag-message></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><toggle-quoted></code></td><td>T</td><td>toggle display of quoted text</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><search-toggle></code></td><td>\\</td><td>toggle search pattern coloring</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><next-page></code></td><td><Space></td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>-</td><td>move to the previous page</td></tr><tr><td><code class="literal"><top></code></td><td>^</td><td>jump to the top of the message</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><next-line></code></td><td><Return></td><td>scroll down one line</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><half-up></code></td><td> </td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td> </td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><previous-line></code></td><td> </td><td>scroll up one line</td></tr><tr><td><code class="literal"><bottom></code></td><td> </td><td>jump to the bottom of the message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias_map"></a>4.4. alias menu</h3></div></div></div><div class="table"><a id="alias_table"></a><p class="title"><b>Table 8.5. Default alias function bindings</b></p><div class="table-contents"><table summary="Default alias function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query_map"></a>4.5. query menu</h3></div></div></div><div class="table"><a id="query_table"></a><p class="title"><b>Table 8.6. Default query function bindings</b></p><div class="table-contents"><table summary="Default query function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><query-append></code></td><td>A</td><td>append new query results to current results</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach_map"></a>4.6. attach menu</h3></div></div></div><div class="table"><a id="attach_table"></a><p class="title"><b>Table 8.7. Default attach function bindings</b></p><div class="table-contents"><table summary="Default attach function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><print-entry></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><save-entry></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><view-mailcap></code></td><td>m</td><td>force viewing of attachment using mailcap</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><view-text></code></td><td>T</td><td>view attachment as text</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><collapse-parts></code></td><td>v</td><td>Toggle display of subparts</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose_map"></a>4.7. compose menu</h3></div></div></div><div class="table"><a id="compose_table"></a><p class="title"><b>Table 8.8. Default compose function bindings</b></p><div class="table-contents"><table summary="Default compose function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><attach-file></code></td><td>a</td><td>attach file(s) to this message</td></tr><tr><td><code class="literal"><attach-message></code></td><td>A</td><td>attach message(s) to this message</td></tr><tr><td><code class="literal"><edit-bcc></code></td><td>b</td><td>edit the BCC list</td></tr><tr><td><code class="literal"><edit-cc></code></td><td>c</td><td>edit the CC list</td></tr><tr><td><code class="literal"><copy-file></code></td><td>C</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><detach-file></code></td><td>D</td><td>delete the current entry</td></tr><tr><td><code class="literal"><toggle-disposition></code></td><td>^D</td><td>toggle disposition between inline/attachment</td></tr><tr><td><code class="literal"><edit-description></code></td><td>d</td><td>edit attachment description</td></tr><tr><td><code class="literal"><edit-message></code></td><td>e</td><td>edit the message</td></tr><tr><td><code class="literal"><edit-headers></code></td><td>E</td><td>edit the message with headers</td></tr><tr><td><code class="literal"><edit-file></code></td><td>^X e</td><td>edit the file to be attached</td></tr><tr><td><code class="literal"><edit-encoding></code></td><td>^E</td><td>edit attachment transfer-encoding</td></tr><tr><td><code class="literal"><edit-from></code></td><td>Esc f</td><td>edit the from field</td></tr><tr><td><code class="literal"><edit-fcc></code></td><td>f</td><td>enter a file to save a copy of this message in</td></tr><tr><td><code class="literal"><filter-entry></code></td><td>F</td><td>filter attachment through a shell command</td></tr><tr><td><code class="literal"><get-attachment></code></td><td>G</td><td>get a temporary copy of an attachment</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><ispell></code></td><td>i</td><td>run ispell on the message</td></tr><tr><td><code class="literal"><print-entry></code></td><td>l</td><td>print the current entry</td></tr><tr><td><code class="literal"><edit-mime></code></td><td>m</td><td>edit attachment using mailcap entry</td></tr><tr><td><code class="literal"><new-mime></code></td><td>n</td><td>compose new attachment using mailcap entry</td></tr><tr><td><code class="literal"><postpone-message></code></td><td>P</td><td>save this message to send later</td></tr><tr><td><code class="literal"><edit-reply-to></code></td><td>r</td><td>edit the Reply-To field</td></tr><tr><td><code class="literal"><rename-file></code></td><td>R</td><td>rename/move an attached file</td></tr><tr><td><code class="literal"><edit-subject></code></td><td>s</td><td>edit the subject of this message</td></tr><tr><td><code class="literal"><edit-to></code></td><td>t</td><td>edit the TO list</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^T</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><write-fcc></code></td><td>w</td><td>write the message to a folder</td></tr><tr><td><code class="literal"><toggle-unlink></code></td><td>u</td><td>toggle whether to delete file after sending it</td></tr><tr><td><code class="literal"><toggle-recode></code></td><td> </td><td>toggle recoding of this attachment</td></tr><tr><td><code class="literal"><update-encoding></code></td><td>U</td><td>update an attachment's encoding info</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><send-message></code></td><td>y</td><td>send the message</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><attach-key></code></td><td>Esc k</td><td>attach a PGP public key</td></tr><tr><td><code class="literal"><pgp-menu></code></td><td>p</td><td>show PGP options</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><smime-menu></code></td><td>S</td><td>show S/MIME options</td></tr><tr><td><code class="literal"><mix></code></td><td>M</td><td>send the message through a mixmaster remailer chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone_map"></a>4.8. postpone menu</h3></div></div></div><div class="table"><a id="postpone_table"></a><p class="title"><b>Table 8.9. Default postpone function bindings</b></p><div class="table-contents"><table summary="Default postpone function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="browser_map"></a>4.9. browser menu</h3></div></div></div><div class="table"><a id="browser_table"></a><p class="title"><b>Table 8.10. Default browser function bindings</b></p><div class="table-contents"><table summary="Default browser function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><change-dir></code></td><td>c</td><td>change directories</td></tr><tr><td><code class="literal"><display-filename></code></td><td>@</td><td>display the currently selected file's name</td></tr><tr><td><code class="literal"><enter-mask></code></td><td>m</td><td>enter a file mask</td></tr><tr><td><code class="literal"><sort></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><select-new></code></td><td>N</td><td>select a new file in this directory</td></tr><tr><td><code class="literal"><check-new></code></td><td> </td><td>check mailboxes for new mail</td></tr><tr><td><code class="literal"><toggle-mailboxes></code></td><td><Tab></td><td>toggle whether to browse mailboxes or all files</td></tr><tr><td><code class="literal"><view-file></code></td><td><Space></td><td>view file</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><create-mailbox></code></td><td>C</td><td>create a new mailbox (IMAP only)</td></tr><tr><td><code class="literal"><delete-mailbox></code></td><td>d</td><td>delete the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><rename-mailbox></code></td><td>r</td><td>rename the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><subscribe></code></td><td>s</td><td>subscribe to current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><unsubscribe></code></td><td>u</td><td>unsubscribe from current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><toggle-subscribed></code></td><td>T</td><td>toggle view all/subscribed mailboxes (IMAP only)</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp_map"></a>4.10. pgp menu</h3></div></div></div><div class="table"><a id="pgp_table"></a><p class="title"><b>Table 8.11. Default pgp function bindings</b></p><div class="table-contents"><table summary="Default pgp function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime_map"></a>4.11. smime menu</h3></div></div></div><div class="table"><a id="smime_table"></a><p class="title"><b>Table 8.12. Default smime function bindings</b></p><div class="table-contents"><table summary="Default smime function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix_map"></a>4.12. mix menu</h3></div></div></div><div class="table"><a id="mix_table"></a><p class="title"><b>Table 8.13. Default mix function bindings</b></p><div class="table-contents"><table summary="Default mix function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><accept></code></td><td><Return></td><td>Accept the chain constructed</td></tr><tr><td><code class="literal"><append></code></td><td>a</td><td>Append a remailer to the chain</td></tr><tr><td><code class="literal"><insert></code></td><td>i</td><td>Insert a remailer into the chain</td></tr><tr><td><code class="literal"><delete></code></td><td>d</td><td>Delete a remailer from the chain</td></tr><tr><td><code class="literal"><chain-prev></code></td><td><Left></td><td>Select the previous element of the chain</td></tr><tr><td><code class="literal"><chain-next></code></td><td><Right></td><td>Select the next element of the chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor_map"></a>4.13. editor menu</h3></div></div></div><div class="table"><a id="editor_table"></a><p class="title"><b>Table 8.14. Default editor function bindings</b></p><div class="table-contents"><table summary="Default editor function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bol></code></td><td>^A</td><td>jump to the beginning of the line</td></tr><tr><td><code class="literal"><backward-char></code></td><td>^B</td><td>move the cursor one character to the left</td></tr><tr><td><code class="literal"><backward-word></code></td><td>Esc b</td><td>move the cursor to the beginning of the word</td></tr><tr><td><code class="literal"><capitalize-word></code></td><td>Esc c</td><td>capitalize the word</td></tr><tr><td><code class="literal"><downcase-word></code></td><td>Esc l</td><td>convert the word to lower case</td></tr><tr><td><code class="literal"><upcase-word></code></td><td>Esc u</td><td>convert the word to upper case</td></tr><tr><td><code class="literal"><delete-char></code></td><td>^D</td><td>delete the char under the cursor</td></tr><tr><td><code class="literal"><eol></code></td><td>^E</td><td>jump to the end of the line</td></tr><tr><td><code class="literal"><forward-char></code></td><td>^F</td><td>move the cursor one character to the right</td></tr><tr><td><code class="literal"><forward-word></code></td><td>Esc f</td><td>move the cursor to the end of the word</td></tr><tr><td><code class="literal"><backspace></code></td><td><Backspace></td><td>delete the char in front of the cursor</td></tr><tr><td><code class="literal"><kill-eol></code></td><td>^K</td><td>delete chars from cursor to end of line</td></tr><tr><td><code class="literal"><kill-eow></code></td><td>Esc d</td><td>delete chars from the cursor to the end of the word</td></tr><tr><td><code class="literal"><kill-line></code></td><td>^U</td><td>delete all chars on the line</td></tr><tr><td><code class="literal"><quote-char></code></td><td>^V</td><td>quote the next typed key</td></tr><tr><td><code class="literal"><kill-word></code></td><td>^W</td><td>delete the word in front of the cursor</td></tr><tr><td><code class="literal"><complete></code></td><td><Tab></td><td>complete filename or alias</td></tr><tr><td><code class="literal"><complete-query></code></td><td>^T</td><td>complete address with query</td></tr><tr><td><code class="literal"><buffy-cycle></code></td><td><Space></td><td>cycle among incoming mailboxes</td></tr><tr><td><code class="literal"><history-up></code></td><td> </td><td>scroll up through the history list</td></tr><tr><td><code class="literal"><history-down></code></td><td> </td><td>scroll down through the history list</td></tr><tr><td><code class="literal"><transpose-chars></code></td><td> </td><td>transpose character under cursor with previous</td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="miscellany"></a>Chapter 9. Miscellany</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="#about">2. About this document</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="acknowledgements"></a>1. Acknowledgements</h2></div></div></div><p>
-Kari Hurtta <code class="email"><<a class="email" href="mailto:kari.hurtta@fmi.fi">kari.hurtta@fmi.fi</a>></code>
-co-developed the original MIME parsing code back in the ELM-ME days.
-</p><p>
-The following people have been very helpful to the development of Mutt:
-</p><div class="itemizedlist"><ul type="disc"><li><p>Vikas Agnihotri <code class="email"><<a class="email" href="mailto:vikasa@writeme.com">vikasa@writeme.com</a>></code></p></li><li><p>Francois Berjon <code class="email"><<a class="email" href="mailto:Francois.Berjon@aar.alcatel-alsthom.fr">Francois.Berjon@aar.alcatel-alsthom.fr</a>></code></p></li><li><p>Aric Blumer <code class="email"><<a class="email" href="mailto:aric@fore.com">aric@fore.com</a>></code></p></li><li><p>John Capo <code class="email"><<a class="email" href="mailto:jc@irbs.com">jc@irbs.com</a>></code></p></li><li><p>David Champion <code class="email"><<a class="email" href="mailto:dgc@uchicago.edu">dgc@uchicago.edu</a>></code></p></li><li><p>Brendan Cully <code class="email"><<a class="email" href="mailto:brendan@kublai.com">brendan@kublai.com</a>></code></p></li><li><p>Liviu Daia <code class="email"><<a class="email" href="mailto:daia@stoilow.imar.ro">daia@stoilow.imar.ro</a>></code></p></li><li><p>Thomas E. Dickey <code class="email"><<a class="email" href="mailto:dickey@herndon4.his.com">dickey@herndon4.his.com</a>></code></p></li><li><p>David DeSimone <code class="email"><<a class="email" href="mailto:fox@convex.hp.com">fox@convex.hp.com</a>></code></p></li><li><p>Nickolay N. Dudorov <code class="email"><<a class="email" href="mailto:nnd@wint.itfs.nsk.su">nnd@wint.itfs.nsk.su</a>></code></p></li><li><p>Ruslan Ermilov <code class="email"><<a class="email" href="mailto:ru@freebsd.org">ru@freebsd.org</a>></code></p></li><li><p>Edmund Grimley Evans <code class="email"><<a class="email" href="mailto:edmundo@rano.org">edmundo@rano.org</a>></code></p></li><li><p>Michael Finken <code class="email"><<a class="email" href="mailto:finken@conware.de">finken@conware.de</a>></code></p></li><li><p>Sven Guckes <code class="email"><<a class="email" href="mailto:guckes@math.fu-berlin.de">guckes@math.fu-berlin.de</a>></code></p></li><li><p>Lars Hecking <code class="email"><<a class="email" href="mailto:lhecking@nmrc.ie">lhecking@nmrc.ie</a>></code></p></li><li><p>Mark Holloman <code class="email"><<a class="email" href="mailto:holloman@nando.net">holloman@nando.net</a>></code></p></li><li><p>Andreas Holzmann <code class="email"><<a class="email" href="mailto:holzmann@fmi.uni-passau.de">holzmann@fmi.uni-passau.de</a>></code></p></li><li><p>Marco d'Itri <code class="email"><<a class="email" href="mailto:md@linux.it">md@linux.it</a>></code></p></li><li><p>Björn Jacke <code class="email"><<a class="email" href="mailto:bjacke@suse.com">bjacke@suse.com</a>></code></p></li><li><p>Byrial Jensen <code class="email"><<a class="email" href="mailto:byrial@image.dk">byrial@image.dk</a>></code></p></li><li><p>David Jeske <code class="email"><<a class="email" href="mailto:jeske@igcom.net">jeske@igcom.net</a>></code></p></li><li><p>Christophe Kalt <code class="email"><<a class="email" href="mailto:kalt@hugo.int-evry.fr">kalt@hugo.int-evry.fr</a>></code></p></li><li><p>Tommi Komulainen <code class="email"><<a class="email" href="mailto:Tommi.Komulainen@iki.fi">Tommi.Komulainen@iki.fi</a>></code></p></li><li><p>Felix von Leitner (a.k.a “<span class="quote">Fefe</span>”) <code class="email"><<a class="email" href="mailto:leitner@math.fu-berlin.de">leitner@math.fu-berlin.de</a>></code></p></li><li><p>Brandon Long <code class="email"><<a class="email" href="mailto:blong@fiction.net">blong@fiction.net</a>></code></p></li><li><p>Jimmy Mäkelä <code class="email"><<a class="email" href="mailto:jmy@flashback.net">jmy@flashback.net</a>></code></p></li><li><p>Lars Marowsky-Bree <code class="email"><<a class="email" href="mailto:lmb@pointer.in-minden.de">lmb@pointer.in-minden.de</a>></code></p></li><li><p>Thomas “<span class="quote">Mike</span>” Michlmayr <code class="email"><<a class="email" href="mailto:mike@cosy.sbg.ac.at">mike@cosy.sbg.ac.at</a>></code></p></li><li><p>Andrew W. Nosenko <code class="email"><<a class="email" href="mailto:awn@bcs.zp.ua">awn@bcs.zp.ua</a>></code></p></li><li><p>David O'Brien <code class="email"><<a class="email" href="mailto:obrien@Nuxi.cs.ucdavis.edu">obrien@Nuxi.cs.ucdavis.edu</a>></code></p></li><li><p>Clint Olsen <code class="email"><<a class="email" href="mailto:olsenc@ichips.intel.com">olsenc@ichips.intel.com</a>></code></p></li><li><p>Park Myeong Seok <code class="email"><<a class="email" href="mailto:pms@romance.kaist.ac.kr">pms@romance.kaist.ac.kr</a>></code></p></li><li><p>Thomas Parmelan <code class="email"><<a class="email" href="mailto:tom@ankh.fr.eu.org">tom@ankh.fr.eu.org</a>></code></p></li><li><p>Ollivier Robert <code class="email"><<a class="email" href="mailto:roberto@keltia.freenix.fr">roberto@keltia.freenix.fr</a>></code></p></li><li><p>Thomas Roessler <code class="email"><<a class="email" href="mailto:roessler@does-not-exist.org">roessler@does-not-exist.org</a>></code></p></li><li><p>Roland Rosenfeld <code class="email"><<a class="email" href="mailto:roland@spinnaker.de">roland@spinnaker.de</a>></code></p></li><li><p>Rocco Rutte <code class="email"><<a class="email" href="mailto:pdmef@gmx.net">pdmef@gmx.net</a>></code></p></li><li><p>TAKIZAWA Takashi <code class="email"><<a class="email" href="mailto:taki@luna.email.ne.jp">taki@luna.email.ne.jp</a>></code></p></li><li><p>Allain Thivillon <code class="email"><<a class="email" href="mailto:Allain.Thivillon@alma.fr">Allain.Thivillon@alma.fr</a>></code></p></li><li><p>Gero Treuner <code class="email"><<a class="email" href="mailto:gero@70t.de">gero@70t.de</a>></code></p></li><li><p>Vsevolod Volkov <code class="email"><<a class="email" href="mailto:vvv@lucky.net">vvv@lucky.net</a>></code></p></li><li><p>Ken Weinert <code class="email"><<a class="email" href="mailto:kenw@ihs.com">kenw@ihs.com</a>></code></p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="about"></a>2. About this document</h2></div></div></div><p>
-This document was written in <a class="ulink" href="http://docbook.sourceforge.net" target="_top">DocBook</a>,
-and then rendered using the <a class="ulink" href="http://xmlsoft.org/XSLT/" target="_top">Gnome XSLT toolkit</a>.
-</p></div></div></div></body></html>
+++ /dev/null
- The Mutt E-Mail Client
-
- Michael Elkins
-
- <me@cs.hmc.edu>
-
- version 1.5.19 (2009-01-05)
-
- Abstract
-
- "All mail clients suck. This one just sucks less." -me, circa 1995
-
- ----------------------------------------------------------------------
-
- Table of Contents
-
- 1. Introduction
-
- 1. Mutt Home Page
-
- 2. Mailing Lists
-
- 3. Software Distribution Sites
-
- 4. Mutt online resources
-
- 5. Contributing to Mutt
-
- 6. Typograhical conventions
-
- 7. Copyright
-
- 2. Getting Started
-
- 1. Core concepts
-
- 2. Moving Around in Menus
-
- 3. Editing Input Fields
-
- 3.1. Introduction
-
- 3.2. History
-
- 4. Reading Mail - The Index and Pager
-
- 4.1. The Message Index
-
- 4.2. The Pager
-
- 4.3. Threaded Mode
-
- 4.4. Miscellaneous Functions
-
- 5. Sending Mail
-
- 5.1. Introduction
-
- 5.2. Editing the message header
-
- 5.3. Sending cryptographically signed/encrypted
- messages
-
- 5.4. Sending anonymous messages via mixmaster
-
- 5.5. Sending format=flowed messages
-
- 6. Forwarding and Bouncing Mail
-
- 7. Postponing Mail
-
- 3. Configuration
-
- 1. Location of initialization files
-
- 2. Syntax of Initialization Files
-
- 3. Address groups
-
- 4. Defining/Using aliases
-
- 5. Changing the default key bindings
-
- 6. Defining aliases for character sets
-
- 7. Setting variables based upon mailbox
-
- 8. Keyboard macros
-
- 9. Using color and mono video attributes
-
- 10. Message header display
-
- 11. Alternative addresses
-
- 12. Mailing lists
-
- 13. Using Multiple spool mailboxes
-
- 14. Monitoring incoming mail
-
- 15. User defined headers
-
- 16. Specify default save mailbox
-
- 17. Specify default Fcc: mailbox when composing
-
- 18. Specify default save filename and default Fcc: mailbox at
- once
-
- 19. Change settings based upon message recipients
-
- 20. Change settings before formatting a message
-
- 21. Choosing the cryptographic key of the recipient
-
- 22. Adding key sequences to the keyboard buffer
-
- 23. Executing functions
-
- 24. Message Scoring
-
- 25. Spam detection
-
- 26. Setting and Querying Variables
-
- 26.1. Commands
-
- 26.2. User-defined variables
-
- 27. Reading initialization commands from another file
-
- 28. Configuring features conditionnaly
-
- 29. Removing hooks
-
- 30. Format Strings
-
- 30.1. Basic usage
-
- 30.2. Filters
-
- 4. Advanced Usage
-
- 1. Regular Expressions
-
- 2. Patterns: Searching, Limiting and Tagging
-
- 2.1. Pattern Modifier
-
- 2.2. Simple Patterns
-
- 2.3. Complex Patterns
-
- 2.4. Searching by Date
-
- 3. Using Tags
-
- 4. Using Hooks
-
- 4.1. Message Matching in Hooks
-
- 5. External Address Queries
-
- 6. Mailbox Formats
-
- 7. Mailbox Shortcuts
-
- 8. Handling Mailing Lists
-
- 9. Handling multiple folders
-
- 10. Editing threads
-
- 10.1. Linking threads
-
- 10.2. Breaking threads
-
- 11. Delivery Status Notification (DSN) Support
-
- 12. Start a WWW Browser on URLs
-
- 5. Mutt's MIME Support
-
- 1. Using MIME in Mutt
-
- 1.1. Viewing MIME messages in the pager
-
- 1.2. The Attachment Menu
-
- 1.3. The Compose Menu
-
- 2. MIME Type configuration with mime.types
-
- 3. MIME Viewer configuration with mailcap
-
- 3.1. The Basics of the mailcap file
-
- 3.2. Secure use of mailcap
-
- 3.3. Advanced mailcap Usage
-
- 3.4. Example mailcap files
-
- 4. MIME Autoview
-
- 5. MIME Multipart/Alternative
-
- 6. Attachment Searching and Counting
-
- 7. MIME Lookup
-
- 6. Optional features
-
- 1. General notes
-
- 1.1. Enabling/disabling features
-
- 1.2. URL syntax
-
- 2. SSL/TLS Support
-
- 3. POP3 Support
-
- 4. IMAP Support
-
- 4.1. The Folder Browser
-
- 4.2. Authentication
-
- 5. SMTP Support
-
- 6. Managing multiple accounts
-
- 7. Local caching
-
- 7.1. Header caching
-
- 7.2. Body caching
-
- 7.3. Maintenance
-
- 8. Exact address generation
-
- 7. Performance tuning
-
- 1. Reading and writing mailboxes
-
- 2. Reading messages from remote folders
-
- 3. Searching and limiting
-
- 8. Reference
-
- 1. Command line options
-
- 2. Configuration Commands
-
- 3. Configuration variables
-
- 3.1. abort_nosubject
-
- 3.2. abort_unmodified
-
- 3.3. alias_file
-
- 3.4. alias_format
-
- 3.5. allow_8bit
-
- 3.6. allow_ansi
-
- 3.7. arrow_cursor
-
- 3.8. ascii_chars
-
- 3.9. askbcc
-
- 3.10. askcc
-
- 3.11. assumed_charset
-
- 3.12. attach_charset
-
- 3.13. attach_format
-
- 3.14. attach_sep
-
- 3.15. attach_split
-
- 3.16. attribution
-
- 3.17. autoedit
-
- 3.18. auto_tag
-
- 3.19. beep
-
- 3.20. beep_new
-
- 3.21. bounce
-
- 3.22. bounce_delivered
-
- 3.23. braille_friendly
-
- 3.24. check_mbox_size
-
- 3.25. charset
-
- 3.26. check_new
-
- 3.27. collapse_unread
-
- 3.28. uncollapse_jump
-
- 3.29. compose_format
-
- 3.30. config_charset
-
- 3.31. confirmappend
-
- 3.32. confirmcreate
-
- 3.33. connect_timeout
-
- 3.34. content_type
-
- 3.35. copy
-
- 3.36. crypt_use_gpgme
-
- 3.37. crypt_use_pka
-
- 3.38. crypt_autopgp
-
- 3.39. crypt_autosmime
-
- 3.40. date_format
-
- 3.41. default_hook
-
- 3.42. delete
-
- 3.43. delete_untag
-
- 3.44. digest_collapse
-
- 3.45. display_filter
-
- 3.46. dotlock_program
-
- 3.47. dsn_notify
-
- 3.48. dsn_return
-
- 3.49. duplicate_threads
-
- 3.50. edit_headers
-
- 3.51. editor
-
- 3.52. encode_from
-
- 3.53. envelope_from_address
-
- 3.54. escape
-
- 3.55. fast_reply
-
- 3.56. fcc_attach
-
- 3.57. fcc_clear
-
- 3.58. folder
-
- 3.59. folder_format
-
- 3.60. followup_to
-
- 3.61. force_name
-
- 3.62. forward_decode
-
- 3.63. forward_edit
-
- 3.64. forward_format
-
- 3.65. forward_quote
-
- 3.66. from
-
- 3.67. gecos_mask
-
- 3.68. hdrs
-
- 3.69. header
-
- 3.70. help
-
- 3.71. hidden_host
-
- 3.72. hide_limited
-
- 3.73. hide_missing
-
- 3.74. hide_thread_subject
-
- 3.75. hide_top_limited
-
- 3.76. hide_top_missing
-
- 3.77. history
-
- 3.78. history_file
-
- 3.79. honor_followup_to
-
- 3.80. hostname
-
- 3.81. ignore_linear_white_space
-
- 3.82. ignore_list_reply_to
-
- 3.83. imap_authenticators
-
- 3.84. imap_check_subscribed
-
- 3.85. imap_delim_chars
-
- 3.86. imap_headers
-
- 3.87. imap_idle
-
- 3.88. imap_keepalive
-
- 3.89. imap_list_subscribed
-
- 3.90. imap_login
-
- 3.91. imap_pass
-
- 3.92. imap_passive
-
- 3.93. imap_peek
-
- 3.94. imap_pipeline_depth
-
- 3.95. imap_servernoise
-
- 3.96. imap_user
-
- 3.97. implicit_autoview
-
- 3.98. include
-
- 3.99. include_onlyfirst
-
- 3.100. indent_string
-
- 3.101. index_format
-
- 3.102. ispell
-
- 3.103. keep_flagged
-
- 3.104. locale
-
- 3.105. mail_check
-
- 3.106. mailcap_path
-
- 3.107. mailcap_sanitize
-
- 3.108. maildir_mtime
-
- 3.109. header_cache
-
- 3.110. maildir_header_cache_verify
-
- 3.111. header_cache_pagesize
-
- 3.112. maildir_trash
-
- 3.113. mark_old
-
- 3.114. markers
-
- 3.115. mask
-
- 3.116. mbox
-
- 3.117. mbox_type
-
- 3.118. metoo
-
- 3.119. menu_context
-
- 3.120. menu_move_off
-
- 3.121. menu_scroll
-
- 3.122. meta_key
-
- 3.123. mh_purge
-
- 3.124. mh_seq_flagged
-
- 3.125. mh_seq_replied
-
- 3.126. mh_seq_unseen
-
- 3.127. mime_forward
-
- 3.128. mime_forward_decode
-
- 3.129. mime_forward_rest
-
- 3.130. mix_entry_format
-
- 3.131. mixmaster
-
- 3.132. move
-
- 3.133. message_cachedir
-
- 3.134. message_cache_clean
-
- 3.135. message_format
-
- 3.136. narrow_tree
-
- 3.137. net_inc
-
- 3.138. pager
-
- 3.139. pager_context
-
- 3.140. pager_format
-
- 3.141. pager_index_lines
-
- 3.142. pager_stop
-
- 3.143. crypt_autosign
-
- 3.144. crypt_autoencrypt
-
- 3.145. pgp_ignore_subkeys
-
- 3.146. crypt_replyencrypt
-
- 3.147. crypt_replysign
-
- 3.148. crypt_replysignencrypted
-
- 3.149. crypt_timestamp
-
- 3.150. pgp_use_gpg_agent
-
- 3.151. crypt_verify_sig
-
- 3.152. smime_is_default
-
- 3.153. smime_ask_cert_label
-
- 3.154. smime_decrypt_use_default_key
-
- 3.155. pgp_entry_format
-
- 3.156. pgp_good_sign
-
- 3.157. pgp_check_exit
-
- 3.158. pgp_long_ids
-
- 3.159. pgp_retainable_sigs
-
- 3.160. pgp_autoinline
-
- 3.161. pgp_replyinline
-
- 3.162. pgp_show_unusable
-
- 3.163. pgp_sign_as
-
- 3.164. pgp_strict_enc
-
- 3.165. pgp_timeout
-
- 3.166. pgp_sort_keys
-
- 3.167. pgp_mime_auto
-
- 3.168. pgp_auto_decode
-
- 3.169. pgp_mime_signature_filename
-
- 3.170. pgp_mime_signature_description
-
- 3.171. pgp_decode_command
-
- 3.172. pgp_getkeys_command
-
- 3.173. pgp_verify_command
-
- 3.174. pgp_decrypt_command
-
- 3.175. pgp_clearsign_command
-
- 3.176. pgp_sign_command
-
- 3.177. pgp_encrypt_sign_command
-
- 3.178. pgp_encrypt_only_command
-
- 3.179. pgp_import_command
-
- 3.180. pgp_export_command
-
- 3.181. pgp_verify_key_command
-
- 3.182. pgp_list_secring_command
-
- 3.183. pgp_list_pubring_command
-
- 3.184. forward_decrypt
-
- 3.185. smime_timeout
-
- 3.186. smime_encrypt_with
-
- 3.187. smime_keys
-
- 3.188. smime_ca_location
-
- 3.189. smime_certificates
-
- 3.190. smime_decrypt_command
-
- 3.191. smime_verify_command
-
- 3.192. smime_verify_opaque_command
-
- 3.193. smime_sign_command
-
- 3.194. smime_sign_opaque_command
-
- 3.195. smime_encrypt_command
-
- 3.196. smime_pk7out_command
-
- 3.197. smime_get_cert_command
-
- 3.198. smime_get_signer_cert_command
-
- 3.199. smime_import_cert_command
-
- 3.200. smime_get_cert_email_command
-
- 3.201. smime_default_key
-
- 3.202. ssl_client_cert
-
- 3.203. ssl_force_tls
-
- 3.204. ssl_starttls
-
- 3.205. certificate_file
-
- 3.206. ssl_use_sslv3
-
- 3.207. ssl_use_tlsv1
-
- 3.208. ssl_min_dh_prime_bits
-
- 3.209. ssl_ca_certificates_file
-
- 3.210. pipe_split
-
- 3.211. pipe_decode
-
- 3.212. pipe_sep
-
- 3.213. pop_authenticators
-
- 3.214. pop_auth_try_all
-
- 3.215. pop_checkinterval
-
- 3.216. pop_delete
-
- 3.217. pop_host
-
- 3.218. pop_last
-
- 3.219. pop_reconnect
-
- 3.220. pop_user
-
- 3.221. pop_pass
-
- 3.222. post_indent_string
-
- 3.223. postpone
-
- 3.224. postponed
-
- 3.225. preconnect
-
- 3.226. print
-
- 3.227. print_command
-
- 3.228. print_decode
-
- 3.229. print_split
-
- 3.230. prompt_after
-
- 3.231. query_command
-
- 3.232. query_format
-
- 3.233. quit
-
- 3.234. quote_regexp
-
- 3.235. read_inc
-
- 3.236. read_only
-
- 3.237. realname
-
- 3.238. recall
-
- 3.239. record
-
- 3.240. reply_regexp
-
- 3.241. reply_self
-
- 3.242. reply_to
-
- 3.243. resolve
-
- 3.244. reverse_alias
-
- 3.245. reverse_name
-
- 3.246. reverse_realname
-
- 3.247. rfc2047_parameters
-
- 3.248. save_address
-
- 3.249. save_empty
-
- 3.250. save_history
-
- 3.251. save_name
-
- 3.252. score
-
- 3.253. score_threshold_delete
-
- 3.254. score_threshold_flag
-
- 3.255. score_threshold_read
-
- 3.256. send_charset
-
- 3.257. sendmail
-
- 3.258. sendmail_wait
-
- 3.259. shell
-
- 3.260. sig_dashes
-
- 3.261. sig_on_top
-
- 3.262. signature
-
- 3.263. simple_search
-
- 3.264. smart_wrap
-
- 3.265. smileys
-
- 3.266. sleep_time
-
- 3.267. smtp_authenticators
-
- 3.268. smtp_pass
-
- 3.269. smtp_url
-
- 3.270. sort
-
- 3.271. sort_alias
-
- 3.272. sort_aux
-
- 3.273. sort_browser
-
- 3.274. sort_re
-
- 3.275. spam_separator
-
- 3.276. spoolfile
-
- 3.277. status_chars
-
- 3.278. status_format
-
- 3.279. status_on_top
-
- 3.280. strict_threads
-
- 3.281. suspend
-
- 3.282. text_flowed
-
- 3.283. thread_received
-
- 3.284. thorough_search
-
- 3.285. tilde
-
- 3.286. time_inc
-
- 3.287. timeout
-
- 3.288. tmpdir
-
- 3.289. to_chars
-
- 3.290. trash
-
- 3.291. tunnel
-
- 3.292. use_8bitmime
-
- 3.293. use_domain
-
- 3.294. use_envelope_from
-
- 3.295. use_from
-
- 3.296. use_idn
-
- 3.297. use_ipv6
-
- 3.298. user_agent
-
- 3.299. visual
-
- 3.300. wait_key
-
- 3.301. weed
-
- 3.302. wrap
-
- 3.303. wrap_search
-
- 3.304. wrapmargin
-
- 3.305. write_inc
-
- 3.306. write_bcc
-
- 3.307. xterm_icon
-
- 3.308. xterm_set_titles
-
- 3.309. xterm_title
-
- 4. Functions
-
- 4.1. generic menu
-
- 4.2. index menu
-
- 4.3. pager menu
-
- 4.4. alias menu
-
- 4.5. query menu
-
- 4.6. attach menu
-
- 4.7. compose menu
-
- 4.8. postpone menu
-
- 4.9. browser menu
-
- 4.10. pgp menu
-
- 4.11. smime menu
-
- 4.12. mix menu
-
- 4.13. editor menu
-
- 9. Miscellany
-
- 1. Acknowledgements
-
- 2. About this document
-
- List of Tables
-
- 1.1. Typographical conventions for special terms
-
- 2.1. Most common navigation keys
-
- 2.2. Most common line editor keys
-
- 2.3. Most common message index keys
-
- 2.4. Message status flags
-
- 2.5. Message recipient flags
-
- 2.6. Most common pager keys
-
- 2.7. ANSI escape sequences
-
- 2.8. Color sequences
-
- 2.9. Most common thread mode keys
-
- 2.10. Most common mail sending keys
-
- 2.11. Most common compose menu keys
-
- 2.12. PGP key menu flags
-
- 3.1. Symbolic key names
-
- 4.1. POSIX regular expression character classes
-
- 4.2. Regular expression repetition operators
-
- 4.3. GNU regular expression extensions
-
- 4.4. Pattern modifiers
-
- 4.5. Simple search keywords
-
- 4.6. Date units
-
- 8.1. Command line options
-
- 8.2. Default generic function bindings
-
- 8.3. Default index function bindings
-
- 8.4. Default pager function bindings
-
- 8.5. Default alias function bindings
-
- 8.6. Default query function bindings
-
- 8.7. Default attach function bindings
-
- 8.8. Default compose function bindings
-
- 8.9. Default postpone function bindings
-
- 8.10. Default browser function bindings
-
- 8.11. Default pgp function bindings
-
- 8.12. Default smime function bindings
-
- 8.13. Default mix function bindings
-
- 8.14. Default editor function bindings
-
- List of Examples
-
- 3.1. Multiple configuration commands per line
-
- 3.2. Commenting configuration files
-
- 3.3. Escaping quotes in congfiguration files
-
- 3.4. Using external command's output in configuration files
-
- 3.5. Using environment variables in configuration files
-
- 3.6. Configuring external alias files
-
- 3.7. Setting sort method based on mailbox name
-
- 3.8. Header weeding
-
- 3.9. Configuring header display order
-
- 3.10. Defining custom headers
-
- 3.11. Using %-expandos in save-hook
-
- 3.12. Embedding push in folder-hook
-
- 3.13. Configuring spam detection
-
- 3.14. Using user-defined variables for config file readability
-
- 3.15. Using user-defined variables for backing up other config option
- values
-
- 3.16. Deferring user-defined variable expansion to runtime
-
- 3.17. Using external filters in format strings
-
- 4.1. Using boolean operators in patterns
-
- 4.2. Combining send-hook and my_hdr
-
- 5.1. Attachment counting
-
-Chapter 1. Introduction
-
- Table of Contents
-
- 1. Mutt Home Page
-
- 2. Mailing Lists
-
- 3. Software Distribution Sites
-
- 4. Mutt online resources
-
- 5. Contributing to Mutt
-
- 6. Typograhical conventions
-
- 7. Copyright
-
- Mutt is a small but very powerful text-based MIME mail client. Mutt 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.
-
-1. Mutt Home Page
-
- The official homepage can be found at http://www.mutt.org/.
-
-2. Mailing Lists
-
- To subscribe to one of the following mailing lists, send a message with
- the word subscribe in the body to list-name-request@mutt.org.
-
- o <mutt-announce-request@mutt.org> -- low traffic list for announcements
-
- o <mutt-users-request@mutt.org> -- help, bug reports and feature
- requests
-
- o <mutt-dev-request@mutt.org> -- development mailing list
-
- Note
-
- All messages posted to mutt-announce are automatically forwarded to
- mutt-users, so you do not need to be subscribed to both lists.
-
-3. Software Distribution Sites
-
- Mutt releases can be downloaded from ftp://ftp.mutt.org/mutt/. For a list
- of mirror sites, please refer to http://www.mutt.org/download.html.
-
-4. Mutt online resources
-
- Bug Tracking System
-
- The official mutt bug tracking system can be found at
- http://dev.mutt.org/
-
- Wiki
-
- An (unofficial) wiki can be found at http://wiki.mutt.org/.
-
- IRC
-
- For the IRC user community, visit channel #mutt on
- irc.freenode.net.
-
- USENET
-
- For USENET, see the newsgroup comp.mail.mutt.
-
-5. Contributing to Mutt
-
- There are various ways to contribute to the Mutt project.
-
- Especially for new users it may be helpful to meet other new and
- experienced users to chat about Mutt, talk about problems and share
- tricks.
-
- Since translations of Mutt into other languages are highly appreciated,
- the mutt developers always look for skilled translators that help improve
- and continue to maintain stale translations.
-
- For contributing code patches for new features and bug fixes, please refer
- to the developer pages at http://dev.mutt.org/ for more details.
-
-6. Typograhical conventions
-
- This section lists typographical conventions followed throughout this
- manual. See table Table 1.1, "Typographical conventions for special terms"
- for typographical conventions for special terms.
-
- Table 1.1. Typographical conventions for special terms
-
- +----------------------------------------------------------+
- | Item | Refers to... |
- |----------------+-----------------------------------------|
- | printf(3) | UNIX manual pages, execute man 3 printf |
- |----------------+-----------------------------------------|
- | <PageUp> | named keys |
- |----------------+-----------------------------------------|
- | <create-alias> | named Mutt function |
- |----------------+-----------------------------------------|
- | ^G | Control+G key combination |
- |----------------+-----------------------------------------|
- | $mail_check | Mutt configuration option |
- +----------------------------------------------------------+
-
- Examples are presented as:
-
- mutt -v
-
- Within command synopsis, curly brackets ("{}") denote a set of options of
- which one is mandatory, square brackets ("[]") denote optional arguments,
- three dots denote that the argument may be repeated arbitrary times.
-
-7. Copyright
-
- Mutt is Copyright (C) 1996-2009 Michael R. Elkins <me@mutt.org> and
- others.
-
- This program is free software; you can redistribute it and/or modify it
- under the terms of the GNU General Public License as published by the Free
- Software Foundation; either version 2 of the License, or (at your option)
- any later version.
-
- This program is distributed in the hope that it will be useful, but
- WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
- for more details.
-
- You should have received a copy of the GNU General Public License along
- with this program; if not, write to the Free Software Foundation, Inc., 51
- Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-
-Chapter 2. Getting Started
-
- Table of Contents
-
- 1. Core concepts
-
- 2. Moving Around in Menus
-
- 3. Editing Input Fields
-
- 3.1. Introduction
-
- 3.2. History
-
- 4. Reading Mail - The Index and Pager
-
- 4.1. The Message Index
-
- 4.2. The Pager
-
- 4.3. Threaded Mode
-
- 4.4. Miscellaneous Functions
-
- 5. Sending Mail
-
- 5.1. Introduction
-
- 5.2. Editing the message header
-
- 5.3. Sending cryptographically signed/encrypted messages
-
- 5.4. Sending anonymous messages via mixmaster
-
- 5.5. Sending format=flowed messages
-
- 6. Forwarding and Bouncing Mail
-
- 7. Postponing Mail
-
- This section is intended as a brief overview of how to use Mutt. There are
- many other features which are described elsewhere in the manual. There is
- even more information available in the Mutt FAQ and various web pages. See
- the Mutt homepage for more details.
-
- The keybindings described in this section are the defaults as distributed.
- Your local system administrator may have altered the defaults for your
- site. You can always type "?" in any menu to display the current bindings.
-
- The first thing you need to do is invoke mutt, simply by typing mutt at
- the command line. There are various command-line options, see either the
- mutt man page or the reference.
-
-1. Core concepts
-
- Mutt is a text-based application which interacts with users through
- different menus which are mostly line-/entry-based or page-based. A
- line-based menu is the so-called "index" menu (listing all messages of the
- currently opened folder) or the "alias" menu (allowing you to select
- recipients from a list). Examples for page-based menus are the "pager"
- (showing one message at a time) or the "help" menu listing all available
- key bindings.
-
- The user interface consists of a context sensitive help line at the top,
- the menu's contents followed by a context sensitive status line and
- finally the command line. The command line is used to display
- informational and error messages as well as for prompts and for entering
- interactive commands.
-
- Because Mutt allows for customizing almost all key bindings, there are
- so-called "functions" which can be executed manually (using the command
- line) or in macros. Macros allow the user to bind a sequence of commands
- to a single key or a short key sequence instead of repeating a sequence of
- actions over and over.
-
- Many commands (such as saving or copying a message to another folder) can
- be applied to a single message or a set of messages (so-called "tagged"
- messages). To help selecting messages, Mutt provides a rich set of message
- patterns (such as recipients, sender, body contents, date sent/received,
- etc.) which can be combined into complex expressions using the boolean and
- and or operations as well as negating. These patterns can also be used to
- (for example) search for messages or to limit the index to show only
- matching messages.
-
- Mutt supports a "hook" concept which allows the user to execute arbitrary
- configuration commands and functions in certain situations such as
- entering a folder, starting a new message or replying to an existing one.
- These hooks can be used to highly customize Mutt's behaviour including
- managing multiple identities, customizing the display for a folder or even
- implementing auto-archiving based on a per-folder basis and much more.
-
-2. Moving Around in Menus
-
- The most important navigation keys common to all menus are shown in
- Table 2.1, "Most common navigation keys".
-
- Table 2.1. Most common navigation keys
-
- +------------------------------------------------------------------------+
- | 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 keybindings for the |
- | | | current menu |
- +------------------------------------------------------------------------+
-
-3. Editing Input Fields
-
- 3.1. Introduction
-
- Mutt has a built-in line editor for inputting text, e.g. email addresses
- or filenames. The keys used to manipulate text input are very similar to
- those of Emacs. See Table 2.2, "Most common line editor keys" for a full
- reference of available functions, their default key bindings, and short
- descriptions.
-
- Table 2.2. Most common line editor keys
-
- +------------------------------------------------------------------------+
- | Key | Function | Description |
- |----------------+-------------------+-----------------------------------|
- | ^A or <Home> | <bol> | move to the start of the line |
- |----------------+-------------------+-----------------------------------|
- | ^B or <Left> | <backward-char> | move back one char |
- |----------------+-------------------+-----------------------------------|
- | Esc B | <backward-word> | move back one word |
- |----------------+-------------------+-----------------------------------|
- | ^D or <Delete> | <delete-char> | delete the char under the cursor |
- |----------------+-------------------+-----------------------------------|
- | ^E or <End> | <eol> | move to the end of the line |
- |----------------+-------------------+-----------------------------------|
- | ^F or <Right> | <forward-char> | move forward one char |
- |----------------+-------------------+-----------------------------------|
- | Esc F | <forward-word> | move forward one word |
- |----------------+-------------------+-----------------------------------|
- | <Tab> | <complete> | complete filename or alias |
- |----------------+-------------------+-----------------------------------|
- | ^T | <complete-query> | complete address with query |
- |----------------+-------------------+-----------------------------------|
- | ^K | <kill-eol> | delete to the end of the line |
- |----------------+-------------------+-----------------------------------|
- | Esc d | <kill-eow> | delete to the end of the word |
- |----------------+-------------------+-----------------------------------|
- | ^W | <kill-word> | kill the word in front of the |
- | | | cursor |
- |----------------+-------------------+-----------------------------------|
- | ^U | <kill-line> | delete entire line |
- |----------------+-------------------+-----------------------------------|
- | ^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 |
- |----------------+-------------------+-----------------------------------|
- | Esc u | <upcase-word> | convert word to upper case |
- |----------------+-------------------+-----------------------------------|
- | Esc l | <downcase-word> | convert word to lower case |
- |----------------+-------------------+-----------------------------------|
- | Esc c | <capitalize-word> | capitalize the word |
- |----------------+-------------------+-----------------------------------|
- | ^G | n/a | abort |
- |----------------+-------------------+-----------------------------------|
- | <Return> | n/a | finish editing |
- +------------------------------------------------------------------------+
-
- You can remap the editor functions using the bind command. For example, to
- make the <Delete> key delete the character in front of the cursor rather
- than under, you could use:
-
- bind editor <delete> backspace
-
- 3.2. History
-
- Mutt maintains a history for the built-in editor. The number of items is
- controlled by the $history variable and can be made persistent using an
- external file specified using $history_file. You may cycle through them at
- an editor prompt by using the <history-up> and/or <history-down> commands.
-
- Mutt maintains several distinct history lists, one for each of the
- following categories:
-
- o muttrc commands
-
- o addresses and aliases
-
- o shell commands
-
- o filenames
-
- o patterns
-
- o everything else
-
- Mutt automatically filters out repeated items from the history. It also
- mimics the behavior of some shells by ignoring items starting with a
- space. The latter feature can be useful in macros to not clobber the
- history's valuable entries with unwanted entries.
-
-4. Reading Mail - The Index and Pager
-
- Similar to many other mail clients, there are two modes in which mail is
- read in Mutt. The first is the index of messages in the mailbox, which is
- called the "index" in Mutt. The second mode is the display of the message
- contents. This is called the "pager."
-
- The next few sections describe the functions provided in each of these
- modes.
-
- 4.1. The Message Index
-
- Common keys used to navigate through and manage messages in the index are
- shown in Table 2.3, "Most common message index keys". How messages are
- presented in the index menu can be customized using the $index_format
- variable.
-
- Table 2.3. Most common message index keys
-
- +--------------------------------------------------------+
- | Key | Description |
- |----------+---------------------------------------------|
- | c | change to a different mailbox |
- |----------+---------------------------------------------|
- | Esc c | change to a folder in read-only mode |
- |----------+---------------------------------------------|
- | C | copy the current message to another mailbox |
- |----------+---------------------------------------------|
- | Esc C | decode a message and copy it to a folder |
- |----------+---------------------------------------------|
- | Esc 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 |
- |----------+---------------------------------------------|
- | Esc 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 |
- |----------+---------------------------------------------|
- | Esc / | search-reverse |
- |----------+---------------------------------------------|
- | ^L | clear and redraw the screen |
- |----------+---------------------------------------------|
- | ^T | untag messages matching a pattern |
- +--------------------------------------------------------+
-
- 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 "flags" in Table 2.4, "Message status flags" may appear,
- some of which can be turned on or off using these functions: <set-flag>
- and <clear-flag> bound by default to "w" and "W" respectively.
-
- Furthermore, the flags in Table 2.5, "Message recipient flags" reflect who
- the message is addressed to. They can be customized with the $to_chars
- variable.
-
- Table 2.4. Message status flags
-
- +----------------------------------------------------------------------+
- | Flag | Description |
- |------+---------------------------------------------------------------|
- | D | message is deleted (is marked for deletion) |
- |------+---------------------------------------------------------------|
- | d | message has attachments marked for deletion |
- |------+---------------------------------------------------------------|
- | K | contains a PGP public key |
- |------+---------------------------------------------------------------|
- | N | message is new |
- |------+---------------------------------------------------------------|
- | O | message is old |
- |------+---------------------------------------------------------------|
- | P | message is PGP encrypted |
- |------+---------------------------------------------------------------|
- | r | message has been replied to |
- |------+---------------------------------------------------------------|
- | S | message is signed, and the signature is successfully verified |
- |------+---------------------------------------------------------------|
- | s | message is signed |
- |------+---------------------------------------------------------------|
- | ! | message is flagged |
- |------+---------------------------------------------------------------|
- | * | message is tagged |
- +----------------------------------------------------------------------+
-
- Table 2.5. Message recipient flags
-
- +----------------------------------------------------------+
- | Flag | Description |
- |------+---------------------------------------------------|
- | + | message is to you and you only |
- |------+---------------------------------------------------|
- | T | message is to you, but also to or cc'ed to others |
- |------+---------------------------------------------------|
- | C | message is cc'ed to you |
- |------+---------------------------------------------------|
- | F | message is from you |
- |------+---------------------------------------------------|
- | L | message is sent to a subscribed mailing list |
- +----------------------------------------------------------+
-
- 4.2. The Pager
-
- By default, Mutt uses its builtin pager to display the contents of
- messages. The pager is very similar to the Unix program less though not
- nearly as featureful.
-
- Table 2.6. Most common pager keys
-
- +------------------------------------------------------------------------+
- | Key | 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 keybindings |
- |----------+-------------------------------------------------------------|
- | / | regular expression search |
- |----------+-------------------------------------------------------------|
- | Esc / | backward regular expression search |
- |----------+-------------------------------------------------------------|
- | \ | toggle highlighting of search matches |
- |----------+-------------------------------------------------------------|
- | ^ | jump to the top of the message |
- +------------------------------------------------------------------------+
-
- In addition to key bindings in Table 2.6, "Most common pager keys", many
- of the functions from the index menu are also 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 for bold
- and underline. These sequences are a series of either the letter,
- backspace (^H), the letter again for bold or the letter, backspace, "_"
- for denoting underline. Mutt 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 translates them into the correct color and
- character settings. The sequences Mutt supports are:
-
- \e[Ps;Ps;..Ps;m
-
- where Ps can be one of the codes shown in Table 2.7, "ANSI escape
- sequences".
-
- Table 2.7. ANSI escape sequences
-
- +------------------------------------------------------------------------+
- | Escape code | Description |
- |-------------+----------------------------------------------------------|
- | 0 | All attributes off |
- |-------------+----------------------------------------------------------|
- | 1 | Bold on |
- |-------------+----------------------------------------------------------|
- | 4 | Underline on |
- |-------------+----------------------------------------------------------|
- | 5 | Blink on |
- |-------------+----------------------------------------------------------|
- | 7 | Reverse video on |
- |-------------+----------------------------------------------------------|
- | 3<color> | Foreground color is <color> (see Table 2.8, "Color |
- | | sequences") |
- |-------------+----------------------------------------------------------|
- | 4<color> | Background color is <color> (see Table 2.8, "Color |
- | | sequences") |
- +------------------------------------------------------------------------+
-
- Table 2.8. Color sequences
-
- +----------------------+
- | Color code | Color |
- |------------+---------|
- | 0 | Black |
- |------------+---------|
- | 1 | Red |
- |------------+---------|
- | 2 | Green |
- |------------+---------|
- | 3 | Yellow |
- |------------+---------|
- | 4 | Blue |
- |------------+---------|
- | 5 | Magenta |
- |------------+---------|
- | 6 | Cyan |
- |------------+---------|
- | 7 | White |
- +----------------------+
-
- Mutt uses these attributes for handling text/enriched messages, and they
- can also be used by an external autoview 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.
-
- Note
-
- Note that the search commands in the pager take regular expressions, which
- are not quite the same as the more complex patterns used by the search
- command in the index. This is because the pager only performs simple text
- search, whereas the index provides boolean filtering on several aspects of
- messages.
-
- 4.3. Threaded Mode
-
- When the mailbox is sorted by threads, there are a few additional
- functions available in the index and pager modes as shown in Table 2.9,
- "Most common thread mode keys".
-
- Table 2.9. Most common thread mode keys
-
- +------------------------------------------------------------------------+
- | Key | Function | Description |
- |-------+----------------------+-----------------------------------------|
- | ^D | <delete-thread> | delete all messages in the current |
- | | | thread |
- |-------+----------------------+-----------------------------------------|
- | ^U | <undelete-thread> | undelete all messages in the current |
- | | | thread |
- |-------+----------------------+-----------------------------------------|
- | ^N | <next-thread> | jump to the start of the next thread |
- |-------+----------------------+-----------------------------------------|
- | ^P | <previous-thread> | jump to the start of the previous |
- | | | thread |
- |-------+----------------------+-----------------------------------------|
- | ^R | <read-thread> | mark the current thread as read |
- |-------+----------------------+-----------------------------------------|
- | Esc d | <delete-subthread> | delete all messages in the current |
- | | | subthread |
- |-------+----------------------+-----------------------------------------|
- | Esc u | <undelete-subthread> | undelete all messages in the current |
- | | | subthread |
- |-------+----------------------+-----------------------------------------|
- | Esc n | <next-subthread> | jump to the start of the next subthread |
- |-------+----------------------+-----------------------------------------|
- | Esc p | <previous-subthread> | jump to the start of the previous |
- | | | subthread |
- |-------+----------------------+-----------------------------------------|
- | Esc r | <read-subthread> | mark the current subthread as read |
- |-------+----------------------+-----------------------------------------|
- | Esc t | <tag-thread> | toggle the tag on the current thread |
- |-------+----------------------+-----------------------------------------|
- | Esc v | <collapse-thread> | toggle collapse for the current thread |
- |-------+----------------------+-----------------------------------------|
- | Esc 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 on the screen. See %M in
- $index_format. For example, you could use "%?M?(#%03M)&(%4l)?" in
- $index_format to optionally display the number of hidden messages if the
- thread is collapsed.
-
- See also: $strict_threads.
-
- 4.4. Miscellaneous Functions
-
- In addition, the index and pager menus have these interesting functions:
-
- <create-alias> (default: a)
-
- Creates a new alias based upon the current message (or prompts for
- a new one). Once editing is complete, an alias command is added to
- the file specified by the $alias_file variable for future use
-
- Note
-
- Mutt does not read the $alias_file upon startup so you must
- explicitly source the file.
-
- <check-traditional-pgp> (default: Esc P)
-
- This function will search the current message for content signed
- or encrypted with PGP the "traditional" way, that is, without
- proper MIME tagging. Technically, this function will temporarily
- change the MIME content types of the body parts containing PGP
- data; this is similar to the <edit-type> function's effect.
-
- <edit> (default: e)
-
- This command (available in the index and pager) allows you to edit
- the raw current message as it's present in the mail folder. After
- you have finished editing, the changed message will be appended to
- the current folder, and the original message will be marked for
- deletion; if the message is unchanged it won't be replaced.
-
- <edit-type> (default: ^E on the attachment menu, and in the pager and
- index menus; ^T on the compose menu)
-
- This command is used to temporarily edit an attachment's content
- type to fix, for instance, bogus character set parameters. When
- invoked from the index or from the pager, you'll have the
- opportunity to edit the top-level attachment's content type. On
- the attachment menu, you can change any attachment's content type.
- These changes are not persistent, and get lost upon changing
- folders.
-
- Note that this command is also available on the compose menu.
- There, it's used to fine-tune the properties of attachments you
- are going to send.
-
- <enter-command> (default: ":")
-
- This command is used to execute any command you would normally put
- in a configuration file. A common use is to check the settings of
- variables, or in conjunction with macros to change settings on the
- fly.
-
- <extract-keys> (default: ^K)
-
- This command extracts PGP public keys from the current or tagged
- message(s) and adds them to your PGP public key ring.
-
- <forget-passphrase> (default: ^F)
-
- This command wipes the passphrase(s) from memory. It is useful, if
- you misspelled the passphrase.
-
- <list-reply> (default: L)
-
- Reply to the current or tagged message(s) by extracting any
- addresses which match the regular expressions given by the lists
- or subscribe commands, but also honor any Mail-Followup-To
- header(s) if the $honor_followup_to configuration variable is set.
- Using this when replying to messages posted to mailing lists helps
- avoid duplicate copies being sent to the author of the message you
- are replying to.
-
- <pipe-message> (default: |)
-
- Asks for an external Unix command and pipes the current or tagged
- message(s) to it. The variables $pipe_decode, $pipe_split,
- $pipe_sep and $wait_key control the exact behavior of this
- function.
-
- <resend-message> (default: Esc e)
-
- Mutt takes the current message as a template for a new message.
- This function is best described as "recall from arbitrary
- folders". It can conveniently be used to forward MIME messages
- while preserving the original mail structure. Note that the amount
- of headers included here depends on the value of the $weed
- variable.
-
- This function is also available from the attachment menu. You can
- use this to easily resend a message which was included with a
- bounce message as a message/rfc822 body part.
-
- <shell-escape> (default: !)
-
- Asks for an external Unix command and executes it. The $wait_key
- can be used to control whether Mutt 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. If no command is given, an interactive shell is
- executed.
-
- <toggle-quoted> (default: T)
-
- The pager uses the $quote_regexp variable to detect quoted text
- when displaying the body of the message. This function toggles the
- display of the quoted material in the message. It is particularly
- useful when being interested in just the response and there is a
- large amount of quoted text in the way.
-
- <skip-quoted> (default: S)
-
- This function will go to the next line of non-quoted text which
- comes after a line of quoted text in the internal pager.
-
-5. Sending Mail
-
- 5.1. Introduction
-
- The bindings shown in Table 2.10, "Most common mail sending keys" are
- available in the index and pager to start a new message.
-
- Table 2.10. Most common mail sending keys
-
- +----------------------------------------------------------+
- | 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 |
- |-------+---------------+----------------------------------|
- | Esc k | <mail-key> | mail a PGP public key to someone |
- +----------------------------------------------------------+
-
- Bouncing a message sends the message as-is to the recipient you specify.
- Forwarding a message allows you to add comments or modify the message you
- are forwarding. These items are discussed in greater detail in the next
- chapter "Forwarding and Bouncing Mail."
-
- Mutt will then enter the compose menu and prompt you for the recipients to
- place on the "To:" header field. Next, it will ask you for the "Subject:"
- field for the message, providing a default if you are replying to or
- forwarding a message. See also $askcc, $askbcc, $autoedit, $bounce,
- $fast_reply, and $include for changing how Mutt asks these questions.
-
- Mutt will then automatically start your $editor on the message body. If
- the $edit_headers variable is set, the headers will be at the top of the
- message in your editor. Any messages you are replying to will be added in
- sort order to the message, with appropriate $attribution, $indent_string
- and $post_indent_string. When forwarding a message, if the $mime_forward
- variable is unset, a copy of the forwarded message will be included. If
- you have specified a $signature, it will be appended to the message.
-
- Once you have finished editing the body of your mail message, you are
- returned to the compose menu providing the functions shown in Table 2.11,
- "Most common compose menu keys" to modify, send or postpone the message.
-
- Table 2.11. Most common compose menu keys
-
- +------------------------------------------------------------------------+
- | Key | Function | Description |
- |-------+---------------------+------------------------------------------|
- | a | <attach-file> | attach a file |
- |-------+---------------------+------------------------------------------|
- | A | <attach-message> | attach message(s) to the message |
- |-------+---------------------+------------------------------------------|
- | Esc 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 |
- |-------+---------------------+------------------------------------------|
- | Esc 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) |
- |-------+---------------------+------------------------------------------|
- | ^F | <forget-passphrase> | wipe passphrase(s) from memory |
- +------------------------------------------------------------------------+
-
- The compose menu is also used to edit the attachments for a message which
- can be either files or other messages. The <attach-message> function to
- will prompt you for a folder to attach messages from. You can now tag
- messages in that folder and they will be attached to the message you are
- sending.
-
- Note
-
- Note that certain operations 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.
-
- 5.2. Editing the message header
-
- When editing the header because of $edit_headers being set, there are a
- several pseudo headers available which will not be included in sent
- messages.
-
- 5.2.1. Fcc: pseudo header
-
- If you specify Fcc: filename as a header, Mutt will pick up filename just
- as if you had used the <edit-fcc> function in the compose menu.
-
- 5.2.2. Attach: pseudo header
-
- You can also attach files to your message by specifying Attach: filename [
- description ] where filename is the file to attach and description is an
- optional string to use as the description of the attached file.
-
- 5.2.3. Pgp: pseudo header
-
- If you want to use PGP, you can specify
-
- Pgp: [ E | S | S<id> ]
-
- "E" selects encryption, "S" selects signing and "S<id>" selects signing
- with the given key, setting $pgp_sign_as permanently.
-
- 5.2.4. In-Reply-To: header
-
- When replying to messages, the In-Reply-To: header contains the Message-Id
- of the message(s) you reply to. If you remove its value, Mutt will not
- generate a References: field, which allows you to create a new message
- thread, for example to create a new message to a mailing list without
- having to enter the mailing list's address.
-
- 5.3. Sending cryptographically signed/encrypted messages
-
- If you have told mutt to PGP or S/MIME encrypt a message, it will guide
- you through a key selection process when you try to send the message. Mutt
- will not ask you any questions about keys which have a certified user ID
- matching one of the message recipients' mail addresses. However, there may
- be situations in which there are several keys, weakly certified user ID
- fields, or where no matching keys can be found.
-
- In these cases, you are dropped into a menu with a list of keys from which
- you can select one. When you quit this menu, or mutt can't find any
- matching keys, you are prompted for a user ID. You can, as usually, abort
- this prompt using ^G. When you do so, mutt will return to the compose
- screen.
-
- Once you have successfully finished the key selection, the message will be
- encrypted using the selected public keys when sent out.
-
- Most fields of the entries in the key selection menu (see also
- $pgp_entry_format) have obvious meanings. But some explanations on the
- capabilities, flags, and validity fields are in order.
-
- The flags sequence (%f) will expand to one of the flags in Table 2.12,
- "PGP key menu flags".
-
- Table 2.12. PGP key menu flags
-
- +-----------------------------------------------------------+
- | Flag | Description |
- |------+----------------------------------------------------|
- | R | The key has been revoked and can't be used. |
- |------+----------------------------------------------------|
- | X | The key is expired and can't be used. |
- |------+----------------------------------------------------|
- | d | You have marked the key as disabled. |
- |------+----------------------------------------------------|
- | c | There are unknown critical self-signature packets. |
- +-----------------------------------------------------------+
-
- The capabilities field (%c) expands to a two-character sequence
- representing a key's capabilities. The first character gives the key's
- encryption capabilities: A minus sign ("-") means that the key cannot be
- used for encryption. A dot (".") means that it's marked as a signature key
- in one of the user IDs, but may also be used for encryption. The letter
- "e" indicates that this key can be used for encryption.
-
- The second character indicates the key's signing capabilities. Once again,
- a "-" implies "not for signing", "." implies that the key is marked as an
- encryption key in one of the user-ids, and "s" denotes a key which can be
- used for signing.
-
- Finally, the validity field (%t) indicates how well-certified a user-id
- is. A question mark ("?") indicates undefined validity, a minus character
- ("-") marks an untrusted association, a space character means a partially
- trusted association, and a plus character ("+") indicates complete
- validity.
-
- 5.4. Sending anonymous messages via mixmaster
-
- You may also have compiled mutt to co-operate with Mixmaster, an anonymous
- remailer. Mixmaster permits you to send your messages anonymously using a
- chain of remailers. Mixmaster support in mutt is for mixmaster version
- 2.04 (beta 45 appears to be the latest) and 2.03. It does not support
- earlier versions or the later so-called version 3 betas, of which the
- latest appears to be called 2.9b23.
-
- To use it, you'll have to obey certain restrictions. Most important, you
- cannot use the Cc and Bcc headers. To tell Mutt to use mixmaster, you have
- to select a remailer chain, using the mix function on the compose menu.
-
- The chain selection screen is divided into two parts. In the (larger)
- upper part, you get a list of remailers you may use. In the lower part,
- you see the currently selected chain of remailers.
-
- You can navigate in the chain using the <chain-prev> and <chain-next>
- functions, which are by default bound to the left and right arrows and to
- the h and l keys (think vi keyboard bindings). To insert a remailer at the
- current chain position, use the <insert> function. To append a remailer
- behind the current chain position, use <select-entry> or <append>. You can
- also delete entries from the chain, using the corresponding function.
- Finally, to abandon your changes, leave the menu, or <accept> them
- pressing (by default) the Return key.
-
- Note that different remailers do have different capabilities, indicated in
- the %c entry of the remailer menu lines (see $mix_entry_format). Most
- important is the "middleman" capability, indicated by a capital "M": This
- means that the remailer in question cannot be used as the final element of
- a chain, but will only forward messages to other mixmaster remailers. For
- details on the other capabilities, please have a look at the mixmaster
- documentation.
-
- 5.5. Sending format=flowed messages
-
- 5.5.1. Concept
-
- format=flowed-style messages (or f=f for short) are text/plain messages
- that consist of paragraphs which a receiver's mail client may reformat to
- its own needs which mostly means to customize line lengths regardless of
- what the sender sent. Technically this is achieved by letting lines of a
- "flowable" paragraph end in spaces except for the last line.
-
- While for text-mode clients like mutt it's the best way to assume only a
- standard 80x25 character cell terminal, it may be desired to let the
- receiver decide completely how to view a message.
-
- 5.5.2. Mutt support
-
- Mutt only supports setting the required format=flowed MIME parameter on
- outgoing messages if the $text_flowed variable is set, specifically it
- does not add the trailing spaces.
-
- After editing the initial message text and before entering the compose
- menu, mutt properly space-stuffes the message. Space-stuffing is required
- by RfC3676 defining format=flowed and means to prepend a space to:
-
- o all lines starting with a space
-
- o lines starting with the word "From" followed by space
-
- o all lines starting with ">" which is not intended to be a quote
- character
-
- Note
-
- Mutt only supports space-stuffing for the first two types of lines but not
- for the third: It is impossible to safely detect whether a leading >
- character starts a quote or not. Furthermore, Mutt only applies
- space-stuffing once after the initial edit is finished.
-
- All leading spaces are to be removed by receiving clients to restore the
- original message prior to further processing.
-
- 5.5.3. Editor considerations
-
- As mutt provides no additional features to compose f=f messages, it's
- completely up to the user and his editor to produce proper messages.
- Please consider your editor's documentation if you intend to send f=f
- messages.
-
- Please note that when editing messages from the compose menu several times
- before really sending a mail, it's up to the user to ensure that the
- message is properly space-stuffed.
-
- For example, vim provides the w flag for its formatoptions setting to
- assist in creating f=f messages, see :help fo-table for details.
-
-6. Forwarding and Bouncing Mail
-
- Bouncing and forwarding let you send an existing message to recipients
- that you specify. Bouncing a message sends a verbatim copy of a message to
- alternative addresses as if they were the message's original recipients
- specified in the Bcc header. Forwarding a message, on the other hand,
- allows you to modify the message before it is resent (for example, by
- adding your own comments). Bouncing is done using the <bounce> function
- and forwarding using the <forward> function bound to "b" and "f"
- respectively.
-
- Forwarding can be done by including the original message in the new
- message's body (surrounded by indicating lines) or including it as a MIME
- attachment, depending on the value of the $mime_forward variable. Decoding
- of attachments, like in the pager, can be controlled by the
- $forward_decode and $mime_forward_decode variables, respectively. The
- desired forwarding format may depend on the content, therefore
- $mime_forward is a quadoption which, for example, can be set to "ask-no".
-
- The inclusion of headers is controlled by the current setting of the $weed
- variable, unless $mime_forward is set.
-
- Editing the message to forward follows the same procedure as sending or
- replying to a message does.
-
-7. Postponing Mail
-
- At times it is desirable to delay sending a message that you have already
- begun to compose. When the <postpone-message> function is used in the
- compose menu, the body of your message and attachments are stored in the
- mailbox specified by the $postponed variable. This means that you can
- recall the message even if you exit Mutt and then restart it at a later
- time.
-
- Once a message is postponed, there are several ways to resume it. From the
- command line you can use the "-p" option, or if you compose a new message
- from the index or pager you will be prompted if postponed messages exist.
- If multiple messages are currently postponed, the postponed menu will pop
- up and you can select which message you would like to resume.
-
- Note
-
- If you postpone a reply to a message, the reply setting of the message is
- only updated when you actually finish the message and send it. Also, you
- must be in the same folder with the message you replied to for the status
- of the message to be updated.
-
- See also the $postpone quad-option.
-
-Chapter 3. Configuration
-
- Table of Contents
-
- 1. Location of initialization files
-
- 2. Syntax of Initialization Files
-
- 3. Address groups
-
- 4. Defining/Using aliases
-
- 5. Changing the default key bindings
-
- 6. Defining aliases for character sets
-
- 7. Setting variables based upon mailbox
-
- 8. Keyboard macros
-
- 9. Using color and mono video attributes
-
- 10. Message header display
-
- 11. Alternative addresses
-
- 12. Mailing lists
-
- 13. Using Multiple spool mailboxes
-
- 14. Monitoring incoming mail
-
- 15. User defined headers
-
- 16. Specify default save mailbox
-
- 17. Specify default Fcc: mailbox when composing
-
- 18. Specify default save filename and default Fcc: mailbox at once
-
- 19. Change settings based upon message recipients
-
- 20. Change settings before formatting a message
-
- 21. Choosing the cryptographic key of the recipient
-
- 22. Adding key sequences to the keyboard buffer
-
- 23. Executing functions
-
- 24. Message Scoring
-
- 25. Spam detection
-
- 26. Setting and Querying Variables
-
- 26.1. Commands
-
- 26.2. User-defined variables
-
- 27. Reading initialization commands from another file
-
- 28. Configuring features conditionnaly
-
- 29. Removing hooks
-
- 30. Format Strings
-
- 30.1. Basic usage
-
- 30.2. Filters
-
-1. Location of initialization files
-
- While the default configuration (or "preferences") make Mutt usable right
- out of the box, it is often desirable to tailor Mutt to suit your own
- tastes. When Mutt is first invoked, it will attempt to read the "system"
- configuration file (defaults set by your local system administrator),
- unless the "-n" command line option is specified. This file is typically
- /usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt will next look for a
- file named .muttrc in your home directory. If this file does not exist and
- your home directory has a subdirectory named .mutt, mutt try to load a
- file named .mutt/muttrc.
-
- .muttrc is the file where you will usually place your commands to
- configure Mutt.
-
- In addition, mutt supports version specific configuration files that are
- parsed instead of the default files as explained above. For instance, if
- your system has a Muttrc-0.88 file in the system configuration directory,
- and you are running version 0.88 of mutt, this file will be sourced
- instead of the Muttrc file. The same is true of the user configuration
- file, if you have a file .muttrc-0.88.6 in your home directory, when you
- run mutt version 0.88.6, it will source this file instead of the default
- .muttrc file. The version number is the same which is visible using the
- "-v" command line switch or using the show-version key (default: V) from
- the index menu.
-
-2. Syntax of Initialization Files
-
- An initialization file consists of a series of commands. Each line of the
- file may contain one or more commands. When multiple commands are used,
- they must be separated by a semicolon (;).
-
- Example 3.1. Multiple configuration commands per line
-
- set realname='Mutt 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,
-
- Example 3.2. Commenting configuration files
-
- 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, backticks are evaluated inside of double quotes,
- but not for single quotes.
-
- \ quotes the next character, just as in shells such as bash and zsh. For
- example, if want to put quotes """ inside of a string, you can use "\" to
- force the next character to be a literal instead of interpreted character.
-
- Example 3.3. Escaping quotes in congfiguration files
-
- set realname="Michael \"MuttDude\" Elkins"
-
- "\\" means to insert a literal "\" into the line. "\n" and "\r" have their
- usual C meanings of linefeed and carriage-return, respectively.
-
- A \ at the end of a line can be used to split commands over multiple
- lines, provided that the split points don't appear in the middle of
- command names.
-
- It is also possible to substitute the output of a Unix command in an
- initialization file. This is accomplished by enclosing the command in
- backticks (``). For example,
-
- Example 3.4. Using external command's output in configuration files
-
- my_hdr X-Operating-System: `uname -a`
-
- The output of the Unix command "uname -a" will be substituted before the
- line is parsed.
-
- Note
-
- Since initialization files are line oriented, only the first line of
- output from the Unix command will be substituted.
-
- Both environment variables and mutt variables can be accessed by
- prepending "$" to the name of the variable. For example,
-
- Example 3.5. Using environment variables in configuration files
-
- set record=+sent_on_$HOSTNAME
-
- will cause mutt to save outgoing messages to a folder named
- "sent_on_kremvax" if the environment variable HOSTNAME is set to
- "kremvax." (See $record for details.)
-
- Mutt expands the variable when it is assigned, not when it is used. If the
- value of a variable on the right-hand side of an assignment changes after
- the assignment, the variable on the left-hand side will not be affected.
-
- The commands understood by mutt are explained in the next paragraphs. For
- a complete list, see the command reference.
-
- All configuration files are expected to be in the current locale as
- specified by the $charset variable which doesn't have a default value
- since it's determined by Mutt at startup. If a configuration file is not
- encoded in the same character set the $config_charset variable should be
- used: all lines starting with the next are recoded from $config_charset to
- $charset.
-
- This mechanism should be avoided if possible as it has the following
- implications:
-
- o These variables should be set early in a configuration file with
- $charset preceding $config_charset so Mutt know what character set to
- convert to.
-
- o If $config_charset is set, it should be set in each configuration file
- because the value is global and not per configuration file.
-
- o Because Mutt first recodes a line before it attempts to parse it, a
- conversion introducing question marks or other characters as part of
- errors (unconvertable characters, transliteration) may introduce
- syntax errors or silently change the meaning of certain tokens (e.g.
- inserting question marks into regular expressions).
-
-3. Address groups
-
- Usage:
-
- group [ -group name ...] { -rx expr ... | -addr expr ... }
-
- ungroup [ -group name ...] { * | -rx expr ... | -addr expr ... }
-
- group is used to directly add either addresses or regular expressions to
- the specified group or groups. The different categories of arguments to
- the group command can be in any order. The flags -rx and -addr specify
- what the following strings (that cannot begin with a hyphen) should be
- interpreted as: either a regular expression or an email address,
- respectively.
-
- These address groups can also be created implicitly by the alias, lists,
- subscribe and alternates commands by specifying the optional -group
- option.
-
- Once defined, these address groups can be used in patterns to search for
- and limit the display to messages matching a group.
-
- ungroup is used to remove addresses or regular expressions from the
- specified group or groups. The syntax is similar to the group command,
- however the special character * can be used to empty a group of all of its
- contents.
-
-4. Defining/Using aliases
-
- Usage:
-
- alias [ -group name ...] key address [ address ...]
-
- It's usually very cumbersome to remember or type out the address of
- someone you are communicating with. Mutt allows you to create "aliases"
- which map a short string to a full address.
-
- Note
-
- If you want to create an alias for more than one address, you must
- separate the addresses with a comma (",").
-
- The optional -group argument to alias causes the aliased address(es) to be
- added to the named group.
-
- To remove an alias or aliases ("*" means all aliases):
-
- unalias [ -group name ...] { * | key ... }
-
- alias muttdude me@cs.hmc.edu (Michael Elkins)
- alias theguys manny, moe, jack
-
- Unlike other mailers, Mutt 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 sourced. Consequently, you can have multiple
- alias files, or you can have all aliases defined in your muttrc.
-
- On the other hand, the <create-alias> function can use only one file, the
- one pointed to by the $alias_file variable (which is ~/.muttrc by
- default). This file is not special either, in the sense that Mutt 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:
-
- Example 3.6. Configuring external alias files
-
- source /usr/local/share/Mutt.aliases
- source ~/.mail_aliases
- set alias_file=~/.mail_aliases
-
- To use aliases, you merely use the alias at any place in mutt where mutt
- prompts 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
- $edit_headers variable set.
-
- In addition, at the various address prompts, you can use the tab character
- to expand a partial alias to the full alias. If there are multiple
- matches, mutt will bring up a menu with the matching aliases. In order to
- be presented with the full list of aliases, you must hit tab with out a
- partial alias, such as at the beginning of the prompt or after a comma
- denoting multiple addresses.
-
- In the alias menu, you can select as many aliases as you want with the
- select-entry key (default: <Return>), and use the exit key (default: q) to
- return to the address prompt.
-
-5. Changing the default key bindings
-
- Usage:
-
- bind map key function
-
- This command allows you to change the default key bindings (operation
- invoked when pressing a key).
-
- map specifies in which menu the binding belongs. Multiple maps may be
- specified by separating them with commas (no additional whitespace is
- allowed). The currently defined maps are:
-
- generic
-
- This is not a real menu, but is used as a fallback for all of the
- other menus except for the pager and editor modes. If a key is not
- defined in another menu, Mutt will look for a binding to use in
- this menu. This allows you to bind a key to a certain function in
- multiple menus instead of having multiple bind statements to
- accomplish the same task.
-
- alias
-
- The alias menu is the list of your personal aliases as defined in
- your muttrc. It is the mapping from a short alias name to the full
- email address(es) of the recipient(s).
-
- attach
-
- The attachment menu is used to access the attachments on received
- messages.
-
- browser
-
- The browser is used for both browsing the local directory
- structure, and for listing all of your incoming mailboxes.
-
- editor
-
- The editor is the line-based editor the user enters text data.
-
- index
-
- The index is the list of messages contained in a mailbox.
-
- compose
-
- The compose menu is the screen used when sending a new message.
-
- pager
-
- The pager is the mode used to display message/attachment data, and
- help listings.
-
- pgp
-
- The pgp menu is used to select the OpenPGP keys used to encrypt
- outgoing messages.
-
- smime
-
- The smime menu is used to select the OpenSSL certificates used to
- encrypt outgoing messages.
-
- postpone
-
- The postpone menu is similar to the index menu, except is used
- when recalling a message the user was composing, but saved until
- later.
-
- query
-
- The query menu is the browser for results returned by
- $query_command.
-
- mix
-
- The mixmaster screen is used to select remailer options for
- outgoing messages (if Mutt is compiled with Mixmaster support).
-
- key is the key (or key sequence) you wish to bind. To specify a control
- character, use the sequence \Cx, where x is the letter of the control
- character (for example, to specify control-A use "\Ca"). Note that the
- case of x as well as \C is ignored, so that \CA, \Ca, \cA and \ca are all
- equivalent. An alternative form is to specify the key as a three digit
- octal number prefixed with a "\" (for example \177 is equivalent to \c?).
- In addition, key may be a symbolic name as shown in Table 3.1, "Symbolic
- key names".
-
- Table 3.1. Symbolic key names
-
- +-------------------------------------+
- | Symbolic name | Meaning |
- |---------------+---------------------|
- | \t | tab |
- |---------------+---------------------|
- | <tab> | tab |
- |---------------+---------------------|
- | <backtab> | backtab / shift-tab |
- |---------------+---------------------|
- | \r | carriage return |
- |---------------+---------------------|
- | \n | newline |
- |---------------+---------------------|
- | \e | escape |
- |---------------+---------------------|
- | <esc> | escape |
- |---------------+---------------------|
- | <up> | up arrow |
- |---------------+---------------------|
- | <down> | down arrow |
- |---------------+---------------------|
- | <left> | left arrow |
- |---------------+---------------------|
- | <right> | right arrow |
- |---------------+---------------------|
- | <pageup> | Page Up |
- |---------------+---------------------|
- | <pagedown> | Page Down |
- |---------------+---------------------|
- | <backspace> | Backspace |
- |---------------+---------------------|
- | <delete> | Delete |
- |---------------+---------------------|
- | <insert> | Insert |
- |---------------+---------------------|
- | <enter> | Enter |
- |---------------+---------------------|
- | <return> | Return |
- |---------------+---------------------|
- | <home> | Home |
- |---------------+---------------------|
- | <end> | End |
- |---------------+---------------------|
- | <space> | Space bar |
- |---------------+---------------------|
- | <f1> | function key 1 |
- |---------------+---------------------|
- | <f10> | function key 10 |
- +-------------------------------------+
-
- key does not need to be enclosed in quotes unless it contains a space ("
- ") or semi-colon (";").
-
- function specifies which action to take when key is pressed. For a
- complete list of functions, see the reference. The special function <noop>
- unbinds the specified key sequence.
-
-6. Defining aliases for character sets
-
- Usage:
-
- charset-hook alias charset
-
- iconv-hook charset local-charset
-
- The charset-hook command defines an alias for a character set. This is
- useful to properly display messages which are tagged with a character set
- name not known to mutt.
-
- The iconv-hook command defines a system-specific name for a character set.
- This is helpful when your systems character conversion library insists on
- using strange, system-specific names for character sets.
-
-7. Setting variables based upon mailbox
-
- Usage:
-
- folder-hook [!]regexp command
-
- It is often desirable to change settings based on which mailbox you are
- reading. The folder-hook command provides a method by which you can
- execute any configuration command. regexp is a regular expression
- specifying in which mailboxes to execute command before loading. If a
- mailbox matches multiple folder-hook's, they are executed in the order
- given in the muttrc.
-
- Note
-
- If you use the "!" shortcut for $spoolfile at the beginning of the
- pattern, you must place it inside of double or single quotes in order to
- distinguish it from the logical not operator for the expression.
-
- Note
-
- Settings are not restored when you leave the mailbox. For example, a
- command action to perform is to change the sorting method based upon the
- mailbox being read:
-
- folder-hook mutt set sort=threads
-
- However, the sorting method is not restored to its previous value when
- reading a different mailbox. To specify a default command, use the pattern
- "." before other folder-hooks adjusting a value on a per-folder basis
- because folder-hooks are evaluated in the order given in the configuration
- file. The following example will set the sort variable to date-sent for
- all folders but to threads for all folders containing "mutt" in their
- name.
-
- Example 3.7. Setting sort method based on mailbox name
-
- folder-hook . set sort=date-sent
- folder-hook mutt set sort=threads
-
-8. Keyboard macros
-
- Usage:
-
- macro menu key sequence [ description ]
-
- Macros are useful when you would like a single key to perform a series of
- actions. When you press key in menu menu, Mutt 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 single key or fewer
- keys.
-
- menu is the map which the macro will be bound in. Multiple maps may be
- specified by separating multiple menu arguments by commas. Whitespace may
- not be used in between the menu arguments and the commas separating them.
-
- key and sequence are expanded by the same rules as the key bindings with
- some additions. The first is that control characters in sequence can also
- be specified as ^x. In order to get a caret ("^") you need to use ^^.
- 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 key bindings. Functions are listed
- in the reference.
-
- The advantage with using function names directly is that the macros will
- work regardless of the current key bindings, so they are not dependent on
- the user having particular key definitions. This makes them more robust
- and portable, and also facilitates defining of macros in files used by
- more than one user (e.g., the system Muttrc).
-
- Optionally you can specify a descriptive text after sequence, which is
- shown in the help screens.
-
- Note
-
- Macro definitions (if any) listed in the help screen(s), are silently
- truncated at the screen width, and are not wrapped.
-
-9. Using color and mono video attributes
-
- Usage:
-
- color object foreground background
-
- color { header | body } foreground background regexp
-
- color index foreground background pattern
-
- uncolor index { * | pattern ... }
-
- If your terminal supports color, you can spice up Mutt 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).
-
- header and body match regexp in the header/body of a message, index
- matches pattern (see Section 2, "Patterns: Searching, Limiting and
- Tagging") in the message index.
-
- object can be one of:
-
- o attachment
-
- o bold (hiliting bold patterns in the body of messages)
-
- o error (error messages printed by Mutt)
-
- o hdrdefault (default color of the message header in the pager)
-
- o indicator (arrow or bar used to indicate the current item in a menu)
-
- o markers (the "+" markers at the beginning of wrapped lines in the
- pager)
-
- o message (informational messages)
-
- o normal
-
- o quoted (text matching $quote_regexp in the body of a message)
-
- o quoted1, quoted2, ..., quotedN (higher levels of quoting)
-
- o search (hiliting of words in the pager)
-
- o signature
-
- o status (mode lines used to display info about the mailbox or message)
-
- o tilde (the "~" used to pad blank lines in the pager)
-
- o tree (thread tree drawn in the message index and attachment menu)
-
- o underline (hiliting underlined patterns in the body of messages)
-
- foreground and background can be one of the following:
-
- o white
-
- o black
-
- o green
-
- o magenta
-
- o blue
-
- o cyan
-
- o yellow
-
- o red
-
- o default
-
- o colorx
-
- foreground can optionally be prefixed with the keyword bright to make the
- foreground color boldfaced (e.g., brightred).
-
- If your terminal supports it, the special keyword default can be used as a
- transparent color. The value brightdefault is also valid. If Mutt is
- linked against the S-Lang library, you also need to set the COLORFGBG
- environment variable to the default colors of your terminal for this to
- work; for example (for Bourne-like shells):
-
- set COLORFGBG="green;black"
- export COLORFGBG
-
- Note
-
- The S-Lang library requires you to use the lightgray and brown keywords
- instead of white and yellow when setting this variable.
-
- Note
-
- The uncolor command can be applied to the index object only. It removes
- entries from the list. You must specify the same pattern specified in the
- color command for it to be removed. The pattern "*" is a special token
- which means to clear the color index list of all entries.
-
- Mutt also recognizes the keywords color0, color1, ..., colorN-1 (N being
- the number of colors supported by your terminal). This is useful when you
- remap the colors for your display (for example by changing the color
- associated with color2 for your xterm), since color names may then lose
- their normal meaning.
-
- If your terminal does not support color, it is still possible change the
- video attributes through the use of the "mono" command:
-
- Usage:
-
- mono object attribute
-
- mono { header | body } attribute regexp
-
- mono index attribute pattern
-
- unmono index { * | pattern ... }
-
- For object, see the color command. attribute can be one of the following:
-
- o none
-
- o bold
-
- o underline
-
- o reverse
-
- o standout
-
-10. Message header display
-
- Usage:
-
- ignore pattern [ pattern ...]
-
- unignore { * | pattern ... }
-
- Messages often have many header fields added by automatic processing
- systems, or which may not seem useful to display on the screen. This
- command allows you to specify header fields which you don't normally want
- to see in the pager.
-
- You do not need to specify the full header field name. For example,
- "ignore content-" will ignore all header fields that begin with the
- pattern "content-". "ignore *" will ignore all headers.
-
- To remove a previously added token from the list, use the "unignore"
- command. The "unignore" command will make Mutt display headers with the
- given pattern. For example, if you do "ignore x-" it is possible to
- "unignore x-mailer".
-
- "unignore *" will remove all tokens from the ignore list.
-
- For example:
-
- Example 3.8. Header weeding
-
- # 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:
-
- Usage:
-
- hdr_order header [ header ...]
-
- unhdr_order { * | header ... }
-
- With the hdr_order command you can specify an order in which mutt will
- attempt to present these headers to you when viewing messages.
-
- "unhdr_order *" will clear all previous headers from the order list, thus
- removing the header order effects set by the system-wide startup file.
-
- Example 3.9. Configuring header display order
-
- hdr_order From Date: From: To: Cc: Subject:
-
-11. Alternative addresses
-
- Usage:
-
- alternates [ -group name ...] regexp [ regexp ...]
-
- unalternates [ -group name ...] { * | regexp ... }
-
- With various functions, mutt will treat messages differently, depending on
- whether you sent them or whether you received them from someone else. For
- instance, when replying to a message that you sent to a different party,
- mutt will automatically suggest to send the response to the original
- message's recipients -- responding to yourself won't make much sense in
- many cases. (See $reply_to.)
-
- Many users receive e-mail under a number of different addresses. To fully
- use mutt's features here, the program must be able to recognize what
- e-mail addresses you receive mail under. That's the purpose of the
- alternates command: It takes a list of regular expressions, each of which
- can identify an address under which you receive e-mail.
-
- As addresses are matched using regular expressions and not exact strict
- comparisons, you should make sure you specify your addresses as precise as
- possible to avoid mismatches. For example, if you specify:
-
- alternates user@example
-
- mutt will consider "some-user@example" as being your address, too which
- may not be desired. As a solution, in such cases addresses should be
- specified as:
-
- alternates '^user@example$'
-
- The -group flag causes all of the subsequent regular expressions to be
- added to the named group.
-
- The unalternates command can be used to write exceptions to alternates
- patterns. If an address matches something in an alternates command, but
- you nonetheless do not think it is from you, you can list a more precise
- pattern under an unalternates command.
-
- To remove a regular expression from the alternates list, use the
- unalternates command with exactly the same regexp. Likewise, if the regexp
- for an alternates command matches an entry on the unalternates list, that
- unalternates entry will be removed. If the regexp for unalternates is "*",
- all entries on alternates will be removed.
-
-12. Mailing lists
-
- Usage:
-
- lists [ -group name ...] regexp [ regexp ...]
-
- unlists [ -group name ...] { * | regexp ... }
-
- subscribe [ -group name ...] regexp [ regexp ...]
-
- unsubscribe [ -group name ...] { * | regexp ... }
-
- Mutt has a few nice features for handling mailing 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
-
- 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 maintains lists of patterns for the addresses of
- known and subscribed mailing lists. Every subscribed mailing list is
- known. To mark a mailing list as known, use the "lists" command. To mark
- it as subscribed, use "subscribe".
-
- You can use regular expressions with both commands. To mark all messages
- sent to a specific bug report's address on mutt's bug tracking system as
- list mail, for instance, you could say "subscribe [0-9]*@bugs.guug.de".
- Often, it's sufficient to just give a portion of the list's e-mail
- address.
-
- Specify as much of the address as you need to to remove ambiguity. For
- example, if you've subscribed to the Mutt mailing list, you will receive
- mail addressed to mutt-users@mutt.org. So, to tell Mutt that this is a
- mailing list, you could add "lists mutt-users@" to your initialization
- file. To tell mutt that you are subscribed to it, add "subscribe
- mutt-users" to your initialization file instead. If you also happen to get
- mail from someone whose address is mutt-users@example.com, you could use
- "lists ^mutt-users@mutt\\.org$" or "subscribe ^mutt-users@mutt\\.org$" to
- match only mail from the actual list.
-
- The -group flag adds all of the subsequent regular expressions to the
- named group.
-
- 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".
-
-13. Using Multiple spool mailboxes
-
- Usage:
-
- mbox-hook [!]pattern mailbox
-
- This command is used to move read messages from a specified mailbox to a
- different mailbox automatically when you quit or change folders. pattern
- is a regular expression specifying the mailbox to treat as a "spool"
- mailbox and mailbox specifies where mail should be saved when read.
-
- Unlike some of the other hook commands, only the first matching pattern is
- used (it is not possible to save read mail in more than a single mailbox).
-
-14. Monitoring incoming mail
-
- Usage:
-
- mailboxes mailbox [ mailbox ...]
-
- unmailboxes { * | mailbox ... }
-
- This command specifies folders which can receive mail and which will be
- checked for new messages periodically.
-
- folder can either be a local file or directory (Mbox/Mmdf or Maildir/Mh).
- If Mutt was built with POP and/or IMAP support, folder can also be a
- POP/IMAP folder URL. The URL syntax is described in Section 1.2, "URL
- syntax", POP and IMAP are described in Section 3, "POP3 Support" and
- Section 4, "IMAP Support" respectively.
-
- Mutt provides a number of advanced features for handling (possibly many)
- folders and new mail within them, please refer to Section 9, "Handling
- multiple folders" for details (including in what situations and how often
- Mutt checks for new mail).
-
- The "unmailboxes" command is used to remove a token from the list of
- folders which receive mail. Use "unmailboxes *" to remove all tokens.
-
- Note
-
- The folders in the mailboxes command are resolved when the command is
- executed, so if these names contain shortcut characters (such as "=" and
- "!"), any variable definition that affects these characters (like $folder
- and $spoolfile) should be set before the mailboxes command. If none of
- these shorcuts are used, a local path should be absolute as otherwise mutt
- tries to find it relative to the directory from where mutt was started
- which may not always be desired.
-
- For Mbox and Mmdf folders, new mail is detected by comparing access and/or
- modification times of files: Mutt assumes a folder has new mail if it
- wasn't accessed after it was last modified. Utilities like biff or frm or
- any other program which accesses the mailbox might cause Mutt to never
- detect new mail for that mailbox if they do not properly reset the access
- time. Other possible causes of Mutt not detecting new mail in these
- folders are backup tools (updating access times) or filesystems mounted
- without access time update support.
-
- In cases where new mail detection for Mbox or Mmdf folders appears to be
- unreliable, the $check_mbox_size option can be used to make Mutt track and
- consult file sizes for new mail detection instead.
-
-15. User defined headers
-
- Usage:
-
- my_hdr string
-
- unmy_hdr { * | field ... }
-
- The my_hdr command allows you to create your own header fields which will
- be added to every message you send.
-
- For example, if you would like to add an "Organization:" header field to
- all of your outgoing messages, you can put the command
-
- Example 3.10. Defining custom headers
-
- my_hdr Organization: A Really Big Company, Anytown, USA
-
- in your .muttrc.
-
- Note
-
- Space characters are not allowed between the keyword and the colon (":").
- The standard for electronic mail (RFC2822) says that space is illegal
- there, so Mutt enforces the rule.
-
- If you would like to add a header field to a single message, you should
- either set the $edit_headers variable, or use the <edit-headers> function
- (default: "E") in the compose menu so that you can edit the header of your
- message along with the body.
-
- To remove user defined header fields, use the unmy_hdr command. You may
- specify an asterisk ("*") to remove all header fields, or the fields to
- remove. For example, to remove all "To" and "Cc" header fields, you could
- use:
-
- unmy_hdr to cc
-
-16. Specify default save mailbox
-
- Usage:
-
- save-hook [!]pattern mailbox
-
- This command is used to override the default mailbox used when saving
- messages. mailbox will be used as the default if the message matches
- pattern, see Message Matching in Hooks for information on the exact
- format.
-
- To provide more flexibility and good defaults, Mutt applies the expandos
- of $index_format to mailbox after it was expanded.
-
- Examples:
-
- Example 3.11. Using %-expandos in save-hook
-
- # default: save all to ~/Mail/<author name>
- save-hook . ~/Mail/%F
-
- # save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
- save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
- # save from aol.com to $folder/spam
- save-hook aol\\.com$ +spam
-
- Also see the fcc-save-hook command.
-
-17. Specify default Fcc: mailbox when composing
-
- Usage:
-
- fcc-hook [!]pattern mailbox
-
- This command is used to save outgoing mail in a mailbox other than
- $record. Mutt 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.
-
- To provide more flexibility and good defaults, Mutt applies the expandos
- of $index_format to mailbox after it was expanded.
-
- See Message Matching in Hooks for information on the exact format of
- pattern.
-
- Example: fcc-hook [@.]aol\\.com$ +spammers
-
- The above will save a copy of all messages going to the aol.com domain to
- the `+spammers' mailbox by default. Also see the fcc-save-hook command.
-
-18. Specify default save filename and default Fcc: mailbox at once
-
- Usage:
-
- fcc-save-hook [!]pattern mailbox
-
- This command is a shortcut, equivalent to doing both a fcc-hook and a
- save-hook with its arguments, including %-expansion on mailbox according
- to $index_format.
-
-19. Change settings based upon message recipients
-
- Usage:
-
- reply-hook [!]pattern command
-
- send-hook [!]pattern command
-
- send2-hook [!]pattern command
-
- These commands can be used to execute arbitrary configuration commands
- based upon recipients of the message. pattern is used to match the
- message, see Message Matching in Hooks for details. command is executed
- when pattern matches.
-
- 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 user's configuration file.
-
- send2-hook is matched every time a message is changed, either by editing
- it, or by using the compose menu to change its recipients or subject.
- send2-hook is executed after send-hook, and can, e.g., be used to set
- parameters such as the $sendmail variable depending on the message's
- sender address.
-
- For each type of send-hook or reply-hook, when multiple matches occur,
- commands are executed in the order they are specified in the muttrc (for
- that type of hook).
-
- Example: send-hook mutt "set mime_forward signature=''"
-
- Another typical use for this command is to change the values of the
- $attribution, $signature and $locale variables in order to change the
- language of the attributions and signatures based upon the recipients.
-
- Note
-
- 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.
-
-20. Change settings before formatting a message
-
- Usage:
-
- message-hook [!]pattern command
-
- This command can be used to execute arbitrary configuration commands
- before viewing or formatting a message based upon information about the
- message. command is executed if the pattern matches the message to be
- displayed. When multiple matches occur, commands are executed in the order
- they are specified in the muttrc.
-
- See Message Matching in Hooks for information on the exact format of
- pattern.
-
- Example:
-
- message-hook ~A 'set pager=builtin'
- message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
-
-21. Choosing the cryptographic key of the recipient
-
- Usage:
-
- crypt-hook pattern keyid
-
- When encrypting messages with PGP/GnuPG 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
- would normally use. The crypt-hook command provides a method by which you
- can specify the ID of the public key to be used when encrypting messages
- to a certain recipient.
-
- The meaning of keyid 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.
-
-22. Adding key sequences to the keyboard buffer
-
- Usage:
-
- push string
-
- This command adds the named string to the keyboard buffer. The string may
- contain control characters, key names and function names like the sequence
- string in the macro command. You may use it to automatically run a
- sequence of commands at startup, or when entering certain folders. For
- example, the following command will automatically collapse all threads
- when entering a folder:
-
- Example 3.12. Embedding push in folder-hook
-
- folder-hook . 'push <collapse-all>'
-
-23. Executing functions
-
- Usage:
-
- exec function [ function ...]
-
- This command can be used to execute any function. Functions are listed in
- the function reference. "exec function" is equivalent to "push
- <function>".
-
-24. Message Scoring
-
- Usage:
-
- score pattern value
-
- unscore { * | pattern ... }
-
- The score commands adds value to a message's score if pattern matches it.
- pattern is a string in the format described in the patterns section (note:
- For efficiency reasons, patterns which scan information not available in
- the index, such as ~b, ~B or ~h, may not be used). value is a positive or
- negative integer. A message's final score is the sum total of all matching
- score entries. However, you may optionally prefix value with an equal sign
- (=) to cause evaluation to stop at a particular entry if there is a match.
- Negative final scores are rounded up to 0.
-
- The unscore command removes score entries from the list. You must specify
- the same pattern specified in the score command for it to be removed. The
- pattern "*" is a special token which means to clear the list of all score
- entries.
-
-25. Spam detection
-
- Usage:
-
- spam pattern format
-
- nospam { * | pattern }
-
- Mutt has generalized support for external spam-scoring filters. By
- defining your spam patterns with the spam and nospam commands, you can
- limit, search, and sort your mail based on its spam attributes, as
- determined by the external filter. You also can display the spam
- attributes in your index display using the %H selector in the
- $index_format variable. (Tip: try %?H?[%H] ? to display spam tags only
- when they are defined for a given message.)
-
- Your first step is to define your external filter's spam patterns using
- the spam command. pattern should be a regular expression that matches a
- header in a mail message. If any message in the mailbox matches this
- regular expression, it will receive a "spam tag" or "spam attribute"
- (unless it also matches a nospam pattern -- see below.) The appearance of
- this attribute is entirely up to you, and is governed by the format
- parameter. format can be any static text, but it also can include
- back-references from the pattern expression. (A regular expression
- "back-reference" refers to a sub-expression contained within parentheses.)
- %1 is replaced with the first back-reference in the regex, %2 with the
- second, etc.
-
- If you're using multiple spam filters, a message can have more than one
- spam-related header. You can define spam patterns for each filter you use.
- If a message matches two or more of these patterns, and the
- $spam_separator variable is set to a string, then the message's spam tag
- will consist of all the format strings joined together, with the value of
- $spam_separator separating them.
-
- For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
- define these spam settings:
-
- Example 3.13. Configuring spam detection
-
- spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
- spam "X-Spam-Status: Yes" "90+/SA"
- spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
- set spam_separator=", "
-
- If I then received a message that DCC registered with "many" hits under
- the "Fuz2" checksum, and that PureMessage registered with a 97%
- probability of being spam, that message's spam tag would read
- 90+/DCC-Fuz2, 97/PM. (The four characters before "=many" in a DCC report
- indicate the checksum used -- in this case, "Fuz2".)
-
- If the $spam_separator variable is unset, then each spam pattern match
- supersedes the previous one. Instead of getting joined format strings,
- you'll get only the last one to match.
-
- The spam tag is what will be displayed in the index when you use %H in the
- $index_format variable. It's also the string that the ~H pattern-matching
- expression matches against for <search> and <limit> functions. And it's
- what sorting by spam attribute will use as a sort key.
-
- That's a pretty complicated example, and most people's actual environments
- will have only one spam filter. The simpler your configuration, the more
- effective mutt can be, especially when it comes to sorting.
-
- Generally, when you sort by spam tag, mutt will sort lexically -- that is,
- by ordering strings alphanumerically. 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 lower priority 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 a more 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"
-
-26. Setting and Querying Variables
-
- 26.1. Commands
-
- The following commands are available to manipulate and query variables:
-
- Usage:
-
- set { [ no | inv ] variable | variable=value } [...]
-
- toggle variable [ variable ...]
-
- unset variable [ variable ...]
-
- reset variable [ variable ...]
-
- This command is used to set (and unset) configuration variables. There are
- four basic types of variables: boolean, number, string and quadoption.
- boolean variables can be set (true) or unset (false). number variables can
- be assigned a positive integer value. string variables consist of any
- number of printable characters and must be enclosed in quotes if they
- contain spaces or tabs. You may also use the escape sequences "\n" and
- "\t" for newline and tab, respectively. quadoption variables are used to
- control whether or not to be prompted for certain actions, or to specify a
- default action. A value of yes will cause the action to be carried out
- automatically as if you had answered yes to the question. Similarly, a
- value of no will cause the action to be carried out as if you had answered
- "no." A value of ask-yes will cause a prompt with a default answer of
- "yes" and ask-no will provide a default answer of "no."
-
- Prefixing a variable with "no" will unset it. Example: set noaskbcc.
-
- For boolean variables, you may optionally prefix the variable name with
- inv to toggle the value (on or off). This is useful when writing macros.
- Example: set invsmart_wrap.
-
- The toggle command automatically prepends the inv prefix to all specified
- variables.
-
- The unset command automatically prepends the no prefix to all specified
- variables.
-
- Using the <enter-command> function in the index menu, you can query the
- value of a variable by prefixing the name of the variable with a question
- mark:
-
- set ?allow_8bit
-
- The question mark is actually only required for boolean and quadoption
- variables.
-
- The reset command resets all given variables to the compile time defaults
- (hopefully mentioned in this manual). If you use the command set and
- prefix the variable with "&" this has the same behavior as the reset
- command.
-
- With the reset command there exists the special variable "all", which
- allows you to reset all variables to their system defaults.
-
- 26.2. User-defined variables
-
- 26.2.1. Introduction
-
- Along with the variables listed in the Configuration variables section,
- mutt supports user-defined variables with names starting with my_ as in,
- for example, my_cfgdir.
-
- The set command either creates a custom my_ variable or changes its value
- if it does exist already. The unset and reset commands remove the variable
- entirely.
-
- Since user-defined variables are expanded in the same way that environment
- variables are (except for the shell-escape command and backtick
- expansion), this feature can be used to make configuration files more
- readable.
-
- 26.2.2. Examples
-
- The following example defines and uses the variable my_cfgdir to
- abbreviate the calls of the source command:
-
- Example 3.14. Using user-defined variables for config file readability
-
- set my_cfgdir = $HOME/mutt/config
-
- source $my_cfgdir/hooks
- source $my_cfgdir/macros
- # more source commands...
-
- A custom variable can also be used in macros to backup the current value
- of another variable. In the following example, the value of the $delete is
- changed temporarily while its original value is saved as my_delete. After
- the macro has executed all commands, the original value of $delete is
- restored.
-
- Example 3.15. Using user-defined variables for backing up other config
- option values
-
- macro pager ,x '\
- <enter-command>set my_delete=$delete<enter>\
- <enter-command>set delete=yes<enter>\
- ...\
- <enter-command>set delete=$my_delete<enter>'
-
- Since mutt expands such values already when parsing the configuration
- file(s), the value of $my_delete in the last example would be the value of
- $delete exactly as it was at that point during parsing the configuration
- file. If another statement would change the value for $delete later in the
- same or another file, it would have no effect on $my_delete. However, the
- expansion can be deferred to runtime, as shown in the next example, when
- escaping the dollar sign.
-
- Example 3.16. Deferring user-defined variable expansion to runtime
-
- macro pager <PageDown> "\
- <enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
- <next-page>\
- <enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
- <enter-command> unset my_old_pager_stop<Enter>"
-
- Note that there is a space between <enter-command> and the set
- configuration command, preventing mutt from recording the macro's commands
- into its history.
-
-27. Reading initialization commands from another file
-
- Usage:
-
- source filename
-
- This command allows the inclusion of initialization commands from other
- files. For example, I place all of my aliases in ~/.mail_aliases so that I
- can make my ~/.muttrc readable and keep my aliases private.
-
- If the filename begins with a tilde ("~"), it will be expanded to the path
- of your home directory.
-
- If the filename ends with a vertical bar (|), then filename is considered
- to be an executable program from which to read input (eg. source
- ~/bin/myscript|).
-
-28. Configuring features conditionnaly
-
- Usage: ifdef item command
-
- This command allows to test if a feature has been compiled in, before
- actually executing the command. Item can be either the name of a function,
- variable, or command. Example:
-
- ifdef imap_keepalive 'source ~/.mutt/imap_setup'
-
-29. Removing hooks
-
- Usage:
-
- unhook { * | hook-type }
-
- This command permits you to flush hooks you have previously defined. You
- can either remove all hooks by giving the "*" character as an argument, or
- you can remove all hooks of a specific type by saying something like
- unhook send-hook.
-
-30. Format Strings
-
- 30.1. Basic usage
-
- Format strings are a general concept you'll find in several locations
- through the mutt configuration, especially in the $index_format,
- $pager_format, $status_format, and other "*_format" variables. These can
- be very straightforward, and it's quite possible you already know how to
- use them.
-
- The most basic format string element is a percent symbol followed by
- another character. For example, %s represents a message's Subject: header
- in the $index_format variable. The "expandos" available are documented
- with each format variable, but there are general modifiers available with
- all formatting expandos, too. Those are our concern here.
-
- Some of the modifiers are borrowed right out of C (though you might know
- them from Perl, Python, shell, or another language). These are the [-]m.n
- modifiers, as in %-12.12s. As with such programming languages, these
- modifiers allow you to specify the minimum and maximum size of the
- resulting string, as well as its justification. If the "-" sign follows
- the percent, the string will be left-justified instead of right-justified.
- If there's a number immediately following that, it's the minimum amount of
- space the formatted string will occupy -- if it's naturally smaller than
- that, it will be padded out with spaces. If a decimal point and another
- number follow, that's the maximum space allowable -- the string will not
- be permitted to exceed that width, no matter its natural size. Each of
- these three elements is optional, so that all these are legal format
- strings: %-12s %4c %.15F %-12.15L
-
- Mutt adds some other modifiers to format strings. If you use an equals
- symbol (=) as a numeric prefix (like the minus above), it will force the
- string to be centered within its minimum space range. For example, %=14y
- will reserve 14 characters for the %y expansion -- that's the X-Label:
- header, in $index_format. If the expansion results in a string less than
- 14 characters, it will be centered in a 14-character space. If the X-Label
- for a message were "test", that expansion would look like " test ".
-
- There are two very little-known modifiers that affect the way that an
- expando is replaced. If there is an underline ("_") character between any
- format modifiers (as above) and the expando letter, it will expands in all
- lower case. And if you use a colon (":"), it will replace all decimal
- points with underlines.
-
- 30.2. Filters
-
- Any format string ending in a vertical bar ("|") will be expanded and
- piped through the first word in the string, using spaces as separator. The
- string returned will be used for display. If the returned string ends in
- %, it will be passed through the formatter a second time. This allows the
- filter to generate a replacement format string including % expandos.
-
- All % expandos in a format string are expanded before the script is called
- so that:
-
- Example 3.17. Using external filters in format strings
-
- set status_format="script.sh '%r %f (%L)'|"
-
- will make mutt expand %r, %f and %L before calling the script. The example
- also shows that arguments can be quoted: the script will receive the
- expanded string between the single quotes as the only argument.
-
- A practical example is the mutt_xtitle script installed in the samples
- subdirectory of the mutt documentation: it can be used as filter for
- $status_format to set the current terminal's title, if supported.
-
-Chapter 4. Advanced Usage
-
- Table of Contents
-
- 1. Regular Expressions
-
- 2. Patterns: Searching, Limiting and Tagging
-
- 2.1. Pattern Modifier
-
- 2.2. Simple Patterns
-
- 2.3. Complex Patterns
-
- 2.4. Searching by Date
-
- 3. Using Tags
-
- 4. Using Hooks
-
- 4.1. Message Matching in Hooks
-
- 5. External Address Queries
-
- 6. Mailbox Formats
-
- 7. Mailbox Shortcuts
-
- 8. Handling Mailing Lists
-
- 9. Handling multiple folders
-
- 10. Editing threads
-
- 10.1. Linking threads
-
- 10.2. Breaking threads
-
- 11. Delivery Status Notification (DSN) Support
-
- 12. Start a WWW Browser on URLs
-
-1. Regular Expressions
-
- All string patterns in Mutt including those in more complex patterns must
- be specified using regular expressions (regexp) in the "POSIX extended"
- syntax (which is more or less the syntax used by egrep and GNU awk). For
- your convenience, we have included below a brief description of this
- syntax.
-
- The search is case sensitive if the pattern contains at least one upper
- case letter, and case insensitive otherwise.
-
- Note
-
- 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
-
- 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 Syntax of Initialization Files for more information on "
- and ' delimiter processing. To match a literal " or ' you must preface it
- with \ (backslash).
-
- The fundamental building blocks are the regular expressions that match a
- single character. Most characters, including all letters and digits, are
- regular expressions that match themselves. Any metacharacter with special
- meaning may be quoted by preceding it with a backslash.
-
- The period "." matches any single character. The caret "^" and the dollar
- sign "$" are metacharacters that respectively match the empty string at
- the beginning and end of a line.
-
- A list of characters enclosed by "[" and "]" matches any single character
- in that list; if the first character of the list is a caret "^" then it
- matches any character not in the list. For example, the regular expression
- [0123456789] matches any single digit. A range of ASCII characters may be
- specified by giving the first and last characters, separated by a hyphen
- "-". Most metacharacters lose their special meaning inside lists. To
- include a literal "]" place it first in the list. Similarly, to include a
- literal "^" place it anywhere but first. Finally, to include a literal
- hyphen "-" place it last.
-
- Certain named classes of characters are predefined. Character classes
- consist of "[:", a keyword denoting the class, and ":]". The following
- classes are defined by the POSIX standard in Table 4.1, "POSIX regular
- expression character classes"
-
- Table 4.1. POSIX regular expression character classes
-
- +------------------------------------------------------------------------+
- | Character class | Description |
- |-----------------+------------------------------------------------------|
- | [:alnum:] | Alphanumeric characters |
- |-----------------+------------------------------------------------------|
- | [:alpha:] | Alphabetic characters |
- |-----------------+------------------------------------------------------|
- | [:blank:] | Space or tab characters |
- |-----------------+------------------------------------------------------|
- | [:cntrl:] | Control characters |
- |-----------------+------------------------------------------------------|
- | [:digit:] | Numeric characters |
- |-----------------+------------------------------------------------------|
- | | Characters that are both printable and visible. (A |
- | [:graph:] | space is printable, but not visible, while an "a" is |
- | | both) |
- |-----------------+------------------------------------------------------|
- | [:lower:] | Lower-case alphabetic characters |
- |-----------------+------------------------------------------------------|
- | [:print:] | Printable characters (characters that are not |
- | | control characters) |
- |-----------------+------------------------------------------------------|
- | | Punctuation characters (characters that are not |
- | [:punct:] | letter, digits, control characters, or space |
- | | characters) |
- |-----------------+------------------------------------------------------|
- | [:space:] | Space characters (such as space, tab and formfeed, |
- | | to name a few) |
- |-----------------+------------------------------------------------------|
- | [:upper:] | Upper-case alphabetic characters |
- |-----------------+------------------------------------------------------|
- | [:xdigit:] | Characters that are hexadecimal digits |
- +------------------------------------------------------------------------+
-
- A character class is only valid in a regular expression inside the
- brackets of a character list.
-
- Note
-
- Note that the brackets in these class names are part of the symbolic
- names, and must be included in addition to the brackets delimiting the
- bracket list. For example, [[:digit:]] is equivalent to [0-9].
-
- Two additional special sequences can appear in character lists. These
- apply to non-ASCII character sets, which can have single symbols (called
- collating elements) that are represented with more than one character, as
- well as several characters that are equivalent for collating or sorting
- purposes:
-
- Collating Symbols
-
- A collating symbol is a multi-character collating element enclosed
- in "[." and ".]". For example, if "ch" is a collating element,
- then [[.ch.]] is a regexp that matches this collating element,
- while [ch] is a regexp that matches either "c" or "h".
-
- Equivalence Classes
-
- An equivalence class is a locale-specific name for a list of
- characters that are equivalent. The name is enclosed in "[=" and
- "=]". For example, the name "e" might be used to represent all of
- "e" "e" and "e". In this case, [[=e=]] is a regexp that matches
- any of "e", "e" and "e".
-
- A regular expression matching a single character may be followed by one of
- several repetition operators described in Table 4.2, "Regular expression
- repetition operators".
-
- Table 4.2. Regular expression repetition operators
-
- +------------------------------------------------------------------------+
- | Operator | Description |
- |----------+-------------------------------------------------------------|
- | ? | The preceding item is optional and matched at most once |
- |----------+-------------------------------------------------------------|
- | * | The preceding item will be matched zero or more times |
- |----------+-------------------------------------------------------------|
- | + | The preceding item will be matched one or more times |
- |----------+-------------------------------------------------------------|
- | {n} | The preceding item is matched exactly n times |
- |----------+-------------------------------------------------------------|
- | {n,} | The preceding item is matched n or more times |
- |----------+-------------------------------------------------------------|
- | {,m} | The preceding item is matched at most m times |
- |----------+-------------------------------------------------------------|
- | {n,m} | The preceding item is matched at least n times, but no more |
- | | than m times |
- +------------------------------------------------------------------------+
-
- Two regular expressions may be concatenated; the resulting regular
- expression matches any string formed by concatenating two substrings that
- respectively match the concatenated subexpressions.
-
- Two regular expressions may be joined by the infix operator "|"; the
- resulting regular expression matches any string matching either
- subexpression.
-
- Repetition takes precedence over concatenation, which in turn takes
- precedence over alternation. A whole subexpression may be enclosed in
- parentheses to override these precedence rules.
-
- Note
-
- If you compile Mutt with the GNU rx package, the following operators may
- also be used in regular expressions as described in Table 4.3, "GNU
- regular expression extensions".
-
- Table 4.3. GNU regular expression extensions
-
- +------------------------------------------------------------------------+
- | Expression | Description |
- |------------+-----------------------------------------------------------|
- | \\y | Matches the empty string at either the beginning or the |
- | | end of a word |
- |------------+-----------------------------------------------------------|
- | \\B | Matches the empty string within a word |
- |------------+-----------------------------------------------------------|
- | \\< | Matches the empty string at the beginning of a word |
- |------------+-----------------------------------------------------------|
- | \\> | Matches the empty string at the end of a word |
- |------------+-----------------------------------------------------------|
- | \\w | Matches any word-constituent character (letter, digit, or |
- | | underscore) |
- |------------+-----------------------------------------------------------|
- | \\W | Matches any character that is not word-constituent |
- |------------+-----------------------------------------------------------|
- | \\` | Matches the empty string at the beginning of a buffer |
- | | (string) |
- |------------+-----------------------------------------------------------|
- | \\' | Matches the empty string at the end of a buffer |
- +------------------------------------------------------------------------+
-
- Please note however that these operators are not defined by POSIX, so they
- may or may not be available in stock libraries on various systems.
-
-2. Patterns: Searching, Limiting and Tagging
-
- Many of Mutt's commands allow you to specify a pattern to match (limit,
- tag-pattern, delete-pattern, etc.). Table 4.4, "Pattern modifiers" shows
- several ways to select messages.
-
- Table 4.4. Pattern modifiers
-
- +------------------------------------------------------------------------+
- | Pattern modifier | Description |
- |------------------+-----------------------------------------------------|
- | ~A | all messages |
- |------------------+-----------------------------------------------------|
- | ~b EXPR | messages which contain EXPR in the message body |
- |------------------+-----------------------------------------------------|
- | | messages which contain STRING in the message body. |
- | =b STRING | If IMAP is enabled, searches for STRING on the |
- | | server, rather than downloading each message and |
- | | searching it locally. |
- |------------------+-----------------------------------------------------|
- | ~B EXPR | messages which contain EXPR in the whole message |
- |------------------+-----------------------------------------------------|
- | ~c EXPR | messages carbon-copied to EXPR |
- |------------------+-----------------------------------------------------|
- | %c GROUP | messages carbon-copied to any member of GROUP |
- |------------------+-----------------------------------------------------|
- | ~C EXPR | messages either to: or cc: EXPR |
- |------------------+-----------------------------------------------------|
- | %C GROUP | messages either to: or cc: to any member of GROUP |
- |------------------+-----------------------------------------------------|
- | ~d [MIN]-[MAX] | messages with "date-sent" in a Date range |
- |------------------+-----------------------------------------------------|
- | ~D | deleted messages |
- |------------------+-----------------------------------------------------|
- | ~e EXPR | messages which contains EXPR in the "Sender" field |
- |------------------+-----------------------------------------------------|
- | %e GROUP | messages which contain a member of GROUP in the |
- | | "Sender" field |
- |------------------+-----------------------------------------------------|
- | ~E | expired messages |
- |------------------+-----------------------------------------------------|
- | ~F | flagged messages |
- |------------------+-----------------------------------------------------|
- | ~f EXPR | messages originating from EXPR |
- |------------------+-----------------------------------------------------|
- | %f GROUP | messages originating from any member of GROUP |
- |------------------+-----------------------------------------------------|
- | ~g | cryptographically signed messages |
- |------------------+-----------------------------------------------------|
- | ~G | cryptographically encrypted messages |
- |------------------+-----------------------------------------------------|
- | ~h EXPR | messages which contain EXPR in the message header |
- |------------------+-----------------------------------------------------|
- | ~H EXPR | messages with a spam attribute matching EXPR |
- |------------------+-----------------------------------------------------|
- | ~i EXPR | messages which match EXPR in the "Message-ID" field |
- |------------------+-----------------------------------------------------|
- | ~k | messages which contain PGP key material |
- |------------------+-----------------------------------------------------|
- | ~L EXPR | messages either originated or received by EXPR |
- |------------------+-----------------------------------------------------|
- | %L GROUP | message either originated or received by any member |
- | | of GROUP |
- |------------------+-----------------------------------------------------|
- | ~l | messages addressed to a known mailing list |
- |------------------+-----------------------------------------------------|
- | ~m [MIN]-[MAX] | messages in the range MIN to MAX *) |
- |------------------+-----------------------------------------------------|
- | ~n [MIN]-[MAX] | messages with a score in the range MIN to MAX *) |
- |------------------+-----------------------------------------------------|
- | ~N | new messages |
- |------------------+-----------------------------------------------------|
- | ~O | old messages |
- |------------------+-----------------------------------------------------|
- | ~p | messages addressed to you (consults alternates) |
- |------------------+-----------------------------------------------------|
- | ~P | messages from you (consults alternates) |
- |------------------+-----------------------------------------------------|
- | ~Q | messages which have been replied to |
- |------------------+-----------------------------------------------------|
- | ~r [MIN]-[MAX] | messages with "date-received" in a Date range |
- |------------------+-----------------------------------------------------|
- | ~R | read messages |
- |------------------+-----------------------------------------------------|
- | ~s EXPR | messages having EXPR in the "Subject" field. |
- |------------------+-----------------------------------------------------|
- | ~S | superseded messages |
- |------------------+-----------------------------------------------------|
- | ~t EXPR | messages addressed to EXPR |
- |------------------+-----------------------------------------------------|
- | ~T | tagged messages |
- |------------------+-----------------------------------------------------|
- | ~u | messages addressed to a subscribed mailing list |
- |------------------+-----------------------------------------------------|
- | ~U | unread messages |
- |------------------+-----------------------------------------------------|
- | ~v | messages part of a collapsed thread. |
- |------------------+-----------------------------------------------------|
- | ~V | cryptographically verified messages |
- |------------------+-----------------------------------------------------|
- | ~x EXPR | messages which contain EXPR in the "References" |
- | | field |
- |------------------+-----------------------------------------------------|
- | ~X [MIN]-[MAX] | messages with MIN to MAX attachments *) |
- |------------------+-----------------------------------------------------|
- | ~y EXPR | messages which contain EXPR in the "X-Label" field |
- |------------------+-----------------------------------------------------|
- | ~z [MIN]-[MAX] | messages with a size in the range MIN to MAX *) |
- |------------------+-----------------------------------------------------|
- | ~= | duplicated messages (see $duplicate_threads) |
- |------------------+-----------------------------------------------------|
- | ~$ | unreferenced messages (requires threaded view) |
- |------------------+-----------------------------------------------------|
- | | messages in threads containing messages matching |
- | ~(PATTERN) | PATTERN, e.g. all threads containing messages from |
- | | you: ~(~P) |
- +------------------------------------------------------------------------+
-
- Where EXPR is a regular expression. Special attention has to be made when
- using regular expressions inside of patterns. Specifically, Mutt'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
- ("\\"). You can force mutt to treat EXPR as a simple string instead of a
- regular expression by using = instead of ~ in the pattern name. For
- example, =b *.* will find all messages that contain the literal string
- "*.*". Simple string matches are less powerful than regular expressions
- but can be considerably faster. This is especially true for IMAP folders,
- because string matches can be performed on the server instead of by
- fetching every message. IMAP treats =h specially: it must be of the form
- "header: substring" and will not partially match header names. The
- substring part may be omitted if you simply wish to find messages
- containing a particular header without regard to its value.
-
- *) The forms "<[MAX]", ">[MIN]", "[MIN]-" and "-[MAX]" are allowed, too.
-
- 2.1. Pattern Modifier
-
- Note
-
- Note that patterns matching 'lists' of addresses (notably c, C, p, P and
- t) match if there is at least one match in the whole list. If you want to
- make sure that all elements of that list match, you need to prefix your
- pattern with "^". This example matches all mails which only has recipients
- from Germany.
-
- ^~C \.de$
-
- 2.2. Simple Patterns
-
- Mutt supports two versions of so called "simple searches" which are issued
- if the query entered for searching, limiting and similar operations does
- not seem to be a valid pattern (i.e. it does not contain one of these
- characters: "~", "=" or "%"). If the query is supposed to contain one of
- these special characters, they must be escaped by prepending a backslash
- ("\").
-
- The first type is by checking whether the query string equals a keyword
- case-insensitively from Table 4.5, "Simple search keywords": If that is
- the case, Mutt will use the shown pattern modifier instead. If a keyword
- would conflict with your search keyword, you need to turn it into a
- regular expression to avoid matching the keyword table. For example, if
- you want to find all messages matching "flag" (using $simple_search) but
- don't want to match flagged messages, simply search for "[f]lag".
-
- Table 4.5. Simple search keywords
-
- +----------------------------+
- | Keyword | Pattern modifier |
- |---------+------------------|
- | all | ~A |
- |---------+------------------|
- | . | ~A |
- |---------+------------------|
- | ^ | ~A |
- |---------+------------------|
- | del | ~D |
- |---------+------------------|
- | flag | ~F |
- |---------+------------------|
- | new | ~N |
- |---------+------------------|
- | old | ~O |
- |---------+------------------|
- | repl | ~Q |
- |---------+------------------|
- | read | ~R |
- |---------+------------------|
- | tag | ~T |
- |---------+------------------|
- | unread | ~U |
- +----------------------------+
-
- The second type of simple search is to build a complex search pattern
- using $simple_search as a template. Mutt will insert your query properly
- quoted and search for the composed complex query.
-
- 2.3. Complex Patterns
-
- Logical AND is performed by specifying more than one criterion. For
- example:
-
- ~t mutt ~f elkins
-
- would select messages which contain the word "mutt" in the list of
- recipients and that have the word "elkins" in the "From" header field.
-
- Mutt also recognizes the following operators to create more complex search
- patterns:
-
- o ! -- logical NOT operator
-
- o | -- logical OR operator
-
- o () -- logical grouping operator
-
- Here is an example illustrating a complex search pattern. This pattern
- will select all messages which do not contain "mutt" in the "To" or "Cc"
- field and which are from "elkins".
-
- Example 4.1. Using boolean operators in patterns
-
- !(~t mutt|~c mutt) ~f elkins
-
- Here is an example using white space in the regular expression (note the '
- and " delimiters). For this to match, the mail's subject must match the
- "^Junk +From +Me$" and it must be from either "Jim +Somebody" or "Ed
- +SomeoneElse":
-
- '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
-
- Note
-
- If a regular expression contains parenthesis, or a vertical bar ("|"), you
- must enclose the expression in double or single quotes since those
- characters are also used to separate different parts of Mutt's pattern
- language. For example: ~f "me@(mutt\.org|cs\.hmc\.edu)"
-
- Without the quotes, the parenthesis wouldn't end. This would be separated
- to two OR'd patterns: ~f me@(mutt\.org and cs\.hmc\.edu). They are never
- what you want.
-
- 2.4. Searching by Date
-
- Mutt supports two types of dates, absolute and relative.
-
- Absolute. Dates must be in DD/MM/YY format (month and year are optional,
- defaulting to the current month and year). An example of a valid range of
- dates is:
-
- Limit to messages matching: ~d 20/1/95-31/10
-
- If you omit the minimum (first) date, and just specify "-DD/MM/YY", all
- messages before the given date will be selected. If you omit the maximum
- (second) date, and specify "DD/MM/YY-", all messages after the given date
- will be selected. If you specify a single date with no dash ("-"), only
- messages sent on the given date will be selected.
-
- Error Margins. You can add error margins to absolute dates. An error
- margin is a sign (+ or -), followed by a digit, followed by one of the
- units in Table 4.6, "Date units". As a special case, you can replace the
- sign by a "*" character, which is equivalent to giving identical plus and
- minus error margins.
-
- Table 4.6. Date units
-
- +--------------------+
- | Unit | Description |
- |------+-------------|
- | y | Years |
- |------+-------------|
- | m | Months |
- |------+-------------|
- | w | Weeks |
- |------+-------------|
- | d | Days |
- +--------------------+
-
- Example: To select any messages two weeks around January 15, 2001, you'd
- use the following pattern:
-
- Limit to messages matching: ~d 15/1/2001*2w
-
- Relative. This type of date is relative to the current date, and may be
- specified as:
-
- o >offset (messages older than offset units)
-
- o <offset (messages newer than offset units)
-
- o =offset (messages exactly offset units old)
-
- offset is specified as a positive number with one of the units from
- Table 4.6, "Date units".
-
- Example: to select messages less than 1 month old, you would use
-
- Limit to messages matching: ~d <1m
-
- Note
-
- All dates used when searching are relative to the local time zone, so
- unless you change the setting of your $index_format to include a %[...]
- format, these are not the dates shown in the main index.
-
-3. Using Tags
-
- Sometimes it is desirable to perform an operation on a group of messages
- all at once rather than one at a time. An example might be to save
- messages to a mailing list to a separate folder, or to delete all messages
- with a given subject. To tag all messages matching a pattern, use the
- <tag-pattern> function, which is bound to "shift-T" by default. Or you can
- select individual messages by hand using the <tag-message> function, which
- is bound to "t" by default. See patterns for Mutt'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 macros 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 will stop "eating" the macro when it encounters
- the "end-cond" operator; after this operator the rest of the macro will be
- executed as normal.
-
-4. Using Hooks
-
- A hook is a concept found in many other programs 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 world, a hook
- consists of a regular expression or pattern along with a configuration
- option/command. See
-
- o folder-hook
-
- o send-hook
-
- o message-hook
-
- o save-hook
-
- o mbox-hook
-
- o fcc-hook
-
- o fcc-save-hook
-
- for specific details on each type of hook available.
-
- Note
-
- If a hook changes configuration settings, these changes remain effective
- until the end of the current mutt session. As this is generally not
- desired, a default hook needs to be added before all other hooks to
- restore configuration defaults. Here is an example with send-hook and the
- my_hdr directive:
-
- Example 4.2. Combining send-hook and my_hdr
-
- send-hook . 'unmy_hdr From:'
- send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-
- 4.1. Message Matching in Hooks
-
- Hooks that act upon messages (message-hook, reply-hook, send-hook,
- send2-hook, save-hook, fcc-hook) are evaluated in a slightly different
- manner. For the other types of hooks, a regular expression 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 allows the use of the search pattern language for matching messages
- in hook commands. This works in exactly the same way as it would when
- limiting or searching 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 User <user@host>'
-
- which would execute the given command when sending mail to me@cs.hmc.edu.
-
- However, it is not required that you write the pattern to match using the
- full searching language. You can still specify a simple regular expression
- like the other hooks, in which case Mutt 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.
-
-5. External Address Queries
-
- Mutt supports connecting to external directory databases such as LDAP,
- ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using
- a simple interface. Using the $query_command variable, you specify the
- wrapper command to use. For example:
-
- set query_command = "mutt_ldap_query.pl '%s'"
-
- The wrapper script should accept the query on the command-line. It should
- return a one line message, then each matching response on a single line,
- each line containing a tab separated address then name then some other
- optional information. On error, or if there are no matching addresses,
- return a non-zero exit code and a one line error message.
-
- An example multiple response output:
-
- Searching database ... 20 entries ... 3 matching:
- me@cs.hmc.edu Michael Elkins mutt dude
- blong@fiction.net Brandon Long mutt and more
- roessler@does-not-exist.org 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 addresses to mail, start
- a new query, or have a new query appended to the current responses.
-
- The other mechanism for accessing the query function is for address
- completion, similar to the alias completion. In any prompt for address
- entry, you can use the <complete-query> function (default: ^T) to run a
- query based on the current address you have typed. Like aliases, mutt will
- look for what you have typed back to the last space or comma. If there is
- a single response for that query, mutt will expand the address in place.
- If there are multiple responses, mutt will activate the query menu. At the
- query menu, you can select one or more addresses to be added to the
- prompt.
-
-6. Mailbox Formats
-
- Mutt 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 new
- mailboxes, Mutt uses the default specified with the $mbox_type variable.
-
- mbox. This is the most widely used mailbox format for UNIX. All messages
- are stored in a single file. Each message has a line of the form:
-
- From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-
- to denote the start of a new message (this is often referred to as the
- "From_" line).
-
- MMDF. This is a variant of the mbox format. Each message is surrounded by
- lines containing "^A^A^A^A" (four control-A's).
-
- MH. A radical departure from mbox and MMDF, a mailbox consists of a
- directory and each message is stored in a separate file. The filename
- indicates the message number (however, this is may not correspond to the
- message number Mutt displays). Deleted messages are renamed with a comma
- (,) prepended to the filename. 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 two programs
- are writing the mailbox over NFS, which means that no file locking is
- needed.
-
-7. Mailbox Shortcuts
-
- There are a number of built in shortcuts which refer to specific
- mailboxes. These shortcuts can be used anywhere you are prompted for a
- file or mailbox path.
-
- o ! -- refers to your $spoolfile (incoming) mailbox
-
- o > -- refers to your $mbox file
-
- o < -- refers to your $record file
-
- o ^ -- refers to the current mailbox
-
- o - or !! -- refers to the file you've last visited
-
- o ~ -- refers to your home directory
-
- o = or + -- refers to your $folder directory
-
- o @alias -- refers to the default save folder as determined by the
- address of the alias
-
-8. Handling Mailing Lists
-
- Mutt 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 and subscribe commands in your muttrc.
-
- Now that Mutt 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 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 also supports the Mail-Followup-To header. When you send a message to
- a list of recipients which includes one or several subscribed mailing
- lists, and if the $followup_to option is set, mutt will generate a
- Mail-Followup-To header which contains all the recipients to whom you send
- this message, but not your address. This indicates that group-replies or
- list-replies (also known as "followups") to this message should only be
- sent to the original recipients of the message, and not separately to you
- - you'll receive your copy through one of the mailing lists you are
- subscribed to.
-
- Conversely, when group-replying or list-replying to a message which has a
- Mail-Followup-To header, mutt will respect this header if the
- $honor_followup_to configuration variable is set. Using list-reply will in
- this case also make sure that the reply goes to the mailing list, even if
- it's not specified in the list of recipients in the Mail-Followup-To.
-
- Note
-
- When header editing is enabled, you can create a Mail-Followup-To header
- manually. Mutt will only auto-generate this header if it doesn't exist
- when you send the message.
-
- The other method some mailing list admins use is to generate a "Reply-To"
- field which points back to the mailing list address rather than the author
- of the message. This can create problems when trying to reply directly to
- the author in private, since most mail clients will automatically reply to
- the address given in the "Reply-To" field. Mutt 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 in the "Reply-To" field, or reply directly to the address
- given in the "From" field. When set to yes, the "Reply-To" field will be
- used when present.
-
- The "X-Label:" header field can be used to further identify mailing lists
- or list subject matter (or just to annotate messages individually). The
- $index_format variable's "%y" and "%Y" escapes can be used to expand
- "X-Label:" fields in the index, and Mutt'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 procmail and other mail filtering agents.
-
- Lastly, Mutt 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 dealing with large volume
- mailing lists easier because you can easily delete uninteresting threads
- and quickly find topics of value.
-
-9. Handling multiple folders
-
- Mutt supports setups with multiple folders, allowing all of them to be
- monitored for new mail (see Section 14, "Monitoring incoming mail" for
- details).
-
- When in the index menu and being idle (also see $timeout), Mutt
- periodically checks for new mail in all folders which have been configured
- via the mailboxes command. The interval depends on the folder type: for
- local/IMAP folders it consults $mail_check and $pop_checkinterval for POP
- folders.
-
- Outside the index menu the directory browser supports checking for new
- mail using the <check-new> function which is unbound by default. Pressing
- TAB will bring up a menu showing the files specified by the mailboxes
- command, and indicate which contain new messages. Mutt will automatically
- enter this mode when invoked from the command line with the -y option.
-
- For the pager, index and directory browser menus, Mutt contains the
- <buffy-list> function (bound to "." by default) which will print a list of
- folders with new mail in the command line at the bottom of the screen.
-
- For the index, by default Mutt displays the number of mailboxes with new
- mail in the status bar, please refer to the $index_format variable for
- details.
-
- When changing folders, Mutt fills the prompt with the first folder from
- the mailboxes list containing new mail (if any), pressing space will cycle
- through folders with new mail.
-
-10. Editing threads
-
- Mutt 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.
-
- 10.1. Linking threads
-
- Some mailers tend to "forget" to correctly set the "In-Reply-To:" and
- "References:" headers when replying to a message. This results in broken
- discussions because Mutt has not enough information to guess the correct
- threading. You can fix this by tagging the reply, then moving to the
- parent message and using the <link-threads> function (bound to & by
- default). The reply will then be connected to this "parent" message.
-
- You can also connect multiple children at once, tagging them and using the
- tag-prefix command (';') or the auto_tag option.
-
- 10.2. Breaking threads
-
- On mailing lists, some people are in the bad habit of starting a new
- discussion by hitting "reply" to any message from the list and changing
- the subject to a totally unrelated one. You can fix such threads by using
- the <break-thread> function (bound by default to #), which will turn the
- subthread starting from the current message into a whole different thread.
-
-11. Delivery Status Notification (DSN) Support
-
- RFC1894 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."
-
- To support DSN, there are two variables. $dsn_notify is used to request
- receipts for different results (such as failed message, message delivered,
- etc.). $dsn_return requests how much of your message should be returned
- with the receipt (headers or full message).
-
- When using $sendmail for mail delivery, you need to use either Berkeley
- sendmail 8.8.x (or greater) a MTA supporting DSN command line options
- compatible to Sendmail: The -N and -R options can be used by the mail
- client to make requests as to what type of status messages should be
- returned. Please consider your MTA documentation whether DSN is supported.
-
- For SMTP delivery using $smtp_url, it depends on the capabilities
- announced by the server whether mutt will attempt to request DSN or not.
-
-12. Start a WWW Browser on URLs
-
- If a message contains URLs, it is efficient to get a menu with all the
- URLs and start a WWW browser on one of them. This functionality is
- provided by the external urlview program which can be retrieved at
- ftp://ftp.mutt.org/mutt/contrib/ and the configuration commands:
-
- macro index \cb |urlview\n
- macro pager \cb |urlview\n
-
-1. Compressed folders Support (OPTIONAL)
-
- If Mutt was compiled with compressed folders support (by running the
- configure script with the --enable-compressed flag), Mutt can open folders
- stored in an arbitrary format, provided that the user has a script to
- convert from/to this format to one of the accepted. The most common use is
- to open compressed archived folders e.g. with gzip. In addition, the user
- can provide a script that gets a folder in an accepted format and appends
- its context to the folder in the user-defined format, which may be faster
- than converting the entire folder to the accepted format, appending to it
- and converting back to the user-defined format. There are three hooks
- defined (open-hook, close-hook and append-hook) which define commands to
- uncompress and compress a folder and to append messages to an existing
- compressed folder respectively. For example:
-
- open-hook \\.gz$ "gzip -cd %f > %t"
- close-hook \\.gz$ "gzip -c %t > %f"
- append-hook \\.gz$ "gzip -c %t >> %f"
-
- You do not have to specify all of the commands. If you omit append-hook,
- the folder will be open and closed again each time you will add to it. If
- you omit close-hook (or give empty command) , the folder will be open in
- the mode. If you specify append-hook though you'll be able to append to
- the folder. Note that Mutt 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.
-
- 1.1. Open a compressed mailbox for reading
-
- Usage: open-hook regexp "command" The command is the command that can be
- used for opening the folders whose names match regexp. The command string
- is the printf-like format string, and it should accept two parameters: %f,
- which is replaced with the (compressed) folder name, and %t which is
- replaced with the name of the temporary folder to which to write. %f and
- %t can be repeated any number of times in the command string, and all of
- the entries are replaced with the appropriate folder name. In addition, %%
- is replaced by %, as in printf, and any other %anything is left as is. The
- command should not remove the original compressed file. The command should
- return non-zero exit status if it fails, so mutt knows something's wrong.
- Example:
-
- open-hook \\.gz$ "gzip -cd %f > %t"
-
- If the command is empty, this operation is disabled for this file type.
-
- 1.2. Write a compressed mailbox
-
- Usage: close-hook regexp "command" This is used to close the folder that
- was open with the open-hook command after some changes were made to it.
- The command string is the command that can be used for closing the folders
- whose names match regexp. It has the same format as in the open-hook
- command. Temporary folder in this case is the folder previously produced
- by the open-hook command. The command should not remove the decompressed
- file. The command should return non-zero exit status if it fails, so mutt
- knows something's wrong. Example:
-
- close-hook \\.gz$ "gzip -c %t > %f"
-
- If the command is empty, this operation is disabled for this file type,
- and the file can only be open in the read-only mode. close-hook is not
- called when you exit from the folder if the folder was not changed.
-
- 1.3. Append a message to a compressed mailbox
-
- Usage: append-hook regexp "command" This command is used for saving to an
- existing compressed folder. The command is the command that can be used
- for appending to the folders whose 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 being appended. The command should not
- remove the decompressed file. The command should return non-zero exit
- status if it fails, so mutt knows something's wrong. Example:
-
- append-hook \\.gz$ "gzip -c %t >> %f"
-
- When append-hook is used, the folder is not opened, which saves time, but
- this means that we can not find out what the folder type is. Thus the
- default ($mbox_type) type is always supposed (i.e. this is the format used
- for the temporary folder). If the file does not exist when you save to it,
- close-hook is called, and not append-hook. append-hook is only for
- appending to existing folders. If the command is empty, this operation is
- disabled for this file type. In this case, the folder will be open and
- closed again (using open-hook and close-hookrespectively) each time you
- will add to it.
-
- 1.4. Encrypted folders
-
- The compressed folders support can also be used to handle encrypted
- folders. If you want to encrypt a folder with PGP, you may want to use the
- following hooks:
-
- open-hook \\.pgp$ "pgp -f < %f > %t"
- close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-
- Please note, that PGP does not support appending to an encrypted folder,
- so there is no append-hook defined. If you are using GnuPG instead of PGP,
- you may use the following hooks instead:
-
- open-hook \\.gpg$ "gpg --decrypt < %f > %t"
- close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
-
- Note: the folder is temporary stored decrypted in the /tmp directory,
- where it can be read by your system administrator. So think about the
- security aspects of this.
-
-Chapter 5. Mutt's MIME Support
-
- Table of Contents
-
- 1. Using MIME in Mutt
-
- 1.1. Viewing MIME messages in the pager
-
- 1.2. The Attachment Menu
-
- 1.3. The Compose Menu
-
- 2. MIME Type configuration with mime.types
-
- 3. MIME Viewer configuration with mailcap
-
- 3.1. The Basics of the mailcap file
-
- 3.2. Secure use of mailcap
-
- 3.3. Advanced mailcap Usage
-
- 3.4. Example mailcap files
-
- 4. MIME Autoview
-
- 5. MIME Multipart/Alternative
-
- 6. Attachment Searching and Counting
-
- 7. MIME Lookup
-
- Quite a bit of effort has been made to make Mutt 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 for MIME, there are two extra
- types of configuration files which Mutt uses. One is the mime.types file,
- which contains the mapping of file extensions to IANA MIME types. The
- other is the mailcap file, which specifies the external commands to use
- for handling specific MIME types.
-
-1. Using MIME in Mutt
-
- There are three areas/menus in Mutt which deal with MIME, they are the
- pager (while viewing a message), the attachment menu and the compose menu.
-
- 1.1. Viewing MIME messages in the pager
-
- When you select a message from the index and view it in the pager, Mutt
- decodes the message to a text representation. Mutt 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
- recognizes a variety of PGP MIME types, including PGP/MIME and
- application/pgp.
-
- Mutt will denote attachments with a couple lines describing them. These
- lines are of the form:
-
- [-- Attachment #1: Description --]
- [-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-
- Where the Description is the description or filename given for the
- attachment, and the Encoding is one of
- 7bit/8bit/quoted-printable/base64/binary.
-
- If Mutt cannot deal with a MIME type, it will display a message like:
-
- [-- image/gif is unsupported (use 'v' to view this part) --]
-
- 1.2. The Attachment Menu
-
- The default binding for view-attachments is `v', which displays the
- attachment menu for a message. The attachment menu displays a list of the
- attachments in a message. From the attachment menu, you can save, print,
- pipe, delete, and view attachments. You can apply these operations to a
- group of attachments at once, by tagging the attachments and by using the
- "tag-prefix" operator. You can also reply to the current message from this
- menu, and only the current attachment (or the attachments tagged) will be
- quoted in your reply. You can view attachments as text, or view them using
- the mailcap viewer definition.
-
- Finally, you can apply the usual message-related functions (like
- <resend-message>, and the <reply> and <forward> functions) to attachments
- of type message/rfc822.
-
- See the help on the attachment menu for more information.
-
- 1.3. The Compose Menu
-
- The compose menu is the menu you see before you send a message. It allows
- you to edit the recipient list, the subject, and other aspects of your
- message. It also contains a list of the attachments of your message,
- including the main body. From this menu, you can print, copy, filter,
- pipe, edit, compose, review, and rename an attachment or a list of tagged
- attachments. You can also modifying the attachment information, notably
- the type, encoding and description.
-
- Attachments appear as follows:
-
- - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description>
- 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description>
-
- The '-' denotes that Mutt will delete the file after sending (or
- postponing, or canceling) the message. It can be toggled with the
- toggle-unlink command (default: u). The next field is the MIME
- content-type, and can be changed with the edit-type command (default: ^T).
- The next field is the encoding for the attachment, which allows a binary
- message to be encoded for transmission on 7bit links. It can be changed
- with the edit-encoding command (default: ^E). The next field is the size
- of the attachment, rounded to kilobytes or megabytes. The next field is
- the filename, which can be changed with the rename-file command (default:
- R). The final field is the description of the attachment, and can be
- changed with the edit-description command (default: d).
-
-2. MIME Type configuration with mime.types
-
- When you add an attachment to your mail message, Mutt searches your
- personal mime.types file at ${HOME}/.mime.types, 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 distribution, and should
- contain most of the MIME types you are likely to use.
-
- If Mutt 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 will assume that the file is plain text, and mark it as
- text/plain. If the file contains binary information, then Mutt will mark
- it as application/octet-stream. You can change the MIME type that Mutt
- 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 recognizes all of these if the appropriate entry is
- found in the mime.types file. It also recognizes other major mime types,
- such as the chemical type that is widely used in the molecular modeling
- community to pass molecular data in various forms to various molecular
- viewers. Non-recognized mime types should only be used if the recipient of
- the message is likely to be expecting such attachments.
-
-3. MIME Viewer configuration with mailcap
-
- Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific
- format specified in Appendix A of RFC 1524. This file format is commonly
- referred to as the mailcap format. Many MIME compliant programs utilize
- the mailcap format, allowing you to specify handling for all MIME types in
- one place for all programs. Programs known to use this format include
- Netscape, XMosaic, lynx and metamail.
-
- In order to handle various MIME types that Mutt can not handle internally,
- Mutt parses a series of external configuration files to find an external
- handler. The default search string for these files is a colon delimited
- list containing the following files:
-
- 1. $HOME/.mailcap
-
- 2. $PKGDATADIR/mailcap
-
- 3. $SYSCONFDIR/mailcap
-
- 4. /etc/mailcap
-
- 5. /usr/etc/mailcap
-
- 6. /usr/local/etc/mailcap
-
- where $HOME is your home directory. The $PKGDATADIR and the $SYSCONFDIR
- directories depend on where mutt is installed: the former is the default
- for shared data, the latter for system configuration files.
-
- The default search path can be obtained by running the following command:
-
- mutt -nF /dev/null -Q mailcap_path
-
- In particular, the metamail distribution will install a mailcap file,
- usually as /usr/local/etc/mailcap, which contains some baseline entries.
-
- 3.1. The Basics of the mailcap file
-
- A mailcap file consists of a series of lines which are comments, blank, or
- definitions.
-
- A comment line consists of a # character followed by anything you want.
-
- A blank line is blank.
-
- A definition line consists of a content type, a view command, and any
- number of optional fields. Each field of a definition line is divided by 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 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 will turn over the terminal to the view program
- until the program quits, at which time Mutt will remove the temporary file
- if it exists.
-
- So, in the simplest form, you can send a text/plain message to the
- external pager more on stdin:
-
- text/plain; more
-
- Or, you could send the message as a file:
-
- text/plain; more %s
-
- Perhaps you would like to use lynx to interactively view a text/html
- message:
-
- text/html; lynx %s
-
- In this case, lynx does not support viewing a file from stdin, so you must
- use the %s syntax.
-
- Note
-
- Some older versions of lynx contain a bug where they will check the
- mailcap file for a viewer for text/html. They will find the line which
- calls lynx, and run it. This causes lynx to continuously spawn itself to
- view the object.
-
- On the other hand, maybe you don't want to use lynx interactively, you
- just want to have it convert the text/html to text/plain, then you can
- use:
-
- text/html; lynx -dump %s | more
-
- Perhaps you wish to use lynx to view text/html files, and a pager on all
- other text formats, then you would use the following:
-
- text/html; lynx %s
- text/*; more
-
- This is the simplest form of a mailcap file.
-
- 3.2. Secure use of mailcap
-
- The interpretation of shell meta-characters embedded in MIME parameters
- can lead to security problems in general. Mutt tries to quote parameters
- in expansion of %s syntaxes properly, and avoids risky characters by
- substituting them, see the $mailcap_sanitize variable.
-
- Although mutt's procedures to invoke programs with mailcap seem to be
- safe, there are other applications parsing mailcap, maybe taking less care
- of it. Therefore you should pay attention to the following rules:
-
- Keep the %-expandos away from shell quoting. Don't quote them with single
- or double quotes. Mutt 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 behavior with quotes introduces new
- leaks - there is no alternative to correct quoting in the first place.
-
- If you have to use the %-expandos' values in context where you need
- quoting or backtick expansions, put that value into a shell variable and
- reference the shell variable where necessary, as in the following example
- (using $charset inside the backtick expansion is safe, since it is not
- itself subject to any further expansion):
-
- text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-
- 3.3. Advanced mailcap Usage
-
- 3.3.1. Optional Fields
-
- In addition to the required content-type and view command fields, you can
- add semi-colon ';' separated fields to set flags and other options. Mutt
- recognizes the following optional fields:
-
- copiousoutput
-
- This flag tells Mutt that the command passes possibly large
- amounts of text on stdout. This causes Mutt 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 assumes that the command is interactive. One could use
- this to replace the pipe to more in the lynx -dump example in the
- Basic section:
-
- text/html; lynx -dump %s ; copiousoutput
-
- This will cause lynx to format the text/html output as text/plain
- and Mutt will use your standard pager to display the results.
-
- needsterminal
-
- Mutt 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 will use $wait_key and the exit status of
- the program to decide if it will ask you to press a key after the
- external program has exited. In all other situations it will not
- prompt you for a key.
-
- compose=<command>
-
- This flag specifies the command to use to create a new attachment
- of a specific MIME type. Mutt supports this from the compose menu.
-
- composetyped=<command>
-
- This flag specifies the command to use to create a new attachment
- of a specific MIME type. This command differs from the compose
- command in that mutt will expect standard MIME headers on the
- data. This can be used to specify parameters, filename,
- description, etc. for a new attachment. Mutt supports this from
- the compose menu.
-
- print=<command>
-
- This flag specifies the command to use to print a specific MIME
- type. Mutt supports this from the attachment and compose menus.
-
- edit=<command>
-
- This flag specifies the command to use to edit a specific MIME
- type. Mutt supports this from the compose menu, and also uses it
- to compose new attachments. Mutt will default to the defined
- editor for text attachments.
-
- nametemplate=<template>
-
- This field specifies the format for the file denoted by %s in the
- command fields. Certain programs will require a certain file
- extension, for instance, to correctly view a file. For instance,
- lynx will only interpret a file as text/html if the file ends in
- .html. So, you would specify lynx as a text/html viewer with a
- line in the mailcap file like:
-
- text/html; lynx %s; nametemplate=%s.html
-
- test=<command>
-
- This field specifies a command to run to test whether this mailcap
- entry should be used. The command is defined with the command
- expansion rules defined in the next section. If the command
- returns 0, then the test passed, and Mutt uses this entry. If the
- command returns non-zero, then the test failed, and Mutt continues
- searching for the right entry. Note that the content-type must
- match before Mutt performs the test. For example:
-
- text/html; netscape -remote 'openURL(%s)' ; test=RunningX
- text/html; lynx %s
-
- In this example, Mutt 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 will call netscape to
- display the text/html object. If RunningX doesn't return 0, then
- Mutt 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 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 will search for an entry with the print command:
-
- image/*; xv %s
- image/gif; ; print= anytopnm %s | pnmtops | lpr; \
- nametemplate=%s.gif
-
- Mutt 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 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 will use the second entry for interactive viewing.
-
- 3.3.3. Command Expansion
-
- The various commands defined in the mailcap files are passed to the
- /bin/sh shell using the system() function. Before the command is passed to
- /bin/sh -c, it is parsed to expand various special parameters with
- information from Mutt. The keywords Mutt expands are:
-
- %s
-
- As seen in the basic mailcap section, this variable is expanded to
- a filename specified by the calling program. This file contains
- the body of the message to view/print/edit or where the composing
- program should place the results of composition. In addition, the
- use of this keyword causes Mutt to not pass the body of the
- message to the view/print/edit program on stdin.
-
- %t
-
- Mutt will expand %t to the text representation of the content type
- of the message in the same form as the first parameter of the
- mailcap definition line, ie text/html or image/gif.
-
- %{<parameter>}
-
- Mutt will expand this to the value of the specified parameter from
- the Content-Type: line of the mail message. For instance, if Your
- mail message contains:
-
- Content-Type: text/plain; charset=iso-8859-1
-
- then Mutt will expand %{charset} to iso-8859-1. The default
- metamail mailcap file uses this feature to test the charset to
- spawn an xterm using the right charset to view the message.
-
- \%
-
- This will be replaced by a %
-
- Mutt 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.
-
- 3.4. Example mailcap files
-
- This mailcap file is fairly simple and standard:
-
- # I'm always running X :)
- video/*; xanim %s > /dev/null
- image/*; xv %s > /dev/null
-
- # I'm always running netscape (if my computer had more memory, maybe)
- text/html; netscape -remote 'openURL(%s)'
-
- This mailcap file shows quite a number of examples:
-
- # Use xanim to view all videos Xanim produces a header on startup,
- # send that to /dev/null so I don't see it
- video/*; xanim %s > /dev/null
-
- # Send html to a running netscape by remote
- text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
-
- # If I'm not running netscape but I am running X, start netscape on the
- # object
- text/html; netscape %s; test=RunningX
-
- # Else use lynx to view it as text
- text/html; lynx %s
-
- # This version would convert the text/html to text/plain
- text/html; lynx -dump %s; copiousoutput
-
- # I use enscript to print text in two columns to a page
- text/*; more %s; print=enscript -2Gr %s
-
- # Netscape adds a flag to tell itself to view jpegs internally
- image/jpeg;xv %s; x-mozilla-flags=internal
-
- # Use xv to view images if I'm running X
- # In addition, this uses the \ to extend the line and set my editor
- # for images
- image/*;xv %s; test=RunningX; \
- edit=xpaint %s
-
- # Convert images to text using the netpbm tools
- image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
- pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
- # Send excel spreadsheets to my NT box
- application/ms-excel; open.pl %s
-
-4. MIME Autoview
-
- In addition to explicitly telling Mutt to view an attachment with the MIME
- viewer defined in the mailcap file, Mutt has support for automatically
- viewing MIME attachments while in the pager.
-
- To work, you must define a viewer in the mailcap file which uses the
- copiousoutput option to denote that it is non-interactive. Usually, you
- also use the entry to convert the attachment to a text representation
- which you can view in the pager.
-
- You then use the auto_view muttrc command to list the content-types that
- you wish to view automatically.
-
- For instance, if you set auto_view to:
-
- auto_view text/html application/x-gunzip \
- application/postscript image/gif application/x-tar-gz
-
- Mutt could use the following mailcap entries to automatically view
- attachments of these types.
-
- text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
- image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | \
- pgmtopbm | pbmtoascii ; copiousoutput
- application/x-gunzip; gzcat; copiousoutput
- application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
- application/postscript; ps2ascii %s; copiousoutput
-
- "unauto_view" can be used to remove previous entries from the autoview
- list. This can be used with message-hook to autoview messages based on
- size, etc. "unauto_view *" will remove all previous entries.
-
-5. MIME Multipart/Alternative
-
- Mutt 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 types is
- preferred. The alternative_order list consists of a number of mimetypes in
- order, including support for implicit and explicit wildcards, for example:
-
- alternative_order text/enriched text/plain text application/postscript image/*
-
- Next, mutt will check if any of the types have a defined auto_view, and
- use that. Failing that, Mutt will look for any text type. As a last
- attempt, mutt will look for any type it knows how to handle.
-
- To remove a MIME type from the alternative_order list, use the
- unalternative_order command.
-
-6. Attachment Searching and Counting
-
- If you ever lose track of attachments in your mailboxes, Mutt's
- attachment-counting and -searching support might be for you. You can make
- your message index display the number of qualifying attachments in each
- message, or search for messages by attachment count. You also can
- configure what kinds of attachments qualify for this feature with the
- attachments and unattachments commands.
-
- In order to provide this information, mutt needs to fully MIME-parse all
- messages affected first. This can slow down operation especially for
- remote mail folders such as IMAP because all messages have to be
- downloaded first regardless whether the user really wants to view them or
- not.
-
- The syntax is:
-
- attachments {+|-}disposition mime-type
- unattachments {+|-}disposition mime-type
- attachments ?
-
- Disposition is the attachment's Content-disposition type -- either inline
- or attachment. You can abbreviate this to I or A.
-
- Disposition is prefixed by either a + symbol or a - symbol. If it's a +,
- you're saying that you want to allow this disposition and MIME type to
- qualify. If it's a -, you're saying that this disposition and MIME type is
- an exception to previous + rules. There are examples below of how this is
- useful.
-
- Mime-type is, unsurprisingly, the MIME type of the attachment you want to
- affect. A MIME type is always of the format major/minor, where major
- describes the broad category of document you're looking at, and minor
- describes the specific type within that category. The major part of
- mime-type must be literal text (or the special token "*"), but the minor
- part may be a regular expression. (Therefore, "*/.*" matches any MIME
- type.)
-
- The MIME types you give to the attachments directive are a kind of
- pattern. When you use the attachments directive, the patterns you specify
- are added to a list. When you use unattachments, the pattern is removed
- from the list. The patterns are not expanded and matched to specific MIME
- types at this time -- they're just text in a list. They're only matched
- when actually evaluating a message.
-
- Some examples might help to illustrate. The examples that are not
- commented out define the default configuration of the lists.
-
- Example 5.1. Attachment counting
-
- ## 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
-
- Entering the command "attachments ?" as a command will list your current
- settings in Muttrc format, so that it can be pasted elsewhere.
-
-7. MIME Lookup
-
- Mutt's mime_lookup list specifies a list of mime-types that should not be
- treated according to their mailcap entry. This option is designed to deal
- with binary types such as application/octet-stream. When an attachment's
- mime-type is listed in mime_lookup, then the extension of the filename
- will be compared to the list of extensions in the mime.types file. The
- mime-type associated with this extension will then be used to process the
- attachment according to the rules in the mailcap file and according to any
- other configuration options (such as auto_view) specified. Common usage
- would be:
-
- mime_lookup application/octet-stream application/X-Lotus-Manuscript
-
- In addition, the unmime_lookup command may be used to disable this feature
- for any particular mime-type if it had been set, for example, in a global
- muttrc.
-
-Chapter 6. Optional features
-
- Table of Contents
-
- 1. General notes
-
- 1.1. Enabling/disabling features
-
- 1.2. URL syntax
-
- 2. SSL/TLS Support
-
- 3. POP3 Support
-
- 4. IMAP Support
-
- 4.1. The Folder Browser
-
- 4.2. Authentication
-
- 5. SMTP Support
-
- 6. Managing multiple accounts
-
- 7. Local caching
-
- 7.1. Header caching
-
- 7.2. Body caching
-
- 7.3. Maintenance
-
- 8. Exact address generation
-
-1. General notes
-
- 1.1. Enabling/disabling features
-
- Mutt supports several of optional features which can be enabled or
- disabled at compile-time by giving the configure script certain arguments.
- These are listed in the "Optional features" section of the configure
- --help output.
-
- Which features are enabled or disabled can later be determined from the
- output of mutt -v. If a compile option starts with "+" it is enabled and
- disabled if prefixed with "-". For example, if mutt was compiled using
- GnuTLS for encrypted communication instead of OpenSSL, mutt -v would
- contain:
-
- -USE_SSL_OPENSSL +USE_SSL_GNUTLS
-
- 1.2. URL syntax
-
- Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
- to access servers using URLs. The canonical syntax for specifying URLs in
- mutt is (an item enclosed in [] means it is optional and may be omitted):
-
- proto[s]://[username[:password]@]server[:port]/[path]
-
- proto is the communication protocol: imap for IMAP, pop for POP3 and smtp
- for SMTP. If "s" for "secure communication" is appended, mutt will attempt
- to establish an encrypted communication using SSL or TLS. If no explicit
- port is given, mutt will use the system's default for the given protocol.
-
- Since all protocols by mutt support authentication, the username may be
- given directly in the URL instead of using the pop_user or imap_user
- variables. It may contain the "@" symbol being used by many mail systems
- as part of the login name. A password can be given, too but is not
- recommended if the URL is specified in a configuration file on disk.
-
- The optional path is only relevant for IMAP.
-
- For IMAP for example, you can select an alternative port by specifying it
- with the server: imap://imapserver:port/INBOX. You can also specify
- different username for each folder:
- imap://username@imapserver[:port]/INBOX or
- imap://username2@imapserver[:port]/path/to/folder. Replacing imap:// by
- imaps:// would make mutt attempt to connect using SSL or TLS on a
- different port to encrypt the communication.
-
-2. SSL/TLS Support
-
- If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
- compiled with support for SSL or TLS using either OpenSSL or GnuTLS ( by
- running the configure script with the --enable-ssl=... option for OpenSSL
- or --enable-gnutls=... for GnuTLS). Mutt can then attempt to encrypt
- communication with remote servers if these protocols are suffixed with "s"
- for "secure communication".
-
-3. POP3 Support
-
- If Mutt 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.
-
- Remote POP3 servers can be accessed using URLs with the pop protocol for
- unencrypted and pops for encrypted communication, see Section 1.2, "URL
- syntax" for details.
-
- Polling for new mail is more expensive over POP3 than locally. For this
- reason the frequency at which Mutt will check for mail remotely can be
- controlled by the $pop_checkinterval variable, which defaults to every 60
- seconds.
-
- 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 runs exactly
- as if the mail had always been local.
-
- Note
-
- If you only need to fetch all messages to a local mailbox you should
- consider using a specialized program, such as fetchmail, getmail or
- similar.
-
-4. IMAP Support
-
- If Mutt was compiled with IMAP support (by running the configure script
- with the --enable-imap flag), it has the ability to work with folders
- located on a remote IMAP server.
-
- You can access the remote inbox by selecting the folder by its URL (see
- Section 1.2, "URL syntax" for details) using the imap or imaps protocol.
- Alternatively, a pine-compatible notation is also supported, ie
- {[username@]imapserver[:port][/ssl]}path/to/folder
-
- Note that not all servers use "/" as the hierarchy separator. Mutt should
- correctly notice which separator is being used by the server and convert
- paths accordingly.
-
- When browsing folders on an IMAP server, you can toggle whether to look at
- only the folders you are subscribed to, or all folders with the
- toggle-subscribed command. See also the $imap_list_subscribed variable.
-
- Polling for new mail on an IMAP server can cause noticeable delays. So,
- you'll want to carefully tune the $mail_check and $timeout variables.
- Personally I use
-
- set mail_check=90
- set timeout=15
-
- with relatively good results over my slow modem line.
-
- Note
-
- Note that if you are using mbox as the mail store on UW servers prior to
- v12.250, the server has been reported to disconnect a client if another
- client selects the same folder.
-
- 4.1. The Folder Browser
-
- As of version 1.2, mutt supports browsing mailboxes on an IMAP server.
- This is mostly the same as the local file browser, with the following
- differences:
-
- o In lieu of file permissions, mutt displays the string "IMAP", possibly
- followed by the symbol "+", indicating that the entry contains both
- messages and subfolders. On Cyrus-like servers folders will often
- contain both messages and subfolders.
-
- o For the case where an entry can contain both messages and subfolders,
- the selection key (bound to enter by default) will choose to descend
- into the subfolder view. If you wish to view the messages in that
- folder, you must use view-file instead (bound to space by default).
-
- o You can create, delete and rename mailboxes with the create-mailbox,
- delete-mailbox, and rename-mailbox commands (default bindings: C, d
- and r, respectively). You may also subscribe and unsubscribe to
- mailboxes (normally these are bound to s and u, respectively).
-
- 4.2. Authentication
-
- Mutt supports four authentication methods with IMAP servers: SASL, GSSAPI,
- CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM
- authentication for you poor exchange users out there, but it has yet to be
- integrated into the main tree). There is also support for the
- pseudo-protocol ANONYMOUS, which allows you to log in to a public IMAP
- server without having an account. To use ANONYMOUS, simply make your
- username blank or "anonymous".
-
- SASL is a special super-authenticator, which selects among several
- protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most
- secure method available on your host and the server. Using some of these
- methods (including DIGEST-MD5 and possibly GSSAPI), your entire session
- will be encrypted and invisible to those teeming network snoops. It is the
- best option if you have it. To use it, you must have the Cyrus SASL
- library installed on your system and compile mutt with the --with-sasl
- flag.
-
- Mutt will try whichever methods are compiled in and available on the
- server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-
- There are a few variables which control authentication:
-
- o $imap_user - controls the username under which you request
- authentication on the IMAP server, for all authenticators. This is
- overridden by an explicit username in the mailbox path (ie by using a
- mailbox name of the form {user@host}).
-
- o $imap_pass - a password which you may preset, used by all
- authentication methods where a password is needed.
-
- o $imap_authenticators - a colon-delimited list of IMAP authentication
- methods to try, in the order you wish to try them. If specified, this
- overrides mutt's default (attempt everything, in the order listed
- above).
-
-5. SMTP Support
-
- Besides supporting traditional mail delivery through a sendmail-compatible
- program, mutt supports delivery through SMTP if it was configured and
- built with --enable-smtp.
-
- If the configuration variable $smtp_url is set, mutt will contact the
- given SMTP server to deliver messages; if it is unset, mutt will use the
- program specified by $sendmail.
-
- For details on the URL syntax, please see Section 1.2, "URL syntax".
-
- The built-in SMTP support supports encryption (the smtps protocol using
- SSL or TLS) as well as SMTP authentication using SASL. The authentication
- mechanisms for SASL are specified in $smtp_authenticators defaulting to an
- empty list which makes mutt try all available methods from most-secure to
- least-secure.
-
-6. Managing multiple accounts
-
- If you happen to have accounts on multiple IMAP, POP and/or SMTP 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 which
- includes (for example) polling for new mail, storing Fcc messages and
- saving messages to a folder. As a consequence, account-hook should only be
- used to set connection-related settings such as passwords or tunnel
- commands but not settings such as sender address or name (because in
- general it should be considered unpredictable which account-hook was last
- used).
-
- Some examples:
-
- account-hook . 'unset imap_user; unset imap_pass; unset tunnel'
- account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
- account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
- account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-
-7. Local caching
-
- Mutt contains two types of local caching: (1) the so-called "header
- caching" and (2) the so-called "body caching" which are both described in
- this section.
-
- Header caching is optional as it depends on external libraries, body
- caching is always enabled if mutt is compiled with POP and/or IMAP support
- as these use it (body caching requires no external library).
-
- 7.1. Header caching
-
- Mutt provides optional support for caching message headers for the
- following types of folders: IMAP, POP, Maildir and MH. Header caching
- greatly improves speed because for remote folders, headers usually only
- need to be downloaded once. For Maildir and MH, reading the headers from a
- single file is much faster than looking at possibly thousands of single
- files (since Maildir and MH use one file per message.)
-
- Header caching can be enabled via the configure script and the
- --enable-hcache option. It's not turned on by default because external
- database libraries are required: one of tokyocabinet, qdbm, gdbm or bdb
- must be present.
-
- If enabled, $header_cache can be used to either point to a file or a
- directory. If set to point to a file, one database file for all folders
- will be used (which may result in lower performance), but one file per
- folder if it points to a directory.
-
- For the one-file-per-folder case, database files for remote folders will
- be named according to their URL while database files for local folders
- will be named by the MD5 checksums of their path. These database files may
- be safely removed if a system is short on space. You can compute the name
- of the header cache file for a particular local folder through a command
- like the following:
-
- $ printf '%s' '/path/to/folder' | md5sum
-
- The md5sum command may also be named md5, depending on your operating
- system.
-
- 7.2. Body caching
-
- Both cache methods can be combined using the same directory for storage
- (and for IMAP/POP even provide meaningful file names) which simplifies
- manual maintenance tasks.
-
- In addition to caching message headers only, mutt can also cache whole
- message bodies. This results in faster display of messages for POP and
- IMAP folders because messages usually have to be downloaded only once.
-
- For configuration, the variable $message_cachedir must point to a
- directory. There, mutt will create a hierarchy of subdirectories named
- like: proto:user@hostname where proto is either "pop" or "imap." Within
- there for each folder, mutt stores messages in single files (just like
- Maildir) so that with manual symlink creation these cache directories can
- be examined with mutt as read-only Maildir folders.
-
- All files can be removed as needed if the consumed disk space becomes an
- issue as mutt will silently fetch missing items again.
-
- 7.3. Maintenance
-
- Mutt does not (yet) support maintenance features for header cache database
- files so that files have to be removed in case they grow too big. It
- depends on the database library used for header caching whether disk space
- freed by removing messages is re-used.
-
- For body caches, mutt can keep the local cache in sync with the remote
- mailbox if the $message_cache_clean variable is set. Cleaning means to
- remove messages from the cache which are no longer present in the mailbox
- which only happens when other mail clients or instances of mutt using a
- different body cache location delete messages (Mutt itself removes deleted
- messages from the cache when syncing a mailbox). As cleaning can take a
- noticeable amount of time, it should not be set in general but only
- occasionally.
-
-8. Exact address generation
-
- Mutt supports the "Name <user@host>" address syntax for reading and
- writing messages, the older "user@host (Name)" syntax is only supported
- when reading messages. The --enable-exact-address switch can be given to
- configure to build it with write-support for the latter syntax.
- EXACT_ADDRESS in the output of mutt -v indicates whether it's supported.
-
-Chapter 7. Performance tuning
-
- Table of Contents
-
- 1. Reading and writing mailboxes
-
- 2. Reading messages from remote folders
-
- 3. Searching and limiting
-
-1. Reading and writing mailboxes
-
- Mutt's performance when reading mailboxes can be improved in two ways:
-
- 1. For remote folders (IMAP and POP) as well as folders using
- one-file-per message storage (Maildir and MH), mutt's performance can
- be greatly improved using header caching. Using a single database per
- folder may further increase performance.
-
- 2. Mutt provides the $read_inc and $write_inc variables to specify at
- which rate to update progress counters. If these values are too low,
- mutt may spend more time on updating the progress counter than it
- spends on actually reading/writing folders.
-
- For example, when opening a maildir folder with a few thousand
- messages, the default value for $read_inc may be too low. It can be
- tuned on on a folder-basis using folder-hooks:
-
- # use very high $read_inc to speed up reading hcache'd maildirs
- folder-hook . 'set read_inc=1000'
- # use lower value for reading slower remote IMAP folders
- folder-hook ^imap 'set read_inc=100'
- # use even lower value for reading even slower remote POP folders
- folder-hook ^pop 'set read_inc=1'
-
- These settings work on a per-message basis. However, as messages may
- greatly differ in size and certain operations are much faster than others,
- even per-folder settings of the increment variables may not be desirable
- as they produce either too few or too much progress updates. Thus, Mutt
- allows to limit the number of progress updates per second it'll actually
- send to the terminal using the $time_inc variable.
-
-2. Reading messages from remote folders
-
- Reading messages from remote folders such as IMAP an POP can be slow
- especially for large mailboxes since mutt only caches a very limited
- number of recently viewed messages (usually 10) per session (so that it
- will be gone for the next session.)
-
- To improve performance and permanently cache whole messages, please refer
- to mutt's so-called body caching for details.
-
-3. Searching and limiting
-
- When searching mailboxes either via a search or a limit action, for some
- patterns mutt distinguishes between regular expression and string
- searches. For regular expressions, patterns are prefixed with "~" and with
- "=" for string searches.
-
- Even though a regular expression search is fast, it's several times slower
- than a pure string search which is noticeable especially on large folders.
- As a consequence, a string search should be used instead of a regular
- expression search if the user already knows enough about the search
- pattern.
-
- For example, when limiting a large folder to all messages sent to or by an
- author, it's much faster to search for the initial part of an e-mail
- address via =Luser@ instead of ~Luser@. This is especially true for
- searching message bodies since a larger amount of input has to be
- searched.
-
- Please note that string search is an exact case-sensitive search while a
- regular expression search with only lower-case letters performs a
- case-insensitive search.
-
-Chapter 8. Reference
-
- Table of Contents
-
- 1. Command line options
-
- 2. Configuration Commands
-
- 3. Configuration variables
-
- 3.1. abort_nosubject
-
- 3.2. abort_unmodified
-
- 3.3. alias_file
-
- 3.4. alias_format
-
- 3.5. allow_8bit
-
- 3.6. allow_ansi
-
- 3.7. arrow_cursor
-
- 3.8. ascii_chars
-
- 3.9. askbcc
-
- 3.10. askcc
-
- 3.11. assumed_charset
-
- 3.12. attach_charset
-
- 3.13. attach_format
-
- 3.14. attach_sep
-
- 3.15. attach_split
-
- 3.16. attribution
-
- 3.17. autoedit
-
- 3.18. auto_tag
-
- 3.19. beep
-
- 3.20. beep_new
-
- 3.21. bounce
-
- 3.22. bounce_delivered
-
- 3.23. braille_friendly
-
- 3.24. check_mbox_size
-
- 3.25. charset
-
- 3.26. check_new
-
- 3.27. collapse_unread
-
- 3.28. uncollapse_jump
-
- 3.29. compose_format
-
- 3.30. config_charset
-
- 3.31. confirmappend
-
- 3.32. confirmcreate
-
- 3.33. connect_timeout
-
- 3.34. content_type
-
- 3.35. copy
-
- 3.36. crypt_use_gpgme
-
- 3.37. crypt_use_pka
-
- 3.38. crypt_autopgp
-
- 3.39. crypt_autosmime
-
- 3.40. date_format
-
- 3.41. default_hook
-
- 3.42. delete
-
- 3.43. delete_untag
-
- 3.44. digest_collapse
-
- 3.45. display_filter
-
- 3.46. dotlock_program
-
- 3.47. dsn_notify
-
- 3.48. dsn_return
-
- 3.49. duplicate_threads
-
- 3.50. edit_headers
-
- 3.51. editor
-
- 3.52. encode_from
-
- 3.53. envelope_from_address
-
- 3.54. escape
-
- 3.55. fast_reply
-
- 3.56. fcc_attach
-
- 3.57. fcc_clear
-
- 3.58. folder
-
- 3.59. folder_format
-
- 3.60. followup_to
-
- 3.61. force_name
-
- 3.62. forward_decode
-
- 3.63. forward_edit
-
- 3.64. forward_format
-
- 3.65. forward_quote
-
- 3.66. from
-
- 3.67. gecos_mask
-
- 3.68. hdrs
-
- 3.69. header
-
- 3.70. help
-
- 3.71. hidden_host
-
- 3.72. hide_limited
-
- 3.73. hide_missing
-
- 3.74. hide_thread_subject
-
- 3.75. hide_top_limited
-
- 3.76. hide_top_missing
-
- 3.77. history
-
- 3.78. history_file
-
- 3.79. honor_followup_to
-
- 3.80. hostname
-
- 3.81. ignore_linear_white_space
-
- 3.82. ignore_list_reply_to
-
- 3.83. imap_authenticators
-
- 3.84. imap_check_subscribed
-
- 3.85. imap_delim_chars
-
- 3.86. imap_headers
-
- 3.87. imap_idle
-
- 3.88. imap_keepalive
-
- 3.89. imap_list_subscribed
-
- 3.90. imap_login
-
- 3.91. imap_pass
-
- 3.92. imap_passive
-
- 3.93. imap_peek
-
- 3.94. imap_pipeline_depth
-
- 3.95. imap_servernoise
-
- 3.96. imap_user
-
- 3.97. implicit_autoview
-
- 3.98. include
-
- 3.99. include_onlyfirst
-
- 3.100. indent_string
-
- 3.101. index_format
-
- 3.102. ispell
-
- 3.103. keep_flagged
-
- 3.104. locale
-
- 3.105. mail_check
-
- 3.106. mailcap_path
-
- 3.107. mailcap_sanitize
-
- 3.108. maildir_mtime
-
- 3.109. header_cache
-
- 3.110. maildir_header_cache_verify
-
- 3.111. header_cache_pagesize
-
- 3.112. maildir_trash
-
- 3.113. mark_old
-
- 3.114. markers
-
- 3.115. mask
-
- 3.116. mbox
-
- 3.117. mbox_type
-
- 3.118. metoo
-
- 3.119. menu_context
-
- 3.120. menu_move_off
-
- 3.121. menu_scroll
-
- 3.122. meta_key
-
- 3.123. mh_purge
-
- 3.124. mh_seq_flagged
-
- 3.125. mh_seq_replied
-
- 3.126. mh_seq_unseen
-
- 3.127. mime_forward
-
- 3.128. mime_forward_decode
-
- 3.129. mime_forward_rest
-
- 3.130. mix_entry_format
-
- 3.131. mixmaster
-
- 3.132. move
-
- 3.133. message_cachedir
-
- 3.134. message_cache_clean
-
- 3.135. message_format
-
- 3.136. narrow_tree
-
- 3.137. net_inc
-
- 3.138. pager
-
- 3.139. pager_context
-
- 3.140. pager_format
-
- 3.141. pager_index_lines
-
- 3.142. pager_stop
-
- 3.143. crypt_autosign
-
- 3.144. crypt_autoencrypt
-
- 3.145. pgp_ignore_subkeys
-
- 3.146. crypt_replyencrypt
-
- 3.147. crypt_replysign
-
- 3.148. crypt_replysignencrypted
-
- 3.149. crypt_timestamp
-
- 3.150. pgp_use_gpg_agent
-
- 3.151. crypt_verify_sig
-
- 3.152. smime_is_default
-
- 3.153. smime_ask_cert_label
-
- 3.154. smime_decrypt_use_default_key
-
- 3.155. pgp_entry_format
-
- 3.156. pgp_good_sign
-
- 3.157. pgp_check_exit
-
- 3.158. pgp_long_ids
-
- 3.159. pgp_retainable_sigs
-
- 3.160. pgp_autoinline
-
- 3.161. pgp_replyinline
-
- 3.162. pgp_show_unusable
-
- 3.163. pgp_sign_as
-
- 3.164. pgp_strict_enc
-
- 3.165. pgp_timeout
-
- 3.166. pgp_sort_keys
-
- 3.167. pgp_mime_auto
-
- 3.168. pgp_auto_decode
-
- 3.169. pgp_mime_signature_filename
-
- 3.170. pgp_mime_signature_description
-
- 3.171. pgp_decode_command
-
- 3.172. pgp_getkeys_command
-
- 3.173. pgp_verify_command
-
- 3.174. pgp_decrypt_command
-
- 3.175. pgp_clearsign_command
-
- 3.176. pgp_sign_command
-
- 3.177. pgp_encrypt_sign_command
-
- 3.178. pgp_encrypt_only_command
-
- 3.179. pgp_import_command
-
- 3.180. pgp_export_command
-
- 3.181. pgp_verify_key_command
-
- 3.182. pgp_list_secring_command
-
- 3.183. pgp_list_pubring_command
-
- 3.184. forward_decrypt
-
- 3.185. smime_timeout
-
- 3.186. smime_encrypt_with
-
- 3.187. smime_keys
-
- 3.188. smime_ca_location
-
- 3.189. smime_certificates
-
- 3.190. smime_decrypt_command
-
- 3.191. smime_verify_command
-
- 3.192. smime_verify_opaque_command
-
- 3.193. smime_sign_command
-
- 3.194. smime_sign_opaque_command
-
- 3.195. smime_encrypt_command
-
- 3.196. smime_pk7out_command
-
- 3.197. smime_get_cert_command
-
- 3.198. smime_get_signer_cert_command
-
- 3.199. smime_import_cert_command
-
- 3.200. smime_get_cert_email_command
-
- 3.201. smime_default_key
-
- 3.202. ssl_client_cert
-
- 3.203. ssl_force_tls
-
- 3.204. ssl_starttls
-
- 3.205. certificate_file
-
- 3.206. ssl_use_sslv3
-
- 3.207. ssl_use_tlsv1
-
- 3.208. ssl_min_dh_prime_bits
-
- 3.209. ssl_ca_certificates_file
-
- 3.210. pipe_split
-
- 3.211. pipe_decode
-
- 3.212. pipe_sep
-
- 3.213. pop_authenticators
-
- 3.214. pop_auth_try_all
-
- 3.215. pop_checkinterval
-
- 3.216. pop_delete
-
- 3.217. pop_host
-
- 3.218. pop_last
-
- 3.219. pop_reconnect
-
- 3.220. pop_user
-
- 3.221. pop_pass
-
- 3.222. post_indent_string
-
- 3.223. postpone
-
- 3.224. postponed
-
- 3.225. preconnect
-
- 3.226. print
-
- 3.227. print_command
-
- 3.228. print_decode
-
- 3.229. print_split
-
- 3.230. prompt_after
-
- 3.231. query_command
-
- 3.232. query_format
-
- 3.233. quit
-
- 3.234. quote_regexp
-
- 3.235. read_inc
-
- 3.236. read_only
-
- 3.237. realname
-
- 3.238. recall
-
- 3.239. record
-
- 3.240. reply_regexp
-
- 3.241. reply_self
-
- 3.242. reply_to
-
- 3.243. resolve
-
- 3.244. reverse_alias
-
- 3.245. reverse_name
-
- 3.246. reverse_realname
-
- 3.247. rfc2047_parameters
-
- 3.248. save_address
-
- 3.249. save_empty
-
- 3.250. save_history
-
- 3.251. save_name
-
- 3.252. score
-
- 3.253. score_threshold_delete
-
- 3.254. score_threshold_flag
-
- 3.255. score_threshold_read
-
- 3.256. send_charset
-
- 3.257. sendmail
-
- 3.258. sendmail_wait
-
- 3.259. shell
-
- 3.260. sig_dashes
-
- 3.261. sig_on_top
-
- 3.262. signature
-
- 3.263. simple_search
-
- 3.264. smart_wrap
-
- 3.265. smileys
-
- 3.266. sleep_time
-
- 3.267. smtp_authenticators
-
- 3.268. smtp_pass
-
- 3.269. smtp_url
-
- 3.270. sort
-
- 3.271. sort_alias
-
- 3.272. sort_aux
-
- 3.273. sort_browser
-
- 3.274. sort_re
-
- 3.275. spam_separator
-
- 3.276. spoolfile
-
- 3.277. status_chars
-
- 3.278. status_format
-
- 3.279. status_on_top
-
- 3.280. strict_threads
-
- 3.281. suspend
-
- 3.282. text_flowed
-
- 3.283. thread_received
-
- 3.284. thorough_search
-
- 3.285. tilde
-
- 3.286. time_inc
-
- 3.287. timeout
-
- 3.288. tmpdir
-
- 3.289. to_chars
-
- 3.290. trash
-
- 3.291. tunnel
-
- 3.292. use_8bitmime
-
- 3.293. use_domain
-
- 3.294. use_envelope_from
-
- 3.295. use_from
-
- 3.296. use_idn
-
- 3.297. use_ipv6
-
- 3.298. user_agent
-
- 3.299. visual
-
- 3.300. wait_key
-
- 3.301. weed
-
- 3.302. wrap
-
- 3.303. wrap_search
-
- 3.304. wrapmargin
-
- 3.305. write_inc
-
- 3.306. write_bcc
-
- 3.307. xterm_icon
-
- 3.308. xterm_set_titles
-
- 3.309. xterm_title
-
- 4. Functions
-
- 4.1. generic menu
-
- 4.2. index menu
-
- 4.3. pager menu
-
- 4.4. alias menu
-
- 4.5. query menu
-
- 4.6. attach menu
-
- 4.7. compose menu
-
- 4.8. postpone menu
-
- 4.9. browser menu
-
- 4.10. pgp menu
-
- 4.11. smime menu
-
- 4.12. mix menu
-
- 4.13. editor menu
-
-1. Command line options
-
- Running mutt with no arguments will make Mutt attempt to read your spool
- mailbox. However, it is possible to read other mailboxes and to send
- messages from the command line as well.
-
- Table 8.1. Command line options
-
- +------------------------------------------------------------------------+
- | Option | Description |
- |--------+---------------------------------------------------------------|
- | -A | expand an alias |
- |--------+---------------------------------------------------------------|
- | -a | attach a file to a message |
- |--------+---------------------------------------------------------------|
- | -b | specify a blind carbon-copy (BCC) address |
- |--------+---------------------------------------------------------------|
- | -c | specify a carbon-copy (Cc) address |
- |--------+---------------------------------------------------------------|
- | -D | print the value of all mutt variables to stdout |
- |--------+---------------------------------------------------------------|
- | -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 Muttrc |
- |--------+---------------------------------------------------------------|
- | -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) |
- |--------+---------------------------------------------------------------|
- | -v | show version number and compile-time definitions |
- |--------+---------------------------------------------------------------|
- | -x | simulate the mailx(1) compose mode |
- |--------+---------------------------------------------------------------|
- | -y | show a menu containing the files specified by the mailboxes |
- | | command |
- |--------+---------------------------------------------------------------|
- | -z | exit immediately if there are no messages in the mailbox |
- |--------+---------------------------------------------------------------|
- | -Z | open the first folder with new message,exit immediately if |
- | | none |
- +------------------------------------------------------------------------+
-
- To read messages in a mailbox
-
- mutt [-nz] [-F muttrc ] [-m type ] [-f mailbox ]
-
- To compose a new message
-
- mutt [-n] [-F muttrc ] [-c address ] [-i filename ] [-s subject ] [ -a
- file [...] -- ] address ...
-
- Mutt also supports a "batch" mode to send prepared messages. Simply
- redirect input from the file you wish to send. For example,
-
- mutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat
-
- This command will send a message to "professor@bigschool.edu" with a
- subject of "data set for run #2". In the body of the message will be the
- contents of the file "~/run2.dat".
-
- All files passed with -a file will be attached as a MIME part to the
- message. To attach several files, use "--" to separate files and recipient
- addresses: mutt -a *.png -- some@one.org
-
-2. Configuration Commands
-
- The following are the commands understood by mutt.
-
- o account-hook pattern command
-
- o alias [ -group name ...] key address [ address ...]
-
- o unalias [ -group name ...] { * | key ... }
-
- o alternates [ -group name ...] regexp [ regexp ...]
-
- o unalternates [ -group name ...] { * | regexp ... }
-
- o alternative-order mimetype [ mimetype ...]
-
- o unalternative-order { * | mimetype ... }
-
- o auto-view mimetype [ mimetype ...]
-
- o unauto-view { * | mimetype ... }
-
- o bind map key function
-
- o charset-hook alias charset
-
- o iconv-hook charset local-charset
-
- o color object foreground background
-
- color { header | body } foreground background regexp
-
- color index foreground background pattern
-
- o uncolor index pattern ...
-
- o exec function [ function ...]
-
- o fcc-hook [!]pattern mailbox
-
- o fcc-save-hook [!]pattern mailbox
-
- o folder-hook [!]regexp command
-
- o group [ -group name ...] { -rx expr ... | -addr expr ... }
-
- o ungroup [ -group name ...] { * | -rx expr ... | -addr expr ... }
-
- o hdr_order header [ header ...]
-
- o unhdr_order { * | header ... }
-
- o ignore pattern [ pattern ...]
-
- o unignore { * | pattern ... }
-
- o lists [ -group name ] regexp [ regexp ...]
-
- o unlists [ -group name ...] { * | regexp ... }
-
- o macro menu key sequence [ description ]
-
- o mailboxes mailbox [ mailbox ...]
-
- o unmailboxes { * | mailbox ... }
-
- o mbox-hook [!]pattern mailbox
-
- o message-hook [!]pattern command
-
- o mime-lookup mimetype [ mimetype ...]
-
- o unmime-lookup { * | mimetype ... }
-
- o mono object attribute
-
- mono { header | body } attribute regexp
-
- mono index attribute pattern
-
- o unmono index { * | pattern ... }
-
- o my_hdr string
-
- o unmy_hdr { * | field ... }
-
- o crypt-hook pattern keyid
-
- o push string
-
- o reset variable [ variable ...]
-
- o save-hook [!]pattern mailbox
-
- o score pattern value
-
- o unscore { * | pattern ... }
-
- o reply-hook [!]pattern command
-
- o send-hook [!]pattern command
-
- o send2-hook [!]pattern command
-
- o set { [ no | inv ] variable | variable=value } [...]
-
- o unset variable [ variable ...]
-
- o source filename
-
- o spam pattern format
-
- o nospam { * | pattern }
-
- o subscribe [ -group name ...] regexp [ regexp ...]
-
- o unsubscribe [ -group name ...] { * | regexp ... }
-
- o toggle variable [ variable ...]
-
- o unhook { * | hook-type }
-
-3. Configuration variables
-
- 3.1. abort_nosubject
-
- Type: quadoption
- Default: ask-yes
-
- If set to yes, when composing messages and no subject is given at the
- subject prompt, composition will be aborted. If set to no, composing
- messages with no subject given at the subject prompt will never be
- aborted.
-
- 3.2. abort_unmodified
-
- Type: quadoption
- Default: yes
-
- If set to yes, composition will automatically abort after editing the
- message body if no changes are made to the file (this check only happens
- after the first edit of the file). When set to no, composition will never
- be aborted.
-
- 3.3. alias_file
-
- Type: path
- Default: "~/.muttrc"
-
- The default file in which to save aliases created by the <create-alias>
- function. Entries added to this file are encoded in the character set
- specified by $config_charset if it is set or the current character set
- otherwise.
-
- Note: Mutt will not automatically source this file; you must explicitly
- use the "source" command for it to be executed in case this option points
- to a dedicated alias file.
-
- The default for this option is the currently used muttrc file, or
- "~/.muttrc" if no user muttrc was found.
-
- 3.4. alias_format
-
- Type: string
- Default: "%4n %2f %t %-10a %r"
-
- Specifies the format of the data displayed for the "alias" menu. The
- following printf(3)-style sequences are available:
-
- %a
-
- alias name
-
- %f
-
- flags - currently, a "d" for an alias marked for deletion
-
- %n
-
- index number
-
- %r
-
- address which alias expands to
-
- %t
-
- character which indicates if the alias is tagged for inclusion
-
- 3.5. allow_8bit
-
- Type: boolean
- Default: yes
-
- Controls whether 8-bit data is converted to 7-bit using either Quoted-
- Printable or Base64 encoding when sending mail.
-
- 3.6. allow_ansi
-
- Type: boolean
- Default: no
-
- Controls whether ANSI color codes in messages (and color tags in rich text
- messages) are to be interpreted. Messages containing these codes are rare,
- but if this option is set, their text will be colored accordingly. Note
- that this may override your color choices, and even present a security
- problem, since a message could include a line like
-
- [-- PGP output follows ...
-
-
- and give it the same color as your attachment color (see also
- $crypt_timestamp).
-
- 3.7. arrow_cursor
-
- Type: boolean
- Default: no
-
- When set, an arrow ("->") will be used to indicate the current entry in
- menus instead of highlighting the whole line. On slow network or modem
- links this will make response faster because there is less that has to be
- redrawn on the screen when moving to the next or previous entries in the
- menu.
-
- 3.8. ascii_chars
-
- Type: boolean
- Default: no
-
- If set, Mutt will use plain ASCII characters when displaying thread and
- attachment trees, instead of the default ACS characters.
-
- 3.9. askbcc
-
- Type: boolean
- Default: no
-
- If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before
- editing an outgoing message.
-
- 3.10. askcc
-
- Type: boolean
- Default: no
-
- If set, Mutt will prompt you for carbon-copy (Cc) recipients before
- editing the body of an outgoing message.
-
- 3.11. assumed_charset
-
- Type: string
- Default: (empty)
-
- This variable is a colon-separated list of character encoding schemes for
- messages without character encoding indication. Header field values and
- message body content without character encoding indication would be
- assumed that they are written in one of this list. By default, all the
- header fields and message body without any charset indication are assumed
- to be in "us-ascii".
-
- For example, Japanese users might prefer this:
-
- set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-
- However, only the first content is valid for the message body.
-
- 3.12. attach_charset
-
- Type: string
- Default: (empty)
-
- This variable is a colon-separated list of character encoding schemes for
- text file attachments. Mutt uses this setting to guess which encoding
- files being attached are encoded in to convert them to a proper character
- set given in $send_charset.
-
- If unset, the value of $charset will be used instead. For example, the
- following configuration would work for Japanese text handling:
-
- set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-
- Note: for Japanese users, "iso-2022-*" must be put at the head of the
- value as shown above if included.
-
- 3.13. attach_format
-
- Type: string
- Default: "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "
-
- This variable describes the format of the "attachment" menu. The following
- printf(3)-style sequences are understood:
-
- %C
-
- charset
-
- %c
-
- requires charset conversion ("n" or "c")
-
- %D
-
- deleted flag
-
- %d
-
- description
-
- %e
-
- MIME content-transfer-encoding
-
- %f
-
- filename
-
- %I
-
- disposition ("I" for inline, "A" for attachment)
-
- %m
-
- major MIME type
-
- %M
-
- MIME subtype
-
- %n
-
- attachment number
-
- %Q
-
- "Q", if MIME part qualifies for attachment counting
-
- %s
-
- size
-
- %t
-
- tagged flag
-
- %T
-
- graphic tree characters
-
- %u
-
- unlink (=to delete) flag
-
- %X
-
- number of qualifying MIME parts in this part and its children
- (please see the "attachments" section for possible speed effects)
-
- %>X
-
- right justify the rest of the string and pad with character "X"
-
- %|X
-
- pad to the end of the line with character "X"
-
- %*X
-
- soft-fill with character "X" as pad
-
- For an explanation of "soft-fill", see the $index_format documentation.
-
- 3.14. attach_sep
-
- Type: string
- Default: "\n"
-
- The separator to add between attachments when operating (saving, printing,
- piping, etc) on a list of tagged attachments.
-
- 3.15. attach_split
-
- Type: boolean
- Default: yes
-
- If this variable is unset, when operating (saving, printing, piping, etc)
- on a list of tagged attachments, Mutt 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 will operate on the
- attachments one by one.
-
- 3.16. attribution
-
- Type: string
- Default: "On %d, %n wrote:"
-
- This is the string that will precede a message which has been included in
- a reply. For a full listing of defined printf(3)-like sequences see the
- section on $index_format.
-
- 3.17. autoedit
-
- Type: boolean
- Default: no
-
- When set along with $edit_headers, Mutt will skip the initial send-menu
- (prompting for subject and recipients) and allow you to immediately begin
- editing the body of your message. The send-menu may still be accessed once
- you have finished editing the body of your message.
-
- Also see $fast_reply.
-
- 3.18. auto_tag
-
- Type: boolean
- Default: no
-
- When set, functions in the index menu which affect a message will be
- applied to all tagged messages (if there are any). When unset, you must
- first use the <tag-prefix> function (bound to ";" by default) to make the
- next function apply to all tagged messages.
-
- 3.19. beep
-
- Type: boolean
- Default: yes
-
- When this variable is set, mutt will beep when an error occurs.
-
- 3.20. beep_new
-
- Type: boolean
- Default: no
-
- When this variable is set, mutt will beep whenever it prints a message
- notifying you of new mail. This is independent of the setting of the $beep
- variable.
-
- 3.21. bounce
-
- Type: quadoption
- Default: ask-yes
-
- Controls whether you will be asked to confirm bouncing messages. If set to
- yes you don't get asked if you want to bounce a message. Setting this
- variable to no is not generally useful, and thus not recommended, because
- you are unable to bounce messages.
-
- 3.22. bounce_delivered
-
- Type: boolean
- Default: yes
-
- When this variable is set, mutt will include Delivered-To headers when
- bouncing messages. Postfix users may wish to unset this variable.
-
- Note: On Debian systems, this option is unset by default in /etc/Muttrc.
-
- 3.23. braille_friendly
-
- Type: boolean
- Default: no
-
- When this variable is set, mutt will place the cursor at the beginning of
- the current line in menus, even when the $arrow_cursor variable is unset,
- making it easier for blind persons using Braille displays to follow these
- menus. The option is unset by default because many visual terminals don't
- permit making the cursor invisible.
-
- 3.24. check_mbox_size
-
- Type: boolean
- Default: no
-
- When this variable is set, mutt will use file size attribute instead of
- access time when checking for new mail in mbox and mmdf folders.
-
- This variable is unset by default and should only be enabled when new mail
- detection for these folder types is unreliable or doesn't work.
-
- Note that enabling this variable should happen before any "mailboxes"
- directives occur in configuration files regarding mbox or mmdf folders
- because mutt needs to determine the initial new mail status of such a
- mailbox by performing a fast mailbox scan when it is defined. Afterwards
- the new mail status is tracked by file size changes.
-
- 3.25. charset
-
- Type: string
- Default: (empty)
-
- Character set your terminal uses to display and enter textual data. It is
- also the fallback for $send_charset.
-
- Upon startup Mutt tries to derive this value from environment variables
- such as $LC_CTYPE or $LANG.
-
- Note: It should only be set in case Mutt isn't abled to determine the
- character set used correctly.
-
- 3.26. check_new
-
- Type: boolean
- Default: yes
-
- Note: this option only affects maildir and MH style mailboxes.
-
- When set, Mutt 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 this variable is unset, no check
- for new mail is performed while the mailbox is open.
-
- 3.27. collapse_unread
-
- Type: boolean
- Default: yes
-
- When unset, Mutt will not collapse a thread if it contains any unread
- messages.
-
- 3.28. uncollapse_jump
-
- Type: boolean
- Default: no
-
- When set, Mutt will jump to the next unread message, if any, when the
- current thread is uncollapsed.
-
- 3.29. compose_format
-
- Type: string
- Default: "-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-"
-
- Controls the format of the status line displayed in the "compose" menu.
- This string is similar to $status_format, but has its own set of
- printf(3)-like sequences:
-
- %a
-
- total number of attachments
-
- %h
-
- local hostname
-
- %l
-
- approximate size (in bytes) of the current message
-
- %v
-
- Mutt version string
-
- See the text describing the $status_format option for more information on
- how to set $compose_format.
-
- 3.30. config_charset
-
- Type: string
- Default: (empty)
-
- When defined, Mutt will recode commands in rc files from this encoding to
- the current character set as specified by $charset and aliases written to
- $alias_file from the current character set.
-
- Please note that if setting $charset it must be done before setting
- $config_charset.
-
- Recoding should be avoided as it may render unconvertable characters as
- question marks which can lead to undesired side effects (for example in
- regular expressions).
-
- 3.31. confirmappend
-
- Type: boolean
- Default: yes
-
- When set, Mutt will prompt for confirmation when appending messages to an
- existing mailbox.
-
- 3.32. confirmcreate
-
- Type: boolean
- Default: yes
-
- When set, Mutt will prompt for confirmation when saving messages to a
- mailbox which does not yet exist before creating it.
-
- 3.33. connect_timeout
-
- Type: number
- Default: 30
-
- Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after
- this many seconds if the connection is not able to be established. A
- negative value causes Mutt to wait indefinitely for the connection attempt
- to succeed.
-
- 3.34. content_type
-
- Type: string
- Default: "text/plain"
-
- Sets the default Content-Type for the body of newly composed messages.
-
- 3.35. copy
-
- Type: quadoption
- Default: yes
-
- 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".
-
- 3.36. crypt_use_gpgme
-
- Type: boolean
- Default: no
-
- This variable controls the use of the GPGME-enabled crypto backends. If it
- is set and Mutt was built with gpgme support, the gpgme code for S/MIME
- and PGP will be used instead of the classic code. Note that you need to
- set this option in .muttrc; it won't have any effect when used
- interactively.
-
- 3.37. crypt_use_pka
-
- Type: boolean
- Default: no
-
- Controls whether mutt uses PKA (see
- http://www.g10code.de/docs/pka-intro.de.pdf) during signature verification
- (only supported by the GPGME backend).
-
- 3.38. crypt_autopgp
-
- Type: boolean
- Default: yes
-
- This variable controls whether or not mutt may automatically enable PGP
- encryption/signing for messages. See also $crypt_autoencrypt,
- $crypt_replyencrypt, $crypt_autosign, $crypt_replysign and
- $smime_is_default.
-
- 3.39. crypt_autosmime
-
- Type: boolean
- Default: yes
-
- This variable controls whether or not mutt may automatically enable S/MIME
- encryption/signing for messages. See also $crypt_autoencrypt,
- $crypt_replyencrypt, $crypt_autosign, $crypt_replysign and
- $smime_is_default.
-
- 3.40. date_format
-
- Type: string
- Default: "!%a, %b %d, %Y at %I:%M:%S%p %Z"
-
- This variable controls the format of the date printed by the "%d" sequence
- in $index_format. This is passed to the strftime(3) function to process
- the date, see the man page for the proper syntax.
-
- 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).
-
- 3.41. default_hook
-
- Type: string
- Default: "~f %s !~P | (~P ~C %s)"
-
- This variable controls how "message-hook", "reply-hook", "send-hook",
- "send2-hook", "save-hook", and "fcc-hook" 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.
-
- 3.42. delete
-
- 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.
-
- 3.43. delete_untag
-
- Type: boolean
- Default: yes
-
- If this option is set, mutt 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.
-
- 3.44. digest_collapse
-
- Type: boolean
- Default: yes
-
- If this option is set, mutt'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.
-
- 3.45. display_filter
-
- Type: path
- Default: (empty)
-
- 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.
-
- 3.46. dotlock_program
-
- Type: path
- Default: "/usr/bin/mutt_dotlock"
-
- Contains the path of the mutt_dotlock(8) binary to be used by mutt.
-
- 3.47. dsn_notify
-
- Type: string
- Default: (empty)
-
- 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.
-
- Example:
-
- set dsn_notify="failure,delay"
-
-
- Note: when using $sendmail for delivery, you should not enable this unless
- you are either using Sendmail 8.8.x or greater or a MTA providing a
- sendmail(1)-compatible interface supporting the -N option for DSN. For
- SMTP delivery, DSN support is autodetected so that it depends on the
- server whether DSN will be used or not.
-
- 3.48. dsn_return
-
- Type: string
- Default: (empty)
-
- 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.
-
- Example:
-
- set dsn_return=hdrs
-
-
- Note: when using $sendmail for delivery, you should not enable this unless
- you are either using Sendmail 8.8.x or greater or a MTA providing a
- sendmail(1)-compatible interface supporting the -R option for DSN. For
- SMTP delivery, DSN support is autodetected so that it depends on the
- server whether DSN will be used or not.
-
- 3.49. duplicate_threads
-
- Type: boolean
- Default: yes
-
- This variable controls whether mutt, when $sort is set to threads, threads
- messages with the same Message-Id together. If it is set, it will indicate
- that it thinks they are duplicates of each other with an equals sign in
- the thread tree.
-
- 3.50. edit_headers
-
- Type: boolean
- Default: no
-
- This option allows you to edit the header of your outgoing messages along
- with the body of your message.
-
- Note that changes made to the References: and Date: headers are ignored
- for interoperability reasons.
-
- 3.51. editor
-
- Type: path
- Default: (empty)
-
- This variable specifies which editor is used by mutt. It defaults to the
- value of the $VISUAL, or $EDITOR, environment variable, or to the string
- "/usr/bin/editor" if neither of those are set.
-
- 3.52. encode_from
-
- Type: boolean
- Default: no
-
- When set, mutt will quoted-printable encode messages when they contain the
- string "From " (note the trailing space) in the beginning of a line. This
- is useful to avoid the tampering certain mail delivery and transport
- agents tend to do with messages (in order to prevent tools from
- misinterpreting the line as a mbox message separator).
-
- 3.53. envelope_from_address
-
- Type: e-mail address
- Default: (empty)
-
- Manually sets the envelope sender for outgoing messages. This value is
- ignored if $use_envelope_from is unset.
-
- 3.54. escape
-
- Type: string
- Default: "~"
-
- Escape character to use for functions in the builtin editor.
-
- 3.55. fast_reply
-
- Type: boolean
- Default: no
-
- 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.
-
- Note: this variable has no effect when the $autoedit variable is set.
-
- 3.56. fcc_attach
-
- Type: boolean
- Default: yes
-
- This variable controls whether or not attachments on outgoing messages are
- saved along with the main body of your message.
-
- 3.57. fcc_clear
-
- Type: boolean
- Default: no
-
- When this variable is set, FCCs will be stored unencrypted and unsigned,
- even when the actual message is encrypted and/or signed. (PGP only)
-
- 3.58. folder
-
- Type: path
- Default: "~/Mail"
-
- 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 when handling the "mailboxes"
- command.
-
- 3.59. folder_format
-
- Type: string
- Default: "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"
-
- 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:
-
- %C
-
- current file number
-
- %d
-
- date/time folder was last modified
-
- %f
-
- filename
-
- %F
-
- file permissions
-
- %g
-
- group name (or numeric gid, if missing)
-
- %l
-
- number of hard links
-
- %N
-
- N if folder has new mail, blank otherwise
-
- %s
-
- size in bytes
-
- %t
-
- "*" 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"
-
- %*X
-
- soft-fill with character "X" as pad
-
- For an explanation of "soft-fill", see the $index_format documentation.
-
- 3.60. followup_to
-
- Type: boolean
- Default: yes
-
- Controls whether or not the "Mail-Followup-To:" header field is generated
- when sending mail. When set, Mutt will generate this field when you are
- replying to a known mailing list, specified with the "subscribe" or
- "lists" commands.
-
- This field has two purposes. First, preventing you from receiving
- duplicate copies of replies to messages which you send to mailing lists,
- and 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.
-
- 3.61. force_name
-
- Type: boolean
- Default: no
-
- This variable is similar to $save_name, except that Mutt 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.
-
- 3.62. forward_decode
-
- Type: boolean
- Default: yes
-
- 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.
-
- 3.63. 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".
-
- 3.64. forward_format
-
- 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.
-
- 3.65. 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.
-
- 3.66. from
-
- Type: e-mail address
- Default: (empty)
-
- When set, this variable contains a default from address. It can be
- overridden using "my_hdr" (including from a "send-hook") and
- $reverse_name. This variable is ignored if $use_from is unset.
-
- This setting defaults to the contents of the environment variable $EMAIL.
-
- 3.67. gecos_mask
-
- Type: regular expression
- Default: "^[^,]*"
-
- A regular expression used by mutt to parse the GECOS field of a password
- entry when expanding the alias. The default value will return the string
- up to the first "," encountered. If the GECOS field contains a string like
- "lastname, firstname" then you should set it to ".*".
-
- This can be useful if you see the following behavior: you address an
- e-mail to user ID "stevef" whose full name is "Steve Franklin". If mutt
- 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
- will expand "Franklin" to "Franklin, Steve".
-
- 3.68. 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.
-
- 3.69. header
-
- Type: boolean
- Default: no
-
- When set, this variable causes Mutt to include the header of the message
- you are replying to into the edit buffer. The $weed setting applies.
-
- 3.70. 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 is running. Since this
- variable is primarily aimed at new users, neither of these should present
- a major problem.
-
- 3.71. hidden_host
-
- Type: boolean
- Default: no
-
- When set, mutt 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-IDs, and it will not lead to the cut-off of
- first-level domains.
-
- 3.72. hide_limited
-
- Type: boolean
- Default: no
-
- When set, mutt will not show the presence of messages that are hidden by
- limiting, in the thread tree.
-
- 3.73. hide_missing
-
- Type: boolean
- Default: yes
-
- When set, mutt will not show the presence of missing messages in the
- thread tree.
-
- 3.74. hide_thread_subject
-
- Type: boolean
- Default: yes
-
- When set, mutt will not show the subject of messages in the thread tree
- that have the same subject as their parent or closest previously displayed
- sibling.
-
- 3.75. hide_top_limited
-
- Type: boolean
- Default: no
-
- When set, mutt 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_limited is set, this option will have no effect.
-
- 3.76. hide_top_missing
-
- Type: boolean
- Default: yes
-
- When set, mutt will not show the presence of missing messages at the top
- of threads in the thread tree. Note that when $hide_missing is set, this
- option will have no effect.
-
- 3.77. history
-
- Type: number
- Default: 10
-
- This variable controls the size (in number of strings remembered) of the
- string history buffer per category. The buffer is cleared each time the
- variable is set.
-
- 3.78. history_file
-
- Type: path
- Default: "~/.mutthistory"
-
- The file in which Mutt will save its history.
-
- 3.79. honor_followup_to
-
- Type: quadoption
- Default: yes
-
- This variable controls whether or not a Mail-Followup-To header is honored
- when group-replying to a message.
-
- 3.80. hostname
-
- Type: string
- Default: (empty)
-
- Specifies the fully-qualified hostname of the system mutt is running on
- containing the host's name and the DNS domain it belongs to. It is used as
- the domain part (after "@") for local email addresses as well as
- Message-Id headers.
-
- Its value is determined at startup as follows: If the node's name as
- returned by the uname(3) function contains the hostname and the domain,
- these are used to construct $hostname. If there is no domain part
- returned, Mutt will look for a "domain" or "search" line in
- /etc/resolv.conf to determine the domain. Optionally, Mutt can be compiled
- with a fixed domain name in which case a detected one is not used.
-
- Also see $use_domain and $hidden_host.
-
- Note: On Debian systems, the default for this variable is obtained from
- /etc/mailname when Mutt starts.
-
- 3.81. ignore_linear_white_space
-
- Type: boolean
- Default: no
-
- This option replaces linear-white-space between encoded-word and text to a
- single space to prevent the display of MIME-encoded "Subject:" field from
- being divided into multiple lines.
-
- 3.82. ignore_list_reply_to
-
- Type: boolean
- Default: no
-
- Affects the behaviour of the <reply> function when replying to messages
- from mailing lists (as defined by the "subscribe" or "lists" commands).
- When set, if the "Reply-To:" field is set to the same value as the "To:"
- field, Mutt assumes that the "Reply-To:" 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.
-
- 3.83. imap_authenticators
-
- Type: string
- Default: (empty)
-
- This is a colon-delimited list of authentication methods mutt may attempt
- to use to log in to an IMAP server, in the order mutt should try them.
- Authentication methods are either "login" or the right side of an IMAP
- "AUTH=xxx" capability string, eg "digest-md5", "gssapi" or "cram-md5".
- This option is case-insensitive. If it's unset (the default) mutt will try
- all available methods, in order from most-secure to least-secure.
-
- Example:
-
- set imap_authenticators="gssapi:cram-md5:login"
-
-
- Note: Mutt will only fall back to other authentication methods if the
- previous methods are unavailable. If a method is available but
- authentication fails, mutt will not connect to the IMAP server.
-
- 3.84. imap_check_subscribed
-
- 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
- just as if you had issued individual "mailboxes" commands.
-
- 3.85. imap_delim_chars
-
- Type: string
- Default: "/."
-
- 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.
-
- 3.86. imap_headers
-
- Type: string
- Default: (empty)
-
- Mutt 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:", "List-Post:", "X-Label:") from IMAP servers before displaying
- the index menu. You may want to add more headers for spam detection.
-
- Note: This is a space separated list, items should be uppercase and not
- contain the colon, e.g. "X-BOGOSITY X-SPAM-STATUS" for the "X-Bogosity:"
- and "X-Spam-Status:" header fields.
-
- 3.87. imap_idle
-
- Type: boolean
- Default: no
-
- When set, mutt will attempt to use the IMAP IDLE extension to check for
- new mail in the current mailbox. Some servers (dovecot was the inspiration
- for this option) react badly to mutt's implementation. If your connection
- seems to freeze up periodically, try unsetting this.
-
- 3.88. imap_keepalive
-
- Type: number
- Default: 900
-
- This variable specifies the maximum amount of time in seconds that mutt
- will wait before polling open IMAP connections, to prevent the server from
- closing them before mutt 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.
-
- 3.89. imap_list_subscribed
-
- Type: boolean
- Default: no
-
- 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.
-
- 3.90. imap_login
-
- Type: string
- Default: (empty)
-
- Your login name on the IMAP server.
-
- This variable defaults to the value of $imap_user.
-
- 3.91. imap_pass
-
- Type: string
- Default: (empty)
-
- Specifies the password for your IMAP account. If unset, Mutt will prompt
- you for your password when you invoke the <fetch-mail> function or try to
- open an IMAP folder.
-
- Warning: you should only use this option when you are on a fairly secure
- machine, because the superuser can read your muttrc even if you are the
- only one who can read the file.
-
- 3.92. imap_passive
-
- Type: boolean
- Default: yes
-
- When set, mutt will not open new IMAP connections to check for new mail.
- Mutt 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
- invocation, or if opening the connection is slow.
-
- 3.93. imap_peek
-
- Type: boolean
- Default: yes
-
- When set, mutt 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.
-
- 3.94. imap_pipeline_depth
-
- Type: number
- Default: 15
-
- Controls the number of IMAP commands that may be queued up before they are
- sent to the server. A deeper pipeline reduces the amount of time mutt must
- wait for the server, and can make IMAP servers feel much more responsive.
- But not all servers correctly handle pipelined commands, so if you have
- problems you might want to try setting this variable to 0.
-
- Note: Changes to this variable have no effect on open connections.
-
- 3.95. imap_servernoise
-
- Type: boolean
- Default: yes
-
- When set, mutt 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.
-
- 3.96. imap_user
-
- Type: string
- Default: (empty)
-
- 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.
-
- 3.97. implicit_autoview
-
- Type: boolean
- Default: no
-
- If set to "yes", mutt 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 will use the
- viewer defined in that entry to convert the body part to text form.
-
- 3.98. 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.
-
- 3.99. include_onlyfirst
-
- Type: boolean
- Default: no
-
- Controls whether or not Mutt includes only the first attachment of the
- message you are replying.
-
- 3.100. 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.
-
- This option is a format string, please see the description of
- $index_format for supported printf(3)-style sequences.
-
- Because for format=lowed style messages the quoting mechanism is strictly
- defined, this setting is ignored if $text_flowed is set.
-
- 3.101. 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 details). The
- following sequences are defined in Mutt:
-
- %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
-
- sender (address + real name), either From: or Return-Path:
-
- %F
-
- author name, or recipient name if the message is from you
-
- %H
-
- spam attribute(s) of this message
-
- %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
-
- original save folder where mutt would formerly have stashed the
- message: list name or recipient name if not sent to a list
-
- %P
-
- progress indicator for the builtin pager (how much of the file has
- been displayed)
-
- %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
-
- %X
-
- number of attachments (please see the "attachments" section for
- possible speed effects)
-
- %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(3); 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(3); a
- leading bang disables locales
-
- %(fmt)
-
- the local date and time when the message was received. "fmt" is
- expanded by the library function strftime(3); a leading bang
- disables locales
-
- %<fmt>
-
- the current local time. "fmt" is expanded by the library function
- strftime(3); 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"
-
- %*X
-
- soft-fill with character "X" as pad
-
- "Soft-fill" deserves some explanation: Normal right-justification will
- print everything to the left of the "%>", displaying padding and whatever
- lies to the right only if there's room. By contrast, soft-fill gives
- priority to the right-hand side, guaranteeing space to display it and
- showing padding only if there's still room. If necessary, soft-fill will
- eat text leftwards to make room for rightward text.
-
- Note that these expandos are supported in "save-hook", "fcc-hook" and
- "fcc-save-hook", too.
-
- 3.102. ispell
-
- Type: path
- Default: "ispell"
-
- How to invoke ispell (GNU's spell-checking software).
-
- 3.103. 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.
-
- 3.104. 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 environment variable $LC_TIME.
-
- 3.105. mail_check
-
- Type: number
- Default: 5
-
- This variable configures how often (in seconds) mutt should look for new
- mail. Also see the $timeout variable.
-
- 3.106. mailcap_path
-
- Type: string
- Default: (empty)
-
- This variable specifies which files to consult when attempting to display
- MIME bodies not directly supported by Mutt.
-
- 3.107. mailcap_sanitize
-
- Type: boolean
- Default: yes
-
- If set, mutt 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!
-
- 3.108. maildir_mtime
-
- Type: boolean
- Default: no
-
- If set, the sort-by-date option in the browser will sort maildirs smartly,
- not using the mtime of the maildir itself but that of the newest message
- in the new subdirectory, making the sorting by reverse date much more
- useful. People with maildirs over NFS may wish to leave this option unset.
-
- 3.109. header_cache
-
- Type: path
- Default: (empty)
-
- This variable points to the header cache database. If pointing to a
- directory Mutt will contain a header cache database file per folder, if
- pointing to a file that file will be a single global header cache. By
- default it is unset so no header caching will be used.
-
- Header caching can greatly improve speed when opening POP, IMAP MH or
- Maildir folders, see "caching" for details.
-
- 3.110. maildir_header_cache_verify
-
- Type: boolean
- Default: yes
-
- Check for Maildir unaware programs other than mutt having modified maildir
- files when the header cache is in use. This incurs one stat(2) per message
- every time the folder is opened (which can be very slow for NFS folders).
-
- 3.111. header_cache_pagesize
-
- Type: string
- Default: "16384"
-
- When mutt is compiled with either gdbm or bdb4 as the header cache
- backend, this option changes the database page size. Too large or too
- small values can waste space, memory, or CPU time. The default should be
- more or less optimal for most use cases.
-
- 3.112. maildir_trash
-
- Type: boolean
- Default: no
-
- If set, messages marked as deleted will be saved with the maildir trashed
- flag instead of unlinked. Note: this only applies to maildir-style
- mailboxes. Setting it will have no effect on other mailbox types.
-
- 3.113. mark_old
-
- Type: boolean
- Default: yes
-
- Controls whether or not mutt marks new unread messages as old if you exit
- a mailbox without reading them. With this option set, the next time you
- start mutt, the messages will show up with an "O" next to them in the
- index menu, indicating that they are old.
-
- 3.114. 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.
-
- 3.115. 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.
-
- 3.116. mbox
-
- Type: path
- Default: "~/mbox"
-
- This specifies the folder into which read mail in your $spoolfile folder
- will be appended.
-
- Also see the $move variable.
-
- 3.117. 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".
-
- 3.118. metoo
-
- Type: boolean
- Default: no
-
- If unset, Mutt will remove your address (see the "alternates" command)
- from the list of recipients when replying to a message.
-
- 3.119. 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.)
-
- 3.120. 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.
-
- 3.121. 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).
-
- 3.122. meta_key
-
- Type: boolean
- Default: no
-
- If set, forces Mutt 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".
-
- 3.123. mh_purge
-
- Type: boolean
- Default: no
-
- When unset, mutt will mimic mh's behaviour and rename deleted messages to
- ,<old file name> in mh folders instead of really deleting them. This
- leaves the message on disk but makes programs reading the folder ignore
- it. If the variable is set, the message files will simply be deleted.
-
- This option is similar to $maildir_trash for Maildir folders.
-
- 3.124. mh_seq_flagged
-
- Type: string
- Default: "flagged"
-
- The name of the MH sequence used for flagged messages.
-
- 3.125. mh_seq_replied
-
- Type: string
- Default: "replied"
-
- The name of the MH sequence used to tag replied messages.
-
- 3.126. mh_seq_unseen
-
- Type: string
- Default: "unseen"
-
- The name of the MH sequence used for unseen messages.
-
- 3.127. mime_forward
-
- Type: quadoption
- Default: no
-
- When set, the message you are forwarding will be attached as a separate
- message/rfc822 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.
-
- 3.128. 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.
-
- 3.129. mime_forward_rest
-
- Type: quadoption
- Default: yes
-
- When forwarding multiple attachments of a MIME message from the attachment
- menu, attachments which cannot be decoded in a reasonable manner will be
- attached to the newly composed message if this option is set.
-
- 3.130. mix_entry_format
-
- Type: string
- Default: "%4n %c %-16s %a"
-
- 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.
-
- 3.131. mixmaster
-
- Type: path
- Default: "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.
-
- Note: On Debian systems, this option is set by default to
- "mixmaster-filter" in /etc/Muttrc.
-
- 3.132. move
-
- Type: quadoption
- Default: no
-
- Controls whether or not Mutt will move read messages from your spool
- mailbox to your $mbox mailbox, or as a result of a "mbox-hook" command.
-
- 3.133. message_cachedir
-
- Type: path
- Default: (empty)
-
- Set this to a directory and mutt will cache copies of messages from your
- IMAP and POP servers here. You are free to remove entries at any time.
-
- When setting this variable to a directory, mutt needs to fetch every
- remote message only once and can perform regular expression searches as
- fast as for local folders.
-
- Also see the $message_cache_clean variable.
-
- 3.134. message_cache_clean
-
- Type: boolean
- Default: no
-
- If set, mutt will clean out obsolete entries from the message cache when
- the mailbox is synchronized. You probably only want to set it every once
- in a while, since it can be a little slow (especially for large folders).
-
- 3.135. 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.
-
- 3.136. narrow_tree
-
- Type: boolean
- Default: no
-
- This variable, when set, makes the thread tree narrower, allowing deeper
- threads to fit on the screen.
-
- 3.137. 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, $write_inc and $net_inc.
-
- 3.138. pager
-
- Type: path
- Default: "builtin"
-
- This variable specifies which pager you would like to use to view
- messages. The value "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 functions directly from the
- pager, and screen resizes cause lines longer than the screen width to be
- badly formatted in the help menu.
-
- 3.139. 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 will display the line after the last one on the screen at the top of
- the next page (0 lines of context).
-
- 3.140. pager_format
-
- Type: string
- Default: "-%Z- %C/%m: %-20.20n %s%* -- (%P)"
-
- 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.
-
- 3.141. 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 setting 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.
-
- 3.142. 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.
-
- 3.143. crypt_autosign
-
- Type: boolean
- Default: no
-
- Setting this variable will cause Mutt 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
- instead of the pgp menu. (Crypto only)
-
- 3.144. crypt_autoencrypt
-
- Type: boolean
- Default: no
-
- Setting this variable will cause Mutt 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 instead.
- (Crypto only)
-
- 3.145. pgp_ignore_subkeys
-
- Type: boolean
- Default: yes
-
- Setting this variable will cause Mutt 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)
-
- 3.146. crypt_replyencrypt
-
- Type: boolean
- Default: yes
-
- If set, automatically PGP or OpenSSL encrypt replies to messages which are
- encrypted. (Crypto only)
-
- 3.147. crypt_replysign
-
- Type: boolean
- Default: no
-
- If set, automatically PGP or OpenSSL sign replies to messages which are
- signed.
-
- Note: this does not work on messages that are encrypted and signed!
- (Crypto only)
-
- 3.148. crypt_replysignencrypted
-
- Type: boolean
- Default: no
-
- 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 is not able to find out whether an encrypted message is also signed.
- (Crypto only)
-
- 3.149. crypt_timestamp
-
- Type: boolean
- Default: yes
-
- If set, mutt 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)
-
- 3.150. pgp_use_gpg_agent
-
- Type: boolean
- Default: no
-
- If set, mutt will use a possibly-running gpg-agent(1) process. (PGP only)
-
- 3.151. crypt_verify_sig
-
- Type: quadoption
- Default: yes
-
- If "yes", always attempt to verify PGP or S/MIME signatures. If "ask-*",
- ask whether or not to verify the signature. If \Fi"no", never attempt to
- verify cryptographic signatures. (Crypto only)
-
- 3.152. smime_is_default
-
- Type: boolean
- Default: no
-
- The default behaviour of mutt 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 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)
-
- 3.153. 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)
-
- 3.154. smime_decrypt_use_default_key
-
- Type: boolean
- Default: yes
-
- If set (default) this tells mutt to use the default key for decryption.
- Otherwise, if managing multiple certificate-key-pairs, mutt 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)
-
- 3.155. 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)
-
- 3.156. pgp_good_sign
-
- Type: regular expression
- Default: (empty)
-
- 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)
-
- 3.157. pgp_check_exit
-
- Type: boolean
- Default: yes
-
- If set, mutt 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)
-
- 3.158. pgp_long_ids
-
- Type: boolean
- Default: no
-
- If set, use 64 bit PGP key IDs, if unset use the normal 32 bit key IDs.
- (PGP only)
-
- 3.159. 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)
-
- 3.160. pgp_autoinline
-
- Type: boolean
- Default: no
-
- This option controls whether Mutt 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 might automatically use PGP/MIME for messages which consist
- of more than a single MIME part. Mutt can be configured to ask before
- sending PGP/MIME messages when inline (traditional) would not work.
-
- Also see the $pgp_mime_auto variable.
-
- Also note that using the old-style PGP message format is strongly
- deprecated. (PGP only)
-
- 3.161. pgp_replyinline
-
- Type: boolean
- Default: no
-
- Setting this variable will cause Mutt 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 internals
- for previously checked/flagged messages.
-
- Note that Mutt might automatically use PGP/MIME for messages which consist
- of more than a single MIME part. Mutt can be configured to ask before
- sending PGP/MIME messages when inline (traditional) would not work.
-
- Also see the $pgp_mime_auto variable.
-
- Also note that using the old-style PGP message format is strongly
- deprecated. (PGP only)
-
- 3.162. pgp_show_unusable
-
- Type: boolean
- Default: yes
-
- If set, mutt 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)
-
- 3.163. pgp_sign_as
-
- Type: string
- Default: (empty)
-
- 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)
-
- 3.164. pgp_strict_enc
-
- Type: boolean
- Default: yes
-
- If set, Mutt 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)
-
- 3.165. pgp_timeout
-
- Type: number
- Default: 300
-
- The number of seconds after which a cached passphrase will expire if not
- used. (PGP only)
-
- 3.166. pgp_sort_keys
-
- Type: sort order
- Default: address
-
- Specifies how the entries in the pgp 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)
-
- 3.167. pgp_mime_auto
-
- Type: quadoption
- Default: ask-yes
-
- This option controls whether Mutt 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 strongly
- deprecated. (PGP only)
-
- 3.168. pgp_auto_decode
-
- Type: boolean
- Default: no
-
- If set, mutt 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 will automatically
- check the message for traditional pgp.
-
- 3.169. pgp_mime_signature_filename
-
- Type: string
- Default: "signature.asc"
-
- This option sets the filename used for signature parts in PGP/MIME signed
- messages.
-
- 3.170. pgp_mime_signature_description
-
- Type: string
- Default: "Digital signature"
-
- This option sets the Content-Description used for signature parts in
- PGP/MIME signed messages.
-
- 3.171. pgp_decode_command
-
- Type: string
- Default: (empty)
-
- 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 and gpg sample configuration
- files in the samples/ subdirectory which has been installed on your system
- alongside the documentation. (PGP only)
-
- 3.172. pgp_getkeys_command
-
- Type: string
- Default: (empty)
-
- This command is invoked whenever mutt will need public key information. Of
- the sequences supported by $pgp_decode_command, %r is the only
- printf(3)-like sequence used with this format. (PGP only)
-
- 3.173. pgp_verify_command
-
- Type: string
- Default: (empty)
-
- This command is used to verify PGP signatures.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.174. pgp_decrypt_command
-
- Type: string
- Default: (empty)
-
- This command is used to decrypt a PGP encrypted message.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.175. pgp_clearsign_command
-
- Type: string
- Default: (empty)
-
- This format is used to create an old-style "clearsigned" PGP message. Note
- that the use of this format is strongly deprecated.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.176. pgp_sign_command
-
- Type: string
- Default: (empty)
-
- This command is used to create the detached PGP signature for a
- multipart/signed PGP/MIME body part.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.177. pgp_encrypt_sign_command
-
- Type: string
- Default: (empty)
-
- This command is used to both sign and encrypt a body part.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.178. pgp_encrypt_only_command
-
- Type: string
- Default: (empty)
-
- This command is used to encrypt a body part without signing it.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.179. pgp_import_command
-
- Type: string
- Default: (empty)
-
- This command is used to import a key from a message into the user's public
- key ring.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.180. pgp_export_command
-
- Type: string
- Default: (empty)
-
- This command is used to export a public key from the user's key ring.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.181. pgp_verify_key_command
-
- Type: string
- Default: (empty)
-
- This command is used to verify key information from the key selection
- menu.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.182. pgp_list_secring_command
-
- Type: string
- Default: (empty)
-
- 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.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.183. pgp_list_pubring_command
-
- Type: string
- Default: (empty)
-
- 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.
-
- This is a format string, see the $pgp_decode_command command for possible
- printf(3)-like sequences. (PGP only)
-
- 3.184. forward_decrypt
-
- 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)
-
- 3.185. smime_timeout
-
- Type: number
- Default: 300
-
- The number of seconds after which a cached passphrase will expire if not
- used. (S/MIME only)
-
- 3.186. smime_encrypt_with
-
- Type: string
- Default: (empty)
-
- This sets the algorithm that should be used for encryption. Valid choices
- are "des", "des3", "rc2-40", "rc2-64", "rc2-128". If unset, "3des"
- (TripleDES) is used. (S/MIME only)
-
- 3.187. smime_keys
-
- Type: path
- Default: (empty)
-
- Since for S/MIME there is no pubring/secring as with PGP, mutt has to
- handle storage and 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 option points to the location of the private keys. (S/MIME
- only)
-
- 3.188. smime_ca_location
-
- Type: path
- Default: (empty)
-
- This variable contains the name of either a directory, or a file which
- contains trusted certificates for use with OpenSSL. (S/MIME only)
-
- Note: On Debian systems, this defaults to the first existing file in the
- following list: ~/.smime/ca-certificates.crt ~/.smime/ca-bundle.crt
- /etc/ssl/certs/ca-certificates.crt.
-
- 3.189. smime_certificates
-
- Type: path
- Default: (empty)
-
- Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to the location of the certificates. (S/MIME
- only)
-
- 3.190. smime_decrypt_command
-
- Type: string
- Default: (empty)
-
- 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)
-
- 3.191. smime_verify_command
-
- Type: string
- Default: (empty)
-
- This command is used to verify S/MIME signatures of type multipart/signed.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.192. smime_verify_opaque_command
-
- Type: string
- Default: (empty)
-
- This command is used to verify S/MIME signatures of type
- application/x-pkcs7-mime.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.193. smime_sign_command
-
- Type: string
- Default: (empty)
-
- This command is used to created S/MIME signatures of type
- multipart/signed, which can be read by all mail clients.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.194. smime_sign_opaque_command
-
- Type: string
- Default: (empty)
-
- 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.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.195. smime_encrypt_command
-
- Type: string
- Default: (empty)
-
- This command is used to create encrypted S/MIME messages.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.196. smime_pk7out_command
-
- Type: string
- Default: (empty)
-
- This command is used to extract PKCS7 structures of S/MIME signatures, in
- order to extract the public X509 certificate(s).
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.197. smime_get_cert_command
-
- Type: string
- Default: (empty)
-
- This command is used to extract X509 certificates from a PKCS7 structure.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.198. smime_get_signer_cert_command
-
- Type: string
- Default: (empty)
-
- 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:" field.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.199. smime_import_cert_command
-
- Type: string
- Default: (empty)
-
- This command is used to import a certificate via smime_keys.
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.200. smime_get_cert_email_command
-
- Type: string
- Default: (empty)
-
- 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).
-
- This is a format string, see the $smime_decrypt_command command for
- possible printf(3)-like sequences. (S/MIME only)
-
- 3.201. smime_default_key
-
- Type: string
- Default: (empty)
-
- 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)
-
- 3.202. ssl_client_cert
-
- Type: path
- Default: (empty)
-
- The file containing a client certificate and its associated private key.
-
- 3.203. ssl_force_tls
-
- Type: boolean
- Default: no
-
- If this variable is set, Mutt 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.
-
- 3.204. ssl_starttls
-
- Type: quadoption
- Default: yes
-
- If set (the default), mutt will attempt to use STARTTLS on servers
- advertising the capability. When unset, mutt will not attempt to use
- STARTTLS regardless of the server's capabilities.
-
- 3.205. certificate_file
-
- Type: path
- Default: "~/.mutt_certificates"
-
- This variable specifies the file where the certificates you trust are
- saved. When an unknown certificate is encountered, you are asked if you
- accept it or not. If you accept it, the certificate can also be saved in
- this file and further connections are automatically accepted.
-
- You can also manually add CA certificates in this file. Any server
- certificate that is signed with one of these CA certificates is also
- automatically accepted.
-
- Example:
-
- set certificate_file=~/.mutt/certificates
-
-
- 3.206. ssl_use_sslv3
-
- Type: boolean
- Default: yes
-
- This variable specifies whether to attempt to use SSLv3 in the SSL
- authentication process.
-
- 3.207. ssl_use_tlsv1
-
- Type: boolean
- Default: yes
-
- This variable specifies whether to attempt to use TLSv1 in the SSL
- authentication process.
-
- 3.208. ssl_min_dh_prime_bits
-
- Type: number
- Default: 0
-
- 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.
-
- 3.209. ssl_ca_certificates_file
-
- Type: path
- Default: (empty)
-
- This variable specifies a file containing trusted CA certificates. Any
- server certificate that is signed with one of these CA certificates is
- also automatically accepted.
-
- Example:
-
- set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-
- Note: On Debian systems, this variable defaults to the example mentioned.
- This file is managed by the "ca-certificates" package.
-
- 3.210. pipe_split
-
- Type: boolean
- Default: no
-
- Used in connection with the <pipe-message> function following
- <tag-prefix>. If this variable is unset, when piping a list of tagged
- messages Mutt will concatenate the messages and will pipe them all
- concatenated. When set, Mutt 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.
-
- 3.211. pipe_decode
-
- Type: boolean
- Default: no
-
- Used in connection with the <pipe-message> command. When unset, Mutt will
- pipe the messages without any preprocessing. When set, Mutt will weed
- headers and will attempt to decode the messages first.
-
- 3.212. pipe_sep
-
- Type: string
- Default: "\n"
-
- The separator to add between messages when piping a list of tagged
- messages to an external Unix command.
-
- 3.213. pop_authenticators
-
- Type: string
- Default: (empty)
-
- This is a colon-delimited list of authentication methods mutt may attempt
- to use to log in to an POP server, in the order mutt should try them.
- Authentication methods are either "user", "apop" or any SASL mechanism, eg
- "digest-md5", "gssapi" or "cram-md5". This option is case-insensitive. If
- this option is unset (the default) mutt will try all available methods, in
- order from most-secure to least-secure.
-
- Example:
-
- set pop_authenticators="digest-md5:apop:user"
-
-
- 3.214. pop_auth_try_all
-
- Type: boolean
- Default: yes
-
- If set, Mutt will try all available authentication methods. When unset,
- Mutt will only fall back to other authentication methods if the previous
- methods are unavailable. If a method is available but authentication
- fails, Mutt will not connect to the POP server.
-
- 3.215. pop_checkinterval
-
- Type: number
- Default: 60
-
- This variable configures how often (in seconds) mutt should look for new
- mail in the currently selected mailbox if it is a POP mailbox.
-
- 3.216. pop_delete
-
- Type: quadoption
- Default: ask-no
-
- If set, Mutt will delete successfully downloaded messages from the POP
- server when using the <fetch-mail> function. When unset, Mutt will
- download messages but also leave them on the POP server.
-
- 3.217. pop_host
-
- Type: string
- Default: (empty)
-
- The name of your POP server for the <fetch-mail> function. You can also
- specify an alternative port, username and password, ie:
-
- [pop[s]://][username[:password]@]popserver[:port]
-
-
- where "[...]" denotes an optional part.
-
- 3.218. pop_last
-
- Type: boolean
- Default: no
-
- If this variable is set, mutt will try to use the "LAST" POP command for
- retrieving only unread messages from the POP server when using the
- <fetch-mail> function.
-
- 3.219. pop_reconnect
-
- Type: quadoption
- Default: ask-yes
-
- Controls whether or not Mutt will try to reconnect to the POP server if
- the connection is lost.
-
- 3.220. pop_user
-
- Type: string
- Default: (empty)
-
- Your login name on the POP server.
-
- This variable defaults to your user name on the local machine.
-
- 3.221. pop_pass
-
- Type: string
- Default: (empty)
-
- Specifies the password for your POP account. If unset, Mutt will prompt
- you for your password when you open a POP mailbox.
-
- Warning: you should only use this option when you are on a fairly secure
- machine, because the superuser can read your muttrc even if you are the
- only one who can read the file.
-
- 3.222. post_indent_string
-
- Type: string
- Default: (empty)
-
- Similar to the $attribution variable, Mutt will append this string after
- the inclusion of a message which is being replied to.
-
- 3.223. postpone
-
- Type: quadoption
- Default: ask-yes
-
- Controls whether or not messages are saved in the $postponed mailbox when
- you elect not to send immediately.
-
- Also see the $recall variable.
-
- 3.224. postponed
-
- Type: path
- Default: "~/postponed"
-
- Mutt allows you to indefinitely "postpone sending a message" which you are
- editing. When you choose to postpone a message, Mutt saves it in the
- mailbox specified by this variable.
-
- Also see the $postpone variable.
-
- 3.225. preconnect
-
- Type: string
- Default: (empty)
-
- If set, a shell command to be executed if mutt 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 gives up opening the server. Example:
-
- set 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.
-
- When set, Mutt uses the tunnel for all remote connections. Please see
- "account-hook" in the manual for how to use different tunnel commands per
- connection.
-
- 3.226. print
-
- Type: quadoption
- Default: ask-no
-
- Controls whether or not Mutt really prints messages. This is set to
- "ask-no" by default, because some people accidentally hit "p" often.
-
- 3.227. print_command
-
- Type: path
- Default: "lpr"
-
- This specifies the command pipe that should be used to print messages.
-
- 3.228. 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.
-
- 3.229. 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.
-
- 3.230. prompt_after
-
- Type: boolean
- Default: yes
-
- If you use an external $pager, setting this variable will cause Mutt to
- prompt you for a command when the pager exits rather than returning to the
- index menu. If unset, Mutt will return to the index menu when the external
- pager exits.
-
- 3.231. query_command
-
- Type: path
- Default: (empty)
-
- This specifies the command that mutt 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.
-
- 3.232. query_format
-
- Type: string
- Default: "%4c %t %-25.25a %-25.25n %?e?(%e)?"
-
- This variable describes the format of the "query" menu. The following
- printf(3)-style sequences are understood:
-
- %a
-
- destination address
-
- %c
-
- current entry number
-
- %e
-
- extra information *
-
- %n
-
- destination name
-
- %t
-
- "*" if current entry is tagged, a space otherwise
-
- %>X
-
- right justify the rest of the string and pad with "X"
-
- %|X
-
- pad to the end of the line with "X"
-
- %*X
-
- soft-fill with character "X" as pad
-
- For an explanation of "soft-fill", see the $index_format documentation.
-
- * = can be optionally printed if nonzero, see the $status_format
- documentation.
-
- 3.233. quit
-
- Type: quadoption
- Default: yes
-
- This variable controls whether "quit" and "exit" actually quit from mutt.
- If this option is set, they do quit, if it is unset, 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.
-
- 3.234. 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. Quoted text may be filtered out
- using the <toggle-quoted> command, or colored according to the "color
- quoted" family of directives.
-
- Higher levels of quoting may be colored differently ("color quoted1",
- "color quoted2", etc.). The quoting level is determined by removing the
- last character from the matched text and recursively reapplying the
- regular expression until it fails to produce a match.
-
- Match detection may be overridden by the $smileys regular expression.
-
- 3.235. read_inc
-
- Type: number
- Default: 10
-
- If set to a value greater than 0, Mutt will display which message it is
- currently on when reading a mailbox or when performing search actions such
- as search and limit. The message is printed after this many messages have
- been read or searched (e.g., if set to 25, Mutt will print a message when
- it is at message 25, and then again when it gets to message 50). This
- variable is meant to indicate progress when reading or searching 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, $net_inc and $time_inc variables and the "tuning"
- section of the manual for performance considerations.
-
- 3.236. read_only
-
- Type: boolean
- Default: no
-
- If set, all folders are opened in read-only mode.
-
- 3.237. realname
-
- Type: string
- Default: (empty)
-
- 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 that this
- variable will not be used when the user has set a real name in the $from
- variable.
-
- 3.238. recall
-
- Type: quadoption
- Default: ask-yes
-
- Controls whether or not Mutt recalls postponed messages when composing a
- new message.
-
- Setting this variable to is not generally useful, and thus not
- recommended.
-
- Also see $postponed variable.
-
- 3.239. record
-
- Type: path
- Default: "~/sent"
-
- 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:" 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.
-
- 3.240. 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:".
-
- 3.241. reply_self
-
- Type: boolean
- Default: no
-
- If unset and you are replying to a message sent by you, Mutt will assume
- that you want to reply to the recipients of that message rather than to
- yourself.
-
- Also see the "alternates" command.
-
- 3.242. reply_to
-
- Type: quadoption
- Default: ask-yes
-
- If set, when replying to a message, Mutt will use the address listed in
- the Reply-to: header 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.
-
- 3.243. 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.
-
- 3.244. reverse_alias
-
- Type: boolean
- Default: no
-
- This variable controls whether or not Mutt 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.
-
- 3.245. 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.
-
- Also see the "alternates" command.
-
- 3.246. reverse_realname
-
- Type: boolean
- Default: yes
-
- This variable fine-tunes the behaviour of the $reverse_name feature. When
- it is set, mutt will use the address from incoming messages as-is,
- possibly including eventual real names. When it is unset, mutt will
- override any such real names with the setting of the $realname variable.
-
- 3.247. rfc2047_parameters
-
- Type: boolean
- Default: no
-
- When this variable is set, Mutt will decode RFC2047-encoded MIME
- parameters. You want to set this variable when mutt suggests you to save
- attachments to files named like:
-
- =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-
- When this variable is set interactively, the change won't be active until
- you change folders.
-
- Note that this use of RFC2047'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
- generates this kind of encoding. Instead, mutt will unconditionally use
- the encoding specified in RFC2231.
-
- 3.248. save_address
-
- Type: boolean
- Default: no
-
- If set, mutt 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.
-
- 3.249. 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 does not delete MH
- and Maildir directories.
-
- 3.250. save_history
-
- Type: number
- Default: 0
-
- This variable controls the size of the history (per category) saved in the
- $history_file file.
-
- 3.251. 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.
-
- 3.252. 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 related are used.
-
- 3.253. 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. Since mutt
- scores are always greater than or equal to zero, the default setting of
- this variable will never mark a message for deletion.
-
- 3.254. 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".
-
- 3.255. 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. Since mutt
- scores are always greater than or equal to zero, the default setting of
- this variable will never mark a message read.
-
- 3.256. send_charset
-
- Type: string
- Default: "us-ascii:iso-8859-1:utf-8"
-
- A colon-delimited list of character sets for outgoing messages. Mutt 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".
-
- In case the text cannot be converted into one of these exactly, mutt uses
- $charset as a fallback.
-
- 3.257. sendmail
-
- Type: path
- Default: "/usr/sbin/sendmail -oem -oi"
-
- Specifies the program and arguments used to deliver mail sent by Mutt.
- Mutt expects that the specified program interprets additional arguments as
- recipient addresses.
-
- 3.258. 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 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.
-
- 3.259. shell
-
- Type: path
- Default: (empty)
-
- Command to use when spawning a subshell. By default, the user's login
- shell from /etc/passwd is used.
-
- 3.260. sig_dashes
-
- Type: boolean
- Default: yes
-
- If set, a line containing "-- " (note the trailing 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 has the ability to highlight the signature in
- a different color in the builtin pager.
-
- 3.261. 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.
-
- 3.262. 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
- standard output.
-
- 3.263. simple_search
-
- Type: string
- Default: "~f %s | ~s %s"
-
- Specifies how Mutt should expand a simple search into a real search
- pattern. A simple search is one that does not contain any of the "~"
- pattern operators. See "patterns" for more information on search patterns.
-
- For example, if you simply type "joe" at a search or limit prompt, Mutt
- will automatically expand it to the value specified by this variable by
- replacing "%s" with the supplied string. For the default value, "joe"
- would be expanded to: "~f joe | ~s joe".
-
- 3.264. 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.
-
- 3.265. smileys
-
- Type: regular expression
- Default: "(>From )|(:[-^]?[][)(><}{|/DP])"
-
- The pager uses this variable to catch some common false positives of
- $quote_regexp, most notably smileys and not consider a line quoted text if
- it also matches $smileys. This mostly happens at the beginning of a line.
-
- 3.266. 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.
-
- 3.267. smtp_authenticators
-
- Type: string
- Default: (empty)
-
- This is a colon-delimited list of authentication methods mutt may attempt
- to use to log in to an SMTP server, in the order mutt should try them.
- Authentication methods are any SASL mechanism, eg "digest-md5", "gssapi"
- or "cram-md5". This option is case-insensitive. If it is "unset" (the
- default) mutt will try all available methods, in order from most-secure to
- least-secure.
-
- Example:
-
- set smtp_authenticators="digest-md5:cram-md5"
-
-
- 3.268. smtp_pass
-
- Type: string
- Default: (empty)
-
- Specifies the password for your SMTP account. If unset, Mutt will prompt
- you for your password when you first send mail via SMTP. See $smtp_url to
- configure mutt to send mail via SMTP.
-
- Warning: you should only use this option when you are on a fairly secure
- machine, because the superuser can read your muttrc even if you are the
- only one who can read the file.
-
- 3.269. smtp_url
-
- Type: string
- Default: (empty)
-
- Defines the SMTP smarthost where sent messages should relayed for
- delivery. This should take the form of an SMTP URL, eg:
-
- smtp[s]://[user[:pass]@]host[:port]/
-
-
- \.\.\. where "[...]" denotes an optional part. Setting this variable
- overrides the value of the $sendmail variable.
-
- 3.270. sort
-
- Type: sort order
- Default: date
-
- Specifies how to sort messages in the "index" menu. Valid values are:
-
- o date or date-sent
-
- o date-received
-
- o from
-
- o mailbox-order (unsorted)
-
- o score
-
- o size
-
- o spam
-
- o subject
-
- o threads
-
- o to
-
- You may optionally use the "reverse-" prefix to specify reverse sorting
- order (example: "set sort=reverse-date-sent").
-
- Note: On Debian systems, this option is set by default to "threads" in
- /etc/Muttrc.
-
- 3.271. sort_alias
-
- Type: sort order
- Default: alias
-
- Specifies how the entries in the "alias" menu are sorted. The following
- are legal values:
-
- o address (sort alphabetically by email address)
-
- o alias (sort alphabetically by alias name)
-
- o unsorted (leave in order specified in .muttrc)
-
- 3.272. 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 will just use "date-sent"). You can also specify the
- "last-" prefix in addition to the "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).
-
- 3.273. 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:
-
- o alpha (alphabetically)
-
- o date
-
- o size
-
- o unsorted
-
- You may optionally use the "reverse-" prefix to specify reverse sorting
- order (example: "set sort_browser=reverse-date").
-
- 3.274. 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 uses to thread messages
- by subject. With $sort_re set, mutt 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_re unset, mutt will attach the message whether or not this is the
- case, as long as the non-$reply_regexp parts of both messages are
- identical.
-
- 3.275. spam_separator
-
- Type: string
- Default: ","
-
- This variable 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 this variable's value as a separator.
-
- 3.276. spoolfile
-
- Type: path
- Default: (empty)
-
- If your spool mailbox is in a non-default place where Mutt cannot find it,
- you can specify its location with this variable. Mutt will automatically
- set this variable to the value of the environment variable $MAIL if it is
- not set.
-
- 3.277. 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).
-
- 3.278. status_format
-
- Type: string
- Default: "-%r-Mutt: %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 *
-
- %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 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"
-
- %*X
-
- soft-fill with character "X" as pad
-
- For an explanation of "soft-fill", see the $index_format documentation.
-
- * = 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_string may 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.?
-
- You can also switch between two strings using the following construct:
-
- %?<sequence_char>?<if_string>&<else_string>?
-
- If the value of sequence_char is non-zero, if_string will be expanded,
- otherwise else_string will be expanded.
-
- You can 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
- will replace any dots in the expansion by underscores. This might be
- helpful with IMAP folders that don't like dots in folder names.
-
- 3.279. 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. If $help is set, too it'll
- be placed at the bottom.
-
- 3.280. strict_threads
-
- Type: boolean
- Default: no
-
- If set, threading will only make use of the "In-Reply-To" and
- "References:" 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 subjects like "hi" which
- will get grouped together. See also $sort_re for a less drastic way of
- controlling this behaviour.
-
- 3.281. suspend
-
- Type: boolean
- Default: yes
-
- When unset, mutt won't stop when the user presses the terminal's susp key,
- usually "^Z". This is useful if you run mutt inside an xterm using a
- command like "xterm -e mutt".
-
- 3.282. text_flowed
-
- Type: boolean
- Default: no
-
- When set, mutt will generate "format=flowed" bodies with a content type of
- "text/plain; format=flowed". 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.
-
- 3.283. thread_received
-
- Type: boolean
- Default: no
-
- When set, mutt uses the date received rather than the date sent to thread
- messages by subject.
-
- 3.284. thorough_search
-
- Type: boolean
- Default: no
-
- Affects the ~b and ~h search operations described in section "patterns".
- If set, the headers and body/attachments of messages to be searched are
- decoded before searching. If unset, messages are searched as they appear
- in the folder.
-
- Users searching attachments or for non-ASCII characters should set this
- value because decoding also includes MIME parsing/decoding and possible
- character set conversions. Otherwise mutt will attempt to match against
- the raw message received (for example quoted-printable encoded or with
- encoded headers) which may lead to incorrect search results.
-
- 3.285. tilde
-
- Type: boolean
- Default: no
-
- When set, the internal-pager will pad blank lines to the bottom of the
- screen with a tilde ("~").
-
- 3.286. time_inc
-
- Type: number
- Default: 0
-
- Along with $read_inc, $write_inc, and $net_inc, this variable controls the
- frequency with which progress updates are displayed. It suppresses updates
- less than $time_inc milliseconds apart. This can improve throughput on
- systems with slow terminals, or when running mutt on a remote system.
-
- Also see the "tuning" section of the manual for performance
- considerations.
-
- 3.287. timeout
-
- Type: number
- Default: 600
-
- When Mutt is waiting for user input either idleing in menus or in an
- interactive prompt, Mutt would block until input is present. Depending on
- the context, this would prevent certain operations from working, like
- checking for new mail or keeping an IMAP connection alive.
-
- This variable controls how many seconds Mutt will at most wait until it
- aborts waiting for input, performs these operations and continues to wait
- for input.
-
- A value of zero or less will cause Mutt to never time out.
-
- 3.288. tmpdir
-
- Type: path
- Default: (empty)
-
- This variable allows you to specify where Mutt 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.
-
- 3.289. 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.
- The second is used when you are the only recipient of the message. The
- third is when your address appears in the "To:" header field, but you are
- not the only recipient of the message. 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 subscribe to.
-
- 3.290. trash
-
- Type: path
- Default: (empty)
-
- 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 you have a way to clean the trash.
-
- 3.291. tunnel
-
- Type: string
- Default: (empty)
-
- Setting this variable will cause mutt 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/SMTP server. Example:
-
- set 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.
-
- 3.292. 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
- you may not be able to send mail.
-
- When set, Mutt will invoke $sendmail with the -B8BITMIME flag when sending
- 8-bit messages to enable ESMTP negotiation.
-
- 3.293. use_domain
-
- Type: boolean
- Default: yes
-
- When set, Mutt will qualify all local addresses (ones without the "@host"
- portion) with the value of $hostname. If unset, no addresses will be
- qualified.
-
- 3.294. use_envelope_from
-
- Type: boolean
- Default: no
-
- When set, mutt will set the envelope sender of the message. If
- $envelope_from_address is set, it will be used as the sender address. If
- unset, mutt will attempt to derive the sender from the "From:" header.
-
- Note that this information is passed to sendmail command using the -f
- command line switch. Therefore setting this option is not useful if the
- $sendmail variable already contains -f or if the executable pointed to by
- $sendmail doesn't support the -f switch.
-
- 3.295. use_from
-
- Type: boolean
- Default: yes
-
- When set, Mutt 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.
-
- 3.296. use_idn
-
- Type: boolean
- Default: yes
-
- When set, Mutt will show you international domain names decoded. Note: You
- can use IDNs for addresses even if this is unset. This variable only
- affects decoding.
-
- 3.297. use_ipv6
-
- Type: boolean
- Default: yes
-
- When set, Mutt will look for IPv6 addresses of hosts it tries to contact.
- If this option is unset, Mutt will restrict itself to IPv4 addresses.
- Normally, the default should work.
-
- 3.298. user_agent
-
- Type: boolean
- Default: yes
-
- When set, mutt will add a "User-Agent:" header to outgoing messages,
- indicating which version of mutt was used for composing them.
-
- 3.299. visual
-
- Type: path
- Default: (empty)
-
- Specifies the visual editor to invoke when the "~v" command is given in
- the builtin editor.
-
- 3.300. wait_key
-
- Type: boolean
- Default: yes
-
- Controls whether Mutt will ask you to press a key after an external
- command has been invoked by these functions: <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 will always ask for a key. When unset, Mutt will wait for a
- key only if the external command returned a non-zero status.
-
- 3.301. weed
-
- Type: boolean
- Default: yes
-
- When set, mutt will weed headers when displaying, forwarding, printing, or
- replying to messages.
-
- 3.302. wrap
-
- Type: number
- Default: 0
-
- When set to a positive value, mutt will wrap text at $wrap characters.
- When set to a negative value, mutt will wrap text so that there are $wrap
- characters of empty space on the right side of the terminal.
-
- 3.303. wrap_search
-
- Type: boolean
- Default: yes
-
- Controls whether searches wrap around the end.
-
- When set, searches will wrap around the first (or last) item. When unset,
- incremental searches will not wrap.
-
- 3.304. wrapmargin
-
- Type: number
- Default: 0
-
- (DEPRECATED) Equivalent to setting $wrap with a negative value.
-
- 3.305. 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, $net_inc and $time_inc variables and the "tuning"
- section of the manual for performance considerations.
-
- 3.306. write_bcc
-
- Type: boolean
- Default: yes
-
- Controls whether mutt writes out the "Bcc:" header when preparing messages
- to be sent. Exim users may wish to unset this. If mutt is set to deliver
- directly via SMTP (see $smtp_url), this option does nothing: mutt will
- never write out the "Bcc:" header in this case.
-
- Note: On Debian systems, exim4 and postfix strip BCC headers by default.
- The above warning applies to exim3 users, see /etc/Muttrc.
-
- 3.307. xterm_icon
-
- Type: string
- Default: "M%?n?AIL&ail?"
-
- Controls the format of the icon title, as long as xterm_set_titles is
- enabled. This string is identical in formatting to the one used by
- "$status_format".
-
- 3.308. xterm_set_titles
-
- Type: boolean
- Default: no
-
- Controls whether mutt sets the xterm title bar and icon name (as long as
- you are in an appropriate terminal).
-
- 3.309. xterm_title
-
- Type: string
- Default: "Mutt 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".
-
-4. 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.
-
- 4.1. generic menu
-
- 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 8.2. Default generic function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |-------------------+-------------+--------------------------------------|
- | <top-page> | H | move to the top of the page |
- |-------------------+-------------+--------------------------------------|
- | <next-entry> | j | move to the next entry |
- |-------------------+-------------+--------------------------------------|
- | <previous-entry> | k | move to the previous entry |
- |-------------------+-------------+--------------------------------------|
- | <bottom-page> | L | move to the bottom of the page |
- |-------------------+-------------+--------------------------------------|
- | <refresh> | ^L | clear and redraw the screen |
- |-------------------+-------------+--------------------------------------|
- | <middle-page> | M | move to the middle of the page |
- |-------------------+-------------+--------------------------------------|
- | <search-next> | n | search for next match |
- |-------------------+-------------+--------------------------------------|
- | <exit> | q | exit this menu |
- |-------------------+-------------+--------------------------------------|
- | <tag-entry> | t | tag the current entry |
- |-------------------+-------------+--------------------------------------|
- | <next-page> | z | move to the next page |
- |-------------------+-------------+--------------------------------------|
- | <previous-page> | Z | move to the previous page |
- |-------------------+-------------+--------------------------------------|
- | <last-entry> | * | move to the last entry |
- |-------------------+-------------+--------------------------------------|
- | <first-entry> | = | move to the first entry |
- |-------------------+-------------+--------------------------------------|
- | <enter-command> | : | enter a muttrc command |
- |-------------------+-------------+--------------------------------------|
- | <next-line> | > | scroll down one line |
- |-------------------+-------------+--------------------------------------|
- | <previous-line> | < | scroll up one line |
- |-------------------+-------------+--------------------------------------|
- | <half-up> | [ | scroll up 1/2 page |
- |-------------------+-------------+--------------------------------------|
- | <half-down> | ] | scroll down 1/2 page |
- |-------------------+-------------+--------------------------------------|
- | <help> | ? | this screen |
- |-------------------+-------------+--------------------------------------|
- | <tag-prefix> | ; | apply next function to tagged |
- | | | messages |
- |-------------------+-------------+--------------------------------------|
- | <tag-prefix-cond> | | apply next function ONLY to tagged |
- | | | messages |
- |-------------------+-------------+--------------------------------------|
- | <end-cond> | | end of conditional execution (noop) |
- |-------------------+-------------+--------------------------------------|
- | <shell-escape> | ! | invoke a command in a subshell |
- |-------------------+-------------+--------------------------------------|
- | <select-entry> | <Return> | select the current entry |
- |-------------------+-------------+--------------------------------------|
- | <search> | / | search for a regular expression |
- |-------------------+-------------+--------------------------------------|
- | <search-reverse> | Esc / | search backwards for a regular |
- | | | expression |
- |-------------------+-------------+--------------------------------------|
- | <search-opposite> | | search for next match in opposite |
- | | | direction |
- |-------------------+-------------+--------------------------------------|
- | <jump> | | jump to an index number |
- |-------------------+-------------+--------------------------------------|
- | <current-top> | | move entry to top of screen |
- |-------------------+-------------+--------------------------------------|
- | <current-middle> | | move entry to middle of screen |
- |-------------------+-------------+--------------------------------------|
- | <current-bottom> | | move entry to bottom of screen |
- |-------------------+-------------+--------------------------------------|
- | <what-key> | | display the keycode for a key press |
- +------------------------------------------------------------------------+
-
- 4.2. index menu
-
- Table 8.3. Default index function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |----------------------------+-------------+-----------------------------|
- | <create-alias> | a | create an alias from a |
- | | | message sender |
- |----------------------------+-------------+-----------------------------|
- | <bounce-message> | b | remail a message to another |
- | | | user |
- |----------------------------+-------------+-----------------------------|
- | <break-thread> | # | break the thread in two |
- |----------------------------+-------------+-----------------------------|
- | <change-folder> | c | open a different folder |
- |----------------------------+-------------+-----------------------------|
- | <change-folder-readonly> | Esc c | open a different folder in |
- | | | read only mode |
- |----------------------------+-------------+-----------------------------|
- | <next-unread-mailbox> | | open next mailbox with new |
- | | | mail |
- |----------------------------+-------------+-----------------------------|
- | <collapse-thread> | Esc v | collapse/uncollapse current |
- | | | thread |
- |----------------------------+-------------+-----------------------------|
- | <collapse-all> | Esc V | collapse/uncollapse all |
- | | | threads |
- |----------------------------+-------------+-----------------------------|
- | <copy-message> | C | copy a message to a |
- | | | file/mailbox |
- |----------------------------+-------------+-----------------------------|
- | <decode-copy> | Esc C | make decoded (text/plain) |
- | | | copy |
- |----------------------------+-------------+-----------------------------|
- | <decode-save> | Esc s | make decoded copy |
- | | | (text/plain) and delete |
- |----------------------------+-------------+-----------------------------|
- | <delete-message> | d | delete the current entry |
- |----------------------------+-------------+-----------------------------|
- | <delete-pattern> | D | delete messages matching a |
- | | | pattern |
- |----------------------------+-------------+-----------------------------|
- | <delete-thread> | ^D | delete all messages in |
- | | | thread |
- |----------------------------+-------------+-----------------------------|
- | <delete-subthread> | Esc d | delete all messages in |
- | | | subthread |
- |----------------------------+-------------+-----------------------------|
- | <edit> | e | edit the raw message |
- |----------------------------+-------------+-----------------------------|
- | <edit-type> | ^E | edit attachment content |
- | | | type |
- |----------------------------+-------------+-----------------------------|
- | <forward-message> | f | forward a message with |
- | | | comments |
- |----------------------------+-------------+-----------------------------|
- | <flag-message> | F | toggle a message's |
- | | | 'important' flag |
- |----------------------------+-------------+-----------------------------|
- | <group-reply> | g | reply to all recipients |
- |----------------------------+-------------+-----------------------------|
- | <fetch-mail> | G | retrieve mail from POP |
- | | | server |
- |----------------------------+-------------+-----------------------------|
- | <imap-fetch-mail> | | force retrieval of mail |
- | | | from IMAP server |
- |----------------------------+-------------+-----------------------------|
- | <display-toggle-weed> | h | display message and toggle |
- | | | header weeding |
- |----------------------------+-------------+-----------------------------|
- | <next-undeleted> | j | move to the next undeleted |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <previous-undeleted> | k | move to the previous |
- | | | undeleted message |
- |----------------------------+-------------+-----------------------------|
- | <limit> | l | show only messages matching |
- | | | a pattern |
- |----------------------------+-------------+-----------------------------|
- | <link-threads> | & | link tagged message to the |
- | | | current one |
- |----------------------------+-------------+-----------------------------|
- | <list-reply> | L | reply to specified mailing |
- | | | list |
- |----------------------------+-------------+-----------------------------|
- | <mail> | m | compose a new mail message |
- |----------------------------+-------------+-----------------------------|
- | <toggle-new> | N | toggle a message's 'new' |
- | | | flag |
- |----------------------------+-------------+-----------------------------|
- | <toggle-write> | % | toggle whether the mailbox |
- | | | will be rewritten |
- |----------------------------+-------------+-----------------------------|
- | <next-thread> | ^N | jump to the next thread |
- |----------------------------+-------------+-----------------------------|
- | <next-subthread> | Esc n | jump to the next subthread |
- |----------------------------+-------------+-----------------------------|
- | | | really delete the current |
- | <purge-message> | | entry, bypassing the trash |
- | | | folder |
- |----------------------------+-------------+-----------------------------|
- | <query> | Q | query external program for |
- | | | addresses |
- |----------------------------+-------------+-----------------------------|
- | <quit> | q | save changes to mailbox and |
- | | | quit |
- |----------------------------+-------------+-----------------------------|
- | <reply> | r | reply to a message |
- |----------------------------+-------------+-----------------------------|
- | <show-limit> | Esc l | show currently active limit |
- | | | pattern |
- |----------------------------+-------------+-----------------------------|
- | <sort-mailbox> | o | sort messages |
- |----------------------------+-------------+-----------------------------|
- | <sort-reverse> | O | sort messages in reverse |
- | | | order |
- |----------------------------+-------------+-----------------------------|
- | <print-message> | p | print the current entry |
- |----------------------------+-------------+-----------------------------|
- | <previous-thread> | ^P | jump to previous thread |
- |----------------------------+-------------+-----------------------------|
- | <previous-subthread> | Esc p | jump to previous subthread |
- |----------------------------+-------------+-----------------------------|
- | <recall-message> | R | recall a postponed message |
- |----------------------------+-------------+-----------------------------|
- | <read-thread> | ^R | mark the current thread as |
- | | | read |
- |----------------------------+-------------+-----------------------------|
- | <read-subthread> | Esc r | mark the current subthread |
- | | | as read |
- |----------------------------+-------------+-----------------------------|
- | <resend-message> | Esc e | use the current message as |
- | | | a template for a new one |
- |----------------------------+-------------+-----------------------------|
- | <save-message> | s | save message/attachment to |
- | | | a file |
- |----------------------------+-------------+-----------------------------|
- | <tag-pattern> | T | tag messages matching a |
- | | | pattern |
- |----------------------------+-------------+-----------------------------|
- | <tag-subthread> | | tag the current subthread |
- |----------------------------+-------------+-----------------------------|
- | <tag-thread> | Esc t | tag the current thread |
- |----------------------------+-------------+-----------------------------|
- | <untag-pattern> | ^T | untag messages matching a |
- | | | pattern |
- |----------------------------+-------------+-----------------------------|
- | <undelete-message> | u | undelete the current entry |
- |----------------------------+-------------+-----------------------------|
- | <undelete-pattern> | U | undelete messages matching |
- | | | a pattern |
- |----------------------------+-------------+-----------------------------|
- | <undelete-subthread> | Esc u | undelete all messages in |
- | | | subthread |
- |----------------------------+-------------+-----------------------------|
- | <undelete-thread> | ^U | undelete all messages in |
- | | | thread |
- |----------------------------+-------------+-----------------------------|
- | <view-attachments> | v | show MIME attachments |
- |----------------------------+-------------+-----------------------------|
- | <show-version> | V | show the Mutt version |
- | | | number and date |
- |----------------------------+-------------+-----------------------------|
- | <set-flag> | w | set a status flag on a |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <clear-flag> | W | clear a status flag from a |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <display-message> | <Return> | display a message |
- |----------------------------+-------------+-----------------------------|
- | <buffy-list> | . | list mailboxes with new |
- | | | mail |
- |----------------------------+-------------+-----------------------------|
- | <sync-mailbox> | $ | save changes to mailbox |
- |----------------------------+-------------+-----------------------------|
- | <display-address> | @ | display full address of |
- | | | sender |
- |----------------------------+-------------+-----------------------------|
- | <pipe-message> | | | pipe message/attachment to |
- | | | a shell command |
- |----------------------------+-------------+-----------------------------|
- | <next-new> | | jump to the next new |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <next-new-then-unread> | <Tab> | jump to the next new or |
- | | | unread message |
- |----------------------------+-------------+-----------------------------|
- | <previous-new> | | jump to the previous new |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <previous-new-then-unread> | Esc <Tab> | jump to the previous new or |
- | | | unread message |
- |----------------------------+-------------+-----------------------------|
- | <next-unread> | | jump to the next unread |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <previous-unread> | | jump to the previous unread |
- | | | message |
- |----------------------------+-------------+-----------------------------|
- | <parent-message> | P | jump to parent message in |
- | | | thread |
- |----------------------------+-------------+-----------------------------|
- | <extract-keys> | ^K | extract supported public |
- | | | keys |
- |----------------------------+-------------+-----------------------------|
- | <forget-passphrase> | ^F | wipe passphrase(s) from |
- | | | memory |
- |----------------------------+-------------+-----------------------------|
- | <check-traditional-pgp> | Esc P | check for classic PGP |
- |----------------------------+-------------+-----------------------------|
- | <mail-key> | Esc k | mail a PGP public key |
- |----------------------------+-------------+-----------------------------|
- | <decrypt-copy> | | make decrypted copy |
- |----------------------------+-------------+-----------------------------|
- | <decrypt-save> | | make decrypted copy and |
- | | | delete |
- +------------------------------------------------------------------------+
-
- 4.3. pager menu
-
- Table 8.4. Default pager function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |--------------------------+-------------+-------------------------------|
- | <break-thread> | # | break the thread in two |
- |--------------------------+-------------+-------------------------------|
- | <create-alias> | a | create an alias from a |
- | | | message sender |
- |--------------------------+-------------+-------------------------------|
- | <bounce-message> | b | remail a message to another |
- | | | user |
- |--------------------------+-------------+-------------------------------|
- | <change-folder> | c | open a different folder |
- |--------------------------+-------------+-------------------------------|
- | <change-folder-readonly> | Esc c | open a different folder in |
- | | | read only mode |
- |--------------------------+-------------+-------------------------------|
- | <next-unread-mailbox> | | open next mailbox with new |
- | | | mail |
- |--------------------------+-------------+-------------------------------|
- | <copy-message> | C | copy a message to a |
- | | | file/mailbox |
- |--------------------------+-------------+-------------------------------|
- | <decode-copy> | Esc C | make decoded (text/plain) |
- | | | copy |
- |--------------------------+-------------+-------------------------------|
- | <delete-message> | d | delete the current entry |
- |--------------------------+-------------+-------------------------------|
- | <delete-thread> | ^D | delete all messages in thread |
- |--------------------------+-------------+-------------------------------|
- | <delete-subthread> | Esc d | delete all messages in |
- | | | subthread |
- |--------------------------+-------------+-------------------------------|
- | <edit> | e | edit the raw message |
- |--------------------------+-------------+-------------------------------|
- | <edit-type> | ^E | edit attachment content type |
- |--------------------------+-------------+-------------------------------|
- | <forward-message> | f | forward a message with |
- | | | comments |
- |--------------------------+-------------+-------------------------------|
- | <flag-message> | F | toggle a message's |
- | | | 'important' flag |
- |--------------------------+-------------+-------------------------------|
- | <group-reply> | g | reply to all recipients |
- |--------------------------+-------------+-------------------------------|
- | <imap-fetch-mail> | | force retrieval of mail from |
- | | | IMAP server |
- |--------------------------+-------------+-------------------------------|
- | <display-toggle-weed> | h | display message and toggle |
- | | | header weeding |
- |--------------------------+-------------+-------------------------------|
- | <next-undeleted> | j | move to the next undeleted |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <next-entry> | J | move to the next entry |
- |--------------------------+-------------+-------------------------------|
- | <previous-undeleted> | k | move to the previous |
- | | | undeleted message |
- |--------------------------+-------------+-------------------------------|
- | <previous-entry> | K | move to the previous entry |
- |--------------------------+-------------+-------------------------------|
- | <link-threads> | & | link tagged message to the |
- | | | current one |
- |--------------------------+-------------+-------------------------------|
- | <list-reply> | L | reply to specified mailing |
- | | | list |
- |--------------------------+-------------+-------------------------------|
- | <redraw-screen> | ^L | clear and redraw the screen |
- |--------------------------+-------------+-------------------------------|
- | <mail> | m | compose a new mail message |
- |--------------------------+-------------+-------------------------------|
- | <mark-as-new> | N | toggle a message's 'new' flag |
- |--------------------------+-------------+-------------------------------|
- | <search-next> | n | search for next match |
- |--------------------------+-------------+-------------------------------|
- | <next-thread> | ^N | jump to the next thread |
- |--------------------------+-------------+-------------------------------|
- | <next-subthread> | Esc n | jump to the next subthread |
- |--------------------------+-------------+-------------------------------|
- | <print-message> | p | print the current entry |
- |--------------------------+-------------+-------------------------------|
- | <previous-thread> | ^P | jump to previous thread |
- |--------------------------+-------------+-------------------------------|
- | <previous-subthread> | Esc p | jump to previous subthread |
- |--------------------------+-------------+-------------------------------|
- | | | really delete the current |
- | <purge-message> | | entry, bypassing the trash |
- | | | folder |
- |--------------------------+-------------+-------------------------------|
- | <quit> | Q | save changes to mailbox and |
- | | | quit |
- |--------------------------+-------------+-------------------------------|
- | <exit> | q | exit this menu |
- |--------------------------+-------------+-------------------------------|
- | <reply> | r | reply to a message |
- |--------------------------+-------------+-------------------------------|
- | <recall-message> | R | recall a postponed message |
- |--------------------------+-------------+-------------------------------|
- | <read-thread> | ^R | mark the current thread as |
- | | | read |
- |--------------------------+-------------+-------------------------------|
- | <read-subthread> | Esc r | mark the current subthread as |
- | | | read |
- |--------------------------+-------------+-------------------------------|
- | <resend-message> | Esc e | use the current message as a |
- | | | template for a new one |
- |--------------------------+-------------+-------------------------------|
- | <save-message> | s | save message/attachment to a |
- | | | file |
- |--------------------------+-------------+-------------------------------|
- | <skip-quoted> | S | skip beyond quoted text |
- |--------------------------+-------------+-------------------------------|
- | <decode-save> | Esc s | make decoded copy |
- | | | (text/plain) and delete |
- |--------------------------+-------------+-------------------------------|
- | <tag-message> | t | tag the current entry |
- |--------------------------+-------------+-------------------------------|
- | <toggle-quoted> | T | toggle display of quoted text |
- |--------------------------+-------------+-------------------------------|
- | <undelete-message> | u | undelete the current entry |
- |--------------------------+-------------+-------------------------------|
- | <undelete-subthread> | Esc u | undelete all messages in |
- | | | subthread |
- |--------------------------+-------------+-------------------------------|
- | <undelete-thread> | ^U | undelete all messages in |
- | | | thread |
- |--------------------------+-------------+-------------------------------|
- | <view-attachments> | v | show MIME attachments |
- |--------------------------+-------------+-------------------------------|
- | <show-version> | V | show the Mutt version number |
- | | | and date |
- |--------------------------+-------------+-------------------------------|
- | <search-toggle> | \\ | toggle search pattern |
- | | | coloring |
- |--------------------------+-------------+-------------------------------|
- | <display-address> | @ | display full address of |
- | | | sender |
- |--------------------------+-------------+-------------------------------|
- | <next-new> | | jump to the next new message |
- |--------------------------+-------------+-------------------------------|
- | <pipe-message> | | | pipe message/attachment to a |
- | | | shell command |
- |--------------------------+-------------+-------------------------------|
- | <help> | ? | this screen |
- |--------------------------+-------------+-------------------------------|
- | <next-page> | <Space> | move to the next page |
- |--------------------------+-------------+-------------------------------|
- | <previous-page> | - | move to the previous page |
- |--------------------------+-------------+-------------------------------|
- | <top> | ^ | jump to the top of the |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <sync-mailbox> | $ | save changes to mailbox |
- |--------------------------+-------------+-------------------------------|
- | <shell-escape> | ! | invoke a command in a |
- | | | subshell |
- |--------------------------+-------------+-------------------------------|
- | <enter-command> | : | enter a muttrc command |
- |--------------------------+-------------+-------------------------------|
- | <buffy-list> | . | list mailboxes with new mail |
- |--------------------------+-------------+-------------------------------|
- | <search> | / | search for a regular |
- | | | expression |
- |--------------------------+-------------+-------------------------------|
- | <search-reverse> | Esc / | search backwards for a |
- | | | regular expression |
- |--------------------------+-------------+-------------------------------|
- | <search-opposite> | | search for next match in |
- | | | opposite direction |
- |--------------------------+-------------+-------------------------------|
- | <next-line> | <Return> | scroll down one line |
- |--------------------------+-------------+-------------------------------|
- | <jump> | | jump to an index number |
- |--------------------------+-------------+-------------------------------|
- | <next-unread> | | jump to the next unread |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <previous-new> | | jump to the previous new |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <previous-unread> | | jump to the previous unread |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <half-up> | | scroll up 1/2 page |
- |--------------------------+-------------+-------------------------------|
- | <half-down> | | scroll down 1/2 page |
- |--------------------------+-------------+-------------------------------|
- | <previous-line> | | scroll up one line |
- |--------------------------+-------------+-------------------------------|
- | <bottom> | | jump to the bottom of the |
- | | | message |
- |--------------------------+-------------+-------------------------------|
- | <parent-message> | P | jump to parent message in |
- | | | thread |
- |--------------------------+-------------+-------------------------------|
- | <check-traditional-pgp> | Esc P | check for classic PGP |
- |--------------------------+-------------+-------------------------------|
- | <mail-key> | Esc k | mail a PGP public key |
- |--------------------------+-------------+-------------------------------|
- | <extract-keys> | ^K | extract supported public keys |
- |--------------------------+-------------+-------------------------------|
- | <forget-passphrase> | ^F | wipe passphrase(s) from |
- | | | memory |
- |--------------------------+-------------+-------------------------------|
- | <decrypt-copy> | | make decrypted copy |
- |--------------------------+-------------+-------------------------------|
- | <decrypt-save> | | make decrypted copy and |
- | | | delete |
- |--------------------------+-------------+-------------------------------|
- | <what-key> | | display the keycode for a key |
- | | | press |
- +------------------------------------------------------------------------+
-
- 4.4. alias menu
-
- Table 8.5. Default alias function bindings
-
- +-------------------------------------------------------------+
- | Function | Default key | Description |
- |------------------+-------------+----------------------------|
- | <delete-entry> | d | delete the current entry |
- |------------------+-------------+----------------------------|
- | <undelete-entry> | u | undelete the current entry |
- +-------------------------------------------------------------+
-
- 4.5. query menu
-
- Table 8.6. Default query 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 |
- +------------------------------------------------------------------------+
-
- 4.6. attach menu
-
- Table 8.7. Default attach function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |-------------------------+-------------+--------------------------------|
- | <bounce-message> | b | remail a message to another |
- | | | user |
- |-------------------------+-------------+--------------------------------|
- | <display-toggle-weed> | h | display message and toggle |
- | | | header weeding |
- |-------------------------+-------------+--------------------------------|
- | <edit-type> | ^E | edit attachment content type |
- |-------------------------+-------------+--------------------------------|
- | <print-entry> | p | print the current entry |
- |-------------------------+-------------+--------------------------------|
- | <save-entry> | s | save message/attachment to a |
- | | | file |
- |-------------------------+-------------+--------------------------------|
- | <pipe-entry> | | | pipe message/attachment to a |
- | | | shell command |
- |-------------------------+-------------+--------------------------------|
- | <view-mailcap> | m | force viewing of attachment |
- | | | using mailcap |
- |-------------------------+-------------+--------------------------------|
- | <reply> | r | reply to a message |
- |-------------------------+-------------+--------------------------------|
- | <resend-message> | Esc e | use the current message as a |
- | | | template for a new one |
- |-------------------------+-------------+--------------------------------|
- | <group-reply> | g | reply to all recipients |
- |-------------------------+-------------+--------------------------------|
- | <list-reply> | L | reply to specified mailing |
- | | | list |
- |-------------------------+-------------+--------------------------------|
- | <forward-message> | f | forward a message with |
- | | | comments |
- |-------------------------+-------------+--------------------------------|
- | <view-text> | T | view attachment as text |
- |-------------------------+-------------+--------------------------------|
- | <view-attach> | <Return> | view attachment using mailcap |
- | | | entry if necessary |
- |-------------------------+-------------+--------------------------------|
- | <delete-entry> | d | delete the current entry |
- |-------------------------+-------------+--------------------------------|
- | <undelete-entry> | u | undelete the current entry |
- |-------------------------+-------------+--------------------------------|
- | <collapse-parts> | v | Toggle display of subparts |
- |-------------------------+-------------+--------------------------------|
- | <check-traditional-pgp> | Esc P | check for classic PGP |
- |-------------------------+-------------+--------------------------------|
- | <extract-keys> | ^K | extract supported public keys |
- |-------------------------+-------------+--------------------------------|
- | <forget-passphrase> | ^F | wipe passphrase(s) from memory |
- +------------------------------------------------------------------------+
-
- 4.7. compose menu
-
- Table 8.8. Default compose function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |-----------------------+-------------+----------------------------------|
- | <attach-file> | a | attach file(s) to this message |
- |-----------------------+-------------+----------------------------------|
- | <attach-message> | A | attach message(s) to this |
- | | | message |
- |-----------------------+-------------+----------------------------------|
- | <edit-bcc> | b | edit the BCC list |
- |-----------------------+-------------+----------------------------------|
- | <edit-cc> | c | edit the CC list |
- |-----------------------+-------------+----------------------------------|
- | <copy-file> | C | save message/attachment to a |
- | | | file |
- |-----------------------+-------------+----------------------------------|
- | <detach-file> | D | delete the current entry |
- |-----------------------+-------------+----------------------------------|
- | <toggle-disposition> | ^D | toggle disposition between |
- | | | inline/attachment |
- |-----------------------+-------------+----------------------------------|
- | <edit-description> | d | edit attachment description |
- |-----------------------+-------------+----------------------------------|
- | <edit-message> | e | edit the message |
- |-----------------------+-------------+----------------------------------|
- | <edit-headers> | E | edit the message with headers |
- |-----------------------+-------------+----------------------------------|
- | <edit-file> | ^X e | edit the file to be attached |
- |-----------------------+-------------+----------------------------------|
- | <edit-encoding> | ^E | edit attachment |
- | | | transfer-encoding |
- |-----------------------+-------------+----------------------------------|
- | <edit-from> | Esc f | edit the from field |
- |-----------------------+-------------+----------------------------------|
- | <edit-fcc> | f | enter a file to save a copy of |
- | | | this message in |
- |-----------------------+-------------+----------------------------------|
- | <filter-entry> | F | filter attachment through a |
- | | | shell command |
- |-----------------------+-------------+----------------------------------|
- | <get-attachment> | G | get a temporary copy of an |
- | | | attachment |
- |-----------------------+-------------+----------------------------------|
- | <display-toggle-weed> | h | display message and toggle |
- | | | header weeding |
- |-----------------------+-------------+----------------------------------|
- | <ispell> | i | run ispell on the message |
- |-----------------------+-------------+----------------------------------|
- | <print-entry> | l | print the current entry |
- |-----------------------+-------------+----------------------------------|
- | <edit-mime> | m | edit attachment using mailcap |
- | | | entry |
- |-----------------------+-------------+----------------------------------|
- | <new-mime> | n | compose new attachment using |
- | | | mailcap entry |
- |-----------------------+-------------+----------------------------------|
- | <postpone-message> | P | save this message to send later |
- |-----------------------+-------------+----------------------------------|
- | <edit-reply-to> | r | edit the Reply-To field |
- |-----------------------+-------------+----------------------------------|
- | <rename-file> | R | rename/move an attached file |
- |-----------------------+-------------+----------------------------------|
- | <edit-subject> | s | edit the subject of this message |
- |-----------------------+-------------+----------------------------------|
- | <edit-to> | t | edit the TO list |
- |-----------------------+-------------+----------------------------------|
- | <edit-type> | ^T | edit attachment content type |
- |-----------------------+-------------+----------------------------------|
- | <write-fcc> | w | write the message to a folder |
- |-----------------------+-------------+----------------------------------|
- | <toggle-unlink> | u | toggle whether to delete file |
- | | | after sending it |
- |-----------------------+-------------+----------------------------------|
- | <toggle-recode> | | toggle recoding of this |
- | | | attachment |
- |-----------------------+-------------+----------------------------------|
- | <update-encoding> | U | update an attachment's encoding |
- | | | info |
- |-----------------------+-------------+----------------------------------|
- | <view-attach> | <Return> | view attachment using mailcap |
- | | | entry if necessary |
- |-----------------------+-------------+----------------------------------|
- | <send-message> | y | send the message |
- |-----------------------+-------------+----------------------------------|
- | <pipe-entry> | | | pipe message/attachment to a |
- | | | shell command |
- |-----------------------+-------------+----------------------------------|
- | <attach-key> | Esc k | attach a PGP public key |
- |-----------------------+-------------+----------------------------------|
- | <pgp-menu> | p | show PGP options |
- |-----------------------+-------------+----------------------------------|
- | <forget-passphrase> | ^F | wipe passphrase(s) from memory |
- |-----------------------+-------------+----------------------------------|
- | <smime-menu> | S | show S/MIME options |
- |-----------------------+-------------+----------------------------------|
- | <mix> | M | send the message through a |
- | | | mixmaster remailer chain |
- +------------------------------------------------------------------------+
-
- 4.8. postpone menu
-
- Table 8.9. Default postpone function bindings
-
- +-------------------------------------------------------------+
- | Function | Default key | Description |
- |------------------+-------------+----------------------------|
- | <delete-entry> | d | delete the current entry |
- |------------------+-------------+----------------------------|
- | <undelete-entry> | u | undelete the current entry |
- +-------------------------------------------------------------+
-
- 4.9. browser menu
-
- Table 8.10. Default browser function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |---------------------+-------------+------------------------------------|
- | <change-dir> | c | change directories |
- |---------------------+-------------+------------------------------------|
- | <display-filename> | @ | display the currently selected |
- | | | file's name |
- |---------------------+-------------+------------------------------------|
- | <enter-mask> | m | enter a file mask |
- |---------------------+-------------+------------------------------------|
- | <sort> | o | sort messages |
- |---------------------+-------------+------------------------------------|
- | <sort-reverse> | O | sort messages in reverse order |
- |---------------------+-------------+------------------------------------|
- | <select-new> | N | select a new file in this |
- | | | directory |
- |---------------------+-------------+------------------------------------|
- | <check-new> | | check mailboxes for new mail |
- |---------------------+-------------+------------------------------------|
- | <toggle-mailboxes> | <Tab> | toggle whether to browse mailboxes |
- | | | or all files |
- |---------------------+-------------+------------------------------------|
- | <view-file> | <Space> | view file |
- |---------------------+-------------+------------------------------------|
- | <buffy-list> | . | list mailboxes with new mail |
- |---------------------+-------------+------------------------------------|
- | <create-mailbox> | C | create a new mailbox (IMAP only) |
- |---------------------+-------------+------------------------------------|
- | <delete-mailbox> | d | delete the current mailbox (IMAP |
- | | | only) |
- |---------------------+-------------+------------------------------------|
- | <rename-mailbox> | r | rename the current mailbox (IMAP |
- | | | only) |
- |---------------------+-------------+------------------------------------|
- | <subscribe> | s | subscribe to current mailbox (IMAP |
- | | | only) |
- |---------------------+-------------+------------------------------------|
- | <unsubscribe> | u | unsubscribe from current mailbox |
- | | | (IMAP only) |
- |---------------------+-------------+------------------------------------|
- | <toggle-subscribed> | T | toggle view all/subscribed |
- | | | mailboxes (IMAP only) |
- +------------------------------------------------------------------------+
-
- 4.10. pgp menu
-
- Table 8.11. Default pgp function bindings
-
- +------------------------------------------------------+
- | Function | Default key | Description |
- |--------------+-------------+-------------------------|
- | <verify-key> | c | verify a PGP public key |
- |--------------+-------------+-------------------------|
- | <view-name> | % | view the key's user id |
- +------------------------------------------------------+
-
- 4.11. smime menu
-
- Table 8.12. Default smime function bindings
-
- +------------------------------------------------------+
- | Function | Default key | Description |
- |--------------+-------------+-------------------------|
- | <verify-key> | c | verify a PGP public key |
- |--------------+-------------+-------------------------|
- | <view-name> | % | view the key's user id |
- +------------------------------------------------------+
-
- 4.12. mix menu
-
- Table 8.13. Default mix function bindings
-
- +-----------------------------------------------------------------------+
- | Function | Default key | Description |
- |--------------+-------------+------------------------------------------|
- | <accept> | <Return> | Accept the chain constructed |
- |--------------+-------------+------------------------------------------|
- | <append> | a | Append a remailer to the chain |
- |--------------+-------------+------------------------------------------|
- | <insert> | i | Insert a remailer into the chain |
- |--------------+-------------+------------------------------------------|
- | <delete> | d | Delete a remailer from the chain |
- |--------------+-------------+------------------------------------------|
- | <chain-prev> | <Left> | Select the previous element of the chain |
- |--------------+-------------+------------------------------------------|
- | <chain-next> | <Right> | Select the next element of the chain |
- +-----------------------------------------------------------------------+
-
- 4.13. editor menu
-
- Table 8.14. Default editor function bindings
-
- +------------------------------------------------------------------------+
- | Function | Default key | Description |
- |-------------------+-------------+--------------------------------------|
- | <bol> | ^A | jump to the beginning of the line |
- |-------------------+-------------+--------------------------------------|
- | <backward-char> | ^B | move the cursor one character to the |
- | | | left |
- |-------------------+-------------+--------------------------------------|
- | <backward-word> | Esc b | move the cursor to the beginning of |
- | | | the word |
- |-------------------+-------------+--------------------------------------|
- | <capitalize-word> | Esc c | capitalize the word |
- |-------------------+-------------+--------------------------------------|
- | <downcase-word> | Esc l | convert the word to lower case |
- |-------------------+-------------+--------------------------------------|
- | <upcase-word> | Esc u | convert the word to upper case |
- |-------------------+-------------+--------------------------------------|
- | <delete-char> | ^D | delete the char under the cursor |
- |-------------------+-------------+--------------------------------------|
- | <eol> | ^E | jump to the end of the line |
- |-------------------+-------------+--------------------------------------|
- | <forward-char> | ^F | move the cursor one character to the |
- | | | right |
- |-------------------+-------------+--------------------------------------|
- | <forward-word> | Esc f | move the cursor to the end of the |
- | | | word |
- |-------------------+-------------+--------------------------------------|
- | <backspace> | <Backspace> | delete the char in front of the |
- | | | cursor |
- |-------------------+-------------+--------------------------------------|
- | <kill-eol> | ^K | delete chars from cursor to end of |
- | | | line |
- |-------------------+-------------+--------------------------------------|
- | <kill-eow> | Esc d | delete chars from the cursor to the |
- | | | end of the word |
- |-------------------+-------------+--------------------------------------|
- | <kill-line> | ^U | delete all chars on the line |
- |-------------------+-------------+--------------------------------------|
- | <quote-char> | ^V | quote the next typed key |
- |-------------------+-------------+--------------------------------------|
- | <kill-word> | ^W | delete the word in front of the |
- | | | cursor |
- |-------------------+-------------+--------------------------------------|
- | <complete> | <Tab> | complete filename or alias |
- |-------------------+-------------+--------------------------------------|
- | <complete-query> | ^T | complete address with query |
- |-------------------+-------------+--------------------------------------|
- | <buffy-cycle> | <Space> | cycle among incoming mailboxes |
- |-------------------+-------------+--------------------------------------|
- | <history-up> | | scroll up through the history list |
- |-------------------+-------------+--------------------------------------|
- | <history-down> | | scroll down through the history list |
- |-------------------+-------------+--------------------------------------|
- | <transpose-chars> | | transpose character under cursor |
- | | | with previous |
- +------------------------------------------------------------------------+
-
-Chapter 9. Miscellany
-
- Table of Contents
-
- 1. Acknowledgements
-
- 2. About this document
-
-1. Acknowledgements
-
- 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:
-
- 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 Bjo: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 Ma:kela: <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 Rocco Rutte <pdmef@gmx.net>
-
- 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>
-
-2. About this document
-
- This document was written in DocBook, and then rendered using the Gnome
- XSLT toolkit.
+++ /dev/null
-<?xml version="1.0" standalone="no"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
-<book>
-
-<bookinfo>
-<title>The Mutt E-Mail Client</title>
-<author>
-<firstname>Michael</firstname><surname>Elkins</surname>
-<email>me@cs.hmc.edu</email>
-</author>
-<releaseinfo>version 1.5.19 (2009-01-05)</releaseinfo>
-
-<abstract>
-<para>
-<quote>All mail clients suck. This one just sucks less.</quote> -me, circa 1995
-</para>
-</abstract>
-</bookinfo>
-
-<chapter id="intro">
-<title>Introduction</title>
-
-<para>
-<emphasis role="bold">Mutt</emphasis> is a small but very powerful text-based MIME mail client. Mutt 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.
-</para>
-
-<sect1 id="homepage">
-<title>Mutt Home Page</title>
-
-<para>
-The official homepage can be found at
-<ulink url="http://www.mutt.org/">http://www.mutt.org/</ulink>.
-</para>
-
-</sect1>
-
-<sect1 id="muttlists">
-<title>Mailing Lists</title>
-
-<para>
-To subscribe to one of the following mailing lists, send a message with the
-word <emphasis>subscribe</emphasis> in the body to
-<literal>list-name</literal><emphasis>-request</emphasis><literal>@mutt.org</literal>.
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-<email>mutt-announce-request@mutt.org</email> -- low traffic list for announcements
-</para>
-</listitem>
-<listitem>
-
-<para>
-<email>mutt-users-request@mutt.org</email> -- help, bug reports and feature requests
-</para>
-</listitem>
-<listitem>
-
-<para>
-<email>mutt-dev-request@mutt.org</email> -- development mailing list
-</para>
-</listitem>
-
-</itemizedlist>
-
-<note>
-<para>
-All messages posted to
-<emphasis>mutt-announce</emphasis> are automatically forwarded to
-<emphasis>mutt-users</emphasis>, so you do not need to be subscribed to
-both lists.
-</para>
-</note>
-
-</sect1>
-
-<sect1 id="distribution">
-<title>Software Distribution Sites</title>
-
-<para>
-Mutt releases can be downloaded from
-<ulink url="ftp://ftp.mutt.org/mutt/">ftp://ftp.mutt.org/mutt/</ulink>.
-For a list of mirror sites, please refer to
-<ulink url="http://www.mutt.org/download.html">http://www.mutt.org/download.html</ulink>.
-</para>
-
-</sect1>
-
-<sect1 id="irc">
-<title>Mutt online resources</title>
-
-<variablelist>
-
-<varlistentry>
-<term>Bug Tracking System</term>
-<listitem>
-<para>
-The official mutt bug tracking system can be found at
-<ulink url="http://dev.mutt.org/">http://dev.mutt.org/</ulink>
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>Wiki</term>
-<listitem>
-<para>
-An (unofficial) wiki can be found
-at <ulink url="http://wiki.mutt.org/">http://wiki.mutt.org/</ulink>.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>IRC</term>
-<listitem>
-<para>
-For the IRC user community, visit channel <emphasis>#mutt</emphasis> on
-<ulink url="http://www.freenode.net/">irc.freenode.net</ulink>.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>USENET</term>
-<listitem>
-<para>
-For USENET, see the newsgroup <ulink url="news:comp.mail.mutt">comp.mail.mutt</ulink>.
-</para>
-</listitem>
-</varlistentry>
-
-</variablelist>
-
-</sect1>
-
-<sect1 id="contrib">
-<title>Contributing to Mutt</title>
-
-<para>
-There are various ways to contribute to the Mutt project.
-</para>
-
-<para>
-Especially for new users it may be helpful to meet other new and
-experienced users to chat about Mutt, talk about problems and share
-tricks.
-</para>
-
-<para>
-Since translations of Mutt into other languages are highly appreciated,
-the mutt developers always look for skilled translators that help
-improve and continue to maintain stale translations.
-</para>
-
-<para>
-For contributing code patches for new features and bug fixes, please
-refer to the developer pages at
-<ulink url="http://dev.mutt.org/">http://dev.mutt.org/</ulink> for more details.
-</para>
-
-</sect1>
-
-<sect1 id="typo">
-<title>Typograhical conventions</title>
-
-<para>
-This section lists typographical conventions followed throughout this
-manual. See table <xref linkend="tab-typo"/> for typographical
-conventions for special terms.
-</para>
-
-<table id="tab-typo">
-<title>Typographical conventions for special terms</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Item</entry><entry>Refers to...</entry></row>
-</thead>
-<tbody>
-<row><entry><literal>printf(3)</literal></entry><entry>UNIX manual pages, execute <literal>man 3 printf</literal></entry></row>
-<row><entry><literal><PageUp></literal></entry><entry>named keys</entry></row>
-<row><entry><literal><create-alias></literal></entry><entry>named Mutt function</entry></row>
-<row><entry><literal>ˆG</literal></entry><entry>Control+G key combination</entry></row>
-<row><entry><literal>$mail_check</literal></entry><entry>Mutt configuration option</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Examples are presented as:
-</para>
-
-<screen>
-mutt -v
-</screen>
-
-<para>
-Within command synopsis, curly brackets (<quote>{}</quote>) denote a set
-of options of which one is mandatory, square brackets
-(<quote>[]</quote>) denote optional arguments, three dots
-denote that the argument may be repeated arbitrary times.
-</para>
-
-</sect1>
-
-<sect1 id="copyright">
-<title>Copyright</title>
-
-<para>
-Mutt is Copyright (C) 1996-2009 Michael R. Elkins
-<email>me@mutt.org</email> and others.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-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.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="gettingstarted">
-<title>Getting Started</title>
-
-<para>
-This section is intended as a brief overview of how to use Mutt. There are
-many other features which are described elsewhere in the manual. There
-is even more information available in the Mutt FAQ and various web
-pages. See the <ulink url="http://www.mutt.org/">Mutt homepage</ulink> for more details.
-</para>
-
-<para>
-The keybindings described in this section are the defaults as distributed.
-Your local system administrator may have altered the defaults for your site.
-You can always type <quote>?</quote> in any menu to display the current bindings.
-</para>
-
-<para>
-The first thing you need to do is invoke mutt, simply by typing <literal>mutt</literal>
-at the command line. There are various command-line options, see
-either the mutt man page or the <link linkend="commandline">reference</link>.
-</para>
-
-<sect1 id="core-concepts">
-<title>Core concepts</title>
-
-<para>
-Mutt is a text-based application which interacts with users through
-different menus which are mostly line-/entry-based or page-based. A
-line-based menu is the so-called <quote>index</quote> menu (listing all messages of
-the currently opened folder) or the <quote>alias</quote> menu (allowing you to
-select recipients from a list). Examples for page-based menus are the
-<quote>pager</quote> (showing one message at a time) or the <quote>help</quote> menu listing
-all available key bindings.
-</para>
-
-<para>
-The user interface consists of a context sensitive help line at the top,
-the menu's contents followed by a context sensitive status line and
-finally the command line. The command line is used to display
-informational and error messages as well as for prompts and for entering
-interactive commands.
-</para>
-
-<para>
-Because Mutt allows for customizing almost all key bindings, there are
-so-called <quote>functions</quote> which can be executed manually (using the
-command line) or in macros. Macros allow the user to bind a sequence of
-commands to a single key or a short key sequence instead of repeating a
-sequence of actions over and over.
-</para>
-
-<para>
-Many commands (such as saving or copying a message to another folder)
-can be applied to a single message or a set of messages (so-called
-<quote>tagged</quote> messages). To help selecting messages, Mutt provides a rich
-set of message patterns (such as recipients, sender, body contents, date
-sent/received, etc.) which can be combined into complex expressions
-using the boolean <emphasis>and</emphasis> and <emphasis>or</emphasis>
-operations as well as negating. These patterns can also be used to (for
-example) search for messages or to limit the index to show only matching
-messages.
-</para>
-
-<para>
-Mutt supports a <quote>hook</quote> concept which allows the user to execute
-arbitrary configuration commands and functions in certain situations
-such as entering a folder, starting a new message or replying to an
-existing one. These hooks can be used to highly customize Mutt's
-behaviour including managing multiple identities, customizing the
-display for a folder or even implementing auto-archiving based on a
-per-folder basis and much more.
-</para>
-
-</sect1>
-
-<sect1 id="menus">
-<title>Moving Around in Menus</title>
-
-<para>
-The most important navigation keys common to all menus are shown in
-<xref linkend="tab-keys-nav"/>.
-</para>
-
-<table id="tab-keys-nav">
-<title>Most common navigation keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>j or <Down></entry><entry><literal><next-entry></literal></entry><entry>move to the next entry</entry></row>
-<row><entry>k or <Up></entry><entry><literal><previous-entry></literal></entry><entry>move to the previous entry</entry></row>
-<row><entry>z or <PageDn></entry><entry><literal><page-down></literal></entry><entry>go to the next page</entry></row>
-<row><entry>Z or <PageUp></entry><entry><literal><page-up></literal></entry><entry>go to the previous page</entry></row>
-<row><entry>= or <Home></entry><entry><literal><first-entry></literal></entry><entry>jump to the first entry</entry></row>
-<row><entry>* or <End></entry><entry><literal><last-entry></literal></entry><entry>jump to the last entry</entry></row>
-<row><entry>q</entry><entry><literal><quit></literal></entry><entry>exit the current menu</entry></row>
-<row><entry>?</entry><entry><literal><help></literal></entry><entry>list all keybindings for the current menu</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-</sect1>
-
-<sect1 id="editing">
-<title>Editing Input Fields</title>
-
-<sect2 id="editing-intro">
-<title>Introduction</title>
-
-<para>
-Mutt has a built-in line editor for inputting text, e.g. email
-addresses or filenames. The keys used to manipulate text input are
-very similar to those of Emacs. See <xref linkend="tab-keys-editor"/> for a full
-reference of available functions, their default key bindings, and
-short descriptions.
-</para>
-
-<table id="tab-keys-editor">
-<title>Most common line editor keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>ˆA or <Home></entry><entry><literal><bol></literal></entry><entry>move to the start of the line</entry></row>
-<row><entry>ˆB or <Left></entry><entry><literal><backward-char></literal></entry><entry>move back one char</entry></row>
-<row><entry>Esc B</entry><entry><literal><backward-word></literal></entry><entry>move back one word</entry></row>
-<row><entry>ˆD or <Delete></entry><entry><literal><delete-char></literal></entry><entry>delete the char under the cursor</entry></row>
-<row><entry>ˆE or <End></entry><entry><literal><eol></literal></entry><entry>move to the end of the line</entry></row>
-<row><entry>ˆF or <Right></entry><entry><literal><forward-char></literal></entry><entry>move forward one char</entry></row>
-<row><entry>Esc F</entry><entry><literal><forward-word></literal></entry><entry>move forward one word</entry></row>
-<row><entry><Tab></entry><entry><literal><complete></literal></entry><entry>complete filename or alias</entry></row>
-<row><entry>ˆT</entry><entry><literal><complete-query></literal></entry><entry>complete address with query</entry></row>
-<row><entry>ˆK</entry><entry><literal><kill-eol></literal></entry><entry>delete to the end of the line</entry></row>
-<row><entry>Esc d</entry><entry><literal><kill-eow></literal></entry><entry>delete to the end of the word</entry></row>
-<row><entry>ˆW</entry><entry><literal><kill-word></literal></entry><entry>kill the word in front of the cursor</entry></row>
-<row><entry>ˆU</entry><entry><literal><kill-line></literal></entry><entry>delete entire line</entry></row>
-<row><entry>ˆV</entry><entry><literal><quote-char></literal></entry><entry>quote the next typed key</entry></row>
-<row><entry><Up></entry><entry><literal><history-up></literal></entry><entry>recall previous string from history</entry></row>
-<row><entry><Down></entry><entry><literal><history-down></literal></entry><entry>recall next string from history</entry></row>
-<row><entry><BackSpace></entry><entry><literal><backspace></literal></entry><entry>kill the char in front of the cursor</entry></row>
-<row><entry>Esc u</entry><entry><literal><upcase-word></literal></entry><entry>convert word to upper case</entry></row>
-<row><entry>Esc l</entry><entry><literal><downcase-word></literal></entry><entry>convert word to lower case</entry></row>
-<row><entry>Esc c</entry><entry><literal><capitalize-word></literal></entry><entry>capitalize the word</entry></row>
-<row><entry>ˆG</entry><entry>n/a</entry><entry>abort</entry></row>
-<row><entry><Return></entry><entry>n/a</entry><entry>finish editing</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-You can remap the <emphasis>editor</emphasis> functions using the
-<link linkend="bind">bind</link> command. For example, to make
-the <Delete> key delete the character in front of
-the cursor rather than under, you could use:
-</para>
-
-<screen>
-bind editor <delete> backspace
-</screen>
-
-</sect2>
-
-<sect2 id="editing-history">
-<title>History</title>
-
-<para>
-Mutt maintains a history for the built-in editor. The number of items
-is controlled by the <link linkend="history">$history</link>
-variable and can be made persistent using an external file specified
-using <link linkend="history-file">$history_file</link>.
-You may cycle through them at an editor prompt by using the
-<literal><history-up></literal> and/or
-<literal><history-down></literal> commands.
-</para>
-
-<para>
-Mutt maintains several distinct history lists, one for each of the
-following categories:
-</para>
-
-<itemizedlist>
-<listitem><para>muttrc commands</para></listitem>
-<listitem><para>addresses and aliases</para></listitem>
-<listitem><para>shell commands</para></listitem>
-<listitem><para>filenames</para></listitem>
-<listitem><para>patterns</para></listitem>
-<listitem><para>everything else</para></listitem>
-</itemizedlist>
-
-<para>
-Mutt automatically filters out repeated items from the history. It
-also mimics the behavior of some shells by ignoring items starting
-with a space. The latter feature can be useful in macros to not clobber
-the history's valuable entries with unwanted entries.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="reading">
-<title>Reading Mail - The Index and Pager</title>
-
-<para>
-Similar to many other mail clients, there are two modes in which mail is
-read in Mutt. The first is the index of messages in the mailbox, which is
-called the <quote>index</quote> in Mutt. The second mode is the display of the
-message contents. This is called the <quote>pager.</quote>
-</para>
-
-<para>
-The next few sections describe the functions provided in each of these
-modes.
-</para>
-
-<sect2 id="index-menu">
-<title>The Message Index</title>
-
-<para>
-Common keys used to navigate through and manage messages in the index
-are shown in <xref linkend="tab-key-index"/>. How messages are presented
-in the index menu can be customized using the
-<link linkend="index-format">$index_format</link> variable.
-</para>
-
-<table id="tab-key-index">
-<title>Most common message index keys</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>c</entry><entry>change to a different mailbox</entry></row>
-<row><entry>Esc c</entry><entry>change to a folder in read-only mode</entry></row>
-<row><entry>C</entry><entry>copy the current message to another mailbox</entry></row>
-<row><entry>Esc C</entry><entry>decode a message and copy it to a folder</entry></row>
-<row><entry>Esc s</entry><entry>decode a message and save it to a folder</entry></row>
-<row><entry>D</entry><entry>delete messages matching a pattern</entry></row>
-<row><entry>d</entry><entry>delete the current message</entry></row>
-<row><entry>F</entry><entry>mark as important</entry></row>
-<row><entry>l</entry><entry>show messages matching a pattern</entry></row>
-<row><entry>N</entry><entry>mark message as new</entry></row>
-<row><entry>o</entry><entry>change the current sort method</entry></row>
-<row><entry>O</entry><entry>reverse sort the mailbox</entry></row>
-<row><entry>q</entry><entry>save changes and exit</entry></row>
-<row><entry>s</entry><entry>save-message</entry></row>
-<row><entry>T</entry><entry>tag messages matching a pattern</entry></row>
-<row><entry>t</entry><entry>toggle the tag on a message</entry></row>
-<row><entry>Esc t</entry><entry>toggle tag on entire message thread</entry></row>
-<row><entry>U</entry><entry>undelete messages matching a pattern</entry></row>
-<row><entry>u</entry><entry>undelete-message</entry></row>
-<row><entry>v</entry><entry>view-attachments</entry></row>
-<row><entry>x</entry><entry>abort changes and exit</entry></row>
-<row><entry><Return></entry><entry>display-message</entry></row>
-<row><entry><Tab></entry><entry>jump to the next new or unread message</entry></row>
-<row><entry>@</entry><entry>show the author's full e-mail address</entry></row>
-<row><entry>$</entry><entry>save changes to mailbox</entry></row>
-<row><entry>/</entry><entry>search</entry></row>
-<row><entry>Esc /</entry><entry>search-reverse</entry></row>
-<row><entry>ˆL</entry><entry>clear and redraw the screen</entry></row>
-<row><entry>ˆT</entry><entry>untag messages matching a pattern</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-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 <quote>flags</quote> in <xref linkend="tab-msg-status-flags"/>
-may appear, some of which can be turned on or off using these functions:
-<literal><set-flag></literal> and
-<literal><clear-flag></literal>
-bound by default to <quote>w</quote> and <quote>W</quote> respectively.
-</para>
-
-<para>
-Furthermore, the flags in <xref linkend="tab-msg-recip-flags"/> reflect
-who the message is addressed to. They can be customized with the
-<link linkend="to-chars">$to_chars</link> variable.
-</para>
-
-<table id="tab-msg-status-flags">
-<title>Message status flags</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Flag</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>D</entry><entry>message is deleted (is marked for deletion)</entry></row>
-<row><entry>d</entry><entry>message has attachments marked for deletion</entry></row>
-<row><entry>K</entry><entry>contains a PGP public key</entry></row>
-<row><entry>N</entry><entry>message is new</entry></row>
-<row><entry>O</entry><entry>message is old</entry></row>
-<row><entry>P</entry><entry>message is PGP encrypted</entry></row>
-<row><entry>r</entry><entry>message has been replied to</entry></row>
-<row><entry>S</entry><entry>message is signed, and the signature is successfully verified</entry></row>
-<row><entry>s</entry><entry>message is signed</entry></row>
-<row><entry>!</entry><entry>message is flagged</entry></row>
-<row><entry>*</entry><entry>message is tagged</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<table id="tab-msg-recip-flags">
-<title>Message recipient flags</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Flag</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>+</entry><entry>message is to you and you only</entry></row>
-<row><entry>T</entry><entry>message is to you, but also to or cc'ed to others</entry></row>
-<row><entry>C</entry><entry>message is cc'ed to you</entry></row>
-<row><entry>F</entry><entry>message is from you</entry></row>
-<row><entry>L</entry><entry>message is sent to a subscribed mailing list</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="pager-menu">
-<title>The Pager</title>
-
-<para>
-By default, Mutt uses its builtin pager to display the contents of messages.
-The pager is very similar to the Unix program <emphasis>less</emphasis> though not nearly as
-featureful.
-</para>
-
-<table id="tab-key-pager">
-<title>Most common pager keys</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><Return></entry><entry>go down one line</entry></row>
-<row><entry><Space></entry><entry>display the next page (or next message if at the end of a message)</entry></row>
-<row><entry>-</entry><entry>go back to the previous page</entry></row>
-<row><entry>n</entry><entry>search for next match</entry></row>
-<row><entry>S</entry><entry>skip beyond quoted text</entry></row>
-<row><entry>T</entry><entry>toggle display of quoted text</entry></row>
-<row><entry>?</entry><entry>show keybindings</entry></row>
-<row><entry>/</entry><entry>regular expression search</entry></row>
-<row><entry>Esc /</entry><entry>backward regular expression search</entry></row>
-<row><entry>\</entry><entry>toggle highlighting of search matches</entry></row>
-<row><entry>ˆ</entry><entry>jump to the top of the message</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-In addition to key bindings in <xref linkend="tab-key-pager"/>,
-many of the functions from the index menu are also available in
-the pager, such as <literal><delete-message></literal> or <literal><copy-message></literal>
-(this is one advantage over using an external pager to view messages).
-</para>
-
-<para>
-Also, the internal pager supports a couple other advanced features. For
-one, it will accept and translate the <quote>standard</quote> nroff sequences for
-bold and underline. These sequences are a series of either the letter,
-backspace (ˆH), the letter again for bold or the letter, backspace,
-<quote>_</quote> for denoting underline. Mutt will attempt to display these
-in bold and underline respectively if your terminal supports them. If
-not, you can use the bold and underline <link linkend="color">color</link>
-objects to specify a color or mono attribute for them.
-</para>
-
-<para>
-Additionally, the internal pager supports the ANSI escape sequences for
-character attributes. Mutt translates them into the correct color and
-character settings. The sequences Mutt supports are:
-</para>
-
-<screen>
-\e[<emphasis>Ps</emphasis>;<emphasis>Ps</emphasis>;..<emphasis>Ps</emphasis>;m
-</screen>
-
-<para>
-where <emphasis>Ps</emphasis> can be one of the codes shown in
-<xref linkend="tab-ansi-esc"/>.
-</para>
-
-<table id="tab-ansi-esc">
-<title>ANSI escape sequences</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Escape code</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>0</entry><entry>All attributes off</entry></row>
-<row><entry>1</entry><entry>Bold on</entry></row>
-<row><entry>4</entry><entry>Underline on</entry></row>
-<row><entry>5</entry><entry>Blink on</entry></row>
-<row><entry>7</entry><entry>Reverse video on</entry></row>
-<row><entry>3<emphasis><color></emphasis></entry><entry>Foreground color is <emphasis><color></emphasis> (see <xref linkend="tab-color"/>)</entry></row>
-<row><entry>4<emphasis><color></emphasis></entry><entry>Background color is <emphasis><color></emphasis> (see <xref linkend="tab-color"/>)</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<table id="tab-color">
-<title>Color sequences</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Color code</entry><entry>Color</entry></row>
-</thead>
-<tbody>
-<row><entry>0</entry><entry>Black</entry></row>
-<row><entry>1</entry><entry>Red</entry></row>
-<row><entry>2</entry><entry>Green</entry></row>
-<row><entry>3</entry><entry>Yellow</entry></row>
-<row><entry>4</entry><entry>Blue</entry></row>
-<row><entry>5</entry><entry>Magenta</entry></row>
-<row><entry>6</entry><entry>Cyan</entry></row>
-<row><entry>7</entry><entry>White</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Mutt uses these attributes for handling <literal>text/enriched</literal>
-messages, and they can also be used by an external
-<link linkend="auto-view">autoview</link> script for highlighting
-purposes.
-</para>
-
-<note>
-<para>
-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.
-</para>
-</note>
-
-<note>
-<para>
-Note that the search commands in the pager take regular expressions,
-which are not quite the same as the more
-complex <link linkend="patterns">patterns</link> used by the search
-command in the index. This is because the pager only performs simple
-text search, whereas the index provides boolean filtering on several
-aspects of messages.
-</para>
-</note>
-
-</sect2>
-
-<sect2 id="threads">
-<title>Threaded Mode</title>
-
-<para>
-When the mailbox is <link linkend="sort">sorted</link> by <emphasis>threads</emphasis>, there are
-a few additional functions available in the <emphasis>index</emphasis> and <emphasis>pager</emphasis> modes
-as shown in <xref linkend="tab-key-threads"/>.
-</para>
-
-<table id="tab-key-threads">
-<title>Most common thread mode keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>ˆD</entry><entry><literal><delete-thread></literal></entry><entry>delete all messages in the current thread</entry></row>
-<row><entry>ˆU</entry><entry><literal><undelete-thread></literal></entry><entry>undelete all messages in the current thread</entry></row>
-<row><entry>ˆN</entry><entry><literal><next-thread></literal></entry><entry>jump to the start of the next thread</entry></row>
-<row><entry>ˆP</entry><entry><literal><previous-thread></literal></entry><entry>jump to the start of the previous thread</entry></row>
-<row><entry>ˆR</entry><entry><literal><read-thread></literal></entry><entry>mark the current thread as read</entry></row>
-<row><entry>Esc d</entry><entry><literal><delete-subthread></literal></entry><entry>delete all messages in the current subthread</entry></row>
-<row><entry>Esc u</entry><entry><literal><undelete-subthread></literal></entry><entry>undelete all messages in the current subthread</entry></row>
-<row><entry>Esc n</entry><entry><literal><next-subthread></literal></entry><entry>jump to the start of the next subthread</entry></row>
-<row><entry>Esc p</entry><entry><literal><previous-subthread></literal></entry><entry>jump to the start of the previous subthread</entry></row>
-<row><entry>Esc r</entry><entry><literal><read-subthread></literal></entry><entry>mark the current subthread as read</entry></row>
-<row><entry>Esc t</entry><entry><literal><tag-thread></literal></entry><entry>toggle the tag on the current thread</entry></row>
-<row><entry>Esc v</entry><entry><literal><collapse-thread></literal></entry><entry>toggle collapse for the current thread</entry></row>
-<row><entry>Esc V</entry><entry><literal><collapse-all></literal></entry><entry>toggle collapse for all threads</entry></row>
-<row><entry>P</entry><entry><literal><parent-message></literal></entry><entry>jump to parent message in thread</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<note>
-<para>
-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 on
-the screen. See %M in <link linkend="index-format">$index_format</link>.
-For example, you could use "%?M?(#%03M)&(%4l)?" in <link linkend="index-format">$index_format</link> to optionally
-display the number of hidden messages if the thread is collapsed.
-</para>
-</note>
-
-<para>
-See also: <link linkend="strict-threads">$strict_threads</link>.
-</para>
-
-</sect2>
-
-<sect2 id="reading-misc">
-<title>Miscellaneous Functions</title>
-
-<para>
-In addition, the <emphasis>index</emphasis> and <emphasis>pager</emphasis>
-menus have these interesting functions:
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>
-<literal><create-alias></literal><anchor id="create-alias"/> (default: a)
-</term>
-<listitem>
-<para>
-Creates a new alias based upon the current message (or prompts for a
-new one). Once editing is complete, an <link linkend="alias">alias</link>
-command is added to the file specified by
-the <link linkend="alias-file">$alias_file</link> variable
-for future use
-</para>
-
-<note>
-<para>
-Mutt does not read the <link linkend="alias-file">$alias_file</link>
-upon startup so you must explicitly <link linkend="source">source</link> the file.
-</para>
-</note>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><check-traditional-pgp></literal><anchor id="check-traditional-pgp"/> (default: Esc P)
-</term>
-<listitem>
-<para>
-This function will search the current message for content signed or
-encrypted with PGP the <quote>traditional</quote> 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 <link linkend="edit-type"><literal><edit-type></literal></link> function's
-effect.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><edit></literal><anchor id="edit"/> (default: e)
-</term>
-<listitem>
-<para>
-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; if the message is unchanged it won't be replaced.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><edit-type></literal><anchor id="edit-type"/> (default:
-ˆE on the attachment menu, and in the pager and index menus;
-ˆT on the compose menu)
-</term>
-<listitem>
-<para>
-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
-<link linkend="attach-menu">attachment menu</link>, you can change any
-attachment's content type. These changes are not persistent, and get
-lost upon changing folders.
-</para>
-
-<para>
-Note that this command is also available on the <link linkend="compose-menu">compose
-menu</link>. There, it's used to fine-tune the properties of attachments you are going
-to send.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><enter-command></literal><anchor id="enter-command"/> (default: <quote>:</quote>)
-</term>
-<listitem>
-<para>
-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 <link linkend="macro">macros</link> to change settings on the
-fly.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><extract-keys></literal><anchor id="extract-keys"/> (default: ˆK)
-</term>
-<listitem>
-<para>
-This command extracts PGP public keys from the current or tagged
-message(s) and adds them to your PGP public key ring.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><forget-passphrase></literal><anchor id="forget-passphrase"/> (default:
-ˆF)
-</term>
-<listitem>
-<para>
-This command wipes the passphrase(s) from memory. It is useful, if
-you misspelled the passphrase.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><list-reply></literal><anchor id="list-reply"/> (default: L)
-</term>
-<listitem>
-<para>
-Reply to the current or tagged message(s) by extracting any addresses which
-match the regular expressions given by the <link linkend="lists">lists or subscribe</link>
-commands, but also honor any <literal>Mail-Followup-To</literal> header(s) if the
-<link linkend="honor-followup-to">$honor_followup_to</link>
-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.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><pipe-message></literal><anchor id="pipe-message"/> (default: |)
-</term>
-<listitem>
-<para>
-Asks for an external Unix command and pipes the current or
-tagged message(s) to it. The variables <link linkend="pipe-decode">$pipe_decode</link>, <link linkend="pipe-split">$pipe_split</link>,
-<link linkend="pipe-sep">$pipe_sep</link> and <link linkend="wait-key">$wait_key</link> control the exact behavior of this function.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><resend-message></literal><anchor id="resend-message"/> (default: Esc e)
-</term>
-<listitem>
-<para>
-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 <link linkend="weed">$weed</link>
-variable.
-</para>
-
-<para>
-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 <literal>message/rfc822</literal> body part.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><shell-escape></literal><anchor id="shell-escape"/> (default: !)
-</term>
-<listitem>
-<para>
-Asks for an external Unix command and executes it. The <link linkend="wait-key">$wait_key</link> can be used to control
-whether Mutt 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. If no command is given, an
-interactive shell is executed.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><toggle-quoted></literal><anchor id="toggle-quoted"/> (default: T)
-</term>
-<listitem>
-<para>
-The pager uses the <link linkend="quote-regexp">$quote_regexp</link> variable to detect quoted text when
-displaying the body of the message. This function toggles the display
-of the quoted material in the message. It is particularly useful when
-being interested in just the response and there is a large amount of
-quoted text in the way.
-</para>
-</listitem>
-</varlistentry>
-
-<varlistentry>
-<term>
-<literal><skip-quoted></literal><anchor id="skip-quoted"/> (default: S)
-</term>
-<listitem>
-<para>
-This function will go to the next line of non-quoted text which comes
-after a line of quoted text in the internal pager.
-</para>
-</listitem>
-</varlistentry>
-
-</variablelist>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="sending">
-<title>Sending Mail</title>
-
-<sect2 id="sending-intro">
-<title>Introduction</title>
-
-<para>
-The bindings shown in <xref linkend="tab-key-send"/> are available in the
-<emphasis>index</emphasis> and <emphasis>pager</emphasis> to start a new message.
-</para>
-
-<table id="tab-key-send">
-<title>Most common mail sending keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>m</entry><entry><literal><compose></literal></entry><entry>compose a new message</entry></row>
-<row><entry>r</entry><entry><literal><reply></literal></entry><entry>reply to sender</entry></row>
-<row><entry>g</entry><entry><literal><group-reply></literal></entry><entry>reply to all recipients</entry></row>
-<row><entry>L</entry><entry><literal><list-reply></literal></entry><entry>reply to mailing list address</entry></row>
-<row><entry>f</entry><entry><literal><forward></literal></entry><entry>forward message</entry></row>
-<row><entry>b</entry><entry><literal><bounce></literal></entry><entry>bounce (remail) message</entry></row>
-<row><entry>Esc k</entry><entry><literal><mail-key></literal></entry><entry>mail a PGP public key to someone</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-<emphasis>Bouncing</emphasis> a message sends the message as-is to the recipient you
-specify. <emphasis>Forwarding</emphasis> 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 <quote><link linkend="forwarding-mail">Forwarding
-and Bouncing Mail</link>.</quote>
-</para>
-
-<para>
-Mutt will then enter the <emphasis>compose</emphasis> menu and prompt you for the
-recipients to place on the <quote>To:</quote> header field. Next, it will ask
-you for the <quote>Subject:</quote> field for the message, providing a default if
-you are replying to or forwarding a message. See also
-<link linkend="askcc">$askcc</link>,
-<link linkend="askbcc">$askbcc</link>,
-<link linkend="autoedit">$autoedit</link>,
-<link linkend="bounce">$bounce</link>,
-<link linkend="fast-reply">$fast_reply</link>,
-and <link linkend="include">$include</link>
-for changing how Mutt asks these questions.
-</para>
-
-<para>
-Mutt will then automatically start your <link linkend="editor">$editor</link>
-on the message body. If the <link linkend="edit-headers">$edit_headers</link>
-variable is set, the headers will be at the top of the message in your editor.
-Any messages you are replying to will be added in sort order to the message,
-with appropriate <link linkend="attribution">$attribution</link>,
-<link linkend="indent-string">$indent_string</link> and
-<link linkend="post-indent-string">$post_indent_string</link>.
-When forwarding a message, if the <link linkend="mime-forward">$mime_forward</link>
-variable is unset, a copy of the forwarded message will be included. If
-you have specified a <link linkend="signature">$signature</link>, it
-will be appended to the message.
-</para>
-
-<para>
-Once you have finished editing the body of your mail message, you are
-returned to the <emphasis>compose</emphasis> menu providing the functions
-shown in <xref linkend="tab-func-compose"/> to modify, send or postpone the
-message.
-</para>
-
-<table id="tab-func-compose">
-<title>Most common compose menu keys</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Key</entry><entry>Function</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>a</entry><entry><literal><attach-file></literal></entry><entry>attach a file</entry></row>
-<row><entry>A</entry><entry><literal><attach-message></literal></entry><entry>attach message(s) to the message</entry></row>
-<row><entry>Esc k</entry><entry><literal><attach-key></literal></entry><entry>attach a PGP public key</entry></row>
-<row><entry>d</entry><entry><literal><edit-description></literal></entry><entry>edit description on attachment</entry></row>
-<row><entry>D</entry><entry><literal><detach-file></literal></entry><entry>detach a file</entry></row>
-<row><entry>t</entry><entry><literal><edit-to></literal></entry><entry>edit the To field</entry></row>
-<row><entry>Esc f</entry><entry><literal><edit-from></literal></entry><entry>edit the From field</entry></row>
-<row><entry>r</entry><entry><literal><edit-reply-to></literal></entry><entry>edit the Reply-To field</entry></row>
-<row><entry>c</entry><entry><literal><edit-cc></literal></entry><entry>edit the Cc field</entry></row>
-<row><entry>b</entry><entry><literal><edit-bcc></literal></entry><entry>edit the Bcc field</entry></row>
-<row><entry>y</entry><entry><literal><send-message></literal></entry><entry>send the message</entry></row>
-<row><entry>s</entry><entry><literal><edit-subject></literal></entry><entry>edit the Subject</entry></row>
-<row><entry>S</entry><entry><literal><smime-menu></literal></entry><entry>select S/MIME options</entry></row>
-<row><entry>f</entry><entry><literal><edit-fcc></literal></entry><entry>specify an <quote>Fcc</quote> mailbox</entry></row>
-<row><entry>p</entry><entry><literal><pgp-menu></literal></entry><entry>select PGP options</entry></row>
-<row><entry>P</entry><entry><literal><postpone-message></literal></entry><entry>postpone this message until later</entry></row>
-<row><entry>q</entry><entry><literal><quit></literal></entry><entry>quit (abort) sending the message</entry></row>
-<row><entry>w</entry><entry><literal><write-fcc></literal></entry><entry>write the message to a folder</entry></row>
-<row><entry>i</entry><entry><literal><ispell></literal></entry><entry>check spelling (if available on your system)</entry></row>
-<row><entry>ˆF</entry><entry><literal><forget-passphrase></literal></entry><entry>wipe passphrase(s) from memory</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-The compose menu is also used to edit the attachments for a message which can be either files
-or other messages. The <literal><attach-message></literal> function to will prompt you for a folder to
-attach messages from. You can now tag messages in that folder and they
-will be attached to the message you are sending.
-</para>
-
-<note>
-<para>
-Note that certain
-operations like composing a new mail, replying, forwarding, etc. are
-not permitted when you are in that folder. The %r in
-<link linkend="status-format">$status_format</link> will change to
-a <quote>A</quote> to indicate that you are in attach-message mode.
-</para>
-</note>
-
-</sect2>
-
-<sect2 id="edit-header">
-<title>Editing the message header</title>
-
-<para>
-When editing the header because of <link linkend="edit-headers">$edit_headers</link>
-being set, there are a several pseudo headers available which
-will not be included in sent messages.
-</para>
-
-<sect3 id="fcc-header">
-<title>Fcc: pseudo header</title>
-
-<para>
-If you specify
-
-<literal>Fcc:</literal> <emphasis>filename</emphasis>
-
-as a header, Mutt will pick up <emphasis>filename</emphasis>
-just as if you had used the <literal><edit-fcc></literal> function in the <emphasis>compose</emphasis> menu.
-</para>
-
-</sect3>
-
-<sect3 id="attach-header">
-<title>Attach: pseudo header</title>
-
-<para>
-You can also attach files to your message by specifying
-
-<literal>Attach:</literal> <emphasis>filename</emphasis> [ <emphasis>description</emphasis> ]
-
-where <emphasis>filename</emphasis> is the file to attach and <emphasis>description</emphasis> is an
-optional string to use as the description of the attached file.
-</para>
-
-</sect3>
-
-<sect3 id="pgp-header">
-<title>Pgp: pseudo header</title>
-
-<para>
-If you want to use PGP, you can specify
-</para>
-
-<para>
-<literal>Pgp:</literal> [ <literal>E</literal> | <literal>S</literal> | <literal>S</literal><emphasis><id></emphasis> ]
-
-</para>
-
-<para>
-<quote>E</quote> selects encryption, <quote>S</quote> selects signing and
-<quote>S<id></quote> selects signing with the given key, setting
-<link linkend="pgp-sign-as">$pgp_sign_as</link>
-permanently.
-</para>
-
-</sect3>
-
-<sect3 id="in-reply-to-header">
-<title>In-Reply-To: header</title>
-
-<para>
-When replying to messages, the <emphasis>In-Reply-To:</emphasis> header contains the
-Message-Id of the message(s) you reply to. If you remove its value, Mutt will not generate a
-<emphasis>References:</emphasis> field, which allows you to create a new message thread, for example
-to create a new message to a mailing list without having to enter the mailing list's address.
-</para>
-
-</sect3>
-
-</sect2>
-
-<sect2 id="sending-crypto">
-<title>Sending cryptographically signed/encrypted messages</title>
-
-<para>
-If you have told mutt to PGP or S/MIME encrypt a message, it will guide you
-through a key selection process when you try to send the message.
-Mutt 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.
-</para>
-
-<para>
-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 <literal>ˆG</literal>. When you do so, mutt will
-return to the compose screen.
-</para>
-
-<para>
-Once you have successfully finished the key selection, the message
-will be encrypted using the selected public keys when sent out.
-</para>
-
-<para>
-Most fields of the entries in the key selection menu (see also <link linkend="pgp-entry-format">$pgp_entry_format</link>)
-have obvious meanings. But some explanations on the capabilities, flags,
-and validity fields are in order.
-</para>
-
-<para>
-The flags sequence (%f) will expand to one of the flags in
-<xref linkend="tab-pgp-menuflags"/>.
-</para>
-
-<table id="tab-pgp-menuflags">
-<title>PGP key menu flags</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Flag</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>R</entry><entry>The key has been revoked and can't be used.</entry></row>
-<row><entry>X</entry><entry>The key is expired and can't be used.</entry></row>
-<row><entry>d</entry><entry>You have marked the key as disabled.</entry></row>
-<row><entry>c</entry><entry>There are unknown critical self-signature packets.</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-The capabilities field (%c) expands to a two-character sequence
-representing a key's capabilities. The first character gives
-the key's encryption capabilities: A minus sign (<quote>-</quote>) means
-that the key cannot be used for encryption. A dot (<quote>.</quote>) means that
-it's marked as a signature key in one of the user IDs, but may
-also be used for encryption. The letter <quote>e</quote> indicates that
-this key can be used for encryption.
-</para>
-
-<para>
-The second character indicates the key's signing capabilities. Once
-again, a <quote>-</quote> implies <quote>not for signing</quote>, <quote>.</quote> implies
-that the key is marked as an encryption key in one of the user-ids, and
-<quote>s</quote> denotes a key which can be used for signing.
-</para>
-
-<para>
-Finally, the validity field (%t) indicates how well-certified a user-id
-is. A question mark (<quote>?</quote>) indicates undefined validity, a minus
-character (<quote>-</quote>) marks an untrusted association, a space character
-means a partially trusted association, and a plus character (<quote>+</quote>)
-indicates complete validity.
-</para>
-
-</sect2>
-
-<sect2 id="sending-mixmaster">
-<title>Sending anonymous messages via mixmaster</title>
-
-<para>
-You may also have compiled 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.
-</para>
-
-<para>
-To use it, you'll have to obey certain restrictions. Most
-important, you cannot use the <literal>Cc</literal> and <literal>Bcc</literal> headers. To tell
-Mutt to use mixmaster, you have to select a remailer chain, using
-the mix function on the compose menu.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-You can navigate in the chain using the <literal><chain-prev></literal> and
-<literal><chain-next></literal> functions, which are by default bound to the left
-and right arrows and to the <literal>h</literal> and <literal>l</literal> keys (think vi
-keyboard bindings). To insert a remailer at the current chain
-position, use the <literal><insert></literal> function. To append a remailer behind
-the current chain position, use <literal><select-entry></literal> or <literal><append></literal>.
-You can also delete entries from the chain, using the corresponding
-function. Finally, to abandon your changes, leave the menu, or
-<literal><accept></literal> them pressing (by default) the <literal>Return</literal> key.
-</para>
-
-<para>
-Note that different remailers do have different capabilities,
-indicated in the %c entry of the remailer menu lines (see
-<link linkend="mix-entry-format">$mix_entry_format</link>). Most important is
-the <quote>middleman</quote> capability, indicated by a capital <quote>M</quote>: 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.
-</para>
-
-</sect2>
-
-<sect2 id="ff">
-<title>Sending format=flowed messages</title>
-
-<sect3 id="ff-concept">
-<title>Concept</title>
-
-<para>
-<literal>format=flowed</literal>-style messages (or <literal>f=f</literal>
-for short) are <literal>text/plain</literal> messages that consist of paragraphs which a receiver's
-mail client may reformat to its own needs which mostly means to
-customize line lengths regardless of what the sender sent. Technically this is
-achieved by letting lines of a <quote>flowable</quote> paragraph end in spaces
-except for the last line.
-</para>
-
-<para>
-While for text-mode clients like mutt it's the best way to assume only a
-standard 80x25 character cell terminal, it may be desired to let the
-receiver decide completely how to view a message.
-</para>
-
-</sect3>
-
-<sect3 id="ff-support">
-<title>Mutt support</title>
-
-<para>
-Mutt only supports setting the required <literal>format=flowed</literal>
-MIME parameter on outgoing messages if the <link
-linkend="text-flowed">$text_flowed</link>
-variable is set, specifically it does not add the
-trailing spaces.
-</para>
-
-<para>
-After editing the initial message text and before entering
-the compose menu, mutt properly space-stuffes the message.
-<emphasis>Space-stuffing</emphasis> is required by RfC3676 defining
-<literal>format=flowed</literal> and means to prepend a space to:
-</para>
-
-<itemizedlist>
-<listitem><para>all lines starting with a space</para></listitem>
-<listitem><para>lines starting with the word <quote><literal>From</literal></quote>
-followed by space</para></listitem>
-<listitem><para>all lines starting with <quote><literal>></literal></quote> which
-is not intended to be a quote character</para></listitem>
-</itemizedlist>
-
-<note>
-<para>
-Mutt only supports space-stuffing
-for the first two types of lines but not for the third: It is impossible to
-safely detect whether a leading <literal>></literal> character starts a
-quote or not. Furthermore, Mutt only applies space-stuffing
-<emphasis>once</emphasis> after the initial edit is finished.
-</para>
-</note>
-
-<para>
-All leading spaces are to be removed by receiving clients to restore
-the original message prior to further processing.
-</para>
-
-</sect3>
-
-<sect3 id="ff-editor">
-<title>Editor considerations</title>
-
-<para>
-As mutt provides no additional features to compose <literal>f=f</literal>
-messages, it's completely up to the user and his editor to produce
-proper messages. Please consider your editor's documentation if you
-intend to send <literal>f=f</literal> messages.
-</para>
-
-<para>
-Please note that when editing messages from the compose menu several
-times before really sending a mail, it's up to the user to ensure that
-the message is properly space-stuffed.
-</para>
-
-<para>
-For example, <emphasis>vim</emphasis> provides the <literal>w</literal>
-flag for its <literal>formatoptions</literal> setting to assist in
-creating <literal>f=f</literal> messages, see <literal>:help
-fo-table</literal> for details.
-</para>
-
-</sect3>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="forwarding-mail">
-<title>Forwarding and Bouncing Mail</title>
-
-<para>
-Bouncing and forwarding let you send an existing message to recipients
-that you specify. Bouncing a message sends a verbatim copy of a message
-to alternative addresses as if they were the message's original
-recipients specified in the Bcc header.
-Forwarding a message, on the other hand, allows you to modify the message
-before it is resent (for example, by adding your own comments). Bouncing
-is done using the <literal><bounce></literal> function and forwarding
-using the <literal><forward></literal> function bound to <quote>b</quote> and <quote>f</quote>
-respectively.
-</para>
-
-<para>
-Forwarding can be done by including the original message in the new
-message's body (surrounded by indicating lines) or including it as a MIME
-attachment, depending on the value of the <link linkend="mime-forward">$mime_forward</link> variable. Decoding of attachments,
-like in the pager, can be controlled by the <link linkend="forward-decode">$forward_decode</link> and <link linkend="mime-forward-decode">$mime_forward_decode</link> variables,
-respectively. The desired forwarding format may depend on the content,
-therefore <emphasis>$mime_forward</emphasis> is a quadoption which, for
-example, can be set to <quote>ask-no</quote>.
-</para>
-
-<para>
-The inclusion of headers is controlled by the current setting of the
-<link linkend="weed">$weed</link> variable, unless <link linkend="mime-forward">$mime_forward</link> is set.
-</para>
-
-<para>
-Editing the message to forward follows the same procedure as sending or
-replying to a message does.
-</para>
-
-</sect1>
-
-<sect1 id="postponing-mail">
-<title>Postponing Mail</title>
-
-<para>
-At times it is desirable to delay sending a message that you have
-already begun to compose. When the <literal><postpone-message></literal> function is
-used in the <emphasis>compose</emphasis> menu, the body of your message and attachments
-are stored in the mailbox specified by the <link linkend="postponed">$postponed</link> variable. This means that you can recall the
-message even if you exit Mutt and then restart it at a later time.
-</para>
-
-<para>
-Once a message is postponed, there are several ways to resume it. From the
-command line you can use the <quote>-p</quote> option, or if you compose a new
-message from the <emphasis>index</emphasis> or <emphasis>pager</emphasis> you will be prompted if postponed
-messages exist. If multiple messages are currently postponed, the
-<emphasis>postponed</emphasis> menu will pop up and you can select which message you would
-like to resume.
-</para>
-
-<note>
-<para>
-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.
-</para>
-</note>
-
-<para>
-See also the <link linkend="postpone">$postpone</link> quad-option.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="configuration">
-<title>Configuration</title>
-
-<sect1 id="configuration-files">
-<title>Location of initialization files</title>
-
-<para>
-While the default configuration (or <quote>preferences</quote>) make Mutt
-usable right out of the box, it is often desirable to tailor Mutt to
-suit your own tastes. When Mutt is first invoked, it will attempt to
-read the <quote>system</quote> configuration file (defaults set by your local
-system administrator), unless the <quote>-n</quote> <link linkend="commandline">command line</link> option is specified. This file is typically
-<literal>/usr/local/share/mutt/Muttrc</literal> or <literal>/etc/Muttrc</literal>. Mutt
-will next look for a file named <literal>.muttrc</literal> in your home
-directory. If this file does not exist and your home directory has
-a subdirectory named <literal>.mutt</literal>, mutt try to load a file named
-<literal>.mutt/muttrc</literal>.
-</para>
-
-<para>
-<literal>.muttrc</literal> is the file where you will usually place your <link linkend="commands">commands</link> to configure Mutt.
-</para>
-
-<para>
-In addition, mutt supports version specific configuration files that are
-parsed instead of the default files as explained above. For instance, if
-your system has a <literal>Muttrc-0.88</literal> file in the system configuration
-directory, and you are running version 0.88 of mutt, this file will be
-sourced instead of the <literal>Muttrc</literal> file. The same is true of the user
-configuration file, if you have a file <literal>.muttrc-0.88.6</literal> in your home
-directory, when you run mutt version 0.88.6, it will source this file
-instead of the default <literal>.muttrc</literal> file. The version number is the
-same which is visible using the <quote>-v</quote> <link linkend="commandline">command line</link> switch or using the <literal>show-version</literal> key (default:
-V) from the index menu.
-</para>
-
-</sect1>
-
-<sect1 id="muttrc-syntax" xreflabel="Syntax of Initialization Files">
-<title>Syntax of Initialization Files</title>
-
-<para>
-An initialization file consists of a series of <link linkend="commands">commands</link>. Each line of the file may contain one or more commands.
-When multiple commands are used, they must be separated by a semicolon
-(;).
-</para>
-
-<example id="ex-rc-multiple-cmds">
-<title>Multiple configuration commands per line</title>
-<screen>
-set realname='Mutt user' ; ignore x-
-</screen>
-</example>
-
-<para>
-The hash mark, or pound sign
-(<quote>#</quote>), is used as a <quote>comment</quote> 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,
-</para>
-
-<example id="ex-ec-comment">
-<title>Commenting configuration files</title>
-<screen>
-my_hdr X-Disclaimer: Why are you listening to me? # This is a comment
-</screen>
-</example>
-
-<para>
-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, backticks are evaluated inside of double
-quotes, but <emphasis role="bold">not</emphasis> for single quotes.
-</para>
-
-<para>
-\ quotes the next character, just as in shells such as bash and zsh.
-For example, if want to put quotes <quote>"</quote> inside of a string, you can use
-<quote>\</quote> to force the next character to be a literal instead of interpreted
-character.
-</para>
-
-<example id="ex-rc-quote">
-<title>Escaping quotes in congfiguration files</title>
-<screen>
-set realname="Michael \"MuttDude\" Elkins"
-</screen>
-</example>
-
-<para>
-<quote>\\</quote> means to insert a literal <quote>\</quote> into the line.
-<quote>\n</quote> and <quote>\r</quote> have their usual C meanings of linefeed and
-carriage-return, respectively.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command in
-backticks (``). For example,
-</para>
-
-<example id="ex-rc-backtick">
-<title>Using external command's output in configuration files</title>
-<screen>
-my_hdr X-Operating-System: `uname -a`
-</screen>
-</example>
-
-<para>
-The output of the Unix command <quote>uname -a</quote> will be substituted before the
-line is parsed.
-</para>
-
-<note>
-<para>
-Since initialization files are line oriented, only
-the first line of output from the Unix command will be substituted.
-</para>
-</note>
-
-<para>
-Both environment variables and mutt variables can be accessed by
-prepending <quote>$</quote> to the name of the variable. For example,
-</para>
-
-<example id="ex-rc-env">
-<title>Using environment variables in configuration files</title>
-<screen>
-set record=+sent_on_$HOSTNAME
-</screen>
-</example>
-
-<para>
-will cause mutt to save outgoing messages to a folder named
-<quote>sent_on_kremvax</quote> if the environment variable HOSTNAME is set to
-<quote>kremvax.</quote> (See <link linkend="record">$record</link> for
-details.)
-</para>
-
-<para>
-Mutt expands the variable when it is assigned, not when it is used. If
-the value of a variable on the right-hand side of an assignment
-changes after the assignment, the variable on the left-hand side will
-not be affected.
-</para>
-
-<para>
-The commands understood by mutt are explained in the next paragraphs.
-For a complete list, see the <link linkend="commands">command reference</link>.
-</para>
-
-<para>
-All configuration files are expected to be in the current locale as
-specified by the <link linkend="charset">$charset</link> variable
-which doesn't have a default value since it's determined by Mutt at startup.
-If a configuration file is not encoded in the same character set the
-<link linkend="config-charset">$config_charset</link>
-variable should be used: all lines starting with the next are recoded
-from $config_charset to $charset.
-</para>
-
-<para>
-This mechanism should be avoided if possible as it has the
-following implications:
-</para>
-
-<itemizedlist>
-
-<listitem><para>These variables should be set early in a configuration
-file with $charset preceding $config_charset so Mutt
-know what character set to convert to.</para></listitem>
-
-<listitem><para>If $config_charset is set, it should be set
-in each configuration file because the value is global and <emphasis>not</emphasis>
-per configuration file.</para></listitem>
-
-<listitem><para>Because Mutt first recodes a line before it attempts to parse it,
-a conversion introducing question marks or other characters as
-part of errors (unconvertable characters, transliteration) may introduce syntax
-errors or silently change the meaning of certain tokens (e.g. inserting
-question marks into regular expressions).</para></listitem>
-
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="addrgroup">
-<title>Address groups</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>group</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain" rep="repeat">
-<option>-rx</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-addr</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>ungroup</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-rx</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-addr</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-<literal>group</literal> is used to directly add either addresses or
-regular expressions to the specified group or groups. The different
-categories of arguments to the <literal>group</literal> command can be
-in any order. The flags <literal>-rx</literal> and
-<literal>-addr</literal> specify what the following strings (that cannot
-begin with a hyphen) should be interpreted as: either a regular
-expression or an email address, respectively.
-</para>
-
-<para>
-These address groups can also be created implicitly by the
-<link linkend="alias">alias</link>, <link linkend="lists">lists</link>,
-<link linkend="lists">subscribe</link> and
-<link linkend="alternates">alternates</link> commands by specifying the
-optional <literal>-group</literal> option.
-</para>
-
-<para>
-Once defined, these address groups can be used in
-<link linkend="patterns">patterns</link> to search for and limit the
-display to messages matching a group.
-</para>
-
-<para>
-<literal>ungroup</literal> is used to remove addresses or regular
-expressions from the specified group or groups. The syntax is similar to
-the <literal>group</literal> command, however the special character
-<literal>*</literal> can be used to empty a group of all of its
-contents.
-</para>
-
-</sect1>
-
-<sect1 id="alias">
-<title>Defining/Using aliases</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>alias</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">address</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">address</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-It's usually very cumbersome to remember or type out the address of someone
-you are communicating with. Mutt allows you to create <quote>aliases</quote> which map
-a short string to a full address.
-</para>
-
-<note>
-<para>
-If you want to create an alias for more than
-one address, you <emphasis role="bold">must</emphasis> separate the addresses with a comma (<quote>,</quote>).
-</para>
-</note>
-
-<para>
-The optional <literal>-group</literal> argument to
-<literal>alias</literal> causes the aliased address(es) to be added to
-the named <emphasis>group</emphasis>.
-</para>
-
-<para>
-To remove an alias or aliases (<quote>*</quote> means all aliases):
-</para>
-
-<cmdsynopsis>
-<command>unalias</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">key</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<screen>
-alias muttdude me@cs.hmc.edu (Michael Elkins)
-alias theguys manny, moe, jack
-</screen>
-
-<para>
-Unlike other mailers, Mutt doesn't require aliases to be defined
-in a special file. The <literal>alias</literal> command can appear anywhere in
-a configuration file, as long as this file is <link linkend="source">sourced</link>. Consequently, you can have multiple alias files, or
-you can have all aliases defined in your muttrc.
-</para>
-
-<para>
-On the other hand, the <link linkend="create-alias"><literal><create-alias></literal></link>
-function can use only one file, the one pointed to by the <link linkend="alias-file">$alias_file</link> variable (which is
-<literal>˜/.muttrc</literal> by default). This file is not special either,
-in the sense that Mutt will happily append aliases to any file, but in
-order for the new aliases to take effect you need to explicitly <link linkend="source">source</link> this file too.
-</para>
-
-<para>
-For example:
-</para>
-
-<example id="ex-alias-external">
-<title>Configuring external alias files</title>
-<screen>
-source /usr/local/share/Mutt.aliases
-source ~/.mail_aliases
-set alias_file=~/.mail_aliases
-</screen>
-</example>
-
-<para>
-To use aliases, you merely use the alias at any place in mutt where mutt
-prompts for addresses, such as the <emphasis>To:</emphasis> or <emphasis>Cc:</emphasis> prompt. You can
-also enter aliases in your editor at the appropriate headers if you have the
-<link linkend="edit-headers">$edit_headers</link> variable set.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-In the alias menu, you can select as many aliases as you want with the
-<literal>select-entry</literal> key (default: <Return>), and use the
-<emphasis>exit</emphasis> key (default: q) to return to the address prompt.
-</para>
-
-</sect1>
-
-<sect1 id="bind">
-<title>Changing the default key bindings</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>bind</command>
-<arg choice="plain">
-<replaceable class="parameter">map</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">function</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command allows you to change the default key bindings (operation
-invoked when pressing a key).
-</para>
-
-<para>
-<emphasis>map</emphasis> specifies in which menu the binding belongs. Multiple maps may
-be specified by separating them with commas (no additional whitespace is
-allowed). The currently defined maps are:
-</para>
-
-<anchor id="maps"/>
-<variablelist>
-
-<varlistentry>
-<term>generic</term>
-<listitem>
-<para>
-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 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.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>alias</term>
-<listitem>
-<para>
-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).
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>attach</term>
-<listitem>
-<para>
-The attachment menu is used to access the attachments on received messages.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>browser</term>
-<listitem>
-<para>
-The browser is used for both browsing the local directory structure, and for
-listing all of your incoming mailboxes.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>editor</term>
-<listitem>
-<para>
-The editor is the line-based editor the user enters text data.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>index</term>
-<listitem>
-<para>
-The index is the list of messages contained in a mailbox.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>compose</term>
-<listitem>
-<para>
-The compose menu is the screen used when sending a new message.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>pager</term>
-<listitem>
-<para>
-The pager is the mode used to display message/attachment data, and help
-listings.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>pgp</term>
-<listitem>
-<para>
-The pgp menu is used to select the OpenPGP keys used to encrypt outgoing
-messages.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>smime</term>
-<listitem>
-<para>
-The smime menu is used to select the OpenSSL certificates used to encrypt outgoing
-messages.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>postpone</term>
-<listitem>
-<para>
-The postpone menu is similar to the index menu, except is used when
-recalling a message the user was composing, but saved until later.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>query</term>
-<listitem>
-<para>
-The query menu is the browser for results returned by
-<link linkend="query-command">$query_command</link>.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>mix</term>
-<listitem>
-<para>
-The mixmaster screen is used to select remailer options for outgoing
-messages (if Mutt is compiled with Mixmaster support).
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-<para>
-<emphasis>key</emphasis> is the key (or key sequence) you wish to bind. To specify a
-control character, use the sequence <emphasis>\Cx</emphasis>, where <emphasis>x</emphasis> is the
-letter of the control character (for example, to specify control-A use
-<quote>\Ca</quote>). Note that the case of <emphasis>x</emphasis> as well as <emphasis>\C</emphasis> is
-ignored, so that <emphasis>\CA</emphasis>, <emphasis>\Ca</emphasis>, <emphasis>\cA</emphasis> and <emphasis>\ca</emphasis> are all
-equivalent. An alternative form is to specify the key as a three digit
-octal number prefixed with a <quote>\</quote> (for example <emphasis>\177</emphasis> is
-equivalent to <emphasis>\c?</emphasis>). In addition, <emphasis>key</emphasis> may
-be a symbolic name as shown in <xref linkend="tab-key-names"/>.
-</para>
-
-<table id="tab-key-names">
-<title>Symbolic key names</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Symbolic name</entry><entry>Meaning</entry></row>
-</thead>
-<tbody>
-<row><entry>\t</entry><entry>tab</entry></row>
-<row><entry><tab></entry><entry>tab</entry></row>
-<row><entry><backtab></entry><entry>backtab / shift-tab</entry></row>
-<row><entry>\r</entry><entry>carriage return</entry></row>
-<row><entry>\n</entry><entry>newline</entry></row>
-<row><entry>\e</entry><entry>escape</entry></row>
-<row><entry><esc></entry><entry>escape</entry></row>
-<row><entry><up></entry><entry>up arrow</entry></row>
-<row><entry><down></entry><entry>down arrow</entry></row>
-<row><entry><left></entry><entry>left arrow</entry></row>
-<row><entry><right></entry><entry>right arrow</entry></row>
-<row><entry><pageup></entry><entry>Page Up</entry></row>
-<row><entry><pagedown></entry><entry>Page Down</entry></row>
-<row><entry><backspace></entry><entry>Backspace</entry></row>
-<row><entry><delete></entry><entry>Delete</entry></row>
-<row><entry><insert></entry><entry>Insert</entry></row>
-<row><entry><enter></entry><entry>Enter</entry></row>
-<row><entry><return></entry><entry>Return</entry></row>
-<row><entry><home></entry><entry>Home</entry></row>
-<row><entry><end></entry><entry>End</entry></row>
-<row><entry><space></entry><entry>Space bar</entry></row>
-<row><entry><f1></entry><entry>function key 1</entry></row>
-<row><entry><f10></entry><entry>function key 10</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-<emphasis>key</emphasis> does not need to be enclosed in quotes unless it contains a
-space (<quote> </quote>) or semi-colon (<quote>;</quote>).
-</para>
-
-<para>
-<emphasis>function</emphasis> specifies which action to take when <emphasis>key</emphasis> is pressed.
-For a complete list of functions, see the <link linkend="functions">reference</link>. The special function <literal><noop></literal> unbinds the specified key
-sequence.
-</para>
-
-</sect1>
-
-<sect1 id="charset-hook">
-<title>Defining aliases for character sets </title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>charset-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">alias</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">charset</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>iconv-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">charset</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">local-charset</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-The <literal>charset-hook</literal> 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.
-</para>
-
-<para>
-The <literal>iconv-hook</literal> 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.
-</para>
-
-</sect1>
-
-<sect1 id="folder-hook">
-<title>Setting variables based upon mailbox</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>folder-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]regexp</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-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. <emphasis>regexp</emphasis> is a regular expression specifying
-in which mailboxes to execute <emphasis>command</emphasis> before loading. If a mailbox
-matches multiple folder-hook's, they are executed in the order given in the
-muttrc.
-</para>
-
-<note>
-<para>
-If you use the <quote>!</quote> shortcut for <link linkend="spoolfile">$spoolfile</link> at the beginning of the pattern, you must place it
-inside of double or single quotes in order to distinguish it from the
-logical <emphasis>not</emphasis> operator for the expression.
-</para>
-</note>
-
-<note>
-<para>
-Settings are <emphasis>not</emphasis> restored when you leave the mailbox.
-For example, a command action to perform is to change the sorting method
-based upon the mailbox being read:
-</para>
-</note>
-
-<screen>
-folder-hook mutt set sort=threads
-</screen>
-
-<para>
-However, the sorting method is not restored to its previous value when
-reading a different mailbox. To specify a <emphasis>default</emphasis> command, use the
-pattern <quote>.</quote> before other folder-hooks adjusting a value on a per-folder basis
-because folder-hooks are evaluated in the order given in the configuration file.
-The following example will set the <link linkend="sort">sort</link> variable
-to <literal>date-sent</literal> for all folders but to <literal>threads</literal>
-for all folders containing <quote>mutt</quote> in their name.
-</para>
-
-<example id="ex-folder-sorting">
-<title>Setting sort method based on mailbox name</title>
-<screen>
-folder-hook . set sort=date-sent
-folder-hook mutt set sort=threads
-</screen>
-</example>
-
-</sect1>
-
-<sect1 id="macro">
-<title>Keyboard macros</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>macro</command>
-<arg choice="plain">
-<replaceable class="parameter">menu</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">sequence</replaceable>
-</arg>
-<arg choice="opt">
-<replaceable class="parameter">description</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-Macros are useful when you would like a single key to perform a series of
-actions. When you press <emphasis>key</emphasis> in menu <emphasis>menu</emphasis>, Mutt will behave as if
-you had typed <emphasis>sequence</emphasis>. So if you have a common sequence of commands
-you type, you can create a macro to execute those commands with a single
-key or fewer keys.
-</para>
-
-<para>
-<emphasis>menu</emphasis> is the <link linkend="maps">map</link> which the macro will be bound in.
-Multiple maps may be specified by separating multiple menu arguments by
-commas. Whitespace may not be used in between the menu arguments and the
-commas separating them.
-</para>
-
-<para>
-<emphasis>key</emphasis> and <emphasis>sequence</emphasis> are expanded by the same rules as the
-<link linkend="bind">key bindings</link> with some additions. The
-first is that control characters in <emphasis>sequence</emphasis> can also be specified
-as <emphasis>ˆx</emphasis>. In order to get a caret (<quote>ˆ</quote>) you need to use
-<emphasis>ˆˆ</emphasis>. Secondly, to specify a certain key such as <emphasis>up</emphasis>
-or to invoke a function directly, you can use the format
-<emphasis><key name></emphasis> and <emphasis><function name></emphasis>. For a listing of key
-names see the section on <link linkend="bind">key bindings</link>. Functions
-are listed in the <link linkend="functions">reference</link>.
-</para>
-
-<para>
-The advantage with using function names directly is that the macros will
-work regardless of the current key bindings, so they are not dependent on
-the user having particular key definitions. This makes them more robust
-and portable, and also facilitates defining of macros in files used by more
-than one user (e.g., the system Muttrc).
-</para>
-
-<para>
-Optionally you can specify a descriptive text after <emphasis>sequence</emphasis>,
-which is shown in the help screens.
-</para>
-
-<note>
-<para>
-Macro definitions (if any) listed in the help screen(s), are
-silently truncated at the screen width, and are not wrapped.
-</para>
-</note>
-
-</sect1>
-
-<sect1 id="color">
-<title>Using color and mono video attributes</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>color</command>
-<arg choice="plain">
-<replaceable class="parameter">object</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>color</command>
-<group choice="req">
-<arg choice="plain">
-<option>header</option>
-</arg>
-<arg choice="plain">
-<option>body</option>
-</arg>
-</group>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>color</command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>uncolor</command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-If your terminal supports color, you can spice up Mutt by creating your own
-color scheme. To define the color of an object (type of information), you
-must specify both a foreground color <emphasis role="bold">and</emphasis> a background color (it is not
-possible to only specify one or the other).
-</para>
-
-<para>
-<emphasis>header</emphasis> and <emphasis>body</emphasis> match <emphasis>regexp</emphasis>
-in the header/body of a message, <emphasis>index</emphasis> matches <emphasis>pattern</emphasis>
-(see <xref linkend="patterns"/>) in the message index.
-</para>
-
-<para>
-<emphasis>object</emphasis> can be one of:
-</para>
-
-<itemizedlist>
-<listitem><para>attachment</para></listitem>
-<listitem><para>bold (hiliting bold patterns in the body of messages)</para></listitem>
-<listitem><para>error (error messages printed by Mutt)</para></listitem>
-<listitem><para>hdrdefault (default color of the message header in the pager)</para></listitem>
-<listitem><para>indicator (arrow or bar used to indicate the current item in a menu)</para></listitem>
-<listitem><para>markers (the <quote>+</quote> markers at the beginning of wrapped lines in the pager)</para></listitem>
-<listitem><para>message (informational messages)</para></listitem>
-<listitem><para>normal</para></listitem>
-<listitem><para>quoted (text matching <link linkend="quote-regexp">$quote_regexp</link> in the body of a message)</para></listitem>
-<listitem><para>quoted1, quoted2, ..., quoted<emphasis role="bold">N</emphasis> (higher levels of quoting)</para></listitem>
-<listitem><para>search (hiliting of words in the pager)</para></listitem>
-<listitem><para>signature</para></listitem><listitem><para>status (mode lines used to display info about the mailbox or message)</para></listitem>
-<listitem><para>tilde (the <quote>˜</quote> used to pad blank lines in the pager)</para></listitem>
-<listitem><para>tree (thread tree drawn in the message index and attachment menu)</para></listitem>
-<listitem><para>underline (hiliting underlined patterns in the body of messages)</para></listitem>
-</itemizedlist>
-
-<para>
-<emphasis>foreground</emphasis> and <emphasis>background</emphasis> can be one of the following:
-</para>
-
-<itemizedlist>
-<listitem><para>white</para></listitem>
-<listitem><para>black</para></listitem>
-<listitem><para>green</para></listitem>
-<listitem><para>magenta</para></listitem>
-<listitem><para>blue</para></listitem>
-<listitem><para>cyan</para></listitem>
-<listitem><para>yellow</para></listitem>
-<listitem><para>red</para></listitem>
-<listitem><para>default</para></listitem>
-<listitem><para>color<emphasis>x</emphasis></para>
-</listitem>
-</itemizedlist>
-
-<para>
-<emphasis>foreground</emphasis> can optionally be prefixed with the keyword <literal>bright</literal> to make
-the foreground color boldfaced (e.g., <literal>brightred</literal>).
-</para>
-
-<para>
-If your terminal supports it, the special keyword <emphasis>default</emphasis> can be
-used as a transparent color. The value <emphasis>brightdefault</emphasis> is also valid.
-If Mutt is linked against the <emphasis>S-Lang</emphasis> library, you also need to set
-the <emphasis>COLORFGBG</emphasis> environment variable to the default colors of your
-terminal for this to work; for example (for Bourne-like shells):
-</para>
-
-<screen>
-set COLORFGBG="green;black"
-export COLORFGBG
-</screen>
-
-<note>
-<para>
-The <emphasis>S-Lang</emphasis> library requires you to use the <emphasis>lightgray</emphasis>
-and <emphasis>brown</emphasis> keywords instead of <emphasis>white</emphasis> and <emphasis>yellow</emphasis> when
-setting this variable.
-</para>
-</note>
-
-<note>
-<para>
-The uncolor command can be applied to the index object only. It
-removes entries from the list. You <emphasis role="bold">must</emphasis> specify the same pattern
-specified in the color command for it to be removed. The pattern <quote>*</quote> is
-a special token which means to clear the color index list of all entries.
-</para>
-</note>
-
-<para>
-Mutt also recognizes the keywords <emphasis>color0</emphasis>, <emphasis>color1</emphasis>, …,
-<emphasis>color</emphasis><emphasis role="bold">N-1</emphasis> (<emphasis role="bold">N</emphasis> 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 <emphasis>color2</emphasis>
-for your xterm), since color names may then lose their normal meaning.
-</para>
-
-<para>
-If your terminal does not support color, it is still possible change the video
-attributes through the use of the <quote>mono</quote> command:
-</para>
-
-<anchor id="mono"/>
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>mono</command>
-<arg choice="plain">
-<replaceable class="parameter">object</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>mono</command>
-<group choice="req">
-<arg choice="plain">
-<option>header</option>
-</arg>
-<arg choice="plain">
-<option>body</option>
-</arg>
-</group>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>mono</command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unmono</command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-For <emphasis>object</emphasis>, see the color command. <emphasis>attribute</emphasis>
-can be one of the following:
-</para>
-
-<itemizedlist>
-<listitem><para>none</para></listitem>
-<listitem><para>bold</para></listitem>
-<listitem><para>underline</para></listitem>
-<listitem><para>reverse</para></listitem>
-<listitem><para>standout</para></listitem>
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="ignore">
-<title>Message header display</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>ignore</command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unignore</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-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 in the pager.
-</para>
-
-<para>
-You do not need to specify the full header field name. For example,
-<quote>ignore content-</quote> will ignore all header fields that begin with the pattern
-<quote>content-</quote>. <quote>ignore *</quote> will ignore all headers.
-</para>
-
-<para>
-To remove a previously added token from the list, use the <quote>unignore</quote> command.
-The <quote>unignore</quote> command will make Mutt display headers with the given pattern.
-For example, if you do <quote>ignore x-</quote> it is possible to <quote>unignore x-mailer</quote>.
-</para>
-
-<para>
-<quote>unignore *</quote> will remove all tokens from the ignore list.
-</para>
-
-<para>
-For example:
-</para>
-
-<example id="ex-header-weeding">
-<title>Header weeding</title>
-<screen>
-# 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:
-</screen>
-</example>
-
-<anchor id="hdr-order"/>
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>hdr_order</command>
-<arg choice="plain">
-<replaceable class="parameter">header</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">header</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unhdr_order</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>header</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-With the <literal>hdr_order</literal> command you can specify an order in
-which mutt will attempt to present these headers to you when viewing messages.
-</para>
-
-<para>
-<quote>unhdr_order *</quote> will clear all previous headers from the order list,
-thus removing the header order effects set by the system-wide startup file.
-</para>
-
-<example id="ex-hdr-order">
-<title>Configuring header display order</title>
-<screen>
-hdr_order From Date: From: To: Cc: Subject:
-</screen>
-</example>
-
-</sect1>
-
-<sect1 id="alternates">
-<title>Alternative addresses</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>alternates</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable>regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unalternates</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-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 <link linkend="reply-to">$reply_to</link>.)
-</para>
-
-<para>
-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 <literal>alternates</literal> command: It takes a list of regular
-expressions, each of which can identify an address under which you
-receive e-mail.
-</para>
-
-<para>
-As addresses are matched using regular expressions and not exact strict
-comparisons, you should make sure you specify your addresses as precise
-as possible to avoid mismatches. For example, if you specify:
-</para>
-
-<screen>
-alternates user@example
-</screen>
-
-<para>
-mutt will consider <quote><literal>some-user@example</literal></quote> as
-being your address, too which may not be desired. As a solution, in such
-cases addresses should be specified as:
-</para>
-
-<screen>
-alternates '^user@example$'
-</screen>
-
-<para>
-The <literal>-group</literal> flag causes all of the subsequent regular expressions
-to be added to the named group.
-</para>
-
-<para>
-The <literal>unalternates</literal> command can be used to write exceptions to
-<literal>alternates</literal> patterns. If an address matches something in an
-<literal>alternates</literal> command, but you nonetheless do not think it is
-from you, you can list a more precise pattern under an <literal>unalternates</literal>
-command.
-</para>
-
-<para>
-To remove a regular expression from the <literal>alternates</literal> list, use the
-<literal>unalternates</literal> command with exactly the same <emphasis>regexp</emphasis>.
-Likewise, if the <emphasis>regexp</emphasis> for an <literal>alternates</literal> command matches
-an entry on the <literal>unalternates</literal> list, that <literal>unalternates</literal>
-entry will be removed. If the <emphasis>regexp</emphasis> for <literal>unalternates</literal>
-is <quote>*</quote>, <emphasis>all entries</emphasis> on <literal>alternates</literal> will be removed.
-</para>
-
-</sect1>
-
-<sect1 id="lists">
-<title>Mailing lists</title>
-
-<anchor id="subscribe"/>
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>lists</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unlists</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>subscribe</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unsubscribe</command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-Mutt has a few nice features for <link linkend="using-lists">handling mailing lists</link>. 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 <link linkend="list-reply"><literal><list-reply></literal></link> 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.
-</para>
-
-<note>
-<para>
-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
-<link linkend="followup-to">$followup_to</link>
-configuration variable.
-</para>
-</note>
-
-<para>
-More precisely, Mutt 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 <quote>lists</quote>
-command. To mark it as subscribed, use <quote>subscribe</quote>.
-</para>
-
-<para>
-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
-<quote>subscribe [0-9]*@bugs.guug.de</quote>. Often, it's sufficient to just
-give a portion of the list's e-mail address.
-</para>
-
-<para>
-Specify as much of the address as you need to to remove ambiguity. For
-example, if you've subscribed to the Mutt mailing list, you will receive mail
-addressed to <emphasis>mutt-users@mutt.org</emphasis>. So, to tell Mutt
-that this is a mailing list, you could add <quote>lists mutt-users@</quote> to your
-initialization file. To tell mutt that you are subscribed to it,
-add <quote>subscribe mutt-users</quote> to your initialization file instead.
-If you also happen to get mail from someone whose address is
-<emphasis>mutt-users@example.com</emphasis>, you could use
-<quote>lists ^mutt-users@mutt\\.org$</quote>
-or <quote>subscribe ^mutt-users@mutt\\.org$</quote> to
-match only mail from the actual list.
-</para>
-
-<para>
-The <literal>-group</literal> flag adds all of the subsequent regular expressions
-to the named group.
-</para>
-
-<para>
-The <quote>unlists</quote> command is used to remove a token from the list of
-known and subscribed mailing-lists. Use <quote>unlists *</quote> to remove all
-tokens.
-</para>
-
-<para>
-To remove a mailing list from the list of subscribed mailing lists,
-but keep it on the list of known mailing lists, use <quote>unsubscribe</quote>.
-</para>
-
-</sect1>
-
-<sect1 id="mbox-hook">
-<title>Using Multiple spool mailboxes</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>mbox-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is used to move read messages from a specified mailbox to a
-different mailbox automatically when you quit or change folders.
-<emphasis>pattern</emphasis> is a regular expression specifying the mailbox to treat as a
-<quote>spool</quote> mailbox and <emphasis>mailbox</emphasis> specifies where mail should be saved when
-read.
-</para>
-
-<para>
-Unlike some of the other <emphasis>hook</emphasis> commands, only the <emphasis>first</emphasis> matching
-pattern is used (it is not possible to save read mail in more than a single
-mailbox).
-</para>
-
-</sect1>
-
-<sect1 id="mailboxes">
-<title>Monitoring incoming mail</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>mailboxes</command>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unmailboxes</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-This command specifies folders which can receive mail and
-which will be checked for new messages periodically.
-</para>
-
-<para>
-<emphasis>folder</emphasis> can either be a local file or directory
-(Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP
-support, <emphasis>folder</emphasis> can also be a POP/IMAP folder
-URL. The URL syntax is described in <xref linkend="url-syntax"/>,
-POP and IMAP are described in <xref linkend="pop"/> and <xref linkend="imap"/>
-respectively.
-</para>
-
-<para>
-Mutt provides a number of advanced features for handling (possibly many)
-folders and new mail within them, please refer to
-<xref linkend="handling-folders"/> for details (including in what
-situations and how often Mutt checks for new mail).
-</para>
-
-<para>
-The <quote>unmailboxes</quote> command is used to remove a token from the list
-of folders which receive mail. Use <quote>unmailboxes *</quote> to remove all
-tokens.
-</para>
-
-<note>
-<para>
-The folders in the <literal>mailboxes</literal> command are resolved when
-the command is executed, so if these names contain <link linkend="shortcuts">shortcut characters</link> (such as <quote>=</quote> and <quote>!</quote>), any variable
-definition that affects these characters (like <link linkend="folder">$folder</link> and <link linkend="spoolfile">$spoolfile</link>)
-should be set before the <literal>mailboxes</literal> command. If
-none of these shorcuts are used, a local path should be absolute as
-otherwise mutt tries to find it relative to the directory
-from where mutt was started which may not always be desired.
-</para>
-</note>
-
-<para>
-For Mbox and Mmdf folders, new mail is detected by comparing access and/or
-modification times of files: Mutt assumes a folder has new mail if it wasn't
-accessed after it was last modified. Utilities like <literal>biff</literal> or
-<literal>frm</literal> or any other program which accesses the mailbox might cause
-Mutt to never detect new mail for that mailbox if they do not properly reset the
-access time. Other possible causes of Mutt not detecting new mail in these folders
-are backup tools (updating access times) or filesystems mounted without
-access time update support.
-</para>
-
-<para>
-In cases where new mail detection for Mbox or Mmdf folders appears to be
-unreliable, the
-<link linkend="check-mbox-size">$check_mbox_size</link>
-option can be used to make Mutt track and consult file sizes for new
-mail detection instead.
-</para>
-
-</sect1>
-
-<sect1 id="my-hdr">
-<title>User defined headers</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>my_hdr</command>
-<arg choice="plain">
-<replaceable class="parameter">string</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unmy_hdr</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">field</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-The <literal>my_hdr</literal> command allows you to create your own header
-fields which will be added to every message you send.
-</para>
-
-<para>
-For example, if you would like to add an <quote>Organization:</quote> header field to
-all of your outgoing messages, you can put the command
-</para>
-
-<example id="ex-my-hdr">
-<title>Defining custom headers</title>
-<screen>
-my_hdr Organization: A Really Big Company, Anytown, USA
-</screen>
-</example>
-
-<para>
-in your <literal>.muttrc</literal>.
-</para>
-
-<note>
-<para>
-Space characters are <emphasis>not</emphasis> allowed between the keyword and
-the colon (<quote>:</quote>). The standard for electronic mail (RFC2822) says that
-space is illegal there, so Mutt enforces the rule.
-</para>
-</note>
-
-<para>
-If you would like to add a header field to a single message, you should
-either set the <link linkend="edit-headers">$edit_headers</link> variable,
-or use the <literal><edit-headers></literal> function (default: <quote>E</quote>) in the compose menu so
-that you can edit the header of your message along with the body.
-</para>
-
-<para>
-To remove user defined header fields, use the <literal>unmy_hdr</literal>
-command. You may specify an asterisk (<quote>*</quote>) to remove all header
-fields, or the fields to remove. For example, to remove all <quote>To</quote> and
-<quote>Cc</quote> header fields, you could use:
-</para>
-
-<screen>
-unmy_hdr to cc
-</screen>
-
-</sect1>
-
-<sect1 id="save-hook">
-<title>Specify default save mailbox</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>save-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is used to override the default mailbox used when saving
-messages. <emphasis>mailbox</emphasis> will be used as the default if the message
-matches <emphasis>pattern</emphasis>, see <xref linkend="pattern-hook"/> for information
-on the exact format.
-</para>
-
-<para>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <link linkend="index-format">$index_format</link> to
-<emphasis>mailbox</emphasis> after it was expanded.
-</para>
-
-<para>
-Examples:
-</para>
-
-<example id="ex-save-hook-exando">
-<title>Using %-expandos in <literal>save-hook</literal></title>
-<screen>
-# default: save all to ~/Mail/<author name>
-save-hook . ~/Mail/%F
-
-# save from me@turing.cs.hmc.edu and me@cs.hmc.edu to $folder/elkins
-save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins
-
-# save from aol.com to $folder/spam
-save-hook aol\\.com$ +spam
-</screen>
-</example>
-
-<para>
-Also see the <link linkend="fcc-save-hook">fcc-save-hook</link> command.
-</para>
-
-</sect1>
-
-<sect1 id="fcc-hook">
-<title>Specify default Fcc: mailbox when composing</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>fcc-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is used to save outgoing mail in a mailbox other than
-<link linkend="record">$record</link>. Mutt searches the initial list of
-message recipients for the first matching <emphasis>regexp</emphasis> and uses <emphasis>mailbox</emphasis>
-as the default Fcc: mailbox. If no match is found the message will be saved
-to <link linkend="record">$record</link> mailbox.
-</para>
-
-<para>
-To provide more flexibility and good defaults, Mutt applies the
-expandos of <link linkend="index-format">$index_format</link> to
-<emphasis>mailbox</emphasis> after it was expanded.
-</para>
-
-<para>
-See <xref linkend="pattern-hook"/> for information on the exact format of <emphasis>pattern</emphasis>.
-</para>
-
-<para>
-Example: <literal>fcc-hook [@.]aol\\.com$ +spammers</literal>
-</para>
-
-<para>
-The above will save a copy of all messages going to the aol.com domain to
-the `+spammers' mailbox by default. Also see the <link linkend="fcc-save-hook">fcc-save-hook</link> command.
-</para>
-
-</sect1>
-
-<sect1 id="fcc-save-hook">
-<title>Specify default save filename and default Fcc: mailbox at once</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>fcc-save-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is a shortcut, equivalent to doing both a <link linkend="fcc-hook">fcc-hook</link>
-and a <link linkend="save-hook">save-hook</link> with its arguments,
-including %-expansion on <emphasis>mailbox</emphasis> according
-to <link linkend="index-format">$index_format</link>.
-</para>
-
-</sect1>
-
-<sect1 id="send-hook">
-<title>Change settings based upon message recipients</title>
-
-<anchor id="reply-hook"/>
-<anchor id="send2-hook"/>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>reply-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>send-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>send2-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-These commands can be used to execute arbitrary configuration commands based
-upon recipients of the message. <emphasis>pattern</emphasis> is used to match
-the message, see <xref linkend="pattern-hook"/> for details. <emphasis>command</emphasis>
-is executed when <emphasis>pattern</emphasis> matches.
-</para>
-
-<para>
-<literal>reply-hook</literal> is matched against the message you are <emphasis>replying to</emphasis>,
-instead of the message you are <emphasis>sending</emphasis>. <literal>send-hook</literal> is
-matched against all messages, both <emphasis>new</emphasis>
-and <emphasis>replies</emphasis>.
-</para>
-
-<note>
-<para>
-<literal>reply-hook</literal>s are matched <emphasis role="bold">before</emphasis> the <literal>send-hook</literal>, <emphasis role="bold">regardless</emphasis>
-of the order specified in the user's configuration file.
-</para>
-</note>
-
-<para>
-<literal>send2-hook</literal> is matched every time a message is changed, either
-by editing it, or by using the compose menu to change its recipients
-or subject. <literal>send2-hook</literal> is executed after <literal>send-hook</literal>, and
-can, e.g., be used to set parameters such as the <link linkend="sendmail">$sendmail</link> variable depending on the message's sender
-address.
-</para>
-
-<para>
-For each type of <literal>send-hook</literal> or <literal>reply-hook</literal>, when multiple matches
-occur, commands are executed in the order they are specified in the muttrc
-(for that type of hook).
-</para>
-
-<para>
-Example: <literal>send-hook mutt "set mime_forward signature=''"</literal>
-</para>
-
-<para>
-Another typical use for this command is to change the values of the
-<link linkend="attribution">$attribution</link>, <link linkend="signature">$signature</link> and <link linkend="locale">$locale</link>
-variables in order to change the language of the attributions and
-signatures based upon the recipients.
-</para>
-
-<note>
-<para>
-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
-<literal>my_hdr</literal> 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.
-</para>
-</note>
-
-</sect1>
-
-<sect1 id="message-hook">
-<title>Change settings before formatting a message</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>message-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command can be used to execute arbitrary configuration commands
-before viewing or formatting a message based upon information about the message.
-<emphasis>command</emphasis> is executed if the <emphasis>pattern</emphasis> matches the message to be
-displayed. When multiple matches occur, commands are executed in the order
-they are specified in the muttrc.
-</para>
-
-<para>
-See <xref linkend="pattern-hook"/> for
-information on the exact format of <emphasis>pattern</emphasis>.
-</para>
-
-<para>
-Example:
-</para>
-
-<screen>
-message-hook ~A 'set pager=builtin'
-message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
-</screen>
-
-</sect1>
-
-<sect1 id="crypt-hook">
-<title>Choosing the cryptographic key of the recipient</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>crypt-hook</command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">keyid</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-When encrypting messages with PGP/GnuPG 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 would
-normally use. The <literal>crypt-hook</literal> 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.
-</para>
-
-<para>
-The meaning of <emphasis>keyid</emphasis> 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.
-</para>
-
-</sect1>
-
-<sect1 id="push">
-<title>Adding key sequences to the keyboard buffer</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>push</command>
-<arg choice="plain">
-<replaceable class="parameter">string</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-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 <link linkend="macro">macro</link> 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:
-</para>
-
-<example id="ex-folder-hook-push">
-<title>Embedding <literal>push</literal> in <literal>folder-hook</literal></title>
-<screen>
-folder-hook . 'push <collapse-all>'
-</screen>
-</example>
-
-</sect1>
-
-<sect1 id="exec">
-<title>Executing functions</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>exec</command>
-<arg choice="plain">
-<replaceable class="parameter">function</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">function</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command can be used to execute any function. Functions are
-listed in the <link linkend="functions">function reference</link>.
-<quote>exec function</quote> is equivalent to <quote>push <function></quote>.
-</para>
-
-</sect1>
-
-<sect1 id="score-command">
-<title>Message Scoring</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>score</command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">value</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unscore</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-The <literal>score</literal> commands adds <emphasis>value</emphasis> to a message's score if <emphasis>pattern</emphasis>
-matches it. <emphasis>pattern</emphasis> is a string in the format described in the <link linkend="patterns">patterns</link> section (note: For efficiency reasons, patterns
-which scan information not available in the index, such as <literal>˜b</literal>,
-<literal>˜B</literal> or <literal>˜h</literal>, may not be used). <emphasis>value</emphasis> is a
-positive or negative integer. A message's final score is the sum total of all
-matching <literal>score</literal> entries. However, you may optionally prefix <emphasis>value</emphasis> with
-an equal sign (=) to cause evaluation to stop at a particular entry if there is
-a match. Negative final scores are rounded up to 0.
-</para>
-
-<para>
-The <literal>unscore</literal> command removes score entries from the list. You <emphasis role="bold">must</emphasis>
-specify the same pattern specified in the <literal>score</literal> command for it to be
-removed. The pattern <quote>*</quote> is a special token which means to clear the list
-of all score entries.
-</para>
-
-</sect1>
-
-<sect1 id="spam">
-<title>Spam detection</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>spam</command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">format</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>nospam</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-Mutt has generalized support for external spam-scoring filters.
-By defining your spam patterns with the <literal>spam</literal> and <literal>nospam</literal>
-commands, you can <emphasis>limit</emphasis>, <emphasis>search</emphasis>, and <emphasis>sort</emphasis> 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 <literal>%H</literal> selector in the <link linkend="index-format">$index_format</link> variable. (Tip: try <literal>%?H?[%H] ?</literal>
-to display spam tags only when they are defined for a given message.)
-</para>
-
-<para>
-Your first step is to define your external filter's spam patterns using
-the <literal>spam</literal> command. <emphasis>pattern</emphasis> 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 <quote>spam tag</quote> or
-<quote>spam attribute</quote> (unless it also matches a <literal>nospam</literal> pattern -- see
-below.) The appearance of this attribute is entirely up to you, and is
-governed by the <emphasis>format</emphasis> parameter. <emphasis>format</emphasis> can be any static
-text, but it also can include back-references from the <emphasis>pattern</emphasis>
-expression. (A regular expression <quote>back-reference</quote> refers to a
-sub-expression contained within parentheses.) <literal>%1</literal> is replaced with
-the first back-reference in the regex, <literal>%2</literal> with the second, etc.
-</para>
-
-<para>
-If you're using multiple spam filters, a message can have more than
-one spam-related header. You can define <literal>spam</literal> 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 <emphasis>format</emphasis> strings joined
-together, with the value of $spam_separator separating
-them.
-</para>
-
-<para>
-For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
-define these spam settings:
-</para>
-
-<example id="ex-spam">
-<title>Configuring spam detection</title>
-<screen>
-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=", "
-</screen>
-</example>
-
-<para>
-If I then received a message that DCC registered with <quote>many</quote> hits
-under the <quote>Fuz2</quote> checksum, and that PureMessage registered with a
-97% probability of being spam, that message's spam tag would read
-<literal>90+/DCC-Fuz2, 97/PM</literal>. (The four characters before <quote>=many</quote> in a
-DCC report indicate the checksum used -- in this case, <quote>Fuz2</quote>.)
-</para>
-
-<para>
-If the $spam_separator variable is unset, then each
-spam pattern match supersedes the previous one. Instead of getting
-joined <emphasis>format</emphasis> strings, you'll get only the last one to match.
-</para>
-
-<para>
-The spam tag is what will be displayed in the index when you use
-<literal>%H</literal> in the <literal>$index_format</literal> variable. It's also the
-string that the <literal>˜H</literal> pattern-matching expression matches against for
-<literal><search></literal> and <literal><limit></literal> functions. And it's what sorting by spam
-attribute will use as a sort key.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-Generally, when you sort by spam tag, mutt will sort <emphasis>lexically</emphasis> --
-that is, by ordering strings alphanumerically. 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
-<literal>sort -n</literal>.) A message with no spam attributes at all -- that is, one
-that didn't match <emphasis>any</emphasis> of your <literal>spam</literal> patterns -- is sorted at
-lowest priority. Numbers are sorted next, beginning with 0 and ranging
-upward. Finally, non-numeric strings are sorted, with <quote>a</quote> taking lower
-priority than <quote>z</quote>. 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.
-</para>
-
-<para>
-The <literal>nospam</literal> command can be used to write exceptions to <literal>spam</literal>
-patterns. If a header pattern matches something in a <literal>spam</literal> command,
-but you nonetheless do not want it to receive a spam tag, you can list a
-more precise pattern under a <literal>nospam</literal> command.
-</para>
-
-<para>
-If the <emphasis>pattern</emphasis> given to <literal>nospam</literal> is exactly the same as the
-<emphasis>pattern</emphasis> on an existing <literal>spam</literal> list entry, the effect will be to
-remove the entry from the spam list, instead of adding an exception.
-Likewise, if the <emphasis>pattern</emphasis> for a <literal>spam</literal> command matches an entry
-on the <literal>nospam</literal> list, that <literal>nospam</literal> entry will be removed. If the
-<emphasis>pattern</emphasis> for <literal>nospam</literal> is <quote>*</quote>, <emphasis>all entries on both lists</emphasis>
-will be removed. This might be the default action if you use <literal>spam</literal>
-and <literal>nospam</literal> in conjunction with a <literal>folder-hook</literal>.
-</para>
-
-<para>
-You can have as many <literal>spam</literal> or <literal>nospam</literal> commands as you like.
-You can even do your own primitive spam detection within mutt -- for
-example, if you consider all mail from <literal>MAILER-DAEMON</literal> to be spam,
-you can use a <literal>spam</literal> command like this:
-</para>
-
-<screen>
-spam "^From: .*MAILER-DAEMON" "999"
-</screen>
-
-</sect1>
-
-<sect1 id="set">
-<title>Setting and Querying Variables</title>
-
-<sect2 id="set-commands">
-<title>Commands</title>
-
-<para>
-The following commands are available to manipulate and query variables:
-</para>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>set</command>
-<group choice="req">
-<arg choice="plain">
-<group choice="opt">
-<arg choice="plain"><option>no</option></arg>
-<arg choice="plain"><option>inv</option></arg>
-</group>
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">variable=value</replaceable>
-</arg>
-</group>
-<arg choice="opt" rep="repeat"/>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>toggle</command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>unset</command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-
-<cmdsynopsis>
-<command>reset</command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command is used to set (and unset) <link linkend="variables">configuration variables</link>. There are four basic types of variables:
-boolean, number, string and quadoption. <emphasis>boolean</emphasis> variables can be
-<emphasis>set</emphasis> (true) or <emphasis>unset</emphasis> (false). <emphasis>number</emphasis> variables can be
-assigned a positive integer value.
-<emphasis>string</emphasis> variables consist of any number of printable characters and
-must be enclosed in quotes if they contain spaces or tabs. You
-may also use the escape sequences <quote>\n</quote> and <quote>\t</quote> for newline and tab, respectively.
-<emphasis>quadoption</emphasis> variables are used to control whether or not to be prompted
-for certain actions, or to specify a default action. A value of <emphasis>yes</emphasis>
-will cause the action to be carried out automatically as if you had answered
-yes to the question. Similarly, a value of <emphasis>no</emphasis> will cause the
-action to be carried out as if you had answered <quote>no.</quote> A value of
-<emphasis>ask-yes</emphasis> will cause a prompt with a default answer of <quote>yes</quote> and
-<emphasis>ask-no</emphasis> will provide a default answer of <quote>no.</quote>
-</para>
-
-<para>
-Prefixing a variable with <quote>no</quote> will unset it. Example: <literal>set noaskbcc</literal>.
-</para>
-
-<para>
-For <emphasis>boolean</emphasis> variables, you may optionally prefix the variable name with
-<literal>inv</literal> to toggle the value (on or off). This is useful when writing
-macros. Example: <literal>set invsmart_wrap</literal>.
-</para>
-
-<para>
-The <literal>toggle</literal> command automatically prepends the <literal>inv</literal> prefix to all
-specified variables.
-</para>
-
-<para>
-The <literal>unset</literal> command automatically prepends the <literal>no</literal> prefix to all
-specified variables.
-</para>
-
-<para>
-Using the <literal><enter-command></literal> function in the <emphasis>index</emphasis> menu, you can query the
-value of a variable by prefixing the name of the variable with a question
-mark:
-</para>
-
-<screen>
-set ?allow_8bit
-</screen>
-
-<para>
-The question mark is actually only required for boolean and quadoption
-variables.
-</para>
-
-<para>
-The <literal>reset</literal> command resets all given variables to the compile time
-defaults (hopefully mentioned in this manual). If you use the command
-<literal>set</literal> and prefix the variable with <quote>&</quote> this has the same
-behavior as the reset command.
-</para>
-
-<para>
-With the <literal>reset</literal> command there exists the special variable <quote>all</quote>,
-which allows you to reset all variables to their system defaults.
-</para>
-
-</sect2>
-
-<sect2 id="set-myvar">
-<title>User-defined variables</title>
-
-<sect3 id="set-myvar-intro">
-<title>Introduction</title>
-
-<para>
-Along with the variables listed in the
-<link linkend="variables">Configuration variables</link> section, mutt
-supports user-defined variables with names starting
-with <literal>my_</literal> as in, for
-example, <literal>my_cfgdir</literal>.
-</para>
-
-<para>
-The <literal>set</literal> command either creates a
-custom <literal>my_</literal> variable or changes its
-value if it does exist already. The <literal>unset</literal> and <literal>reset</literal>
-commands remove the variable entirely.
-</para>
-
-<para>
-Since user-defined variables are expanded in the same way that
-environment variables are (except for
-the <link linkend="shell-escape">shell-escape</link> command and
-backtick expansion), this feature can be used to make configuration
-files more readable.
-</para>
-
-</sect3>
-
-<sect3 id="set-myvar-examples">
-<title>Examples</title>
-
-<para>
-The following example defines and uses the variable <literal>my_cfgdir</literal>
-to abbreviate the calls of the <link linkend="source">source</link> command:
-</para>
-
-<example id="ex-myvar1">
-<title>Using user-defined variables for config file readability</title>
-<screen>
-set my_cfgdir = $HOME/mutt/config
-
-source $my_cfgdir/hooks
-source $my_cfgdir/macros
-# more source commands...
-</screen>
-</example>
-
-<para>
-A custom variable can also be used in macros to backup the current value
-of another variable. In the following example, the value of the
-<link linkend="delete">$delete</link> is changed temporarily
-while its original value is saved as <literal>my_delete</literal>.
-After the macro has executed all commands, the original value of <link
-linkend="delete">$delete</link> is restored.
-</para>
-
-<example id="ex-myvar2">
-<title>Using user-defined variables for backing up other config option values</title>
-<screen>
-macro pager ,x '\
-<enter-command>set my_delete=$delete<enter>\
-<enter-command>set delete=yes<enter>\
-...\
-<enter-command>set delete=$my_delete<enter>'
-</screen>
-</example>
-
-<para>
-Since mutt expands such values already when parsing the configuration
-file(s), the value of <literal>$my_delete</literal> in the
-last example would be the value of <literal>$delete</literal> exactly
-as it was at that point during parsing the configuration file. If
-another statement would change the value for <literal>$delete</literal>
-later in the same or another file, it would have no effect on
-<literal>$my_delete</literal>. However, the expansion can
-be deferred to runtime, as shown in the next example, when escaping the
-dollar sign.
-</para>
-
-<example id="ex-myvar3">
-<title>Deferring user-defined variable expansion to runtime</title>
-<screen>
-macro pager <PageDown> "\
-<enter-command> set my_old_pager_stop=\$pager_stop pager_stop<Enter>\
-<next-page>\
-<enter-command> set pager_stop=\$my_old_pager_stop<Enter>\
-<enter-command> unset my_old_pager_stop<Enter>"
-</screen>
-</example>
-
-<para>
-Note that there is a space
-between <literal><enter-command></literal> and
-the <literal>set</literal> configuration command, preventing mutt from
-recording the macro's commands into its history.
-</para>
-
-</sect3>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="source">
-<title>Reading initialization commands from another file</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>source</command>
-<arg choice="plain">
-<replaceable class="parameter">filename</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-This command allows the inclusion of initialization commands
-from other files. For example, I place all of my aliases in
-<literal>˜/.mail_aliases</literal> so that I can make my
-<literal>˜/.muttrc</literal> readable and keep my aliases private.
-</para>
-
-<para>
-If the filename begins with a tilde (<quote>˜</quote>), it will be expanded to the
-path of your home directory.
-</para>
-
-<para>
-If the filename ends with a vertical bar (|), then <emphasis>filename</emphasis> is
-considered to be an executable program from which to read input (eg.
-<literal>source ˜/bin/myscript|</literal>).
-</para>
-
-</sect1>
-
-<sect1 id="ifdef">
-
-<title>Configuring features conditionnaly</title>
-
-<para>
-Usage: <literal>ifdef</literal> <emphasis>item</emphasis> <emphasis>command</emphasis>
-</para>
-
-<para>
-This command allows to test if a feature has been compiled in, before
-actually executing the command. Item can be either the name of a
-function, variable, or command. Example:
-</para>
-
-<para>
-<screen>
-ifdef imap_keepalive 'source ~/.mutt/imap_setup'
-</screen>
-</para>
-
-</sect1>
-
-<sect1 id="unhook">
-<title>Removing hooks</title>
-
-<para>Usage:</para>
-
-<cmdsynopsis>
-<command>unhook</command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">hook-type</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-
-<para>
-This command permits you to flush hooks you have previously defined.
-You can either remove all hooks by giving the <quote>*</quote> character as an
-argument, or you can remove all hooks of a specific type by saying
-something like <literal>unhook send-hook</literal>.
-</para>
-
-</sect1>
-
-<sect1 id="formatstrings">
-<title>Format Strings</title>
-
-<sect2 id="formatstrings-basics">
-<title>Basic usage</title>
-
-<para>
-Format strings are a general concept you'll find in several locations
-through the mutt configuration, especially in the
-<link linkend="index-format">$index_format</link>,
-<link linkend="pager-format">$pager_format</link>,
-<link linkend="status-format">$status_format</link>,
-and other <quote>*_format</quote> variables. These can be very straightforward,
-and it's quite possible you already know how to use them.
-</para>
-
-<para>
-The most basic format string element is a percent symbol followed
-by another character. For example, <literal>%s</literal>
-represents a message's Subject: header in the <link
-linkend="index-format">$index_format</link> variable. The
-<quote>expandos</quote> available are documented with each format variable, but
-there are general modifiers available with all formatting expandos,
-too. Those are our concern here.
-</para>
-
-<para>
-Some of the modifiers are borrowed right out of C (though you might
-know them from Perl, Python, shell, or another language). These are
-the [-]m.n modifiers, as in <literal>%-12.12s</literal>. As with
-such programming languages, these modifiers allow you to specify the
-minimum and maximum size of the resulting string, as well as its
-justification. If the <quote>-</quote> sign follows the percent, the string will
-be left-justified instead of right-justified. If there's a number
-immediately following that, it's the minimum amount of space the
-formatted string will occupy -- if it's naturally smaller than that, it
-will be padded out with spaces. If a decimal point and another number
-follow, that's the maximum space allowable -- the string will not be
-permitted to exceed that width, no matter its natural size. Each of
-these three elements is optional, so that all these are legal format
-strings:
-<literal>%-12s</literal>
-<literal>%4c</literal>
-<literal>%.15F</literal>
-<literal>%-12.15L</literal>
-</para>
-
-<para>
-Mutt adds some other modifiers to format strings. If you use an equals
-symbol (<literal>=</literal>) as a numeric prefix (like the minus
-above), it will force the string to be centered within its minimum
-space range. For example, <literal>%=14y</literal> will reserve 14
-characters for the %y expansion -- that's the X-Label: header, in
-<literal>$index_format</literal>. If the expansion
-results in a string less than 14 characters, it will be centered in a
-14-character space. If the X-Label for a message were "test", that
-expansion would look like <quote> test </quote>.
-</para>
-
-<para>
-There are two very little-known modifiers that affect the way that an
-expando is replaced. If there is an underline (<quote>_</quote>) character
-between any format modifiers (as above) and the expando letter, it will
-expands in all lower case. And if you use a colon (<quote>:</quote>), it will
-replace all decimal points with underlines.
-</para>
-
-</sect2>
-
-<sect2 id="formatstrings-filters">
-<title>Filters</title>
-
-<para>
-Any format string ending in a vertical bar (<quote>|</quote>) will be
-expanded and piped through the first word in the string, using spaces
-as separator. The string returned will be used for display.
-If the returned string ends in %, it will be passed through
-the formatter a second time. This allows the filter to generate a
-replacement format string including % expandos.
-</para>
-
-<para>
-All % expandos in a format string are expanded before the script
-is called so that:
-</para>
-
-<example id="ex-fmtpipe">
-<title>Using external filters in format strings</title>
-<screen>
-set status_format="script.sh '%r %f (%L)'|"
-</screen>
-</example>
-
-<para>
-will make mutt expand <literal>%r</literal>,
-<literal>%f</literal> and <literal>%L</literal>
-before calling the script. The example also shows that arguments can be
-quoted: the script will receive the expanded string between the single quotes
-as the only argument.
-</para>
-
-<para>
-A practical example is the <literal>mutt_xtitle</literal>
-script installed in the <literal>samples</literal>
-subdirectory of the mutt documentation: it can be used as filter for
-<literal>$status_format</literal> to set the current
-terminal's title, if supported.
-</para>
-
-</sect2>
-
-</sect1>
-
-</chapter>
-
-<chapter id="advancedusage">
-<title>Advanced Usage</title>
-
-<sect1 id="regexp">
-<title>Regular Expressions</title>
-
-<para>
-All string patterns in Mutt including those in more complex
-<link linkend="patterns">patterns</link> must be specified
-using regular expressions (regexp) in the <quote>POSIX extended</quote> 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.
-</para>
-
-<para>
-The search is case sensitive if the pattern contains at least one upper
-case letter, and case insensitive otherwise.
-</para>
-
-<note>
-<para>
-Note that <quote>\</quote>
-must be quoted if used for a regular expression in an initialization
-command: <quote>\\</quote>.
-</para>
-</note>
-
-<para>
-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.
-</para>
-
-<note>
-<para>
-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 <xref linkend="muttrc-syntax"/>
-for more information on " and ' delimiter processing. To match a
-literal " or ' you must preface it with \ (backslash).
-</para>
-</note>
-
-<para>
-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.
-</para>
-
-<para>
-The period <quote>.</quote> matches any single character. The caret <quote>ˆ</quote> and
-the dollar sign <quote>$</quote> are metacharacters that respectively match
-the empty string at the beginning and end of a line.
-</para>
-
-<para>
-A list of characters enclosed by <quote>[</quote> and <quote>]</quote> matches any
-single character in that list; if the first character of the list
-is a caret <quote>ˆ</quote> then it matches any character <emphasis role="bold">not</emphasis> in the
-list. For example, the regular expression <emphasis role="bold">[0123456789]</emphasis>
-matches any single digit. A range of ASCII characters may be specified
-by giving the first and last characters, separated by a hyphen
-<quote>-</quote>. Most metacharacters lose their special meaning inside
-lists. To include a literal <quote>]</quote> place it first in the list.
-Similarly, to include a literal <quote>ˆ</quote> place it anywhere but first.
-Finally, to include a literal hyphen <quote>-</quote> place it last.
-</para>
-
-<para>
-Certain named classes of characters are predefined. Character classes
-consist of <quote>[:</quote>, a keyword denoting the class, and <quote>:]</quote>.
-The following classes are defined by the POSIX standard in
-<xref linkend="posix-regex-char-classes"/>
-</para>
-
-<table id="posix-regex-char-classes">
-<title>POSIX regular expression character classes</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Character class</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>[:alnum:]</entry><entry>Alphanumeric characters</entry></row>
-<row><entry>[:alpha:]</entry><entry>Alphabetic characters</entry></row>
-<row><entry>[:blank:]</entry><entry>Space or tab characters</entry></row>
-<row><entry>[:cntrl:]</entry><entry>Control characters</entry></row>
-<row><entry>[:digit:]</entry><entry>Numeric characters</entry></row>
-<row><entry>[:graph:]</entry><entry>Characters that are both printable and visible. (A space is printable, but not visible, while an <quote>a</quote> is both)</entry></row>
-<row><entry>[:lower:]</entry><entry>Lower-case alphabetic characters</entry></row>
-<row><entry>[:print:]</entry><entry>Printable characters (characters that are not control characters)</entry></row>
-<row><entry>[:punct:]</entry><entry>Punctuation characters (characters that are not letter, digits, control characters, or space characters)</entry></row>
-<row><entry>[:space:]</entry><entry>Space characters (such as space, tab and formfeed, to name a few)</entry></row>
-<row><entry>[:upper:]</entry><entry>Upper-case alphabetic characters</entry></row>
-<row><entry>[:xdigit:]</entry><entry>Characters that are hexadecimal digits</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-A character class is only valid in a regular expression inside the
-brackets of a character list.
-</para>
-
-<note>
-<para>
-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, <emphasis role="bold">[[:digit:]]</emphasis> is equivalent to
-<emphasis role="bold">[0-9]</emphasis>.
-</para>
-</note>
-
-<para>
-Two additional special sequences can appear in character lists. These
-apply to non-ASCII character sets, which can have single symbols (called
-collating elements) that are represented with more than one character,
-as well as several characters that are equivalent for collating or
-sorting purposes:
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>Collating Symbols</term>
-<listitem>
-<para>
-A collating symbol is a multi-character collating element enclosed in
-<quote>[.</quote> and <quote>.]</quote>. For example, if <quote>ch</quote> is a collating
-element, then <emphasis role="bold">[[.ch.]]</emphasis> is a regexp that matches
-this collating element, while <emphasis role="bold">[ch]</emphasis> is a regexp that
-matches either <quote>c</quote> or <quote>h</quote>.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>Equivalence Classes</term>
-<listitem>
-<para>
-An equivalence class is a locale-specific name for a list of
-characters that are equivalent. The name is enclosed in <quote>[=</quote>
-and <quote>=]</quote>. For example, the name <quote>e</quote> might be used to
-represent all of <quote>è</quote> <quote>é</quote> and <quote>e</quote>. In this case,
-<emphasis role="bold">[[=e=]]</emphasis> is a regexp that matches any of
-<quote>è</quote>, <quote>é</quote> and <quote>e</quote>.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-<para>
-A regular expression matching a single character may be followed by one
-of several repetition operators described in <xref linkend="regex-repeat"/>.
-</para>
-
-<table id="regex-repeat">
-<title>Regular expression repetition operators</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Operator</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>?</entry><entry>The preceding item is optional and matched at most once</entry></row>
-<row><entry>*</entry><entry>The preceding item will be matched zero or more times</entry></row>
-<row><entry>+</entry><entry>The preceding item will be matched one or more times</entry></row>
-<row><entry>{n}</entry><entry>The preceding item is matched exactly <emphasis>n</emphasis> times</entry></row>
-<row><entry>{n,}</entry><entry>The preceding item is matched <emphasis>n</emphasis> or more times</entry></row>
-<row><entry>{,m}</entry><entry>The preceding item is matched at most <emphasis>m</emphasis> times</entry></row>
-<row><entry>{n,m}</entry><entry>The preceding item is matched at least <emphasis>n</emphasis> times, but no more than <emphasis>m</emphasis> times</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Two regular expressions may be concatenated; the resulting regular
-expression matches any string formed by concatenating two substrings
-that respectively match the concatenated subexpressions.
-</para>
-
-<para>
-Two regular expressions may be joined by the infix operator <quote>|</quote>;
-the resulting regular expression matches any string matching either
-subexpression.
-</para>
-
-<para>
-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.
-</para>
-
-<note>
-<para>
-If you compile Mutt with the GNU <emphasis>rx</emphasis> package, the
-following operators may also be used in regular expressions as described in <xref linkend="regex-gnu-ext"/>.
-</para>
-</note>
-
-<table id="regex-gnu-ext">
-<title>GNU regular expression extensions</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Expression</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>\\y</entry><entry>Matches the empty string at either the beginning or the end of a word</entry></row>
-<row><entry>\\B</entry><entry>Matches the empty string within a word</entry></row>
-<row><entry>\\<</entry><entry>Matches the empty string at the beginning of a word</entry></row>
-<row><entry>\\></entry><entry>Matches the empty string at the end of a word</entry></row>
-<row><entry>\\w</entry><entry>Matches any word-constituent character (letter, digit, or underscore)</entry></row>
-<row><entry>\\W</entry><entry>Matches any character that is not word-constituent</entry></row>
-<row><entry>\\`</entry><entry>Matches the empty string at the beginning of a buffer (string)</entry></row>
-<row><entry>\\'</entry><entry>Matches the empty string at the end of a buffer</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-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.
-</para>
-
-</sect1>
-
-<sect1 id="patterns">
-<title>Patterns: Searching, Limiting and Tagging</title>
-
-<para>
-Many of Mutt's commands allow you to specify a pattern to match
-(<literal>limit</literal>, <literal>tag-pattern</literal>,
-<literal>delete-pattern</literal>, etc.). <xref linkend="tab-patterns"/>
-shows several ways to select messages.
-</para>
-
-<table id="tab-patterns">
-<title>Pattern modifiers</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Pattern modifier</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>~A</entry><entry>all messages</entry></row>
-<row><entry>~b <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the message body</entry></row>
-<row><entry>=b <emphasis>STRING</emphasis></entry><entry>messages which contain <emphasis>STRING</emphasis> in the message body. If IMAP is enabled, searches for <emphasis>STRING</emphasis> on the server, rather than downloading each message and searching it locally.</entry></row>
-<row><entry>~B <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the whole message</entry></row>
-<row><entry>~c <emphasis>EXPR</emphasis></entry><entry>messages carbon-copied to <emphasis>EXPR</emphasis></entry></row>
-<row><entry>%c <emphasis>GROUP</emphasis></entry><entry>messages carbon-copied to any member of <emphasis>GROUP</emphasis></entry></row>
-<row><entry>~C <emphasis>EXPR</emphasis></entry><entry>messages either to: or cc: <emphasis>EXPR</emphasis></entry></row>
-<row><entry>%C <emphasis>GROUP</emphasis></entry><entry>messages either to: or cc: to any member of <emphasis>GROUP</emphasis></entry></row>
-<row><entry>~d [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with <quote>date-sent</quote> in a Date range</entry></row>
-<row><entry>~D</entry><entry>deleted messages</entry></row>
-<row><entry>~e <emphasis>EXPR</emphasis></entry><entry>messages which contains <emphasis>EXPR</emphasis> in the <quote>Sender</quote> field</entry></row>
-<row><entry>%e <emphasis>GROUP</emphasis></entry><entry>messages which contain a member of <emphasis>GROUP</emphasis> in the <quote>Sender</quote> field</entry></row>
-<row><entry>~E</entry><entry>expired messages</entry></row>
-<row><entry>~F</entry><entry>flagged messages</entry></row>
-<row><entry>~f <emphasis>EXPR</emphasis></entry><entry>messages originating from <emphasis>EXPR</emphasis></entry></row>
-<row><entry>%f <emphasis>GROUP</emphasis></entry><entry>messages originating from any member of <emphasis>GROUP</emphasis></entry></row>
-<row><entry>~g</entry><entry>cryptographically signed messages</entry></row>
-<row><entry>~G</entry><entry>cryptographically encrypted messages</entry></row>
-<row><entry>~h <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the message header</entry></row>
-<row><entry>~H <emphasis>EXPR</emphasis></entry><entry>messages with a spam attribute matching <emphasis>EXPR</emphasis></entry></row>
-<row><entry>~i <emphasis>EXPR</emphasis></entry><entry>messages which match <emphasis>EXPR</emphasis> in the <quote>Message-ID</quote> field</entry></row>
-<row><entry>~k</entry><entry>messages which contain PGP key material</entry></row>
-<row><entry>~L <emphasis>EXPR</emphasis></entry><entry>messages either originated or received by <emphasis>EXPR</emphasis></entry></row>
-<row><entry>%L <emphasis>GROUP</emphasis></entry><entry>message either originated or received by any member of <emphasis>GROUP</emphasis></entry></row>
-<row><entry>~l</entry><entry>messages addressed to a known mailing list</entry></row>
-<row><entry>~m [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *)</entry></row>
-<row><entry>~n [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with a score in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *)</entry></row>
-<row><entry>~N</entry><entry>new messages</entry></row>
-<row><entry>~O</entry><entry>old messages</entry></row>
-<row><entry>~p</entry><entry>messages addressed to you (consults alternates)</entry></row>
-<row><entry>~P</entry><entry>messages from you (consults alternates)</entry></row>
-<row><entry>~Q</entry><entry>messages which have been replied to</entry></row>
-<row><entry>~r [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with <quote>date-received</quote> in a Date range</entry></row>
-<row><entry>~R</entry><entry>read messages</entry></row>
-<row><entry>~s <emphasis>EXPR</emphasis></entry><entry>messages having <emphasis>EXPR</emphasis> in the <quote>Subject</quote> field.</entry></row>
-<row><entry>~S</entry><entry>superseded messages</entry></row>
-<row><entry>~t <emphasis>EXPR</emphasis></entry><entry>messages addressed to <emphasis>EXPR</emphasis></entry></row>
-<row><entry>~T</entry><entry>tagged messages</entry></row>
-<row><entry>~u</entry><entry>messages addressed to a subscribed mailing list</entry></row>
-<row><entry>~U</entry><entry>unread messages</entry></row>
-<row><entry>~v</entry><entry>messages part of a collapsed thread.</entry></row>
-<row><entry>~V</entry><entry>cryptographically verified messages</entry></row>
-<row><entry>~x <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the <quote>References</quote> field</entry></row>
-<row><entry>~X [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> attachments *)</entry></row>
-<row><entry>~y <emphasis>EXPR</emphasis></entry><entry>messages which contain <emphasis>EXPR</emphasis> in the <quote>X-Label</quote> field</entry></row>
-<row><entry>~z [<emphasis>MIN</emphasis>]-[<emphasis>MAX</emphasis>]</entry><entry>messages with a size in the range <emphasis>MIN</emphasis> to <emphasis>MAX</emphasis> *)</entry></row>
-<row><entry>~=</entry><entry>duplicated messages (see <link linkend="duplicate-threads">$duplicate_threads</link>)</entry></row>
-<row><entry>~$</entry><entry>unreferenced messages (requires threaded view)</entry></row>
-<row><entry>~(<emphasis>PATTERN</emphasis>)</entry><entry>messages in threads
-containing messages matching <emphasis>PATTERN</emphasis>, e.g. all
-threads containing messages from you: ~(~P)</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Where <emphasis>EXPR</emphasis> is a
-<link linkend="regexp">regular expression</link>. Special attention has to be
-made when using regular expressions inside of patterns. Specifically,
-Mutt's parser for these patterns will strip one level of backslash (<quote>\</quote>),
-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 (<quote>\\</quote>). You can force mutt to treat <emphasis>EXPR</emphasis> as a simple string
-instead of a regular expression by using = instead of ˜ in the
-pattern name. For example, <literal>=b *.*</literal> will find all messages that contain
-the literal string <quote>*.*</quote>. Simple string matches are less powerful than
-regular expressions but can be considerably faster. This is especially
-true for IMAP folders, because string matches can be performed on the
-server instead of by fetching every message. IMAP treats <literal>=h</literal> specially:
-it must be of the form "header: substring" and will not partially
-match header names. The substring part may be omitted if you simply
-wish to find messages containing a particular header without regard to
-its value.
-</para>
-
-<para>
-*) The forms <quote><[<emphasis>MAX</emphasis>]</quote>, <quote>>[<emphasis>MIN</emphasis>]</quote>,
-<quote>[<emphasis>MIN</emphasis>]-</quote> and <quote>-[<emphasis>MAX</emphasis>]</quote>
-are allowed, too.
-</para>
-
-<sect2 id="patterns-modifier">
-<title>Pattern Modifier</title>
-
-<note>
-<para>
-Note that patterns matching 'lists' of addresses (notably c, C, p, P and t)
-match if there is at least one match in the whole list. If you want to
-make sure that all elements of that list match, you need to prefix your
-pattern with <quote>ˆ</quote>.
-This example matches all mails which only has recipients from Germany.
-</para>
-</note>
-
-<screen>
-^~C \.de$
-</screen>
-
-</sect2>
-
-<sect2 id="simple-patterns">
-<title>Simple Patterns</title>
-
-<para>
-Mutt supports two versions of so called <quote>simple searches</quote> which are
-issued if the query entered for searching, limiting and similar
-operations does not seem to be a valid pattern (i.e. it does not contain
-one of these characters: <quote>˜</quote>, <quote>=</quote> or <quote>%</quote>). If the query is
-supposed to contain one of these special characters, they must be escaped
-by prepending a backslash (<quote>\</quote>).
-</para>
-
-<para>
-The first type is by checking whether the query string equals
-a keyword case-insensitively from <xref linkend="tab-simplesearch-keywords"/>:
-If that is the case, Mutt will use the shown pattern modifier instead.
-If a keyword would conflict with your search keyword, you need to turn
-it into a regular expression to avoid matching the keyword table. For
-example, if you want to find all messages matching <quote>flag</quote>
-(using <link linkend="simple-search">$simple_search</link>)
-but don't want to match flagged messages, simply search for
-<quote><literal>[f]lag</literal></quote>.
-</para>
-
-<table id="tab-simplesearch-keywords">
-<title>Simple search keywords</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Keyword</entry><entry>Pattern modifier</entry></row>
-</thead>
-<tbody>
-<row><entry>all</entry><entry>~A</entry></row>
-<row><entry>.</entry><entry>~A</entry></row>
-<row><entry>ˆ</entry><entry>~A</entry></row>
-<row><entry>del</entry><entry>~D</entry></row>
-<row><entry>flag</entry><entry>~F</entry></row>
-<row><entry>new</entry><entry>~N</entry></row>
-<row><entry>old</entry><entry>~O</entry></row>
-<row><entry>repl</entry><entry>~Q</entry></row>
-<row><entry>read</entry><entry>~R</entry></row>
-<row><entry>tag</entry><entry>~T</entry></row>
-<row><entry>unread</entry><entry>~U</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-The second type of simple search is to build a complex search
-pattern using <link linkend="simple-search">$simple_search</link>
-as a template. Mutt will insert your query properly quoted and search
-for the composed complex query.
-</para>
-
-</sect2>
-
-<sect2 id="complex-patterns">
-<title>Complex Patterns</title>
-
-<para>
-Logical AND is performed by specifying more than one criterion. For
-example:
-</para>
-
-<screen>
-~t mutt ~f elkins
-</screen>
-
-<para>
-would select messages which contain the word <quote>mutt</quote> in the list of
-recipients <emphasis role="bold">and</emphasis> that have the word <quote>elkins</quote> in the <quote>From</quote> header
-field.
-</para>
-
-<para>
-Mutt also recognizes the following operators to create more complex search
-patterns:
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-! -- logical NOT operator
-</para>
-</listitem>
-<listitem>
-
-<para>
-| -- logical OR operator
-</para>
-</listitem>
-<listitem>
-
-<para>
-() -- logical grouping operator
-</para>
-</listitem>
-
-</itemizedlist>
-
-<para>
-Here is an example illustrating a complex search pattern. This pattern will
-select all messages which do not contain <quote>mutt</quote> in the <quote>To</quote> or <quote>Cc</quote>
-field and which are from <quote>elkins</quote>.
-</para>
-
-<example id="ex-pattern-bool">
-<title>Using boolean operators in patterns</title>
-<screen>
-!(~t mutt|~c mutt) ~f elkins
-</screen>
-</example>
-
-<para>
-Here is an example using white space in the regular expression (note
-the ' and " delimiters). For this to match, the mail's subject must
-match the <quote>ˆJunk +From +Me$</quote> and it must be from either <quote>Jim +Somebody</quote>
-or <quote>Ed +SomeoneElse</quote>:
-</para>
-
-<screen>
- '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
-</screen>
-
-<note>
-<para>
-If a regular expression contains parenthesis, or a vertical bar
-("|"), you <emphasis role="bold">must</emphasis> enclose the expression in double or single quotes since
-those characters are also used to separate different parts of Mutt's
-pattern language. For example: <literal>~f "me@(mutt\.org|cs\.hmc\.edu)"</literal>
-</para>
-</note>
-
-<para>
-Without the quotes, the parenthesis wouldn't end.
-This would be separated to two OR'd patterns: <emphasis>˜f me@(mutt\.org</emphasis>
-and <emphasis>cs\.hmc\.edu)</emphasis>. They are never what you want.
-</para>
-
-</sect2>
-
-<sect2 id="date-patterns">
-<title>Searching by Date</title>
-
-<para>
-Mutt supports two types of dates, <emphasis>absolute</emphasis> and <emphasis>relative</emphasis>.
-</para>
-
-<para>
-<emphasis role="bold">Absolute</emphasis>. Dates <emphasis role="bold">must</emphasis> be in DD/MM/YY format (month and year are
-optional, defaulting to the current month and year). An example of a valid
-range of dates is:
-</para>
-
-<screen>
-Limit to messages matching: ~d 20/1/95-31/10
-</screen>
-
-<para>
-If you omit the minimum (first) date, and just specify <quote>-DD/MM/YY</quote>, all
-messages <emphasis>before</emphasis> the given date will be selected. If you omit the maximum
-(second) date, and specify <quote>DD/MM/YY-</quote>, all messages <emphasis>after</emphasis> the given
-date will be selected. If you specify a single date with no dash (<quote>-</quote>),
-only messages sent on the given date will be selected.
-</para>
-
-<para>
-<emphasis role="bold">Error Margins</emphasis>. You can add error margins to absolute dates.
-An error margin is a sign (+ or -), followed by a digit, followed by
-one of the units in <xref linkend="tab-date-units"/>. As a special case, you can replace the
-sign by a <quote>*</quote> character, which is equivalent to giving identical plus and minus error margins.
-</para>
-
-<table id="tab-date-units">
-<title>Date units</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Unit</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>y</entry><entry>Years</entry></row>
-<row><entry>m</entry><entry>Months</entry></row>
-<row><entry>w</entry><entry>Weeks</entry></row>
-<row><entry>d</entry><entry>Days</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-Example: To select any messages two weeks around January 15, 2001,
-you'd use the following pattern:
-</para>
-
-<screen>
-Limit to messages matching: ~d 15/1/2001*2w
-</screen>
-
-<para>
-<emphasis role="bold">Relative</emphasis>. This type of date is relative to the current date, and may
-be specified as:
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-><emphasis>offset</emphasis> (messages older than <emphasis>offset</emphasis> units)
-</para>
-</listitem>
-<listitem>
-
-<para>
-<<emphasis>offset</emphasis> (messages newer than <emphasis>offset</emphasis> units)
-</para>
-</listitem>
-<listitem>
-
-<para>
-=<emphasis>offset</emphasis> (messages exactly <emphasis>offset</emphasis> units old)
-</para>
-</listitem>
-
-</itemizedlist>
-
-<para>
-<emphasis>offset</emphasis> is specified as a positive number with one of the units from <xref linkend="tab-date-units"/>.
-</para>
-
-<para>
-Example: to select messages less than 1 month old, you would use
-</para>
-
-<screen>
-Limit to messages matching: ~d <1m
-</screen>
-
-<note>
-<para>
-All dates used when searching are relative to the
-<emphasis role="bold">local</emphasis> time zone, so unless you change the setting of your <link linkend="index-format">$index_format</link> to include a
-<literal>%[...]</literal> format, these are <emphasis role="bold">not</emphasis> the dates shown
-in the main index.
-</para>
-</note>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="tags">
-<title>Using Tags</title>
-
-<para>
-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 <literal><tag-pattern></literal> function, which is bound to
-<quote>shift-T</quote> by default. Or you can select individual messages by
-hand using the <literal><tag-message></literal> function, which is bound to <quote>t</quote> by
-default. See <link linkend="patterns">patterns</link> for Mutt's pattern
-matching syntax.
-</para>
-
-<para>
-Once you have tagged the desired messages, you can use the
-<quote>tag-prefix</quote> operator, which is the <quote>;</quote> (semicolon) key by default.
-When the <quote>tag-prefix</quote> operator is used, the <emphasis role="bold">next</emphasis> operation will
-be applied to all tagged messages if that operation can be used in that
-manner. If the <link linkend="auto-tag">$auto_tag</link>
-variable is set, the next operation applies to the tagged messages
-automatically, without requiring the <quote>tag-prefix</quote>.
-</para>
-
-<para>
-In <link linkend="macro">macros</link> or <link linkend="push">push</link> commands,
-you can use the <quote>tag-prefix-cond</quote> operator. If there are no tagged
-messages, mutt will "eat" the rest of the macro to abort it's execution.
-Mutt will stop "eating" the macro when it encounters the <quote>end-cond</quote>
-operator; after this operator the rest of the macro will be executed as
-normal.
-</para>
-
-</sect1>
-
-<sect1 id="hooks">
-<title>Using Hooks</title>
-
-<para>
-A <emphasis>hook</emphasis> is a concept found in many other programs 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 world, a <emphasis>hook</emphasis>
-consists of a <link linkend="regexp">regular expression</link> or
-<link linkend="patterns">pattern</link> along with a
-configuration option/command. See
-
-<itemizedlist>
-<listitem>
-
-<para>
-<link linkend="folder-hook">folder-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="send-hook">send-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="message-hook">message-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="save-hook">save-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="mbox-hook">mbox-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="fcc-hook">fcc-hook</link>
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="fcc-save-hook">fcc-save-hook</link>
-</para>
-</listitem>
-
-</itemizedlist>
-
-for specific details on each type of <emphasis>hook</emphasis> available.
-</para>
-
-<note>
-<para>
-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:
-</para>
-</note>
-
-<example id="ex-send-hook-my-hdr">
-<title>Combining <literal>send-hook</literal> and <literal>my_hdr</literal></title>
-<screen>
-send-hook . 'unmy_hdr From:'
-send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
-</screen>
-</example>
-
-<sect2 id="pattern-hook" xreflabel="Message Matching in Hooks">
-<title>Message Matching in Hooks</title>
-
-<para>
-Hooks that act upon messages (<literal>message-hook, reply-hook,
-send-hook, send2-hook, save-hook, fcc-hook</literal>) are evaluated in a
-slightly different manner. For the other
-types of hooks, a <link linkend="regexp">regular expression</link> 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.
-</para>
-
-<para>
-Mutt allows the use of the <link linkend="patterns">search pattern</link>
-language for matching messages in hook commands. This works in
-exactly the same way as it would when <emphasis>limiting</emphasis> or
-<emphasis>searching</emphasis> 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.).
-</para>
-
-<para>
-For example, if you wanted to set your return address based upon sending
-mail to a specific address, you could do something like:
-</para>
-
-<screen>
-send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
-</screen>
-
-<para>
-which would execute the given command when sending mail to
-<emphasis>me@cs.hmc.edu</emphasis>.
-</para>
-
-<para>
-However, it is not required that you write the pattern to match using the
-full searching language. You can still specify a simple <emphasis>regular
-expression</emphasis> like the other hooks, in which case Mutt will translate your
-pattern into the full language, using the translation specified by the
-<link linkend="default-hook">$default_hook</link> variable. The
-pattern is translated at the time the hook is declared, so the value of
-<link linkend="default-hook">$default_hook</link> that is in effect
-at that time will be used.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="query">
-<title>External Address Queries</title>
-
-<para>
-Mutt 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 <link linkend="query-command">$query_command</link> variable, you specify the wrapper
-command to use. For example:
-</para>
-
-<screen>
-set query_command = "mutt_ldap_query.pl '%s'"
-</screen>
-
-<para>
-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 then
-some other optional information. On error, or if there are no matching
-addresses, return a non-zero exit code and a one line error message.
-</para>
-
-<para>
-An example multiple response output:
-</para>
-
-<screen>
-Searching database ... 20 entries ... 3 matching:
-me@cs.hmc.edu Michael Elkins mutt dude
-blong@fiction.net Brandon Long mutt and more
-roessler@does-not-exist.org Thomas Roessler mutt pgp
-</screen>
-
-<para>
-There are two mechanisms for accessing the query function of mutt. One
-is to do a query from the index menu using the <literal><query></literal> 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 addresses
-to mail, start a new query, or have a new query appended to the current
-responses.
-</para>
-
-<para>
-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 <literal><complete-query></literal> 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 query
-menu. At the query menu, you can select one or more addresses to be
-added to the prompt.
-</para>
-
-</sect1>
-
-<sect1 id="mailbox-formats">
-<title>Mailbox Formats</title>
-
-<para>
-Mutt 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 new
-mailboxes, Mutt uses the default specified with the <link linkend="mbox-type">$mbox_type</link> variable.
-</para>
-
-<para>
-<emphasis role="bold">mbox</emphasis>. 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:
-</para>
-
-<screen>
-From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST
-</screen>
-
-<para>
-to denote the start of a new message (this is often referred to as the
-<quote>From_</quote> line).
-</para>
-
-<para>
-<emphasis role="bold">MMDF</emphasis>. This is a variant of the <emphasis>mbox</emphasis> format. Each message is
-surrounded by lines containing <quote>ˆAˆAˆAˆA</quote> (four control-A's).
-</para>
-
-<para>
-<emphasis role="bold">MH</emphasis>. A radical departure from <emphasis>mbox</emphasis> and <emphasis>MMDF</emphasis>, 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 displays). Deleted messages are
-renamed with a comma (,) prepended to the filename. Mutt
-detects this type of mailbox by looking for either <literal>.mh_sequences</literal>
-or <literal>.xmhcache</literal> (needed to distinguish normal directories from MH
-mailboxes).
-</para>
-
-<para>
-<emphasis role="bold">Maildir</emphasis>. The newest of the mailbox formats, used by the Qmail MTA (a
-replacement for sendmail). Similar to <emphasis>MH</emphasis>, except that it adds three
-subdirectories of the mailbox: <emphasis>tmp</emphasis>, <emphasis>new</emphasis> and <emphasis>cur</emphasis>. Filenames
-for the messages are chosen in such a way they are unique, even when two
-programs are writing the mailbox over NFS, which means that no file locking
-is needed.
-</para>
-
-</sect1>
-
-<sect1 id="shortcuts">
-<title>Mailbox Shortcuts</title>
-
-<para>
-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.
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-! -- refers to your <link linkend="spoolfile">$spoolfile</link> (incoming) mailbox
-</para>
-</listitem>
-<listitem>
-
-<para>
-> -- refers to your <link linkend="mbox">$mbox</link> file
-</para>
-</listitem>
-<listitem>
-
-<para>
-< -- refers to your <link linkend="record">$record</link> file
-</para>
-</listitem>
-<listitem>
-
-<para>
-ˆ -- refers to the current mailbox
-</para>
-</listitem>
-<listitem>
-
-<para>
-- or !! -- refers to the file you've last visited
-</para>
-</listitem>
-<listitem>
-
-<para>
-˜ -- refers to your home directory
-</para>
-</listitem>
-<listitem>
-
-<para>
-= or + -- refers to your <link linkend="folder">$folder</link> directory
-</para>
-</listitem>
-<listitem>
-
-<para>
-@<emphasis>alias</emphasis> -- refers to the <link linkend="save-hook">default save folder</link> as determined by the address of the alias
-</para>
-</listitem>
-
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="using-lists">
-<title>Handling Mailing Lists</title>
-
-<para>
-Mutt 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 <link linkend="lists">lists and subscribe</link> commands in your muttrc.
-</para>
-
-<para>
-Now that Mutt 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 <emphasis>index</emphasis> menu display. This is useful to distinguish between
-personal and list mail in the same mailbox. In the <link linkend="index-format">$index_format</link> variable, the escape <quote>%L</quote>
-will return the string <quote>To <list></quote> when <quote>list</quote> appears in the
-<quote>To</quote> field, and <quote>Cc <list></quote> when it appears in the <quote>Cc</quote>
-field (otherwise it returns the name of the author).
-</para>
-
-<para>
-Often times the <quote>To</quote> and <quote>Cc</quote> fields in mailing list messages
-tend to get quite large. Most people do not bother to remove the
-author of the message they reply to from the list, resulting in
-two or more copies being sent to that person. The <literal><list-reply></literal>
-function, which by default is bound to <quote>L</quote> in the <emphasis>index</emphasis> menu
-and <emphasis>pager</emphasis>, helps reduce the clutter by only replying to the
-known mailing list addresses instead of all recipients (except as
-specified by <literal>Mail-Followup-To</literal>, see below).
-</para>
-
-<para>
-Mutt also supports the <literal>Mail-Followup-To</literal> header. When you send
-a message to a list of recipients which includes one or several
-subscribed mailing lists, and if the <link linkend="followup-to">$followup_to</link> 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 <quote>followups</quote>) 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.
-</para>
-
-<para>
-Conversely, when group-replying or list-replying to a message which
-has a <literal>Mail-Followup-To</literal> header, mutt will respect this header if
-the <link linkend="honor-followup-to">$honor_followup_to</link> 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 <literal>Mail-Followup-To</literal>.
-</para>
-
-<note>
-<para>
-When header editing is enabled, you can create a
-<literal>Mail-Followup-To</literal> header manually. Mutt will only auto-generate
-this header if it doesn't exist when you send the message.
-</para>
-</note>
-
-<para>
-The other method some mailing list admins use is to generate a
-<quote>Reply-To</quote> 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 <quote>Reply-To</quote>
-field. Mutt uses the <link linkend="reply-to">$reply_to</link>
-variable to help decide which address to use. If set to <emphasis>ask-yes</emphasis> or
-<emphasis>ask-no</emphasis>, you will be
-prompted as to whether or not you would like to use the address given in
-the <quote>Reply-To</quote> field, or reply directly to the address given in the
-<quote>From</quote> field. When set to <emphasis>yes</emphasis>, the <quote>Reply-To</quote> field will be used when
-present.
-</para>
-
-<para>
-The <quote>X-Label:</quote> header field can be used to further identify mailing
-lists or list subject matter (or just to annotate messages
-individually). The <link linkend="index-format">$index_format</link> variable's <quote>%y</quote> and
-<quote>%Y</quote> escapes can be used to expand <quote>X-Label:</quote> fields in the
-index, and Mutt's pattern-matcher can match regular expressions to
-<quote>X-Label:</quote> fields with the <quote>˜y</quote> selector. <quote>X-Label:</quote> is not a
-standard message header field, but it can easily be inserted by procmail
-and other mail filtering agents.
-</para>
-
-<para>
-Lastly, Mutt has the ability to <link linkend="sort">sort</link> the mailbox into
-<link linkend="threads">threads</link>. 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 dealing
-with large volume mailing lists easier because you can easily delete
-uninteresting threads and quickly find topics of value.
-</para>
-
-</sect1>
-
-<sect1 id="handling-folders">
-<title>Handling multiple folders</title>
-
-<para>
-Mutt supports setups with multiple folders, allowing all of them to
-be monitored for new mail (see <xref linkend="mailboxes"/> for details).
-</para>
-
-<para>
-When in the index menu and being idle (also see
-<link linkend="timeout">$timeout</link>), Mutt periodically checks
-for new mail in all folders which have been configured via the
-<literal>mailboxes</literal> command. The interval depends on the folder
-type: for local/IMAP folders it consults
-<link linkend="mail-check">$mail_check</link> and
-<link linkend="pop-checkinterval">$pop_checkinterval</link>
-for POP folders.
-</para>
-
-<para>
-Outside the index menu the directory browser supports checking
-for new mail using the <literal><check-new></literal> function which is
-unbound by default. Pressing TAB will bring up a
-menu showing the files specified by the <literal>mailboxes</literal> command,
-and indicate which contain new messages. Mutt will automatically enter this
-mode when invoked from the command line with the <literal>-y</literal> option.
-</para>
-
-<para>
-For the pager, index and directory browser menus, Mutt contains the
-<literal><buffy-list></literal> function (bound to <quote>.</quote> by default)
-which will print a list of folders with new mail in the command line at
-the bottom of the screen.
-</para>
-
-<para>
-For the index, by default Mutt displays the number of mailboxes with new
-mail in the status bar, please refer to the
-<link linkend="index-format">$index_format</link>
-variable for details.
-</para>
-
-<para>
-When changing folders, Mutt fills the prompt with the first folder from
-the mailboxes list containing new mail (if any), pressing
-<emphasis>space</emphasis> will cycle through folders with new mail.
-</para>
-
-</sect1>
-
-<sect1 id="editing-threads">
-<title>Editing threads</title>
-
-<para>
-Mutt 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.
-</para>
-
-<sect2 id="link-threads">
-<title>Linking threads</title>
-
-<para>
-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 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 <literal><link-threads></literal> function (bound to & by default). The
-reply will then be connected to this "parent" message.
-</para>
-
-<para>
-You can also connect multiple children at once, tagging them and using the
-tag-prefix command (';') or the auto_tag option.
-</para>
-
-</sect2>
-
-<sect2 id="break-threads">
-<title>Breaking threads</title>
-
-<para>
-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 <literal><break-thread></literal> function (bound
-by default to #), which will turn the subthread starting from the
-current message into a whole different thread.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="dsn">
-<title>Delivery Status Notification (DSN) Support</title>
-
-<para>
-RFC1894 defines a set of MIME content types for relaying information
-about the status of electronic mail messages. These can be thought of as
-<quote>return receipts.</quote>
-</para>
-
-<para>
-To support DSN, there are two variables. <link linkend="dsn-notify">$dsn_notify</link> is used to request receipts for
-different results (such as failed message, message delivered, etc.).
-<link linkend="dsn-return">$dsn_return</link> requests how much
-of your message should be returned with the receipt (headers or full
-message).
-</para>
-
-<para>
-When using <link linkend="sendmail">$sendmail</link> for mail
-delivery, you need to use either Berkeley sendmail 8.8.x (or greater) a MTA
-supporting DSN command line options compatible to Sendmail: The -N and -R
-options can be used by the mail client to make requests as to what type of
-status messages should be returned. Please consider your MTA documentation
-whether DSN is supported.
-</para>
-
-<para>
-For SMTP delivery using <link
- linkend="smtp-url">$smtp_url</link>, it depends on the
-capabilities announced by the server whether mutt will attempt to
-request DSN or not.
-</para>
-
-</sect1>
-
-<sect1 id="urlview">
-<title>Start a WWW Browser on URLs</title>
-
-<para>
-If a message contains URLs, 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
-<ulink url="ftp://ftp.mutt.org/mutt/contrib/">ftp://ftp.mutt.org/mutt/contrib/</ulink>
-and the configuration commands:
-</para>
-
-<screen>
-macro index \cb |urlview\n
-macro pager \cb |urlview\n
-</screen>
-
-</sect1>
-
-</chapter>
-
-<sect1 id="compressedfolders">
-<title>Compressed folders Support (OPTIONAL)</title>
-
-<para>
-If Mutt was compiled with compressed folders support (by running the
-<emphasis>configure</emphasis> script with the
-<emphasis>--enable-compressed</emphasis> flag), Mutt can open folders
-stored in an arbitrary format, provided that the user has a script to
-convert from/to this format to one of the accepted.
-
-The most common use is to open compressed archived folders e.g. with
-gzip.
-
-In addition, the user can provide a script that gets a folder in an
-accepted format and appends its context to the folder in the
-user-defined format, which may be faster than converting the entire
-folder to the accepted format, appending to it and converting back to
-the user-defined format.
-
-There are three hooks defined (<link
-linkend="open-hook">open-hook</link>, <link
-linkend="close-hook">close-hook</link> and <link
-linkend="append-hook">append-hook</link>) which define commands to
-uncompress and compress a folder and to append messages to an existing
-compressed folder respectively.
-
-For example:
-
-<screen>
-open-hook \\.gz$ "gzip -cd %f > %t"
-close-hook \\.gz$ "gzip -c %t > %f"
-append-hook \\.gz$ "gzip -c %t >> %f"
-</screen>
-
-You do not have to specify all of the commands. If you omit <link
-linkend="append-hook">append-hook</link>, the folder will be open and
-closed again each time you will add to it. If you omit <link
-linkend="close-hook">close-hook</link> (or give empty command) , the
-folder will be open in the mode. If you specify <link
-linkend="append-hook">append-hook</link> though you'll be able to
-append to the folder.
-
-Note that Mutt 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
-<link linkend="save-empty">$save_empty</link>, so that
-the compressed file will be removed if you delete all of the messages.
-</para>
-
-<sect2 id="open-hook">
-<title>Open a compressed mailbox for reading</title>
-
-<para>
-Usage: <literal>open-hook</literal> <emphasis>regexp</emphasis> "<emphasis>command</emphasis>"
-
-The <emphasis>command</emphasis> is the command that can be used for
-opening the folders whose names match <emphasis>regexp</emphasis>.
-
-The <emphasis>command</emphasis> string is the printf-like format
-string, and it should accept two parameters: %f, which is
-replaced with the (compressed) folder name, and %t which is
-replaced with the name of the temporary folder to which to write.
-
-%f and %t can be repeated any number of times in the
-command string, and all of the entries are replaced with the
-appropriate folder name. In addition, %% is replaced by
-%, as in printf, and any other %anything is left as is.
-
-The <emphasis>command</emphasis> should <emphasis
-role="bold">not</emphasis> remove the original compressed file. The
-<emphasis>command</emphasis> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-<screen>
-open-hook \\.gz$ "gzip -cd %f > %t"
-</screen>
-
-If the <emphasis>command</emphasis> is empty, this operation is
-disabled for this file type.
-</para>
-</sect2>
-
-<sect2 id="close-hook">
-<title>Write a compressed mailbox</title>
-
-<para>
-Usage: <literal>close-hook</literal> <emphasis>regexp</emphasis> "<emphasis>command</emphasis>"
-
-This is used to close the folder that was open with the <link
-linkend="open-hook">open-hook</link> command after some changes were
-made to it.
-
-The <emphasis>command</emphasis> string is the command that can be
-used for closing the folders whose names match
-<emphasis>regexp</emphasis>. It has the same format as in the <link
-linkend="open-hook">open-hook</link> command. Temporary folder in this
-case is the folder previously produced by the <link
-linkend="open-hook">open-hook</link> command.
-
-The <emphasis>command</emphasis> should <emphasis
-role="bold">not</emphasis> remove the decompressed file. The
-<emphasis>command</emphasis> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-<screen>
-close-hook \\.gz$ "gzip -c %t > %f"
-</screen>
-
-If the <emphasis>command</emphasis> is empty, this operation is
-disabled for this file type, and the file can only be open in the
-read-only mode.
-
-<link linkend="close-hook">close-hook</link> is not called when you
-exit from the folder if the folder was not changed.
-</para>
-</sect2>
-
-<sect2 id="append-hook">
-<title>Append a message to a compressed mailbox</title>
-
-<para>
-Usage: <literal>append-hook</literal> <emphasis>regexp</emphasis> "<emphasis>command</emphasis>"
-
-This command is used for saving to an existing compressed folder. The
-<emphasis>command</emphasis> is the command that can be used for
-appending to the folders whose names match
-<emphasis>regexp</emphasis>. It has the same format as in the <link
-linkend="open-hook">open-hook</link> command. The temporary folder in
-this case contains the messages that are being appended.
-
-The <emphasis>command</emphasis> should <emphasis
-role="bold">not</emphasis> remove the decompressed file. The
-<emphasis>command</emphasis> should return non-zero exit status if it
-fails, so mutt knows something's wrong.
-
-Example:
-
-<screen>
-append-hook \\.gz$ "gzip -c %t >> %f"
-</screen>
-
-When <link linkend="append-hook">append-hook</link> 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 (<link
-linkend="mbox-type">$mbox_type</link>) type is always
-supposed (i.e. this is the format used for the temporary folder).
-
-If the file does not exist when you save to it, <link
-linkend="close-hook">close-hook</link> is called, and not <link
-linkend="append-hook">append-hook</link>. <link
-linkend="append-hook">append-hook</link> is only for appending to
-existing folders.
-
-If the <emphasis>command</emphasis> is empty, this operation is
-disabled for this file type. In this case, the folder will be open and
-closed again (using <link linkend="open-hook">open-hook</link> and
-<link linkend="close-hook">close-hook</link>respectively) each time you
-will add to it.
-</para>
-</sect2>
-
-<sect2>
-<title>Encrypted folders</title>
-
-<para>
-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 use
-the following hooks:
-
-<screen>
-open-hook \\.pgp$ "pgp -f < %f > %t"
-close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"
-</screen>
-
-Please note, that PGP does not support appending to an encrypted
-folder, so there is no append-hook defined.
-
-If you are using GnuPG instead of PGP, you may use the following hooks
-instead:
-
-<screen>
-open-hook \\.gpg$ "gpg --decrypt < %f > %t"
-close-hook \\.gpg$ "gpg --encrypt --recipient YourGpgUserIdOrKeyId < %t > %f"
-</screen>
-
-<emphasis role="bold">Note:</emphasis> the folder is temporary stored
-decrypted in the /tmp directory, where it can be read by your system
-administrator. So think about the security aspects of this.
-</para>
-</sect2>
-</sect1>
-
-<chapter id="mimesupport">
-<title>Mutt's MIME Support</title>
-
-<para>
-Quite a bit of effort has been made to make Mutt 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 for MIME, there are two extra
-types of configuration files which Mutt uses. One is the
-<literal>mime.types</literal> file, which contains the mapping of file extensions to
-IANA MIME types. The other is the <literal>mailcap</literal> file, which specifies
-the external commands to use for handling specific MIME types.
-</para>
-
-<sect1 id="using-mime">
-<title>Using MIME in Mutt</title>
-
-<para>
-There are three areas/menus in Mutt which deal with MIME, they are the
-pager (while viewing a message), the attachment menu and the compose
-menu.
-</para>
-
-<sect2 id="mime-pager">
-<title>Viewing MIME messages in the pager</title>
-
-<para>
-When you select a message from the index and view it in the pager, Mutt
-decodes the message to a text representation. Mutt internally supports
-a number of MIME types, including <literal>text/plain, text/enriched,
-message/rfc822, and message/news</literal>. In addition, the export
-controlled version of Mutt recognizes a variety of PGP MIME types,
-including PGP/MIME and application/pgp.
-</para>
-
-<para>
-Mutt will denote attachments with a couple lines describing them.
-These lines are of the form:
-</para>
-
-<screen>
-[-- Attachment #1: Description --]
-[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-</screen>
-
-<para>
-Where the <literal>Description</literal> is the description or filename given for the
-attachment, and the <literal>Encoding</literal> is one of
-<literal>7bit/8bit/quoted-printable/base64/binary</literal>.
-</para>
-
-<para>
-If Mutt cannot deal with a MIME type, it will display a message like:
-</para>
-
-<screen>
-[-- image/gif is unsupported (use 'v' to view this part) --]
-</screen>
-
-</sect2>
-
-<sect2 id="attach-menu">
-<title>The Attachment Menu</title>
-
-<para>
-The default binding for <literal>view-attachments</literal> is `v', which displays the
-attachment menu for a message. The attachment menu displays a list of
-the 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 <quote>tag-prefix</quote> 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.
-</para>
-
-<para>
-Finally, you can apply the usual message-related functions (like
-<link linkend="resend-message"><literal><resend-message></literal></link>, and the
-<literal><reply></literal> and <literal><forward></literal>
-functions) to attachments of type <literal>message/rfc822</literal>.
-</para>
-
-<para>
-See the help on the attachment menu for more information.
-</para>
-
-</sect2>
-
-<sect2 id="compose-menu">
-<title>The Compose Menu</title>
-
-<para>
-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.
-</para>
-
-<para>
-Attachments appear as follows:
-</para>
-
-<screen>
-- 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>
-</screen>
-
-<para>
-The '-' denotes that Mutt will delete the file after sending (or
-postponing, or canceling) the message. It can be toggled with the
-<literal>toggle-unlink</literal> command (default: u). The next field is the MIME
-content-type, and can be changed with the <literal>edit-type</literal> 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 <literal>edit-encoding</literal> 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 <literal>rename-file</literal> command (default: R).
-The final field is the description of the attachment, and can be
-changed with the <literal>edit-description</literal> command (default: d).
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="mime-types">
-<title>MIME Type configuration with <literal>mime.types</literal></title>
-
-<para>
-When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at <literal>${HOME}/.mime.types</literal>, and then
-the system mime.types file at <literal>/usr/local/share/mutt/mime.types</literal> or
-<literal>/etc/mime.types</literal>
-</para>
-
-<para>
-The mime.types file consist of lines containing a MIME type and a space
-separated list of extensions. For example:
-</para>
-
-<screen>
-application/postscript ps eps
-application/pgp pgp
-audio/x-aiff aif aifc aiff
-</screen>
-
-<para>
-A sample <literal>mime.types</literal> file comes with the Mutt distribution, and
-should contain most of the MIME types you are likely to use.
-</para>
-
-<para>
-If Mutt 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 will assume that the file is plain text, and mark it
-as <literal>text/plain</literal>. If the file contains binary information, then Mutt will
-mark it as <literal>application/octet-stream</literal>. You can change the MIME
-type that Mutt assigns to an attachment by using the <literal>edit-type</literal>
-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 recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
-major mime types, such as the chemical type that is widely used in the
-molecular modeling community to pass molecular data in various forms to
-various molecular viewers. Non-recognized mime types should only be used
-if the recipient of the message is likely to be expecting such attachments.
-</para>
-
-</sect1>
-
-<sect1 id="mailcap">
-<title>MIME Viewer configuration with <literal>mailcap</literal></title>
-
-<para>
-Mutt supports RFC 1524 MIME Configuration, in particular the Unix
-specific format specified in Appendix A of RFC 1524. 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.
-</para>
-
-<para>
-In order to handle various MIME types that Mutt can not handle
-internally, Mutt parses a series of external configuration files to
-find an external handler. The default search string for these files
-is a colon delimited list containing the following files:
-</para>
-
-<orderedlist>
-<listitem><para><literal>$HOME/.mailcap</literal></para></listitem>
-<listitem><para><literal>$PKGDATADIR/mailcap</literal></para></listitem>
-<listitem><para><literal>$SYSCONFDIR/mailcap</literal></para></listitem>
-<listitem><para><literal>/etc/mailcap</literal></para></listitem>
-<listitem><para><literal>/usr/etc/mailcap</literal></para></listitem>
-<listitem><para><literal>/usr/local/etc/mailcap</literal></para></listitem>
-</orderedlist>
-
-<para>
-where <literal>$HOME</literal> is your home directory. The
-<literal>$PKGDATADIR</literal> and the
-<literal>$SYSCONFDIR</literal> directories depend on where mutt
-is installed: the former is the default for shared data, the
-latter for system configuration files.
-</para>
-
-<para>
-The default search path can be obtained by running the following
-command:
-</para>
-
-<screen>
-mutt -nF /dev/null -Q mailcap_path
-</screen>
-
-<para>
-In particular, the metamail distribution will install a mailcap file,
-usually as <literal>/usr/local/etc/mailcap</literal>, which contains some baseline
-entries.
-</para>
-
-<sect2 id="mailcap-basics">
-<title>The Basics of the mailcap file</title>
-
-<para>
-A mailcap file consists of a series of lines which are comments, blank,
-or definitions.
-</para>
-
-<para>
-A comment line consists of a # character followed by anything you want.
-</para>
-
-<para>
-A blank line is blank.
-</para>
-
-<para>
-A definition line consists of a content type, a view command, and any
-number of optional fields. Each field of a definition line is divided
-by a semicolon ';' character.
-</para>
-
-<para>
-The content type is specified in the MIME standard type/subtype method.
-For example,
-<literal>text/plain, text/html, image/gif, </literal>
-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, <literal>image/*</literal>, or
-<literal>video,</literal> will match all image types and video types,
-respectively.
-</para>
-
-<para>
-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 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 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.
-</para>
-
-<para>
-So, in the simplest form, you can send a text/plain message to the
-external pager more on stdin:
-</para>
-
-<screen>
-text/plain; more
-</screen>
-
-<para>
-Or, you could send the message as a file:
-</para>
-
-<screen>
-text/plain; more %s
-</screen>
-
-<para>
-Perhaps you would like to use lynx to interactively view a text/html
-message:
-</para>
-
-<screen>
-text/html; lynx %s
-</screen>
-
-<para>
-In this case, lynx does not support viewing a file from stdin, so you
-must use the %s syntax.
-</para>
-
-<note>
-<para>
-<emphasis>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.</emphasis>
-</para>
-</note>
-
-<para>
-On the other hand, maybe you don't want to use lynx interactively, you
-just want to have it convert the text/html to text/plain, then you can
-use:
-</para>
-
-<screen>
-text/html; lynx -dump %s | more
-</screen>
-
-<para>
-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:
-</para>
-
-<screen>
-text/html; lynx %s
-text/*; more
-</screen>
-
-<para>
-This is the simplest form of a mailcap file.
-</para>
-
-</sect2>
-
-<sect2 id="secure-mailcap">
-<title>Secure use of mailcap</title>
-
-<para>
-The interpretation of shell meta-characters embedded in MIME parameters
-can lead to security problems in general. Mutt tries to quote parameters
-in expansion of %s syntaxes properly, and avoids risky characters by
-substituting them, see the <link linkend="mailcap-sanitize">$mailcap_sanitize</link> variable.
-</para>
-
-<para>
-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:
-</para>
-
-<para>
-<emphasis>Keep the %-expandos away from shell quoting.</emphasis>
-Don't quote them with single or double quotes. Mutt 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 behavior with quotes introduces new leaks - there is no
-alternative to correct quoting in the first place.
-</para>
-
-<para>
-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 <literal>$charset</literal> inside the backtick expansion is safe,
-since it is not itself subject to any further expansion):
-</para>
-
-<screen>
-text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-</screen>
-
-</sect2>
-
-<sect2 id="advanced-mailcap">
-<title>Advanced mailcap Usage</title>
-
-<sect3 id="optional-mailcap-fields">
-<title>Optional Fields</title>
-
-<para>
-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 recognizes the following optional fields:
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>copiousoutput</term>
-<listitem>
-<para>
-This flag tells Mutt that the command passes possibly large amounts of
-text on stdout. This causes Mutt 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 assumes that the command
-is interactive. One could use this to replace the pipe to <literal>more</literal>
-in the <literal>lynx -dump</literal> example in the Basic section:
-</para>
-
-<screen>
-text/html; lynx -dump %s ; copiousoutput
-</screen>
-
-<para>
-This will cause lynx to format the text/html output as text/plain
-and Mutt will use your standard pager to display the results.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>needsterminal</term>
-<listitem>
-<para>
-Mutt uses this flag when viewing attachments with <link linkend="auto-view">auto_view</link>, in order to decide whether it should honor the setting
-of the <link linkend="wait-key">$wait_key</link> variable or
-not. When an attachment is viewed using an interactive program, and the
-corresponding mailcap entry has a <emphasis>needsterminal</emphasis> flag, Mutt will use
-<link linkend="wait-key">$wait_key</link> and the exit status
-of 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.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>compose=<command></term>
-<listitem>
-<para>
-This flag specifies the command to use to create a new attachment of a
-specific MIME type. Mutt supports this from the compose menu.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>composetyped=<command></term>
-<listitem>
-<para>
-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 supports this from the compose menu.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>print=<command></term>
-<listitem>
-<para>
-This flag specifies the command to use to print a specific MIME type.
-Mutt supports this from the attachment and compose menus.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>edit=<command></term>
-<listitem>
-<para>
-This flag specifies the command to use to edit a specific MIME type.
-Mutt supports this from the compose menu, and also uses it to compose
-new attachments. Mutt will default to the defined editor for text
-attachments.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>nametemplate=<template></term>
-<listitem>
-<para>
-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 <literal>text/html</literal> if the file ends in <literal>.html</literal>.
-So, you would specify lynx as a <literal>text/html</literal> viewer with a line in
-the mailcap file like:
-</para>
-
-<screen>
-text/html; lynx %s; nametemplate=%s.html
-</screen>
-
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>test=<command></term>
-<listitem>
-<para>
-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 uses this entry. If the command returns non-zero,
-then the test failed, and Mutt continues searching for the right entry.
-Note that the content-type must match before Mutt performs the test.
-For example:
-</para>
-
-<screen>
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s
-</screen>
-
-<para>
-In this example, Mutt 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 will call netscape to display the
-text/html object. If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-</sect3>
-
-<sect3 id="mailcap-search-order">
-<title>Search Order</title>
-
-<para>
-When searching for an entry in the mailcap file, Mutt will search for
-the most useful entry for its purpose. For instance, if you are
-attempting to print an <literal>image/gif</literal>, and you have the following
-entries in your mailcap file, Mutt will search for an entry with the
-print command:
-</para>
-
-<screen>
-image/*; xv %s
-image/gif; ; print= anytopnm %s | pnmtops | lpr; \
- nametemplate=%s.gif
-</screen>
-
-<para>
-Mutt will skip the <literal>image/*</literal> entry and use the <literal>image/gif</literal>
-entry with the print command.
-</para>
-
-<para>
-In addition, you can use this with <link linkend="auto-view">auto_view</link>
-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.
-</para>
-
-<screen>
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s; nametemplate=%s.html
-text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
-</screen>
-
-<para>
-For <link linkend="auto-view">auto_view</link>, Mutt 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 will use the second entry
-for interactive viewing.
-</para>
-
-</sect3>
-
-<sect3 id="mailcap-command-expansion">
-<title>Command Expansion</title>
-
-<para>
-The various commands defined in the mailcap files are passed to the
-<literal>/bin/sh</literal> shell using the system() function. Before the
-command is passed to <literal>/bin/sh -c</literal>, it is parsed to expand
-various special parameters with information from Mutt. The keywords
-Mutt expands are:
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>%s</term>
-<listitem>
-<para>
-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 to not pass the body of the message
-to the view/print/edit program on stdin.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>%t</term>
-<listitem>
-<para>
-Mutt 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 <literal>text/html</literal> or
-<literal>image/gif</literal>.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>%{<parameter>}</term>
-<listitem>
-<para>
-Mutt 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:
-</para>
-
-<screen>
-Content-Type: text/plain; charset=iso-8859-1
-</screen>
-
-<para>
-then Mutt 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.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>\%</term>
-<listitem>
-<para>
-This will be replaced by a %
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-<para>
-Mutt 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.
-</para>
-
-</sect3>
-
-</sect2>
-
-<sect2 id="mailcap-example">
-<title>Example mailcap files</title>
-
-<para>
-This mailcap file is fairly simple and standard:
-</para>
-
-<screen>
-# I'm always running X :)
-video/*; xanim %s > /dev/null
-image/*; xv %s > /dev/null
-
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html; netscape -remote 'openURL(%s)'
-</screen>
-
-<para>
-This mailcap file shows quite a number of examples:
-</para>
-
-<screen>
-# Use xanim to view all videos Xanim produces a header on startup,
-# send that to /dev/null so I don't see it
-video/*; xanim %s > /dev/null
-
-# Send html to a running netscape by remote
-text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
-
-# If I'm not running netscape but I am running X, start netscape on the
-# object
-text/html; netscape %s; test=RunningX
-
-# Else use lynx to view it as text
-text/html; lynx %s
-
-# This version would convert the text/html to text/plain
-text/html; lynx -dump %s; copiousoutput
-
-# I use enscript to print text in two columns to a page
-text/*; more %s; print=enscript -2Gr %s
-
-# Netscape adds a flag to tell itself to view jpegs internally
-image/jpeg;xv %s; x-mozilla-flags=internal
-
-# Use xv to view images if I'm running X
-# In addition, this uses the \ to extend the line and set my editor
-# for images
-image/*;xv %s; test=RunningX; \
- edit=xpaint %s
-
-# Convert images to text using the netpbm tools
-image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
-pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
-# Send excel spreadsheets to my NT box
-application/ms-excel; open.pl %s
-</screen>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="auto-view">
-<title>MIME Autoview</title>
-
-<para>
-In addition to explicitly telling Mutt to view an attachment with the
-MIME viewer defined in the mailcap file, Mutt has support for
-automatically viewing MIME attachments while in the pager.
-</para>
-
-<para>
-To work, you must define a viewer in the mailcap file which uses the
-<literal>copiousoutput</literal> 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.
-</para>
-
-<para>
-You then use the <literal>auto_view</literal> muttrc command to list the
-content-types that you wish to view automatically.
-</para>
-
-<para>
-For instance, if you set auto_view to:
-</para>
-
-<screen>
-auto_view text/html application/x-gunzip \
- application/postscript image/gif application/x-tar-gz
-</screen>
-
-<para>
-Mutt could use the following mailcap entries to automatically view
-attachments of these types.
-</para>
-
-<screen>
-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
-</screen>
-
-<para>
-<quote>unauto_view</quote> 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.
-<quote>unauto_view *</quote> will remove all previous entries.
-</para>
-
-</sect1>
-
-<sect1 id="alternative-order">
-<title>MIME Multipart/Alternative</title>
-
-<para>
-Mutt 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 types
-is preferred. The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
-</para>
-
-<screen>
-alternative_order text/enriched text/plain text application/postscript image/*
-</screen>
-
-<para>
-Next, mutt will check if any of the types have a defined
-<link linkend="auto-view">auto_view</link>, and use that. Failing
-that, Mutt will look for any text type. As a last attempt, mutt will
-look for any type it knows how to handle.
-</para>
-
-<para>
-To remove a MIME type from the <literal>alternative_order</literal> list, use the
-<literal>unalternative_order</literal> command.
-</para>
-
-</sect1>
-
-<sect1 id="attachments">
-<title>Attachment Searching and Counting</title>
-
-<para>
-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.
-</para>
-
-<para>
-In order to provide this information, mutt needs to fully MIME-parse
-all messages affected first. This can slow down operation especially for
-remote mail folders such as IMAP because all messages have to be
-downloaded first regardless whether the user really wants to view them
-or not.
-</para>
-
-<para>
-The syntax is:
-</para>
-
-<screen>
-attachments {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments ?
-</screen>
-
-<para>
-Disposition is the attachment's Content-disposition type -- either
-<literal>inline</literal> or <literal>attachment</literal>.
-You can abbreviate this to <literal>I</literal> or <literal>A</literal>.
-</para>
-
-<para>
-Disposition is prefixed by either a + symbol or 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.
-</para>
-
-<para>
-Mime-type is, unsurprisingly, the MIME type of the attachment you want
-to affect. A MIME type is always of the format <literal>major/minor</literal>, where
-<literal>major</literal> describes the broad category of document you're looking at, and
-<literal>minor</literal> describes the specific type within that category. The major
-part of mime-type must be literal text (or the special token <quote><literal>*</literal></quote>), but
-the minor part may be a regular expression. (Therefore, <quote><literal>*/.*</literal></quote> matches
-any MIME type.)
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-Some examples might help to illustrate. The examples that are not
-commented out define the default configuration of the lists.
-</para>
-
-<example id="ex-attach-count">
-<title>Attachment counting</title>
-<screen>
-## 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
-</screen>
-</example>
-
-<para>
-Entering the command <quote><literal>attachments ?</literal></quote>
-as a command will list your current settings in Muttrc format, so that
-it can be pasted elsewhere.
-</para>
-
-</sect1>
-
-<sect1 id="mime-lookup">
-<title>MIME Lookup</title>
-
-<para>
-Mutt's mime_lookup list specifies a list of mime-types that should not
-be treated according to their mailcap entry. This option is designed to
-deal 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:
-</para>
-
-<screen>
-mime_lookup application/octet-stream application/X-Lotus-Manuscript
-</screen>
-
-<para>
-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.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="optionalfeatures">
-<title>Optional features</title>
-
-<sect1 id="optionalfeatures-notes">
-<title>General notes</title>
-
-<sect2 id="compile-time-features">
-<title>Enabling/disabling features</title>
-
-<para>
-Mutt supports several of optional features which can be enabled or
-disabled at compile-time by giving the <emphasis>configure</emphasis> script
-certain arguments. These are listed in the <quote>Optional features</quote> section of
-the <emphasis>configure --help</emphasis> output.
-</para>
-
-<para>
-Which features are enabled or disabled can later be determined from the
-output of <literal>mutt -v</literal>. If a compile option starts with
-<quote>+</quote> it is enabled and disabled if prefixed with <quote>-</quote>. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
-OpenSSL, <literal>mutt -v</literal> would contain:
-</para>
-
-<screen>
--USE_SSL_OPENSSL +USE_SSL_GNUTLS</screen>
-
-</sect2>
-
-<sect2 id="url-syntax">
-<title>URL syntax</title>
-
-<para>
-Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
-to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in <literal>[]</literal> means it is optional and
-may be omitted):
-</para>
-
-<screen>
-proto[s]://[username[:password]@]server[:port]/[path]
-</screen>
-
-<para>
-<literal>proto</literal> is the communication protocol:
-<literal>imap</literal> for IMAP, <literal>pop</literal> for POP3 and
-<literal>smtp</literal> for SMTP. If <quote>s</quote> for <quote>secure communication</quote>
-is appended, mutt will attempt to establish an encrypted communication
-using SSL or TLS. If no explicit port is given, mutt will use the
-system's default for the given protocol.
-</para>
-
-<para>
-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the <literal>pop_user</literal> or
-<literal>imap_user</literal> variables. It may contain the <quote>@</quote> symbol
-being used by many mail systems as part of the login name. A password can be
-given, too but is not recommended if the URL is specified in a configuration
-file on disk.
-</para>
-
-<para>
-The optional path is only relevant for IMAP.
-</para>
-
-<para>
-For IMAP for example, you can select an alternative port by specifying it with the
-server: <literal>imap://imapserver:port/INBOX</literal>. You can also specify different
-username for each folder: <literal>imap://username@imapserver[:port]/INBOX</literal>
-or <literal>imap://username2@imapserver[:port]/path/to/folder</literal>.
-Replacing <literal>imap://</literal> by <literal>imaps://</literal>
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="ssl">
-<title>SSL/TLS Support</title>
-
-<para>
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
-compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
-by running the <emphasis>configure</emphasis> script with the
-<emphasis>--enable-ssl=...</emphasis> option for OpenSSL or
-<emphasis>--enable-gnutls=...</emphasis> for GnuTLS). Mutt can then
-attempt to encrypt communication with remote servers if these protocols
-are suffixed with <quote>s</quote> for <quote>secure communication</quote>.
-</para>
-
-</sect1>
-
-<sect1 id="pop">
-<title>POP3 Support</title>
-
-<para>
-If Mutt was compiled with POP3 support (by running the <emphasis>configure</emphasis>
-script with the <emphasis>--enable-pop</emphasis> flag), it has the ability to work
-with mailboxes located on a remote POP3 server and fetch mail for local
-browsing.
-</para>
-
-<para>
-Remote POP3 servers can be accessed using URLs with the <literal>pop</literal> protocol
-for unencrypted and <literal>pops</literal> for encrypted
-communication, see <xref linkend="url-syntax"/> for details.
-</para>
-
-<para>
-Polling for new mail is more expensive over POP3 than locally. For this
-reason the frequency at which Mutt will check for mail remotely can be
-controlled by the
-<link linkend="pop-checkinterval">$pop_checkinterval</link>
-variable, which defaults to every 60 seconds.
-</para>
-
-<anchor id="fetch-mail"/>
-<para>
-Another way to access your POP3 mail is the <literal><fetch-mail$</literal> function
-(default: G). It allows to connect to <link linkend="pop-host">$pop_host</link>, fetch all your new mail and place it in the
-local <link linkend="spoolfile">$spoolfile</link>. After this
-point, Mutt runs exactly as if the mail had always been local.
-</para>
-
-<note>
-<para>
-If you only need to fetch all messages to a
-local mailbox you should consider using a specialized program, such as
-<literal>fetchmail</literal>, <literal>getmail</literal> or similar.
-</para>
-</note>
-
-</sect1>
-
-<sect1 id="imap">
-<title>IMAP Support</title>
-
-<para>
-If Mutt was compiled with IMAP support (by running the <emphasis>configure</emphasis>
-script with the <emphasis>--enable-imap</emphasis> flag), it has the ability to work
-with folders located on a remote IMAP server.
-</para>
-
-<para>
-You can access the remote inbox by selecting the folder by its URL
-(see <xref linkend="url-syntax"/> for details) using the
-<literal>imap</literal> or <literal>imaps</literal> protocol.
-Alternatively, a pine-compatible notation is also supported, ie
-<literal>{[username@]imapserver[:port][/ssl]}path/to/folder</literal>
-</para>
-
-<para>
-Note that not all servers use <quote>/</quote> as the hierarchy separator. Mutt should
-correctly notice which separator is being used by the server and convert
-paths accordingly.
-</para>
-
-<para>
-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
-<emphasis>toggle-subscribed</emphasis> command. See also the
-<link linkend="imap-list-subscribed">$imap_list_subscribed</link> variable.
-</para>
-
-<para>
-Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
-want to carefully tune the
-<link linkend="mail-check">$mail_check</link>
-and
-<link linkend="timeout">$timeout</link>
-variables. Personally I use
-</para>
-
-<screen>
-set mail_check=90
-set timeout=15
-</screen>
-
-<para>
-with relatively good results over my slow modem line.
-</para>
-
-<note>
-<para>
-Note that if you are using mbox as the mail store on UW servers prior to
-v12.250, the server has been reported to disconnect a client if another client
-selects the same folder.
-</para>
-</note>
-
-<sect2 id="imap-browser">
-<title>The Folder Browser</title>
-
-<para>
-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:
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-In lieu 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.
-</para>
-</listitem>
-<listitem>
-
-<para>
-For the case where an entry can contain both messages and
-subfolders, the selection key (bound to <literal>enter</literal> by default)
-will choose to descend into the subfolder view. If you wish to view
-the messages in that folder, you must use <literal>view-file</literal> instead
-(bound to <literal>space</literal> by default).
-</para>
-</listitem>
-<listitem>
-
-<para>
-You can create, delete and rename mailboxes with the
-<literal>create-mailbox</literal>, <literal>delete-mailbox</literal>, and
-<literal>rename-mailbox</literal> commands (default bindings: <literal>C</literal>,
-<literal>d</literal> and <literal>r</literal>, respectively). You may also
-<literal>subscribe</literal> and <literal>unsubscribe</literal> to mailboxes (normally
-these are bound to <literal>s</literal> and <literal>u</literal>, respectively).
-</para>
-</listitem>
-
-</itemizedlist>
-
-</sect2>
-
-<sect2 id="imap-authentication">
-<title>Authentication</title>
-
-<para>
-Mutt 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".
-</para>
-
-<para>
-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 library
-installed on your system and compile mutt with the <emphasis>--with-sasl</emphasis> flag.
-</para>
-
-<para>
-Mutt will try whichever methods are compiled in and available on the server,
-in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-</para>
-
-<para>
-There are a few variables which control authentication:
-</para>
-
-<itemizedlist>
-<listitem>
-
-<para>
-<link linkend="imap-user">$imap_user</link> - 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 (ie by using a mailbox name of the form
-<literal>{user@host}</literal>).
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="imap-pass">$imap_pass</link> - a
-password which you may preset, used by all authentication methods where
-a password is needed.
-</para>
-</listitem>
-<listitem>
-
-<para>
-<link linkend="imap-authenticators">$imap_authenticators</link> - 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).
-</para>
-</listitem>
-
-</itemizedlist>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="smtp">
-<title>SMTP Support</title>
-
-<para>
-Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
-was configured and built with <literal>--enable-smtp</literal>.
-</para>
-
-<para>
-If the configuration variable
-<link linkend="smtp-url">$smtp_url</link> is set, mutt
-will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by <link linkend="sendmail">$sendmail</link>.
-</para>
-
-<para>
-For details on the URL syntax, please see <xref linkend="url-syntax"/>.
-</para>
-
-<para>
-The built-in SMTP support supports encryption (the <literal>smtps</literal> protocol
-using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
-for SASL are specified in <link linkend="smtp-authenticators">$smtp_authenticators</link>
-defaulting to an empty list which makes mutt try all available methods
-from most-secure to least-secure.
-</para>
-
-</sect1>
-
-<sect1 id="account-hook">
-<title>Managing multiple accounts</title>
-
-<para>
-If you happen to have accounts on multiple IMAP, POP and/or SMTP 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 which includes (for example) polling for new mail, storing Fcc
-messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
-as passwords or tunnel commands but not settings such as sender
-address or name (because in general it should be considered unpredictable
-which account-hook was last used).
-</para>
-
-<para>
-Some examples:
-</para>
-
-<screen>
-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"'
-account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-</screen>
-
-</sect1>
-
-<sect1 id="caching">
-<title>Local caching</title>
-
-<para>
-Mutt contains two types of local caching: <emphasis>(1)</emphasis>
-the so-called <quote>header caching</quote> and <emphasis>(2)</emphasis> the
-so-called <quote>body caching</quote> which are both described in this section.
-</para>
-
-<para>
-Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
-support as these use it (body caching requires no external library).
-</para>
-
-<sect2 id="header-caching">
-<title>Header caching</title>
-
-<para>
-Mutt provides optional support for caching message headers for the
-following types of folders: IMAP, POP, Maildir and MH. Header caching
-greatly improves speed because for remote folders, headers
-usually only need to be downloaded once. For Maildir and MH, reading the
-headers from a single file is much faster than looking at possibly
-thousands of single files (since Maildir and MH use one file per message.)
-</para>
-
-<para>
-Header caching can be enabled via the configure script and the
-<emphasis>--enable-hcache</emphasis> option. It's not turned on
-by default because external database libraries are required: one
-of tokyocabinet, qdbm, gdbm or bdb must be present.
-</para>
-
-<para>
-If enabled, <link
-linkend="header-cache">$header_cache</link> can be
-used to either point to a file or a directory. If set to point to
-a file, one database file for all folders will be used (which may
-result in lower performance), but one file per folder if it points
-to a directory.
-</para>
-
-<para>
-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-</para>
-
-<screen>
-$ printf '%s' '/path/to/folder' | md5sum
-</screen>
-
-<para>
-The <literal>md5sum</literal> command may also be
-named <literal>md5</literal>, depending on your operating system.
-</para>
-
-</sect2>
-
-<sect2 id="body-caching">
-<title>Body caching</title>
-
-<para>
-Both cache methods can be combined using the same directory for storage
-(and for IMAP/POP even provide meaningful file names) which simplifies
-manual maintenance tasks.
-</para>
-
-
-<para>
-In addition to caching message headers only, mutt can also cache
-whole message bodies. This results in faster display of messages
-for POP and IMAP folders because messages usually have to be
-downloaded only once.
-</para>
-
-<para>
-For configuration, the variable <link linkend="message-cachedir"
->$message_cachedir</link> must point to a
-directory. There, mutt will create a hierarchy of subdirectories
-named like: <literal>proto:user@hostname</literal> where
-<literal>proto</literal> is either <quote>pop</quote> or <quote>imap.</quote> Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-</para>
-
-<para>
-All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
-</para>
-
-</sect2>
-
-<sect2 id="maint-cache">
-<title>Maintenance</title>
-
-<para>
-Mutt does not (yet) support maintenance features for header cache
-database files so that files have to be removed in case they grow too
-big. It depends on the database library used for header caching whether
-disk space freed by removing messages is re-used.
-</para>
-
-<para>
-For body caches, mutt can keep the local cache in sync with the
-remote mailbox if the
-<link linkend="message-cache-clean">$message_cache_clean</link>
-variable is set. Cleaning means to remove messages from the cache which
-are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
-delete messages (Mutt itself removes deleted messages from the cache
-when syncing a mailbox). As cleaning can take a noticeable amount of time,
-it should not be set in general but only occasionally.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="exact-address">
-<title>Exact address generation</title>
-
-<para>
-Mutt supports the <quote>Name <user@host></quote> address syntax for reading and
-writing messages, the older <quote>user@host (Name)</quote> syntax is only supported when
-reading messages. The <emphasis>--enable-exact-address</emphasis>
-switch can be given to configure to build it with write-support
-for the latter syntax. <literal>EXACT_ADDRESS</literal> in the output of
-<literal>mutt -v</literal> indicates whether it's supported.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="tuning">
-<title>Performance tuning</title>
-
-<sect1 id="tuning-mailboxes">
-<title>Reading and writing mailboxes</title>
-
-<para>
-Mutt's performance when reading mailboxes can be improved in two ways:
-</para>
-
-<orderedlist>
-
-<listitem>
-<para>
-For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
-performance can be greatly improved using
-<link linkend="header-caching">header caching</link>.
-Using a single database per folder may further increase
-performance.
-</para>
-</listitem>
-
-<listitem>
-<para>
-Mutt provides the <link linkend="read-inc">$read_inc</link>
-and <link linkend="write-inc">$write_inc</link>
-variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
-time on updating the progress counter than it spends on
-actually reading/writing folders.
-</para>
-<para>
-For example, when opening a maildir folder with a few
-thousand messages, the default value for
-<link linkend="read-inc">$read_inc</link>
-may be too low. It can be tuned on on a folder-basis using
-<link linkend="folder-hook">folder-hooks</link>:
-</para>
-
-<screen>
-# use very high $read_inc to speed up reading hcache'd maildirs
-folder-hook . 'set read_inc=1000'
-# use lower value for reading slower remote IMAP folders
-folder-hook ^imap 'set read_inc=100'
-# use even lower value for reading even slower remote POP folders
-folder-hook ^pop 'set read_inc=1'</screen>
-
-</listitem>
-</orderedlist>
-
-<para>These settings work on a per-message basis. However, as messages may
-greatly differ in size and certain operations are much faster than others,
-even per-folder settings of the increment variables may not be
-desirable as they produce either too few or too much progress updates.
-Thus, Mutt allows to limit the number of progress updates per second it'll
-actually send to the terminal using the
-<link linkend="time-inc">$time_inc</link> variable.</para>
-
-</sect1>
-
-<sect1 id="tuning-messages">
-<title>Reading messages from remote folders</title>
-
-<para>
-Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
-limited number of recently viewed messages (usually 10) per
-session (so that it will be gone for the next session.)
-</para>
-
-<para>
-To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
-<link linkend="body-caching">body caching</link> for details.
-</para>
-
-</sect1>
-
-<sect1 id="tuning-search">
-<title>Searching and limiting</title>
-
-<para>
-When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
-searches. For regular expressions, patterns are prefixed with
-<quote>˜</quote> and with <quote>=</quote> for string searches.
-</para>
-
-<para>
-Even though a regular expression search is fast, it's several times
-slower than a pure string search which is noticeable especially on large
-folders. As a consequence, a string search should be used instead of a
-regular expression search if the user already knows enough about the
-search pattern.
-</para>
-
-<para>
-For example, when limiting a large folder to all messages sent to or by
-an author, it's much faster to search for the initial part of an e-mail
-address via <literal>=Luser@</literal> instead of
-<literal>˜Luser@</literal>. This is especially true for searching
-message bodies since a larger amount of input has to be searched.
-</para>
-
-<para>
-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
-</para>
-
-</sect1>
-
-</chapter>
-
-<chapter id="reference">
-<title>Reference</title>
-
-<sect1 id="commandline">
-<title>Command line options</title>
-
-<para>
-Running <literal>mutt</literal> with no arguments will make Mutt attempt to read your spool
-mailbox. However, it is possible to read other mailboxes and
-to send messages from the command line as well.
-</para>
-
-<table id="tab-commandline-options">
-<title>Command line options</title>
-<tgroup cols="2">
-<thead>
-<row><entry>Option</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry>-A</entry><entry>expand an alias</entry></row>
-<row><entry>-a</entry><entry>attach a file to a message</entry></row>
-<row><entry>-b</entry><entry>specify a blind carbon-copy (BCC) address</entry></row>
-<row><entry>-c</entry><entry>specify a carbon-copy (Cc) address</entry></row>
-<row><entry>-D</entry><entry>print the value of all mutt variables to stdout</entry></row>
-<row><entry>-e</entry><entry>specify a config command to be run after initialization files are read</entry></row>
-<row><entry>-f</entry><entry>specify a mailbox to load</entry></row>
-<row><entry>-F</entry><entry>specify an alternate file to read initialization commands</entry></row>
-<row><entry>-h</entry><entry>print help on command line options</entry></row>
-<row><entry>-H</entry><entry>specify a draft file from which to read a header and body</entry></row>
-<row><entry>-i</entry><entry>specify a file to include in a message composition</entry></row>
-<row><entry>-m</entry><entry>specify a default mailbox type</entry></row>
-<row><entry>-n</entry><entry>do not read the system Muttrc</entry></row>
-<row><entry>-p</entry><entry>recall a postponed message</entry></row>
-<row><entry>-Q</entry><entry>query a configuration variable</entry></row>
-<row><entry>-R</entry><entry>open mailbox in read-only mode</entry></row>
-<row><entry>-s</entry><entry>specify a subject (enclose in quotes if it contains spaces)</entry></row>
-<row><entry>-v</entry><entry>show version number and compile-time definitions</entry></row>
-<row><entry>-x</entry><entry>simulate the mailx(1) compose mode</entry></row>
-<row><entry>-y</entry><entry>show a menu containing the files specified by the mailboxes command</entry></row>
-<row><entry>-z</entry><entry>exit immediately if there are no messages in the mailbox</entry></row>
-<row><entry>-Z</entry><entry>open the first folder with new message,exit immediately if none</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-To read messages in a mailbox
-</para>
-
-<cmdsynopsis>
-<command>mutt</command>
-<arg choice="opt"><option>-nz</option></arg>
-<arg choice="opt"><option>-F</option>
-<replaceable>muttrc</replaceable>
-</arg>
-<arg choice="opt"><option>-m</option>
-<replaceable>type</replaceable>
-</arg>
-<arg choice="opt"><option>-f</option>
-<replaceable>mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-To compose a new message
-</para>
-
-<cmdsynopsis>
-<command>mutt</command>
-<arg choice="opt"><option>-n</option></arg>
-<arg choice="opt"><option>-F</option>
-<replaceable>muttrc</replaceable>
-</arg>
-<arg choice="opt"><option>-c</option>
-<replaceable>address</replaceable>
-</arg>
-<arg choice="opt"><option>-i</option>
-<replaceable>filename</replaceable>
-</arg>
-<arg choice="opt"><option>-s</option>
-<replaceable>subject</replaceable>
-</arg>
-<arg choice="opt">
-<option>-a</option>
-<replaceable>file</replaceable>
-<arg choice="opt" rep="repeat"/>
---
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>address</replaceable>
-</arg>
-</cmdsynopsis>
-
-<para>
-Mutt also supports a <quote>batch</quote> mode to send prepared messages. Simply redirect
-input from the file you wish to send. For example,
-</para>
-
-<para>
-<literal>mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat</literal>
-</para>
-
-<para>
-This command will send a message to <quote>professor@bigschool.edu</quote> with a subject
-of <quote>data set for run #2</quote>. In the body of the message will be the contents
-of the file <quote>˜/run2.dat</quote>.
-</para>
-
-<para>
-All files passed with -a <emphasis>file</emphasis> will be attached as a MIME
-part to the message. To attach several files, use <quote>--</quote> to separate files and
-recipient addresses: <literal>mutt -a *.png -- some@one.org</literal>
-</para>
-
-</sect1>
-
-<sect1 id="commands">
-<title>Configuration Commands</title>
-
-<para>
-The following are the commands understood by mutt.
-</para>
-
-<itemizedlist>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="account-hook">account-hook</link></command>
-<arg choice="plain">
-<replaceable>pattern</replaceable>
-<replaceable>command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alias">alias</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">address</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">address</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alias">unalias</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">key</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alternates">alternates</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable>regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alternates">unalternates</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alternative-order">alternative-order</link></command>
-<arg choice="plain">
-<replaceable>mimetype</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="alternative-order">unalternative-order</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="auto-view">auto-view</link></command>
-<arg choice="plain">
-<replaceable>mimetype</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-<listitem>
-
-<cmdsynopsis>
-<command><link linkend="auto-view">unauto-view</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="bind">bind</link></command>
-<arg choice="plain">
-<replaceable class="parameter">map</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">function</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="charset-hook">charset-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">alias</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">charset</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="charset-hook">iconv-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">charset</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">local-charset</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="color">color</link></command>
-<arg choice="plain">
-<replaceable class="parameter">object</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command><link linkend="color">color</link></command>
-<group choice="req">
-<arg choice="plain">
-<option>header</option>
-</arg>
-<arg choice="plain">
-<option>body</option>
-</arg>
-</group>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command><link linkend="color">color</link></command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">foreground</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">background</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="color">uncolor</link></command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="exec">exec</link></command>
-<arg choice="plain">
-<replaceable class="parameter">function</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">function</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="fcc-hook">fcc-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="fcc-save-hook">fcc-save-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="folder-hook">folder-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]regexp</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="addrgroup">group</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain" rep="repeat">
-<option>-rx</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-addr</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="addrgroup">ungroup</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-rx</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<option>-addr</option>
-<replaceable class="parameter">expr</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="hdr-order">hdr_order</link></command>
-<arg choice="plain">
-<replaceable class="parameter">header</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">header</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="hdr-order">unhdr_order</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>header</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="ignore">ignore</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="ignore">unignore</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="lists">lists</link></command>
-<arg>
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="lists">unlists</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="macro">macro</link></command>
-<arg choice="plain">
-<replaceable class="parameter">menu</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">key</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">sequence</replaceable>
-</arg>
-<arg choice="opt">
-<replaceable class="parameter">description</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mailboxes">mailboxes</link></command>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mailboxes">unmailboxes</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mbox-hook">mbox-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="message-hook">message-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mime-lookup">mime-lookup</link></command>
-<arg choice="plain">
-<replaceable>mimetype</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mime-lookup">unmime-lookup</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable>*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable>mimetype</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mono">mono</link></command>
-<arg choice="plain">
-<replaceable class="parameter">object</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command><link linkend="mono">mono</link></command>
-<group choice="req">
-<arg choice="plain">
-<option>header</option>
-</arg>
-<arg choice="plain">
-<option>body</option>
-</arg>
-</group>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-<cmdsynopsis>
-<command><link linkend="mono">mono</link></command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">attribute</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="mono">unmono</link></command>
-<arg choice="plain">
-<option>index</option>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="my-hdr">my_hdr</link></command>
-<arg choice="plain">
-<replaceable class="parameter">string</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="my-hdr">unmy_hdr</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">field</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="crypt-hook">crypt-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">keyid</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="push">push</link></command>
-<arg choice="plain">
-<replaceable class="parameter">string</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">reset</link></command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="save-hook">save-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">mailbox</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="score">score</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">value</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="score">unscore</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="reply-hook">reply-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="send-hook">send-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="send2-hook">send2-hook</link></command>
-<arg choice="plain">
-<replaceable class="parameter">[!]pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">command</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">set</link></command>
-<group choice="req">
-<arg choice="plain">
-<group choice="opt">
-<arg choice="plain"><option>no</option></arg>
-<arg choice="plain"><option>inv</option></arg>
-</group>
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">variable=value</replaceable>
-</arg>
-</group>
-<arg choice="opt" rep="repeat"/>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">unset</link></command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="source">source</link></command>
-<arg choice="plain">
-<replaceable class="parameter">filename</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="spam">spam</link></command>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">format</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="spam">nospam</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">pattern</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="subscribe">subscribe</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable class="parameter">name</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="subscribe">unsubscribe</link></command>
-<arg choice="opt" rep="repeat">
-<option>-group</option>
-<replaceable>name</replaceable>
-</arg>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain" rep="repeat">
-<replaceable class="parameter">regexp</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="set">toggle</link></command>
-<arg choice="plain">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-<arg choice="opt" rep="repeat">
-<replaceable class="parameter">variable</replaceable>
-</arg>
-</cmdsynopsis>
-</listitem>
-
-<listitem>
-<cmdsynopsis>
-<command><link linkend="unhook">unhook</link></command>
-<group choice="req">
-<arg choice="plain">
-<replaceable class="parameter">*</replaceable>
-</arg>
-<arg choice="plain">
-<replaceable class="parameter">hook-type</replaceable>
-</arg>
-</group>
-</cmdsynopsis>
-</listitem>
-
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="variables">
-<title>Configuration variables</title>
-
-<sect2 id="abort-nosubject">
-<title>abort_nosubject</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-If set to <emphasis>yes</emphasis>, when composing messages and no subject is given
-at the subject prompt, composition will be aborted. If set to
-<emphasis>no</emphasis>, composing messages with no subject given at the subject
-prompt will never be aborted.
-</para>
-</sect2>
-
-<sect2 id="abort-unmodified">
-<title>abort_unmodified</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-If set to <emphasis>yes</emphasis>, composition will automatically abort after
-editing the message body if no changes are made to the file (this
-check only happens after the <emphasis>first</emphasis> edit of the file). When set
-to <emphasis>no</emphasis>, composition will never be aborted.
-</para>
-</sect2>
-
-<sect2 id="alias-file">
-<title>alias_file</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/.muttrc</literal></quote></literallayout>
-
-<para>
-The default file in which to save aliases created by the
-<literal><link linkend="create-alias"><create-alias></link></literal> function. Entries added to this file are
-encoded in the character set specified by <link linkend="config-charset">$config_charset</link> if it
-is <emphasis>set</emphasis> or the current character set otherwise.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> Mutt will not automatically source this file; you must
-explicitly use the <quote><link linkend="source">source</link></quote> command for it to be executed in case
-this option points to a dedicated alias file.
-</para>
-<para>
-The default for this option is the currently used muttrc file, or
-<quote>˜/.muttrc</quote> if no user muttrc was found.
-</para>
-</sect2>
-
-<sect2 id="alias-format">
-<title>alias_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4n %2f %t %-10a %r</literal></quote></literallayout>
-
-<para>
-Specifies the format of the data displayed for the <quote><link linkend="alias">alias</link></quote> menu. The
-following <literal>printf(3)</literal>-style sequences are available:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%a </term>
-<listitem><para>alias name
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>flags - currently, a <quote>d</quote> for an alias marked for deletion
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>index number
-</para></listitem></varlistentry>
-<varlistentry><term>%r </term>
-<listitem><para>address which alias expands to
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para>character which indicates if the alias is tagged for inclusion
-</para></listitem></varlistentry></variablelist>
-</sect2>
-
-<sect2 id="allow-8bit">
-<title>allow_8bit</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether 8-bit data is converted to 7-bit using either Quoted-
-Printable or Base64 encoding when sending mail.
-</para>
-</sect2>
-
-<sect2 id="allow-ansi">
-<title>allow_ansi</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-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 <emphasis>set</emphasis>,
-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
-
-</para>
-
-<screen>
-[-- PGP output follows ...
-
-</screen><para>
-and give it the same color as your attachment color (see also
-<link linkend="crypt-timestamp">$crypt_timestamp</link>).
-</para>
-</sect2>
-
-<sect2 id="arrow-cursor">
-<title>arrow_cursor</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, an arrow (<quote>-></quote>) 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.
-</para>
-</sect2>
-
-<sect2 id="ascii-chars">
-<title>ascii_chars</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will use plain ASCII characters when displaying thread
-and attachment trees, instead of the default <emphasis>ACS</emphasis> characters.
-</para>
-</sect2>
-
-<sect2 id="askbcc">
-<title>askbcc</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
-before editing an outgoing message.
-</para>
-</sect2>
-
-<sect2 id="askcc">
-<title>askcc</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will prompt you for carbon-copy (Cc) recipients before
-editing the body of an outgoing message.
-</para>
-</sect2>
-
-<sect2 id="assumed-charset">
-<title>assumed_charset</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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 <quote>us-ascii</quote>.
-</para>
-<para>
-For example, Japanese users might prefer this:
-
-</para>
-
-<screen>
-set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</screen><para>
-However, only the first content is valid for the message body.
-</para>
-</sect2>
-
-<sect2 id="attach-charset">
-<title>attach_charset</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This variable is a colon-separated list of character encoding
-schemes for text file attachments. Mutt uses this setting to guess
-which encoding files being attached are encoded in to convert them to
-a proper character set given in <link linkend="send-charset">$send_charset</link>.
-</para>
-<para>
-If <emphasis>unset</emphasis>, the value of <link linkend="charset">$charset</link> will be used instead.
-For example, the following configuration would work for Japanese
-text handling:
-
-</para>
-
-<screen>
-set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</screen><para>
-Note: for Japanese users, <quote>iso-2022-*</quote> must be put at the head
-of the value as shown above if included.
-</para>
-</sect2>
-
-<sect2 id="attach-format">
-<title>attach_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] </literal></quote></literallayout>
-
-<para>
-This variable describes the format of the <quote>attachment</quote> menu. The
-following <literal>printf(3)</literal>-style sequences are understood:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%C </term>
-<listitem><para>charset
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>requires charset conversion (<quote>n</quote> or <quote>c</quote>)
-</para></listitem></varlistentry>
-<varlistentry><term>%D </term>
-<listitem><para>deleted flag
-</para></listitem></varlistentry>
-<varlistentry><term>%d </term>
-<listitem><para>description
-</para></listitem></varlistentry>
-<varlistentry><term>%e </term>
-<listitem><para>MIME content-transfer-encoding
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>filename
-</para></listitem></varlistentry>
-<varlistentry><term>%I </term>
-<listitem><para>disposition (<quote>I</quote> for inline, <quote>A</quote> for attachment)
-</para></listitem></varlistentry>
-<varlistentry><term>%m </term>
-<listitem><para>major MIME type
-</para></listitem></varlistentry>
-<varlistentry><term>%M </term>
-<listitem><para>MIME subtype
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>attachment number
-</para></listitem></varlistentry>
-<varlistentry><term>%Q </term>
-<listitem><para><quote>Q</quote>, if MIME part qualifies for attachment counting
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>size
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para>tagged flag
-</para></listitem></varlistentry>
-<varlistentry><term>%T </term>
-<listitem><para>graphic tree characters
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>unlink (=to delete) flag
-</para></listitem></varlistentry>
-<varlistentry><term>%X </term>
-<listitem><para>number of qualifying MIME parts in this part and its children
-(please see the <quote><link linkend="attachments">attachments</link></quote> section for possible speed effects)
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For an explanation of <quote>soft-fill</quote>, see the <link linkend="index-format">$index_format</link> documentation.
-</para>
-</sect2>
-
-<sect2 id="attach-sep">
-<title>attach_sep</title>
-<literallayout>Type: string
-Default: <quote><literal>\n</literal></quote></literallayout>
-
-<para>
-The separator to add between attachments when operating (saving,
-printing, piping, etc) on a list of tagged attachments.
-</para>
-</sect2>
-
-<sect2 id="attach-split">
-<title>attach_split</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If this variable is <emphasis>unset</emphasis>, when operating (saving, printing, piping,
-etc) on a list of tagged attachments, Mutt will concatenate the
-attachments and will operate on them as a single attachment. The
-<link linkend="attach-sep">$attach_sep</link> separator is added after each attachment. When <emphasis>set</emphasis>,
-Mutt will operate on the attachments one by one.
-</para>
-</sect2>
-
-<sect2 id="attribution">
-<title>attribution</title>
-<literallayout>Type: string
-Default: <quote><literal>On %d, %n wrote:</literal></quote></literallayout>
-
-<para>
-This is the string that will precede a message which has been included
-in a reply. For a full listing of defined <literal>printf(3)</literal>-like sequences see
-the section on <link linkend="index-format">$index_format</link>.
-</para>
-</sect2>
-
-<sect2 id="autoedit">
-<title>autoedit</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis> along with <link linkend="edit-headers">$edit_headers</link>, Mutt will skip the initial
-send-menu (prompting for subject and recipients) 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.
-</para>
-<para>
-Also see <link linkend="fast-reply">$fast_reply</link>.
-</para>
-</sect2>
-
-<sect2 id="auto-tag">
-<title>auto_tag</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, functions in the <emphasis>index</emphasis> menu which affect a message
-will be applied to all tagged messages (if there are any). When
-unset, you must first use the <literal><tag-prefix></literal> function (bound to <quote>;</quote>
-by default) to make the next function apply to all tagged messages.
-</para>
-</sect2>
-
-<sect2 id="beep">
-<title>beep</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will beep when an error occurs.
-</para>
-</sect2>
-
-<sect2 id="beep-new">
-<title>beep_new</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will beep whenever it prints a message
-notifying you of new mail. This is independent of the setting of the
-<link linkend="beep">$beep</link> variable.
-</para>
-</sect2>
-
-<sect2 id="bounce">
-<title>bounce</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether you will be asked to confirm bouncing messages.
-If set to <emphasis>yes</emphasis> you don't get asked if you want to bounce a
-message. Setting this variable to <emphasis>no</emphasis> is not generally useful,
-and thus not recommended, because you are unable to bounce messages.
-</para>
-</sect2>
-
-<sect2 id="bounce-delivered">
-<title>bounce_delivered</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will include Delivered-To headers when
-bouncing messages. Postfix users may wish to <emphasis>unset</emphasis> this variable.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this option is unset by default in
-/etc/Muttrc.
-</para>
-</sect2>
-
-<sect2 id="braille-friendly">
-<title>braille_friendly</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will place the cursor at the beginning
-of the current line in menus, even when the <link linkend="arrow-cursor">$arrow_cursor</link> variable
-is <emphasis>unset</emphasis>, making it easier for blind persons using Braille displays to
-follow these menus. The option is <emphasis>unset</emphasis> by default because many
-visual terminals don't permit making the cursor invisible.
-</para>
-</sect2>
-
-<sect2 id="check-mbox-size">
-<title>check_mbox_size</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
-</para>
-<para>
-This variable is <emphasis>unset</emphasis> by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
-</para>
-<para>
-Note that enabling this variable should happen before any <quote><link linkend="mailboxes">mailboxes</link></quote>
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-</para>
-</sect2>
-
-<sect2 id="charset">
-<title>charset</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Character set your terminal uses to display and enter textual data.
-It is also the fallback for <link linkend="send-charset">$send_charset</link>.
-</para>
-<para>
-Upon startup Mutt tries to derive this value from environment variables
-such as <literal>$LC_CTYPE</literal> or <literal>$LANG</literal>.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> It should only be set in case Mutt isn't abled to determine the
-character set used correctly.
-</para>
-</sect2>
-
-<sect2 id="check-new">
-<title>check_new</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-<emphasis role="bold">Note:</emphasis> this option only affects <emphasis>maildir</emphasis> and <emphasis>MH</emphasis> style
-mailboxes.
-</para>
-<para>
-When <emphasis>set</emphasis>, Mutt 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
-this variable is <emphasis>unset</emphasis>, no check for new mail is performed
-while the mailbox is open.
-</para>
-</sect2>
-
-<sect2 id="collapse-unread">
-<title>collapse_unread</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, Mutt will not collapse a thread if it contains any
-unread messages.
-</para>
-</sect2>
-
-<sect2 id="uncollapse-jump">
-<title>uncollapse_jump</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will jump to the next unread message, if any,
-when the current thread is <emphasis>un</emphasis>collapsed.
-</para>
-</sect2>
-
-<sect2 id="compose-format">
-<title>compose_format</title>
-<literallayout>Type: string
-Default: <quote><literal>-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-</literal></quote></literallayout>
-
-<para>
-Controls the format of the status line displayed in the <quote>compose</quote>
-menu. This string is similar to <link linkend="status-format">$status_format</link>, but has its own
-set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%a </term>
-<listitem><para>total number of attachments
-</para></listitem></varlistentry>
-<varlistentry><term>%h </term>
-<listitem><para>local hostname
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>approximate size (in bytes) of the current message
-</para></listitem></varlistentry>
-<varlistentry><term>%v </term>
-<listitem><para>Mutt version string
-</para></listitem></varlistentry></variablelist>
-
-<para>
-See the text describing the <link linkend="status-format">$status_format</link> option for more
-information on how to set <link linkend="compose-format">$compose_format</link>.
-</para>
-</sect2>
-
-<sect2 id="config-charset">
-<title>config_charset</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-When defined, Mutt will recode commands in rc files from this
-encoding to the current character set as specified by <link linkend="charset">$charset</link>
-and aliases written to <link linkend="alias-file">$alias_file</link> from the current character set.
-</para>
-<para>
-Please note that if setting <link linkend="charset">$charset</link> it must be done before
-setting <link linkend="config-charset">$config_charset</link>.
-</para>
-<para>
-Recoding should be avoided as it may render unconvertable
-characters as question marks which can lead to undesired
-side effects (for example in regular expressions).
-</para>
-</sect2>
-
-<sect2 id="confirmappend">
-<title>confirmappend</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will prompt for confirmation when appending messages to
-an existing mailbox.
-</para>
-</sect2>
-
-<sect2 id="confirmcreate">
-<title>confirmcreate</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will prompt for confirmation when saving messages to a
-mailbox which does not yet exist before creating it.
-</para>
-</sect2>
-
-<sect2 id="connect-timeout">
-<title>connect_timeout</title>
-<literallayout>Type: number
-Default: 30</literallayout>
-
-<para>
-Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-many seconds if the connection is not able to be established. A negative
-value causes Mutt to wait indefinitely for the connection attempt to succeed.
-</para>
-</sect2>
-
-<sect2 id="content-type">
-<title>content_type</title>
-<literallayout>Type: string
-Default: <quote><literal>text/plain</literal></quote></literallayout>
-
-<para>
-Sets the default Content-Type for the body of newly composed messages.
-</para>
-</sect2>
-
-<sect2 id="copy">
-<title>copy</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not copies of your outgoing messages
-will be saved for later references. Also see <link linkend="record">$record</link>,
-<link linkend="save-name">$save_name</link>, <link linkend="force-name">$force_name</link> and <quote><link linkend="fcc-hook">fcc-hook</link></quote>.
-</para>
-</sect2>
-
-<sect2 id="crypt-use-gpgme">
-<title>crypt_use_gpgme</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable controls the use of the GPGME-enabled crypto backends.
-If it is <emphasis>set</emphasis> and Mutt was built with gpgme support, the gpgme code for
-S/MIME and PGP will be used instead of the classic code. Note that
-you need to set this option in .muttrc; it won't have any effect when
-used interactively.
-</para>
-</sect2>
-
-<sect2 id="crypt-use-pka">
-<title>crypt_use_pka</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Controls whether mutt uses PKA
-(see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
-verification (only supported by the GPGME backend).
-</para>
-</sect2>
-
-<sect2 id="crypt-autopgp">
-<title>crypt_autopgp</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages. See also <link linkend="crypt-autoencrypt">$crypt_autoencrypt</link>,
-<link linkend="crypt-replyencrypt">$crypt_replyencrypt</link>,
-<link linkend="crypt-autosign">$crypt_autosign</link>, <link linkend="crypt-replysign">$crypt_replysign</link> and <link linkend="smime-is-default">$smime_is_default</link>.
-</para>
-</sect2>
-
-<sect2 id="crypt-autosmime">
-<title>crypt_autosmime</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also <link linkend="crypt-autoencrypt">$crypt_autoencrypt</link>,
-<link linkend="crypt-replyencrypt">$crypt_replyencrypt</link>,
-<link linkend="crypt-autosign">$crypt_autosign</link>, <link linkend="crypt-replysign">$crypt_replysign</link> and <link linkend="smime-is-default">$smime_is_default</link>.
-</para>
-</sect2>
-
-<sect2 id="date-format">
-<title>date_format</title>
-<literallayout>Type: string
-Default: <quote><literal>!%a, %b %d, %Y at %I:%M:%S%p %Z</literal></quote></literallayout>
-
-<para>
-This variable controls the format of the date printed by the <quote>%d</quote>
-sequence in <link linkend="index-format">$index_format</link>. This is passed to the <literal>strftime(3)</literal>
-function to process the date, see the man page for the proper syntax.
-</para>
-<para>
-Unless the first character in the string is a bang (<quote>!</quote>), the month
-and week day names are expanded according to the locale specified in
-the variable <link linkend="locale">$locale</link>. 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 <emphasis>C</emphasis> locale (that is in US
-English).
-</para>
-</sect2>
-
-<sect2 id="default-hook">
-<title>default_hook</title>
-<literallayout>Type: string
-Default: <quote><literal>˜f %s !˜P | (˜P ˜C %s)</literal></quote></literallayout>
-
-<para>
-This variable controls how <quote><link linkend="message-hook">message-hook</link></quote>, <quote><link linkend="reply-hook">reply-hook</link></quote>, <quote><link linkend="send-hook">send-hook</link></quote>,
-<quote><link linkend="send2-hook">send2-hook</link></quote>, <quote><link linkend="save-hook">save-hook</link></quote>, and <quote><link linkend="fcc-hook">fcc-hook</link></quote> 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.
-</para>
-<para>
-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
-<quote><link linkend="alternates">alternates</link></quote>) and is to or cc'ed to a user matching the given
-regular expression.
-</para>
-</sect2>
-
-<sect2 id="delete">
-<title>delete</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not messages are really deleted when closing or
-synchronizing a mailbox. If set to <emphasis>yes</emphasis>, messages marked for
-deleting will automatically be purged without prompting. If set to
-<emphasis>no</emphasis>, messages marked for deletion will be kept in the mailbox.
-</para>
-</sect2>
-
-<sect2 id="delete-untag">
-<title>delete_untag</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If this option is <emphasis>set</emphasis>, mutt 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.
-</para>
-</sect2>
-
-<sect2 id="digest-collapse">
-<title>digest_collapse</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If this option is <emphasis>set</emphasis>, mutt's received-attachments menu will not show the subparts of
-individual messages in a multipart/digest. To see these subparts, press <quote>v</quote> on that menu.
-</para>
-</sect2>
-
-<sect2 id="display-filter">
-<title>display_filter</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-When set, specifies a command used to filter messages. When a message
-is viewed it is passed as standard input to <link linkend="display-filter">$display_filter</link>, and the
-filtered message is read from the standard output.
-</para>
-</sect2>
-
-<sect2 id="dotlock-program">
-<title>dotlock_program</title>
-<literallayout>Type: path
-Default: <quote><literal>/usr/bin/mutt_dotlock</literal></quote></literallayout>
-
-<para>
-Contains the path of the <literal>mutt_dotlock(8)</literal> binary to be used by
-mutt.
-</para>
-</sect2>
-
-<sect2 id="dsn-notify">
-<title>dsn_notify</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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: <emphasis>never</emphasis>, to never request notification,
-<emphasis>failure</emphasis>, to request notification on transmission failure,
-<emphasis>delay</emphasis>, to be notified of message delays, <emphasis>success</emphasis>, to be
-notified of successful transmission.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set dsn_notify="failure,delay"
-
-</screen><para>
-<emphasis role="bold">Note:</emphasis> when using <link linkend="sendmail">$sendmail</link> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <literal>sendmail(1)</literal>-compatible interface supporting the <literal>-N</literal> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</para>
-</sect2>
-
-<sect2 id="dsn-return">
-<title>dsn_return</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This variable controls how much of your message is returned in DSN
-messages. It may be set to either <emphasis>hdrs</emphasis> to return just the
-message header, or <emphasis>full</emphasis> to return the full message.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set dsn_return=hdrs
-
-</screen><para>
-<emphasis role="bold">Note:</emphasis> when using <link linkend="sendmail">$sendmail</link> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <literal>sendmail(1)</literal>-compatible interface supporting the <literal>-R</literal> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</para>
-</sect2>
-
-<sect2 id="duplicate-threads">
-<title>duplicate_threads</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable controls whether mutt, when <link linkend="sort">$sort</link> is set to <emphasis>threads</emphasis>, threads
-messages with the same Message-Id together. If it is <emphasis>set</emphasis>, it will indicate
-that it thinks they are duplicates of each other with an equals sign
-in the thread tree.
-</para>
-</sect2>
-
-<sect2 id="edit-headers">
-<title>edit_headers</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This option allows you to edit the header of your outgoing messages
-along with the body of your message.
-</para>
-<para>
-<emphasis role="bold">Note</emphasis> that changes made to the References: and Date: headers are
-ignored for interoperability reasons.
-</para>
-</sect2>
-
-<sect2 id="editor">
-<title>editor</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable specifies which editor is used by mutt.
-It defaults to the value of the <literal>$VISUAL</literal>, or <literal>$EDITOR</literal>, environment
-variable, or to the string <quote>/usr/bin/editor</quote> if neither of those are set.
-</para>
-</sect2>
-
-<sect2 id="encode-from">
-<title>encode_from</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will quoted-printable encode messages when
-they contain the string <quote>From </quote> (note the trailing space) in the beginning of a line.
-This is useful to avoid the tampering certain mail delivery and transport
-agents tend to do with messages (in order to prevent tools from
-misinterpreting the line as a mbox message separator).
-</para>
-</sect2>
-
-<sect2 id="envelope-from-address">
-<title>envelope_from_address</title>
-<literallayout>Type: e-mail address
-Default: (empty)</literallayout>
-
-<para>
-Manually sets the <emphasis>envelope</emphasis> sender for outgoing messages.
-This value is ignored if <link linkend="use-envelope-from">$use_envelope_from</link> is <emphasis>unset</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="escape">
-<title>escape</title>
-<literallayout>Type: string
-Default: <quote><literal>˜</literal></quote></literallayout>
-
-<para>
-Escape character to use for functions in the builtin editor.
-</para>
-</sect2>
-
-<sect2 id="fast-reply">
-<title>fast_reply</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the initial prompt for recipients and subject are skipped
-when replying to messages, and the initial prompt for subject is
-skipped when forwarding messages.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> this variable has no effect when the <link linkend="autoedit">$autoedit</link>
-variable is <emphasis>set</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="fcc-attach">
-<title>fcc_attach</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not attachments on outgoing messages
-are saved along with the main body of your message.
-</para>
-</sect2>
-
-<sect2 id="fcc-clear">
-<title>fcc_clear</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, FCCs will be stored unencrypted and
-unsigned, even when the actual message is encrypted and/or
-signed.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="folder">
-<title>folder</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/Mail</literal></quote></literallayout>
-
-<para>
-Specifies the default location of your mailboxes. A <quote>+</quote> or <quote>=</quote> 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 <emphasis>before</emphasis>
-you use <quote>+</quote> or <quote>=</quote> for any other variables since expansion takes place
-when handling the <quote><link linkend="mailboxes">mailboxes</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="folder-format">
-<title>folder_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f</literal></quote></literallayout>
-
-<para>
-This variable allows you to customize the file browser display to your
-personal taste. This string is similar to <link linkend="index-format">$index_format</link>, but has
-its own set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%C </term>
-<listitem><para>current file number
-</para></listitem></varlistentry>
-<varlistentry><term>%d </term>
-<listitem><para>date/time folder was last modified
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>filename
-</para></listitem></varlistentry>
-<varlistentry><term>%F </term>
-<listitem><para>file permissions
-</para></listitem></varlistentry>
-<varlistentry><term>%g </term>
-<listitem><para>group name (or numeric gid, if missing)
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>number of hard links
-</para></listitem></varlistentry>
-<varlistentry><term>%N </term>
-<listitem><para>N if folder has new mail, blank otherwise
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>size in bytes
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para><quote>*</quote> if the file is tagged, blank otherwise
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>owner name (or numeric uid, if missing)
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For an explanation of <quote>soft-fill</quote>, see the <link linkend="index-format">$index_format</link> documentation.
-</para>
-</sect2>
-
-<sect2 id="followup-to">
-<title>followup_to</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether or not the <quote>Mail-Followup-To:</quote> header field is
-generated when sending mail. When <emphasis>set</emphasis>, Mutt will generate this
-field when you are replying to a known mailing list, specified with
-the <quote><link linkend="subscribe">subscribe</link></quote> or <quote><link linkend="lists">lists</link></quote> commands.
-</para>
-<para>
-This field has two purposes. First, preventing you from
-receiving duplicate copies of replies to messages which you send
-to mailing lists, and second, ensuring that you do get a reply
-separately for any messages sent to known lists to which you are
-not subscribed.
-</para>
-<para>
-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.
-</para>
-</sect2>
-
-<sect2 id="force-name">
-<title>force_name</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable is similar to <link linkend="save-name">$save_name</link>, except that Mutt 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.
-</para>
-<para>
-Also see the <link linkend="record">$record</link> variable.
-</para>
-</sect2>
-
-<sect2 id="forward-decode">
-<title>forward_decode</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls the decoding of complex MIME messages into <literal>text/plain</literal> when
-forwarding a message. The message header is also RFC2047 decoded.
-This variable is only used, if <link linkend="mime-forward">$mime_forward</link> is <emphasis>unset</emphasis>,
-otherwise <link linkend="mime-forward-decode">$mime_forward_decode</link> is used instead.
-</para>
-</sect2>
-
-<sect2 id="forward-edit">
-<title>forward_edit</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-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 <quote>no</quote>.
-</para>
-</sect2>
-
-<sect2 id="forward-format">
-<title>forward_format</title>
-<literallayout>Type: string
-Default: <quote><literal>[%a: %s]</literal></quote></literallayout>
-
-<para>
-This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the <link linkend="index-format">$index_format</link> variable.
-</para>
-</sect2>
-
-<sect2 id="forward-quote">
-<title>forward_quote</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, forwarded messages included in the main body of the
-message (when <link linkend="mime-forward">$mime_forward</link> is <emphasis>unset</emphasis>) will be quoted using
-<link linkend="indent-string">$indent_string</link>.
-</para>
-</sect2>
-
-<sect2 id="from">
-<title>from</title>
-<literallayout>Type: e-mail address
-Default: (empty)</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, this variable contains a default from address. It
-can be overridden using <quote><link linkend="my-hdr">my_hdr</link></quote> (including from a <quote><link linkend="send-hook">send-hook</link></quote>) and
-<link linkend="reverse-name">$reverse_name</link>. This variable is ignored if <link linkend="use-from">$use_from</link> is <emphasis>unset</emphasis>.
-</para>
-<para>
-This setting defaults to the contents of the environment variable <literal>$EMAIL</literal>.
-</para>
-</sect2>
-
-<sect2 id="gecos-mask">
-<title>gecos_mask</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>ˆ[ˆ,]*</literal></quote></literallayout>
-
-<para>
-A regular expression used by mutt to parse the GECOS field of a password
-entry when expanding the alias. The default value
-will return the string up to the first <quote>,</quote> encountered.
-If the GECOS field contains a string like <quote>lastname, firstname</quote> then you
-should set it to <quote><literal>.*</literal></quote>.
-</para>
-<para>
-This can be useful if you see the following behavior: you address an e-mail
-to user ID <quote>stevef</quote> whose full name is <quote>Steve Franklin</quote>. If mutt expands
-<quote>stevef</quote> to <quote>"Franklin" stevef@foo.bar</quote> then you should set the <link linkend="gecos-mask">$gecos_mask</link> to
-a regular expression that will match the whole name so mutt will expand
-<quote>Franklin</quote> to <quote>Franklin, Steve</quote>.
-</para>
-</sect2>
-
-<sect2 id="hdrs">
-<title>hdrs</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, the header fields normally added by the <quote><link linkend="my-hdr">my_hdr</link></quote>
-command are not created. This variable <emphasis>must</emphasis> be unset before
-composing a new message or replying in order to take effect. If <emphasis>set</emphasis>,
-the user defined header fields are added to every new message.
-</para>
-</sect2>
-
-<sect2 id="header">
-<title>header</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, this variable causes Mutt to include the header
-of the message you are replying to into the edit buffer.
-The <link linkend="weed">$weed</link> setting applies.
-</para>
-</sect2>
-
-<sect2 id="help">
-<title>help</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, help lines describing the bindings for the major functions
-provided by each menu are displayed on the first line of the screen.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> 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 is
-running. Since this variable is primarily aimed at new users, neither
-of these should present a major problem.
-</para>
-</sect2>
-
-<sect2 id="hidden-host">
-<title>hidden_host</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will skip the host name part of <link linkend="hostname">$hostname</link> variable
-when adding the domain part to addresses. This variable does not
-affect the generation of Message-IDs, and it will not lead to the
-cut-off of first-level domains.
-</para>
-</sect2>
-
-<sect2 id="hide-limited">
-<title>hide_limited</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the presence of messages that are hidden
-by limiting, in the thread tree.
-</para>
-</sect2>
-
-<sect2 id="hide-missing">
-<title>hide_missing</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the presence of missing messages in the
-thread tree.
-</para>
-</sect2>
-
-<sect2 id="hide-thread-subject">
-<title>hide_thread_subject</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the subject of messages in the thread
-tree that have the same subject as their parent or closest previously
-displayed sibling.
-</para>
-</sect2>
-
-<sect2 id="hide-top-limited">
-<title>hide_top_limited</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the presence of messages that are hidden
-by limiting, at the top of threads in the thread tree. Note that when
-<link linkend="hide-limited">$hide_limited</link> is <emphasis>set</emphasis>, this option will have no effect.
-</para>
-</sect2>
-
-<sect2 id="hide-top-missing">
-<title>hide_top_missing</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not show the presence of missing messages at the
-top of threads in the thread tree. Note that when <link linkend="hide-missing">$hide_missing</link> is
-<emphasis>set</emphasis>, this option will have no effect.
-</para>
-</sect2>
-
-<sect2 id="history">
-<title>history</title>
-<literallayout>Type: number
-Default: 10</literallayout>
-
-<para>
-This variable controls the size (in number of strings remembered) of
-the string history buffer per category. The buffer is cleared each time the
-variable is set.
-</para>
-</sect2>
-
-<sect2 id="history-file">
-<title>history_file</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/.mutthistory</literal></quote></literallayout>
-
-<para>
-The file in which Mutt will save its history.
-</para>
-</sect2>
-
-<sect2 id="honor-followup-to">
-<title>honor_followup_to</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-This variable controls whether or not a Mail-Followup-To header is
-honored when group-replying to a message.
-</para>
-</sect2>
-
-<sect2 id="hostname">
-<title>hostname</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Specifies the fully-qualified hostname of the system mutt is running on
-containing the host's name and the DNS domain it belongs to. It is used
-as the domain part (after <quote>@</quote>) for local email addresses as well as
-Message-Id headers.
-</para>
-<para>
-Its value is determined at startup as follows: If the node's name
-as returned by the <literal>uname(3)</literal> function contains the hostname and the
-domain, these are used to construct <link linkend="hostname">$hostname</link>. If there is no
-domain part returned, Mutt will look for a <quote>domain</quote> or <quote>search</quote>
-line in <literal>/etc/resolv.conf</literal> to determine the domain. Optionally, Mutt
-can be compiled with a fixed domain name in which case a detected
-one is not used.
-</para>
-<para>
-Also see <link linkend="use-domain">$use_domain</link> and <link linkend="hidden-host">$hidden_host</link>.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, the default for this variable is obtained
-from /etc/mailname when Mutt starts.
-</para>
-</sect2>
-
-<sect2 id="ignore-linear-white-space">
-<title>ignore_linear_white_space</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This option replaces linear-white-space between encoded-word
-and text to a single space to prevent the display of MIME-encoded
-<quote>Subject:</quote> field from being divided into multiple lines.
-</para>
-</sect2>
-
-<sect2 id="ignore-list-reply-to">
-<title>ignore_list_reply_to</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Affects the behaviour of the <literal><reply></literal> function when replying to
-messages from mailing lists (as defined by the <quote><link linkend="subscribe">subscribe</link></quote> or
-<quote><link linkend="lists">lists</link></quote> commands). When <emphasis>set</emphasis>, if the <quote>Reply-To:</quote> field is
-set to the same value as the <quote>To:</quote> field, Mutt assumes that the
-<quote>Reply-To:</quote> 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 <emphasis>set</emphasis>, use the <literal><link linkend="list-reply"><list-reply></link></literal>
-function; <literal><group-reply></literal> will reply to both the sender and the
-list.
-</para>
-</sect2>
-
-<sect2 id="imap-authenticators">
-<title>imap_authenticators</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an IMAP server, in the order mutt should
-try them. Authentication methods are either <quote>login</quote> or the right
-side of an IMAP <quote>AUTH=xxx</quote> capability string, eg <quote>digest-md5</quote>, <quote>gssapi</quote>
-or <quote>cram-md5</quote>. This option is case-insensitive. If it's
-<emphasis>unset</emphasis> (the default) mutt will try all available methods,
-in order from most-secure to least-secure.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set imap_authenticators="gssapi:cram-md5:login"
-
-</screen><para>
-<emphasis role="bold">Note:</emphasis> Mutt will only fall back to other authentication methods if
-the previous methods are unavailable. If a method is available but
-authentication fails, mutt will not connect to the IMAP server.
-</para>
-</sect2>
-
-<sect2 id="imap-check-subscribed">
-<title>imap_check_subscribed</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, 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 just as if you had issued individual <quote><link linkend="mailboxes">mailboxes</link></quote>
-commands.
-</para>
-</sect2>
-
-<sect2 id="imap-delim-chars">
-<title>imap_delim_chars</title>
-<literallayout>Type: string
-Default: <quote><literal>/.</literal></quote></literallayout>
-
-<para>
-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 <quote>=</quote> shortcut for your <emphasis>folder</emphasis> variable.
-</para>
-</sect2>
-
-<sect2 id="imap-headers">
-<title>imap_headers</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Mutt requests these header fields in addition to the default headers
-(<quote>Date:</quote>, <quote>From:</quote>, <quote>Subject:</quote>, <quote>To:</quote>, <quote>Cc:</quote>, <quote>Message-Id:</quote>,
-<quote>References:</quote>, <quote>Content-Type:</quote>, <quote>Content-Description:</quote>, <quote>In-Reply-To:</quote>,
-<quote>Reply-To:</quote>, <quote>Lines:</quote>, <quote>List-Post:</quote>, <quote>X-Label:</quote>) from IMAP
-servers before displaying the index menu. You may want to add more
-headers for spam detection.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> This is a space separated list, items should be uppercase
-and not contain the colon, e.g. <quote>X-BOGOSITY X-SPAM-STATUS</quote> for the
-<quote>X-Bogosity:</quote> and <quote>X-Spam-Status:</quote> header fields.
-</para>
-</sect2>
-
-<sect2 id="imap-idle">
-<title>imap_idle</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will attempt to use the IMAP IDLE extension
-to check for new mail in the current mailbox. Some servers
-(dovecot was the inspiration for this option) react badly
-to mutt's implementation. If your connection seems to freeze
-up periodically, try unsetting this.
-</para>
-</sect2>
-
-<sect2 id="imap-keepalive">
-<title>imap_keepalive</title>
-<literallayout>Type: number
-Default: 900</literallayout>
-
-<para>
-This variable specifies the maximum amount of time in seconds that mutt
-will wait before polling open IMAP connections, to prevent the server
-from closing them before mutt 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.
-</para>
-</sect2>
-
-<sect2 id="imap-list-subscribed">
-<title>imap_list_subscribed</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-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 <literal><toggle-subscribed></literal> function.
-</para>
-</sect2>
-
-<sect2 id="imap-login">
-<title>imap_login</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Your login name on the IMAP server.
-</para>
-<para>
-This variable defaults to the value of <link linkend="imap-user">$imap_user</link>.
-</para>
-</sect2>
-
-<sect2 id="imap-pass">
-<title>imap_pass</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Specifies the password for your IMAP account. If <emphasis>unset</emphasis>, Mutt will
-prompt you for your password when you invoke the <literal><link linkend="fetch-mail"><fetch-mail></link></literal> function
-or try to open an IMAP folder.
-</para>
-<para>
-<emphasis role="bold">Warning</emphasis>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</para>
-</sect2>
-
-<sect2 id="imap-passive">
-<title>imap_passive</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will not open new IMAP connections to check for new
-mail. Mutt 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 invocation, or if opening the connection
-is slow.
-</para>
-</sect2>
-
-<sect2 id="imap-peek">
-<title>imap_peek</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt 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.
-</para>
-</sect2>
-
-<sect2 id="imap-pipeline-depth">
-<title>imap_pipeline_depth</title>
-<literallayout>Type: number
-Default: 15</literallayout>
-
-<para>
-Controls the number of IMAP commands that may be queued up before they
-are sent to the server. A deeper pipeline reduces the amount of time
-mutt must wait for the server, and can make IMAP servers feel much
-more responsive. But not all servers correctly handle pipelined commands,
-so if you have problems you might want to try setting this variable to 0.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> Changes to this variable have no effect on open connections.
-</para>
-</sect2>
-
-<sect2 id="imap-servernoise">
-<title>imap_servernoise</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt 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.
-</para>
-</sect2>
-
-<sect2 id="imap-user">
-<title>imap_user</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-The name of the user whose mail you intend to access on the IMAP
-server.
-</para>
-<para>
-This variable defaults to your user name on the local machine.
-</para>
-</sect2>
-
-<sect2 id="implicit-autoview">
-<title>implicit_autoview</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If set to <quote>yes</quote>, mutt will look for a mailcap entry with the
-<quote><literal>copiousoutput</literal></quote> flag set for <emphasis>every</emphasis> MIME attachment it doesn't have
-an internal viewer defined for. If such an entry is found, mutt will
-use the viewer defined in that entry to convert the body part to text
-form.
-</para>
-</sect2>
-
-<sect2 id="include">
-<title>include</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not a copy of the message(s) you are replying to
-is included in your reply.
-</para>
-</sect2>
-
-<sect2 id="include-onlyfirst">
-<title>include_onlyfirst</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Controls whether or not Mutt includes only the first attachment
-of the message you are replying.
-</para>
-</sect2>
-
-<sect2 id="indent-string">
-<title>indent_string</title>
-<literallayout>Type: string
-Default: <quote><literal>> </literal></quote></literallayout>
-
-<para>
-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.
-</para>
-<para>
-This option is a format string, please see the description of
-<link linkend="index-format">$index_format</link> for supported <literal>printf(3)</literal>-style sequences.
-</para>
-<para>
-Because for <literal>format=lowed</literal> style messages the quoting mechanism
-is strictly defined, this setting is ignored if <link linkend="text-flowed">$text_flowed</link> is
-<emphasis>set</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="index-format">
-<title>index_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s</literal></quote></literallayout>
-
-<para>
-This variable allows you to customize the message index display to
-your personal taste.
-</para>
-<para>
-<quote>Format strings</quote> are similar to the strings used in the C
-function <literal>printf(3)</literal> to format output (see the man page for more details).
-The following sequences are defined in Mutt:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%a </term>
-<listitem><para>address of the author
-</para></listitem></varlistentry>
-<varlistentry><term>%A </term>
-<listitem><para>reply-to address (if present; otherwise: address of author)
-</para></listitem></varlistentry>
-<varlistentry><term>%b </term>
-<listitem><para>filename of the original message folder (think mailbox)
-</para></listitem></varlistentry>
-<varlistentry><term>%B </term>
-<listitem><para>the list to which the letter was sent, or else the folder name (%b).
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>number of characters (bytes) in the message
-</para></listitem></varlistentry>
-<varlistentry><term>%C </term>
-<listitem><para>current message number
-</para></listitem></varlistentry>
-<varlistentry><term>%d </term>
-<listitem><para>date and time of the message in the format specified by
-<link linkend="date-format">$date_format</link> converted to sender's time zone
-</para></listitem></varlistentry>
-<varlistentry><term>%D </term>
-<listitem><para>date and time of the message in the format specified by
-<link linkend="date-format">$date_format</link> converted to the local time zone
-</para></listitem></varlistentry>
-<varlistentry><term>%e </term>
-<listitem><para>current message number in thread
-</para></listitem></varlistentry>
-<varlistentry><term>%E </term>
-<listitem><para>number of messages in current thread
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>sender (address + real name), either From: or Return-Path:
-</para></listitem></varlistentry>
-<varlistentry><term>%F </term>
-<listitem><para>author name, or recipient name if the message is from you
-</para></listitem></varlistentry>
-<varlistentry><term>%H </term>
-<listitem><para>spam attribute(s) of this message
-</para></listitem></varlistentry>
-<varlistentry><term>%i </term>
-<listitem><para>message-id of the current message
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>number of lines in the message (does not work with maildir,
-mh, and possibly IMAP folders)
-</para></listitem></varlistentry>
-<varlistentry><term>%L </term>
-<listitem><para>If an address in the <quote>To:</quote> or <quote>Cc:</quote> header field matches an address
-defined by the users <quote><link linkend="subscribe">subscribe</link></quote> command, this displays
-"To <list-name>", otherwise the same as %F.
-</para></listitem></varlistentry>
-<varlistentry><term>%m </term>
-<listitem><para>total number of message in the mailbox
-</para></listitem></varlistentry>
-<varlistentry><term>%M </term>
-<listitem><para>number of hidden messages if the thread is collapsed.
-</para></listitem></varlistentry>
-<varlistentry><term>%N </term>
-<listitem><para>message score
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>author's real name (or address if missing)
-</para></listitem></varlistentry>
-<varlistentry><term>%O </term>
-<listitem><para>original save folder where mutt would formerly have
-stashed the message: list name or recipient name
-if not sent to a list
-</para></listitem></varlistentry>
-<varlistentry><term>%P </term>
-<listitem><para>progress indicator for the builtin pager (how much of the file has been displayed)
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>subject of the message
-</para></listitem></varlistentry>
-<varlistentry><term>%S </term>
-<listitem><para>status of the message (<quote>N</quote>/<quote>D</quote>/<quote>d</quote>/<quote>!</quote>/<quote>r</quote>/*)
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para><quote>To:</quote> field (recipients)
-</para></listitem></varlistentry>
-<varlistentry><term>%T </term>
-<listitem><para>the appropriate character from the <link linkend="to-chars">$to_chars</link> string
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>user (login) name of the author
-</para></listitem></varlistentry>
-<varlistentry><term>%v </term>
-<listitem><para>first name of the author, or the recipient if the message is from you
-</para></listitem></varlistentry>
-<varlistentry><term>%X </term>
-<listitem><para>number of attachments
-(please see the <quote><link linkend="attachments">attachments</link></quote> section for possible speed effects)
-</para></listitem></varlistentry>
-<varlistentry><term>%y </term>
-<listitem><para><quote>X-Label:</quote> field, if present
-</para></listitem></varlistentry>
-<varlistentry><term>%Y </term>
-<listitem><para><quote>X-Label:</quote> field, if present, and <emphasis>(1)</emphasis> not at part of a thread tree,
-<emphasis>(2)</emphasis> at the top of a thread, or <emphasis>(3)</emphasis> <quote>X-Label:</quote> is different from
-preceding message's <quote>X-Label:</quote>.
-</para></listitem></varlistentry>
-<varlistentry><term>%Z </term>
-<listitem><para>message status flags
-</para></listitem></varlistentry>
-<varlistentry><term>%{fmt} </term>
-<listitem><para>the date and time of the message is converted to sender's
-time zone, and <quote>fmt</quote> is expanded by the library function
-<literal>strftime(3)</literal>; a leading bang disables locales
-</para></listitem></varlistentry>
-<varlistentry><term>%[fmt] </term>
-<listitem><para>the date and time of the message is converted to the local
-time zone, and <quote>fmt</quote> is expanded by the library function
-<literal>strftime(3)</literal>; a leading bang disables locales
-</para></listitem></varlistentry>
-<varlistentry><term>%(fmt) </term>
-<listitem><para>the local date and time when the message was received.
-<quote>fmt</quote> is expanded by the library function <literal>strftime(3)</literal>;
-a leading bang disables locales
-</para></listitem></varlistentry>
-<varlistentry><term>%<fmt> </term>
-<listitem><para>the current local time. <quote>fmt</quote> is expanded by the library
-function <literal>strftime(3)</literal>; a leading bang disables locales.
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with character <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-<quote>Soft-fill</quote> deserves some explanation: Normal right-justification
-will print everything to the left of the <quote>%></quote>, displaying padding and
-whatever lies to the right only if there's room. By contrast,
-soft-fill gives priority to the right-hand side, guaranteeing space
-to display it and showing padding only if there's still room. If
-necessary, soft-fill will eat text leftwards to make room for
-rightward text.
-</para>
-<para>
-Note that these expandos are supported in
-<quote><link linkend="save-hook">save-hook</link></quote>, <quote><link linkend="fcc-hook">fcc-hook</link></quote> and <quote><link linkend="fcc-save-hook">fcc-save-hook</link></quote>, too.
-</para>
-</sect2>
-
-<sect2 id="ispell">
-<title>ispell</title>
-<literallayout>Type: path
-Default: <quote><literal>ispell</literal></quote></literallayout>
-
-<para>
-How to invoke ispell (GNU's spell-checking software).
-</para>
-</sect2>
-
-<sect2 id="keep-flagged">
-<title>keep_flagged</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, read messages marked as flagged will not be moved
-from your spool mailbox to your <link linkend="mbox">$mbox</link> mailbox, or as a result of
-a <quote><link linkend="mbox-hook">mbox-hook</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="locale">
-<title>locale</title>
-<literallayout>Type: string
-Default: <quote><literal>C</literal></quote></literallayout>
-
-<para>
-The locale used by <literal>strftime(3)</literal> to format dates. Legal values are
-the strings your system accepts for the locale environment variable <literal>$LC_TIME</literal>.
-</para>
-</sect2>
-
-<sect2 id="mail-check">
-<title>mail_check</title>
-<literallayout>Type: number
-Default: 5</literallayout>
-
-<para>
-This variable configures how often (in seconds) mutt should look for
-new mail. Also see the <link linkend="timeout">$timeout</link> variable.
-</para>
-</sect2>
-
-<sect2 id="mailcap-path">
-<title>mailcap_path</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This variable specifies which files to consult when attempting to
-display MIME bodies not directly supported by Mutt.
-</para>
-</sect2>
-
-<sect2 id="mailcap-sanitize">
-<title>mailcap_sanitize</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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.
-</para>
-<para>
-<emphasis role="bold">DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
-DOING!</emphasis>
-</para>
-</sect2>
-
-<sect2 id="maildir-mtime">
-<title>maildir_mtime</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If set, the sort-by-date option in the browser will sort maildirs
-smartly, not using the mtime of the maildir itself but that of the
-newest message in the new subdirectory, making the sorting by
-reverse date much more useful. People with maildirs over NFS may
-wish to leave this option unset.
-</para>
-</sect2>
-
-<sect2 id="header-cache">
-<title>header_cache</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is <emphasis>unset</emphasis> so no header
-caching will be used.
-</para>
-<para>
-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see <quote><link linkend="caching">caching</link></quote> for details.
-</para>
-</sect2>
-
-<sect2 id="maildir-header-cache-verify">
-<title>maildir_header_cache_verify</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Check for Maildir unaware programs other than mutt having modified maildir
-files when the header cache is in use. This incurs one <literal>stat(2)</literal> per
-message every time the folder is opened (which can be very slow for NFS
-folders).
-</para>
-</sect2>
-
-<sect2 id="header-cache-pagesize">
-<title>header_cache_pagesize</title>
-<literallayout>Type: string
-Default: <quote><literal>16384</literal></quote></literallayout>
-
-<para>
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-</para>
-</sect2>
-
-<sect2 id="maildir-trash">
-<title>maildir_trash</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, messages marked as deleted will be saved with the maildir
-trashed flag instead of unlinked. <emphasis role="bold">Note:</emphasis> this only applies
-to maildir-style mailboxes. Setting it will have no effect on other
-mailbox types.
-</para>
-</sect2>
-
-<sect2 id="mark-old">
-<title>mark_old</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether or not mutt marks <emphasis>new</emphasis> <emphasis role="bold">unread</emphasis>
-messages as <emphasis>old</emphasis> if you exit a mailbox without reading them.
-With this option <emphasis>set</emphasis>, the next time you start mutt, the messages
-will show up with an <quote>O</quote> next to them in the index menu,
-indicating that they are old.
-</para>
-</sect2>
-
-<sect2 id="markers">
-<title>markers</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls the display of wrapped lines in the internal pager. If set, a
-<quote>+</quote> marker is displayed at the beginning of wrapped lines.
-</para>
-<para>
-Also see the <link linkend="smart-wrap">$smart_wrap</link> variable.
-</para>
-</sect2>
-
-<sect2 id="mask">
-<title>mask</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>!ˆ\.[ˆ.]</literal></quote></literallayout>
-
-<para>
-A regular expression used in the file browser, optionally preceded by
-the <emphasis>not</emphasis> operator <quote>!</quote>. Only files whose names match this mask
-will be shown. The match is always case-sensitive.
-</para>
-</sect2>
-
-<sect2 id="mbox">
-<title>mbox</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/mbox</literal></quote></literallayout>
-
-<para>
-This specifies the folder into which read mail in your <link linkend="spoolfile">$spoolfile</link>
-folder will be appended.
-</para>
-<para>
-Also see the <link linkend="move">$move</link> variable.
-</para>
-</sect2>
-
-<sect2 id="mbox-type">
-<title>mbox_type</title>
-<literallayout>Type: folder magic
-Default: mbox</literallayout>
-
-<para>
-The default mailbox type used when creating new folders. May be any of
-<quote>mbox</quote>, <quote>MMDF</quote>, <quote>MH</quote> and <quote>Maildir</quote>.
-</para>
-</sect2>
-
-<sect2 id="metoo">
-<title>metoo</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>unset</emphasis>, Mutt will remove your address (see the <quote><link linkend="alternates">alternates</link></quote>
-command) from the list of recipients when replying to a message.
-</para>
-</sect2>
-
-<sect2 id="menu-context">
-<title>menu_context</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to <link linkend="pager-context">$pager_context</link>.)
-</para>
-</sect2>
-
-<sect2 id="menu-move-off">
-<title>menu_move_off</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, the bottom entry of menus will never scroll up past
-the bottom of the screen, unless there are less entries than lines.
-When <emphasis>set</emphasis>, the bottom entry may move off the bottom.
-</para>
-</sect2>
-
-<sect2 id="menu-scroll">
-<title>menu_scroll</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, menus will be scrolled up or down one line when you
-attempt to move across a screen boundary. If <emphasis>unset</emphasis>, the screen
-is cleared and the next or previous page of the menu is displayed
-(useful for slow links to avoid many redraws).
-</para>
-</sect2>
-
-<sect2 id="meta-key">
-<title>meta_key</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, forces Mutt 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 <literal>0xf8</literal>, then this is treated as if the user had
-pressed Esc then <quote>x</quote>. This is because the result of removing the
-high bit from <literal>0xf8</literal> is <literal>0x78</literal>, which is the ASCII character
-<quote>x</quote>.
-</para>
-</sect2>
-
-<sect2 id="mh-purge">
-<title>mh_purge</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, mutt will mimic mh's behaviour and rename deleted messages
-to <emphasis>,<old file name></emphasis> in mh folders instead of really deleting
-them. This leaves the message on disk but makes programs reading the folder
-ignore it. If the variable is <emphasis>set</emphasis>, the message files will simply be
-deleted.
-</para>
-<para>
-This option is similar to <link linkend="maildir-trash">$maildir_trash</link> for Maildir folders.
-</para>
-</sect2>
-
-<sect2 id="mh-seq-flagged">
-<title>mh_seq_flagged</title>
-<literallayout>Type: string
-Default: <quote><literal>flagged</literal></quote></literallayout>
-
-<para>
-The name of the MH sequence used for flagged messages.
-</para>
-</sect2>
-
-<sect2 id="mh-seq-replied">
-<title>mh_seq_replied</title>
-<literallayout>Type: string
-Default: <quote><literal>replied</literal></quote></literallayout>
-
-<para>
-The name of the MH sequence used to tag replied messages.
-</para>
-</sect2>
-
-<sect2 id="mh-seq-unseen">
-<title>mh_seq_unseen</title>
-<literallayout>Type: string
-Default: <quote><literal>unseen</literal></quote></literallayout>
-
-<para>
-The name of the MH sequence used for unseen messages.
-</para>
-</sect2>
-
-<sect2 id="mime-forward">
-<title>mime_forward</title>
-<literallayout>Type: quadoption
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the message you are forwarding will be attached as a
-separate <literal>message/rfc822</literal> 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 <quote>ask-no</quote> or <quote>ask-yes</quote>.
-</para>
-<para>
-Also see <link linkend="forward-decode">$forward_decode</link> and <link linkend="mime-forward-decode">$mime_forward_decode</link>.
-</para>
-</sect2>
-
-<sect2 id="mime-forward-decode">
-<title>mime_forward_decode</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Controls the decoding of complex MIME messages into <literal>text/plain</literal> when
-forwarding a message while <link linkend="mime-forward">$mime_forward</link> is <emphasis>set</emphasis>. Otherwise
-<link linkend="forward-decode">$forward_decode</link> is used instead.
-</para>
-</sect2>
-
-<sect2 id="mime-forward-rest">
-<title>mime_forward_rest</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-When forwarding multiple attachments of a MIME message from the attachment
-menu, attachments which cannot be decoded in a reasonable manner will
-be attached to the newly composed message if this option is <emphasis>set</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="mix-entry-format">
-<title>mix_entry_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4n %c %-16s %a</literal></quote></literallayout>
-
-<para>
-This variable describes the format of a remailer line on the mixmaster
-chain selection screen. The following <literal>printf(3)</literal>-like sequences are
-supported:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%n </term>
-<listitem><para>The running number on the menu.
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>Remailer capabilities.
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>The remailer's short name.
-</para></listitem></varlistentry>
-<varlistentry><term>%a </term>
-<listitem><para>The remailer's e-mail address.
-</para></listitem></varlistentry></variablelist>
-</sect2>
-
-<sect2 id="mixmaster">
-<title>mixmaster</title>
-<literallayout>Type: path
-Default: <quote><literal>mixmaster</literal></quote></literallayout>
-
-<para>
-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.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this option is set by default to
-<quote>mixmaster-filter</quote> in /etc/Muttrc.
-</para>
-</sect2>
-
-<sect2 id="move">
-<title>move</title>
-<literallayout>Type: quadoption
-Default: no</literallayout>
-
-<para>
-Controls whether or not Mutt will move read messages
-from your spool mailbox to your <link linkend="mbox">$mbox</link> mailbox, or as a result of
-a <quote><link linkend="mbox-hook">mbox-hook</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="message-cachedir">
-<title>message_cachedir</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-</para>
-<para>
-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-</para>
-<para>
-Also see the <link linkend="message-cache-clean">$message_cache_clean</link> variable.
-</para>
-</sect2>
-
-<sect2 id="message-cache-clean">
-<title>message_cache_clean</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-</para>
-</sect2>
-
-<sect2 id="message-format">
-<title>message_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%s</literal></quote></literallayout>
-
-<para>
-This is the string displayed in the <quote>attachment</quote> menu for
-attachments of type <literal>message/rfc822</literal>. For a full listing of defined
-<literal>printf(3)</literal>-like sequences see the section on <link linkend="index-format">$index_format</link>.
-</para>
-</sect2>
-
-<sect2 id="narrow-tree">
-<title>narrow_tree</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable, when <emphasis>set</emphasis>, makes the thread tree narrower, allowing
-deeper threads to fit on the screen.
-</para>
-</sect2>
-
-<sect2 id="net-inc">
-<title>net_inc</title>
-<literallayout>Type: number
-Default: 10</literallayout>
-
-<para>
-Operations that expect to transfer a large amount of data over the
-network will update their progress every <link linkend="net-inc">$net_inc</link> kilobytes.
-If set to 0, no progress messages will be displayed.
-</para>
-<para>
-See also <link linkend="read-inc">$read_inc</link>, <link linkend="write-inc">$write_inc</link> and <link linkend="net-inc">$net_inc</link>.
-</para>
-</sect2>
-
-<sect2 id="pager">
-<title>pager</title>
-<literallayout>Type: path
-Default: <quote><literal>builtin</literal></quote></literallayout>
-
-<para>
-This variable specifies which pager you would like to use to view
-messages. The value <quote>builtin</quote> means to use the builtin pager, otherwise this
-variable should specify the pathname of the external pager you would
-like to use.
-</para>
-<para>
-Using an external pager may have some disadvantages: Additional
-keystrokes are necessary because you can't call mutt functions
-directly from the pager, and screen resizes cause lines longer than
-the screen width to be badly formatted in the help menu.
-</para>
-</sect2>
-
-<sect2 id="pager-context">
-<title>pager_context</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-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 will display the line after the last one on the screen
-at the top of the next page (0 lines of context).
-</para>
-</sect2>
-
-<sect2 id="pager-format">
-<title>pager_format</title>
-<literallayout>Type: string
-Default: <quote><literal>-%Z- %C/%m: %-20.20n %s%* -- (%P)</literal></quote></literallayout>
-
-<para>
-This variable controls the format of the one-line message <quote>status</quote>
-displayed before each message in either the internal or an external
-pager. The valid sequences are listed in the <link linkend="index-format">$index_format</link>
-section.
-</para>
-</sect2>
-
-<sect2 id="pager-index-lines">
-<title>pager_index_lines</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-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 setting 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 <link linkend="pager-index-lines">$pager_index_lines</link>, then the index will only use as
-many lines as it needs.
-</para>
-</sect2>
-
-<sect2 id="pager-stop">
-<title>pager_stop</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the internal-pager will <emphasis role="bold">not</emphasis> move to the next message
-when you are at the end of a message and invoke the <literal><next-page></literal>
-function.
-</para>
-</sect2>
-
-<sect2 id="crypt-autosign">
-<title>crypt_autosign</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Setting this variable will cause Mutt 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 <link linkend="smime-is-default">$smime_is_default</link> is <emphasis>set</emphasis>,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="crypt-autoencrypt">
-<title>crypt_autoencrypt</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages. This is probably only useful in
-connection to the <quote><link linkend="send-hook">send-hook</link></quote> command. It can be overridden
-by use of the pgp menu, when encryption is not required or
-signing is requested as well. If <link linkend="smime-is-default">$smime_is_default</link> is <emphasis>set</emphasis>,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="pgp-ignore-subkeys">
-<title>pgp_ignore_subkeys</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities. <emphasis>Unset</emphasis> this
-if you want to play interesting key selection games.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="crypt-replyencrypt">
-<title>crypt_replyencrypt</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="crypt-replysign">
-<title>crypt_replysign</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, automatically PGP or OpenSSL sign replies to messages which are
-signed.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> this does not work on messages that are encrypted
-<emphasis>and</emphasis> signed!
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="crypt-replysignencrypted">
-<title>crypt_replysignencrypted</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, automatically PGP or OpenSSL sign replies to messages
-which are encrypted. This makes sense in combination with
-<link linkend="crypt-replyencrypt">$crypt_replyencrypt</link>, because it allows you to sign all
-messages which are automatically encrypted. This works around
-the problem noted in <link linkend="crypt-replysign">$crypt_replysign</link>, that mutt is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="crypt-timestamp">
-<title>crypt_timestamp</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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 <emphasis>unset</emphasis> this setting.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="pgp-use-gpg-agent">
-<title>pgp_use_gpg_agent</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt will use a possibly-running <literal>gpg-agent(1)</literal> process.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="crypt-verify-sig">
-<title>crypt_verify_sig</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-If <emphasis><quote>yes</quote></emphasis>, always attempt to verify PGP or S/MIME signatures.
-If <emphasis><quote>ask-*</quote></emphasis>, ask whether or not to verify the signature.
-If \Fi<quote>no</quote>, never attempt to verify cryptographic signatures.
-(Crypto only)
-</para>
-</sect2>
-
-<sect2 id="smime-is-default">
-<title>smime_is_default</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-The default behaviour of mutt is to use PGP on all auto-sign/encryption
-operations. To override and to use OpenSSL instead this must be <emphasis>set</emphasis>.
-However, this has no effect while replying, since mutt will automatically
-select the same application that was used to sign/encrypt the original
-message. (Note that this variable can be overridden by unsetting <link linkend="crypt-autosmime">$crypt_autosmime</link>.)
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-ask-cert-label">
-<title>smime_ask_cert_label</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-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
-<emphasis>set</emphasis> by default.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-decrypt-use-default-key">
-<title>smime_decrypt_use_default_key</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis> (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate-key-pairs, mutt 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)
-</para>
-</sect2>
-
-<sect2 id="pgp-entry-format">
-<title>pgp_entry_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4n %t%f %4l/0x%k %-4a %2c %u</literal></quote></literallayout>
-
-<para>
-This variable allows you to customize the PGP key selection menu to
-your personal taste. This string is similar to <link linkend="index-format">$index_format</link>, but
-has its own set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%n </term>
-<listitem><para>number
-</para></listitem></varlistentry>
-<varlistentry><term>%k </term>
-<listitem><para>key id
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>user id
-</para></listitem></varlistentry>
-<varlistentry><term>%a </term>
-<listitem><para>algorithm
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>key length
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>flags
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>capabilities
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para>trust/validity of the key-uid association
-</para></listitem></varlistentry>
-<varlistentry><term>%[<s>] </term>
-<listitem><para>date of the key where <s> is an <literal>strftime(3)</literal> expression
-</para></listitem></varlistentry></variablelist>
-
-<para>
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-good-sign">
-<title>pgp_good_sign</title>
-<literallayout>Type: regular expression
-Default: (empty)</literallayout>
-
-<para>
-If you assign a text to this variable, then a PGP signature is only
-considered verified if the output from <link linkend="pgp-verify-command">$pgp_verify_command</link> contains
-the text. Use this variable if the exit code from the command is 0
-even for bad signatures.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-check-exit">
-<title>pgp_check_exit</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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)
-</para>
-</sect2>
-
-<sect2 id="pgp-long-ids">
-<title>pgp_long_ids</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, use 64 bit PGP key IDs, if <emphasis>unset</emphasis> use the normal 32 bit key IDs.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-retainable-sigs">
-<title>pgp_retainable_sigs</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, signed and encrypted messages will consist of nested
-<literal>multipart/signed</literal> and <literal>multipart/encrypted</literal> body parts.
-</para>
-<para>
-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (<literal>multipart/encrypted</literal>) can be easily
-removed, while the inner <literal>multipart/signed</literal> part is retained.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-autoinline">
-<title>pgp_autoinline</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This option controls whether Mutt 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.
-</para>
-<para>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</para>
-<para>
-Also see the <link linkend="pgp-mime-auto">$pgp_mime_auto</link> variable.
-</para>
-<para>
-Also note that using the old-style PGP message format is <emphasis role="bold">strongly</emphasis>
-<emphasis role="bold">deprecated</emphasis>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-replyinline">
-<title>pgp_replyinline</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Setting this variable will cause Mutt 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
-internals for previously checked/flagged messages.
-</para>
-<para>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</para>
-<para>
-Also see the <link linkend="pgp-mime-auto">$pgp_mime_auto</link> variable.
-</para>
-<para>
-Also note that using the old-style PGP message format is <emphasis role="bold">strongly</emphasis>
-<emphasis role="bold">deprecated</emphasis>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-show-unusable">
-<title>pgp_show_unusable</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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 <quote>disabled</quote> by the user.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-sign-as">
-<title>pgp_sign_as</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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. <literal>0x00112233</literal>).
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-strict-enc">
-<title>pgp_strict_enc</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt 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)
-</para>
-</sect2>
-
-<sect2 id="pgp-timeout">
-<title>pgp_timeout</title>
-<literallayout>Type: number
-Default: 300</literallayout>
-
-<para>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-sort-keys">
-<title>pgp_sort_keys</title>
-<literallayout>Type: sort order
-Default: address</literallayout>
-
-<para>
-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-
-</para>
-
-<variablelist>
-<varlistentry><term>address </term>
-<listitem><para>sort alphabetically by user id
-</para></listitem></varlistentry>
-<varlistentry><term>keyid </term>
-<listitem><para>sort alphabetically by key id
-</para></listitem></varlistentry>
-<varlistentry><term>date </term>
-<listitem><para>sort by key creation date
-</para></listitem></varlistentry>
-<varlistentry><term>trust </term>
-<listitem><para>sort by the trust of the key
-</para></listitem></varlistentry></variablelist>
-
-<para>
-If you prefer reverse order of the above values, prefix it with
-<quote>reverse-</quote>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-mime-auto">
-<title>pgp_mime_auto</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-</para>
-<para>
-Also note that using the old-style PGP message format is <emphasis role="bold">strongly</emphasis>
-<emphasis role="bold">deprecated</emphasis>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-auto-decode">
-<title>pgp_auto_decode</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt 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 <literal><link linkend="check-traditional-pgp"><check-traditional-pgp></link></literal> function, mutt will automatically
-check the message for traditional pgp.
-</para>
-</sect2>
-
-<sect2 id="pgp-mime-signature-filename">
-<title>pgp_mime_signature_filename</title>
-<literallayout>Type: string
-Default: <quote><literal>signature.asc</literal></quote></literallayout>
-
-<para>
-This option sets the filename used for signature parts in PGP/MIME
-signed messages.
-</para>
-</sect2>
-
-<sect2 id="pgp-mime-signature-description">
-<title>pgp_mime_signature_description</title>
-<literallayout>Type: string
-Default: <quote><literal>Digital signature</literal></quote></literallayout>
-
-<para>
-This option sets the Content-Description used for signature parts in
-PGP/MIME signed messages.
-</para>
-</sect2>
-
-<sect2 id="pgp-decode-command">
-<title>pgp_decode_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This format strings specifies a command which is used to decode
-application/pgp attachments.
-</para>
-<para>
-The PGP command formats have their own set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%p </term>
-<listitem><para>Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-string otherwise. Note: This may be used with a %? construct.
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>Expands to the name of a file containing a message.
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>Expands to the name of a file containing the signature part
- of a <literal>multipart/signed</literal> attachment when verifying it.
-</para></listitem></varlistentry>
-<varlistentry><term>%a </term>
-<listitem><para>The value of <link linkend="pgp-sign-as">$pgp_sign_as</link>.
-</para></listitem></varlistentry>
-<varlistentry><term>%r </term>
-<listitem><para>One or more key IDs.
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For examples on how to configure these formats for the various versions
-of PGP which are floating around, see the pgp and gpg sample configuration files in
-the <literal>samples/</literal> subdirectory which has been installed on your system
-alongside the documentation.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-getkeys-command">
-<title>pgp_getkeys_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by <link linkend="pgp-decode-command">$pgp_decode_command</link>, %r is the only
-<literal>printf(3)</literal>-like sequence used with this format.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-verify-command">
-<title>pgp_verify_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to verify PGP signatures.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-decrypt-command">
-<title>pgp_decrypt_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to decrypt a PGP encrypted message.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-clearsign-command">
-<title>pgp_clearsign_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This format is used to create an old-style <quote>clearsigned</quote> PGP
-message. Note that the use of this format is <emphasis role="bold">strongly</emphasis>
-<emphasis role="bold">deprecated</emphasis>.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-sign-command">
-<title>pgp_sign_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to create the detached PGP signature for a
-<literal>multipart/signed</literal> PGP/MIME body part.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-encrypt-sign-command">
-<title>pgp_encrypt_sign_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to both sign and encrypt a body part.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-encrypt-only-command">
-<title>pgp_encrypt_only_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to encrypt a body part without signing it.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-import-command">
-<title>pgp_import_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to import a key from a message into
-the user's public key ring.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-export-command">
-<title>pgp_export_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to export a public key from the user's
-key ring.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-verify-key-command">
-<title>pgp_verify_key_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to verify key information from the key selection
-menu.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-list-secring-command">
-<title>pgp_list_secring_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to list the secret key ring's contents. The
-output format must be analogous to the one used by:
-
-</para>
-
-<screen>
-gpg --list-keys --with-colons.
-
-</screen><para>
-This format is also generated by the <literal>pgpring</literal> utility which comes
-with mutt.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="pgp-list-pubring-command">
-<title>pgp_list_pubring_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to list the public key ring's contents. The
-output format must be analogous to the one used by
-
-</para>
-
-<screen>
-gpg --list-keys --with-colons.
-
-</screen><para>
-This format is also generated by the <literal>pgpring</literal> utility which comes
-with mutt.
-</para>
-<para>
-This is a format string, see the <link linkend="pgp-decode-command">$pgp_decode_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="forward-decrypt">
-<title>forward_decrypt</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls the handling of encrypted messages when forwarding a message.
-When <emphasis>set</emphasis>, the outer layer of encryption is stripped off. This
-variable is only used if <link linkend="mime-forward">$mime_forward</link> is <emphasis>set</emphasis> and
-<link linkend="mime-forward-decode">$mime_forward_decode</link> is <emphasis>unset</emphasis>.
-(PGP only)
-</para>
-</sect2>
-
-<sect2 id="smime-timeout">
-<title>smime_timeout</title>
-<literallayout>Type: number
-Default: 300</literallayout>
-
-<para>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-encrypt-with">
-<title>smime_encrypt_with</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This sets the algorithm that should be used for encryption.
-Valid choices are <quote>des</quote>, <quote>des3</quote>, <quote>rc2-40</quote>, <quote>rc2-64</quote>, <quote>rc2-128</quote>.
-If <emphasis>unset</emphasis>, <quote>3des</quote> (TripleDES) is used.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-keys">
-<title>smime_keys</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and 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 option points to the location of the private keys.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-ca-location">
-<title>smime_ca_location</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this defaults to the first existing file in
-the following list: ˜/.smime/ca-certificates.crt ˜/.smime/ca-bundle.crt
-/etc/ssl/certs/ca-certificates.crt.
-</para>
-</sect2>
-
-<sect2 id="smime-certificates">
-<title>smime_certificates</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-the location of the certificates.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-decrypt-command">
-<title>smime_decrypt_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This format string specifies a command which is used to decrypt
-<literal>application/x-pkcs7-mime</literal> attachments.
-</para>
-<para>
-The OpenSSL command formats have their own set of <literal>printf(3)</literal>-like sequences
-similar to PGP's:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%f </term>
-<listitem><para>Expands to the name of a file containing a message.
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>Expands to the name of a file containing the signature part
- of a <literal>multipart/signed</literal> attachment when verifying it.
-</para></listitem></varlistentry>
-<varlistentry><term>%k </term>
-<listitem><para>The key-pair specified with <link linkend="smime-default-key">$smime_default_key</link>
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>One or more certificate IDs.
-</para></listitem></varlistentry>
-<varlistentry><term>%a </term>
-<listitem><para>The algorithm used for encryption.
-</para></listitem></varlistentry>
-<varlistentry><term>%C </term>
-<listitem><para>CA location: Depending on whether <link linkend="smime-ca-location">$smime_ca_location</link>
- points to a directory or file, this expands to
- <quote>-CApath <link linkend="smime-ca-location">$smime_ca_location</link></quote> or <quote>-CAfile <link linkend="smime-ca-location">$smime_ca_location</link></quote>.
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For examples on how to configure these formats, see the <literal>smime.rc</literal> in
-the <literal>samples/</literal> subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-verify-command">
-<title>smime_verify_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to verify S/MIME signatures of type <literal>multipart/signed</literal>.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-verify-opaque-command">
-<title>smime_verify_opaque_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to verify S/MIME signatures of type
-<literal>application/x-pkcs7-mime</literal>.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-sign-command">
-<title>smime_sign_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to created S/MIME signatures of type
-<literal>multipart/signed</literal>, which can be read by all mail clients.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-sign-opaque-command">
-<title>smime_sign_opaque_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to created S/MIME signatures of type
-<literal>application/x-pkcs7-signature</literal>, which can only be handled by mail
-clients supporting the S/MIME extension.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-encrypt-command">
-<title>smime_encrypt_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to create encrypted S/MIME messages.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-pk7out-command">
-<title>smime_pk7out_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-get-cert-command">
-<title>smime_get_cert_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to extract X509 certificates from a PKCS7 structure.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-get-signer-cert-command">
-<title>smime_get_signer_cert_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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 <quote>From:</quote> field.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-import-cert-command">
-<title>smime_import_cert_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This command is used to import a certificate via smime_keys.
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-get-cert-email-command">
-<title>smime_get_cert_email_command</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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).
-</para>
-<para>
-This is a format string, see the <link linkend="smime-decrypt-command">$smime_decrypt_command</link> command for
-possible <literal>printf(3)</literal>-like sequences.
-(S/MIME only)
-</para>
-</sect2>
-
-<sect2 id="smime-default-key">
-<title>smime_default_key</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-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)
-</para>
-</sect2>
-
-<sect2 id="ssl-client-cert">
-<title>ssl_client_cert</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-The file containing a client certificate and its associated private
-key.
-</para>
-</sect2>
-
-<sect2 id="ssl-force-tls">
-<title>ssl_force_tls</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If this variable is <emphasis>set</emphasis>, Mutt 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 <link linkend="ssl-starttls">$ssl_starttls</link>.
-</para>
-</sect2>
-
-<sect2 id="ssl-starttls">
-<title>ssl_starttls</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis> (the default), mutt will attempt to use <literal>STARTTLS</literal> on servers
-advertising the capability. When <emphasis>unset</emphasis>, mutt will not attempt to
-use <literal>STARTTLS</literal> regardless of the server's capabilities.
-</para>
-</sect2>
-
-<sect2 id="certificate-file">
-<title>certificate_file</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/.mutt_certificates</literal></quote></literallayout>
-
-<para>
-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.
-</para>
-<para>
-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set certificate_file=~/.mutt/certificates
-
-</screen></sect2>
-
-<sect2 id="ssl-use-sslv3">
-<title>ssl_use_sslv3</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-</para>
-</sect2>
-
-<sect2 id="ssl-use-tlsv1">
-<title>ssl_use_tlsv1</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-</para>
-</sect2>
-
-<sect2 id="ssl-min-dh-prime-bits">
-<title>ssl_min_dh_prime_bits</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-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.
-</para>
-</sect2>
-
-<sect2 id="ssl-ca-certificates-file">
-<title>ssl_ca_certificates_file</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-</screen><para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this variable defaults to the example
-mentioned. This file is managed by the <quote>ca-certificates</quote> package.
-</para>
-</sect2>
-
-<sect2 id="pipe-split">
-<title>pipe_split</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Used in connection with the <literal><pipe-message></literal> function following
-<literal><tag-prefix></literal>. If this variable is <emphasis>unset</emphasis>, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated. When <emphasis>set</emphasis>, Mutt will pipe the messages one by one.
-In both cases the messages are piped in the current sorted order,
-and the <link linkend="pipe-sep">$pipe_sep</link> separator is added after each message.
-</para>
-</sect2>
-
-<sect2 id="pipe-decode">
-<title>pipe_decode</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Used in connection with the <literal><pipe-message></literal> command. When <emphasis>unset</emphasis>,
-Mutt will pipe the messages without any preprocessing. When <emphasis>set</emphasis>, Mutt
-will weed headers and will attempt to decode the messages
-first.
-</para>
-</sect2>
-
-<sect2 id="pipe-sep">
-<title>pipe_sep</title>
-<literallayout>Type: string
-Default: <quote><literal>\n</literal></quote></literallayout>
-
-<para>
-The separator to add between messages when piping a list of tagged
-messages to an external Unix command.
-</para>
-</sect2>
-
-<sect2 id="pop-authenticators">
-<title>pop_authenticators</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an POP server, in the order mutt should
-try them. Authentication methods are either <quote>user</quote>, <quote>apop</quote> or any
-SASL mechanism, eg <quote>digest-md5</quote>, <quote>gssapi</quote> or <quote>cram-md5</quote>.
-This option is case-insensitive. If this option is <emphasis>unset</emphasis>
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set pop_authenticators="digest-md5:apop:user"
-
-</screen></sect2>
-
-<sect2 id="pop-auth-try-all">
-<title>pop_auth_try_all</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will try all available authentication methods.
-When <emphasis>unset</emphasis>, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-</para>
-</sect2>
-
-<sect2 id="pop-checkinterval">
-<title>pop_checkinterval</title>
-<literallayout>Type: number
-Default: 60</literallayout>
-
-<para>
-This variable configures how often (in seconds) mutt should look for
-new mail in the currently selected mailbox if it is a POP mailbox.
-</para>
-</sect2>
-
-<sect2 id="pop-delete">
-<title>pop_delete</title>
-<literallayout>Type: quadoption
-Default: ask-no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, Mutt will delete successfully downloaded messages from the POP
-server when using the <literal><link linkend="fetch-mail"><fetch-mail></link></literal> function. When <emphasis>unset</emphasis>, Mutt will
-download messages but also leave them on the POP server.
-</para>
-</sect2>
-
-<sect2 id="pop-host">
-<title>pop_host</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-The name of your POP server for the <literal><link linkend="fetch-mail"><fetch-mail></link></literal> function. You
-can also specify an alternative port, username and password, ie:
-
-</para>
-
-<screen>
-[pop[s]://][username[:password]@]popserver[:port]
-
-</screen><para>
-where <quote>[...]</quote> denotes an optional part.
-</para>
-</sect2>
-
-<sect2 id="pop-last">
-<title>pop_last</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If this variable is <emphasis>set</emphasis>, mutt will try to use the <quote><literal>LAST</literal></quote> POP command
-for retrieving only unread messages from the POP server when using
-the <literal><link linkend="fetch-mail"><fetch-mail></link></literal> function.
-</para>
-</sect2>
-
-<sect2 id="pop-reconnect">
-<title>pop_reconnect</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-</para>
-</sect2>
-
-<sect2 id="pop-user">
-<title>pop_user</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Your login name on the POP server.
-</para>
-<para>
-This variable defaults to your user name on the local machine.
-</para>
-</sect2>
-
-<sect2 id="pop-pass">
-<title>pop_pass</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Specifies the password for your POP account. If <emphasis>unset</emphasis>, Mutt will
-prompt you for your password when you open a POP mailbox.
-</para>
-<para>
-<emphasis role="bold">Warning</emphasis>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc
-even if you are the only one who can read the file.
-</para>
-</sect2>
-
-<sect2 id="post-indent-string">
-<title>post_indent_string</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Similar to the <link linkend="attribution">$attribution</link> variable, Mutt will append this
-string after the inclusion of a message which is being replied to.
-</para>
-</sect2>
-
-<sect2 id="postpone">
-<title>postpone</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not messages are saved in the <link linkend="postponed">$postponed</link>
-mailbox when you elect not to send immediately.
-</para>
-<para>
-Also see the <link linkend="recall">$recall</link> variable.
-</para>
-</sect2>
-
-<sect2 id="postponed">
-<title>postponed</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/postponed</literal></quote></literallayout>
-
-<para>
-Mutt allows you to indefinitely <quote><link linkend="postpone">postpone</link> sending a message</quote> which
-you are editing. When you choose to postpone a message, Mutt saves it
-in the mailbox specified by this variable.
-</para>
-<para>
-Also see the <link linkend="postpone">$postpone</link> variable.
-</para>
-</sect2>
-
-<sect2 id="preconnect">
-<title>preconnect</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, a shell command to be executed if mutt fails to establish
-a connection to the server. This is useful for setting up secure
-connections, e.g. with <literal>ssh(1)</literal>. If the command returns a nonzero
-status, mutt gives up opening the server. Example:
-
-</para>
-
-<screen>
-set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
-sleep 20 < /dev/null > /dev/null"
-
-</screen><para>
-Mailbox <quote>foo</quote> on <quote>mailhost.net</quote> can now be reached
-as <quote>{localhost:1234}foo</quote>.
-</para>
-<para>
-Note: For this example to work, you must be able to log in to the
-remote machine without having to enter a password.
-</para>
-<para>
-When set, Mutt uses the tunnel for all remote connections.
-Please see <quote><link linkend="account-hook">account-hook</link></quote> in the manual for how to use different
-tunnel commands per connection.
-</para>
-</sect2>
-
-<sect2 id="print">
-<title>print</title>
-<literallayout>Type: quadoption
-Default: ask-no</literallayout>
-
-<para>
-Controls whether or not Mutt really prints messages.
-This is set to <quote>ask-no</quote> by default, because some people
-accidentally hit <quote>p</quote> often.
-</para>
-</sect2>
-
-<sect2 id="print-command">
-<title>print_command</title>
-<literallayout>Type: path
-Default: <quote><literal>lpr</literal></quote></literallayout>
-
-<para>
-This specifies the command pipe that should be used to print messages.
-</para>
-</sect2>
-
-<sect2 id="print-decode">
-<title>print_decode</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Used in connection with the <literal><print-message></literal> command. If this
-option is <emphasis>set</emphasis>, the message is decoded before it is passed to the
-external command specified by <link linkend="print-command">$print_command</link>. If this option
-is <emphasis>unset</emphasis>, 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.
-</para>
-</sect2>
-
-<sect2 id="print-split">
-<title>print_split</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Used in connection with the <literal><print-message></literal> command. If this option
-is <emphasis>set</emphasis>, the command specified by <link linkend="print-command">$print_command</link> is executed once for
-each message which is to be printed. If this option is <emphasis>unset</emphasis>,
-the command specified by <link linkend="print-command">$print_command</link> is executed only once, and
-all the messages are concatenated, with a form feed as the message
-separator.
-</para>
-<para>
-Those who use the <literal>enscript</literal>(1) program's mail-printing mode will
-most likely want to <emphasis>set</emphasis> this option.
-</para>
-</sect2>
-
-<sect2 id="prompt-after">
-<title>prompt_after</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If you use an <emphasis>external</emphasis> <link linkend="pager">$pager</link>, setting this variable will
-cause Mutt to prompt you for a command when the pager exits rather
-than returning to the index menu. If <emphasis>unset</emphasis>, Mutt will return to the
-index menu when the external pager exits.
-</para>
-</sect2>
-
-<sect2 id="query-command">
-<title>query_command</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This specifies the command that mutt will use to make external address
-queries. The string should contain a <quote>%s</quote>, which will be substituted
-with the query string the user types. See <quote><link linkend="query">query</link></quote> for more
-information.
-</para>
-</sect2>
-
-<sect2 id="query-format">
-<title>query_format</title>
-<literallayout>Type: string
-Default: <quote><literal>%4c %t %-25.25a %-25.25n %?e?(%e)?</literal></quote></literallayout>
-
-<para>
-This variable describes the format of the <quote>query</quote> menu. The
-following <literal>printf(3)</literal>-style sequences are understood:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%a </term>
-<listitem><para>destination address
-</para></listitem></varlistentry>
-<varlistentry><term>%c </term>
-<listitem><para>current entry number
-</para></listitem></varlistentry>
-<varlistentry><term>%e </term>
-<listitem><para>extra information *
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>destination name
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para><quote>*</quote> if current entry is tagged, a space otherwise
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For an explanation of <quote>soft-fill</quote>, see the <link linkend="index-format">$index_format</link> documentation.
-</para>
-<para>
-* = can be optionally printed if nonzero, see the <link linkend="status-format">$status_format</link> documentation.
-</para>
-</sect2>
-
-<sect2 id="quit">
-<title>quit</title>
-<literallayout>Type: quadoption
-Default: yes</literallayout>
-
-<para>
-This variable controls whether <quote>quit</quote> and <quote>exit</quote> actually quit
-from mutt. If this option is <emphasis>set</emphasis>, they do quit, if it is <emphasis>unset</emphasis>, they
-have no effect, and if it is set to <emphasis>ask-yes</emphasis> or <emphasis>ask-no</emphasis>, you are
-prompted for confirmation when you try to quit.
-</para>
-</sect2>
-
-<sect2 id="quote-regexp">
-<title>quote_regexp</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>ˆ([ \t]*[|>:}#])+</literal></quote></literallayout>
-
-<para>
-A regular expression used in the internal pager to determine quoted
-sections of text in the body of a message. Quoted text may be filtered
-out using the <literal><toggle-quoted></literal> command, or colored according to the
-<quote>color quoted</quote> family of directives.
-</para>
-<para>
-Higher levels of quoting may be colored differently (<quote>color quoted1</quote>,
-<quote>color quoted2</quote>, etc.). The quoting level is determined by removing
-the last character from the matched text and recursively reapplying
-the regular expression until it fails to produce a match.
-</para>
-<para>
-Match detection may be overridden by the <link linkend="smileys">$smileys</link> regular expression.
-</para>
-</sect2>
-
-<sect2 id="read-inc">
-<title>read_inc</title>
-<literallayout>Type: number
-Default: 10</literallayout>
-
-<para>
-If set to a value greater than 0, Mutt will display which message it
-is currently on when reading a mailbox or when performing search actions
-such as search and limit. The message is printed after
-this many messages have been read or searched (e.g., if set to 25, Mutt will
-print a message when it is at message 25, and then again when it gets
-to message 50). This variable is meant to indicate progress when
-reading or searching large mailboxes which may take some time.
-When set to 0, only a single message will appear before the reading
-the mailbox.
-</para>
-<para>
-Also see the <link linkend="write-inc">$write_inc</link>, <link linkend="net-inc">$net_inc</link> and <link linkend="time-inc">$time_inc</link> variables and the
-<quote><link linkend="tuning">tuning</link></quote> section of the manual for performance considerations.
-</para>
-</sect2>
-
-<sect2 id="read-only">
-<title>read_only</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, all folders are opened in read-only mode.
-</para>
-</sect2>
-
-<sect2 id="realname">
-<title>realname</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This variable specifies what <quote>real</quote> or <quote>personal</quote> name should be used
-when sending messages.
-</para>
-<para>
-By default, this is the GECOS field from <literal>/etc/passwd</literal>. Note that this
-variable will <emphasis>not</emphasis> be used when the user has set a real name
-in the <link linkend="from">$from</link> variable.
-</para>
-</sect2>
-
-<sect2 id="recall">
-<title>recall</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-Controls whether or not Mutt recalls postponed messages
-when composing a new message.
-</para>
-<para>
-<emphasis>Setting</emphasis> this variable to is not generally useful, and thus not
-recommended.
-</para>
-<para>
-Also see <link linkend="postponed">$postponed</link> variable.
-</para>
-</sect2>
-
-<sect2 id="record">
-<title>record</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/sent</literal></quote></literallayout>
-
-<para>
-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 <quote><link linkend="my-hdr">my_hdr</link></quote>
-command to create a <quote>Bcc:</quote> field with your email address in it.)
-</para>
-<para>
-The value of <emphasis><link linkend="record">$record</link></emphasis> is overridden by the <link linkend="force-name">$force_name</link> and
-<link linkend="save-name">$save_name</link> variables, and the <quote><link linkend="fcc-hook">fcc-hook</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="reply-regexp">
-<title>reply_regexp</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>ˆ(re([\[0-9\]+])*|aw):[ \t]*</literal></quote></literallayout>
-
-<para>
-A regular expression used to recognize reply messages when threading
-and replying. The default value corresponds to the English "Re:" and
-the German "Aw:".
-</para>
-</sect2>
-
-<sect2 id="reply-self">
-<title>reply_self</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>unset</emphasis> and you are replying to a message sent by you, Mutt will
-assume that you want to reply to the recipients of that message rather
-than to yourself.
-</para>
-<para>
-Also see the <quote><link linkend="alternates">alternates</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="reply-to">
-<title>reply_to</title>
-<literallayout>Type: quadoption
-Default: ask-yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, when replying to a message, Mutt will use the address listed
-in the Reply-to: header as the recipient of the reply. If <emphasis>unset</emphasis>,
-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.
-</para>
-</sect2>
-
-<sect2 id="resolve">
-<title>resolve</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the cursor will be automatically advanced to the next
-(possibly undeleted) message whenever a command that modifies the
-current message is executed.
-</para>
-</sect2>
-
-<sect2 id="reverse-alias">
-<title>reverse_alias</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable controls whether or not Mutt will display the <quote>personal</quote>
-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:
-
-</para>
-
-<screen>
-alias juser abd30425@somewhere.net (Joe User)
-
-</screen><para>
-and then you receive mail which contains the following header:
-
-</para>
-
-<screen>
-From: abd30425@somewhere.net
-
-</screen><para>
-It would be displayed in the index menu as <quote>Joe User</quote> instead of
-<quote>abd30425@somewhere.net.</quote> This is useful when the person's e-mail
-address is not human friendly.
-</para>
-</sect2>
-
-<sect2 id="reverse-name">
-<title>reverse_name</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-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 <emphasis>set</emphasis>, the default <emphasis>From:</emphasis> line of
-the reply messages is built using the address where you received the
-messages you are replying to <emphasis role="bold">if</emphasis> that address matches your
-<quote><link linkend="alternates">alternates</link></quote>. If the variable is <emphasis>unset</emphasis>, or the address that would be
-used doesn't match your <quote><link linkend="alternates">alternates</link></quote>, the <emphasis>From:</emphasis> line will use
-your address on the current machine.
-</para>
-<para>
-Also see the <quote><link linkend="alternates">alternates</link></quote> command.
-</para>
-</sect2>
-
-<sect2 id="reverse-realname">
-<title>reverse_realname</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable fine-tunes the behaviour of the <link linkend="reverse-name">$reverse_name</link> feature.
-When it is <emphasis>set</emphasis>, mutt will use the address from incoming messages as-is,
-possibly including eventual real names. When it is <emphasis>unset</emphasis>, mutt will
-override any such real names with the setting of the <link linkend="realname">$realname</link> variable.
-</para>
-</sect2>
-
-<sect2 id="rfc2047-parameters">
-<title>rfc2047_parameters</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When this variable is <emphasis>set</emphasis>, Mutt will decode RFC2047-encoded MIME
-parameters. You want to set this variable when mutt suggests you
-to save attachments to files named like:
-
-</para>
-
-<screen>
-=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-</screen><para>
-When this variable is <emphasis>set</emphasis> interactively, the change won't be
-active until you change folders.
-</para>
-<para>
-Note that this use of RFC2047's encoding is explicitly
-prohibited by the standard, but nevertheless encountered in the
-wild.
-</para>
-<para>
-Also note that setting this parameter will <emphasis>not</emphasis> have the effect
-that mutt <emphasis>generates</emphasis> this kind of encoding. Instead, mutt will
-unconditionally use the encoding specified in RFC2231.
-</para>
-</sect2>
-
-<sect2 id="save-address">
-<title>save_address</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If <link linkend="save-name">$save_name</link> or <link linkend="force-name">$force_name</link>
-is <emphasis>set</emphasis> too, the selection of the Fcc folder will be changed as well.
-</para>
-</sect2>
-
-<sect2 id="save-empty">
-<title>save_empty</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, mailboxes which contain no saved messages will be removed
-when closed (the exception is <link linkend="spoolfile">$spoolfile</link> which is never removed).
-If <emphasis>set</emphasis>, mailboxes are never removed.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> This only applies to mbox and MMDF folders, Mutt does not
-delete MH and Maildir directories.
-</para>
-</sect2>
-
-<sect2 id="save-history">
-<title>save_history</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-This variable controls the size of the history (per category) saved in the
-<link linkend="history-file">$history_file</link> file.
-</para>
-</sect2>
-
-<sect2 id="save-name">
-<title>save_name</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-This variable controls how copies of outgoing messages are saved.
-When <emphasis>set</emphasis>, 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 <link linkend="folder">$folder</link> directory with the <emphasis>username</emphasis> 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
-<link linkend="record">$record</link> mailbox.
-</para>
-<para>
-Also see the <link linkend="force-name">$force_name</link> variable.
-</para>
-</sect2>
-
-<sect2 id="score">
-<title>score</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When this variable is <emphasis>unset</emphasis>, scoring is turned off. This can
-be useful to selectively disable scoring for certain folders when the
-<link linkend="score-threshold-delete">$score_threshold_delete</link> variable and related are used.
-</para>
-</sect2>
-
-<sect2 id="score-threshold-delete">
-<title>score_threshold_delete</title>
-<literallayout>Type: number
-Default: -1</literallayout>
-
-<para>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked for deletion by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message for deletion.
-</para>
-</sect2>
-
-<sect2 id="score-threshold-flag">
-<title>score_threshold_flag</title>
-<literallayout>Type: number
-Default: 9999</literallayout>
-
-<para>
-Messages which have been assigned a score greater than or equal to this
-variable's value are automatically marked "flagged".
-</para>
-</sect2>
-
-<sect2 id="score-threshold-read">
-<title>score_threshold_read</title>
-<literallayout>Type: number
-Default: -1</literallayout>
-
-<para>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked as read by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message read.
-</para>
-</sect2>
-
-<sect2 id="send-charset">
-<title>send_charset</title>
-<literallayout>Type: string
-Default: <quote><literal>us-ascii:iso-8859-1:utf-8</literal></quote></literallayout>
-
-<para>
-A colon-delimited list of character sets for outgoing messages. Mutt will use the
-first character set into which the text can be converted exactly.
-If your <link linkend="charset">$charset</link> is not <quote>iso-8859-1</quote> and recipients may not
-understand <quote>UTF-8</quote>, it is advisable to include in the list an
-appropriate widely used standard character set (such as
-<quote>iso-8859-2</quote>, <quote>koi8-r</quote> or <quote>iso-2022-jp</quote>) either instead of or after
-<quote>iso-8859-1</quote>.
-</para>
-<para>
-In case the text cannot be converted into one of these exactly,
-mutt uses <link linkend="charset">$charset</link> as a fallback.
-</para>
-</sect2>
-
-<sect2 id="sendmail">
-<title>sendmail</title>
-<literallayout>Type: path
-Default: <quote><literal>/usr/sbin/sendmail -oem -oi</literal></quote></literallayout>
-
-<para>
-Specifies the program and arguments used to deliver mail sent by Mutt.
-Mutt expects that the specified program interprets additional
-arguments as recipient addresses.
-</para>
-</sect2>
-
-<sect2 id="sendmail-wait">
-<title>sendmail_wait</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-Specifies the number of seconds to wait for the <link linkend="sendmail">$sendmail</link> process
-to finish before giving up and putting delivery in the background.
-</para>
-<para>
-Mutt interprets the value of this variable as follows:
-
-</para>
-
-<variablelist>
-<varlistentry><term>>0 </term>
-<listitem><para>number of seconds to wait for sendmail to finish before continuing
-</para></listitem></varlistentry>
-<varlistentry><term>0 </term>
-<listitem><para>wait forever for sendmail to finish
-</para></listitem></varlistentry>
-<varlistentry><term><0 </term>
-<listitem><para>always put sendmail in the background without waiting
-</para></listitem></varlistentry></variablelist>
-
-<para>
-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.
-</para>
-</sect2>
-
-<sect2 id="shell">
-<title>shell</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Command to use when spawning a subshell. By default, the user's login
-shell from <literal>/etc/passwd</literal> is used.
-</para>
-</sect2>
-
-<sect2 id="sig-dashes">
-<title>sig_dashes</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, a line containing <quote>-- </quote> (note the trailing space) will be inserted before your
-<link linkend="signature">$signature</link>. It is <emphasis role="bold">strongly</emphasis> recommended that you not <emphasis>unset</emphasis>
-this variable unless your signature contains just your name. The
-reason for this is because many software packages use <quote>-- \n</quote> to
-detect your signature. For example, Mutt has the ability to highlight
-the signature in a different color in the builtin pager.
-</para>
-</sect2>
-
-<sect2 id="sig-on-top">
-<title>sig_on_top</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, the signature will be included before any quoted or forwarded
-text. It is <emphasis role="bold">strongly</emphasis> 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.
-</para>
-</sect2>
-
-<sect2 id="signature">
-<title>signature</title>
-<literallayout>Type: path
-Default: <quote><literal>˜/.signature</literal></quote></literallayout>
-
-<para>
-Specifies the filename of your signature, which is appended to all
-outgoing messages. If the filename ends with a pipe (<quote>|</quote>), it is
-assumed that filename is a shell command and input should be read from
-its standard output.
-</para>
-</sect2>
-
-<sect2 id="simple-search">
-<title>simple_search</title>
-<literallayout>Type: string
-Default: <quote><literal>˜f %s | ˜s %s</literal></quote></literallayout>
-
-<para>
-Specifies how Mutt should expand a simple search into a real search
-pattern. A simple search is one that does not contain any of the <quote>˜</quote> pattern
-operators. See <quote><link linkend="patterns">patterns</link></quote> for more information on search patterns.
-</para>
-<para>
-For example, if you simply type <quote>joe</quote> at a search or limit prompt, Mutt
-will automatically expand it to the value specified by this variable by
-replacing <quote>%s</quote> with the supplied string.
-For the default value, <quote>joe</quote> would be expanded to: <quote>˜f joe | ˜s joe</quote>.
-</para>
-</sect2>
-
-<sect2 id="smart-wrap">
-<title>smart_wrap</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls the display of lines longer than the screen width in the
-internal pager. If <emphasis>set</emphasis>, long lines are wrapped at a word boundary. If
-<emphasis>unset</emphasis>, lines are simply wrapped at the screen edge. Also see the
-<link linkend="markers">$markers</link> variable.
-</para>
-</sect2>
-
-<sect2 id="smileys">
-<title>smileys</title>
-<literallayout>Type: regular expression
-Default: <quote><literal>(>From )|(:[-ˆ]?[][)(><}{|/DP])</literal></quote></literallayout>
-
-<para>
-The <emphasis>pager</emphasis> uses this variable to catch some common false
-positives of <link linkend="quote-regexp">$quote_regexp</link>, most notably smileys and not consider
-a line quoted text if it also matches <link linkend="smileys">$smileys</link>. This mostly
-happens at the beginning of a line.
-</para>
-</sect2>
-
-<sect2 id="sleep-time">
-<title>sleep_time</title>
-<literallayout>Type: number
-Default: 1</literallayout>
-
-<para>
-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.
-</para>
-</sect2>
-
-<sect2 id="smtp-authenticators">
-<title>smtp_authenticators</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an SMTP server, in the order mutt should
-try them. Authentication methods are any SASL mechanism, eg
-<quote>digest-md5</quote>, <quote>gssapi</quote> or <quote>cram-md5</quote>.
-This option is case-insensitive. If it is <quote>unset</quote>
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</para>
-<para>
-Example:
-
-</para>
-
-<screen>
-set smtp_authenticators="digest-md5:cram-md5"
-
-</screen></sect2>
-
-<sect2 id="smtp-pass">
-<title>smtp_pass</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Specifies the password for your SMTP account. If <emphasis>unset</emphasis>, Mutt will
-prompt you for your password when you first send mail via SMTP.
-See <link linkend="smtp-url">$smtp_url</link> to configure mutt to send mail via SMTP.
-</para>
-<para>
-<emphasis role="bold">Warning</emphasis>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</para>
-</sect2>
-
-<sect2 id="smtp-url">
-<title>smtp_url</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Defines the SMTP smarthost where sent messages should relayed for
-delivery. This should take the form of an SMTP URL, eg:
-
-</para>
-
-<screen>
-smtp[s]://[user[:pass]@]host[:port]/
-
-</screen><para>
-\.\.\. where <quote>[...]</quote> denotes an optional part.
-Setting this variable overrides the value of the <link linkend="sendmail">$sendmail</link>
-variable.
-</para>
-</sect2>
-
-<sect2 id="sort">
-<title>sort</title>
-<literallayout>Type: sort order
-Default: date</literallayout>
-
-<para>
-Specifies how to sort messages in the <quote>index</quote> menu. Valid values
-are:
-
-</para>
-
-<itemizedlist>
-<listitem><para>date or date-sent
-</para></listitem><listitem><para>date-received
-</para></listitem><listitem><para>from
-</para></listitem><listitem><para>mailbox-order (unsorted)
-</para></listitem><listitem><para>score
-</para></listitem><listitem><para>size
-</para></listitem><listitem><para>spam
-</para></listitem><listitem><para>subject
-</para></listitem><listitem><para>threads
-</para></listitem><listitem><para>to
-</para></listitem></itemizedlist>
-
-<para>
-You may optionally use the <quote>reverse-</quote> prefix to specify reverse sorting
-order (example: <quote><literal>set sort=reverse-date-sent</literal></quote>).
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, this option is set by default to
-<quote>threads</quote> in /etc/Muttrc.
-</para>
-</sect2>
-
-<sect2 id="sort-alias">
-<title>sort_alias</title>
-<literallayout>Type: sort order
-Default: alias</literallayout>
-
-<para>
-Specifies how the entries in the <quote>alias</quote> menu are sorted. The
-following are legal values:
-
-</para>
-
-<itemizedlist>
-<listitem><para>address (sort alphabetically by email address)
-</para></listitem><listitem><para>alias (sort alphabetically by alias name)
-</para></listitem><listitem><para>unsorted (leave in order specified in .muttrc)
-</para></listitem></itemizedlist>
-</sect2>
-
-<sect2 id="sort-aux">
-<title>sort_aux</title>
-<literallayout>Type: sort order
-Default: date</literallayout>
-
-<para>
-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 <link linkend="sort">$sort</link> can, except
-<quote>threads</quote> (in that case, mutt will just use <quote>date-sent</quote>). You can also
-specify the <quote>last-</quote> prefix in addition to the <quote>reverse-</quote> prefix, but <quote>last-</quote>
-must come after <quote>reverse-</quote>. The <quote>last-</quote> prefix causes messages to be
-sorted against its siblings by which has the last descendant, using
-the rest of <link linkend="sort-aux">$sort_aux</link> as an ordering. For instance,
-
-</para>
-
-<screen>
-set sort_aux=last-date-received
-
-</screen><para>
-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 <quote><literal>set sort=reverse-threads</literal></quote>.)
-</para>
-<para>
-Note: For reversed <link linkend="sort">$sort</link>
-order <link linkend="sort-aux">$sort_aux</link> is reversed again (which is not the right thing to do,
-but kept to not break any existing configuration setting).
-</para>
-</sect2>
-
-<sect2 id="sort-browser">
-<title>sort_browser</title>
-<literallayout>Type: sort order
-Default: alpha</literallayout>
-
-<para>
-Specifies how to sort entries in the file browser. By default, the
-entries are sorted alphabetically. Valid values:
-
-</para>
-
-<itemizedlist>
-<listitem><para>alpha (alphabetically)
-</para></listitem><listitem><para>date
-</para></listitem><listitem><para>size
-</para></listitem><listitem><para>unsorted
-</para></listitem></itemizedlist>
-
-<para>
-You may optionally use the <quote>reverse-</quote> prefix to specify reverse sorting
-order (example: <quote><literal>set sort_browser=reverse-date</literal></quote>).
-</para>
-</sect2>
-
-<sect2 id="sort-re">
-<title>sort_re</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-This variable is only useful when sorting by threads with
-<link linkend="strict-threads">$strict_threads</link> <emphasis>unset</emphasis>. In that case, it changes the heuristic
-mutt uses to thread messages by subject. With <link linkend="sort-re">$sort_re</link> <emphasis>set</emphasis>, mutt 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 <link linkend="reply-regexp">$reply_regexp</link>. With <link linkend="sort-re">$sort_re</link> <emphasis>unset</emphasis>, mutt will attach
-the message whether or not this is the case, as long as the
-non-<link linkend="reply-regexp">$reply_regexp</link> parts of both messages are identical.
-</para>
-</sect2>
-
-<sect2 id="spam-separator">
-<title>spam_separator</title>
-<literallayout>Type: string
-Default: <quote><literal>,</literal></quote></literallayout>
-
-<para>
-This variable controls what happens when multiple spam headers
-are matched: if <emphasis>unset</emphasis>, each successive header will overwrite any
-previous matches value for the spam label. If <emphasis>set</emphasis>, each successive
-match will append to the previous, using this variable's value as a
-separator.
-</para>
-</sect2>
-
-<sect2 id="spoolfile">
-<title>spoolfile</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-If your spool mailbox is in a non-default place where Mutt cannot find
-it, you can specify its location with this variable. Mutt will
-automatically set this variable to the value of the environment
-variable <literal>$MAIL</literal> if it is not set.
-</para>
-</sect2>
-
-<sect2 id="status-chars">
-<title>status_chars</title>
-<literallayout>Type: string
-Default: <quote><literal>-*%A</literal></quote></literallayout>
-
-<para>
-Controls the characters used by the <quote>%r</quote> indicator in
-<link linkend="status-format">$status_format</link>. 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 <literal><toggle-write></literal> operation, bound by default to <quote>%</quote>). 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).
-</para>
-</sect2>
-
-<sect2 id="status-format">
-<title>status_format</title>
-<literallayout>Type: string
-Default: <quote><literal>-%r-Mutt: %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)---</literal></quote></literallayout>
-
-<para>
-Controls the format of the status line displayed in the <quote>index</quote>
-menu. This string is similar to <link linkend="index-format">$index_format</link>, but has its own
-set of <literal>printf(3)</literal>-like sequences:
-
-</para>
-
-<variablelist>
-<varlistentry><term>%b </term>
-<listitem><para>number of mailboxes with new mail *
-</para></listitem></varlistentry>
-<varlistentry><term>%d </term>
-<listitem><para>number of deleted messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%f </term>
-<listitem><para>the full pathname of the current mailbox
-</para></listitem></varlistentry>
-<varlistentry><term>%F </term>
-<listitem><para>number of flagged messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%h </term>
-<listitem><para>local hostname
-</para></listitem></varlistentry>
-<varlistentry><term>%l </term>
-<listitem><para>size (in bytes) of the current mailbox *
-</para></listitem></varlistentry>
-<varlistentry><term>%L </term>
-<listitem><para>size (in bytes) of the messages shown
-(i.e., which match the current limit) *
-</para></listitem></varlistentry>
-<varlistentry><term>%m </term>
-<listitem><para>the number of messages in the mailbox *
-</para></listitem></varlistentry>
-<varlistentry><term>%M </term>
-<listitem><para>the number of messages shown (i.e., which match the current limit) *
-</para></listitem></varlistentry>
-<varlistentry><term>%n </term>
-<listitem><para>number of new messages in the mailbox *
-</para></listitem></varlistentry>
-<varlistentry><term>%o </term>
-<listitem><para>number of old unread messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%p </term>
-<listitem><para>number of postponed messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%P </term>
-<listitem><para>percentage of the way through the index
-</para></listitem></varlistentry>
-<varlistentry><term>%r </term>
-<listitem><para>modified/read-only/won't-write/attach-message indicator,
-according to <link linkend="status-chars">$status_chars</link>
-</para></listitem></varlistentry>
-<varlistentry><term>%s </term>
-<listitem><para>current sorting mode (<link linkend="sort">$sort</link>)
-</para></listitem></varlistentry>
-<varlistentry><term>%S </term>
-<listitem><para>current aux sorting method (<link linkend="sort-aux">$sort_aux</link>)
-</para></listitem></varlistentry>
-<varlistentry><term>%t </term>
-<listitem><para>number of tagged messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%u </term>
-<listitem><para>number of unread messages *
-</para></listitem></varlistentry>
-<varlistentry><term>%v </term>
-<listitem><para>Mutt version string
-</para></listitem></varlistentry>
-<varlistentry><term>%V </term>
-<listitem><para>currently active limit pattern, if any *
-</para></listitem></varlistentry>
-<varlistentry><term>%>X </term>
-<listitem><para>right justify the rest of the string and pad with <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%|X </term>
-<listitem><para>pad to the end of the line with <quote>X</quote>
-</para></listitem></varlistentry>
-<varlistentry><term>%*X </term>
-<listitem><para>soft-fill with character <quote>X</quote> as pad
-</para></listitem></varlistentry></variablelist>
-
-<para>
-For an explanation of <quote>soft-fill</quote>, see the <link linkend="index-format">$index_format</link> documentation.
-</para>
-<para>
-* = can be optionally printed if nonzero
-</para>
-<para>
-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:
-</para>
-<para>
-<literal>%?<sequence_char>?<optional_string>?</literal>
-</para>
-<para>
-where <emphasis>sequence_char</emphasis> is a character from the table above, and
-<emphasis>optional_string</emphasis> is the string you would like printed if
-<emphasis>sequence_char</emphasis> is nonzero. <emphasis>optional_string</emphasis> <emphasis role="bold">may</emphasis> contain
-other sequences as well as normal text, but you may <emphasis role="bold">not</emphasis> nest
-optional strings.
-</para>
-<para>
-Here is an example illustrating how to optionally print the number of
-new messages in a mailbox:
-</para>
-<para>
-<literal>%?n?%n new messages.?</literal>
-</para>
-<para>
-You can also switch between two strings using the following construct:
-</para>
-<para>
-<literal>%?<sequence_char>?<if_string>&<else_string>?</literal>
-</para>
-<para>
-If the value of <emphasis>sequence_char</emphasis> is non-zero, <emphasis>if_string</emphasis> will
-be expanded, otherwise <emphasis>else_string</emphasis> will be expanded.
-</para>
-<para>
-You can force the result of any <literal>printf(3)</literal>-like sequence to be lowercase
-by prefixing the sequence character with an underscore (<quote>_</quote>) sign.
-For example, if you want to display the local hostname in lowercase,
-you would use: <quote><literal>%_h</literal></quote>.
-</para>
-<para>
-If you prefix the sequence character with a colon (<quote>:</quote>) character, mutt
-will replace any dots in the expansion by underscores. This might be helpful
-with IMAP folders that don't like dots in folder names.
-</para>
-</sect2>
-
-<sect2 id="status-on-top">
-<title>status_on_top</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Setting this variable causes the <quote>status bar</quote> to be displayed on
-the first line of the screen rather than near the bottom. If <link linkend="help">$help</link>
-is <emphasis>set</emphasis>, too it'll be placed at the bottom.
-</para>
-</sect2>
-
-<sect2 id="strict-threads">
-<title>strict_threads</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-If <emphasis>set</emphasis>, threading will only make use of the <quote>In-Reply-To</quote> and
-<quote>References:</quote> fields when you <link linkend="sort">$sort</link> by message threads. By
-default, messages with the same subject are grouped together in
-<quote>pseudo threads.</quote>. This may not always be desirable, such as in a
-personal mailbox where you might have several unrelated messages with
-the subjects like <quote>hi</quote> which will get grouped together. See also
-<link linkend="sort-re">$sort_re</link> for a less drastic way of controlling this
-behaviour.
-</para>
-</sect2>
-
-<sect2 id="suspend">
-<title>suspend</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>unset</emphasis>, mutt won't stop when the user presses the terminal's
-<emphasis>susp</emphasis> key, usually <quote>ˆZ</quote>. This is useful if you run mutt
-inside an xterm using a command like <quote><literal>xterm -e mutt</literal></quote>.
-</para>
-</sect2>
-
-<sect2 id="text-flowed">
-<title>text_flowed</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will generate <quote>format=flowed</quote> bodies with a content type
-of <quote><literal>text/plain; format=flowed</literal></quote>.
-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.
-</para>
-<para>
-Note that <link linkend="indent-string">$indent_string</link> is ignored when this option is <emphasis>set</emphasis>.
-</para>
-</sect2>
-
-<sect2 id="thread-received">
-<title>thread_received</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt uses the date received rather than the date sent
-to thread messages by subject.
-</para>
-</sect2>
-
-<sect2 id="thorough-search">
-<title>thorough_search</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Affects the <literal>˜b</literal> and <literal>˜h</literal> search operations described in
-section <quote><link linkend="patterns">patterns</link></quote>. If <emphasis>set</emphasis>, the headers and body/attachments of
-messages to be searched are decoded before searching. If <emphasis>unset</emphasis>,
-messages are searched as they appear in the folder.
-</para>
-<para>
-Users searching attachments or for non-ASCII characters should <emphasis>set</emphasis>
-this value because decoding also includes MIME parsing/decoding and possible
-character set conversions. Otherwise mutt will attempt to match against the
-raw message received (for example quoted-printable encoded or with encoded
-headers) which may lead to incorrect search results.
-</para>
-</sect2>
-
-<sect2 id="tilde">
-<title>tilde</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, the internal-pager will pad blank lines to the bottom of the
-screen with a tilde (<quote>˜</quote>).
-</para>
-</sect2>
-
-<sect2 id="time-inc">
-<title>time_inc</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-Along with <link linkend="read-inc">$read_inc</link>, <link linkend="write-inc">$write_inc</link>, and <link linkend="net-inc">$net_inc</link>, this
-variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than <link linkend="time-inc">$time_inc</link> milliseconds
-apart. This can improve throughput on systems with slow terminals,
-or when running mutt on a remote system.
-</para>
-<para>
-Also see the <quote><link linkend="tuning">tuning</link></quote> section of the manual for performance considerations.
-</para>
-</sect2>
-
-<sect2 id="timeout">
-<title>timeout</title>
-<literallayout>Type: number
-Default: 600</literallayout>
-
-<para>
-When Mutt is waiting for user input either idleing in menus or
-in an interactive prompt, Mutt would block until input is
-present. Depending on the context, this would prevent certain
-operations from working, like checking for new mail or keeping
-an IMAP connection alive.
-</para>
-<para>
-This variable controls how many seconds Mutt will at most wait
-until it aborts waiting for input, performs these operations and
-continues to wait for input.
-</para>
-<para>
-A value of zero or less will cause Mutt to never time out.
-</para>
-</sect2>
-
-<sect2 id="tmpdir">
-<title>tmpdir</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-This variable allows you to specify where Mutt will place its
-temporary files needed for displaying and composing messages. If
-this variable is not set, the environment variable <literal>$TMPDIR</literal> is
-used. If <literal>$TMPDIR</literal> is not set then <quote><literal>/tmp</literal></quote> is used.
-</para>
-</sect2>
-
-<sect2 id="to-chars">
-<title>to_chars</title>
-<literallayout>Type: string
-Default: <quote><literal> +TCFL</literal></quote></literallayout>
-
-<para>
-Controls the character used to indicate mail addressed to you. The
-first character is the one used when the mail is <emphasis>not</emphasis> addressed to your
-address. The second is used when you are the only
-recipient of the message. The third is when your address
-appears in the <quote>To:</quote> header field, but you are not the only recipient of
-the message. The fourth character is used when your
-address is specified in the <quote>Cc:</quote> header field, but you are not the only
-recipient. The fifth character is used to indicate mail that was sent
-by <emphasis>you</emphasis>. The sixth character is used to indicate when a mail
-was sent to a mailing-list you subscribe to.
-</para>
-</sect2>
-
-<sect2 id="trash">
-<title>trash</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-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.
-</para>
-<para>
-NOTE: When you delete a message in the trash folder, it is really
-deleted, so that you have a way to clean the trash.
-</para>
-</sect2>
-
-<sect2 id="tunnel">
-<title>tunnel</title>
-<literallayout>Type: string
-Default: (empty)</literallayout>
-
-<para>
-Setting this variable will cause mutt 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/SMTP server. Example:
-
-</para>
-
-<screen>
-set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-
-</screen><para>
-Note: For this example to work you must be able to log in to the remote
-machine without having to enter a password.
-</para>
-</sect2>
-
-<sect2 id="use-8bitmime">
-<title>use_8bitmime</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-<emphasis role="bold">Warning:</emphasis> do not set this variable unless you are using a version
-of sendmail which supports the <literal>-B8BITMIME</literal> flag (such as sendmail
-8.8.x) or you may not be able to send mail.
-</para>
-<para>
-When <emphasis>set</emphasis>, Mutt will invoke <link linkend="sendmail">$sendmail</link> with the <literal>-B8BITMIME</literal>
-flag when sending 8-bit messages to enable ESMTP negotiation.
-</para>
-</sect2>
-
-<sect2 id="use-domain">
-<title>use_domain</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will qualify all local addresses (ones without the
-<quote>@host</quote> portion) with the value of <link linkend="hostname">$hostname</link>. If <emphasis>unset</emphasis>, no
-addresses will be qualified.
-</para>
-</sect2>
-
-<sect2 id="use-envelope-from">
-<title>use_envelope_from</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will set the <emphasis>envelope</emphasis> sender of the message.
-If <link linkend="envelope-from-address">$envelope_from_address</link> is <emphasis>set</emphasis>, it will be used as the sender
-address. If <emphasis>unset</emphasis>, mutt will attempt to derive the sender from the
-<quote>From:</quote> header.
-</para>
-<para>
-Note that this information is passed to sendmail command using the
-<literal>-f</literal> command line switch. Therefore setting this option is not useful
-if the <link linkend="sendmail">$sendmail</link> variable already contains <literal>-f</literal> or if the
-executable pointed to by <link linkend="sendmail">$sendmail</link> doesn't support the <literal>-f</literal> switch.
-</para>
-</sect2>
-
-<sect2 id="use-from">
-<title>use_from</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will generate the <quote>From:</quote> header field when
-sending messages. If <emphasis>unset</emphasis>, no <quote>From:</quote> header field will be
-generated unless the user explicitly sets one using the <quote><link linkend="my-hdr">my_hdr</link></quote>
-command.
-</para>
-</sect2>
-
-<sect2 id="use-idn">
-<title>use_idn</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will show you international domain names decoded.
-Note: You can use IDNs for addresses even if this is <emphasis>unset</emphasis>.
-This variable only affects decoding.
-</para>
-</sect2>
-
-<sect2 id="use-ipv6">
-<title>use_ipv6</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, Mutt will look for IPv6 addresses of hosts it tries to
-contact. If this option is <emphasis>unset</emphasis>, Mutt will restrict itself to IPv4 addresses.
-Normally, the default should work.
-</para>
-</sect2>
-
-<sect2 id="user-agent">
-<title>user_agent</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will add a <quote>User-Agent:</quote> header to outgoing
-messages, indicating which version of mutt was used for composing
-them.
-</para>
-</sect2>
-
-<sect2 id="visual">
-<title>visual</title>
-<literallayout>Type: path
-Default: (empty)</literallayout>
-
-<para>
-Specifies the visual editor to invoke when the <quote><literal>˜v</literal></quote> command is
-given in the builtin editor.
-</para>
-</sect2>
-
-<sect2 id="wait-key">
-<title>wait_key</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether Mutt will ask you to press a key after an external command
-has been invoked by these functions: <literal><shell-escape></literal>,
-<literal><pipe-message></literal>, <literal><pipe-entry></literal>, <literal><print-message></literal>,
-and <literal><print-entry></literal> commands.
-</para>
-<para>
-It is also used when viewing attachments with <quote><link linkend="auto-view">auto_view</link></quote>, provided
-that the corresponding mailcap entry has a <emphasis>needsterminal</emphasis> flag,
-and the external program is interactive.
-</para>
-<para>
-When <emphasis>set</emphasis>, Mutt will always ask for a key. When <emphasis>unset</emphasis>, Mutt will wait
-for a key only if the external command returned a non-zero status.
-</para>
-</sect2>
-
-<sect2 id="weed">
-<title>weed</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-When <emphasis>set</emphasis>, mutt will weed headers when displaying, forwarding,
-printing, or replying to messages.
-</para>
-</sect2>
-
-<sect2 id="wrap">
-<title>wrap</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-When set to a positive value, mutt will wrap text at <link linkend="wrap">$wrap</link> characters.
-When set to a negative value, mutt will wrap text so that there are <link linkend="wrap">$wrap</link>
-characters of empty space on the right side of the terminal.
-</para>
-</sect2>
-
-<sect2 id="wrap-search">
-<title>wrap_search</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether searches wrap around the end.
-</para>
-<para>
-When <emphasis>set</emphasis>, searches will wrap around the first (or last) item. When
-<emphasis>unset</emphasis>, incremental searches will not wrap.
-</para>
-</sect2>
-
-<sect2 id="wrapmargin">
-<title>wrapmargin</title>
-<literallayout>Type: number
-Default: 0</literallayout>
-
-<para>
-(DEPRECATED) Equivalent to setting <link linkend="wrap">$wrap</link> with a negative value.
-</para>
-</sect2>
-
-<sect2 id="write-inc">
-<title>write_inc</title>
-<literallayout>Type: number
-Default: 10</literallayout>
-
-<para>
-When writing a mailbox, a message will be printed every
-<link linkend="write-inc">$write_inc</link> messages to indicate progress. If set to 0, only a
-single message will be displayed before writing a mailbox.
-</para>
-<para>
-Also see the <link linkend="read-inc">$read_inc</link>, <link linkend="net-inc">$net_inc</link> and <link linkend="time-inc">$time_inc</link> variables and the
-<quote><link linkend="tuning">tuning</link></quote> section of the manual for performance considerations.
-</para>
-</sect2>
-
-<sect2 id="write-bcc">
-<title>write_bcc</title>
-<literallayout>Type: boolean
-Default: yes</literallayout>
-
-<para>
-Controls whether mutt writes out the <quote>Bcc:</quote> header when preparing
-messages to be sent. Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see <link linkend="smtp-url">$smtp_url</link>), this
-option does nothing: mutt will never write out the <quote>Bcc:</quote> header
-in this case.
-</para>
-<para>
-<emphasis role="bold">Note:</emphasis> On Debian systems, exim4 and postfix strip BCC headers by
-default. The above warning applies to exim3 users, see /etc/Muttrc.
-</para>
-</sect2>
-
-<sect2 id="xterm-icon">
-<title>xterm_icon</title>
-<literallayout>Type: string
-Default: <quote><literal>M%?n?AIL&ail?</literal></quote></literallayout>
-
-<para>
-Controls the format of the icon title, as long as xterm_set_titles
-is enabled. This string is identical in formatting to the one used by
-<quote><link linkend="status-format">$status_format</link></quote>.
-</para>
-</sect2>
-
-<sect2 id="xterm-set-titles">
-<title>xterm_set_titles</title>
-<literallayout>Type: boolean
-Default: no</literallayout>
-
-<para>
-Controls whether mutt sets the xterm title bar and icon name
-(as long as you are in an appropriate terminal).
-</para>
-</sect2>
-
-<sect2 id="xterm-title">
-<title>xterm_title</title>
-<literallayout>Type: string
-Default: <quote><literal>Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?</literal></quote></literallayout>
-
-<para>
-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 <quote><link linkend="status-format">$status_format</link></quote>.
-</para>
-</sect2>
-
-</sect1>
-
-<sect1 id="functions">
-<title>Functions</title>
-
-<para>
-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 <link linkend="bind">bind</link>
-command.
-</para>
-
-<sect2 id="generic_map">
-<title>generic menu</title>
-<para>
-The <emphasis>generic</emphasis> menu is not a real menu, but specifies common functions
-(such as movement) available in all menus except for <emphasis>pager</emphasis> and
-<emphasis>editor</emphasis>. Changing settings for this menu will affect the default
-bindings for all menus (except as noted).
-</para>
-
-
-<table id="generic_table">
-<title>Default generic function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><top-page></literal></entry><entry>H</entry><entry>move to the top of the page</entry></row>
-<row><entry><literal><next-entry></literal></entry><entry>j</entry><entry>move to the next entry</entry></row>
-<row><entry><literal><previous-entry></literal></entry><entry>k</entry><entry>move to the previous entry</entry></row>
-<row><entry><literal><bottom-page></literal></entry><entry>L</entry><entry>move to the bottom of the page</entry></row>
-<row><entry><literal><refresh></literal></entry><entry>^L</entry><entry>clear and redraw the screen</entry></row>
-<row><entry><literal><middle-page></literal></entry><entry>M</entry><entry>move to the middle of the page</entry></row>
-<row><entry><literal><search-next></literal></entry><entry>n</entry><entry>search for next match</entry></row>
-<row><entry><literal><exit></literal></entry><entry>q</entry><entry>exit this menu</entry></row>
-<row><entry><literal><tag-entry></literal></entry><entry>t</entry><entry>tag the current entry</entry></row>
-<row><entry><literal><next-page></literal></entry><entry>z</entry><entry>move to the next page</entry></row>
-<row><entry><literal><previous-page></literal></entry><entry>Z</entry><entry>move to the previous page</entry></row>
-<row><entry><literal><last-entry></literal></entry><entry>*</entry><entry>move to the last entry</entry></row>
-<row><entry><literal><first-entry></literal></entry><entry>=</entry><entry>move to the first entry</entry></row>
-<row><entry><literal><enter-command></literal></entry><entry>:</entry><entry>enter a muttrc command</entry></row>
-<row><entry><literal><next-line></literal></entry><entry>></entry><entry>scroll down one line</entry></row>
-<row><entry><literal><previous-line></literal></entry><entry><</entry><entry>scroll up one line</entry></row>
-<row><entry><literal><half-up></literal></entry><entry>[</entry><entry>scroll up 1/2 page</entry></row>
-<row><entry><literal><half-down></literal></entry><entry>]</entry><entry>scroll down 1/2 page</entry></row>
-<row><entry><literal><help></literal></entry><entry>?</entry><entry>this screen</entry></row>
-<row><entry><literal><tag-prefix></literal></entry><entry>;</entry><entry>apply next function to tagged messages</entry></row>
-<row><entry><literal><tag-prefix-cond></literal></entry><entry></entry><entry>apply next function ONLY to tagged messages</entry></row>
-<row><entry><literal><end-cond></literal></entry><entry></entry><entry>end of conditional execution (noop)</entry></row>
-<row><entry><literal><shell-escape></literal></entry><entry>!</entry><entry>invoke a command in a subshell</entry></row>
-<row><entry><literal><select-entry></literal></entry><entry><Return></entry><entry>select the current entry</entry></row>
-<row><entry><literal><search></literal></entry><entry>/</entry><entry>search for a regular expression</entry></row>
-<row><entry><literal><search-reverse></literal></entry><entry>Esc /</entry><entry>search backwards for a regular expression</entry></row>
-<row><entry><literal><search-opposite></literal></entry><entry></entry><entry>search for next match in opposite direction</entry></row>
-<row><entry><literal><jump></literal></entry><entry></entry><entry>jump to an index number</entry></row>
-<row><entry><literal><current-top></literal></entry><entry></entry><entry>move entry to top of screen</entry></row>
-<row><entry><literal><current-middle></literal></entry><entry></entry><entry>move entry to middle of screen</entry></row>
-<row><entry><literal><current-bottom></literal></entry><entry></entry><entry>move entry to bottom of screen</entry></row>
-<row><entry><literal><what-key></literal></entry><entry></entry><entry>display the keycode for a key press</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="index_map">
-<title>index menu</title>
-
-
-<table id="index_table">
-<title>Default index function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><create-alias></literal></entry><entry>a</entry><entry>create an alias from a message sender</entry></row>
-<row><entry><literal><bounce-message></literal></entry><entry>b</entry><entry>remail a message to another user</entry></row>
-<row><entry><literal><break-thread></literal></entry><entry>#</entry><entry>break the thread in two</entry></row>
-<row><entry><literal><change-folder></literal></entry><entry>c</entry><entry>open a different folder</entry></row>
-<row><entry><literal><change-folder-readonly></literal></entry><entry>Esc c</entry><entry>open a different folder in read only mode</entry></row>
-<row><entry><literal><next-unread-mailbox></literal></entry><entry></entry><entry>open next mailbox with new mail</entry></row>
-<row><entry><literal><collapse-thread></literal></entry><entry>Esc v</entry><entry>collapse/uncollapse current thread</entry></row>
-<row><entry><literal><collapse-all></literal></entry><entry>Esc V</entry><entry>collapse/uncollapse all threads</entry></row>
-<row><entry><literal><copy-message></literal></entry><entry>C</entry><entry>copy a message to a file/mailbox</entry></row>
-<row><entry><literal><decode-copy></literal></entry><entry>Esc C</entry><entry>make decoded (text/plain) copy</entry></row>
-<row><entry><literal><decode-save></literal></entry><entry>Esc s</entry><entry>make decoded copy (text/plain) and delete</entry></row>
-<row><entry><literal><delete-message></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><delete-pattern></literal></entry><entry>D</entry><entry>delete messages matching a pattern</entry></row>
-<row><entry><literal><delete-thread></literal></entry><entry>^D</entry><entry>delete all messages in thread</entry></row>
-<row><entry><literal><delete-subthread></literal></entry><entry>Esc d</entry><entry>delete all messages in subthread</entry></row>
-<row><entry><literal><edit></literal></entry><entry>e</entry><entry>edit the raw message</entry></row>
-<row><entry><literal><edit-type></literal></entry><entry>^E</entry><entry>edit attachment content type</entry></row>
-<row><entry><literal><forward-message></literal></entry><entry>f</entry><entry>forward a message with comments</entry></row>
-<row><entry><literal><flag-message></literal></entry><entry>F</entry><entry>toggle a message's 'important' flag</entry></row>
-<row><entry><literal><group-reply></literal></entry><entry>g</entry><entry>reply to all recipients</entry></row>
-<row><entry><literal><fetch-mail></literal></entry><entry>G</entry><entry>retrieve mail from POP server</entry></row>
-<row><entry><literal><imap-fetch-mail></literal></entry><entry></entry><entry>force retrieval of mail from IMAP server</entry></row>
-<row><entry><literal><display-toggle-weed></literal></entry><entry>h</entry><entry>display message and toggle header weeding</entry></row>
-<row><entry><literal><next-undeleted></literal></entry><entry>j</entry><entry>move to the next undeleted message</entry></row>
-<row><entry><literal><previous-undeleted></literal></entry><entry>k</entry><entry>move to the previous undeleted message</entry></row>
-<row><entry><literal><limit></literal></entry><entry>l</entry><entry>show only messages matching a pattern</entry></row>
-<row><entry><literal><link-threads></literal></entry><entry>&</entry><entry>link tagged message to the current one</entry></row>
-<row><entry><literal><list-reply></literal></entry><entry>L</entry><entry>reply to specified mailing list</entry></row>
-<row><entry><literal><mail></literal></entry><entry>m</entry><entry>compose a new mail message</entry></row>
-<row><entry><literal><toggle-new></literal></entry><entry>N</entry><entry>toggle a message's 'new' flag</entry></row>
-<row><entry><literal><toggle-write></literal></entry><entry>%</entry><entry>toggle whether the mailbox will be rewritten</entry></row>
-<row><entry><literal><next-thread></literal></entry><entry>^N</entry><entry>jump to the next thread</entry></row>
-<row><entry><literal><next-subthread></literal></entry><entry>Esc n</entry><entry>jump to the next subthread</entry></row>
-<row><entry><literal><purge-message></literal></entry><entry></entry><entry>really delete the current entry, bypassing the trash folder</entry></row>
-<row><entry><literal><query></literal></entry><entry>Q</entry><entry>query external program for addresses</entry></row>
-<row><entry><literal><quit></literal></entry><entry>q</entry><entry>save changes to mailbox and quit</entry></row>
-<row><entry><literal><reply></literal></entry><entry>r</entry><entry>reply to a message</entry></row>
-<row><entry><literal><show-limit></literal></entry><entry>Esc l</entry><entry>show currently active limit pattern</entry></row>
-<row><entry><literal><sort-mailbox></literal></entry><entry>o</entry><entry>sort messages</entry></row>
-<row><entry><literal><sort-reverse></literal></entry><entry>O</entry><entry>sort messages in reverse order</entry></row>
-<row><entry><literal><print-message></literal></entry><entry>p</entry><entry>print the current entry</entry></row>
-<row><entry><literal><previous-thread></literal></entry><entry>^P</entry><entry>jump to previous thread</entry></row>
-<row><entry><literal><previous-subthread></literal></entry><entry>Esc p</entry><entry>jump to previous subthread</entry></row>
-<row><entry><literal><recall-message></literal></entry><entry>R</entry><entry>recall a postponed message</entry></row>
-<row><entry><literal><read-thread></literal></entry><entry>^R</entry><entry>mark the current thread as read</entry></row>
-<row><entry><literal><read-subthread></literal></entry><entry>Esc r</entry><entry>mark the current subthread as read</entry></row>
-<row><entry><literal><resend-message></literal></entry><entry>Esc e</entry><entry>use the current message as a template for a new one</entry></row>
-<row><entry><literal><save-message></literal></entry><entry>s</entry><entry>save message/attachment to a file</entry></row>
-<row><entry><literal><tag-pattern></literal></entry><entry>T</entry><entry>tag messages matching a pattern</entry></row>
-<row><entry><literal><tag-subthread></literal></entry><entry></entry><entry>tag the current subthread</entry></row>
-<row><entry><literal><tag-thread></literal></entry><entry>Esc t</entry><entry>tag the current thread</entry></row>
-<row><entry><literal><untag-pattern></literal></entry><entry>^T</entry><entry>untag messages matching a pattern</entry></row>
-<row><entry><literal><undelete-message></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-<row><entry><literal><undelete-pattern></literal></entry><entry>U</entry><entry>undelete messages matching a pattern</entry></row>
-<row><entry><literal><undelete-subthread></literal></entry><entry>Esc u</entry><entry>undelete all messages in subthread</entry></row>
-<row><entry><literal><undelete-thread></literal></entry><entry>^U</entry><entry>undelete all messages in thread</entry></row>
-<row><entry><literal><view-attachments></literal></entry><entry>v</entry><entry>show MIME attachments</entry></row>
-<row><entry><literal><show-version></literal></entry><entry>V</entry><entry>show the Mutt version number and date</entry></row>
-<row><entry><literal><set-flag></literal></entry><entry>w</entry><entry>set a status flag on a message</entry></row>
-<row><entry><literal><clear-flag></literal></entry><entry>W</entry><entry>clear a status flag from a message</entry></row>
-<row><entry><literal><display-message></literal></entry><entry><Return></entry><entry>display a message</entry></row>
-<row><entry><literal><buffy-list></literal></entry><entry>.</entry><entry>list mailboxes with new mail</entry></row>
-<row><entry><literal><sync-mailbox></literal></entry><entry>$</entry><entry>save changes to mailbox</entry></row>
-<row><entry><literal><display-address></literal></entry><entry>@</entry><entry>display full address of sender</entry></row>
-<row><entry><literal><pipe-message></literal></entry><entry>|</entry><entry>pipe message/attachment to a shell command</entry></row>
-<row><entry><literal><next-new></literal></entry><entry></entry><entry>jump to the next new message</entry></row>
-<row><entry><literal><next-new-then-unread></literal></entry><entry><Tab></entry><entry>jump to the next new or unread message</entry></row>
-<row><entry><literal><previous-new></literal></entry><entry></entry><entry>jump to the previous new message</entry></row>
-<row><entry><literal><previous-new-then-unread></literal></entry><entry>Esc <Tab></entry><entry>jump to the previous new or unread message</entry></row>
-<row><entry><literal><next-unread></literal></entry><entry></entry><entry>jump to the next unread message</entry></row>
-<row><entry><literal><previous-unread></literal></entry><entry></entry><entry>jump to the previous unread message</entry></row>
-<row><entry><literal><parent-message></literal></entry><entry>P</entry><entry>jump to parent message in thread</entry></row>
-<row><entry><literal><extract-keys></literal></entry><entry>^K</entry><entry>extract supported public keys</entry></row>
-<row><entry><literal><forget-passphrase></literal></entry><entry>^F</entry><entry>wipe passphrase(s) from memory</entry></row>
-<row><entry><literal><check-traditional-pgp></literal></entry><entry>Esc P</entry><entry>check for classic PGP</entry></row>
-<row><entry><literal><mail-key></literal></entry><entry>Esc k</entry><entry>mail a PGP public key</entry></row>
-<row><entry><literal><decrypt-copy></literal></entry><entry></entry><entry>make decrypted copy</entry></row>
-<row><entry><literal><decrypt-save></literal></entry><entry></entry><entry>make decrypted copy and delete</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="pager_map">
-<title>pager menu</title>
-
-
-<table id="pager_table">
-<title>Default pager function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><break-thread></literal></entry><entry>#</entry><entry>break the thread in two</entry></row>
-<row><entry><literal><create-alias></literal></entry><entry>a</entry><entry>create an alias from a message sender</entry></row>
-<row><entry><literal><bounce-message></literal></entry><entry>b</entry><entry>remail a message to another user</entry></row>
-<row><entry><literal><change-folder></literal></entry><entry>c</entry><entry>open a different folder</entry></row>
-<row><entry><literal><change-folder-readonly></literal></entry><entry>Esc c</entry><entry>open a different folder in read only mode</entry></row>
-<row><entry><literal><next-unread-mailbox></literal></entry><entry></entry><entry>open next mailbox with new mail</entry></row>
-<row><entry><literal><copy-message></literal></entry><entry>C</entry><entry>copy a message to a file/mailbox</entry></row>
-<row><entry><literal><decode-copy></literal></entry><entry>Esc C</entry><entry>make decoded (text/plain) copy</entry></row>
-<row><entry><literal><delete-message></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><delete-thread></literal></entry><entry>^D</entry><entry>delete all messages in thread</entry></row>
-<row><entry><literal><delete-subthread></literal></entry><entry>Esc d</entry><entry>delete all messages in subthread</entry></row>
-<row><entry><literal><edit></literal></entry><entry>e</entry><entry>edit the raw message</entry></row>
-<row><entry><literal><edit-type></literal></entry><entry>^E</entry><entry>edit attachment content type</entry></row>
-<row><entry><literal><forward-message></literal></entry><entry>f</entry><entry>forward a message with comments</entry></row>
-<row><entry><literal><flag-message></literal></entry><entry>F</entry><entry>toggle a message's 'important' flag</entry></row>
-<row><entry><literal><group-reply></literal></entry><entry>g</entry><entry>reply to all recipients</entry></row>
-<row><entry><literal><imap-fetch-mail></literal></entry><entry></entry><entry>force retrieval of mail from IMAP server</entry></row>
-<row><entry><literal><display-toggle-weed></literal></entry><entry>h</entry><entry>display message and toggle header weeding</entry></row>
-<row><entry><literal><next-undeleted></literal></entry><entry>j</entry><entry>move to the next undeleted message</entry></row>
-<row><entry><literal><next-entry></literal></entry><entry>J</entry><entry>move to the next entry</entry></row>
-<row><entry><literal><previous-undeleted></literal></entry><entry>k</entry><entry>move to the previous undeleted message</entry></row>
-<row><entry><literal><previous-entry></literal></entry><entry>K</entry><entry>move to the previous entry</entry></row>
-<row><entry><literal><link-threads></literal></entry><entry>&</entry><entry>link tagged message to the current one</entry></row>
-<row><entry><literal><list-reply></literal></entry><entry>L</entry><entry>reply to specified mailing list</entry></row>
-<row><entry><literal><redraw-screen></literal></entry><entry>^L</entry><entry>clear and redraw the screen</entry></row>
-<row><entry><literal><mail></literal></entry><entry>m</entry><entry>compose a new mail message</entry></row>
-<row><entry><literal><mark-as-new></literal></entry><entry>N</entry><entry>toggle a message's 'new' flag</entry></row>
-<row><entry><literal><search-next></literal></entry><entry>n</entry><entry>search for next match</entry></row>
-<row><entry><literal><next-thread></literal></entry><entry>^N</entry><entry>jump to the next thread</entry></row>
-<row><entry><literal><next-subthread></literal></entry><entry>Esc n</entry><entry>jump to the next subthread</entry></row>
-<row><entry><literal><print-message></literal></entry><entry>p</entry><entry>print the current entry</entry></row>
-<row><entry><literal><previous-thread></literal></entry><entry>^P</entry><entry>jump to previous thread</entry></row>
-<row><entry><literal><previous-subthread></literal></entry><entry>Esc p</entry><entry>jump to previous subthread</entry></row>
-<row><entry><literal><purge-message></literal></entry><entry></entry><entry>really delete the current entry, bypassing the trash folder</entry></row>
-<row><entry><literal><quit></literal></entry><entry>Q</entry><entry>save changes to mailbox and quit</entry></row>
-<row><entry><literal><exit></literal></entry><entry>q</entry><entry>exit this menu</entry></row>
-<row><entry><literal><reply></literal></entry><entry>r</entry><entry>reply to a message</entry></row>
-<row><entry><literal><recall-message></literal></entry><entry>R</entry><entry>recall a postponed message</entry></row>
-<row><entry><literal><read-thread></literal></entry><entry>^R</entry><entry>mark the current thread as read</entry></row>
-<row><entry><literal><read-subthread></literal></entry><entry>Esc r</entry><entry>mark the current subthread as read</entry></row>
-<row><entry><literal><resend-message></literal></entry><entry>Esc e</entry><entry>use the current message as a template for a new one</entry></row>
-<row><entry><literal><save-message></literal></entry><entry>s</entry><entry>save message/attachment to a file</entry></row>
-<row><entry><literal><skip-quoted></literal></entry><entry>S</entry><entry>skip beyond quoted text</entry></row>
-<row><entry><literal><decode-save></literal></entry><entry>Esc s</entry><entry>make decoded copy (text/plain) and delete</entry></row>
-<row><entry><literal><tag-message></literal></entry><entry>t</entry><entry>tag the current entry</entry></row>
-<row><entry><literal><toggle-quoted></literal></entry><entry>T</entry><entry>toggle display of quoted text</entry></row>
-<row><entry><literal><undelete-message></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-<row><entry><literal><undelete-subthread></literal></entry><entry>Esc u</entry><entry>undelete all messages in subthread</entry></row>
-<row><entry><literal><undelete-thread></literal></entry><entry>^U</entry><entry>undelete all messages in thread</entry></row>
-<row><entry><literal><view-attachments></literal></entry><entry>v</entry><entry>show MIME attachments</entry></row>
-<row><entry><literal><show-version></literal></entry><entry>V</entry><entry>show the Mutt version number and date</entry></row>
-<row><entry><literal><search-toggle></literal></entry><entry>\\</entry><entry>toggle search pattern coloring</entry></row>
-<row><entry><literal><display-address></literal></entry><entry>@</entry><entry>display full address of sender</entry></row>
-<row><entry><literal><next-new></literal></entry><entry></entry><entry>jump to the next new message</entry></row>
-<row><entry><literal><pipe-message></literal></entry><entry>|</entry><entry>pipe message/attachment to a shell command</entry></row>
-<row><entry><literal><help></literal></entry><entry>?</entry><entry>this screen</entry></row>
-<row><entry><literal><next-page></literal></entry><entry><Space></entry><entry>move to the next page</entry></row>
-<row><entry><literal><previous-page></literal></entry><entry>-</entry><entry>move to the previous page</entry></row>
-<row><entry><literal><top></literal></entry><entry>^</entry><entry>jump to the top of the message</entry></row>
-<row><entry><literal><sync-mailbox></literal></entry><entry>$</entry><entry>save changes to mailbox</entry></row>
-<row><entry><literal><shell-escape></literal></entry><entry>!</entry><entry>invoke a command in a subshell</entry></row>
-<row><entry><literal><enter-command></literal></entry><entry>:</entry><entry>enter a muttrc command</entry></row>
-<row><entry><literal><buffy-list></literal></entry><entry>.</entry><entry>list mailboxes with new mail</entry></row>
-<row><entry><literal><search></literal></entry><entry>/</entry><entry>search for a regular expression</entry></row>
-<row><entry><literal><search-reverse></literal></entry><entry>Esc /</entry><entry>search backwards for a regular expression</entry></row>
-<row><entry><literal><search-opposite></literal></entry><entry></entry><entry>search for next match in opposite direction</entry></row>
-<row><entry><literal><next-line></literal></entry><entry><Return></entry><entry>scroll down one line</entry></row>
-<row><entry><literal><jump></literal></entry><entry></entry><entry>jump to an index number</entry></row>
-<row><entry><literal><next-unread></literal></entry><entry></entry><entry>jump to the next unread message</entry></row>
-<row><entry><literal><previous-new></literal></entry><entry></entry><entry>jump to the previous new message</entry></row>
-<row><entry><literal><previous-unread></literal></entry><entry></entry><entry>jump to the previous unread message</entry></row>
-<row><entry><literal><half-up></literal></entry><entry></entry><entry>scroll up 1/2 page</entry></row>
-<row><entry><literal><half-down></literal></entry><entry></entry><entry>scroll down 1/2 page</entry></row>
-<row><entry><literal><previous-line></literal></entry><entry></entry><entry>scroll up one line</entry></row>
-<row><entry><literal><bottom></literal></entry><entry></entry><entry>jump to the bottom of the message</entry></row>
-<row><entry><literal><parent-message></literal></entry><entry>P</entry><entry>jump to parent message in thread</entry></row>
-<row><entry><literal><check-traditional-pgp></literal></entry><entry>Esc P</entry><entry>check for classic PGP</entry></row>
-<row><entry><literal><mail-key></literal></entry><entry>Esc k</entry><entry>mail a PGP public key</entry></row>
-<row><entry><literal><extract-keys></literal></entry><entry>^K</entry><entry>extract supported public keys</entry></row>
-<row><entry><literal><forget-passphrase></literal></entry><entry>^F</entry><entry>wipe passphrase(s) from memory</entry></row>
-<row><entry><literal><decrypt-copy></literal></entry><entry></entry><entry>make decrypted copy</entry></row>
-<row><entry><literal><decrypt-save></literal></entry><entry></entry><entry>make decrypted copy and delete</entry></row>
-<row><entry><literal><what-key></literal></entry><entry></entry><entry>display the keycode for a key press</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="alias_map">
-<title>alias menu</title>
-
-
-<table id="alias_table">
-<title>Default alias function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><delete-entry></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><undelete-entry></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="query_map">
-<title>query menu</title>
-
-
-<table id="query_table">
-<title>Default query function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><create-alias></literal></entry><entry>a</entry><entry>create an alias from a message sender</entry></row>
-<row><entry><literal><mail></literal></entry><entry>m</entry><entry>compose a new mail message</entry></row>
-<row><entry><literal><query></literal></entry><entry>Q</entry><entry>query external program for addresses</entry></row>
-<row><entry><literal><query-append></literal></entry><entry>A</entry><entry>append new query results to current results</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="attach_map">
-<title>attach menu</title>
-
-
-<table id="attach_table">
-<title>Default attach function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><bounce-message></literal></entry><entry>b</entry><entry>remail a message to another user</entry></row>
-<row><entry><literal><display-toggle-weed></literal></entry><entry>h</entry><entry>display message and toggle header weeding</entry></row>
-<row><entry><literal><edit-type></literal></entry><entry>^E</entry><entry>edit attachment content type</entry></row>
-<row><entry><literal><print-entry></literal></entry><entry>p</entry><entry>print the current entry</entry></row>
-<row><entry><literal><save-entry></literal></entry><entry>s</entry><entry>save message/attachment to a file</entry></row>
-<row><entry><literal><pipe-entry></literal></entry><entry>|</entry><entry>pipe message/attachment to a shell command</entry></row>
-<row><entry><literal><view-mailcap></literal></entry><entry>m</entry><entry>force viewing of attachment using mailcap</entry></row>
-<row><entry><literal><reply></literal></entry><entry>r</entry><entry>reply to a message</entry></row>
-<row><entry><literal><resend-message></literal></entry><entry>Esc e</entry><entry>use the current message as a template for a new one</entry></row>
-<row><entry><literal><group-reply></literal></entry><entry>g</entry><entry>reply to all recipients</entry></row>
-<row><entry><literal><list-reply></literal></entry><entry>L</entry><entry>reply to specified mailing list</entry></row>
-<row><entry><literal><forward-message></literal></entry><entry>f</entry><entry>forward a message with comments</entry></row>
-<row><entry><literal><view-text></literal></entry><entry>T</entry><entry>view attachment as text</entry></row>
-<row><entry><literal><view-attach></literal></entry><entry><Return></entry><entry>view attachment using mailcap entry if necessary</entry></row>
-<row><entry><literal><delete-entry></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><undelete-entry></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-<row><entry><literal><collapse-parts></literal></entry><entry>v</entry><entry>Toggle display of subparts</entry></row>
-<row><entry><literal><check-traditional-pgp></literal></entry><entry>Esc P</entry><entry>check for classic PGP</entry></row>
-<row><entry><literal><extract-keys></literal></entry><entry>^K</entry><entry>extract supported public keys</entry></row>
-<row><entry><literal><forget-passphrase></literal></entry><entry>^F</entry><entry>wipe passphrase(s) from memory</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="compose_map">
-<title>compose menu</title>
-
-
-<table id="compose_table">
-<title>Default compose function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><attach-file></literal></entry><entry>a</entry><entry>attach file(s) to this message</entry></row>
-<row><entry><literal><attach-message></literal></entry><entry>A</entry><entry>attach message(s) to this message</entry></row>
-<row><entry><literal><edit-bcc></literal></entry><entry>b</entry><entry>edit the BCC list</entry></row>
-<row><entry><literal><edit-cc></literal></entry><entry>c</entry><entry>edit the CC list</entry></row>
-<row><entry><literal><copy-file></literal></entry><entry>C</entry><entry>save message/attachment to a file</entry></row>
-<row><entry><literal><detach-file></literal></entry><entry>D</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><toggle-disposition></literal></entry><entry>^D</entry><entry>toggle disposition between inline/attachment</entry></row>
-<row><entry><literal><edit-description></literal></entry><entry>d</entry><entry>edit attachment description</entry></row>
-<row><entry><literal><edit-message></literal></entry><entry>e</entry><entry>edit the message</entry></row>
-<row><entry><literal><edit-headers></literal></entry><entry>E</entry><entry>edit the message with headers</entry></row>
-<row><entry><literal><edit-file></literal></entry><entry>^X e</entry><entry>edit the file to be attached</entry></row>
-<row><entry><literal><edit-encoding></literal></entry><entry>^E</entry><entry>edit attachment transfer-encoding</entry></row>
-<row><entry><literal><edit-from></literal></entry><entry>Esc f</entry><entry>edit the from field</entry></row>
-<row><entry><literal><edit-fcc></literal></entry><entry>f</entry><entry>enter a file to save a copy of this message in</entry></row>
-<row><entry><literal><filter-entry></literal></entry><entry>F</entry><entry>filter attachment through a shell command</entry></row>
-<row><entry><literal><get-attachment></literal></entry><entry>G</entry><entry>get a temporary copy of an attachment</entry></row>
-<row><entry><literal><display-toggle-weed></literal></entry><entry>h</entry><entry>display message and toggle header weeding</entry></row>
-<row><entry><literal><ispell></literal></entry><entry>i</entry><entry>run ispell on the message</entry></row>
-<row><entry><literal><print-entry></literal></entry><entry>l</entry><entry>print the current entry</entry></row>
-<row><entry><literal><edit-mime></literal></entry><entry>m</entry><entry>edit attachment using mailcap entry</entry></row>
-<row><entry><literal><new-mime></literal></entry><entry>n</entry><entry>compose new attachment using mailcap entry</entry></row>
-<row><entry><literal><postpone-message></literal></entry><entry>P</entry><entry>save this message to send later</entry></row>
-<row><entry><literal><edit-reply-to></literal></entry><entry>r</entry><entry>edit the Reply-To field</entry></row>
-<row><entry><literal><rename-file></literal></entry><entry>R</entry><entry>rename/move an attached file</entry></row>
-<row><entry><literal><edit-subject></literal></entry><entry>s</entry><entry>edit the subject of this message</entry></row>
-<row><entry><literal><edit-to></literal></entry><entry>t</entry><entry>edit the TO list</entry></row>
-<row><entry><literal><edit-type></literal></entry><entry>^T</entry><entry>edit attachment content type</entry></row>
-<row><entry><literal><write-fcc></literal></entry><entry>w</entry><entry>write the message to a folder</entry></row>
-<row><entry><literal><toggle-unlink></literal></entry><entry>u</entry><entry>toggle whether to delete file after sending it</entry></row>
-<row><entry><literal><toggle-recode></literal></entry><entry></entry><entry>toggle recoding of this attachment</entry></row>
-<row><entry><literal><update-encoding></literal></entry><entry>U</entry><entry>update an attachment's encoding info</entry></row>
-<row><entry><literal><view-attach></literal></entry><entry><Return></entry><entry>view attachment using mailcap entry if necessary</entry></row>
-<row><entry><literal><send-message></literal></entry><entry>y</entry><entry>send the message</entry></row>
-<row><entry><literal><pipe-entry></literal></entry><entry>|</entry><entry>pipe message/attachment to a shell command</entry></row>
-<row><entry><literal><attach-key></literal></entry><entry>Esc k</entry><entry>attach a PGP public key</entry></row>
-<row><entry><literal><pgp-menu></literal></entry><entry>p</entry><entry>show PGP options</entry></row>
-<row><entry><literal><forget-passphrase></literal></entry><entry>^F</entry><entry>wipe passphrase(s) from memory</entry></row>
-<row><entry><literal><smime-menu></literal></entry><entry>S</entry><entry>show S/MIME options</entry></row>
-<row><entry><literal><mix></literal></entry><entry>M</entry><entry>send the message through a mixmaster remailer chain</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="postpone_map">
-<title>postpone menu</title>
-
-
-<table id="postpone_table">
-<title>Default postpone function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><delete-entry></literal></entry><entry>d</entry><entry>delete the current entry</entry></row>
-<row><entry><literal><undelete-entry></literal></entry><entry>u</entry><entry>undelete the current entry</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="browser_map">
-<title>browser menu</title>
-
-
-<table id="browser_table">
-<title>Default browser function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><change-dir></literal></entry><entry>c</entry><entry>change directories</entry></row>
-<row><entry><literal><display-filename></literal></entry><entry>@</entry><entry>display the currently selected file's name</entry></row>
-<row><entry><literal><enter-mask></literal></entry><entry>m</entry><entry>enter a file mask</entry></row>
-<row><entry><literal><sort></literal></entry><entry>o</entry><entry>sort messages</entry></row>
-<row><entry><literal><sort-reverse></literal></entry><entry>O</entry><entry>sort messages in reverse order</entry></row>
-<row><entry><literal><select-new></literal></entry><entry>N</entry><entry>select a new file in this directory</entry></row>
-<row><entry><literal><check-new></literal></entry><entry></entry><entry>check mailboxes for new mail</entry></row>
-<row><entry><literal><toggle-mailboxes></literal></entry><entry><Tab></entry><entry>toggle whether to browse mailboxes or all files</entry></row>
-<row><entry><literal><view-file></literal></entry><entry><Space></entry><entry>view file</entry></row>
-<row><entry><literal><buffy-list></literal></entry><entry>.</entry><entry>list mailboxes with new mail</entry></row>
-<row><entry><literal><create-mailbox></literal></entry><entry>C</entry><entry>create a new mailbox (IMAP only)</entry></row>
-<row><entry><literal><delete-mailbox></literal></entry><entry>d</entry><entry>delete the current mailbox (IMAP only)</entry></row>
-<row><entry><literal><rename-mailbox></literal></entry><entry>r</entry><entry>rename the current mailbox (IMAP only)</entry></row>
-<row><entry><literal><subscribe></literal></entry><entry>s</entry><entry>subscribe to current mailbox (IMAP only)</entry></row>
-<row><entry><literal><unsubscribe></literal></entry><entry>u</entry><entry>unsubscribe from current mailbox (IMAP only)</entry></row>
-<row><entry><literal><toggle-subscribed></literal></entry><entry>T</entry><entry>toggle view all/subscribed mailboxes (IMAP only)</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="pgp_map">
-<title>pgp menu</title>
-
-
-<table id="pgp_table">
-<title>Default pgp function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><verify-key></literal></entry><entry>c</entry><entry>verify a PGP public key</entry></row>
-<row><entry><literal><view-name></literal></entry><entry>%</entry><entry>view the key's user id</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="smime_map">
-<title>smime menu</title>
-
-
-<table id="smime_table">
-<title>Default smime function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><verify-key></literal></entry><entry>c</entry><entry>verify a PGP public key</entry></row>
-<row><entry><literal><view-name></literal></entry><entry>%</entry><entry>view the key's user id</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="mix_map">
-<title>mix menu</title>
-
-
-<table id="mix_table">
-<title>Default mix function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><accept></literal></entry><entry><Return></entry><entry>Accept the chain constructed</entry></row>
-<row><entry><literal><append></literal></entry><entry>a</entry><entry>Append a remailer to the chain</entry></row>
-<row><entry><literal><insert></literal></entry><entry>i</entry><entry>Insert a remailer into the chain</entry></row>
-<row><entry><literal><delete></literal></entry><entry>d</entry><entry>Delete a remailer from the chain</entry></row>
-<row><entry><literal><chain-prev></literal></entry><entry><Left></entry><entry>Select the previous element of the chain</entry></row>
-<row><entry><literal><chain-next></literal></entry><entry><Right></entry><entry>Select the next element of the chain</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-<sect2 id="editor_map">
-<title>editor menu</title>
-
-
-<table id="editor_table">
-<title>Default editor function bindings</title>
-<tgroup cols="3">
-<thead>
-<row><entry>Function</entry><entry>Default key</entry><entry>Description</entry></row>
-</thead>
-<tbody>
-<row><entry><literal><bol></literal></entry><entry>^A</entry><entry>jump to the beginning of the line</entry></row>
-<row><entry><literal><backward-char></literal></entry><entry>^B</entry><entry>move the cursor one character to the left</entry></row>
-<row><entry><literal><backward-word></literal></entry><entry>Esc b</entry><entry>move the cursor to the beginning of the word</entry></row>
-<row><entry><literal><capitalize-word></literal></entry><entry>Esc c</entry><entry>capitalize the word</entry></row>
-<row><entry><literal><downcase-word></literal></entry><entry>Esc l</entry><entry>convert the word to lower case</entry></row>
-<row><entry><literal><upcase-word></literal></entry><entry>Esc u</entry><entry>convert the word to upper case</entry></row>
-<row><entry><literal><delete-char></literal></entry><entry>^D</entry><entry>delete the char under the cursor</entry></row>
-<row><entry><literal><eol></literal></entry><entry>^E</entry><entry>jump to the end of the line</entry></row>
-<row><entry><literal><forward-char></literal></entry><entry>^F</entry><entry>move the cursor one character to the right</entry></row>
-<row><entry><literal><forward-word></literal></entry><entry>Esc f</entry><entry>move the cursor to the end of the word</entry></row>
-<row><entry><literal><backspace></literal></entry><entry><Backspace></entry><entry>delete the char in front of the cursor</entry></row>
-<row><entry><literal><kill-eol></literal></entry><entry>^K</entry><entry>delete chars from cursor to end of line</entry></row>
-<row><entry><literal><kill-eow></literal></entry><entry>Esc d</entry><entry>delete chars from the cursor to the end of the word</entry></row>
-<row><entry><literal><kill-line></literal></entry><entry>^U</entry><entry>delete all chars on the line</entry></row>
-<row><entry><literal><quote-char></literal></entry><entry>^V</entry><entry>quote the next typed key</entry></row>
-<row><entry><literal><kill-word></literal></entry><entry>^W</entry><entry>delete the word in front of the cursor</entry></row>
-<row><entry><literal><complete></literal></entry><entry><Tab></entry><entry>complete filename or alias</entry></row>
-<row><entry><literal><complete-query></literal></entry><entry>^T</entry><entry>complete address with query</entry></row>
-<row><entry><literal><buffy-cycle></literal></entry><entry><Space></entry><entry>cycle among incoming mailboxes</entry></row>
-<row><entry><literal><history-up></literal></entry><entry></entry><entry>scroll up through the history list</entry></row>
-<row><entry><literal><history-down></literal></entry><entry></entry><entry>scroll down through the history list</entry></row>
-<row><entry><literal><transpose-chars></literal></entry><entry></entry><entry>transpose character under cursor with previous</entry></row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect2>
-
-
-</sect1>
-
-</chapter>
-
-<chapter id="miscellany">
-<title>Miscellany</title>
-
-<sect1 id="acknowledgements">
-<title>Acknowledgements</title>
-
-<para>
-Kari Hurtta <email>kari.hurtta@fmi.fi</email>
-co-developed the original MIME parsing code back in the ELM-ME days.
-</para>
-
-<para>
-The following people have been very helpful to the development of Mutt:
-</para>
-
-<itemizedlist>
-<listitem><para>Vikas Agnihotri <email>vikasa@writeme.com</email></para></listitem>
-<listitem><para>Francois Berjon <email>Francois.Berjon@aar.alcatel-alsthom.fr</email></para></listitem>
-<listitem><para>Aric Blumer <email>aric@fore.com</email></para></listitem>
-<listitem><para>John Capo <email>jc@irbs.com</email></para></listitem>
-<listitem><para>David Champion <email>dgc@uchicago.edu</email></para></listitem>
-<listitem><para>Brendan Cully <email>brendan@kublai.com</email></para></listitem>
-<listitem><para>Liviu Daia <email>daia@stoilow.imar.ro</email></para></listitem>
-<listitem><para>Thomas E. Dickey <email>dickey@herndon4.his.com</email></para></listitem>
-<listitem><para>David DeSimone <email>fox@convex.hp.com</email></para></listitem>
-<listitem><para>Nickolay N. Dudorov <email>nnd@wint.itfs.nsk.su</email></para></listitem>
-<listitem><para>Ruslan Ermilov <email>ru@freebsd.org</email></para></listitem>
-<listitem><para>Edmund Grimley Evans <email>edmundo@rano.org</email></para></listitem>
-<listitem><para>Michael Finken <email>finken@conware.de</email></para></listitem>
-<listitem><para>Sven Guckes <email>guckes@math.fu-berlin.de</email></para></listitem>
-<listitem><para>Lars Hecking <email>lhecking@nmrc.ie</email></para></listitem>
-<listitem><para>Mark Holloman <email>holloman@nando.net</email></para></listitem>
-<listitem><para>Andreas Holzmann <email>holzmann@fmi.uni-passau.de</email></para></listitem>
-<listitem><para>Marco d'Itri <email>md@linux.it</email></para></listitem>
-<listitem><para>Björn Jacke <email>bjacke@suse.com</email></para></listitem>
-<listitem><para>Byrial Jensen <email>byrial@image.dk</email></para></listitem>
-<listitem><para>David Jeske <email>jeske@igcom.net</email></para></listitem>
-<listitem><para>Christophe Kalt <email>kalt@hugo.int-evry.fr</email></para></listitem>
-<listitem><para>Tommi Komulainen <email>Tommi.Komulainen@iki.fi</email></para></listitem>
-<listitem><para>Felix von Leitner (a.k.a <quote>Fefe</quote>) <email>leitner@math.fu-berlin.de</email></para></listitem>
-<listitem><para>Brandon Long <email>blong@fiction.net</email></para></listitem>
-<listitem><para>Jimmy Mäkelä <email>jmy@flashback.net</email></para></listitem>
-<listitem><para>Lars Marowsky-Bree <email>lmb@pointer.in-minden.de</email></para></listitem>
-<listitem><para>Thomas <quote>Mike</quote> Michlmayr <email>mike@cosy.sbg.ac.at</email></para></listitem>
-<listitem><para>Andrew W. Nosenko <email>awn@bcs.zp.ua</email></para></listitem>
-<listitem><para>David O'Brien <email>obrien@Nuxi.cs.ucdavis.edu</email></para></listitem>
-<listitem><para>Clint Olsen <email>olsenc@ichips.intel.com</email></para></listitem>
-<listitem><para>Park Myeong Seok <email>pms@romance.kaist.ac.kr</email></para></listitem>
-<listitem><para>Thomas Parmelan <email>tom@ankh.fr.eu.org</email></para></listitem>
-<listitem><para>Ollivier Robert <email>roberto@keltia.freenix.fr</email></para></listitem>
-<listitem><para>Thomas Roessler <email>roessler@does-not-exist.org</email></para></listitem>
-<listitem><para>Roland Rosenfeld <email>roland@spinnaker.de</email></para></listitem>
-<listitem><para>Rocco Rutte <email>pdmef@gmx.net</email></para></listitem>
-<listitem><para>TAKIZAWA Takashi <email>taki@luna.email.ne.jp</email></para></listitem>
-<listitem><para>Allain Thivillon <email>Allain.Thivillon@alma.fr</email></para></listitem>
-<listitem><para>Gero Treuner <email>gero@70t.de</email></para></listitem>
-<listitem><para>Vsevolod Volkov <email>vvv@lucky.net</email></para></listitem>
-<listitem><para>Ken Weinert <email>kenw@ihs.com</email></para></listitem>
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="about">
-<title>About this document</title>
-
-<para>
-This document was written in <ulink url="http://docbook.sourceforge.net">DocBook</ulink>,
-and then rendered using the <ulink url="http://xmlsoft.org/XSLT/">Gnome XSLT toolkit</ulink>.
-</para>
-
-</sect1>
-
-</chapter>
-
-</book>
-
-<!--
-vim:ft=xml
--->
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 5. Mutt's MIME Support</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="advancedusage.html" title="Chapter 4. Advanced Usage" /><link rel="next" href="optionalfeatures.html" title="Chapter 6. Optional features" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 5. Mutt's MIME Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="advancedusage.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="optionalfeatures.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="mimesupport"></a>Chapter 5. Mutt's MIME Support</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="mimesupport.html#using-mime">1. Using MIME in Mutt</a></span></dt><dd><dl><dt><span class="sect2"><a href="mimesupport.html#mime-pager">1.1. Viewing MIME messages in the pager</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#attach-menu">1.2. The Attachment Menu</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#compose-menu">1.3. The Compose Menu</a></span></dt></dl></dd><dt><span class="sect1"><a href="mimesupport.html#mime-types">2. MIME Type configuration with <code class="literal">mime.types</code></a></span></dt><dt><span class="sect1"><a href="mimesupport.html#mailcap">3. MIME Viewer configuration with <code class="literal">mailcap</code></a></span></dt><dd><dl><dt><span class="sect2"><a href="mimesupport.html#mailcap-basics">3.1. The Basics of the mailcap file</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#secure-mailcap">3.2. Secure use of mailcap</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#advanced-mailcap">3.3. Advanced mailcap Usage</a></span></dt><dt><span class="sect2"><a href="mimesupport.html#mailcap-example">3.4. Example mailcap files</a></span></dt></dl></dd><dt><span class="sect1"><a href="mimesupport.html#auto-view">4. MIME Autoview</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#alternative-order">5. MIME Multipart/Alternative</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#attachments">6. Attachment Searching and Counting</a></span></dt><dt><span class="sect1"><a href="mimesupport.html#mime-lookup">7. MIME Lookup</a></span></dt></dl></div><p>
-Quite a bit of effort has been made to make Mutt 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 for MIME, there are two extra
-types of configuration files which Mutt uses. One is the
-<code class="literal">mime.types</code> file, which contains the mapping of file extensions to
-IANA MIME types. The other is the <code class="literal">mailcap</code> file, which specifies
-the external commands to use for handling specific MIME types.
-</p><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="using-mime"></a>1. Using MIME in Mutt</h2></div></div></div><p>
-There are three areas/menus in Mutt which deal with MIME, they are the
-pager (while viewing a message), the attachment menu and the compose
-menu.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-pager"></a>1.1. Viewing MIME messages in the pager</h3></div></div></div><p>
-When you select a message from the index and view it in the pager, Mutt
-decodes the message to a text representation. Mutt internally supports
-a number of MIME types, including <code class="literal">text/plain, text/enriched,
-message/rfc822, and message/news</code>. In addition, the export
-controlled version of Mutt recognizes a variety of PGP MIME types,
-including PGP/MIME and application/pgp.
-</p><p>
-Mutt will denote attachments with a couple lines describing them.
-These lines are of the form:
-</p><pre class="screen">
-[-- Attachment #1: Description --]
-[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
-</pre><p>
-Where the <code class="literal">Description</code> is the description or filename given for the
-attachment, and the <code class="literal">Encoding</code> is one of
-<code class="literal">7bit/8bit/quoted-printable/base64/binary</code>.
-</p><p>
-If Mutt cannot deal with a MIME type, it will display a message like:
-</p><pre class="screen">
-[-- image/gif is unsupported (use 'v' to view this part) --]
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-menu"></a>1.2. The Attachment Menu</h3></div></div></div><p>
-The default binding for <code class="literal">view-attachments</code> is `v', which displays the
-attachment menu for a message. The attachment menu displays a list of
-the 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 “<span class="quote">tag-prefix</span>” 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.
-</p><p>
-Finally, you can apply the usual message-related functions (like
-<a class="link" href="gettingstarted.html#resend-message"><code class="literal"><resend-message></code></a>, and the
-<code class="literal"><reply></code> and <code class="literal"><forward></code>
-functions) to attachments of type <code class="literal">message/rfc822</code>.
-</p><p>
-See the help on the attachment menu for more information.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-menu"></a>1.3. The Compose Menu</h3></div></div></div><p>
-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.
-</p><p>
-Attachments appear as follows:
-</p><pre class="screen">
-- 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>
-</pre><p>
-The '-' denotes that Mutt will delete the file after sending (or
-postponing, or canceling) the message. It can be toggled with the
-<code class="literal">toggle-unlink</code> command (default: u). The next field is the MIME
-content-type, and can be changed with the <code class="literal">edit-type</code> 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 <code class="literal">edit-encoding</code> 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 <code class="literal">rename-file</code> command (default: R).
-The final field is the description of the attachment, and can be
-changed with the <code class="literal">edit-description</code> command (default: d).
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-types"></a>2. MIME Type configuration with <code class="literal">mime.types</code></h2></div></div></div><p>
-When you add an attachment to your mail message, Mutt searches your
-personal mime.types file at <code class="literal">${HOME}/.mime.types</code>, and then
-the system mime.types file at <code class="literal">/usr/local/share/mutt/mime.types</code> or
-<code class="literal">/etc/mime.types</code>
-</p><p>
-The mime.types file consist of lines containing a MIME type and a space
-separated list of extensions. For example:
-</p><pre class="screen">
-application/postscript ps eps
-application/pgp pgp
-audio/x-aiff aif aifc aiff
-</pre><p>
-A sample <code class="literal">mime.types</code> file comes with the Mutt distribution, and
-should contain most of the MIME types you are likely to use.
-</p><p>
-If Mutt 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 will assume that the file is plain text, and mark it
-as <code class="literal">text/plain</code>. If the file contains binary information, then Mutt will
-mark it as <code class="literal">application/octet-stream</code>. You can change the MIME
-type that Mutt assigns to an attachment by using the <code class="literal">edit-type</code>
-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 recognizes all of these if the
-appropriate entry is found in the mime.types file. It also recognizes other
-major mime types, such as the chemical type that is widely used in the
-molecular modeling community to pass molecular data in various forms to
-various molecular viewers. Non-recognized mime types should only be used
-if the recipient of the message is likely to be expecting such attachments.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mailcap"></a>3. MIME Viewer configuration with <code class="literal">mailcap</code></h2></div></div></div><p>
-Mutt supports RFC 1524 MIME Configuration, in particular the Unix
-specific format specified in Appendix A of RFC 1524. 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.
-</p><p>
-In order to handle various MIME types that Mutt can not handle
-internally, Mutt parses a series of external configuration files to
-find an external handler. The default search string for these files
-is a colon delimited list containing the following files:
-</p><div class="orderedlist"><ol type="1"><li><p><code class="literal">$HOME/.mailcap</code></p></li><li><p><code class="literal">$PKGDATADIR/mailcap</code></p></li><li><p><code class="literal">$SYSCONFDIR/mailcap</code></p></li><li><p><code class="literal">/etc/mailcap</code></p></li><li><p><code class="literal">/usr/etc/mailcap</code></p></li><li><p><code class="literal">/usr/local/etc/mailcap</code></p></li></ol></div><p>
-where <code class="literal">$HOME</code> is your home directory. The
-<code class="literal">$PKGDATADIR</code> and the
-<code class="literal">$SYSCONFDIR</code> directories depend on where mutt
-is installed: the former is the default for shared data, the
-latter for system configuration files.
-</p><p>
-The default search path can be obtained by running the following
-command:
-</p><pre class="screen">
-mutt -nF /dev/null -Q mailcap_path
-</pre><p>
-In particular, the metamail distribution will install a mailcap file,
-usually as <code class="literal">/usr/local/etc/mailcap</code>, which contains some baseline
-entries.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-basics"></a>3.1. The Basics of the mailcap file</h3></div></div></div><p>
-A mailcap file consists of a series of lines which are comments, blank,
-or definitions.
-</p><p>
-A comment line consists of a # character followed by anything you want.
-</p><p>
-A blank line is blank.
-</p><p>
-A definition line consists of a content type, a view command, and any
-number of optional fields. Each field of a definition line is divided
-by a semicolon ';' character.
-</p><p>
-The content type is specified in the MIME standard type/subtype method.
-For example,
-<code class="literal">text/plain, text/html, image/gif, </code>
-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, <code class="literal">image/*</code>, or
-<code class="literal">video,</code> will match all image types and video types,
-respectively.
-</p><p>
-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 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 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.
-</p><p>
-So, in the simplest form, you can send a text/plain message to the
-external pager more on stdin:
-</p><pre class="screen">
-text/plain; more
-</pre><p>
-Or, you could send the message as a file:
-</p><pre class="screen">
-text/plain; more %s
-</pre><p>
-Perhaps you would like to use lynx to interactively view a text/html
-message:
-</p><pre class="screen">
-text/html; lynx %s
-</pre><p>
-In this case, lynx does not support viewing a file from stdin, so you
-must use the %s syntax.
-</p><div class="note"><h3 class="title">Note</h3><p>
-<span class="emphasis"><em>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.</em></span>
-</p></div><p>
-On the other hand, maybe you don't want to use lynx interactively, you
-just want to have it convert the text/html to text/plain, then you can
-use:
-</p><pre class="screen">
-text/html; lynx -dump %s | more
-</pre><p>
-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:
-</p><pre class="screen">
-text/html; lynx %s
-text/*; more
-</pre><p>
-This is the simplest form of a mailcap file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="secure-mailcap"></a>3.2. Secure use of mailcap</h3></div></div></div><p>
-The interpretation of shell meta-characters embedded in MIME parameters
-can lead to security problems in general. Mutt tries to quote parameters
-in expansion of %s syntaxes properly, and avoids risky characters by
-substituting them, see the <a class="link" href="reference.html#mailcap-sanitize" title="3.107. mailcap_sanitize">$mailcap_sanitize</a> variable.
-</p><p>
-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:
-</p><p>
-<span class="emphasis"><em>Keep the %-expandos away from shell quoting.</em></span>
-Don't quote them with single or double quotes. Mutt 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 behavior with quotes introduces new leaks - there is no
-alternative to correct quoting in the first place.
-</p><p>
-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 <code class="literal">$charset</code> inside the backtick expansion is safe,
-since it is not itself subject to any further expansion):
-</p><pre class="screen">
-text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
- && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="advanced-mailcap"></a>3.3. Advanced mailcap Usage</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="optional-mailcap-fields"></a>3.3.1. Optional Fields</h4></div></div></div><p>
-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 recognizes the following optional fields:
-</p><div class="variablelist"><dl><dt><span class="term">copiousoutput</span></dt><dd><p>
-This flag tells Mutt that the command passes possibly large amounts of
-text on stdout. This causes Mutt 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 assumes that the command
-is interactive. One could use this to replace the pipe to <code class="literal">more</code>
-in the <code class="literal">lynx -dump</code> example in the Basic section:
-</p><pre class="screen">
-text/html; lynx -dump %s ; copiousoutput
-</pre><p>
-This will cause lynx to format the text/html output as text/plain
-and Mutt will use your standard pager to display the results.
-</p></dd><dt><span class="term">needsterminal</span></dt><dd><p>
-Mutt uses this flag when viewing attachments with <a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a>, in order to decide whether it should honor the setting
-of the <a class="link" href="reference.html#wait-key" title="3.300. wait_key">$wait_key</a> variable or
-not. When an attachment is viewed using an interactive program, and the
-corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag, Mutt will use
-<a class="link" href="reference.html#wait-key" title="3.300. wait_key">$wait_key</a> and the exit status
-of 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.
-</p></dd><dt><span class="term">compose=<command></span></dt><dd><p>
-This flag specifies the command to use to create a new attachment of a
-specific MIME type. Mutt supports this from the compose menu.
-</p></dd><dt><span class="term">composetyped=<command></span></dt><dd><p>
-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 supports this from the compose menu.
-</p></dd><dt><span class="term">print=<command></span></dt><dd><p>
-This flag specifies the command to use to print a specific MIME type.
-Mutt supports this from the attachment and compose menus.
-</p></dd><dt><span class="term">edit=<command></span></dt><dd><p>
-This flag specifies the command to use to edit a specific MIME type.
-Mutt supports this from the compose menu, and also uses it to compose
-new attachments. Mutt will default to the defined editor for text
-attachments.
-</p></dd><dt><span class="term">nametemplate=<template></span></dt><dd><p>
-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 <code class="literal">text/html</code> if the file ends in <code class="literal">.html</code>.
-So, you would specify lynx as a <code class="literal">text/html</code> viewer with a line in
-the mailcap file like:
-</p><pre class="screen">
-text/html; lynx %s; nametemplate=%s.html
-</pre></dd><dt><span class="term">test=<command></span></dt><dd><p>
-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 uses this entry. If the command returns non-zero,
-then the test failed, and Mutt continues searching for the right entry.
-Note that the content-type must match before Mutt performs the test.
-For example:
-</p><pre class="screen">
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s
-</pre><p>
-In this example, Mutt 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 will call netscape to display the
-text/html object. If RunningX doesn't return 0, then Mutt will go on
-to the next entry and use lynx to display the text/html object.
-</p></dd></dl></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-search-order"></a>3.3.2. Search Order</h4></div></div></div><p>
-When searching for an entry in the mailcap file, Mutt will search for
-the most useful entry for its purpose. For instance, if you are
-attempting to print an <code class="literal">image/gif</code>, and you have the following
-entries in your mailcap file, Mutt will search for an entry with the
-print command:
-</p><pre class="screen">
-image/*; xv %s
-image/gif; ; print= anytopnm %s | pnmtops | lpr; \
- nametemplate=%s.gif
-</pre><p>
-Mutt will skip the <code class="literal">image/*</code> entry and use the <code class="literal">image/gif</code>
-entry with the print command.
-</p><p>
-In addition, you can use this with <a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a>
-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.
-</p><pre class="screen">
-text/html; netscape -remote 'openURL(%s)' ; test=RunningX
-text/html; lynx %s; nametemplate=%s.html
-text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
-</pre><p>
-For <a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a>, Mutt 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 will use the second entry
-for interactive viewing.
-</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="mailcap-command-expansion"></a>3.3.3. Command Expansion</h4></div></div></div><p>
-The various commands defined in the mailcap files are passed to the
-<code class="literal">/bin/sh</code> shell using the system() function. Before the
-command is passed to <code class="literal">/bin/sh -c</code>, it is parsed to expand
-various special parameters with information from Mutt. The keywords
-Mutt expands are:
-</p><div class="variablelist"><dl><dt><span class="term">%s</span></dt><dd><p>
-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 to not pass the body of the message
-to the view/print/edit program on stdin.
-</p></dd><dt><span class="term">%t</span></dt><dd><p>
-Mutt 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 <code class="literal">text/html</code> or
-<code class="literal">image/gif</code>.
-</p></dd><dt><span class="term">%{<parameter>}</span></dt><dd><p>
-Mutt 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:
-</p><pre class="screen">
-Content-Type: text/plain; charset=iso-8859-1
-</pre><p>
-then Mutt 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.
-</p></dd><dt><span class="term">\%</span></dt><dd><p>
-This will be replaced by a %
-</p></dd></dl></div><p>
-Mutt 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.
-</p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-example"></a>3.4. Example mailcap files</h3></div></div></div><p>
-This mailcap file is fairly simple and standard:
-</p><pre class="screen">
-# I'm always running X :)
-video/*; xanim %s > /dev/null
-image/*; xv %s > /dev/null
-
-# I'm always running netscape (if my computer had more memory, maybe)
-text/html; netscape -remote 'openURL(%s)'
-</pre><p>
-This mailcap file shows quite a number of examples:
-</p><pre class="screen">
-# Use xanim to view all videos Xanim produces a header on startup,
-# send that to /dev/null so I don't see it
-video/*; xanim %s > /dev/null
-
-# Send html to a running netscape by remote
-text/html; netscape -remote 'openURL(%s)'; test=RunningNetscape
-
-# If I'm not running netscape but I am running X, start netscape on the
-# object
-text/html; netscape %s; test=RunningX
-
-# Else use lynx to view it as text
-text/html; lynx %s
-
-# This version would convert the text/html to text/plain
-text/html; lynx -dump %s; copiousoutput
-
-# I use enscript to print text in two columns to a page
-text/*; more %s; print=enscript -2Gr %s
-
-# Netscape adds a flag to tell itself to view jpegs internally
-image/jpeg;xv %s; x-mozilla-flags=internal
-
-# Use xv to view images if I'm running X
-# In addition, this uses the \ to extend the line and set my editor
-# for images
-image/*;xv %s; test=RunningX; \
- edit=xpaint %s
-
-# Convert images to text using the netpbm tools
-image/*; (anytopnm %s | pnmscale -xysize 80 46 | ppmtopgm | pgmtopbm |
-pbmtoascii -1x2 ) 2>&1 ; copiousoutput
-
-# Send excel spreadsheets to my NT box
-application/ms-excel; open.pl %s
-</pre></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="auto-view"></a>4. MIME Autoview</h2></div></div></div><p>
-In addition to explicitly telling Mutt to view an attachment with the
-MIME viewer defined in the mailcap file, Mutt has support for
-automatically viewing MIME attachments while in the pager.
-</p><p>
-To work, you must define a viewer in the mailcap file which uses the
-<code class="literal">copiousoutput</code> 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.
-</p><p>
-You then use the <code class="literal">auto_view</code> muttrc command to list the
-content-types that you wish to view automatically.
-</p><p>
-For instance, if you set auto_view to:
-</p><pre class="screen">
-auto_view text/html application/x-gunzip \
- application/postscript image/gif application/x-tar-gz
-</pre><p>
-Mutt could use the following mailcap entries to automatically view
-attachments of these types.
-</p><pre class="screen">
-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
-</pre><p>
-“<span class="quote">unauto_view</span>” 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.
-“<span class="quote">unauto_view *</span>” will remove all previous entries.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="alternative-order"></a>5. MIME Multipart/Alternative</h2></div></div></div><p>
-Mutt 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 types
-is preferred. The alternative_order list consists of a number of
-mimetypes in order, including support for implicit and explicit
-wildcards, for example:
-</p><pre class="screen">
-alternative_order text/enriched text/plain text application/postscript image/*
-</pre><p>
-Next, mutt will check if any of the types have a defined
-<a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a>, and use that. Failing
-that, Mutt will look for any text type. As a last attempt, mutt will
-look for any type it knows how to handle.
-</p><p>
-To remove a MIME type from the <code class="literal">alternative_order</code> list, use the
-<code class="literal">unalternative_order</code> command.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="attachments"></a>6. Attachment Searching and Counting</h2></div></div></div><p>
-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.
-</p><p>
-In order to provide this information, mutt needs to fully MIME-parse
-all messages affected first. This can slow down operation especially for
-remote mail folders such as IMAP because all messages have to be
-downloaded first regardless whether the user really wants to view them
-or not.
-</p><p>
-The syntax is:
-</p><pre class="screen">
-attachments {+|-}disposition mime-type
-unattachments {+|-}disposition mime-type
-attachments ?
-</pre><p>
-Disposition is the attachment's Content-disposition type -- either
-<code class="literal">inline</code> or <code class="literal">attachment</code>.
-You can abbreviate this to <code class="literal">I</code> or <code class="literal">A</code>.
-</p><p>
-Disposition is prefixed by either a + symbol or 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.
-</p><p>
-Mime-type is, unsurprisingly, the MIME type of the attachment you want
-to affect. A MIME type is always of the format <code class="literal">major/minor</code>, where
-<code class="literal">major</code> describes the broad category of document you're looking at, and
-<code class="literal">minor</code> describes the specific type within that category. The major
-part of mime-type must be literal text (or the special token “<span class="quote"><code class="literal">*</code></span>”), but
-the minor part may be a regular expression. (Therefore, “<span class="quote"><code class="literal">*/.*</code></span>” matches
-any MIME type.)
-</p><p>
-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.
-</p><p>
-Some examples might help to illustrate. The examples that are not
-commented out define the default configuration of the lists.
-</p><div class="example"><a id="ex-attach-count"></a><p class="title"><b>Example 5.1. Attachment counting</b></p><div class="example-contents"><pre class="screen">
-## 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
-</pre></div></div><br class="example-break" /><p>
-Entering the command “<span class="quote"><code class="literal">attachments ?</code></span>”
-as a command will list your current settings in Muttrc format, so that
-it can be pasted elsewhere.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="mime-lookup"></a>7. MIME Lookup</h2></div></div></div><p>
-Mutt's mime_lookup list specifies a list of mime-types that should not
-be treated according to their mailcap entry. This option is designed to
-deal 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:
-</p><pre class="screen">
-mime_lookup application/octet-stream application/X-Lotus-Manuscript
-</pre><p>
-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.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="advancedusage.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="optionalfeatures.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Advanced Usage </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 6. Optional features</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 9. Miscellany</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="reference.html" title="Chapter 8. Reference" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 9. Miscellany</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="reference.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="miscellany"></a>Chapter 9. Miscellany</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="miscellany.html#acknowledgements">1. Acknowledgements</a></span></dt><dt><span class="sect1"><a href="miscellany.html#about">2. About this document</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="acknowledgements"></a>1. Acknowledgements</h2></div></div></div><p>
-Kari Hurtta <code class="email"><<a class="email" href="mailto:kari.hurtta@fmi.fi">kari.hurtta@fmi.fi</a>></code>
-co-developed the original MIME parsing code back in the ELM-ME days.
-</p><p>
-The following people have been very helpful to the development of Mutt:
-</p><div class="itemizedlist"><ul type="disc"><li><p>Vikas Agnihotri <code class="email"><<a class="email" href="mailto:vikasa@writeme.com">vikasa@writeme.com</a>></code></p></li><li><p>Francois Berjon <code class="email"><<a class="email" href="mailto:Francois.Berjon@aar.alcatel-alsthom.fr">Francois.Berjon@aar.alcatel-alsthom.fr</a>></code></p></li><li><p>Aric Blumer <code class="email"><<a class="email" href="mailto:aric@fore.com">aric@fore.com</a>></code></p></li><li><p>John Capo <code class="email"><<a class="email" href="mailto:jc@irbs.com">jc@irbs.com</a>></code></p></li><li><p>David Champion <code class="email"><<a class="email" href="mailto:dgc@uchicago.edu">dgc@uchicago.edu</a>></code></p></li><li><p>Brendan Cully <code class="email"><<a class="email" href="mailto:brendan@kublai.com">brendan@kublai.com</a>></code></p></li><li><p>Liviu Daia <code class="email"><<a class="email" href="mailto:daia@stoilow.imar.ro">daia@stoilow.imar.ro</a>></code></p></li><li><p>Thomas E. Dickey <code class="email"><<a class="email" href="mailto:dickey@herndon4.his.com">dickey@herndon4.his.com</a>></code></p></li><li><p>David DeSimone <code class="email"><<a class="email" href="mailto:fox@convex.hp.com">fox@convex.hp.com</a>></code></p></li><li><p>Nickolay N. Dudorov <code class="email"><<a class="email" href="mailto:nnd@wint.itfs.nsk.su">nnd@wint.itfs.nsk.su</a>></code></p></li><li><p>Ruslan Ermilov <code class="email"><<a class="email" href="mailto:ru@freebsd.org">ru@freebsd.org</a>></code></p></li><li><p>Edmund Grimley Evans <code class="email"><<a class="email" href="mailto:edmundo@rano.org">edmundo@rano.org</a>></code></p></li><li><p>Michael Finken <code class="email"><<a class="email" href="mailto:finken@conware.de">finken@conware.de</a>></code></p></li><li><p>Sven Guckes <code class="email"><<a class="email" href="mailto:guckes@math.fu-berlin.de">guckes@math.fu-berlin.de</a>></code></p></li><li><p>Lars Hecking <code class="email"><<a class="email" href="mailto:lhecking@nmrc.ie">lhecking@nmrc.ie</a>></code></p></li><li><p>Mark Holloman <code class="email"><<a class="email" href="mailto:holloman@nando.net">holloman@nando.net</a>></code></p></li><li><p>Andreas Holzmann <code class="email"><<a class="email" href="mailto:holzmann@fmi.uni-passau.de">holzmann@fmi.uni-passau.de</a>></code></p></li><li><p>Marco d'Itri <code class="email"><<a class="email" href="mailto:md@linux.it">md@linux.it</a>></code></p></li><li><p>Björn Jacke <code class="email"><<a class="email" href="mailto:bjacke@suse.com">bjacke@suse.com</a>></code></p></li><li><p>Byrial Jensen <code class="email"><<a class="email" href="mailto:byrial@image.dk">byrial@image.dk</a>></code></p></li><li><p>David Jeske <code class="email"><<a class="email" href="mailto:jeske@igcom.net">jeske@igcom.net</a>></code></p></li><li><p>Christophe Kalt <code class="email"><<a class="email" href="mailto:kalt@hugo.int-evry.fr">kalt@hugo.int-evry.fr</a>></code></p></li><li><p>Tommi Komulainen <code class="email"><<a class="email" href="mailto:Tommi.Komulainen@iki.fi">Tommi.Komulainen@iki.fi</a>></code></p></li><li><p>Felix von Leitner (a.k.a “<span class="quote">Fefe</span>”) <code class="email"><<a class="email" href="mailto:leitner@math.fu-berlin.de">leitner@math.fu-berlin.de</a>></code></p></li><li><p>Brandon Long <code class="email"><<a class="email" href="mailto:blong@fiction.net">blong@fiction.net</a>></code></p></li><li><p>Jimmy Mäkelä <code class="email"><<a class="email" href="mailto:jmy@flashback.net">jmy@flashback.net</a>></code></p></li><li><p>Lars Marowsky-Bree <code class="email"><<a class="email" href="mailto:lmb@pointer.in-minden.de">lmb@pointer.in-minden.de</a>></code></p></li><li><p>Thomas “<span class="quote">Mike</span>” Michlmayr <code class="email"><<a class="email" href="mailto:mike@cosy.sbg.ac.at">mike@cosy.sbg.ac.at</a>></code></p></li><li><p>Andrew W. Nosenko <code class="email"><<a class="email" href="mailto:awn@bcs.zp.ua">awn@bcs.zp.ua</a>></code></p></li><li><p>David O'Brien <code class="email"><<a class="email" href="mailto:obrien@Nuxi.cs.ucdavis.edu">obrien@Nuxi.cs.ucdavis.edu</a>></code></p></li><li><p>Clint Olsen <code class="email"><<a class="email" href="mailto:olsenc@ichips.intel.com">olsenc@ichips.intel.com</a>></code></p></li><li><p>Park Myeong Seok <code class="email"><<a class="email" href="mailto:pms@romance.kaist.ac.kr">pms@romance.kaist.ac.kr</a>></code></p></li><li><p>Thomas Parmelan <code class="email"><<a class="email" href="mailto:tom@ankh.fr.eu.org">tom@ankh.fr.eu.org</a>></code></p></li><li><p>Ollivier Robert <code class="email"><<a class="email" href="mailto:roberto@keltia.freenix.fr">roberto@keltia.freenix.fr</a>></code></p></li><li><p>Thomas Roessler <code class="email"><<a class="email" href="mailto:roessler@does-not-exist.org">roessler@does-not-exist.org</a>></code></p></li><li><p>Roland Rosenfeld <code class="email"><<a class="email" href="mailto:roland@spinnaker.de">roland@spinnaker.de</a>></code></p></li><li><p>Rocco Rutte <code class="email"><<a class="email" href="mailto:pdmef@gmx.net">pdmef@gmx.net</a>></code></p></li><li><p>TAKIZAWA Takashi <code class="email"><<a class="email" href="mailto:taki@luna.email.ne.jp">taki@luna.email.ne.jp</a>></code></p></li><li><p>Allain Thivillon <code class="email"><<a class="email" href="mailto:Allain.Thivillon@alma.fr">Allain.Thivillon@alma.fr</a>></code></p></li><li><p>Gero Treuner <code class="email"><<a class="email" href="mailto:gero@70t.de">gero@70t.de</a>></code></p></li><li><p>Vsevolod Volkov <code class="email"><<a class="email" href="mailto:vvv@lucky.net">vvv@lucky.net</a>></code></p></li><li><p>Ken Weinert <code class="email"><<a class="email" href="mailto:kenw@ihs.com">kenw@ihs.com</a>></code></p></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="about"></a>2. About this document</h2></div></div></div><p>
-This document was written in <a class="ulink" href="http://docbook.sourceforge.net" target="_top">DocBook</a>,
-and then rendered using the <a class="ulink" href="http://xmlsoft.org/XSLT/" target="_top">Gnome XSLT toolkit</a>.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="reference.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">Chapter 8. Reference </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
+++ /dev/null
-.\" -*-nroff-*-
-.\"
-.\"
-.\" Copyright (C) 1996-2004 Michael R. Elkins <me@cs.hmc.edu>
-.\"
-.\" This program is free software; you can redistribute it and/or modify
-.\" it under the terms of the GNU General Public License as published by
-.\" the Free Software Foundation; either version 2 of the License, or
-.\" (at your option) any later version.
-.\"
-.\" This program is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-.\"
-.TH mutt 1 "January 2009" Unix "User Manuals"
-.SH NAME
-mutt \- The Mutt Mail User Agent
-.SH SYNOPSIS
-.PP
-.B mutt
-[\-nRyzZ]
-[\-e \fIcmd\fP] [\-F \fIfile\fP] [\-m \fItype\fP] [\-f \fIfile\fP]
-.PP
-.B mutt
-[\-nx]
-[\-e \fIcmd\fP]
-[\-F \fIfile\fP]
-[\-H \fIfile\fP]
-[\-i \fIfile\fP]
-[\-s \fIsubj\fP]
-[\-b \fIaddr\fP]
-[\-c \fIaddr\fP]
-[\-a \fIfile\fP [...]]
-[\-\-]
-\fIaddr\fP [...]
-.PP
-.B mutt
-[\-nx]
-[\-e \fIcmd\fP]
-[\-F \fIfile\fP]
-[\-s \fIsubj\fP]
-[\-b \fIaddr\fP]
-[\-c \fIaddr\fP]
-[\-a \fIfile\fP [...]]
-[\-\-]
-\fIaddr\fP [...]
-< message
-.PP
-.B mutt
-[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-p
-.PP
-.B mutt
-[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-A \fIalias\fP
-.PP
-.B mutt
-[\-n] [\-e \fIcmd\fP] [\-F \fIfile\fP] \-Q \fIquery\fP
-.PP
-.B mutt
-\-v[v]
-.PP
-.B mutt
-\-D
-.SH DESCRIPTION
-.PP
-Mutt is a small but very powerful text based program for reading and sending electronic
-mail under unix operating systems, including support for color terminals, MIME,
-OpenPGP, and a threaded sorting mode.
-.PP
-.I Note:
-.IR
-This manual page gives a brief overview of mutt's command line
-options. You should find a copy of the full manual in /usr/share/doc, in
-text, HTML, and/or PDF format.
-.SH OPTIONS
-.PP
-.IP "-A \fIalias\fP"
-An expanded version of the given alias is passed to stdout.
-.IP "-a \fIfile\fP [...]"
-Attach a file to your message using MIME.
-When attaching single or multiple files, separating filenames and recipient addresses with
-"\-\-" is mandatory, e.g. \fBmutt \-a image.jpg \-\- addr1\fP or
-\fBmutt \-a img.jpg *.png \-\- addr1 addr2\fP.
-The \-a option must be placed at the end of command line options.
-.IP "-b \fIaddress\fP"
-Specify a blind-carbon-copy (BCC) recipient
-.IP "-c \fIaddress\fP"
-Specify a carbon-copy (CC) recipient
-.IP "-d \fIlevel\fp"
-If mutt was complied with +DEBUG log debugging output to ~/.muttdebug0.
-\fILevel\fP can range from 1-5 and effects verbosity. A value of 2 is
-recommended.
-.IP "-D"
-Print the value of all configuration options to stdout.
-.IP "-e \fIcommand\fP"
-Specify a configuration command to be run after processing of initialization
-files.
-.IP "-f \fImailbox\fP"
-Specify which mailbox to load.
-.IP "-F \fImuttrc\fP"
-Specify an initialization file to read instead of ~/.muttrc
-.IP "-h"
-Display help.
-.IP "-H \fIdraft\fP"
-Specify a draft file which contains header and body to use to send a
-message.
-.IP "-i \fIinclude\fP"
-Specify a file to include into the body of a message.
-.IP "-m \fItype\fP "
-specify a default mailbox type
-.IP "-n"
-Causes Mutt to bypass the system configuration file.
-.IP "-p"
-Resume a postponed message.
-.IP "-Q \fIquery\fP"
-Query a configuration variables value. The query is executed after
-all configuration files have been parsed, and any commands given on
-the command line have been executed.
-.IP "-R"
-Open a mailbox in \fIread-only\fP mode.
-.IP "-s \fIsubject\fP"
-Specify the subject of the message.
-.IP "-v"
-Display the Mutt version number and compile-time definitions.
-.IP "-vv"
-Display license and copyright information.
-.IP "-x"
-Emulate the mailx compose mode.
-.IP "-y"
-Start Mutt with a listing of all mailboxes specified by the \fImailboxes\fP
-command.
-.IP "-z"
-When used with \-f, causes Mutt not to start if there are no messages in the
-mailbox.
-.IP "-Z"
-Causes Mutt to open the first mailbox specified by the \fImailboxes\fP
-command which contains new mail.
-.IP "--"
-Treat remaining arguments as \fIaddr\fP even if they start with a dash.
-See also "\-a" above.
-.SH ENVIRONMENT
-.PP
-.IP "EDITOR"
-Specifies the editor to use if VISUAL is unset.
-.IP "EMAIL"
-The user's e-mail address.
-.IP "HOME"
-Full path of the user's home directory.
-.IP "MAIL"
-Full path of the user's spool mailbox.
-.IP "MAILDIR"
-Full path of the user's spool mailbox. Commonly used when the spool
-mailbox is a
-.B maildir (5)
-folder.
-.IP "MAILCAPS"
-Path to search for mailcap files.
-.IP "MM_NOASK"
-If this variable is set, mailcap are always used without prompting first.
-.IP "PGPPATH"
-Directory in which the user's PGP public keyring can be found.
-.IP "TMPDIR"
-Directory in which temporary files are created.
-.IP "REPLYTO"
-Default Reply-To address.
-.IP "VISUAL"
-Specifies the editor to use when composing messages.
-.SH FILES
-.PP
-.IP "~/.muttrc or ~/.mutt/muttrc"
-User configuration file.
-.IP "/etc/Muttrc"
-System-wide configuration file.
-.IP "/tmp/muttXXXXXX"
-Temporary files created by Mutt.
-.IP "~/.mailcap"
-User definition for handling non-text MIME types.
-.IP "/etc/mailcap"
-System definition for handling non-text MIME types.
-.IP "~/.mime.types"
-User's personal mapping between MIME types and file extensions.
-.IP "/etc/mime.types"
-System mapping between MIME types and file extensions.
-.IP "/usr/bin/mutt_dotlock"
-The privileged dotlocking program.
-.IP "/usr/share/doc/mutt/manual.txt.gz"
-The Mutt manual.
-.SH BUGS
-.PP
-None. Mutts have fleas, not bugs.
-.SH FLEAS
-.PP
-Suspend/resume while editing a file with an external editor does not work
-under SunOS 4.x if you use the curses lib in /usr/5lib. It \fIdoes\fP work
-with the S-Lang library, however.
-.PP
-Resizing the screen while using an external pager causes Mutt to go haywire
-on some systems.
-.PP
-Suspend/resume does not work under Ultrix.
-.PP
-The help line for the index menu is not updated if you change the bindings
-for one of the functions listed while Mutt is running.
-.PP
-For a more up-to-date list of bugs, errm, fleas, please visit the
-mutt project's bug tracking system under http://bugs.mutt.org/.
-.SH NO WARRANTIES
-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.
-.SH SEE ALSO
-.PP
-.BR curses (3),
-.BR mailcap (5),
-.BR maildir (5),
-.BR mbox (5),
-.BR mutt_dotlock (1),
-.BR muttrc (5),
-.BR ncurses (3),
-.BR sendmail (1),
-.BR smail (1).
-.PP
-Mutt Home Page: http://www.mutt.org/
-.PP
-The Mutt manual
-.SH AUTHOR
-.PP
-Michael Elkins, and others. Use <mutt-dev@mutt.org> to contact
-the developers.
+++ /dev/null
-'\" t
-.\" -*-nroff-*-
-.\"
-.\" Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu>
-.\" Copyright (C) 1999-2000 Thomas Roessler <roessler@does-not-exist.org>
-.\"
-.\" This program is free software; you can redistribute it and/or modify
-.\" it under the terms of the GNU General Public License as published by
-.\" the Free Software Foundation; either version 2 of the License, or
-.\" (at your option) any later version.
-.\"
-.\" This program is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-.\"
-.TH muttrc 5 "September 2002" Unix "User Manuals"
-.SH NAME
-muttrc \- Configuration file for the Mutt Mail User Agent
-.SH DESCRIPTION
-.PP
-A mutt configuration file consists of a series of \(lqcommands\(rq.
-Each line of the file may contain one or more commands. When
-multiple commands are used, they must be separated by a semicolon
-(\(lq\fB;\fP\(rq).
-.PP
-The hash mark, or pound sign (\(lq\fB#\fP\(rq), is used as a
-\(lqcomment\(rq character. You can use it to annotate your
-initialization file. All text after the comment character to the end
-of the line is ignored.
-.PP
-Single quotes (\(lq\fB'\fP\(rq) and double quotes (\(lq\fB"\fP\(rq)
-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 which
-should be evaluated. For example, backticks are evaluated inside of
-double quotes, but not single quotes.
-.PP
-\fB\(rs\fP quotes the next character, just as in shells such as bash and zsh.
-For example, if want to put quotes (\(lq\fB"\fP\(rq) inside of a
-string, you can use \(lq\fB\(rs\fP\(rq to force the next character
-to be a literal instead of interpreted character.
-.PP
-\(lq\fB\(rs\(rs\fP\(rq means to insert a literal \(lq\fB\(rs\fP\(rq into the
-line. \(lq\fB\(rsn\fP\(rq and \(lq\fB\(rsr\fP\(rq have their usual
-C meanings of linefeed and carriage-return, respectively.
-.PP
-A \(lq\fB\(rs\fP\(rq 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.
-.PP
-It is also possible to substitute the output of a Unix command in an
-initialization file. This is accomplished by enclosing the command
-in backticks (\fB`\fP\fIcommand\fP\fB`\fP).
-.PP
-UNIX environment variables can be accessed like the way it is done in shells
-like sh and bash: Prepend the name of the variable by a dollar
-(\(lq\fB\(Do\fP\(rq) sign.
-.PP
-.SH COMMANDS
-.PP
-.nf
-\fBalias\fP [\fB-group\fP \fIname\fP [...]] \fIkey\fP \fIaddress\fP [\fB,\fP \fIaddress\fP [ ... ]]
-\fBunalias\fP [\fB * \fP | \fIkey\fP ]
-.fi
-.IP
-\fBalias\fP defines an alias \fIkey\fP for the given addresses. Each
-\fIaddress\fP will be resolved into either an email address (user@example.com)
-or a named email address (User Name <user@example.com>). The address may be specified in either format, or in the format \(lquser@example.com (User
-Name)\(rq.
-\fBunalias\fP removes the alias corresponding to the given \fIkey\fP or
-all aliases when \(lq\fB*\fP\(rq is used as an argument. The optional
-\fB-group\fP argument to \fBalias\fP causes the aliased address(es) to be
-added to the named \fIgroup\fP.
-.PP
-.nf
-\fBgroup\fP [\fB-group\fP \fIname\fP] [\fB-rx\fP \fIEXPR\fP [ \fI...\fP ]] [\fB-addr\fP \fIaddress\fP [ \fI...\fP ]]
-\fBungroup\fP [\fB-group\fP \fIname\fP ] [ \fB*\fP | [[\fB-rx\fP \fIEXPR\fP [ \fI...\fP ]] [\fB-addr\fP \fIaddress\fP [ \fI...\fP ]]]
-.fi
-.IP
-\fBgroup\fP is used to directly add either addresses or regular expressions to
-the specified group or groups. The different categories of arguments to the
-\fBgroup\fP command can be in any order. The flags \fI-rx\fP and \fI-addr\fP
-specify what the following strings (that cannot begin with a hyphen) should be
-interpreted as: either a regular expression or an email address, respectively.
-\fBungroup\fP is used to remove addresses or regular expressions from the
-specified group or groups. The syntax is similar to the \fBgroup\fP command,
-however the special character \fB*\fP can be used to empty a group of all of
-its contents.
-.IP
-These address groups can also be created implicitly by the \fBalias\fP, \fBlists\fP,
-\fBsubscribe\fP and \fBalternates\fP commands by specifying the optional \fI-group\fP
-option.
-.IP
-Once defined, these address groups can be used in patterns to search for and limit the
-display to messages matching a group.
-.PP
-.nf
-\fBalternates\fP [\fB-group\fP \fIname\fP] \fIregexp\fP [ \fB,\fP \fIregexp\fP [ ... ]]
-\fBunalternates\fP [\fB * \fP | \fIregexp\fP [ \fB,\fP \fIregexp\fP [ ... ]] ]
-.fi
-.IP
-\fBalternates\fP is used to inform mutt about alternate addresses
-where you receive mail; you can use regular expressions to specify
-alternate addresses. This affects mutt's idea about messages
-from you, and messages addressed to you. \fBunalternates\fP removes
-a regular expression from the list of known alternates. The \fB-group\fP flag
-causes all of the subsequent regular expressions to be added to the named group.
-.PP
-.nf
-\fBalternative_order\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-\fBunalternative_order\fP [\fB * \fP | \fItype\fP/\fIsubtype\fP] [...]
-.fi
-.IP
-\fBalternative_order\fP command permits you to define an order of preference which is
-used by mutt to determine which part of a
-\fBmultipart/alternative\fP body to display.
-A subtype of \(lq\fB*\fP\(rq matches any subtype, as does an empty
-subtype. \fBunalternative_order\fP removes entries from the
-ordered list or deletes the entire list when \(lq\fB*\fP\(rq is used
-as an argument.
-.PP
-.nf
-\fBauto_view\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-\fBunauto_view\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-.fi
-.IP
-This commands permits you to specify that mutt should automatically
-convert the given MIME types to text/plain when displaying messages.
-For this to work, there must be a
-.BR mailcap (5)
-entry for the given MIME type with the
-.B copiousoutput
-flag set. A subtype of \(lq\fB*\fP\(rq
-matches any subtype, as does an empty subtype.
-.PP
-.nf
-\fBmime_lookup\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-\fBunmime_lookup\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ]
-.fi
-.IP
-This command permits you to define a list of "data" MIME content
-types for which mutt will try to determine the actual file type from
-the file name, and not use a
-.BR mailcap (5)
-entry given for the original MIME type. For instance, you may add
-the \fBapplication/octet-stream\fP MIME type to this list.
-.TP
-\fBbind\fP \fImap1,map2,...\fP \fIkey\fP \fIfunction\fP
-This command binds the given \fIkey\fP for the given \fImap\fP or maps
-to the given \fIfunction\fP. Multiple maps may be specified by
-separating them with commas (no whitespace is allowed).
-.IP
-Valid maps are:
-.BR generic ", " alias ", " attach ", "
-.BR browser ", " editor ", "
-.BR index ", " compose ", "
-.BR pager ", " pgp ", " postpone ", "
-.BR mix .
-.IP
-For more information on keys and functions, please consult the Mutt
-Manual.
-.TP
-\fBaccount-hook\fP [\fB!\fP]\fIregexp\fP \fIcommand\fP
-This hook is executed whenever you access a remote mailbox. Useful
-to adjust configuration settings to different IMAP or POP servers.
-.TP
-\fBcharset-hook\fP \fIalias\fP \fIcharset\fP
-This 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.
-.TP
-\fBiconv-hook\fP \fIcharset\fP \fIlocal-charset\fP
-This command defines a system-specific name for a character set.
-This is useful when your system's
-.BR iconv (3)
-implementation does not understand MIME character set names (such as
-.BR iso-8859-1 ),
-but instead insists on being fed with implementation-specific
-character set names (such as
-.BR 8859-1 ).
-In this specific case, you'd put this into your configuration file:
-.IP
-.B "iconv-hook iso-8859-1 8859-1"
-.TP
-\fBmessage-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP
-Before mutt displays (or formats for replying or forwarding) a
-message which matches the given \fIpattern\fP (or, when it is
-preceded by an exclamation mark, does not match the \fIpattern\fP),
-the given \fIcommand\fP is executed. When multiple
-\fBmessage-hook\fPs match, they are executed in the order in
-which they occur in the configuration file.
-.TP
-\fBfolder-hook\fP [\fB!\fP]\fIregexp\fP \fIcommand\fP
-When mutt enters a folder which matches \fIregexp\fP (or, when
-\fIregexp\fP is preceded by an exclamation mark, does not match
-\fIregexp\fP), the given \fIcommand\fP is executed.
-.IP
-When several \fBfolder-hook\fPs match a given mail folder, they are
-executed in the order given in the configuration file.
-.TP
-\fBmacro\fP \fImap\fP \fIkey\fP \fIsequence\fP [ \fIdescription\fP ]
-This command binds the given \fIsequence\fP of keys to the given
-\fIkey\fP in the given \fImap\fP or maps. For valid maps, see \fBbind\fP. To
-specify multiple maps, put only a comma between the maps.
-.PP
-.nf
-\fBcolor\fP \fIobject\fP \fIforeground\fP \fIbackground\fP [ \fI regexp\fP ]
-\fBcolor\fP index \fIforeground\fP \fIbackground\fP [ \fI pattern\fP ]
-\fBuncolor\fP index \fIpattern\fP [ \fIpattern\fP ... ]
-.fi
-.IP
-If your terminal supports color, these commands can be used to
-assign \fIforeground\fP/\fIbackground\fP combinations to certain
-objects. Valid objects are:
-.BR attachment ", " body ", " bold ", " header ", "
-.BR hdrdefault ", " index ", " indicator ", " markers ", "
-.BR message ", " normal ", " quoted ", " quoted\fIN\fP ", "
-.BR search ", " signature ", " status ", " tilde ", " tree ", "
-.BR underline .
-The
-.BR body " and " header
-objects allow you to restrict the colorization to a regular
-expression. The \fBindex\fP object permits you to select colored
-messages by pattern.
-.IP
-Valid colors include:
-.BR white ", " black ", " green ", " magenta ", " blue ", "
-.BR cyan ", " yellow ", " red ", " default ", " color\fIN\fP .
-.PP
-.nf
-\fBmono\fP \fIobject\fP \fIattribute\fP [ \fIregexp\fP ]
-\fBmono\fP index \fIattribute\fP [ \fIpattern\fP ]
-.fi
-.IP
-For terminals which don't support color, you can still assign
-attributes to objects. Valid attributes include:
-.BR none ", " bold ", " underline ", "
-.BR reverse ", and " standout .
-.TP
-[\fBun\fP]\fBignore\fP \fIpattern\fP [ \fIpattern\fP ... ]
-The \fBignore\fP command permits you to specify header fields which
-you usually don't wish to see. Any header field whose tag
-\fIbegins\fP with an \(lqignored\(rq pattern will be ignored.
-.IP
-The \fBunignore\fP command permits you to define exceptions from
-the above mentioned list of ignored headers.
-.PP
-.nf
-\fBlists\fP [\fB-group\fP \fIname\fP] \fIregexp\fP [ \fIregexp\fP ... ]
-\fBunlists\fP \fIregexp\fP [ \fIregexp\fP ... ]
-\fBsubscribe\fP [\fB-group\fP \fIname\fP] \fIregexp\fP [ \fIregexp\fP ... ]
-\fBunsubscribe\fP \fIregexp\fP [ \fIregexp\fP ... ]
-.fi
-.IP
-Mutt maintains two lists of mailing list address patterns, a list of
-subscribed mailing lists, and a list of known mailing lists. All
-subscribed mailing lists are known. Patterns use regular expressions.
-.IP
-The \fBlists\fP command adds a mailing list address to the list of
-known mailing lists. The \fBunlists\fP command removes a mailing
-list from the lists of known and subscribed mailing lists. The
-\fBsubscribe\fP command adds a mailing list to the lists of known
-and subscribed mailing lists. The \fBunsubscribe\fP command removes
-it from the list of subscribed mailing lists. The \fb-group\fP flag
-adds all of the subsequent regular expressions to the named group.
-.TP
-\fBmbox-hook\fP [\fB!\fP]\fIpattern\fP \fImailbox\fP
-When mutt changes to a mail folder which matches \fIpattern\fP,
-\fImailbox\fP will be used as the \(lqmbox\(rq folder, i.e., read
-messages will be moved to that folder when the mail folder is left.
-.IP
-The first matching \fBmbox-hook\fP applies.
-.PP
-.nf
-\fBmailboxes\fP \fIfilename\fP [ \fIfilename\fP ... ]
-\fBunmailboxes\fP [ \fB*\fP | \fIfilename\fP ... ]
-.fi
-.IP
-The \fBmailboxes\fP specifies folders which can receive mail and which will
-be checked for new messages. When changing folders, pressing space
-will cycle through folders with new mail. The \fBunmailboxes\fP
-command is used to remove a file name from the list of folders which
-can receive mail. If "\fB*\fP" is specified as the file name, the
-list is emptied.
-.PP
-.nf
-\fBmy_hdr\fP \fIstring\fP
-\fBunmy_hdr\fP \fIfield\fP
-.fi
-.IP
-Using \fBmy_hdr\fP, you can define headers which will be added to
-the messages you compose. \fBunmy_hdr\fP will remove the given
-user-defined headers.
-.TP
-\fBhdr_order\fP \fIheader1\fP \fIheader2\fP [ ... ]
-With this command, you can specify an order in which mutt will
-attempt to present headers to you when viewing messages.
-.TP
-\fBsave-hook\fP [\fB!\fP]\fIpattern\fP \fIfilename\fP
-When a message matches \fIpattern\fP, the default file name when
-saving it will be the given \fIfilename\fP.
-.TP
-\fBfcc-hook\fP [\fB!\fP]\fIpattern\fP \fIfilename\fP
-When an outgoing message matches \fIpattern\fP, the default file
-name for storing a copy (fcc) will be the given \fIfilename\fP.
-.TP
-\fBfcc-save-hook\fP [\fB!\fP]\fIpattern\fP \fIfilename\fP
-This command is an abbreviation for identical \fBfcc-hook\fP and
-\fBsave-hook\fP commands.
-.TP
-\fBsend-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP
-When composing a message matching \fIpattern\fP, \fIcommand\fP is
-executed. When multiple \fBsend-hook\fPs match, they are executed
-in the order in which they occur in the configuration file.
-.TP
-\fBsend2-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP
-Whenever a message matching \fIpattern\fP is changed (either by
-editing it or by using the compose menu), \fIcommand\fP
-is executed. When multiple \fBsend2-hook\fPs match, they are
-executed in the order in which they occur in the configuration file.
-Possible applications include setting the $sendmail variable when a
-message's from header is changed.
-.IP
-\fBsend2-hook\fP execution is not triggered by use of
-\fBenter-command\fP from the compose menu.
-.TP
-\fBreply-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP
-When replying to a message matching \fIpattern\fP, \fIcommand\fP is
-executed. When multiple \fBreply-hook\fPs match, they are executed
-in the order in which they occur in the configuration file, but all
-\fBreply-hook\fPs are matched and executed before \fBsend-hook\fPs,
-regardless of their order in the configuration file.
-.TP
-\fBcrypt-hook\fP \fIpattern\fP \fIkey-id\fP
-The crypt-hook command provides a method by which you can
-specify the ID of the public key to be used when encrypting messages
-to a certain recipient. The meaning of "key ID" is to be taken
-broadly: This can be a different e-mail address, a numerical key ID,
-or even just an arbitrary search string.
-.PP
-.nf
-\fBopen-hook\fP \fIregexp\fP "\fIcommand\fP"
-\fBclose-hook\fP \fIregexp\fP "\fIcommand\fP"
-\fBappend-hook\fP \fIregexp\fP "\fIcommand\fP"
-.fi
-.IP
-These commands provide a way to handle compressed folders. The given
-\fBregexp\fP specifies which folders are taken as compressed (e.g.
-"\fI\\\\.gz$\fP"). The commands tell Mutt how to uncompress a folder
-(\fBopen-hook\fP), compress a folder (\fBclose-hook\fP) or append a
-compressed mail to a compressed folder (\fBappend-hook\fP). The
-\fIcommand\fP string is the
-.BR printf (3)
-like format string, and it should accept two parameters: \fB%f\fP,
-which is replaced with the (compressed) folder name, and \fB%t\fP
-which is replaced with the name of the temporary folder to which to
-write.
-.TP
-\fBpush\fP \fIstring\fP
-This command adds the named \fIstring\fP to the keyboard buffer.
-.PP
-.nf
-\fBset\fP [\fBno\fP|\fBinv\fP|\fB&\fP|\fB?\fP]\fIvariable\fP[=\fIvalue\fP] [ ... ]
-\fBtoggle\fP \fIvariable\fP [ ... ]
-\fBunset\fP \fIvariable\fP [ ... ]
-\fBreset\fP \fIvariable\fP [ ... ]
-.fi
-.IP
-These commands are used to set and manipulate configuration
-variables.
-.IP
-Mutt knows four basic types of variables: boolean, number, string
-and quadoption. Boolean variables can be \fBset\fP (true),
-\fBunset\fP (false), or \fBtoggle\fPd. Number variables can be assigned
-a positive integer value.
-.IP
-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 \(lqC\(rq escape sequences \fB\\n\fP and
-\fB\\t\fP for newline and tab, respectively.
-.IP
-Quadoption variables are used to control whether or not to be
-prompted for certain actions, or to specify a default action. A
-value of \fByes\fP will cause the action to be carried out automatically
-as if you had answered yes to the question. Similarly, a value of
-\fBno\fP will cause the the action to be carried out as if you had
-answered \(lqno.\(rq A value of \fBask-yes\fP will cause a prompt
-with a default answer of \(lqyes\(rq and \fBask-no\fP will provide a
-default answer of \(lqno.\(rq
-.IP
-The \fBreset\fP command resets all given variables to the compile
-time defaults. If you reset the special variable \fBall\fP, all
-variables will reset to their compile time defaults.
-.TP
-\fBsource\fP \fIfilename\fP
-The given file will be evaluated as a configuration file.
-.TP
-.nf
-\fBspam\fP \fIpattern\fP \fIformat\fP
-\fBnospam\fP \fIpattern\fP
-.fi
-These commands define spam-detection patterns from external spam
-filters, so that mutt can sort, limit, and search on
-``spam tags'' or ``spam attributes'', or display them
-in the index. See the Mutt manual for details.
-.TP
-\fBunhook\fP [\fB * \fP | \fIhook-type\fP ]
-This command will remove all hooks of a given type, or all hooks
-when \(lq\fB*\fP\(rq is used as an argument. \fIhook-type\fP
-can be any of the \fB-hook\fP commands documented above.
-.SH PATTERNS
-.PP
-In various places with mutt, including some of the abovementioned
-\fBhook\fP commands, you can specify patterns to match messages.
-.SS Constructing Patterns
-.PP
-A simple pattern consists of an operator of the form
-\(lq\fB~\fP\fIcharacter\fP\(rq, possibly followed by a parameter
-against which mutt is supposed to match the object specified by
-this operator. For some \fIcharacter\fPs, the \fB~\fP may be
-replaced by another character to alter the behavior of the match.
-These are described in the list of operators, below.
-.PP
-With some of these operators, the object to be matched consists of
-several e-mail addresses. In these cases, the object is matched if
-at least one of these e-mail addresses matches. You can prepend a
-hat (\(lq\fB^\fP\(rq) character to such a pattern to indicate that
-\fIall\fP addresses must match in order to match the object.
-.PP
-You can construct complex patterns by combining simple patterns with
-logical operators. Logical AND is specified by simply concatenating
-two simple patterns, for instance \(lq~C mutt-dev ~s bug\(rq.
-Logical OR is specified by inserting a vertical bar (\(lq\fB|\fP\(rq)
-between two patterns, for instance \(lq~C mutt-dev | ~s bug\(rq.
-Additionally, you can negate a pattern by prepending a bang
-(\(lq\fB!\fP\(rq) character. For logical grouping, use braces
-(\(lq()\(rq). Example: \(lq!(~t mutt|~c mutt) ~f elkins\(rq.
-.SS Simple Patterns
-.PP
-Mutt understands the following simple patterns:
-.P
-.PD 0
-.TP 12
-~A
-all messages
-.TP
-~b \fIEXPR\fP
-messages which contain \fIEXPR\fP in the message body.
-.TP
-=b \fISTRING\fP
-messages which contain \fISTRING\fP in the message body. If IMAP is enabled, searches for \fISTRING\fP on the server, rather than downloading each message and searching it locally.
-.TP
-~B \fIEXPR\fP
-messages which contain \fIEXPR\fP in the whole message.
-.TP
-~c \fIEXPR\fP
-messages carbon-copied to \fIEXPR\fP
-.TP
-%c \fIGROUP\fP
-messages carbon-copied to any member of \fIGROUP\fP
-.TP
-~C \fIEXPR\fP
-messages either to: or cc: \fIEXPR\fP
-.TP
-%C \fIGROUP\fP
-messages either to: or cc: to any member of \fIGROUP\fP
-.TP
-~d \fIMIN\fP-\fIMAX\fP
-messages with \(lqdate-sent\(rq in a Date range
-.TP
-~D
-deleted messages
-.TP
-~e \fIEXPR\fP
-messages which contain \fIEXPR\fP in the \(lqSender\(rq field
-.TP
-%e \fIGROUP\fP
-messages which contain a member of \fIGROUP\fP in the \(lqSender\(rq field
-.TP
-~E
-expired messages
-.TP
-~f \fIEXPR\fP
-messages originating from \fIEXPR\fP
-.TP
-%f \fIGROUP\fP
-messages originating form any member of \fIGROUP\fP
-.TP
-~F
-flagged messages
-.TP
-~g
-PGP signed messages
-.TP
-~G
-PGP encrypted messages
-.TP
-~h \fIEXPR\fP
-messages which contain \fIEXPR\fP in the message header
-.TP
-~H \fIEXPR\fP
-messages with spam tags matching \fIEXPR\fP
-.TP
-~i \fIEXPR\fP
-messages which match \fIEXPR\fP in the \(lqMessage-ID\(rq field
-.TP
-~k
-messages containing PGP key material
-.TP
-~l
-messages addressed to a known mailing list (defined by either \fBsubscribe\fP or \fBlist\fP)
-.TP
-~L \fIEXPR\fP
-messages either originated or received by \fIEXPR\fP
-.TP
-%L \fIGROUP\fP
-messages either originated or received by any member of \fIGROUP\fP
-.TP
-~m \fIMIN\fP-\fIMAX\fP
-message in the range \fIMIN\fP to \fIMAX\fP
-.TP
-~n \fIMIN\fP-\fIMAX\fP
-messages with a score in the range \fIMIN\fP to \fIMAX\fP
-.TP
-~N
-new messages
-.TP
-~O
-old messages
-.TP
-~p
-messages addressed to you (as defined by \fBalternates\fP)
-.TP
-~P
-messages from you (as defined by \fBalternates\fP)
-.TP
-~Q
-messages which have been replied to
-.TP
-~r \fIMIN\fP-\fIMAX\fP
-messages with \(lqdate-received\(rq in a Date range
-.TP
-~R
-read messages
-.TP
-~s \fIEXPR\fP
-messages having \fIEXPR\fP in the \(lqSubject\(rq field.
-.TP
-~S
-superseded messages
-.TP
-~t \fIEXPR\fP
-messages addressed to \fIEXPR\fP
-.TP
-~T
-tagged messages
-.TP
-~u
-messages addressed to a subscribed mailing list (defined by \fBsubscribe\fP commands)
-.TP
-~U
-unread messages
-.TP
-~v
-message is part of a collapsed thread.
-.TP
-~V
-cryptographically verified messages
-.TP
-~x \fIEXPR\fP
-messages which contain \fIEXPR\fP in the \(lqReferences\(rq field
-.TP
-~X \fIMIN\fP-\fIMAX\fP
-messages with MIN - MAX attachments
-.TP
-~y \fIEXPR\fP
-messages which contain \fIEXPR\fP in the \(lqX-Label\(rq field
-.TP
-~z \fIMIN\fP-\fIMAX\fP
-messages with a size in the range \fIMIN\fP to \fIMAX\fP
-.TP
-~=
-duplicated messages (see $duplicate_threads)
-.TP
-~$
-unreferenced message (requires threaded view)
-.TP
-~(PATTERN)
-messages in threads containing messages matching a certain pattern, e.g. all threads containing messages from you: ~(~P)
-.PD 1
-.DT
-.PP
-In the above, \fIEXPR\fP is a regular expression.
-.PP
-With the \fB~m\fP, \fB~n\fP, \fB~X\fP, and \fB~z\fP operators, you can also
-specify ranges in the forms \fB<\fP\fIMAX\fP, \fB>\fP\fIMIN\fP,
-\fIMIN\fP\fB-\fP, and \fB-\fP\fIMAX\fP.
-.SS Matching dates
-.PP
-The \fB~d\fP and \fB~r\fP operators are used to match date ranges,
-which are interpreted to be given in your local time zone.
-.PP
-A date is of the form
-\fIDD\fP[\fB/\fP\fIMM\fP[\fB/\fP[\fIcc\fP]\fIYY\fP]], that is, a
-two-digit date, optionally followed by a two-digit month, optionally
-followed by a year specifications. Omitted fields default to the
-current month and year.
-.PP
-Mutt understands either two or four digit year specifications. When
-given a two-digit year, mutt will interpret values less than 70 as
-lying in the 21st century (i.e., \(lq38\(rq means 2038 and not 1938,
-and \(lq00\(rq is interpreted as 2000), and values
-greater than or equal to 70 as lying in the 20th century.
-.PP
-Note that this behaviour \fIis\fP Y2K compliant, but that mutt
-\fIdoes\fP have a Y2.07K problem.
-.PP
-If a date range consists of a single date, the operator in question
-will match that precise date. If the date range consists of a dash
-(\(lq\fB-\fP\(rq), followed by a date, this range will match any
-date before and up to the date given. Similarly, a date followed by
-a dash matches the date given and any later point of time. Two
-dates, separated by a dash, match any date which lies in the given
-range of time.
-.PP
-You can also modify any absolute date by giving an error range. An
-error range consists of one of the characters
-.BR + ,
-.BR - ,
-.BR * ,
-followed by a positive number, followed by one of the unit
-characters
-.BR y ,
-.BR m ,
-.BR w ", or"
-.BR d ,
-specifying a unit of years, months, weeks, or days.
-.B +
-increases the maximum date matched by the given interval of time,
-.B -
-decreases the minimum date matched by the given interval of time, and
-.B *
-increases the maximum date and decreases the minimum date matched by
-the given interval of time. It is possible to give multiple error
-margins, which cumulate. Example:
-.B "1/1/2001-1w+2w*3d"
-.PP
-You can also specify offsets relative to the current date. An
-offset is specified as one of the characters
-.BR < ,
-.BR > ,
-.BR = ,
-followed by a positive number, followed by one of the unit
-characters
-.BR y ,
-.BR m ,
-.BR w ", or"
-.BR d .
-.B >
-matches dates which are older than the specified amount of time, an
-offset which begins with the character
-.B <
-matches dates which are more recent than the specified amount of time,
-and an offset which begins with the character
-.B =
-matches points of time which are precisely the given amount of time
-ago.
-.SH CONFIGURATION VARIABLES
-
-.TP
-.B abort_nosubject
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-If set to \fIyes\fP, when composing messages and no subject is given
-at the subject prompt, composition will be aborted. If set to
-\fIno\fP, composing messages with no subject given at the subject
-prompt will never be aborted.
-
-
-.TP
-.B abort_unmodified
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-If set to \fIyes\fP, composition will automatically abort after
-editing the message body if no changes are made to the file (this
-check only happens after the \fIfirst\fP edit of the file). When set
-to \fIno\fP, composition will never be aborted.
-
-
-.TP
-.B alias_file
-.nf
-Type: path
-Default: \(lq~/.muttrc\(rq
-.fi
-.IP
-The default file in which to save aliases created by the
-\fC<create-alias>\fP function. Entries added to this file are
-encoded in the character set specified by $config_charset if it
-is \fIset\fP or the current character set otherwise.
-.IP
-\fBNote:\fP Mutt will not automatically source this file; you must
-explicitly use the \(lqsource\(rq command for it to be executed in case
-this option points to a dedicated alias file.
-.IP
-The default for this option is the currently used muttrc file, or
-\(lq~/.muttrc\(rq if no user muttrc was found.
-
-
-.TP
-.B alias_format
-.nf
-Type: string
-Default: \(lq%4n %2f %t %\-10a %r\(rq
-.fi
-.IP
-Specifies the format of the data displayed for the \(lqalias\(rq menu. The
-following \fCprintf(3)\fP\-style sequences are available:
-.RS
-.PD 0
-.TP
-%a
-alias name
-.TP
-%f
-flags \- currently, a \(lqd\(rq for an alias marked for deletion
-.TP
-%n
-index number
-.TP
-%r
-address which alias expands to
-.TP
-%t
-character which indicates if the alias is tagged for inclusion
-.RE
-.PD 1
-
-.TP
-.B allow_8bit
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether 8\-bit data is converted to 7\-bit using either Quoted\-
-Printable or Base64 encoding when sending mail.
-
-
-.TP
-.B allow_ansi
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-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 \fIset\fP,
-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
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-[\-\- PGP output follows ...
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-and give it the same color as your attachment color (see also
-$crypt_timestamp).
-
-
-.TP
-.B arrow_cursor
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, an arrow (\(lq\->\(rq) 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.
-
-
-.TP
-.B ascii_chars
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, Mutt will use plain ASCII characters when displaying thread
-and attachment trees, instead of the default \fIACS\fP characters.
-
-
-.TP
-.B askbcc
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, Mutt will prompt you for blind\-carbon\-copy (Bcc) recipients
-before editing an outgoing message.
-
-
-.TP
-.B askcc
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, Mutt will prompt you for carbon\-copy (Cc) recipients before
-editing the body of an outgoing message.
-
-
-.TP
-.B assumed_charset
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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 \(lqus\-ascii\(rq.
-.IP
-For example, Japanese users might prefer this:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set assumed_charset=\(rqiso\-2022\-jp:euc\-jp:shift_jis:utf\-8\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-However, only the first content is valid for the message body.
-
-
-.TP
-.B attach_charset
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This variable is a colon\-separated list of character encoding
-schemes for text file attachments. Mutt uses this setting to guess
-which encoding files being attached are encoded in to convert them to
-a proper character set given in $send_charset.
-.IP
-If \fIunset\fP, the value of $charset will be used instead.
-For example, the following configuration would work for Japanese
-text handling:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set attach_charset=\(rqiso\-2022\-jp:euc\-jp:shift_jis:utf\-8\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-Note: for Japanese users, \(lqiso\-2022\-*\(rq must be put at the head
-of the value as shown above if included.
-
-
-.TP
-.B attach_format
-.nf
-Type: string
-Default: \(lq%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] \(rq
-.fi
-.IP
-This variable describes the format of the \(lqattachment\(rq menu. The
-following \fCprintf(3)\fP\-style sequences are understood:
-.RS
-.PD 0
-.TP
-%C
-charset
-.TP
-%c
-requires charset conversion (\(lqn\(rq or \(lqc\(rq)
-.TP
-%D
-deleted flag
-.TP
-%d
-description
-.TP
-%e
-MIME content\-transfer\-encoding
-.TP
-%f
-filename
-.TP
-%I
-disposition (\(lqI\(rq for inline, \(lqA\(rq for attachment)
-.TP
-%m
-major MIME type
-.TP
-%M
-MIME subtype
-.TP
-%n
-attachment number
-.TP
-%Q
-\(lqQ\(rq, if MIME part qualifies for attachment counting
-.TP
-%s
-size
-.TP
-%t
-tagged flag
-.TP
-%T
-graphic tree characters
-.TP
-%u
-unlink (=to delete) flag
-.TP
-%X
-number of qualifying MIME parts in this part and its children
-(please see the \(lqattachments\(rq section for possible speed effects)
-.TP
-%>X
-right justify the rest of the string and pad with character \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with character \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-For an explanation of \(lqsoft\-fill\(rq, see the $index_format documentation.
-
-
-.TP
-.B attach_sep
-.nf
-Type: string
-Default: \(lq\\n\(rq
-.fi
-.IP
-The separator to add between attachments when operating (saving,
-printing, piping, etc) on a list of tagged attachments.
-
-
-.TP
-.B attach_split
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If this variable is \fIunset\fP, when operating (saving, printing, piping,
-etc) on a list of tagged attachments, Mutt will concatenate the
-attachments and will operate on them as a single attachment. The
-$attach_sep separator is added after each attachment. When \fIset\fP,
-Mutt will operate on the attachments one by one.
-
-
-.TP
-.B attribution
-.nf
-Type: string
-Default: \(lqOn %d, %n wrote:\(rq
-.fi
-.IP
-This is the string that will precede a message which has been included
-in a reply. For a full listing of defined \fCprintf(3)\fP\-like sequences see
-the section on $index_format.
-
-
-.TP
-.B autoedit
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP along with $edit_headers, Mutt will skip the initial
-send\-menu (prompting for subject and recipients) 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.
-.IP
-Also see $fast_reply.
-
-
-.TP
-.B auto_tag
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, functions in the \fIindex\fP menu which affect a message
-will be applied to all tagged messages (if there are any). When
-unset, you must first use the \fC<tag\-prefix>\fP function (bound to \(lq;\(rq
-by default) to make the next function apply to all tagged messages.
-
-
-.TP
-.B beep
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When this variable is \fIset\fP, mutt will beep when an error occurs.
-
-
-.TP
-.B beep_new
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, mutt will beep whenever it prints a message
-notifying you of new mail. This is independent of the setting of the
-$beep variable.
-
-
-.TP
-.B bounce
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether you will be asked to confirm bouncing messages.
-If set to \fIyes\fP you don't get asked if you want to bounce a
-message. Setting this variable to \fIno\fP is not generally useful,
-and thus not recommended, because you are unable to bounce messages.
-
-
-.TP
-.B bounce_delivered
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When this variable is \fIset\fP, mutt will include Delivered\-To headers when
-bouncing messages. Postfix users may wish to \fIunset\fP this variable.
-.IP
-\fBNote:\fP On Debian systems, this option is unset by default in
-/etc/Muttrc.
-
-
-.TP
-.B braille_friendly
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, mutt will place the cursor at the beginning
-of the current line in menus, even when the $arrow_cursor variable
-is \fIunset\fP, making it easier for blind persons using Braille displays to
-follow these menus. The option is \fIunset\fP by default because many
-visual terminals don't permit making the cursor invisible.
-
-
-.TP
-.B check_mbox_size
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
-.IP
-This variable is \fIunset\fP by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
-.IP
-Note that enabling this variable should happen before any \(lqmailboxes\(rq
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-
-
-.TP
-.B charset
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Character set your terminal uses to display and enter textual data.
-It is also the fallback for $send_charset.
-.IP
-Upon startup Mutt tries to derive this value from environment variables
-such as \fC$LC_CTYPE\fP or \fC$LANG\fP.
-.IP
-\fBNote:\fP It should only be set in case Mutt isn't abled to determine the
-character set used correctly.
-
-
-.TP
-.B check_new
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-\fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
-mailboxes.
-.IP
-When \fIset\fP, Mutt 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
-this variable is \fIunset\fP, no check for new mail is performed
-while the mailbox is open.
-
-
-.TP
-.B collapse_unread
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, Mutt will not collapse a thread if it contains any
-unread messages.
-
-
-.TP
-.B uncollapse_jump
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, Mutt will jump to the next unread message, if any,
-when the current thread is \fIun\fPcollapsed.
-
-
-.TP
-.B compose_format
-.nf
-Type: string
-Default: \(lq\-\- Mutt: Compose [Approx. msg size: %l Atts: %a]%>\-\(rq
-.fi
-.IP
-Controls the format of the status line displayed in the \(lqcompose\(rq
-menu. This string is similar to $status_format, but has its own
-set of \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%a
-total number of attachments
-.TP
-%h
-local hostname
-.TP
-%l
-approximate size (in bytes) of the current message
-.TP
-%v
-Mutt version string
-.RE
-.PD 1
-.IP
-See the text describing the $status_format option for more
-information on how to set $compose_format.
-
-
-.TP
-.B config_charset
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-When defined, Mutt will recode commands in rc files from this
-encoding to the current character set as specified by $charset
-and aliases written to $alias_file from the current character set.
-.IP
-Please note that if setting $charset it must be done before
-setting $config_charset.
-.IP
-Recoding should be avoided as it may render unconvertable
-characters as question marks which can lead to undesired
-side effects (for example in regular expressions).
-
-
-.TP
-.B confirmappend
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will prompt for confirmation when appending messages to
-an existing mailbox.
-
-
-.TP
-.B confirmcreate
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will prompt for confirmation when saving messages to a
-mailbox which does not yet exist before creating it.
-
-
-.TP
-.B connect_timeout
-.nf
-Type: number
-Default: 30
-.fi
-.IP
-Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-many seconds if the connection is not able to be established. A negative
-value causes Mutt to wait indefinitely for the connection attempt to succeed.
-
-
-.TP
-.B content_type
-.nf
-Type: string
-Default: \(lqtext/plain\(rq
-.fi
-.IP
-Sets the default Content\-Type for the body of newly composed messages.
-
-
-.TP
-.B copy
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-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 \(lqfcc-hook\(rq.
-
-
-.TP
-.B crypt_use_gpgme
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable controls the use of the GPGME\-enabled crypto backends.
-If it is \fIset\fP and Mutt was built with gpgme support, the gpgme code for
-S/MIME and PGP will be used instead of the classic code. Note that
-you need to set this option in .muttrc; it won't have any effect when
-used interactively.
-
-
-.TP
-.B crypt_use_pka
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Controls whether mutt uses PKA
-(see http://www.g10code.de/docs/pka\-intro.de.pdf) during signature
-verification (only supported by the GPGME backend).
-
-
-.TP
-.B crypt_autopgp
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages. See also $crypt_autoencrypt,
-$crypt_replyencrypt,
-$crypt_autosign, $crypt_replysign and $smime_is_default.
-
-
-.TP
-.B crypt_autosmime
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also $crypt_autoencrypt,
-$crypt_replyencrypt,
-$crypt_autosign, $crypt_replysign and $smime_is_default.
-
-
-.TP
-.B date_format
-.nf
-Type: string
-Default: \(lq!%a, %b %d, %Y at %I:%M:%S%p %Z\(rq
-.fi
-.IP
-This variable controls the format of the date printed by the \(lq%d\(rq
-sequence in $index_format. This is passed to the \fCstrftime(3)\fP
-function to process the date, see the man page for the proper syntax.
-.IP
-Unless the first character in the string is a bang (\(lq!\(rq), 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 \fIC\fP locale (that is in US
-English).
-
-
-.TP
-.B default_hook
-.nf
-Type: string
-Default: \(lq~f %s !~P | (~P ~C %s)\(rq
-.fi
-.IP
-This variable controls how \(lqmessage-hook\(rq, \(lqreply-hook\(rq, \(lqsend-hook\(rq,
-\(lqsend2-hook\(rq, \(lqsave-hook\(rq, and \(lqfcc-hook\(rq 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.
-.IP
-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
-\(lqalternates\(rq) and is to or cc'ed to a user matching the given
-regular expression.
-
-
-.TP
-.B delete
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not messages are really deleted when closing or
-synchronizing a mailbox. If set to \fIyes\fP, messages marked for
-deleting will automatically be purged without prompting. If set to
-\fIno\fP, messages marked for deletion will be kept in the mailbox.
-
-
-.TP
-.B delete_untag
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If this option is \fIset\fP, mutt 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.
-
-
-.TP
-.B digest_collapse
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If this option is \fIset\fP, mutt's received\-attachments menu will not show the subparts of
-individual messages in a multipart/digest. To see these subparts, press \(lqv\(rq on that menu.
-
-
-.TP
-.B display_filter
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-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.
-
-
-.TP
-.B dotlock_program
-.nf
-Type: path
-Default: \(lq/usr/bin/mutt_dotlock\(rq
-.fi
-.IP
-Contains the path of the \fCmutt_dotlock(8)\fP binary to be used by
-mutt.
-
-
-.TP
-.B dsn_notify
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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: \fInever\fP, to never request notification,
-\fIfailure\fP, to request notification on transmission failure,
-\fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
-notified of successful transmission.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set dsn_notify=\(rqfailure,delay\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\fBNote:\fP when using $sendmail for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a \fCsendmail(1)\fP\-compatible interface supporting the \fC\-N\fP option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-
-
-.TP
-.B dsn_return
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This variable controls how much of your message is returned in DSN
-messages. It may be set to either \fIhdrs\fP to return just the
-message header, or \fIfull\fP to return the full message.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set dsn_return=hdrs
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\fBNote:\fP when using $sendmail for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a \fCsendmail(1)\fP\-compatible interface supporting the \fC\-R\fP option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-
-
-.TP
-.B duplicate_threads
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable controls whether mutt, when $sort is set to \fIthreads\fP, threads
-messages with the same Message\-Id together. If it is \fIset\fP, it will indicate
-that it thinks they are duplicates of each other with an equals sign
-in the thread tree.
-
-
-.TP
-.B edit_headers
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This option allows you to edit the header of your outgoing messages
-along with the body of your message.
-.IP
-\fBNote\fP that changes made to the References: and Date: headers are
-ignored for interoperability reasons.
-
-
-.TP
-.B editor
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable specifies which editor is used by mutt.
-It defaults to the value of the \fC$VISUAL\fP, or \fC$EDITOR\fP, environment
-variable, or to the string \(lq/usr/bin/editor\(rq if neither of those are set.
-
-
-.TP
-.B encode_from
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will quoted\-printable encode messages when
-they contain the string \(lqFrom \(rq (note the trailing space) in the beginning of a line.
-This is useful to avoid the tampering certain mail delivery and transport
-agents tend to do with messages (in order to prevent tools from
-misinterpreting the line as a mbox message separator).
-
-
-.TP
-.B envelope_from_address
-.nf
-Type: e-mail address
-Default: \(lq\(rq
-.fi
-.IP
-Manually sets the \fIenvelope\fP sender for outgoing messages.
-This value is ignored if $use_envelope_from is \fIunset\fP.
-
-
-.TP
-.B escape
-.nf
-Type: string
-Default: \(lq~\(rq
-.fi
-.IP
-Escape character to use for functions in the builtin editor.
-
-
-.TP
-.B fast_reply
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, the initial prompt for recipients and subject are skipped
-when replying to messages, and the initial prompt for subject is
-skipped when forwarding messages.
-.IP
-\fBNote:\fP this variable has no effect when the $autoedit
-variable is \fIset\fP.
-
-
-.TP
-.B fcc_attach
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable controls whether or not attachments on outgoing messages
-are saved along with the main body of your message.
-
-
-.TP
-.B fcc_clear
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, FCCs will be stored unencrypted and
-unsigned, even when the actual message is encrypted and/or
-signed.
-(PGP only)
-
-
-.TP
-.B folder
-.nf
-Type: path
-Default: \(lq~/Mail\(rq
-.fi
-.IP
-Specifies the default location of your mailboxes. A \(lq+\(rq or \(lq=\(rq 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 \fIbefore\fP
-you use \(lq+\(rq or \(lq=\(rq for any other variables since expansion takes place
-when handling the \(lqmailboxes\(rq command.
-
-
-.TP
-.B folder_format
-.nf
-Type: string
-Default: \(lq%2C %t %N %F %2l %\-8.8u %\-8.8g %8s %d %f\(rq
-.fi
-.IP
-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 \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%C
-current file number
-.TP
-%d
-date/time folder was last modified
-.TP
-%f
-filename
-.TP
-%F
-file permissions
-.TP
-%g
-group name (or numeric gid, if missing)
-.TP
-%l
-number of hard links
-.TP
-%N
-N if folder has new mail, blank otherwise
-.TP
-%s
-size in bytes
-.TP
-%t
-\(lq*\(rq if the file is tagged, blank otherwise
-.TP
-%u
-owner name (or numeric uid, if missing)
-.TP
-%>X
-right justify the rest of the string and pad with character \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with character \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-For an explanation of \(lqsoft\-fill\(rq, see the $index_format documentation.
-
-
-.TP
-.B followup_to
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether or not the \(lqMail\-Followup\-To:\(rq header field is
-generated when sending mail. When \fIset\fP, Mutt will generate this
-field when you are replying to a known mailing list, specified with
-the \(lqsubscribe\(rq or \(lqlists\(rq commands.
-.IP
-This field has two purposes. First, preventing you from
-receiving duplicate copies of replies to messages which you send
-to mailing lists, and second, ensuring that you do get a reply
-separately for any messages sent to known lists to which you are
-not subscribed.
-.IP
-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.
-
-
-.TP
-.B force_name
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable is similar to $save_name, except that Mutt 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.
-.IP
-Also see the $record variable.
-
-
-.TP
-.B forward_decode
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls the decoding of complex MIME messages into \fCtext/plain\fP when
-forwarding a message. The message header is also RFC2047 decoded.
-This variable is only used, if $mime_forward is \fIunset\fP,
-otherwise $mime_forward_decode is used instead.
-
-
-.TP
-.B forward_edit
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-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 \(lqno\(rq.
-
-
-.TP
-.B forward_format
-.nf
-Type: string
-Default: \(lq[%a: %s]\(rq
-.fi
-.IP
-This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the $index_format variable.
-
-
-.TP
-.B forward_quote
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, forwarded messages included in the main body of the
-message (when $mime_forward is \fIunset\fP) will be quoted using
-$indent_string.
-
-
-.TP
-.B from
-.nf
-Type: e-mail address
-Default: \(lq\(rq
-.fi
-.IP
-When \fIset\fP, this variable contains a default from address. It
-can be overridden using \(lqmy_hdr\(rq (including from a \(lqsend-hook\(rq) and
-$reverse_name. This variable is ignored if $use_from is \fIunset\fP.
-.IP
-This setting defaults to the contents of the environment variable \fC$EMAIL\fP.
-
-
-.TP
-.B gecos_mask
-.nf
-Type: regular expression
-Default: \(lq^[^,]*\(rq
-.fi
-.IP
-A regular expression used by mutt to parse the GECOS field of a password
-entry when expanding the alias. The default value
-will return the string up to the first \(lq,\(rq encountered.
-If the GECOS field contains a string like \(lqlastname, firstname\(rq then you
-should set it to \(lq\fC.*\fP\(rq.
-.IP
-This can be useful if you see the following behavior: you address an e\-mail
-to user ID \(lqstevef\(rq whose full name is \(lqSteve Franklin\(rq. If mutt expands
-\(lqstevef\(rq to \(lq\(rqFranklin\(rq stevef@foo.bar\(rq then you should set the $gecos_mask to
-a regular expression that will match the whole name so mutt will expand
-\(lqFranklin\(rq to \(lqFranklin, Steve\(rq.
-
-
-.TP
-.B hdrs
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, the header fields normally added by the \(lqmy_hdr\(rq
-command are not created. This variable \fImust\fP be unset before
-composing a new message or replying in order to take effect. If \fIset\fP,
-the user defined header fields are added to every new message.
-
-
-.TP
-.B header
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, this variable causes Mutt to include the header
-of the message you are replying to into the edit buffer.
-The $weed setting applies.
-
-
-.TP
-.B help
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, help lines describing the bindings for the major functions
-provided by each menu are displayed on the first line of the screen.
-.IP
-\fBNote:\fP 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 is
-running. Since this variable is primarily aimed at new users, neither
-of these should present a major problem.
-
-
-.TP
-.B hidden_host
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt 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\-IDs, and it will not lead to the
-cut\-off of first\-level domains.
-
-
-.TP
-.B hide_limited
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will not show the presence of messages that are hidden
-by limiting, in the thread tree.
-
-
-.TP
-.B hide_missing
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will not show the presence of missing messages in the
-thread tree.
-
-
-.TP
-.B hide_thread_subject
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will not show the subject of messages in the thread
-tree that have the same subject as their parent or closest previously
-displayed sibling.
-
-
-.TP
-.B hide_top_limited
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt 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_limited is \fIset\fP, this option will have no effect.
-
-
-.TP
-.B hide_top_missing
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will not show the presence of missing messages at the
-top of threads in the thread tree. Note that when $hide_missing is
-\fIset\fP, this option will have no effect.
-
-
-.TP
-.B history
-.nf
-Type: number
-Default: 10
-.fi
-.IP
-This variable controls the size (in number of strings remembered) of
-the string history buffer per category. The buffer is cleared each time the
-variable is set.
-
-
-.TP
-.B history_file
-.nf
-Type: path
-Default: \(lq~/.mutthistory\(rq
-.fi
-.IP
-The file in which Mutt will save its history.
-
-
-.TP
-.B honor_followup_to
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-This variable controls whether or not a Mail\-Followup\-To header is
-honored when group\-replying to a message.
-
-
-.TP
-.B hostname
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the fully\-qualified hostname of the system mutt is running on
-containing the host's name and the DNS domain it belongs to. It is used
-as the domain part (after \(lq@\(rq) for local email addresses as well as
-Message\-Id headers.
-.IP
-Its value is determined at startup as follows: If the node's name
-as returned by the \fCuname(3)\fP function contains the hostname and the
-domain, these are used to construct $hostname. If there is no
-domain part returned, Mutt will look for a \(lqdomain\(rq or \(lqsearch\(rq
-line in \fC/etc/resolv.conf\fP to determine the domain. Optionally, Mutt
-can be compiled with a fixed domain name in which case a detected
-one is not used.
-.IP
-Also see $use_domain and $hidden_host.
-.IP
-\fBNote:\fP On Debian systems, the default for this variable is obtained
-from /etc/mailname when Mutt starts.
-
-
-.TP
-.B ignore_linear_white_space
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This option replaces linear\-white\-space between encoded\-word
-and text to a single space to prevent the display of MIME\-encoded
-\(lqSubject:\(rq field from being divided into multiple lines.
-
-
-.TP
-.B ignore_list_reply_to
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Affects the behaviour of the \fC<reply>\fP function when replying to
-messages from mailing lists (as defined by the \(lqsubscribe\(rq or
-\(lqlists\(rq commands). When \fIset\fP, if the \(lqReply\-To:\(rq field is
-set to the same value as the \(lqTo:\(rq field, Mutt assumes that the
-\(lqReply\-To:\(rq 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 \fIset\fP, use the \fC<list-reply>\fP
-function; \fC<group\-reply>\fP will reply to both the sender and the
-list.
-
-
-.TP
-.B imap_authenticators
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This is a colon\-delimited list of authentication methods mutt may
-attempt to use to log in to an IMAP server, in the order mutt should
-try them. Authentication methods are either \(lqlogin\(rq or the right
-side of an IMAP \(lqAUTH=xxx\(rq capability string, eg \(lqdigest\-md5\(rq, \(lqgssapi\(rq
-or \(lqcram\-md5\(rq. This option is case\-insensitive. If it's
-\fIunset\fP (the default) mutt will try all available methods,
-in order from most\-secure to least\-secure.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set imap_authenticators=\(rqgssapi:cram\-md5:login\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\fBNote:\fP Mutt will only fall back to other authentication methods if
-the previous methods are unavailable. If a method is available but
-authentication fails, mutt will not connect to the IMAP server.
-
-
-.TP
-.B imap_check_subscribed
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, 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 just as if you had issued individual \(lqmailboxes\(rq
-commands.
-
-
-.TP
-.B imap_delim_chars
-.nf
-Type: string
-Default: \(lq/.\(rq
-.fi
-.IP
-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 \(lq=\(rq shortcut for your \fIfolder\fP variable.
-
-
-.TP
-.B imap_headers
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Mutt requests these header fields in addition to the default headers
-(\(lqDate:\(rq, \(lqFrom:\(rq, \(lqSubject:\(rq, \(lqTo:\(rq, \(lqCc:\(rq, \(lqMessage\-Id:\(rq,
-\(lqReferences:\(rq, \(lqContent\-Type:\(rq, \(lqContent\-Description:\(rq, \(lqIn\-Reply\-To:\(rq,
-\(lqReply\-To:\(rq, \(lqLines:\(rq, \(lqList\-Post:\(rq, \(lqX\-Label:\(rq) from IMAP
-servers before displaying the index menu. You may want to add more
-headers for spam detection.
-.IP
-\fBNote:\fP This is a space separated list, items should be uppercase
-and not contain the colon, e.g. \(lqX\-BOGOSITY X\-SPAM\-STATUS\(rq for the
-\(lqX\-Bogosity:\(rq and \(lqX\-Spam\-Status:\(rq header fields.
-
-
-.TP
-.B imap_idle
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will attempt to use the IMAP IDLE extension
-to check for new mail in the current mailbox. Some servers
-(dovecot was the inspiration for this option) react badly
-to mutt's implementation. If your connection seems to freeze
-up periodically, try unsetting this.
-
-
-.TP
-.B imap_keepalive
-.nf
-Type: number
-Default: 900
-.fi
-.IP
-This variable specifies the maximum amount of time in seconds that mutt
-will wait before polling open IMAP connections, to prevent the server
-from closing them before mutt 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.
-
-
-.TP
-.B imap_list_subscribed
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-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 \fC<toggle\-subscribed>\fP function.
-
-
-.TP
-.B imap_login
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Your login name on the IMAP server.
-.IP
-This variable defaults to the value of $imap_user.
-
-
-.TP
-.B imap_pass
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the password for your IMAP account. If \fIunset\fP, Mutt will
-prompt you for your password when you invoke the \fC<fetch-mail>\fP function
-or try to open an IMAP folder.
-.IP
-\fBWarning\fP: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-
-
-.TP
-.B imap_passive
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will not open new IMAP connections to check for new
-mail. Mutt 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 invocation, or if opening the connection
-is slow.
-
-
-.TP
-.B imap_peek
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt 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.
-
-
-.TP
-.B imap_pipeline_depth
-.nf
-Type: number
-Default: 15
-.fi
-.IP
-Controls the number of IMAP commands that may be queued up before they
-are sent to the server. A deeper pipeline reduces the amount of time
-mutt must wait for the server, and can make IMAP servers feel much
-more responsive. But not all servers correctly handle pipelined commands,
-so if you have problems you might want to try setting this variable to 0.
-.IP
-\fBNote:\fP Changes to this variable have no effect on open connections.
-
-
-.TP
-.B imap_servernoise
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt 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.
-
-
-.TP
-.B imap_user
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-The name of the user whose mail you intend to access on the IMAP
-server.
-.IP
-This variable defaults to your user name on the local machine.
-
-
-.TP
-.B implicit_autoview
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If set to \(lqyes\(rq, mutt will look for a mailcap entry with the
-\(lq\fCcopiousoutput\fP\(rq flag set for \fIevery\fP MIME attachment it doesn't have
-an internal viewer defined for. If such an entry is found, mutt will
-use the viewer defined in that entry to convert the body part to text
-form.
-
-
-.TP
-.B include
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not a copy of the message(s) you are replying to
-is included in your reply.
-
-
-.TP
-.B include_onlyfirst
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Controls whether or not Mutt includes only the first attachment
-of the message you are replying.
-
-
-.TP
-.B indent_string
-.nf
-Type: string
-Default: \(lq> \(rq
-.fi
-.IP
-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.
-.IP
-This option is a format string, please see the description of
-$index_format for supported \fCprintf(3)\fP\-style sequences.
-.IP
-Because for \fCformat=lowed\fP style messages the quoting mechanism
-is strictly defined, this setting is ignored if $text_flowed is
-\fIset\fP.
-
-
-.TP
-.B index_format
-.nf
-Type: string
-Default: \(lq%4C %Z %{%b %d} %\-15.15L (%?l?%4l&%4c?) %s\(rq
-.fi
-.IP
-This variable allows you to customize the message index display to
-your personal taste.
-.IP
-\(lqFormat strings\(rq are similar to the strings used in the C
-function \fCprintf(3)\fP to format output (see the man page for more details).
-The following sequences are defined in Mutt:
-.RS
-.PD 0
-.TP
-%a
-address of the author
-.TP
-%A
-reply\-to address (if present; otherwise: address of author)
-.TP
-%b
-filename of the original message folder (think mailbox)
-.TP
-%B
-the list to which the letter was sent, or else the folder name (%b).
-.TP
-%c
-number of characters (bytes) in the message
-.TP
-%C
-current message number
-.TP
-%d
-date and time of the message in the format specified by
-$date_format converted to sender's time zone
-.TP
-%D
-date and time of the message in the format specified by
-$date_format converted to the local time zone
-.TP
-%e
-current message number in thread
-.TP
-%E
-number of messages in current thread
-.TP
-%f
-sender (address + real name), either From: or Return\-Path:
-.TP
-%F
-author name, or recipient name if the message is from you
-.TP
-%H
-spam attribute(s) of this message
-.TP
-%i
-message\-id of the current message
-.TP
-%l
-number of lines in the message (does not work with maildir,
-mh, and possibly IMAP folders)
-.TP
-%L
-If an address in the \(lqTo:\(rq or \(lqCc:\(rq header field matches an address
-defined by the users \(lqsubscribe\(rq command, this displays
-\(rqTo <list\-name>\(rq, otherwise the same as %F.
-.TP
-%m
-total number of message in the mailbox
-.TP
-%M
-number of hidden messages if the thread is collapsed.
-.TP
-%N
-message score
-.TP
-%n
-author's real name (or address if missing)
-.TP
-%O
-original save folder where mutt would formerly have
-stashed the message: list name or recipient name
-if not sent to a list
-.TP
-%P
-progress indicator for the builtin pager (how much of the file has been displayed)
-.TP
-%s
-subject of the message
-.TP
-%S
-status of the message (\(lqN\(rq/\(lqD\(rq/\(lqd\(rq/\(lq!\(rq/\(lqr\(rq/*)
-.TP
-%t
-\(lqTo:\(rq field (recipients)
-.TP
-%T
-the appropriate character from the $to_chars string
-.TP
-%u
-user (login) name of the author
-.TP
-%v
-first name of the author, or the recipient if the message is from you
-.TP
-%X
-number of attachments
-(please see the \(lqattachments\(rq section for possible speed effects)
-.TP
-%y
-\(lqX\-Label:\(rq field, if present
-.TP
-%Y
-\(lqX\-Label:\(rq field, if present, and \fI(1)\fP not at part of a thread tree,
-\fI(2)\fP at the top of a thread, or \fI(3)\fP \(lqX\-Label:\(rq is different from
-preceding message's \(lqX\-Label:\(rq.
-.TP
-%Z
-message status flags
-.TP
-%{fmt}
-the date and time of the message is converted to sender's
-time zone, and \(lqfmt\(rq is expanded by the library function
-\fCstrftime(3)\fP; a leading bang disables locales
-.TP
-%[fmt]
-the date and time of the message is converted to the local
-time zone, and \(lqfmt\(rq is expanded by the library function
-\fCstrftime(3)\fP; a leading bang disables locales
-.TP
-%(fmt)
-the local date and time when the message was received.
-\(lqfmt\(rq is expanded by the library function \fCstrftime(3)\fP;
-a leading bang disables locales
-.TP
-%<fmt>
-the current local time. \(lqfmt\(rq is expanded by the library
-function \fCstrftime(3)\fP; a leading bang disables locales.
-.TP
-%>X
-right justify the rest of the string and pad with character \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with character \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-\(lqSoft\-fill\(rq deserves some explanation: Normal right\-justification
-will print everything to the left of the \(lq%>\(rq, displaying padding and
-whatever lies to the right only if there's room. By contrast,
-soft\-fill gives priority to the right\-hand side, guaranteeing space
-to display it and showing padding only if there's still room. If
-necessary, soft\-fill will eat text leftwards to make room for
-rightward text.
-.IP
-Note that these expandos are supported in
-\(lqsave-hook\(rq, \(lqfcc-hook\(rq and \(lqfcc-save-hook\(rq, too.
-
-
-.TP
-.B ispell
-.nf
-Type: path
-Default: \(lqispell\(rq
-.fi
-.IP
-How to invoke ispell (GNU's spell\-checking software).
-
-
-.TP
-.B keep_flagged
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, read messages marked as flagged will not be moved
-from your spool mailbox to your $mbox mailbox, or as a result of
-a \(lqmbox-hook\(rq command.
-
-
-.TP
-.B locale
-.nf
-Type: string
-Default: \(lqC\(rq
-.fi
-.IP
-The locale used by \fCstrftime(3)\fP to format dates. Legal values are
-the strings your system accepts for the locale environment variable \fC$LC_TIME\fP.
-
-
-.TP
-.B mail_check
-.nf
-Type: number
-Default: 5
-.fi
-.IP
-This variable configures how often (in seconds) mutt should look for
-new mail. Also see the $timeout variable.
-
-
-.TP
-.B mailcap_path
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This variable specifies which files to consult when attempting to
-display MIME bodies not directly supported by Mutt.
-
-
-.TP
-.B mailcap_sanitize
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, mutt 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.
-.IP
-\fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
-DOING!\fP
-
-
-.TP
-.B maildir_mtime
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If set, the sort\-by\-date option in the browser will sort maildirs
-smartly, not using the mtime of the maildir itself but that of the
-newest message in the new subdirectory, making the sorting by
-reverse date much more useful. People with maildirs over NFS may
-wish to leave this option unset.
-
-
-.TP
-.B header_cache
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is \fIunset\fP so no header
-caching will be used.
-.IP
-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see \(lqcaching\(rq for details.
-
-
-.TP
-.B maildir_header_cache_verify
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Check for Maildir unaware programs other than mutt having modified maildir
-files when the header cache is in use. This incurs one \fCstat(2)\fP per
-message every time the folder is opened (which can be very slow for NFS
-folders).
-
-
-.TP
-.B header_cache_pagesize
-.nf
-Type: string
-Default: \(lq16384\(rq
-.fi
-.IP
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-
-
-.TP
-.B maildir_trash
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, messages marked as deleted will be saved with the maildir
-trashed flag instead of unlinked. \fBNote:\fP this only applies
-to maildir\-style mailboxes. Setting it will have no effect on other
-mailbox types.
-
-
-.TP
-.B mark_old
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether or not mutt marks \fInew\fP \fBunread\fP
-messages as \fIold\fP if you exit a mailbox without reading them.
-With this option \fIset\fP, the next time you start mutt, the messages
-will show up with an \(lqO\(rq next to them in the index menu,
-indicating that they are old.
-
-
-.TP
-.B markers
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls the display of wrapped lines in the internal pager. If set, a
-\(lq+\(rq marker is displayed at the beginning of wrapped lines.
-.IP
-Also see the $smart_wrap variable.
-
-
-.TP
-.B mask
-.nf
-Type: regular expression
-Default: \(lq!^\\.[^.]\(rq
-.fi
-.IP
-A regular expression used in the file browser, optionally preceded by
-the \fInot\fP operator \(lq!\(rq. Only files whose names match this mask
-will be shown. The match is always case\-sensitive.
-
-
-.TP
-.B mbox
-.nf
-Type: path
-Default: \(lq~/mbox\(rq
-.fi
-.IP
-This specifies the folder into which read mail in your $spoolfile
-folder will be appended.
-.IP
-Also see the $move variable.
-
-
-.TP
-.B mbox_type
-.nf
-Type: folder magic
-Default: mbox
-.fi
-.IP
-The default mailbox type used when creating new folders. May be any of
-\(lqmbox\(rq, \(lqMMDF\(rq, \(lqMH\(rq and \(lqMaildir\(rq.
-
-
-.TP
-.B metoo
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIunset\fP, Mutt will remove your address (see the \(lqalternates\(rq
-command) from the list of recipients when replying to a message.
-
-
-.TP
-.B menu_context
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to $pager_context.)
-
-
-.TP
-.B menu_move_off
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, the bottom entry of menus will never scroll up past
-the bottom of the screen, unless there are less entries than lines.
-When \fIset\fP, the bottom entry may move off the bottom.
-
-
-.TP
-.B menu_scroll
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, menus will be scrolled up or down one line when you
-attempt to move across a screen boundary. If \fIunset\fP, the screen
-is cleared and the next or previous page of the menu is displayed
-(useful for slow links to avoid many redraws).
-
-
-.TP
-.B meta_key
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, forces Mutt 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 \fC0xf8\fP, then this is treated as if the user had
-pressed Esc then \(lqx\(rq. This is because the result of removing the
-high bit from \fC0xf8\fP is \fC0x78\fP, which is the ASCII character
-\(lqx\(rq.
-
-
-.TP
-.B mh_purge
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIunset\fP, mutt will mimic mh's behaviour and rename deleted messages
-to \fI,<old file name>\fP in mh folders instead of really deleting
-them. This leaves the message on disk but makes programs reading the folder
-ignore it. If the variable is \fIset\fP, the message files will simply be
-deleted.
-.IP
-This option is similar to $maildir_trash for Maildir folders.
-
-
-.TP
-.B mh_seq_flagged
-.nf
-Type: string
-Default: \(lqflagged\(rq
-.fi
-.IP
-The name of the MH sequence used for flagged messages.
-
-
-.TP
-.B mh_seq_replied
-.nf
-Type: string
-Default: \(lqreplied\(rq
-.fi
-.IP
-The name of the MH sequence used to tag replied messages.
-
-
-.TP
-.B mh_seq_unseen
-.nf
-Type: string
-Default: \(lqunseen\(rq
-.fi
-.IP
-The name of the MH sequence used for unseen messages.
-
-
-.TP
-.B mime_forward
-.nf
-Type: quadoption
-Default: no
-.fi
-.IP
-When \fIset\fP, the message you are forwarding will be attached as a
-separate \fCmessage/rfc822\fP 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 \(lqask\-no\(rq or \(lqask\-yes\(rq.
-.IP
-Also see $forward_decode and $mime_forward_decode.
-
-
-.TP
-.B mime_forward_decode
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Controls the decoding of complex MIME messages into \fCtext/plain\fP when
-forwarding a message while $mime_forward is \fIset\fP. Otherwise
-$forward_decode is used instead.
-
-
-.TP
-.B mime_forward_rest
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-When forwarding multiple attachments of a MIME message from the attachment
-menu, attachments which cannot be decoded in a reasonable manner will
-be attached to the newly composed message if this option is \fIset\fP.
-
-
-.TP
-.B mix_entry_format
-.nf
-Type: string
-Default: \(lq%4n %c %\-16s %a\(rq
-.fi
-.IP
-This variable describes the format of a remailer line on the mixmaster
-chain selection screen. The following \fCprintf(3)\fP\-like sequences are
-supported:
-.RS
-.PD 0
-.TP
-%n
-The running number on the menu.
-.TP
-%c
-Remailer capabilities.
-.TP
-%s
-The remailer's short name.
-.TP
-%a
-The remailer's e\-mail address.
-.RE
-.PD 1
-
-.TP
-.B mixmaster
-.nf
-Type: path
-Default: \(lqmixmaster\(rq
-.fi
-.IP
-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.
-.IP
-\fBNote:\fP On Debian systems, this option is set by default to
-\(lqmixmaster\-filter\(rq in /etc/Muttrc.
-
-
-.TP
-.B move
-.nf
-Type: quadoption
-Default: no
-.fi
-.IP
-Controls whether or not Mutt will move read messages
-from your spool mailbox to your $mbox mailbox, or as a result of
-a \(lqmbox-hook\(rq command.
-
-
-.TP
-.B message_cachedir
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-.IP
-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-.IP
-Also see the $message_cache_clean variable.
-
-
-.TP
-.B message_cache_clean
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-
-
-.TP
-.B message_format
-.nf
-Type: string
-Default: \(lq%s\(rq
-.fi
-.IP
-This is the string displayed in the \(lqattachment\(rq menu for
-attachments of type \fCmessage/rfc822\fP. For a full listing of defined
-\fCprintf(3)\fP\-like sequences see the section on $index_format.
-
-
-.TP
-.B narrow_tree
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable, when \fIset\fP, makes the thread tree narrower, allowing
-deeper threads to fit on the screen.
-
-
-.TP
-.B net_inc
-.nf
-Type: number
-Default: 10
-.fi
-.IP
-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.
-.IP
-See also $read_inc, $write_inc and $net_inc.
-
-
-.TP
-.B pager
-.nf
-Type: path
-Default: \(lqbuiltin\(rq
-.fi
-.IP
-This variable specifies which pager you would like to use to view
-messages. The value \(lqbuiltin\(rq means to use the builtin pager, otherwise this
-variable should specify the pathname of the external pager you would
-like to use.
-.IP
-Using an external pager may have some disadvantages: Additional
-keystrokes are necessary because you can't call mutt functions
-directly from the pager, and screen resizes cause lines longer than
-the screen width to be badly formatted in the help menu.
-
-
-.TP
-.B pager_context
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-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 will display the line after the last one on the screen
-at the top of the next page (0 lines of context).
-
-
-.TP
-.B pager_format
-.nf
-Type: string
-Default: \(lq\-%Z\- %C/%m: %\-20.20n %s%* \-\- (%P)\(rq
-.fi
-.IP
-This variable controls the format of the one\-line message \(lqstatus\(rq
-displayed before each message in either the internal or an external
-pager. The valid sequences are listed in the $index_format
-section.
-
-
-.TP
-.B pager_index_lines
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-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 setting 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.
-
-
-.TP
-.B pager_stop
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, the internal\-pager will \fBnot\fP move to the next message
-when you are at the end of a message and invoke the \fC<next\-page>\fP
-function.
-
-
-.TP
-.B crypt_autosign
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Setting this variable will cause Mutt 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 \fIset\fP,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-
-
-.TP
-.B crypt_autoencrypt
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages. This is probably only useful in
-connection to the \(lqsend-hook\(rq 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 \fIset\fP,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-
-
-.TP
-.B pgp_ignore_subkeys
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
-if you want to play interesting key selection games.
-(PGP only)
-
-
-.TP
-.B crypt_replyencrypt
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-
-
-.TP
-.B crypt_replysign
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
-signed.
-.IP
-\fBNote:\fP this does not work on messages that are encrypted
-\fIand\fP signed!
-(Crypto only)
-
-
-.TP
-.B crypt_replysignencrypted
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, 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 is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-
-
-.TP
-.B crypt_timestamp
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, mutt 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 \fIunset\fP this setting.
-(Crypto only)
-
-
-.TP
-.B pgp_use_gpg_agent
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, mutt will use a possibly\-running \fCgpg\-agent(1)\fP process.
-(PGP only)
-
-
-.TP
-.B crypt_verify_sig
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-If \fI\(lqyes\(rq\fP, always attempt to verify PGP or S/MIME signatures.
-If \fI\(lqask\-*\(rq\fP, ask whether or not to verify the signature.
-If \\Fi\(lqno\(rq\fP, never attempt to verify cryptographic signatures.
-(Crypto only)
-
-
-.TP
-.B smime_is_default
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-The default behaviour of mutt is to use PGP on all auto\-sign/encryption
-operations. To override and to use OpenSSL instead this must be \fIset\fP.
-However, this has no effect while replying, since mutt 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)
-
-
-.TP
-.B smime_ask_cert_label
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-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
-\fIset\fP by default.
-(S/MIME only)
-
-
-.TP
-.B smime_decrypt_use_default_key
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate\-key\-pairs, mutt 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)
-
-
-.TP
-.B pgp_entry_format
-.nf
-Type: string
-Default: \(lq%4n %t%f %4l/0x%k %\-4a %2c %u\(rq
-.fi
-.IP
-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 \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%n
-number
-.TP
-%k
-key id
-.TP
-%u
-user id
-.TP
-%a
-algorithm
-.TP
-%l
-key length
-.TP
-%f
-flags
-.TP
-%c
-capabilities
-.TP
-%t
-trust/validity of the key\-uid association
-.TP
-%[<s>]
-date of the key where <s> is an \fCstrftime(3)\fP expression
-.RE
-.PD 1
-.IP
-(PGP only)
-
-
-.TP
-.B pgp_good_sign
-.nf
-Type: regular expression
-Default: \(lq\(rq
-.fi
-.IP
-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)
-
-
-.TP
-.B pgp_check_exit
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, mutt 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)
-
-
-.TP
-.B pgp_long_ids
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, use 64 bit PGP key IDs, if \fIunset\fP use the normal 32 bit key IDs.
-(PGP only)
-
-
-.TP
-.B pgp_retainable_sigs
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, signed and encrypted messages will consist of nested
-\fCmultipart/signed\fP and \fCmultipart/encrypted\fP body parts.
-.IP
-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (\fCmultipart/encrypted\fP) can be easily
-removed, while the inner \fCmultipart/signed\fP part is retained.
-(PGP only)
-
-
-.TP
-.B pgp_autoinline
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This option controls whether Mutt 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.
-.IP
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-.IP
-Also see the $pgp_mime_auto variable.
-.IP
-Also note that using the old\-style PGP message format is \fBstrongly\fP
-\fBdeprecated\fP.
-(PGP only)
-
-
-.TP
-.B pgp_replyinline
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Setting this variable will cause Mutt 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
-internals for previously checked/flagged messages.
-.IP
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-.IP
-Also see the $pgp_mime_auto variable.
-.IP
-Also note that using the old\-style PGP message format is \fBstrongly\fP
-\fBdeprecated\fP.
-(PGP only)
-
-
-.TP
-.B pgp_show_unusable
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, mutt 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 \(lqdisabled\(rq by the user.
-(PGP only)
-
-
-.TP
-.B pgp_sign_as
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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. \fC0x00112233\fP).
-(PGP only)
-
-
-.TP
-.B pgp_strict_enc
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, Mutt 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)
-
-
-.TP
-.B pgp_timeout
-.nf
-Type: number
-Default: 300
-.fi
-.IP
-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-
-
-.TP
-.B pgp_sort_keys
-.nf
-Type: sort order
-Default: address
-.fi
-.IP
-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-.RS
-.PD 0
-.TP
-address
-sort alphabetically by user id
-.TP
-keyid
-sort alphabetically by key id
-.TP
-date
-sort by key creation date
-.TP
-trust
-sort by the trust of the key
-.RE
-.PD 1
-.IP
-If you prefer reverse order of the above values, prefix it with
-\(lqreverse\-\(rq.
-(PGP only)
-
-
-.TP
-.B pgp_mime_auto
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-.IP
-Also note that using the old\-style PGP message format is \fBstrongly\fP
-\fBdeprecated\fP.
-(PGP only)
-
-
-.TP
-.B pgp_auto_decode
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, mutt 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 \fC<check-traditional-pgp>\fP function, mutt will automatically
-check the message for traditional pgp.
-
-
-.TP
-.B pgp_mime_signature_filename
-.nf
-Type: string
-Default: \(lqsignature.asc\(rq
-.fi
-.IP
-This option sets the filename used for signature parts in PGP/MIME
-signed messages.
-
-
-.TP
-.B pgp_mime_signature_description
-.nf
-Type: string
-Default: \(lqDigital signature\(rq
-.fi
-.IP
-This option sets the Content\-Description used for signature parts in
-PGP/MIME signed messages.
-
-
-.TP
-.B pgp_decode_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This format strings specifies a command which is used to decode
-application/pgp attachments.
-.IP
-The PGP command formats have their own set of \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%p
-Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-string otherwise. Note: This may be used with a %? construct.
-.TP
-%f
-Expands to the name of a file containing a message.
-.TP
-%s
-Expands to the name of a file containing the signature part
- of a \fCmultipart/signed\fP attachment when verifying it.
-.TP
-%a
-The value of $pgp_sign_as.
-.TP
-%r
-One or more key IDs.
-.RE
-.PD 1
-.IP
-For examples on how to configure these formats for the various versions
-of PGP which are floating around, see the pgp and gpg sample configuration files in
-the \fCsamples/\fP subdirectory which has been installed on your system
-alongside the documentation.
-(PGP only)
-
-
-.TP
-.B pgp_getkeys_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by $pgp_decode_command, %r is the only
-\fCprintf(3)\fP\-like sequence used with this format.
-(PGP only)
-
-
-.TP
-.B pgp_verify_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to verify PGP signatures.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_decrypt_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to decrypt a PGP encrypted message.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_clearsign_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This format is used to create an old\-style \(lqclearsigned\(rq PGP
-message. Note that the use of this format is \fBstrongly\fP
-\fBdeprecated\fP.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_sign_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to create the detached PGP signature for a
-\fCmultipart/signed\fP PGP/MIME body part.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_encrypt_sign_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to both sign and encrypt a body part.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_encrypt_only_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to encrypt a body part without signing it.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_import_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to import a key from a message into
-the user's public key ring.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_export_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to export a public key from the user's
-key ring.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_verify_key_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to verify key information from the key selection
-menu.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_list_secring_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to list the secret key ring's contents. The
-output format must be analogous to the one used by:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-gpg \-\-list\-keys \-\-with\-colons.
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-This format is also generated by the \fCpgpring\fP utility which comes
-with mutt.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B pgp_list_pubring_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to list the public key ring's contents. The
-output format must be analogous to the one used by
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-gpg \-\-list\-keys \-\-with\-colons.
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-This format is also generated by the \fCpgpring\fP utility which comes
-with mutt.
-.IP
-This is a format string, see the $pgp_decode_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(PGP only)
-
-
-.TP
-.B forward_decrypt
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls the handling of encrypted messages when forwarding a message.
-When \fIset\fP, the outer layer of encryption is stripped off. This
-variable is only used if $mime_forward is \fIset\fP and
-$mime_forward_decode is \fIunset\fP.
-(PGP only)
-
-
-.TP
-.B smime_timeout
-.nf
-Type: number
-Default: 300
-.fi
-.IP
-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-
-
-.TP
-.B smime_encrypt_with
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This sets the algorithm that should be used for encryption.
-Valid choices are \(lqdes\(rq, \(lqdes3\(rq, \(lqrc2\-40\(rq, \(lqrc2\-64\(rq, \(lqrc2\-128\(rq.
-If \fIunset\fP, \(lq3des\(rq (TripleDES) is used.
-(S/MIME only)
-
-
-.TP
-.B smime_keys
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and 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 option points to the location of the private keys.
-(S/MIME only)
-
-
-.TP
-.B smime_ca_location
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-.IP
-\fBNote:\fP On Debian systems, this defaults to the first existing file in
-the following list: ~/.smime/ca\-certificates.crt ~/.smime/ca\-bundle.crt
-/etc/ssl/certs/ca\-certificates.crt.
-
-
-.TP
-.B smime_certificates
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-the location of the certificates.
-(S/MIME only)
-
-
-.TP
-.B smime_decrypt_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This format string specifies a command which is used to decrypt
-\fCapplication/x\-pkcs7\-mime\fP attachments.
-.IP
-The OpenSSL command formats have their own set of \fCprintf(3)\fP\-like sequences
-similar to PGP's:
-.RS
-.PD 0
-.TP
-%f
-Expands to the name of a file containing a message.
-.TP
-%s
-Expands to the name of a file containing the signature part
- of a \fCmultipart/signed\fP attachment when verifying it.
-.TP
-%k
-The key\-pair specified with $smime_default_key
-.TP
-%c
-One or more certificate IDs.
-.TP
-%a
-The algorithm used for encryption.
-.TP
-%C
-CA location: Depending on whether $smime_ca_location
- points to a directory or file, this expands to
- \(lq\-CApath $smime_ca_location\(rq or \(lq\-CAfile $smime_ca_location\(rq.
-.RE
-.PD 1
-.IP
-For examples on how to configure these formats, see the \fCsmime.rc\fP in
-the \fCsamples/\fP subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-
-
-.TP
-.B smime_verify_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to verify S/MIME signatures of type \fCmultipart/signed\fP.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_verify_opaque_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to verify S/MIME signatures of type
-\fCapplication/x\-pkcs7\-mime\fP.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_sign_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to created S/MIME signatures of type
-\fCmultipart/signed\fP, which can be read by all mail clients.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_sign_opaque_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to created S/MIME signatures of type
-\fCapplication/x\-pkcs7\-signature\fP, which can only be handled by mail
-clients supporting the S/MIME extension.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_encrypt_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to create encrypted S/MIME messages.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_pk7out_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_get_cert_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to extract X509 certificates from a PKCS7 structure.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_get_signer_cert_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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 \(lqFrom:\(rq field.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_import_cert_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This command is used to import a certificate via smime_keys.
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_get_cert_email_command
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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).
-.IP
-This is a format string, see the $smime_decrypt_command command for
-possible \fCprintf(3)\fP\-like sequences.
-(S/MIME only)
-
-
-.TP
-.B smime_default_key
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-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)
-
-
-.TP
-.B ssl_client_cert
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-The file containing a client certificate and its associated private
-key.
-
-
-.TP
-.B ssl_force_tls
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If this variable is \fIset\fP, Mutt 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.
-
-
-.TP
-.B ssl_starttls
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-If \fIset\fP (the default), mutt will attempt to use \fCSTARTTLS\fP on servers
-advertising the capability. When \fIunset\fP, mutt will not attempt to
-use \fCSTARTTLS\fP regardless of the server's capabilities.
-
-
-.TP
-.B certificate_file
-.nf
-Type: path
-Default: \(lq~/.mutt_certificates\(rq
-.fi
-.IP
-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.
-.IP
-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set certificate_file=~/.mutt/certificates
-
-.fi
-.ec
-.ft P
-.sp
-
-
-.TP
-.B ssl_use_sslv3
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-
-
-.TP
-.B ssl_use_tlsv1
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-
-
-.TP
-.B ssl_min_dh_prime_bits
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-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.
-
-
-.TP
-.B ssl_ca_certificates_file
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set ssl_ca_certificates_file=/etc/ssl/certs/ca\-certificates.crt
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\fBNote:\fP On Debian systems, this variable defaults to the example
-mentioned. This file is managed by the \(lqca\-certificates\(rq package.
-
-
-.TP
-.B pipe_split
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Used in connection with the \fC<pipe\-message>\fP function following
-\fC<tag\-prefix>\fP. If this variable is \fIunset\fP, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated. When \fIset\fP, Mutt 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.
-
-
-.TP
-.B pipe_decode
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Used in connection with the \fC<pipe\-message>\fP command. When \fIunset\fP,
-Mutt will pipe the messages without any preprocessing. When \fIset\fP, Mutt
-will weed headers and will attempt to decode the messages
-first.
-
-
-.TP
-.B pipe_sep
-.nf
-Type: string
-Default: \(lq\\n\(rq
-.fi
-.IP
-The separator to add between messages when piping a list of tagged
-messages to an external Unix command.
-
-
-.TP
-.B pop_authenticators
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This is a colon\-delimited list of authentication methods mutt may
-attempt to use to log in to an POP server, in the order mutt should
-try them. Authentication methods are either \(lquser\(rq, \(lqapop\(rq or any
-SASL mechanism, eg \(lqdigest\-md5\(rq, \(lqgssapi\(rq or \(lqcram\-md5\(rq.
-This option is case\-insensitive. If this option is \fIunset\fP
-(the default) mutt will try all available methods, in order from
-most\-secure to least\-secure.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set pop_authenticators=\(rqdigest\-md5:apop:user\(rq
-
-.fi
-.ec
-.ft P
-.sp
-
-
-.TP
-.B pop_auth_try_all
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, Mutt will try all available authentication methods.
-When \fIunset\fP, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-
-
-.TP
-.B pop_checkinterval
-.nf
-Type: number
-Default: 60
-.fi
-.IP
-This variable configures how often (in seconds) mutt should look for
-new mail in the currently selected mailbox if it is a POP mailbox.
-
-
-.TP
-.B pop_delete
-.nf
-Type: quadoption
-Default: ask\-no
-.fi
-.IP
-If \fIset\fP, Mutt will delete successfully downloaded messages from the POP
-server when using the \fC<fetch-mail>\fP function. When \fIunset\fP, Mutt will
-download messages but also leave them on the POP server.
-
-
-.TP
-.B pop_host
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-The name of your POP server for the \fC<fetch-mail>\fP function. You
-can also specify an alternative port, username and password, ie:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-[pop[s]://][username[:password]@]popserver[:port]
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-where \(lq[...]\(rq denotes an optional part.
-
-
-.TP
-.B pop_last
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If this variable is \fIset\fP, mutt will try to use the \(lq\fCLAST\fP\(rq POP command
-for retrieving only unread messages from the POP server when using
-the \fC<fetch-mail>\fP function.
-
-
-.TP
-.B pop_reconnect
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-
-
-.TP
-.B pop_user
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Your login name on the POP server.
-.IP
-This variable defaults to your user name on the local machine.
-
-
-.TP
-.B pop_pass
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the password for your POP account. If \fIunset\fP, Mutt will
-prompt you for your password when you open a POP mailbox.
-.IP
-\fBWarning\fP: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc
-even if you are the only one who can read the file.
-
-
-.TP
-.B post_indent_string
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Similar to the $attribution variable, Mutt will append this
-string after the inclusion of a message which is being replied to.
-
-
-.TP
-.B postpone
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not messages are saved in the $postponed
-mailbox when you elect not to send immediately.
-.IP
-Also see the $recall variable.
-
-
-.TP
-.B postponed
-.nf
-Type: path
-Default: \(lq~/postponed\(rq
-.fi
-.IP
-Mutt allows you to indefinitely \(lqpostpone sending a message\(rq which
-you are editing. When you choose to postpone a message, Mutt saves it
-in the mailbox specified by this variable.
-.IP
-Also see the $postpone variable.
-
-
-.TP
-.B preconnect
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-If \fIset\fP, a shell command to be executed if mutt fails to establish
-a connection to the server. This is useful for setting up secure
-connections, e.g. with \fCssh(1)\fP. If the command returns a nonzero
-status, mutt gives up opening the server. Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set preconnect=\(rqssh \-f \-q \-L 1234:mailhost.net:143 mailhost.net \\
-sleep 20 < /dev/null > /dev/null\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-Mailbox \(lqfoo\(rq on \(lqmailhost.net\(rq can now be reached
-as \(lq{localhost:1234}foo\(rq.
-.IP
-Note: For this example to work, you must be able to log in to the
-remote machine without having to enter a password.
-.IP
-When set, Mutt uses the tunnel for all remote connections.
-Please see \(lqaccount-hook\(rq in the manual for how to use different
-tunnel commands per connection.
-
-
-.TP
-.B print
-.nf
-Type: quadoption
-Default: ask\-no
-.fi
-.IP
-Controls whether or not Mutt really prints messages.
-This is set to \(lqask\-no\(rq by default, because some people
-accidentally hit \(lqp\(rq often.
-
-
-.TP
-.B print_command
-.nf
-Type: path
-Default: \(lqlpr\(rq
-.fi
-.IP
-This specifies the command pipe that should be used to print messages.
-
-
-.TP
-.B print_decode
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Used in connection with the \fC<print\-message>\fP command. If this
-option is \fIset\fP, the message is decoded before it is passed to the
-external command specified by $print_command. If this option
-is \fIunset\fP, 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.
-
-
-.TP
-.B print_split
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Used in connection with the \fC<print\-message>\fP command. If this option
-is \fIset\fP, the command specified by $print_command is executed once for
-each message which is to be printed. If this option is \fIunset\fP,
-the command specified by $print_command is executed only once, and
-all the messages are concatenated, with a form feed as the message
-separator.
-.IP
-Those who use the \fCenscript\fP(1) program's mail\-printing mode will
-most likely want to \fIset\fP this option.
-
-
-.TP
-.B prompt_after
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If you use an \fIexternal\fP $pager, setting this variable will
-cause Mutt to prompt you for a command when the pager exits rather
-than returning to the index menu. If \fIunset\fP, Mutt will return to the
-index menu when the external pager exits.
-
-
-.TP
-.B query_command
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This specifies the command that mutt will use to make external address
-queries. The string should contain a \(lq%s\(rq, which will be substituted
-with the query string the user types. See \(lqquery\(rq for more
-information.
-
-
-.TP
-.B query_format
-.nf
-Type: string
-Default: \(lq%4c %t %\-25.25a %\-25.25n %?e?(%e)?\(rq
-.fi
-.IP
-This variable describes the format of the \(lqquery\(rq menu. The
-following \fCprintf(3)\fP\-style sequences are understood:
-.RS
-.PD 0
-.TP
-%a
-destination address
-.TP
-%c
-current entry number
-.TP
-%e
-extra information *
-.TP
-%n
-destination name
-.TP
-%t
-\(lq*\(rq if current entry is tagged, a space otherwise
-.TP
-%>X
-right justify the rest of the string and pad with \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-For an explanation of \(lqsoft\-fill\(rq, see the $index_format documentation.
-.IP
-* = can be optionally printed if nonzero, see the $status_format documentation.
-
-
-.TP
-.B quit
-.nf
-Type: quadoption
-Default: yes
-.fi
-.IP
-This variable controls whether \(lqquit\(rq and \(lqexit\(rq actually quit
-from mutt. If this option is \fIset\fP, they do quit, if it is \fIunset\fP, they
-have no effect, and if it is set to \fIask\-yes\fP or \fIask\-no\fP, you are
-prompted for confirmation when you try to quit.
-
-
-.TP
-.B quote_regexp
-.nf
-Type: regular expression
-Default: \(lq^([ \\t]*[|>:}#])+\(rq
-.fi
-.IP
-A regular expression used in the internal pager to determine quoted
-sections of text in the body of a message. Quoted text may be filtered
-out using the \fC<toggle\-quoted>\fP command, or colored according to the
-\(lqcolor quoted\(rq family of directives.
-.IP
-Higher levels of quoting may be colored differently (\(lqcolor quoted1\(rq,
-\(lqcolor quoted2\(rq, etc.). The quoting level is determined by removing
-the last character from the matched text and recursively reapplying
-the regular expression until it fails to produce a match.
-.IP
-Match detection may be overridden by the $smileys regular expression.
-
-
-.TP
-.B read_inc
-.nf
-Type: number
-Default: 10
-.fi
-.IP
-If set to a value greater than 0, Mutt will display which message it
-is currently on when reading a mailbox or when performing search actions
-such as search and limit. The message is printed after
-this many messages have been read or searched (e.g., if set to 25, Mutt will
-print a message when it is at message 25, and then again when it gets
-to message 50). This variable is meant to indicate progress when
-reading or searching large mailboxes which may take some time.
-When set to 0, only a single message will appear before the reading
-the mailbox.
-.IP
-Also see the $write_inc, $net_inc and $time_inc variables and the
-\(lqtuning\(rq section of the manual for performance considerations.
-
-
-.TP
-.B read_only
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, all folders are opened in read\-only mode.
-
-
-.TP
-.B realname
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This variable specifies what \(lqreal\(rq or \(lqpersonal\(rq name should be used
-when sending messages.
-.IP
-By default, this is the GECOS field from \fC/etc/passwd\fP. Note that this
-variable will \fInot\fP be used when the user has set a real name
-in the $from variable.
-
-
-.TP
-.B recall
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-Controls whether or not Mutt recalls postponed messages
-when composing a new message.
-.IP
-\fISetting\fP this variable to is not generally useful, and thus not
-recommended.
-.IP
-Also see $postponed variable.
-
-
-.TP
-.B record
-.nf
-Type: path
-Default: \(lq~/sent\(rq
-.fi
-.IP
-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 \(lqmy_hdr\(rq
-command to create a \(lqBcc:\(rq field with your email address in it.)
-.IP
-The value of \fI$record\fP is overridden by the $force_name and
-$save_name variables, and the \(lqfcc-hook\(rq command.
-
-
-.TP
-.B reply_regexp
-.nf
-Type: regular expression
-Default: \(lq^(re([\\[0\-9\\]+])*|aw):[ \\t]*\(rq
-.fi
-.IP
-A regular expression used to recognize reply messages when threading
-and replying. The default value corresponds to the English \(rqRe:\(rq and
-the German \(rqAw:\(rq.
-
-
-.TP
-.B reply_self
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIunset\fP and you are replying to a message sent by you, Mutt will
-assume that you want to reply to the recipients of that message rather
-than to yourself.
-.IP
-Also see the \(lqalternates\(rq command.
-
-
-.TP
-.B reply_to
-.nf
-Type: quadoption
-Default: ask\-yes
-.fi
-.IP
-If \fIset\fP, when replying to a message, Mutt will use the address listed
-in the Reply\-to: header as the recipient of the reply. If \fIunset\fP,
-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.
-
-
-.TP
-.B resolve
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, the cursor will be automatically advanced to the next
-(possibly undeleted) message whenever a command that modifies the
-current message is executed.
-
-
-.TP
-.B reverse_alias
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable controls whether or not Mutt will display the \(lqpersonal\(rq
-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:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-alias juser abd30425@somewhere.net (Joe User)
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-and then you receive mail which contains the following header:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-From: abd30425@somewhere.net
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-It would be displayed in the index menu as \(lqJoe User\(rq instead of
-\(lqabd30425@somewhere.net.\(rq This is useful when the person's e\-mail
-address is not human friendly.
-
-
-.TP
-.B reverse_name
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-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 \fIset\fP, the default \fIFrom:\fP line of
-the reply messages is built using the address where you received the
-messages you are replying to \fBif\fP that address matches your
-\(lqalternates\(rq. If the variable is \fIunset\fP, or the address that would be
-used doesn't match your \(lqalternates\(rq, the \fIFrom:\fP line will use
-your address on the current machine.
-.IP
-Also see the \(lqalternates\(rq command.
-
-
-.TP
-.B reverse_realname
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable fine\-tunes the behaviour of the $reverse_name feature.
-When it is \fIset\fP, mutt will use the address from incoming messages as\-is,
-possibly including eventual real names. When it is \fIunset\fP, mutt will
-override any such real names with the setting of the $realname variable.
-
-
-.TP
-.B rfc2047_parameters
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When this variable is \fIset\fP, Mutt will decode RFC2047\-encoded MIME
-parameters. You want to set this variable when mutt suggests you
-to save attachments to files named like:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-=?iso\-8859\-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-When this variable is \fIset\fP interactively, the change won't be
-active until you change folders.
-.IP
-Note that this use of RFC2047's encoding is explicitly
-prohibited by the standard, but nevertheless encountered in the
-wild.
-.IP
-Also note that setting this parameter will \fInot\fP have the effect
-that mutt \fIgenerates\fP this kind of encoding. Instead, mutt will
-unconditionally use the encoding specified in RFC2231.
-
-
-.TP
-.B save_address
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If $save_name or $force_name
-is \fIset\fP too, the selection of the Fcc folder will be changed as well.
-
-
-.TP
-.B save_empty
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, mailboxes which contain no saved messages will be removed
-when closed (the exception is $spoolfile which is never removed).
-If \fIset\fP, mailboxes are never removed.
-.IP
-\fBNote:\fP This only applies to mbox and MMDF folders, Mutt does not
-delete MH and Maildir directories.
-
-
-.TP
-.B save_history
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-This variable controls the size of the history (per category) saved in the
-$history_file file.
-
-
-.TP
-.B save_name
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-This variable controls how copies of outgoing messages are saved.
-When \fIset\fP, 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 \fIusername\fP 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.
-.IP
-Also see the $force_name variable.
-
-
-.TP
-.B score
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When this variable is \fIunset\fP, scoring is turned off. This can
-be useful to selectively disable scoring for certain folders when the
-$score_threshold_delete variable and related are used.
-
-
-.TP
-.B score_threshold_delete
-.nf
-Type: number
-Default: \-1
-.fi
-.IP
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked for deletion by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message for deletion.
-
-
-.TP
-.B score_threshold_flag
-.nf
-Type: number
-Default: 9999
-.fi
-.IP
-Messages which have been assigned a score greater than or equal to this
-variable's value are automatically marked \(rqflagged\(rq.
-
-
-.TP
-.B score_threshold_read
-.nf
-Type: number
-Default: \-1
-.fi
-.IP
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked as read by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message read.
-
-
-.TP
-.B send_charset
-.nf
-Type: string
-Default: \(lqus\-ascii:iso\-8859\-1:utf\-8\(rq
-.fi
-.IP
-A colon\-delimited list of character sets for outgoing messages. Mutt will use the
-first character set into which the text can be converted exactly.
-If your $charset is not \(lqiso\-8859\-1\(rq and recipients may not
-understand \(lqUTF\-8\(rq, it is advisable to include in the list an
-appropriate widely used standard character set (such as
-\(lqiso\-8859\-2\(rq, \(lqkoi8\-r\(rq or \(lqiso\-2022\-jp\(rq) either instead of or after
-\(lqiso\-8859\-1\(rq.
-.IP
-In case the text cannot be converted into one of these exactly,
-mutt uses $charset as a fallback.
-
-
-.TP
-.B sendmail
-.nf
-Type: path
-Default: \(lq/usr/sbin/sendmail \-oem \-oi\(rq
-.fi
-.IP
-Specifies the program and arguments used to deliver mail sent by Mutt.
-Mutt expects that the specified program interprets additional
-arguments as recipient addresses.
-
-
-.TP
-.B sendmail_wait
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-Specifies the number of seconds to wait for the $sendmail process
-to finish before giving up and putting delivery in the background.
-.IP
-Mutt interprets the value of this variable as follows:
-.RS
-.PD 0
-.TP
->0
-number of seconds to wait for sendmail to finish before continuing
-.TP
-0
-wait forever for sendmail to finish
-.TP
-<0
-always put sendmail in the background without waiting
-.RE
-.PD 1
-.IP
-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.
-
-
-.TP
-.B shell
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Command to use when spawning a subshell. By default, the user's login
-shell from \fC/etc/passwd\fP is used.
-
-
-.TP
-.B sig_dashes
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-If \fIset\fP, a line containing \(lq\-\- \(rq (note the trailing space) will be inserted before your
-$signature. It is \fBstrongly\fP recommended that you not \fIunset\fP
-this variable unless your signature contains just your name. The
-reason for this is because many software packages use \(lq\-\- \\n\(rq to
-detect your signature. For example, Mutt has the ability to highlight
-the signature in a different color in the builtin pager.
-
-
-.TP
-.B sig_on_top
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, the signature will be included before any quoted or forwarded
-text. It is \fBstrongly\fP 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.
-
-
-.TP
-.B signature
-.nf
-Type: path
-Default: \(lq~/.signature\(rq
-.fi
-.IP
-Specifies the filename of your signature, which is appended to all
-outgoing messages. If the filename ends with a pipe (\(lq|\(rq), it is
-assumed that filename is a shell command and input should be read from
-its standard output.
-
-
-.TP
-.B simple_search
-.nf
-Type: string
-Default: \(lq~f %s | ~s %s\(rq
-.fi
-.IP
-Specifies how Mutt should expand a simple search into a real search
-pattern. A simple search is one that does not contain any of the \(lq~\(rq pattern
-operators. See \(lqpatterns\(rq for more information on search patterns.
-.IP
-For example, if you simply type \(lqjoe\(rq at a search or limit prompt, Mutt
-will automatically expand it to the value specified by this variable by
-replacing \(lq%s\(rq with the supplied string.
-For the default value, \(lqjoe\(rq would be expanded to: \(lq~f joe | ~s joe\(rq.
-
-
-.TP
-.B smart_wrap
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls the display of lines longer than the screen width in the
-internal pager. If \fIset\fP, long lines are wrapped at a word boundary. If
-\fIunset\fP, lines are simply wrapped at the screen edge. Also see the
-$markers variable.
-
-
-.TP
-.B smileys
-.nf
-Type: regular expression
-Default: \(lq(>From )|(:[\-^]?[][)(><}{|/DP])\(rq
-.fi
-.IP
-The \fIpager\fP uses this variable to catch some common false
-positives of $quote_regexp, most notably smileys and not consider
-a line quoted text if it also matches $smileys. This mostly
-happens at the beginning of a line.
-
-
-.TP
-.B sleep_time
-.nf
-Type: number
-Default: 1
-.fi
-.IP
-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.
-
-
-.TP
-.B smtp_authenticators
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-This is a colon\-delimited list of authentication methods mutt may
-attempt to use to log in to an SMTP server, in the order mutt should
-try them. Authentication methods are any SASL mechanism, eg
-\(lqdigest\-md5\(rq, \(lqgssapi\(rq or \(lqcram\-md5\(rq.
-This option is case\-insensitive. If it is \(lqunset\(rq
-(the default) mutt will try all available methods, in order from
-most\-secure to least\-secure.
-.IP
-Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set smtp_authenticators=\(rqdigest\-md5:cram\-md5\(rq
-
-.fi
-.ec
-.ft P
-.sp
-
-
-.TP
-.B smtp_pass
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the password for your SMTP account. If \fIunset\fP, Mutt will
-prompt you for your password when you first send mail via SMTP.
-See $smtp_url to configure mutt to send mail via SMTP.
-.IP
-\fBWarning\fP: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-
-
-.TP
-.B smtp_url
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Defines the SMTP smarthost where sent messages should relayed for
-delivery. This should take the form of an SMTP URL, eg:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-smtp[s]://[user[:pass]@]host[:port]/
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-\\.\\.\\. where \(lq[...]\(rq denotes an optional part.
-Setting this variable overrides the value of the $sendmail
-variable.
-
-
-.TP
-.B sort
-.nf
-Type: sort order
-Default: date
-.fi
-.IP
-Specifies how to sort messages in the \(lqindex\(rq menu. Valid values
-are:
-.RS
-.PD 0
-.TP
-\(hy date or date\-sent
-.TP
-\(hy date\-received
-.TP
-\(hy from
-.TP
-\(hy mailbox\-order (unsorted)
-.TP
-\(hy score
-.TP
-\(hy size
-.TP
-\(hy spam
-.TP
-\(hy subject
-.TP
-\(hy threads
-.TP
-\(hy to
-.RE
-.PD 1
-.IP
-You may optionally use the \(lqreverse\-\(rq prefix to specify reverse sorting
-order (example: \(lq\fCset sort=reverse\-date\-sent\fP\(rq).
-.IP
-\fBNote:\fP On Debian systems, this option is set by default to
-\(lqthreads\(rq in /etc/Muttrc.
-
-
-.TP
-.B sort_alias
-.nf
-Type: sort order
-Default: alias
-.fi
-.IP
-Specifies how the entries in the \(lqalias\(rq menu are sorted. The
-following are legal values:
-.RS
-.PD 0
-.TP
-\(hy address (sort alphabetically by email address)
-.TP
-\(hy alias (sort alphabetically by alias name)
-.TP
-\(hy unsorted (leave in order specified in .muttrc)
-.RE
-.PD 1
-
-.TP
-.B sort_aux
-.nf
-Type: sort order
-Default: date
-.fi
-.IP
-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
-\(lqthreads\(rq (in that case, mutt will just use \(lqdate\-sent\(rq). You can also
-specify the \(lqlast\-\(rq prefix in addition to the \(lqreverse\-\(rq prefix, but \(lqlast\-\(rq
-must come after \(lqreverse\-\(rq. The \(lqlast\-\(rq 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,
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set sort_aux=last\-date\-received
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-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 \(lq\fCset sort=reverse\-threads\fP\(rq.)
-.IP
-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).
-
-
-.TP
-.B sort_browser
-.nf
-Type: sort order
-Default: alpha
-.fi
-.IP
-Specifies how to sort entries in the file browser. By default, the
-entries are sorted alphabetically. Valid values:
-.RS
-.PD 0
-.TP
-\(hy alpha (alphabetically)
-.TP
-\(hy date
-.TP
-\(hy size
-.TP
-\(hy unsorted
-.RE
-.PD 1
-.IP
-You may optionally use the \(lqreverse\-\(rq prefix to specify reverse sorting
-order (example: \(lq\fCset sort_browser=reverse\-date\fP\(rq).
-
-
-.TP
-.B sort_re
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-This variable is only useful when sorting by threads with
-$strict_threads \fIunset\fP. In that case, it changes the heuristic
-mutt uses to thread messages by subject. With $sort_re \fIset\fP, mutt 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_re \fIunset\fP, mutt will attach
-the message whether or not this is the case, as long as the
-non\-$reply_regexp parts of both messages are identical.
-
-
-.TP
-.B spam_separator
-.nf
-Type: string
-Default: \(lq,\(rq
-.fi
-.IP
-This variable controls what happens when multiple spam headers
-are matched: if \fIunset\fP, each successive header will overwrite any
-previous matches value for the spam label. If \fIset\fP, each successive
-match will append to the previous, using this variable's value as a
-separator.
-
-
-.TP
-.B spoolfile
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-If your spool mailbox is in a non\-default place where Mutt cannot find
-it, you can specify its location with this variable. Mutt will
-automatically set this variable to the value of the environment
-variable \fC$MAIL\fP if it is not set.
-
-
-.TP
-.B status_chars
-.nf
-Type: string
-Default: \(lq\-*%A\(rq
-.fi
-.IP
-Controls the characters used by the \(lq%r\(rq 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 \fC<toggle\-write>\fP operation, bound by default to \(lq%\(rq). 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).
-
-
-.TP
-.B status_format
-.nf
-Type: string
-Default: \(lq\-%r\-Mutt: %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)\-\-\-\(rq
-.fi
-.IP
-Controls the format of the status line displayed in the \(lqindex\(rq
-menu. This string is similar to $index_format, but has its own
-set of \fCprintf(3)\fP\-like sequences:
-.RS
-.PD 0
-.TP
-%b
-number of mailboxes with new mail *
-.TP
-%d
-number of deleted messages *
-.TP
-%f
-the full pathname of the current mailbox
-.TP
-%F
-number of flagged messages *
-.TP
-%h
-local hostname
-.TP
-%l
-size (in bytes) of the current mailbox *
-.TP
-%L
-size (in bytes) of the messages shown
-(i.e., which match the current limit) *
-.TP
-%m
-the number of messages in the mailbox *
-.TP
-%M
-the number of messages shown (i.e., which match the current limit) *
-.TP
-%n
-number of new messages in the mailbox *
-.TP
-%o
-number of old unread messages *
-.TP
-%p
-number of postponed messages *
-.TP
-%P
-percentage of the way through the index
-.TP
-%r
-modified/read\-only/won't\-write/attach\-message indicator,
-according to $status_chars
-.TP
-%s
-current sorting mode ($sort)
-.TP
-%S
-current aux sorting method ($sort_aux)
-.TP
-%t
-number of tagged messages *
-.TP
-%u
-number of unread messages *
-.TP
-%v
-Mutt version string
-.TP
-%V
-currently active limit pattern, if any *
-.TP
-%>X
-right justify the rest of the string and pad with \(lqX\(rq
-.TP
-%|X
-pad to the end of the line with \(lqX\(rq
-.TP
-%*X
-soft\-fill with character \(lqX\(rq as pad
-.RE
-.PD 1
-.IP
-For an explanation of \(lqsoft\-fill\(rq, see the $index_format documentation.
-.IP
-* = can be optionally printed if nonzero
-.IP
-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:
-.IP
-\fC%?<sequence_char>?<optional_string>?\fP
-.IP
-where \fIsequence_char\fP is a character from the table above, and
-\fIoptional_string\fP is the string you would like printed if
-\fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
-other sequences as well as normal text, but you may \fBnot\fP nest
-optional strings.
-.IP
-Here is an example illustrating how to optionally print the number of
-new messages in a mailbox:
-.IP
-\fC%?n?%n new messages.?\fP
-.IP
-You can also switch between two strings using the following construct:
-.IP
-\fC%?<sequence_char>?<if_string>&<else_string>?\fP
-.IP
-If the value of \fIsequence_char\fP is non\-zero, \fIif_string\fP will
-be expanded, otherwise \fIelse_string\fP will be expanded.
-.IP
-You can force the result of any \fCprintf(3)\fP\-like sequence to be lowercase
-by prefixing the sequence character with an underscore (\(lq_\(rq) sign.
-For example, if you want to display the local hostname in lowercase,
-you would use: \(lq\fC%_h\fP\(rq.
-.IP
-If you prefix the sequence character with a colon (\(lq:\(rq) character, mutt
-will replace any dots in the expansion by underscores. This might be helpful
-with IMAP folders that don't like dots in folder names.
-
-
-.TP
-.B status_on_top
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Setting this variable causes the \(lqstatus bar\(rq to be displayed on
-the first line of the screen rather than near the bottom. If $help
-is \fIset\fP, too it'll be placed at the bottom.
-
-
-.TP
-.B strict_threads
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-If \fIset\fP, threading will only make use of the \(lqIn\-Reply\-To\(rq and
-\(lqReferences:\(rq fields when you $sort by message threads. By
-default, messages with the same subject are grouped together in
-\(lqpseudo threads.\(rq. This may not always be desirable, such as in a
-personal mailbox where you might have several unrelated messages with
-the subjects like \(lqhi\(rq which will get grouped together. See also
-$sort_re for a less drastic way of controlling this
-behaviour.
-
-
-.TP
-.B suspend
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIunset\fP, mutt won't stop when the user presses the terminal's
-\fIsusp\fP key, usually \(lq^Z\(rq. This is useful if you run mutt
-inside an xterm using a command like \(lq\fCxterm \-e mutt\fP\(rq.
-
-
-.TP
-.B text_flowed
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will generate \(lqformat=flowed\(rq bodies with a content type
-of \(lq\fCtext/plain; format=flowed\fP\(rq.
-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.
-.IP
-Note that $indent_string is ignored when this option is \fIset\fP.
-
-
-.TP
-.B thread_received
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt uses the date received rather than the date sent
-to thread messages by subject.
-
-
-.TP
-.B thorough_search
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Affects the \fC~b\fP and \fC~h\fP search operations described in
-section \(lqpatterns\(rq. If \fIset\fP, the headers and body/attachments of
-messages to be searched are decoded before searching. If \fIunset\fP,
-messages are searched as they appear in the folder.
-.IP
-Users searching attachments or for non\-ASCII characters should \fIset\fP
-this value because decoding also includes MIME parsing/decoding and possible
-character set conversions. Otherwise mutt will attempt to match against the
-raw message received (for example quoted\-printable encoded or with encoded
-headers) which may lead to incorrect search results.
-
-
-.TP
-.B tilde
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, the internal\-pager will pad blank lines to the bottom of the
-screen with a tilde (\(lq~\(rq).
-
-
-.TP
-.B time_inc
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-Along with $read_inc, $write_inc, and $net_inc, this
-variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than $time_inc milliseconds
-apart. This can improve throughput on systems with slow terminals,
-or when running mutt on a remote system.
-.IP
-Also see the \(lqtuning\(rq section of the manual for performance considerations.
-
-
-.TP
-.B timeout
-.nf
-Type: number
-Default: 600
-.fi
-.IP
-When Mutt is waiting for user input either idleing in menus or
-in an interactive prompt, Mutt would block until input is
-present. Depending on the context, this would prevent certain
-operations from working, like checking for new mail or keeping
-an IMAP connection alive.
-.IP
-This variable controls how many seconds Mutt will at most wait
-until it aborts waiting for input, performs these operations and
-continues to wait for input.
-.IP
-A value of zero or less will cause Mutt to never time out.
-
-
-.TP
-.B tmpdir
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-This variable allows you to specify where Mutt will place its
-temporary files needed for displaying and composing messages. If
-this variable is not set, the environment variable \fC$TMPDIR\fP is
-used. If \fC$TMPDIR\fP is not set then \(lq\fC/tmp\fP\(rq is used.
-
-
-.TP
-.B to_chars
-.nf
-Type: string
-Default: \(lq +TCFL\(rq
-.fi
-.IP
-Controls the character used to indicate mail addressed to you. The
-first character is the one used when the mail is \fInot\fP addressed to your
-address. The second is used when you are the only
-recipient of the message. The third is when your address
-appears in the \(lqTo:\(rq header field, but you are not the only recipient of
-the message. The fourth character is used when your
-address is specified in the \(lqCc:\(rq header field, but you are not the only
-recipient. The fifth character is used to indicate mail that was sent
-by \fIyou\fP. The sixth character is used to indicate when a mail
-was sent to a mailing\-list you subscribe to.
-
-
-.TP
-.B trash
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-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.
-.IP
-NOTE: When you delete a message in the trash folder, it is really
-deleted, so that you have a way to clean the trash.
-
-
-.TP
-.B tunnel
-.nf
-Type: string
-Default: \(lq\(rq
-.fi
-.IP
-Setting this variable will cause mutt 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/SMTP server. Example:
-
-.IP
-.DS
-.sp
-.ft CR
-.nf
-set tunnel=\(rqssh \-q mailhost.net /usr/local/libexec/imapd\(rq
-
-.fi
-.ec
-.ft P
-.sp
-.IP
-Note: For this example to work you must be able to log in to the remote
-machine without having to enter a password.
-
-
-.TP
-.B use_8bitmime
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-\fBWarning:\fP do not set this variable unless you are using a version
-of sendmail which supports the \fC\-B8BITMIME\fP flag (such as sendmail
-8.8.x) or you may not be able to send mail.
-.IP
-When \fIset\fP, Mutt will invoke $sendmail with the \fC\-B8BITMIME\fP
-flag when sending 8\-bit messages to enable ESMTP negotiation.
-
-
-.TP
-.B use_domain
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will qualify all local addresses (ones without the
-\(lq@host\(rq portion) with the value of $hostname. If \fIunset\fP, no
-addresses will be qualified.
-
-
-.TP
-.B use_envelope_from
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-When \fIset\fP, mutt will set the \fIenvelope\fP sender of the message.
-If $envelope_from_address is \fIset\fP, it will be used as the sender
-address. If \fIunset\fP, mutt will attempt to derive the sender from the
-\(lqFrom:\(rq header.
-.IP
-Note that this information is passed to sendmail command using the
-\fC\-f\fP command line switch. Therefore setting this option is not useful
-if the $sendmail variable already contains \fC\-f\fP or if the
-executable pointed to by $sendmail doesn't support the \fC\-f\fP switch.
-
-
-.TP
-.B use_from
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will generate the \(lqFrom:\(rq header field when
-sending messages. If \fIunset\fP, no \(lqFrom:\(rq header field will be
-generated unless the user explicitly sets one using the \(lqmy_hdr\(rq
-command.
-
-
-.TP
-.B use_idn
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will show you international domain names decoded.
-Note: You can use IDNs for addresses even if this is \fIunset\fP.
-This variable only affects decoding.
-
-
-.TP
-.B use_ipv6
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, Mutt will look for IPv6 addresses of hosts it tries to
-contact. If this option is \fIunset\fP, Mutt will restrict itself to IPv4 addresses.
-Normally, the default should work.
-
-
-.TP
-.B user_agent
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will add a \(lqUser\-Agent:\(rq header to outgoing
-messages, indicating which version of mutt was used for composing
-them.
-
-
-.TP
-.B visual
-.nf
-Type: path
-Default: \(lq\(rq
-.fi
-.IP
-Specifies the visual editor to invoke when the \(lq\fC~v\fP\(rq command is
-given in the builtin editor.
-
-
-.TP
-.B wait_key
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether Mutt will ask you to press a key after an external command
-has been invoked by these functions: \fC<shell\-escape>\fP,
-\fC<pipe\-message>\fP, \fC<pipe\-entry>\fP, \fC<print\-message>\fP,
-and \fC<print\-entry>\fP commands.
-.IP
-It is also used when viewing attachments with \(lqauto_view\(rq, provided
-that the corresponding mailcap entry has a \fIneedsterminal\fP flag,
-and the external program is interactive.
-.IP
-When \fIset\fP, Mutt will always ask for a key. When \fIunset\fP, Mutt will wait
-for a key only if the external command returned a non\-zero status.
-
-
-.TP
-.B weed
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-When \fIset\fP, mutt will weed headers when displaying, forwarding,
-printing, or replying to messages.
-
-
-.TP
-.B wrap
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-When set to a positive value, mutt will wrap text at $wrap characters.
-When set to a negative value, mutt will wrap text so that there are $wrap
-characters of empty space on the right side of the terminal.
-
-
-.TP
-.B wrap_search
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether searches wrap around the end.
-.IP
-When \fIset\fP, searches will wrap around the first (or last) item. When
-\fIunset\fP, incremental searches will not wrap.
-
-
-.TP
-.B wrapmargin
-.nf
-Type: number
-Default: 0
-.fi
-.IP
-(DEPRECATED) Equivalent to setting $wrap with a negative value.
-
-
-.TP
-.B write_inc
-.nf
-Type: number
-Default: 10
-.fi
-.IP
-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.
-.IP
-Also see the $read_inc, $net_inc and $time_inc variables and the
-\(lqtuning\(rq section of the manual for performance considerations.
-
-
-.TP
-.B write_bcc
-.nf
-Type: boolean
-Default: yes
-.fi
-.IP
-Controls whether mutt writes out the \(lqBcc:\(rq header when preparing
-messages to be sent. Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see $smtp_url), this
-option does nothing: mutt will never write out the \(lqBcc:\(rq header
-in this case.
-.IP
-\fBNote:\fP On Debian systems, exim4 and postfix strip BCC headers by
-default. The above warning applies to exim3 users, see /etc/Muttrc.
-
-
-.TP
-.B xterm_icon
-.nf
-Type: string
-Default: \(lqM%?n?AIL&ail?\(rq
-.fi
-.IP
-Controls the format of the icon title, as long as xterm_set_titles
-is enabled. This string is identical in formatting to the one used by
-\(lq$status_format\(rq.
-
-
-.TP
-.B xterm_set_titles
-.nf
-Type: boolean
-Default: no
-.fi
-.IP
-Controls whether mutt sets the xterm title bar and icon name
-(as long as you are in an appropriate terminal).
-
-
-.TP
-.B xterm_title
-.nf
-Type: string
-Default: \(lqMutt with %?m?%m messages&no messages?%?n? [%n NEW]?\(rq
-.fi
-.IP
-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 \(lq$status_format\(rq.
-
-
-.\" -*-nroff-*-
-.SH SEE ALSO
-.PP
-.BR iconv (1),
-.BR iconv (3),
-.BR mailcap (5),
-.BR maildir (5),
-.BR mbox (5),
-.BR mutt (1),
-.BR printf (3),
-.BR regex (7),
-.BR strftime (3)
-.PP
-The Mutt Manual
-.PP
-The Mutt home page: http://www.mutt.org/
-.SH AUTHOR
-.PP
-Michael Elkins, and others. Use <mutt-dev@mutt.org> to contact
-the developers.
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Optional features</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="mimesupport.html" title="Chapter 5. Mutt's MIME Support" /><link rel="next" href="tuning.html" title="Chapter 7. Performance tuning" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Optional features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="mimesupport.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="tuning.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="optionalfeatures"></a>Chapter 6. Optional features</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="optionalfeatures.html#optionalfeatures-notes">1. General notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#compile-time-features">1.1. Enabling/disabling features</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#url-syntax">1.2. URL syntax</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#ssl">2. SSL/TLS Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#pop">3. POP3 Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#imap">4. IMAP Support</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#imap-browser">4.1. The Folder Browser</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#imap-authentication">4.2. Authentication</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#smtp">5. SMTP Support</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#account-hook">6. Managing multiple accounts</a></span></dt><dt><span class="sect1"><a href="optionalfeatures.html#caching">7. Local caching</a></span></dt><dd><dl><dt><span class="sect2"><a href="optionalfeatures.html#header-caching">7.1. Header caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#body-caching">7.2. Body caching</a></span></dt><dt><span class="sect2"><a href="optionalfeatures.html#maint-cache">7.3. Maintenance</a></span></dt></dl></dd><dt><span class="sect1"><a href="optionalfeatures.html#exact-address">8. Exact address generation</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="optionalfeatures-notes"></a>1. General notes</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compile-time-features"></a>1.1. Enabling/disabling features</h3></div></div></div><p>
-Mutt supports several of optional features which can be enabled or
-disabled at compile-time by giving the <span class="emphasis"><em>configure</em></span> script
-certain arguments. These are listed in the “<span class="quote">Optional features</span>” section of
-the <span class="emphasis"><em>configure --help</em></span> output.
-</p><p>
-Which features are enabled or disabled can later be determined from the
-output of <code class="literal">mutt -v</code>. If a compile option starts with
-“<span class="quote">+</span>” it is enabled and disabled if prefixed with “<span class="quote">-</span>”. For example, if
-mutt was compiled using GnuTLS for encrypted communication instead of
-OpenSSL, <code class="literal">mutt -v</code> would contain:
-</p><pre class="screen">
--USE_SSL_OPENSSL +USE_SSL_GNUTLS</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="url-syntax"></a>1.2. URL syntax</h3></div></div></div><p>
-Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
-to access servers using URLs. The canonical syntax for specifying URLs
-in mutt is (an item enclosed in <code class="literal">[]</code> means it is optional and
-may be omitted):
-</p><pre class="screen">
-proto[s]://[username[:password]@]server[:port]/[path]
-</pre><p>
-<code class="literal">proto</code> is the communication protocol:
-<code class="literal">imap</code> for IMAP, <code class="literal">pop</code> for POP3 and
-<code class="literal">smtp</code> for SMTP. If “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”
-is appended, mutt will attempt to establish an encrypted communication
-using SSL or TLS. If no explicit port is given, mutt will use the
-system's default for the given protocol.
-</p><p>
-Since all protocols by mutt support authentication, the username may be
-given directly in the URL instead of using the <code class="literal">pop_user</code> or
-<code class="literal">imap_user</code> variables. It may contain the “<span class="quote">@</span>” symbol
-being used by many mail systems as part of the login name. A password can be
-given, too but is not recommended if the URL is specified in a configuration
-file on disk.
-</p><p>
-The optional path is only relevant for IMAP.
-</p><p>
-For IMAP for example, you can select an alternative port by specifying it with the
-server: <code class="literal">imap://imapserver:port/INBOX</code>. You can also specify different
-username for each folder: <code class="literal">imap://username@imapserver[:port]/INBOX</code>
-or <code class="literal">imap://username2@imapserver[:port]/path/to/folder</code>.
-Replacing <code class="literal">imap://</code> by <code class="literal">imaps://</code>
-would make mutt attempt to connect using SSL or TLS on a different port
-to encrypt the communication.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="ssl"></a>2. SSL/TLS Support</h2></div></div></div><p>
-If mutt is compiled with IMAP, POP3 and/or SMTP support, it can also be
-compiled with support for SSL or TLS using either OpenSSL or GnuTLS (
-by running the <span class="emphasis"><em>configure</em></span> script with the
-<span class="emphasis"><em>--enable-ssl=...</em></span> option for OpenSSL or
-<span class="emphasis"><em>--enable-gnutls=...</em></span> for GnuTLS). Mutt can then
-attempt to encrypt communication with remote servers if these protocols
-are suffixed with “<span class="quote">s</span>” for “<span class="quote">secure communication</span>”.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="pop"></a>3. POP3 Support</h2></div></div></div><p>
-If Mutt was compiled with POP3 support (by running the <span class="emphasis"><em>configure</em></span>
-script with the <span class="emphasis"><em>--enable-pop</em></span> flag), it has the ability to work
-with mailboxes located on a remote POP3 server and fetch mail for local
-browsing.
-</p><p>
-Remote POP3 servers can be accessed using URLs with the <code class="literal">pop</code> protocol
-for unencrypted and <code class="literal">pops</code> for encrypted
-communication, see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details.
-</p><p>
-Polling for new mail is more expensive over POP3 than locally. For this
-reason the frequency at which Mutt will check for mail remotely can be
-controlled by the
-<a class="link" href="reference.html#pop-checkinterval" title="3.215. pop_checkinterval">$pop_checkinterval</a>
-variable, which defaults to every 60 seconds.
-</p><a id="fetch-mail"></a><p>
-Another way to access your POP3 mail is the <code class="literal"><fetch-mail$</code> function
-(default: G). It allows to connect to <a class="link" href="reference.html#pop-host" title="3.217. pop_host">$pop_host</a>, fetch all your new mail and place it in the
-local <a class="link" href="reference.html#spoolfile" title="3.276. spoolfile">$spoolfile</a>. After this
-point, Mutt runs exactly as if the mail had always been local.
-</p><div class="note"><h3 class="title">Note</h3><p>
-If you only need to fetch all messages to a
-local mailbox you should consider using a specialized program, such as
-<code class="literal">fetchmail</code>, <code class="literal">getmail</code> or similar.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="imap"></a>4. IMAP Support</h2></div></div></div><p>
-If Mutt was compiled with IMAP support (by running the <span class="emphasis"><em>configure</em></span>
-script with the <span class="emphasis"><em>--enable-imap</em></span> flag), it has the ability to work
-with folders located on a remote IMAP server.
-</p><p>
-You can access the remote inbox by selecting the folder by its URL
-(see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a> for details) using the
-<code class="literal">imap</code> or <code class="literal">imaps</code> protocol.
-Alternatively, a pine-compatible notation is also supported, ie
-<code class="literal">{[username@]imapserver[:port][/ssl]}path/to/folder</code>
-</p><p>
-Note that not all servers use “<span class="quote">/</span>” as the hierarchy separator. Mutt should
-correctly notice which separator is being used by the server and convert
-paths accordingly.
-</p><p>
-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
-<span class="emphasis"><em>toggle-subscribed</em></span> command. See also the
-<a class="link" href="reference.html#imap-list-subscribed" title="3.89. imap_list_subscribed">$imap_list_subscribed</a> variable.
-</p><p>
-Polling for new mail on an IMAP server can cause noticeable delays. So, you'll
-want to carefully tune the
-<a class="link" href="reference.html#mail-check" title="3.105. mail_check">$mail_check</a>
-and
-<a class="link" href="reference.html#timeout" title="3.287. timeout">$timeout</a>
-variables. Personally I use
-</p><pre class="screen">
-set mail_check=90
-set timeout=15
-</pre><p>
-with relatively good results over my slow modem line.
-</p><div class="note"><h3 class="title">Note</h3><p>
-Note that if you are using mbox as the mail store on UW servers prior to
-v12.250, the server has been reported to disconnect a client if another client
-selects the same folder.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-browser"></a>4.1. The Folder Browser</h3></div></div></div><p>
-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:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-In lieu 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.
-</p></li><li><p>
-For the case where an entry can contain both messages and
-subfolders, the selection key (bound to <code class="literal">enter</code> by default)
-will choose to descend into the subfolder view. If you wish to view
-the messages in that folder, you must use <code class="literal">view-file</code> instead
-(bound to <code class="literal">space</code> by default).
-</p></li><li><p>
-You can create, delete and rename mailboxes with the
-<code class="literal">create-mailbox</code>, <code class="literal">delete-mailbox</code>, and
-<code class="literal">rename-mailbox</code> commands (default bindings: <code class="literal">C</code>,
-<code class="literal">d</code> and <code class="literal">r</code>, respectively). You may also
-<code class="literal">subscribe</code> and <code class="literal">unsubscribe</code> to mailboxes (normally
-these are bound to <code class="literal">s</code> and <code class="literal">u</code>, respectively).
-</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authentication"></a>4.2. Authentication</h3></div></div></div><p>
-Mutt 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".
-</p><p>
-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 library
-installed on your system and compile mutt with the <span class="emphasis"><em>--with-sasl</em></span> flag.
-</p><p>
-Mutt will try whichever methods are compiled in and available on the server,
-in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN.
-</p><p>
-There are a few variables which control authentication:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-<a class="link" href="reference.html#imap-user" title="3.96. imap_user">$imap_user</a> - 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 (ie by using a mailbox name of the form
-<code class="literal">{user@host}</code>).
-</p></li><li><p>
-<a class="link" href="reference.html#imap-pass" title="3.91. imap_pass">$imap_pass</a> - a
-password which you may preset, used by all authentication methods where
-a password is needed.
-</p></li><li><p>
-<a class="link" href="reference.html#imap-authenticators" title="3.83. imap_authenticators">$imap_authenticators</a> - 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).
-</p></li></ul></div></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="smtp"></a>5. SMTP Support</h2></div></div></div><p>
-Besides supporting traditional mail delivery through a
-sendmail-compatible program, mutt supports delivery through SMTP if it
-was configured and built with <code class="literal">--enable-smtp</code>.
-</p><p>
-If the configuration variable
-<a class="link" href="reference.html#smtp-url" title="3.269. smtp_url">$smtp_url</a> is set, mutt
-will contact the given SMTP server to deliver messages; if it is unset,
-mutt will use the program specified by <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a>.
-</p><p>
-For details on the URL syntax, please see <a class="xref" href="optionalfeatures.html#url-syntax" title="1.2. URL syntax">Section 1.2, “URL syntax”</a>.
-</p><p>
-The built-in SMTP support supports encryption (the <code class="literal">smtps</code> protocol
-using SSL or TLS) as well as SMTP authentication using SASL. The authentication mechanisms
-for SASL are specified in <a class="link" href="reference.html#smtp-authenticators" title="3.267. smtp_authenticators">$smtp_authenticators</a>
-defaulting to an empty list which makes mutt try all available methods
-from most-secure to least-secure.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="account-hook"></a>6. Managing multiple accounts</h2></div></div></div><p>
-If you happen to have accounts on multiple IMAP, POP and/or SMTP 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 which includes (for example) polling for new mail, storing Fcc
-messages and saving messages to a folder. As a consequence,
-account-hook should only be used to set connection-related settings such
-as passwords or tunnel commands but not settings such as sender
-address or name (because in general it should be considered unpredictable
-which account-hook was last used).
-</p><p>
-Some examples:
-</p><pre class="screen">
-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"'
-account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"'
-</pre></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="caching"></a>7. Local caching</h2></div></div></div><p>
-Mutt contains two types of local caching: <span class="emphasis"><em>(1)</em></span>
-the so-called “<span class="quote">header caching</span>” and <span class="emphasis"><em>(2)</em></span> the
-so-called “<span class="quote">body caching</span>” which are both described in this section.
-</p><p>
-Header caching is optional as it depends on external libraries, body
-caching is always enabled if mutt is compiled with POP and/or IMAP
-support as these use it (body caching requires no external library).
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-caching"></a>7.1. Header caching</h3></div></div></div><p>
-Mutt provides optional support for caching message headers for the
-following types of folders: IMAP, POP, Maildir and MH. Header caching
-greatly improves speed because for remote folders, headers
-usually only need to be downloaded once. For Maildir and MH, reading the
-headers from a single file is much faster than looking at possibly
-thousands of single files (since Maildir and MH use one file per message.)
-</p><p>
-Header caching can be enabled via the configure script and the
-<span class="emphasis"><em>--enable-hcache</em></span> option. It's not turned on
-by default because external database libraries are required: one
-of tokyocabinet, qdbm, gdbm or bdb must be present.
-</p><p>
-If enabled, <a class="link" href="reference.html#header-cache" title="3.109. header_cache">$header_cache</a> can be
-used to either point to a file or a directory. If set to point to
-a file, one database file for all folders will be used (which may
-result in lower performance), but one file per folder if it points
-to a directory.
-</p><p>
-For the one-file-per-folder case, database files for remote folders
-will be named according to their URL while database files for local
-folders will be named by the MD5 checksums of their path. These database
-files may be safely removed if a system is short on space. You
-can compute the name of the header cache file for a particular local folder
-through a command like the following:
-</p><pre class="screen">
-$ printf '%s' '/path/to/folder' | md5sum
-</pre><p>
-The <code class="literal">md5sum</code> command may also be
-named <code class="literal">md5</code>, depending on your operating system.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="body-caching"></a>7.2. Body caching</h3></div></div></div><p>
-Both cache methods can be combined using the same directory for storage
-(and for IMAP/POP even provide meaningful file names) which simplifies
-manual maintenance tasks.
-</p><p>
-In addition to caching message headers only, mutt can also cache
-whole message bodies. This results in faster display of messages
-for POP and IMAP folders because messages usually have to be
-downloaded only once.
-</p><p>
-For configuration, the variable <a class="link" href="reference.html#message-cachedir" title="3.133. message_cachedir">$message_cachedir</a> must point to a
-directory. There, mutt will create a hierarchy of subdirectories
-named like: <code class="literal">proto:user@hostname</code> where
-<code class="literal">proto</code> is either “<span class="quote">pop</span>” or “<span class="quote">imap.</span>” Within
-there for each folder, mutt stores messages in single files (just
-like Maildir) so that with manual symlink creation these cache
-directories can be examined with mutt as read-only Maildir folders.
-</p><p>
-All files can be removed as needed if the consumed disk space
-becomes an issue as mutt will silently fetch missing items again.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maint-cache"></a>7.3. Maintenance</h3></div></div></div><p>
-Mutt does not (yet) support maintenance features for header cache
-database files so that files have to be removed in case they grow too
-big. It depends on the database library used for header caching whether
-disk space freed by removing messages is re-used.
-</p><p>
-For body caches, mutt can keep the local cache in sync with the
-remote mailbox if the
-<a class="link" href="reference.html#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a>
-variable is set. Cleaning means to remove messages from the cache which
-are no longer present in the mailbox which only happens when other mail
-clients or instances of mutt using a different body cache location
-delete messages (Mutt itself removes deleted messages from the cache
-when syncing a mailbox). As cleaning can take a noticeable amount of time,
-it should not be set in general but only occasionally.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="exact-address"></a>8. Exact address generation</h2></div></div></div><p>
-Mutt supports the “<span class="quote">Name <user@host></span>” address syntax for reading and
-writing messages, the older “<span class="quote">user@host (Name)</span>” syntax is only supported when
-reading messages. The <span class="emphasis"><em>--enable-exact-address</em></span>
-switch can be given to configure to build it with write-support
-for the latter syntax. <code class="literal">EXACT_ADDRESS</code> in the output of
-<code class="literal">mutt -v</code> indicates whether it's supported.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="mimesupport.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="tuning.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Mutt's MIME Support </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Performance tuning</td></tr></table></div></body></html>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 8. Reference</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="tuning.html" title="Chapter 7. Performance tuning" /><link rel="next" href="miscellany.html" title="Chapter 9. Miscellany" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 8. Reference</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="tuning.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="miscellany.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="reference"></a>Chapter 8. Reference</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="reference.html#commandline">1. Command line options</a></span></dt><dt><span class="sect1"><a href="reference.html#commands">2. Configuration Commands</a></span></dt><dt><span class="sect1"><a href="reference.html#variables">3. Configuration variables</a></span></dt><dd><dl><dt><span class="sect2"><a href="reference.html#abort-nosubject">3.1. abort_nosubject</a></span></dt><dt><span class="sect2"><a href="reference.html#abort-unmodified">3.2. abort_unmodified</a></span></dt><dt><span class="sect2"><a href="reference.html#alias-file">3.3. alias_file</a></span></dt><dt><span class="sect2"><a href="reference.html#alias-format">3.4. alias_format</a></span></dt><dt><span class="sect2"><a href="reference.html#allow-8bit">3.5. allow_8bit</a></span></dt><dt><span class="sect2"><a href="reference.html#allow-ansi">3.6. allow_ansi</a></span></dt><dt><span class="sect2"><a href="reference.html#arrow-cursor">3.7. arrow_cursor</a></span></dt><dt><span class="sect2"><a href="reference.html#ascii-chars">3.8. ascii_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#askbcc">3.9. askbcc</a></span></dt><dt><span class="sect2"><a href="reference.html#askcc">3.10. askcc</a></span></dt><dt><span class="sect2"><a href="reference.html#assumed-charset">3.11. assumed_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-charset">3.12. attach_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-format">3.13. attach_format</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-sep">3.14. attach_sep</a></span></dt><dt><span class="sect2"><a href="reference.html#attach-split">3.15. attach_split</a></span></dt><dt><span class="sect2"><a href="reference.html#attribution">3.16. attribution</a></span></dt><dt><span class="sect2"><a href="reference.html#autoedit">3.17. autoedit</a></span></dt><dt><span class="sect2"><a href="reference.html#auto-tag">3.18. auto_tag</a></span></dt><dt><span class="sect2"><a href="reference.html#beep">3.19. beep</a></span></dt><dt><span class="sect2"><a href="reference.html#beep-new">3.20. beep_new</a></span></dt><dt><span class="sect2"><a href="reference.html#bounce">3.21. bounce</a></span></dt><dt><span class="sect2"><a href="reference.html#bounce-delivered">3.22. bounce_delivered</a></span></dt><dt><span class="sect2"><a href="reference.html#braille-friendly">3.23. braille_friendly</a></span></dt><dt><span class="sect2"><a href="reference.html#check-mbox-size">3.24. check_mbox_size</a></span></dt><dt><span class="sect2"><a href="reference.html#charset">3.25. charset</a></span></dt><dt><span class="sect2"><a href="reference.html#check-new">3.26. check_new</a></span></dt><dt><span class="sect2"><a href="reference.html#collapse-unread">3.27. collapse_unread</a></span></dt><dt><span class="sect2"><a href="reference.html#uncollapse-jump">3.28. uncollapse_jump</a></span></dt><dt><span class="sect2"><a href="reference.html#compose-format">3.29. compose_format</a></span></dt><dt><span class="sect2"><a href="reference.html#config-charset">3.30. config_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#confirmappend">3.31. confirmappend</a></span></dt><dt><span class="sect2"><a href="reference.html#confirmcreate">3.32. confirmcreate</a></span></dt><dt><span class="sect2"><a href="reference.html#connect-timeout">3.33. connect_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#content-type">3.34. content_type</a></span></dt><dt><span class="sect2"><a href="reference.html#copy">3.35. copy</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-use-gpgme">3.36. crypt_use_gpgme</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-use-pka">3.37. crypt_use_pka</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autopgp">3.38. crypt_autopgp</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autosmime">3.39. crypt_autosmime</a></span></dt><dt><span class="sect2"><a href="reference.html#date-format">3.40. date_format</a></span></dt><dt><span class="sect2"><a href="reference.html#default-hook">3.41. default_hook</a></span></dt><dt><span class="sect2"><a href="reference.html#delete">3.42. delete</a></span></dt><dt><span class="sect2"><a href="reference.html#delete-untag">3.43. delete_untag</a></span></dt><dt><span class="sect2"><a href="reference.html#digest-collapse">3.44. digest_collapse</a></span></dt><dt><span class="sect2"><a href="reference.html#display-filter">3.45. display_filter</a></span></dt><dt><span class="sect2"><a href="reference.html#dotlock-program">3.46. dotlock_program</a></span></dt><dt><span class="sect2"><a href="reference.html#dsn-notify">3.47. dsn_notify</a></span></dt><dt><span class="sect2"><a href="reference.html#dsn-return">3.48. dsn_return</a></span></dt><dt><span class="sect2"><a href="reference.html#duplicate-threads">3.49. duplicate_threads</a></span></dt><dt><span class="sect2"><a href="reference.html#edit-headers">3.50. edit_headers</a></span></dt><dt><span class="sect2"><a href="reference.html#editor">3.51. editor</a></span></dt><dt><span class="sect2"><a href="reference.html#encode-from">3.52. encode_from</a></span></dt><dt><span class="sect2"><a href="reference.html#envelope-from-address">3.53. envelope_from_address</a></span></dt><dt><span class="sect2"><a href="reference.html#escape">3.54. escape</a></span></dt><dt><span class="sect2"><a href="reference.html#fast-reply">3.55. fast_reply</a></span></dt><dt><span class="sect2"><a href="reference.html#fcc-attach">3.56. fcc_attach</a></span></dt><dt><span class="sect2"><a href="reference.html#fcc-clear">3.57. fcc_clear</a></span></dt><dt><span class="sect2"><a href="reference.html#folder">3.58. folder</a></span></dt><dt><span class="sect2"><a href="reference.html#folder-format">3.59. folder_format</a></span></dt><dt><span class="sect2"><a href="reference.html#followup-to">3.60. followup_to</a></span></dt><dt><span class="sect2"><a href="reference.html#force-name">3.61. force_name</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-decode">3.62. forward_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-edit">3.63. forward_edit</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-format">3.64. forward_format</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-quote">3.65. forward_quote</a></span></dt><dt><span class="sect2"><a href="reference.html#from">3.66. from</a></span></dt><dt><span class="sect2"><a href="reference.html#gecos-mask">3.67. gecos_mask</a></span></dt><dt><span class="sect2"><a href="reference.html#hdrs">3.68. hdrs</a></span></dt><dt><span class="sect2"><a href="reference.html#header">3.69. header</a></span></dt><dt><span class="sect2"><a href="reference.html#help">3.70. help</a></span></dt><dt><span class="sect2"><a href="reference.html#hidden-host">3.71. hidden_host</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-limited">3.72. hide_limited</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-missing">3.73. hide_missing</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-thread-subject">3.74. hide_thread_subject</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-top-limited">3.75. hide_top_limited</a></span></dt><dt><span class="sect2"><a href="reference.html#hide-top-missing">3.76. hide_top_missing</a></span></dt><dt><span class="sect2"><a href="reference.html#history">3.77. history</a></span></dt><dt><span class="sect2"><a href="reference.html#history-file">3.78. history_file</a></span></dt><dt><span class="sect2"><a href="reference.html#honor-followup-to">3.79. honor_followup_to</a></span></dt><dt><span class="sect2"><a href="reference.html#hostname">3.80. hostname</a></span></dt><dt><span class="sect2"><a href="reference.html#ignore-linear-white-space">3.81. ignore_linear_white_space</a></span></dt><dt><span class="sect2"><a href="reference.html#ignore-list-reply-to">3.82. ignore_list_reply_to</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-authenticators">3.83. imap_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-check-subscribed">3.84. imap_check_subscribed</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-delim-chars">3.85. imap_delim_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-headers">3.86. imap_headers</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-idle">3.87. imap_idle</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-keepalive">3.88. imap_keepalive</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-list-subscribed">3.89. imap_list_subscribed</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-login">3.90. imap_login</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-pass">3.91. imap_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-passive">3.92. imap_passive</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-peek">3.93. imap_peek</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-pipeline-depth">3.94. imap_pipeline_depth</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-servernoise">3.95. imap_servernoise</a></span></dt><dt><span class="sect2"><a href="reference.html#imap-user">3.96. imap_user</a></span></dt><dt><span class="sect2"><a href="reference.html#implicit-autoview">3.97. implicit_autoview</a></span></dt><dt><span class="sect2"><a href="reference.html#include">3.98. include</a></span></dt><dt><span class="sect2"><a href="reference.html#include-onlyfirst">3.99. include_onlyfirst</a></span></dt><dt><span class="sect2"><a href="reference.html#indent-string">3.100. indent_string</a></span></dt><dt><span class="sect2"><a href="reference.html#index-format">3.101. index_format</a></span></dt><dt><span class="sect2"><a href="reference.html#ispell">3.102. ispell</a></span></dt><dt><span class="sect2"><a href="reference.html#keep-flagged">3.103. keep_flagged</a></span></dt><dt><span class="sect2"><a href="reference.html#locale">3.104. locale</a></span></dt><dt><span class="sect2"><a href="reference.html#mail-check">3.105. mail_check</a></span></dt><dt><span class="sect2"><a href="reference.html#mailcap-path">3.106. mailcap_path</a></span></dt><dt><span class="sect2"><a href="reference.html#mailcap-sanitize">3.107. mailcap_sanitize</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-mtime">3.108. maildir_mtime</a></span></dt><dt><span class="sect2"><a href="reference.html#header-cache">3.109. header_cache</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-header-cache-verify">3.110. maildir_header_cache_verify</a></span></dt><dt><span class="sect2"><a href="reference.html#header-cache-pagesize">3.111. header_cache_pagesize</a></span></dt><dt><span class="sect2"><a href="reference.html#maildir-trash">3.112. maildir_trash</a></span></dt><dt><span class="sect2"><a href="reference.html#mark-old">3.113. mark_old</a></span></dt><dt><span class="sect2"><a href="reference.html#markers">3.114. markers</a></span></dt><dt><span class="sect2"><a href="reference.html#mask">3.115. mask</a></span></dt><dt><span class="sect2"><a href="reference.html#mbox">3.116. mbox</a></span></dt><dt><span class="sect2"><a href="reference.html#mbox-type">3.117. mbox_type</a></span></dt><dt><span class="sect2"><a href="reference.html#metoo">3.118. metoo</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-context">3.119. menu_context</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-move-off">3.120. menu_move_off</a></span></dt><dt><span class="sect2"><a href="reference.html#menu-scroll">3.121. menu_scroll</a></span></dt><dt><span class="sect2"><a href="reference.html#meta-key">3.122. meta_key</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-purge">3.123. mh_purge</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-flagged">3.124. mh_seq_flagged</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-replied">3.125. mh_seq_replied</a></span></dt><dt><span class="sect2"><a href="reference.html#mh-seq-unseen">3.126. mh_seq_unseen</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward">3.127. mime_forward</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward-decode">3.128. mime_forward_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#mime-forward-rest">3.129. mime_forward_rest</a></span></dt><dt><span class="sect2"><a href="reference.html#mix-entry-format">3.130. mix_entry_format</a></span></dt><dt><span class="sect2"><a href="reference.html#mixmaster">3.131. mixmaster</a></span></dt><dt><span class="sect2"><a href="reference.html#move">3.132. move</a></span></dt><dt><span class="sect2"><a href="reference.html#message-cachedir">3.133. message_cachedir</a></span></dt><dt><span class="sect2"><a href="reference.html#message-cache-clean">3.134. message_cache_clean</a></span></dt><dt><span class="sect2"><a href="reference.html#message-format">3.135. message_format</a></span></dt><dt><span class="sect2"><a href="reference.html#narrow-tree">3.136. narrow_tree</a></span></dt><dt><span class="sect2"><a href="reference.html#net-inc">3.137. net_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#pager">3.138. pager</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-context">3.139. pager_context</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-format">3.140. pager_format</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-index-lines">3.141. pager_index_lines</a></span></dt><dt><span class="sect2"><a href="reference.html#pager-stop">3.142. pager_stop</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autosign">3.143. crypt_autosign</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-autoencrypt">3.144. crypt_autoencrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-ignore-subkeys">3.145. pgp_ignore_subkeys</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replyencrypt">3.146. crypt_replyencrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replysign">3.147. crypt_replysign</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-replysignencrypted">3.148. crypt_replysignencrypted</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-timestamp">3.149. crypt_timestamp</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-use-gpg-agent">3.150. pgp_use_gpg_agent</a></span></dt><dt><span class="sect2"><a href="reference.html#crypt-verify-sig">3.151. crypt_verify_sig</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-is-default">3.152. smime_is_default</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-ask-cert-label">3.153. smime_ask_cert_label</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-decrypt-use-default-key">3.154. smime_decrypt_use_default_key</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-entry-format">3.155. pgp_entry_format</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-good-sign">3.156. pgp_good_sign</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-check-exit">3.157. pgp_check_exit</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-long-ids">3.158. pgp_long_ids</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-retainable-sigs">3.159. pgp_retainable_sigs</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-autoinline">3.160. pgp_autoinline</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-replyinline">3.161. pgp_replyinline</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-show-unusable">3.162. pgp_show_unusable</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sign-as">3.163. pgp_sign_as</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-strict-enc">3.164. pgp_strict_enc</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-timeout">3.165. pgp_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sort-keys">3.166. pgp_sort_keys</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-auto">3.167. pgp_mime_auto</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-auto-decode">3.168. pgp_auto_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-signature-filename">3.169. pgp_mime_signature_filename</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-mime-signature-description">3.170. pgp_mime_signature_description</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-decode-command">3.171. pgp_decode_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-getkeys-command">3.172. pgp_getkeys_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-verify-command">3.173. pgp_verify_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-decrypt-command">3.174. pgp_decrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-clearsign-command">3.175. pgp_clearsign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-sign-command">3.176. pgp_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-encrypt-sign-command">3.177. pgp_encrypt_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-encrypt-only-command">3.178. pgp_encrypt_only_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-import-command">3.179. pgp_import_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-export-command">3.180. pgp_export_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-verify-key-command">3.181. pgp_verify_key_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-list-secring-command">3.182. pgp_list_secring_command</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp-list-pubring-command">3.183. pgp_list_pubring_command</a></span></dt><dt><span class="sect2"><a href="reference.html#forward-decrypt">3.184. forward_decrypt</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-timeout">3.185. smime_timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-encrypt-with">3.186. smime_encrypt_with</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-keys">3.187. smime_keys</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-ca-location">3.188. smime_ca_location</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-certificates">3.189. smime_certificates</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-decrypt-command">3.190. smime_decrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-verify-command">3.191. smime_verify_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-verify-opaque-command">3.192. smime_verify_opaque_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-sign-command">3.193. smime_sign_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-sign-opaque-command">3.194. smime_sign_opaque_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-encrypt-command">3.195. smime_encrypt_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-pk7out-command">3.196. smime_pk7out_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-cert-command">3.197. smime_get_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-signer-cert-command">3.198. smime_get_signer_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-import-cert-command">3.199. smime_import_cert_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-get-cert-email-command">3.200. smime_get_cert_email_command</a></span></dt><dt><span class="sect2"><a href="reference.html#smime-default-key">3.201. smime_default_key</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-client-cert">3.202. ssl_client_cert</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-force-tls">3.203. ssl_force_tls</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-starttls">3.204. ssl_starttls</a></span></dt><dt><span class="sect2"><a href="reference.html#certificate-file">3.205. certificate_file</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-use-sslv3">3.206. ssl_use_sslv3</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-use-tlsv1">3.207. ssl_use_tlsv1</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-min-dh-prime-bits">3.208. ssl_min_dh_prime_bits</a></span></dt><dt><span class="sect2"><a href="reference.html#ssl-ca-certificates-file">3.209. ssl_ca_certificates_file</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-split">3.210. pipe_split</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-decode">3.211. pipe_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#pipe-sep">3.212. pipe_sep</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-authenticators">3.213. pop_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-auth-try-all">3.214. pop_auth_try_all</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-checkinterval">3.215. pop_checkinterval</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-delete">3.216. pop_delete</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-host">3.217. pop_host</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-last">3.218. pop_last</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-reconnect">3.219. pop_reconnect</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-user">3.220. pop_user</a></span></dt><dt><span class="sect2"><a href="reference.html#pop-pass">3.221. pop_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#post-indent-string">3.222. post_indent_string</a></span></dt><dt><span class="sect2"><a href="reference.html#postpone">3.223. postpone</a></span></dt><dt><span class="sect2"><a href="reference.html#postponed">3.224. postponed</a></span></dt><dt><span class="sect2"><a href="reference.html#preconnect">3.225. preconnect</a></span></dt><dt><span class="sect2"><a href="reference.html#print">3.226. print</a></span></dt><dt><span class="sect2"><a href="reference.html#print-command">3.227. print_command</a></span></dt><dt><span class="sect2"><a href="reference.html#print-decode">3.228. print_decode</a></span></dt><dt><span class="sect2"><a href="reference.html#print-split">3.229. print_split</a></span></dt><dt><span class="sect2"><a href="reference.html#prompt-after">3.230. prompt_after</a></span></dt><dt><span class="sect2"><a href="reference.html#query-command">3.231. query_command</a></span></dt><dt><span class="sect2"><a href="reference.html#query-format">3.232. query_format</a></span></dt><dt><span class="sect2"><a href="reference.html#quit">3.233. quit</a></span></dt><dt><span class="sect2"><a href="reference.html#quote-regexp">3.234. quote_regexp</a></span></dt><dt><span class="sect2"><a href="reference.html#read-inc">3.235. read_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#read-only">3.236. read_only</a></span></dt><dt><span class="sect2"><a href="reference.html#realname">3.237. realname</a></span></dt><dt><span class="sect2"><a href="reference.html#recall">3.238. recall</a></span></dt><dt><span class="sect2"><a href="reference.html#record">3.239. record</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-regexp">3.240. reply_regexp</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-self">3.241. reply_self</a></span></dt><dt><span class="sect2"><a href="reference.html#reply-to">3.242. reply_to</a></span></dt><dt><span class="sect2"><a href="reference.html#resolve">3.243. resolve</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-alias">3.244. reverse_alias</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-name">3.245. reverse_name</a></span></dt><dt><span class="sect2"><a href="reference.html#reverse-realname">3.246. reverse_realname</a></span></dt><dt><span class="sect2"><a href="reference.html#rfc2047-parameters">3.247. rfc2047_parameters</a></span></dt><dt><span class="sect2"><a href="reference.html#save-address">3.248. save_address</a></span></dt><dt><span class="sect2"><a href="reference.html#save-empty">3.249. save_empty</a></span></dt><dt><span class="sect2"><a href="reference.html#save-history">3.250. save_history</a></span></dt><dt><span class="sect2"><a href="reference.html#save-name">3.251. save_name</a></span></dt><dt><span class="sect2"><a href="reference.html#score">3.252. score</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-delete">3.253. score_threshold_delete</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-flag">3.254. score_threshold_flag</a></span></dt><dt><span class="sect2"><a href="reference.html#score-threshold-read">3.255. score_threshold_read</a></span></dt><dt><span class="sect2"><a href="reference.html#send-charset">3.256. send_charset</a></span></dt><dt><span class="sect2"><a href="reference.html#sendmail">3.257. sendmail</a></span></dt><dt><span class="sect2"><a href="reference.html#sendmail-wait">3.258. sendmail_wait</a></span></dt><dt><span class="sect2"><a href="reference.html#shell">3.259. shell</a></span></dt><dt><span class="sect2"><a href="reference.html#sig-dashes">3.260. sig_dashes</a></span></dt><dt><span class="sect2"><a href="reference.html#sig-on-top">3.261. sig_on_top</a></span></dt><dt><span class="sect2"><a href="reference.html#signature">3.262. signature</a></span></dt><dt><span class="sect2"><a href="reference.html#simple-search">3.263. simple_search</a></span></dt><dt><span class="sect2"><a href="reference.html#smart-wrap">3.264. smart_wrap</a></span></dt><dt><span class="sect2"><a href="reference.html#smileys">3.265. smileys</a></span></dt><dt><span class="sect2"><a href="reference.html#sleep-time">3.266. sleep_time</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-authenticators">3.267. smtp_authenticators</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-pass">3.268. smtp_pass</a></span></dt><dt><span class="sect2"><a href="reference.html#smtp-url">3.269. smtp_url</a></span></dt><dt><span class="sect2"><a href="reference.html#sort">3.270. sort</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-alias">3.271. sort_alias</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-aux">3.272. sort_aux</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-browser">3.273. sort_browser</a></span></dt><dt><span class="sect2"><a href="reference.html#sort-re">3.274. sort_re</a></span></dt><dt><span class="sect2"><a href="reference.html#spam-separator">3.275. spam_separator</a></span></dt><dt><span class="sect2"><a href="reference.html#spoolfile">3.276. spoolfile</a></span></dt><dt><span class="sect2"><a href="reference.html#status-chars">3.277. status_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#status-format">3.278. status_format</a></span></dt><dt><span class="sect2"><a href="reference.html#status-on-top">3.279. status_on_top</a></span></dt><dt><span class="sect2"><a href="reference.html#strict-threads">3.280. strict_threads</a></span></dt><dt><span class="sect2"><a href="reference.html#suspend">3.281. suspend</a></span></dt><dt><span class="sect2"><a href="reference.html#text-flowed">3.282. text_flowed</a></span></dt><dt><span class="sect2"><a href="reference.html#thread-received">3.283. thread_received</a></span></dt><dt><span class="sect2"><a href="reference.html#thorough-search">3.284. thorough_search</a></span></dt><dt><span class="sect2"><a href="reference.html#tilde">3.285. tilde</a></span></dt><dt><span class="sect2"><a href="reference.html#time-inc">3.286. time_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#timeout">3.287. timeout</a></span></dt><dt><span class="sect2"><a href="reference.html#tmpdir">3.288. tmpdir</a></span></dt><dt><span class="sect2"><a href="reference.html#to-chars">3.289. to_chars</a></span></dt><dt><span class="sect2"><a href="reference.html#trash">3.290. trash</a></span></dt><dt><span class="sect2"><a href="reference.html#tunnel">3.291. tunnel</a></span></dt><dt><span class="sect2"><a href="reference.html#use-8bitmime">3.292. use_8bitmime</a></span></dt><dt><span class="sect2"><a href="reference.html#use-domain">3.293. use_domain</a></span></dt><dt><span class="sect2"><a href="reference.html#use-envelope-from">3.294. use_envelope_from</a></span></dt><dt><span class="sect2"><a href="reference.html#use-from">3.295. use_from</a></span></dt><dt><span class="sect2"><a href="reference.html#use-idn">3.296. use_idn</a></span></dt><dt><span class="sect2"><a href="reference.html#use-ipv6">3.297. use_ipv6</a></span></dt><dt><span class="sect2"><a href="reference.html#user-agent">3.298. user_agent</a></span></dt><dt><span class="sect2"><a href="reference.html#visual">3.299. visual</a></span></dt><dt><span class="sect2"><a href="reference.html#wait-key">3.300. wait_key</a></span></dt><dt><span class="sect2"><a href="reference.html#weed">3.301. weed</a></span></dt><dt><span class="sect2"><a href="reference.html#wrap">3.302. wrap</a></span></dt><dt><span class="sect2"><a href="reference.html#wrap-search">3.303. wrap_search</a></span></dt><dt><span class="sect2"><a href="reference.html#wrapmargin">3.304. wrapmargin</a></span></dt><dt><span class="sect2"><a href="reference.html#write-inc">3.305. write_inc</a></span></dt><dt><span class="sect2"><a href="reference.html#write-bcc">3.306. write_bcc</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-icon">3.307. xterm_icon</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-set-titles">3.308. xterm_set_titles</a></span></dt><dt><span class="sect2"><a href="reference.html#xterm-title">3.309. xterm_title</a></span></dt></dl></dd><dt><span class="sect1"><a href="reference.html#functions">4. Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="reference.html#generic_map">4.1. generic menu</a></span></dt><dt><span class="sect2"><a href="reference.html#index_map">4.2. index menu</a></span></dt><dt><span class="sect2"><a href="reference.html#pager_map">4.3. pager menu</a></span></dt><dt><span class="sect2"><a href="reference.html#alias_map">4.4. alias menu</a></span></dt><dt><span class="sect2"><a href="reference.html#query_map">4.5. query menu</a></span></dt><dt><span class="sect2"><a href="reference.html#attach_map">4.6. attach menu</a></span></dt><dt><span class="sect2"><a href="reference.html#compose_map">4.7. compose menu</a></span></dt><dt><span class="sect2"><a href="reference.html#postpone_map">4.8. postpone menu</a></span></dt><dt><span class="sect2"><a href="reference.html#browser_map">4.9. browser menu</a></span></dt><dt><span class="sect2"><a href="reference.html#pgp_map">4.10. pgp menu</a></span></dt><dt><span class="sect2"><a href="reference.html#smime_map">4.11. smime menu</a></span></dt><dt><span class="sect2"><a href="reference.html#mix_map">4.12. mix menu</a></span></dt><dt><span class="sect2"><a href="reference.html#editor_map">4.13. editor menu</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commandline"></a>1. Command line options</h2></div></div></div><p>
-Running <code class="literal">mutt</code> with no arguments will make Mutt attempt to read your spool
-mailbox. However, it is possible to read other mailboxes and
-to send messages from the command line as well.
-</p><div class="table"><a id="tab-commandline-options"></a><p class="title"><b>Table 8.1. Command line options</b></p><div class="table-contents"><table summary="Command line options" border="1"><colgroup><col /><col /></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td>-A</td><td>expand an alias</td></tr><tr><td>-a</td><td>attach a file to a message</td></tr><tr><td>-b</td><td>specify a blind carbon-copy (BCC) address</td></tr><tr><td>-c</td><td>specify a carbon-copy (Cc) address</td></tr><tr><td>-D</td><td>print the value of all mutt variables to stdout</td></tr><tr><td>-e</td><td>specify a config command to be run after initialization files are read</td></tr><tr><td>-f</td><td>specify a mailbox to load</td></tr><tr><td>-F</td><td>specify an alternate file to read initialization commands</td></tr><tr><td>-h</td><td>print help on command line options</td></tr><tr><td>-H</td><td>specify a draft file from which to read a header and body</td></tr><tr><td>-i</td><td>specify a file to include in a message composition</td></tr><tr><td>-m</td><td>specify a default mailbox type</td></tr><tr><td>-n</td><td>do not read the system Muttrc</td></tr><tr><td>-p</td><td>recall a postponed message</td></tr><tr><td>-Q</td><td>query a configuration variable</td></tr><tr><td>-R</td><td>open mailbox in read-only mode</td></tr><tr><td>-s</td><td>specify a subject (enclose in quotes if it contains spaces)</td></tr><tr><td>-v</td><td>show version number and compile-time definitions</td></tr><tr><td>-x</td><td>simulate the mailx(1) compose mode</td></tr><tr><td>-y</td><td>show a menu containing the files specified by the mailboxes command</td></tr><tr><td>-z</td><td>exit immediately if there are no messages in the mailbox</td></tr><tr><td>-Z</td><td>open the first folder with new message,exit immediately if none</td></tr></tbody></table></div></div><br class="table-break" /><p>
-To read messages in a mailbox
-</p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-nz</code>] [<code class="option">-F</code>
-<em class="replaceable"><code>muttrc</code></em>
-] [<code class="option">-m</code>
-<em class="replaceable"><code>type</code></em>
-] [<code class="option">-f</code>
-<em class="replaceable"><code>mailbox</code></em>
-]</p></div><p>
-To compose a new message
-</p><div class="cmdsynopsis"><p><code class="command">mutt</code> [<code class="option">-n</code>] [<code class="option">-F</code>
-<em class="replaceable"><code>muttrc</code></em>
-] [<code class="option">-c</code>
-<em class="replaceable"><code>address</code></em>
-] [<code class="option">-i</code>
-<em class="replaceable"><code>filename</code></em>
-] [<code class="option">-s</code>
-<em class="replaceable"><code>subject</code></em>
-] [
-<code class="option">-a</code>
-<em class="replaceable"><code>file</code></em>
- [...]
---
-]
-<em class="replaceable"><code>address</code></em>
-... </p></div><p>
-Mutt also supports a “<span class="quote">batch</span>” mode to send prepared messages. Simply redirect
-input from the file you wish to send. For example,
-</p><p>
-<code class="literal">mutt -s "data set for run #2" professor@bigschool.edu
-< ˜/run2.dat</code>
-</p><p>
-This command will send a message to “<span class="quote">professor@bigschool.edu</span>” with a subject
-of “<span class="quote">data set for run #2</span>”. In the body of the message will be the contents
-of the file “<span class="quote">˜/run2.dat</span>”.
-</p><p>
-All files passed with -a <span class="emphasis"><em>file</em></span> will be attached as a MIME
-part to the message. To attach several files, use “<span class="quote">--</span>” to separate files and
-recipient addresses: <code class="literal">mutt -a *.png -- some@one.org</code>
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="commands"></a>2. Configuration Commands</h2></div></div></div><p>
-The following are the commands understood by mutt.
-</p><div class="itemizedlist"><ul type="disc"><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="optionalfeatures.html#account-hook" title="6. Managing multiple accounts">account-hook</a></code>
-<em class="replaceable"><code>pattern</code></em>
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">alias</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>address</code></em>
- [
-<em class="replaceable"><code>address</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">unalias</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>key</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">unalternates</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#alternative-order" title="5. MIME Multipart/Alternative">alternative-order</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#alternative-order" title="5. MIME Multipart/Alternative">unalternative-order</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto-view</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">unauto-view</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">bind</a></code>
-<em class="replaceable"><code>map</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>function</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#charset-hook" title="6. Defining aliases for character sets">charset-hook</a></code>
-<em class="replaceable"><code>alias</code></em>
-
-<em class="replaceable"><code>charset</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#charset-hook" title="6. Defining aliases for character sets">iconv-hook</a></code>
-<em class="replaceable"><code>charset</code></em>
-
-<em class="replaceable"><code>local-charset</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">color</a></code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">color</a></code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">color</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>foreground</code></em>
-
-<em class="replaceable"><code>background</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#color" title="9. Using color and mono video attributes">uncolor</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>pattern</code></em>
-... </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#exec" title="23. Executing functions">exec</a></code>
-<em class="replaceable"><code>function</code></em>
- [
-<em class="replaceable"><code>function</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#folder-hook" title="7. Setting variables based upon mailbox">folder-hook</a></code>
-<em class="replaceable"><code>[!]regexp</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#addrgroup" title="3. Address groups">group</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#addrgroup" title="3. Address groups">ungroup</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<code class="option">-rx</code>
-<em class="replaceable"><code>expr</code></em>
-... |
-<code class="option">-addr</code>
-<em class="replaceable"><code>expr</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#hdr-order">hdr_order</a></code>
-<em class="replaceable"><code>header</code></em>
- [
-<em class="replaceable"><code>header</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#hdr-order">unhdr_order</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>header</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#ignore" title="10. Message header display">ignore</a></code>
-<em class="replaceable"><code>pattern</code></em>
- [
-<em class="replaceable"><code>pattern</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#ignore" title="10. Message header display">unignore</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#lists" title="12. Mailing lists">lists</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#lists" title="12. Mailing lists">unlists</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#macro" title="8. Keyboard macros">macro</a></code>
-<em class="replaceable"><code>menu</code></em>
-
-<em class="replaceable"><code>key</code></em>
-
-<em class="replaceable"><code>sequence</code></em>
- [
-<em class="replaceable"><code>description</code></em>
-]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></code>
-<em class="replaceable"><code>mailbox</code></em>
- [
-<em class="replaceable"><code>mailbox</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">unmailboxes</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mailbox</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#message-hook" title="20. Change settings before formatting a message">message-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#mime-lookup" title="7. MIME Lookup">mime-lookup</a></code>
-<em class="replaceable"><code>mimetype</code></em>
- [
-<em class="replaceable"><code>mimetype</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="mimesupport.html#mime-lookup" title="7. MIME Lookup">unmime-lookup</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>mimetype</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mono">mono</a></code>
-<em class="replaceable"><code>object</code></em>
-
-<em class="replaceable"><code>attribute</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mono">mono</a></code> {
-<code class="option">header</code>
- |
-<code class="option">body</code>
- }
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>regexp</code></em>
- </p></div><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mono">mono</a></code>
-<code class="option">index</code>
-
-<em class="replaceable"><code>attribute</code></em>
-
-<em class="replaceable"><code>pattern</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#mono">unmono</a></code>
-<code class="option">index</code>
- {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></code>
-<em class="replaceable"><code>string</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">unmy_hdr</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>field</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#crypt-hook" title="21. Choosing the cryptographic key of the recipient">crypt-hook</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>keyid</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#push" title="22. Adding key sequences to the keyboard buffer">push</a></code>
-<em class="replaceable"><code>string</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#set" title="26. Setting and Querying Variables">reset</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>mailbox</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="reference.html#score" title="3.252. score">score</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>value</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="reference.html#score" title="3.252. score">unscore</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#reply-hook">reply-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#send2-hook">send2-hook</a></code>
-<em class="replaceable"><code>[!]pattern</code></em>
-
-<em class="replaceable"><code>command</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#set" title="26. Setting and Querying Variables">set</a></code> {
-[ <code class="option">no</code> | <code class="option">inv</code> ]
-<em class="replaceable"><code>variable</code></em>
- |
-<em class="replaceable"><code>variable=value</code></em>
- } [...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#set" title="26. Setting and Querying Variables">unset</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a></code>
-<em class="replaceable"><code>filename</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#spam" title="25. Spam detection">spam</a></code>
-<em class="replaceable"><code>pattern</code></em>
-
-<em class="replaceable"><code>format</code></em>
- </p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#spam" title="25. Spam detection">nospam</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>pattern</code></em>
- }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#subscribe">subscribe</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...]
-<em class="replaceable"><code>regexp</code></em>
- [
-<em class="replaceable"><code>regexp</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#subscribe">unsubscribe</a></code> [
-<code class="option">-group</code>
-<em class="replaceable"><code>name</code></em>
-...] {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>regexp</code></em>
-... }</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#set" title="26. Setting and Querying Variables">toggle</a></code>
-<em class="replaceable"><code>variable</code></em>
- [
-<em class="replaceable"><code>variable</code></em>
-...]</p></div></li><li><div class="cmdsynopsis"><p><code class="command"><a class="link" href="configuration.html#unhook" title="29. Removing hooks">unhook</a></code> {
-<em class="replaceable"><code>*</code></em>
- |
-<em class="replaceable"><code>hook-type</code></em>
- }</p></div></li></ul></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="variables"></a>3. Configuration variables</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-nosubject"></a>3.1. abort_nosubject</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-If set to <span class="emphasis"><em>yes</em></span>, when composing messages and no subject is given
-at the subject prompt, composition will be aborted. If set to
-<span class="emphasis"><em>no</em></span>, composing messages with no subject given at the subject
-prompt will never be aborted.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="abort-unmodified"></a>3.2. abort_unmodified</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If set to <span class="emphasis"><em>yes</em></span>, composition will automatically abort after
-editing the message body if no changes are made to the file (this
-check only happens after the <span class="emphasis"><em>first</em></span> edit of the file). When set
-to <span class="emphasis"><em>no</em></span>, composition will never be aborted.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-file"></a>3.3. alias_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.muttrc</code></span>”</p></div><p>
-The default file in which to save aliases created by the
-<code class="literal"><a class="link" href="gettingstarted.html#create-alias"><create-alias></a></code> function. Entries added to this file are
-encoded in the character set specified by <a class="link" href="reference.html#config-charset" title="3.30. config_charset">$config_charset</a> if it
-is <span class="emphasis"><em>set</em></span> or the current character set otherwise.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> Mutt will not automatically source this file; you must
-explicitly use the “<span class="quote"><a class="link" href="configuration.html#source" title="27. Reading initialization commands from another file">source</a></span>” command for it to be executed in case
-this option points to a dedicated alias file.
-</p><p>
-The default for this option is the currently used muttrc file, or
-“<span class="quote">˜/.muttrc</span>” if no user muttrc was found.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias-format"></a>3.4. alias_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %2f %t %-10a %r</code></span>”</p></div><p>
-Specifies the format of the data displayed for the “<span class="quote"><a class="link" href="configuration.html#alias" title="4. Defining/Using aliases">alias</a></span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are available:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>alias name
-</p></dd><dt><span class="term">%f </span></dt><dd><p>flags - currently, a “<span class="quote">d</span>” for an alias marked for deletion
-</p></dd><dt><span class="term">%n </span></dt><dd><p>index number
-</p></dd><dt><span class="term">%r </span></dt><dd><p>address which alias expands to
-</p></dd><dt><span class="term">%t </span></dt><dd><p>character which indicates if the alias is tagged for inclusion
-</p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-8bit"></a>3.5. allow_8bit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether 8-bit data is converted to 7-bit using either Quoted-
-Printable or Base64 encoding when sending mail.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="allow-ansi"></a>3.6. allow_ansi</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <span class="emphasis"><em>set</em></span>,
-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
-
-</p><pre class="screen">
-[-- PGP output follows ...
-
-</pre><p>
-and give it the same color as your attachment color (see also
-<a class="link" href="reference.html#crypt-timestamp" title="3.149. crypt_timestamp">$crypt_timestamp</a>).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="arrow-cursor"></a>3.7. arrow_cursor</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, an arrow (“<span class="quote">-></span>”) 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ascii-chars"></a>3.8. ascii_chars</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will use plain ASCII characters when displaying thread
-and attachment trees, instead of the default <span class="emphasis"><em>ACS</em></span> characters.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askbcc"></a>3.9. askbcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
-before editing an outgoing message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="askcc"></a>3.10. askcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will prompt you for carbon-copy (Cc) recipients before
-editing the body of an outgoing message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="assumed-charset"></a>3.11. assumed_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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 “<span class="quote">us-ascii</span>”.
-</p><p>
-For example, Japanese users might prefer this:
-
-</p><pre class="screen">
-set assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</pre><p>
-However, only the first content is valid for the message body.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-charset"></a>3.12. attach_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable is a colon-separated list of character encoding
-schemes for text file attachments. Mutt uses this setting to guess
-which encoding files being attached are encoded in to convert them to
-a proper character set given in <a class="link" href="reference.html#send-charset" title="3.256. send_charset">$send_charset</a>.
-</p><p>
-If <span class="emphasis"><em>unset</em></span>, the value of <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> will be used instead.
-For example, the following configuration would work for Japanese
-text handling:
-
-</p><pre class="screen">
-set attach_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
-
-</pre><p>
-Note: for Japanese users, “<span class="quote">iso-2022-*</span>” must be put at the head
-of the value as shown above if included.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-format"></a>3.13. attach_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] </code></span>”</p></div><p>
-This variable describes the format of the “<span class="quote">attachment</span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are understood:
-
-</p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>charset
-</p></dd><dt><span class="term">%c </span></dt><dd><p>requires charset conversion (“<span class="quote">n</span>” or “<span class="quote">c</span>”)
-</p></dd><dt><span class="term">%D </span></dt><dd><p>deleted flag
-</p></dd><dt><span class="term">%d </span></dt><dd><p>description
-</p></dd><dt><span class="term">%e </span></dt><dd><p>MIME content-transfer-encoding
-</p></dd><dt><span class="term">%f </span></dt><dd><p>filename
-</p></dd><dt><span class="term">%I </span></dt><dd><p>disposition (“<span class="quote">I</span>” for inline, “<span class="quote">A</span>” for attachment)
-</p></dd><dt><span class="term">%m </span></dt><dd><p>major MIME type
-</p></dd><dt><span class="term">%M </span></dt><dd><p>MIME subtype
-</p></dd><dt><span class="term">%n </span></dt><dd><p>attachment number
-</p></dd><dt><span class="term">%Q </span></dt><dd><p>“<span class="quote">Q</span>”, if MIME part qualifies for attachment counting
-</p></dd><dt><span class="term">%s </span></dt><dd><p>size
-</p></dd><dt><span class="term">%t </span></dt><dd><p>tagged flag
-</p></dd><dt><span class="term">%T </span></dt><dd><p>graphic tree characters
-</p></dd><dt><span class="term">%u </span></dt><dd><p>unlink (=to delete) flag
-</p></dd><dt><span class="term">%X </span></dt><dd><p>number of qualifying MIME parts in this part and its children
-(please see the “<span class="quote"><a class="link" href="mimesupport.html#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-sep"></a>3.14. attach_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
-The separator to add between attachments when operating (saving,
-printing, piping, etc) on a list of tagged attachments.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach-split"></a>3.15. attach_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this variable is <span class="emphasis"><em>unset</em></span>, when operating (saving, printing, piping,
-etc) on a list of tagged attachments, Mutt will concatenate the
-attachments and will operate on them as a single attachment. The
-<a class="link" href="reference.html#attach-sep" title="3.14. attach_sep">$attach_sep</a> separator is added after each attachment. When <span class="emphasis"><em>set</em></span>,
-Mutt will operate on the attachments one by one.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attribution"></a>3.16. attribution</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">On %d, %n wrote:</code></span>”</p></div><p>
-This is the string that will precede a message which has been included
-in a reply. For a full listing of defined <code class="literal">printf(3)</code>-like sequences see
-the section on <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="autoedit"></a>3.17. autoedit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span> along with <a class="link" href="reference.html#edit-headers" title="3.50. edit_headers">$edit_headers</a>, Mutt will skip the initial
-send-menu (prompting for subject and recipients) 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.
-</p><p>
-Also see <a class="link" href="reference.html#fast-reply" title="3.55. fast_reply">$fast_reply</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="auto-tag"></a>3.18. auto_tag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, functions in the <span class="emphasis"><em>index</em></span> menu which affect a message
-will be applied to all tagged messages (if there are any). When
-unset, you must first use the <code class="literal"><tag-prefix></code> function (bound to “<span class="quote">;</span>”
-by default) to make the next function apply to all tagged messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep"></a>3.19. beep</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep when an error occurs.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="beep-new"></a>3.20. beep_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will beep whenever it prints a message
-notifying you of new mail. This is independent of the setting of the
-<a class="link" href="reference.html#beep" title="3.19. beep">$beep</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce"></a>3.21. bounce</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether you will be asked to confirm bouncing messages.
-If set to <span class="emphasis"><em>yes</em></span> you don't get asked if you want to bounce a
-message. Setting this variable to <span class="emphasis"><em>no</em></span> is not generally useful,
-and thus not recommended, because you are unable to bounce messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="bounce-delivered"></a>3.22. bounce_delivered</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will include Delivered-To headers when
-bouncing messages. Postfix users may wish to <span class="emphasis"><em>unset</em></span> this variable.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is unset by default in
-/etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="braille-friendly"></a>3.23. braille_friendly</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will place the cursor at the beginning
-of the current line in menus, even when the <a class="link" href="reference.html#arrow-cursor" title="3.7. arrow_cursor">$arrow_cursor</a> variable
-is <span class="emphasis"><em>unset</em></span>, making it easier for blind persons using Braille displays to
-follow these menus. The option is <span class="emphasis"><em>unset</em></span> by default because many
-visual terminals don't permit making the cursor invisible.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-mbox-size"></a>3.24. check_mbox_size</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, mutt will use file size attribute instead of
-access time when checking for new mail in mbox and mmdf folders.
-</p><p>
-This variable is <span class="emphasis"><em>unset</em></span> by default and should only be enabled when
-new mail detection for these folder types is unreliable or doesn't work.
-</p><p>
-Note that enabling this variable should happen before any “<span class="quote"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
-directives occur in configuration files regarding mbox or mmdf folders
-because mutt needs to determine the initial new mail status of such a
-mailbox by performing a fast mailbox scan when it is defined.
-Afterwards the new mail status is tracked by file size changes.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="charset"></a>3.25. charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Character set your terminal uses to display and enter textual data.
-It is also the fallback for <a class="link" href="reference.html#send-charset" title="3.256. send_charset">$send_charset</a>.
-</p><p>
-Upon startup Mutt tries to derive this value from environment variables
-such as <code class="literal">$LC_CTYPE</code> or <code class="literal">$LANG</code>.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> It should only be set in case Mutt isn't abled to determine the
-character set used correctly.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="check-new"></a>3.26. check_new</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-<span class="bold"><strong>Note:</strong></span> this option only affects <span class="emphasis"><em>maildir</em></span> and <span class="emphasis"><em>MH</em></span> style
-mailboxes.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt 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
-this variable is <span class="emphasis"><em>unset</em></span>, no check for new mail is performed
-while the mailbox is open.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="collapse-unread"></a>3.27. collapse_unread</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, Mutt will not collapse a thread if it contains any
-unread messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="uncollapse-jump"></a>3.28. uncollapse_jump</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will jump to the next unread message, if any,
-when the current thread is <span class="emphasis"><em>un</em></span>collapsed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose-format"></a>3.29. compose_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-- Mutt: Compose [Approx. msg size: %l Atts: %a]%>-</code></span>”</p></div><p>
-Controls the format of the status line displayed in the “<span class="quote">compose</span>”
-menu. This string is similar to <a class="link" href="reference.html#status-format" title="3.278. status_format">$status_format</a>, but has its own
-set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>total number of attachments
-</p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
-</p></dd><dt><span class="term">%l </span></dt><dd><p>approximate size (in bytes) of the current message
-</p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
-</p></dd></dl></div><p>
-See the text describing the <a class="link" href="reference.html#status-format" title="3.278. status_format">$status_format</a> option for more
-information on how to set <a class="link" href="reference.html#compose-format" title="3.29. compose_format">$compose_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="config-charset"></a>3.30. config_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-When defined, Mutt will recode commands in rc files from this
-encoding to the current character set as specified by <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a>
-and aliases written to <a class="link" href="reference.html#alias-file" title="3.3. alias_file">$alias_file</a> from the current character set.
-</p><p>
-Please note that if setting <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> it must be done before
-setting <a class="link" href="reference.html#config-charset" title="3.30. config_charset">$config_charset</a>.
-</p><p>
-Recoding should be avoided as it may render unconvertable
-characters as question marks which can lead to undesired
-side effects (for example in regular expressions).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmappend"></a>3.31. confirmappend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when appending messages to
-an existing mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="confirmcreate"></a>3.32. confirmcreate</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will prompt for confirmation when saving messages to a
-mailbox which does not yet exist before creating it.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="connect-timeout"></a>3.33. connect_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 30</p></div><p>
-Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this
-many seconds if the connection is not able to be established. A negative
-value causes Mutt to wait indefinitely for the connection attempt to succeed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="content-type"></a>3.34. content_type</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">text/plain</code></span>”</p></div><p>
-Sets the default Content-Type for the body of newly composed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="copy"></a>3.35. copy</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether or not copies of your outgoing messages
-will be saved for later references. Also see <a class="link" href="reference.html#record" title="3.239. record">$record</a>,
-<a class="link" href="reference.html#save-name" title="3.251. save_name">$save_name</a>, <a class="link" href="reference.html#force-name" title="3.61. force_name">$force_name</a> and “<span class="quote"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-gpgme"></a>3.36. crypt_use_gpgme</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls the use of the GPGME-enabled crypto backends.
-If it is <span class="emphasis"><em>set</em></span> and Mutt was built with gpgme support, the gpgme code for
-S/MIME and PGP will be used instead of the classic code. Note that
-you need to set this option in .muttrc; it won't have any effect when
-used interactively.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-use-pka"></a>3.37. crypt_use_pka</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether mutt uses PKA
-(see http://www.g10code.de/docs/pka-intro.de.pdf) during signature
-verification (only supported by the GPGME backend).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autopgp"></a>3.38. crypt_autopgp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not mutt may automatically enable
-PGP encryption/signing for messages. See also <a class="link" href="reference.html#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
-<a class="link" href="reference.html#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
-<a class="link" href="reference.html#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="reference.html#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="reference.html#smime-is-default" title="3.152. smime_is_default">$smime_is_default</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosmime"></a>3.39. crypt_autosmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not mutt may automatically enable
-S/MIME encryption/signing for messages. See also <a class="link" href="reference.html#crypt-autoencrypt" title="3.144. crypt_autoencrypt">$crypt_autoencrypt</a>,
-<a class="link" href="reference.html#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>,
-<a class="link" href="reference.html#crypt-autosign" title="3.143. crypt_autosign">$crypt_autosign</a>, <a class="link" href="reference.html#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a> and <a class="link" href="reference.html#smime-is-default" title="3.152. smime_is_default">$smime_is_default</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="date-format"></a>3.40. date_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">!%a, %b %d, %Y at %I:%M:%S%p %Z</code></span>”</p></div><p>
-This variable controls the format of the date printed by the “<span class="quote">%d</span>”
-sequence in <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>. This is passed to the <code class="literal">strftime(3)</code>
-function to process the date, see the man page for the proper syntax.
-</p><p>
-Unless the first character in the string is a bang (“<span class="quote">!</span>”), the month
-and week day names are expanded according to the locale specified in
-the variable <a class="link" href="reference.html#locale" title="3.104. locale">$locale</a>. 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 <span class="emphasis"><em>C</em></span> locale (that is in US
-English).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="default-hook"></a>3.41. default_hook</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜f %s !˜P | (˜P ˜C %s)</code></span>”</p></div><p>
-This variable controls how “<span class="quote"><a class="link" href="configuration.html#message-hook" title="20. Change settings before formatting a message">message-hook</a></span>”, “<span class="quote"><a class="link" href="configuration.html#reply-hook">reply-hook</a></span>”, “<span class="quote"><a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”,
-“<span class="quote"><a class="link" href="configuration.html#send2-hook">send2-hook</a></span>”, “<span class="quote"><a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, and “<span class="quote"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” 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.
-</p><p>
-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
-“<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>”) and is to or cc'ed to a user matching the given
-regular expression.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete"></a>3.42. delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not messages are really deleted when closing or
-synchronizing a mailbox. If set to <span class="emphasis"><em>yes</em></span>, messages marked for
-deleting will automatically be purged without prompting. If set to
-<span class="emphasis"><em>no</em></span>, messages marked for deletion will be kept in the mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="delete-untag"></a>3.43. delete_untag</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this option is <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="digest-collapse"></a>3.44. digest_collapse</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If this option is <span class="emphasis"><em>set</em></span>, mutt's received-attachments menu will not show the subparts of
-individual messages in a multipart/digest. To see these subparts, press “<span class="quote">v</span>” on that menu.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="display-filter"></a>3.45. display_filter</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-When set, specifies a command used to filter messages. When a message
-is viewed it is passed as standard input to <a class="link" href="reference.html#display-filter" title="3.45. display_filter">$display_filter</a>, and the
-filtered message is read from the standard output.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dotlock-program"></a>3.46. dotlock_program</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">/usr/bin/mutt_dotlock</code></span>”</p></div><p>
-Contains the path of the <code class="literal">mutt_dotlock(8)</code> binary to be used by
-mutt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-notify"></a>3.47. dsn_notify</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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: <span class="emphasis"><em>never</em></span>, to never request notification,
-<span class="emphasis"><em>failure</em></span>, to request notification on transmission failure,
-<span class="emphasis"><em>delay</em></span>, to be notified of message delays, <span class="emphasis"><em>success</em></span>, to be
-notified of successful transmission.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set dsn_notify="failure,delay"
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> when using <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-N</code> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="dsn-return"></a>3.48. dsn_return</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable controls how much of your message is returned in DSN
-messages. It may be set to either <span class="emphasis"><em>hdrs</em></span> to return just the
-message header, or <span class="emphasis"><em>full</em></span> to return the full message.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set dsn_return=hdrs
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> when using <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a> for delivery, you should not enable
-this unless you are either using Sendmail 8.8.x or greater or a MTA
-providing a <code class="literal">sendmail(1)</code>-compatible interface supporting the <code class="literal">-R</code> option
-for DSN. For SMTP delivery, DSN support is autodetected so that it
-depends on the server whether DSN will be used or not.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="duplicate-threads"></a>3.49. duplicate_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether mutt, when <a class="link" href="reference.html#sort" title="3.270. sort">$sort</a> is set to <span class="emphasis"><em>threads</em></span>, threads
-messages with the same Message-Id together. If it is <span class="emphasis"><em>set</em></span>, it will indicate
-that it thinks they are duplicates of each other with an equals sign
-in the thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="edit-headers"></a>3.50. edit_headers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option allows you to edit the header of your outgoing messages
-along with the body of your message.
-</p><p>
-<span class="bold"><strong>Note</strong></span> that changes made to the References: and Date: headers are
-ignored for interoperability reasons.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor"></a>3.51. editor</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable specifies which editor is used by mutt.
-It defaults to the value of the <code class="literal">$VISUAL</code>, or <code class="literal">$EDITOR</code>, environment
-variable, or to the string “<span class="quote">/usr/bin/editor</span>” if neither of those are set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="encode-from"></a>3.52. encode_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will quoted-printable encode messages when
-they contain the string “<span class="quote">From </span>” (note the trailing space) in the beginning of a line.
-This is useful to avoid the tampering certain mail delivery and transport
-agents tend to do with messages (in order to prevent tools from
-misinterpreting the line as a mbox message separator).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="envelope-from-address"></a>3.53. envelope_from_address</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
-Default: (empty)</p></div><p>
-Manually sets the <span class="emphasis"><em>envelope</em></span> sender for outgoing messages.
-This value is ignored if <a class="link" href="reference.html#use-envelope-from" title="3.294. use_envelope_from">$use_envelope_from</a> is <span class="emphasis"><em>unset</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="escape"></a>3.54. escape</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜</code></span>”</p></div><p>
-Escape character to use for functions in the builtin editor.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fast-reply"></a>3.55. fast_reply</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, 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><p>
-<span class="bold"><strong>Note:</strong></span> this variable has no effect when the <a class="link" href="reference.html#autoedit" title="3.17. autoedit">$autoedit</a>
-variable is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-attach"></a>3.56. fcc_attach</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable controls whether or not attachments on outgoing messages
-are saved along with the main body of your message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="fcc-clear"></a>3.57. fcc_clear</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, FCCs will be stored unencrypted and
-unsigned, even when the actual message is encrypted and/or
-signed.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder"></a>3.58. folder</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/Mail</code></span>”</p></div><p>
-Specifies the default location of your mailboxes. A “<span class="quote">+</span>” or “<span class="quote">=</span>” 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 <span class="emphasis"><em>before</em></span>
-you use “<span class="quote">+</span>” or “<span class="quote">=</span>” for any other variables since expansion takes place
-when handling the “<span class="quote"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="folder-format"></a>3.59. folder_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f</code></span>”</p></div><p>
-This variable allows you to customize the file browser display to your
-personal taste. This string is similar to <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>, but has
-its own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%C </span></dt><dd><p>current file number
-</p></dd><dt><span class="term">%d </span></dt><dd><p>date/time folder was last modified
-</p></dd><dt><span class="term">%f </span></dt><dd><p>filename
-</p></dd><dt><span class="term">%F </span></dt><dd><p>file permissions
-</p></dd><dt><span class="term">%g </span></dt><dd><p>group name (or numeric gid, if missing)
-</p></dd><dt><span class="term">%l </span></dt><dd><p>number of hard links
-</p></dd><dt><span class="term">%N </span></dt><dd><p>N if folder has new mail, blank otherwise
-</p></dd><dt><span class="term">%s </span></dt><dd><p>size in bytes
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if the file is tagged, blank otherwise
-</p></dd><dt><span class="term">%u </span></dt><dd><p>owner name (or numeric uid, if missing)
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="followup-to"></a>3.60. followup_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether or not the “<span class="quote">Mail-Followup-To:</span>” header field is
-generated when sending mail. When <span class="emphasis"><em>set</em></span>, Mutt will generate this
-field when you are replying to a known mailing list, specified with
-the “<span class="quote"><a class="link" href="configuration.html#subscribe">subscribe</a></span>” or “<span class="quote"><a class="link" href="configuration.html#lists" title="12. Mailing lists">lists</a></span>” commands.
-</p><p>
-This field has two purposes. First, preventing you from
-receiving duplicate copies of replies to messages which you send
-to mailing lists, and second, ensuring that you do get a reply
-separately for any messages sent to known lists to which you are
-not subscribed.
-</p><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="force-name"></a>3.61. force_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable is similar to <a class="link" href="reference.html#save-name" title="3.251. save_name">$save_name</a>, except that Mutt 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.
-</p><p>
-Also see the <a class="link" href="reference.html#record" title="3.239. record">$record</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decode"></a>3.62. forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
-forwarding a message. The message header is also RFC2047 decoded.
-This variable is only used, if <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>,
-otherwise <a class="link" href="reference.html#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is used instead.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-edit"></a>3.63. forward_edit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-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 “<span class="quote">no</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-format"></a>3.64. forward_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">[%a: %s]</code></span>”</p></div><p>
-This variable controls the default subject when forwarding a message.
-It uses the same format sequences as the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-quote"></a>3.65. forward_quote</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, forwarded messages included in the main body of the
-message (when <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>unset</em></span>) will be quoted using
-<a class="link" href="reference.html#indent-string" title="3.100. indent_string">$indent_string</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="from"></a>3.66. from</h3></div></div></div><div class="literallayout"><p>Type: e-mail address<br />
-Default: (empty)</p></div><p>
-When <span class="emphasis"><em>set</em></span>, this variable contains a default from address. It
-can be overridden using “<span class="quote"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></span>” (including from a “<span class="quote"><a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>”) and
-<a class="link" href="reference.html#reverse-name" title="3.245. reverse_name">$reverse_name</a>. This variable is ignored if <a class="link" href="reference.html#use-from" title="3.295. use_from">$use_from</a> is <span class="emphasis"><em>unset</em></span>.
-</p><p>
-This setting defaults to the contents of the environment variable <code class="literal">$EMAIL</code>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="gecos-mask"></a>3.67. gecos_mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^[^,]*</code></span>”</p></div><p>
-A regular expression used by mutt to parse the GECOS field of a password
-entry when expanding the alias. The default value
-will return the string up to the first “<span class="quote">,</span>” encountered.
-If the GECOS field contains a string like “<span class="quote">lastname, firstname</span>” then you
-should set it to “<span class="quote"><code class="literal">.*</code></span>”.
-</p><p>
-This can be useful if you see the following behavior: you address an e-mail
-to user ID “<span class="quote">stevef</span>” whose full name is “<span class="quote">Steve Franklin</span>”. If mutt expands
-“<span class="quote">stevef</span>” to “<span class="quote">"Franklin" stevef@foo.bar</span>” then you should set the <a class="link" href="reference.html#gecos-mask" title="3.67. gecos_mask">$gecos_mask</a> to
-a regular expression that will match the whole name so mutt will expand
-“<span class="quote">Franklin</span>” to “<span class="quote">Franklin, Steve</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hdrs"></a>3.68. hdrs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, the header fields normally added by the “<span class="quote"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command are not created. This variable <span class="emphasis"><em>must</em></span> be unset before
-composing a new message or replying in order to take effect. If <span class="emphasis"><em>set</em></span>,
-the user defined header fields are added to every new message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header"></a>3.69. header</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, this variable causes Mutt to include the header
-of the message you are replying to into the edit buffer.
-The <a class="link" href="reference.html#weed" title="3.301. weed">$weed</a> setting applies.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="help"></a>3.70. help</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, help lines describing the bindings for the major functions
-provided by each menu are displayed on the first line of the screen.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> 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 is
-running. Since this variable is primarily aimed at new users, neither
-of these should present a major problem.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hidden-host"></a>3.71. hidden_host</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will skip the host name part of <a class="link" href="reference.html#hostname" title="3.80. hostname">$hostname</a> variable
-when adding the domain part to addresses. This variable does not
-affect the generation of Message-IDs, and it will not lead to the
-cut-off of first-level domains.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-limited"></a>3.72. hide_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
-by limiting, in the thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-missing"></a>3.73. hide_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages in the
-thread tree.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-thread-subject"></a>3.74. hide_thread_subject</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the subject of messages in the thread
-tree that have the same subject as their parent or closest previously
-displayed sibling.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-limited"></a>3.75. hide_top_limited</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of messages that are hidden
-by limiting, at the top of threads in the thread tree. Note that when
-<a class="link" href="reference.html#hide-limited" title="3.72. hide_limited">$hide_limited</a> is <span class="emphasis"><em>set</em></span>, this option will have no effect.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hide-top-missing"></a>3.76. hide_top_missing</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not show the presence of missing messages at the
-top of threads in the thread tree. Note that when <a class="link" href="reference.html#hide-missing" title="3.73. hide_missing">$hide_missing</a> is
-<span class="emphasis"><em>set</em></span>, this option will have no effect.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history"></a>3.77. history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-This variable controls the size (in number of strings remembered) of
-the string history buffer per category. The buffer is cleared each time the
-variable is set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="history-file"></a>3.78. history_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.mutthistory</code></span>”</p></div><p>
-The file in which Mutt will save its history.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="honor-followup-to"></a>3.79. honor_followup_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether or not a Mail-Followup-To header is
-honored when group-replying to a message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="hostname"></a>3.80. hostname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the fully-qualified hostname of the system mutt is running on
-containing the host's name and the DNS domain it belongs to. It is used
-as the domain part (after “<span class="quote">@</span>”) for local email addresses as well as
-Message-Id headers.
-</p><p>
-Its value is determined at startup as follows: If the node's name
-as returned by the <code class="literal">uname(3)</code> function contains the hostname and the
-domain, these are used to construct <a class="link" href="reference.html#hostname" title="3.80. hostname">$hostname</a>. If there is no
-domain part returned, Mutt will look for a “<span class="quote">domain</span>” or “<span class="quote">search</span>”
-line in <code class="literal">/etc/resolv.conf</code> to determine the domain. Optionally, Mutt
-can be compiled with a fixed domain name in which case a detected
-one is not used.
-</p><p>
-Also see <a class="link" href="reference.html#use-domain" title="3.293. use_domain">$use_domain</a> and <a class="link" href="reference.html#hidden-host" title="3.71. hidden_host">$hidden_host</a>.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, the default for this variable is obtained
-from /etc/mailname when Mutt starts.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-linear-white-space"></a>3.81. ignore_linear_white_space</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option replaces linear-white-space between encoded-word
-and text to a single space to prevent the display of MIME-encoded
-“<span class="quote">Subject:</span>” field from being divided into multiple lines.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ignore-list-reply-to"></a>3.82. ignore_list_reply_to</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Affects the behaviour of the <code class="literal"><reply></code> function when replying to
-messages from mailing lists (as defined by the “<span class="quote"><a class="link" href="configuration.html#subscribe">subscribe</a></span>” or
-“<span class="quote"><a class="link" href="configuration.html#lists" title="12. Mailing lists">lists</a></span>” commands). When <span class="emphasis"><em>set</em></span>, if the “<span class="quote">Reply-To:</span>” field is
-set to the same value as the “<span class="quote">To:</span>” field, Mutt assumes that the
-“<span class="quote">Reply-To:</span>” 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 <span class="emphasis"><em>set</em></span>, use the <code class="literal"><a class="link" href="gettingstarted.html#list-reply"><list-reply></a></code>
-function; <code class="literal"><group-reply></code> will reply to both the sender and the
-list.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-authenticators"></a>3.83. imap_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an IMAP server, in the order mutt should
-try them. Authentication methods are either “<span class="quote">login</span>” or the right
-side of an IMAP “<span class="quote">AUTH=xxx</span>” capability string, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>”
-or “<span class="quote">cram-md5</span>”. This option is case-insensitive. If it's
-<span class="emphasis"><em>unset</em></span> (the default) mutt will try all available methods,
-in order from most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set imap_authenticators="gssapi:cram-md5:login"
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> Mutt will only fall back to other authentication methods if
-the previous methods are unavailable. If a method is available but
-authentication fails, mutt will not connect to the IMAP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-check-subscribed"></a>3.84. imap_check_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, 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 just as if you had issued individual “<span class="quote"><a class="link" href="configuration.html#mailboxes" title="14. Monitoring incoming mail">mailboxes</a></span>”
-commands.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-delim-chars"></a>3.85. imap_delim_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">/.</code></span>”</p></div><p>
-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 “<span class="quote">=</span>” shortcut for your <span class="emphasis"><em>folder</em></span> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-headers"></a>3.86. imap_headers</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Mutt requests these header fields in addition to the default headers
-(“<span class="quote">Date:</span>”, “<span class="quote">From:</span>”, “<span class="quote">Subject:</span>”, “<span class="quote">To:</span>”, “<span class="quote">Cc:</span>”, “<span class="quote">Message-Id:</span>”,
-“<span class="quote">References:</span>”, “<span class="quote">Content-Type:</span>”, “<span class="quote">Content-Description:</span>”, “<span class="quote">In-Reply-To:</span>”,
-“<span class="quote">Reply-To:</span>”, “<span class="quote">Lines:</span>”, “<span class="quote">List-Post:</span>”, “<span class="quote">X-Label:</span>”) from IMAP
-servers before displaying the index menu. You may want to add more
-headers for spam detection.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> This is a space separated list, items should be uppercase
-and not contain the colon, e.g. “<span class="quote">X-BOGOSITY X-SPAM-STATUS</span>” for the
-“<span class="quote">X-Bogosity:</span>” and “<span class="quote">X-Spam-Status:</span>” header fields.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-idle"></a>3.87. imap_idle</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will attempt to use the IMAP IDLE extension
-to check for new mail in the current mailbox. Some servers
-(dovecot was the inspiration for this option) react badly
-to mutt's implementation. If your connection seems to freeze
-up periodically, try unsetting this.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-keepalive"></a>3.88. imap_keepalive</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 900</p></div><p>
-This variable specifies the maximum amount of time in seconds that mutt
-will wait before polling open IMAP connections, to prevent the server
-from closing them before mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-list-subscribed"></a>3.89. imap_list_subscribed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <code class="literal"><toggle-subscribed></code> function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-login"></a>3.90. imap_login</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Your login name on the IMAP server.
-</p><p>
-This variable defaults to the value of <a class="link" href="reference.html#imap-user" title="3.96. imap_user">$imap_user</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pass"></a>3.91. imap_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your IMAP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you invoke the <code class="literal"><a class="link" href="optionalfeatures.html#fetch-mail"><fetch-mail></a></code> function
-or try to open an IMAP folder.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-passive"></a>3.92. imap_passive</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will not open new IMAP connections to check for new
-mail. Mutt 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 invocation, or if opening the connection
-is slow.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-peek"></a>3.93. imap_peek</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-pipeline-depth"></a>3.94. imap_pipeline_depth</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 15</p></div><p>
-Controls the number of IMAP commands that may be queued up before they
-are sent to the server. A deeper pipeline reduces the amount of time
-mutt must wait for the server, and can make IMAP servers feel much
-more responsive. But not all servers correctly handle pipelined commands,
-so if you have problems you might want to try setting this variable to 0.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> Changes to this variable have no effect on open connections.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-servernoise"></a>3.95. imap_servernoise</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="imap-user"></a>3.96. imap_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-The name of the user whose mail you intend to access on the IMAP
-server.
-</p><p>
-This variable defaults to your user name on the local machine.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="implicit-autoview"></a>3.97. implicit_autoview</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If set to “<span class="quote">yes</span>”, mutt will look for a mailcap entry with the
-“<span class="quote"><code class="literal">copiousoutput</code></span>” flag set for <span class="emphasis"><em>every</em></span> MIME attachment it doesn't have
-an internal viewer defined for. If such an entry is found, mutt will
-use the viewer defined in that entry to convert the body part to text
-form.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include"></a>3.98. include</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not a copy of the message(s) you are replying to
-is included in your reply.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="include-onlyfirst"></a>3.99. include_onlyfirst</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether or not Mutt includes only the first attachment
-of the message you are replying.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="indent-string"></a>3.100. indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">> </code></span>”</p></div><p>
-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.
-</p><p>
-This option is a format string, please see the description of
-<a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> for supported <code class="literal">printf(3)</code>-style sequences.
-</p><p>
-Because for <code class="literal">format=lowed</code> style messages the quoting mechanism
-is strictly defined, this setting is ignored if <a class="link" href="reference.html#text-flowed" title="3.282. text_flowed">$text_flowed</a> is
-<span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index-format"></a>3.101. index_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s</code></span>”</p></div><p>
-This variable allows you to customize the message index display to
-your personal taste.
-</p><p>
-“<span class="quote">Format strings</span>” are similar to the strings used in the C
-function <code class="literal">printf(3)</code> to format output (see the man page for more details).
-The following sequences are defined in Mutt:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>address of the author
-</p></dd><dt><span class="term">%A </span></dt><dd><p>reply-to address (if present; otherwise: address of author)
-</p></dd><dt><span class="term">%b </span></dt><dd><p>filename of the original message folder (think mailbox)
-</p></dd><dt><span class="term">%B </span></dt><dd><p>the list to which the letter was sent, or else the folder name (%b).
-</p></dd><dt><span class="term">%c </span></dt><dd><p>number of characters (bytes) in the message
-</p></dd><dt><span class="term">%C </span></dt><dd><p>current message number
-</p></dd><dt><span class="term">%d </span></dt><dd><p>date and time of the message in the format specified by
-<a class="link" href="reference.html#date-format" title="3.40. date_format">$date_format</a> converted to sender's time zone
-</p></dd><dt><span class="term">%D </span></dt><dd><p>date and time of the message in the format specified by
-<a class="link" href="reference.html#date-format" title="3.40. date_format">$date_format</a> converted to the local time zone
-</p></dd><dt><span class="term">%e </span></dt><dd><p>current message number in thread
-</p></dd><dt><span class="term">%E </span></dt><dd><p>number of messages in current thread
-</p></dd><dt><span class="term">%f </span></dt><dd><p>sender (address + real name), either From: or Return-Path:
-</p></dd><dt><span class="term">%F </span></dt><dd><p>author name, or recipient name if the message is from you
-</p></dd><dt><span class="term">%H </span></dt><dd><p>spam attribute(s) of this message
-</p></dd><dt><span class="term">%i </span></dt><dd><p>message-id of the current message
-</p></dd><dt><span class="term">%l </span></dt><dd><p>number of lines in the message (does not work with maildir,
-mh, and possibly IMAP folders)
-</p></dd><dt><span class="term">%L </span></dt><dd><p>If an address in the “<span class="quote">To:</span>” or “<span class="quote">Cc:</span>” header field matches an address
-defined by the users “<span class="quote"><a class="link" href="configuration.html#subscribe">subscribe</a></span>” command, this displays
-"To <list-name>", otherwise the same as %F.
-</p></dd><dt><span class="term">%m </span></dt><dd><p>total number of message in the mailbox
-</p></dd><dt><span class="term">%M </span></dt><dd><p>number of hidden messages if the thread is collapsed.
-</p></dd><dt><span class="term">%N </span></dt><dd><p>message score
-</p></dd><dt><span class="term">%n </span></dt><dd><p>author's real name (or address if missing)
-</p></dd><dt><span class="term">%O </span></dt><dd><p>original save folder where mutt would formerly have
-stashed the message: list name or recipient name
-if not sent to a list
-</p></dd><dt><span class="term">%P </span></dt><dd><p>progress indicator for the builtin pager (how much of the file has been displayed)
-</p></dd><dt><span class="term">%s </span></dt><dd><p>subject of the message
-</p></dd><dt><span class="term">%S </span></dt><dd><p>status of the message (“<span class="quote">N</span>”/“<span class="quote">D</span>”/“<span class="quote">d</span>”/“<span class="quote">!</span>”/“<span class="quote">r</span>”/*)
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">To:</span>” field (recipients)
-</p></dd><dt><span class="term">%T </span></dt><dd><p>the appropriate character from the <a class="link" href="reference.html#to-chars" title="3.289. to_chars">$to_chars</a> string
-</p></dd><dt><span class="term">%u </span></dt><dd><p>user (login) name of the author
-</p></dd><dt><span class="term">%v </span></dt><dd><p>first name of the author, or the recipient if the message is from you
-</p></dd><dt><span class="term">%X </span></dt><dd><p>number of attachments
-(please see the “<span class="quote"><a class="link" href="mimesupport.html#attachments" title="6. Attachment Searching and Counting">attachments</a></span>” section for possible speed effects)
-</p></dd><dt><span class="term">%y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present
-</p></dd><dt><span class="term">%Y </span></dt><dd><p>“<span class="quote">X-Label:</span>” field, if present, and <span class="emphasis"><em>(1)</em></span> not at part of a thread tree,
-<span class="emphasis"><em>(2)</em></span> at the top of a thread, or <span class="emphasis"><em>(3)</em></span> “<span class="quote">X-Label:</span>” is different from
-preceding message's “<span class="quote">X-Label:</span>”.
-</p></dd><dt><span class="term">%Z </span></dt><dd><p>message status flags
-</p></dd><dt><span class="term">%{fmt} </span></dt><dd><p>the date and time of the message is converted to sender's
-time zone, and “<span class="quote">fmt</span>” is expanded by the library function
-<code class="literal">strftime(3)</code>; a leading bang disables locales
-</p></dd><dt><span class="term">%[fmt] </span></dt><dd><p>the date and time of the message is converted to the local
-time zone, and “<span class="quote">fmt</span>” is expanded by the library function
-<code class="literal">strftime(3)</code>; a leading bang disables locales
-</p></dd><dt><span class="term">%(fmt) </span></dt><dd><p>the local date and time when the message was received.
-“<span class="quote">fmt</span>” is expanded by the library function <code class="literal">strftime(3)</code>;
-a leading bang disables locales
-</p></dd><dt><span class="term">%<fmt> </span></dt><dd><p>the current local time. “<span class="quote">fmt</span>” is expanded by the library
-function <code class="literal">strftime(3)</code>; a leading bang disables locales.
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with character “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-“<span class="quote">Soft-fill</span>” deserves some explanation: Normal right-justification
-will print everything to the left of the “<span class="quote">%></span>”, displaying padding and
-whatever lies to the right only if there's room. By contrast,
-soft-fill gives priority to the right-hand side, guaranteeing space
-to display it and showing padding only if there's still room. If
-necessary, soft-fill will eat text leftwards to make room for
-rightward text.
-</p><p>
-Note that these expandos are supported in
-“<span class="quote"><a class="link" href="configuration.html#save-hook" title="16. Specify default save mailbox">save-hook</a></span>”, “<span class="quote"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” and “<span class="quote"><a class="link" href="configuration.html#fcc-save-hook" title="18. Specify default save filename and default Fcc: mailbox at once">fcc-save-hook</a></span>”, too.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ispell"></a>3.102. ispell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">ispell</code></span>”</p></div><p>
-How to invoke ispell (GNU's spell-checking software).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="keep-flagged"></a>3.103. keep_flagged</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, read messages marked as flagged will not be moved
-from your spool mailbox to your <a class="link" href="reference.html#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
-a “<span class="quote"><a class="link" href="configuration.html#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="locale"></a>3.104. locale</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">C</code></span>”</p></div><p>
-The locale used by <code class="literal">strftime(3)</code> to format dates. Legal values are
-the strings your system accepts for the locale environment variable <code class="literal">$LC_TIME</code>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mail-check"></a>3.105. mail_check</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 5</p></div><p>
-This variable configures how often (in seconds) mutt should look for
-new mail. Also see the <a class="link" href="reference.html#timeout" title="3.287. timeout">$timeout</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-path"></a>3.106. mailcap_path</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable specifies which files to consult when attempting to
-display MIME bodies not directly supported by Mutt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mailcap-sanitize"></a>3.107. mailcap_sanitize</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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.
-</p><p>
-<span class="bold"><strong>DON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
-DOING!</strong></span>
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-mtime"></a>3.108. maildir_mtime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If set, the sort-by-date option in the browser will sort maildirs
-smartly, not using the mtime of the maildir itself but that of the
-newest message in the new subdirectory, making the sorting by
-reverse date much more useful. People with maildirs over NFS may
-wish to leave this option unset.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache"></a>3.109. header_cache</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable points to the header cache database.
-If pointing to a directory Mutt will contain a header cache
-database file per folder, if pointing to a file that file will
-be a single global header cache. By default it is <span class="emphasis"><em>unset</em></span> so no header
-caching will be used.
-</p><p>
-Header caching can greatly improve speed when opening POP, IMAP
-MH or Maildir folders, see “<span class="quote"><a class="link" href="optionalfeatures.html#caching" title="7. Local caching">caching</a></span>” for details.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-header-cache-verify"></a>3.110. maildir_header_cache_verify</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Check for Maildir unaware programs other than mutt having modified maildir
-files when the header cache is in use. This incurs one <code class="literal">stat(2)</code> per
-message every time the folder is opened (which can be very slow for NFS
-folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="header-cache-pagesize"></a>3.111. header_cache_pagesize</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">16384</code></span>”</p></div><p>
-When mutt is compiled with either gdbm or bdb4 as the header cache backend,
-this option changes the database page size. Too large or too small
-values can waste space, memory, or CPU time. The default should be more
-or less optimal for most use cases.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="maildir-trash"></a>3.112. maildir_trash</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, messages marked as deleted will be saved with the maildir
-trashed flag instead of unlinked. <span class="bold"><strong>Note:</strong></span> this only applies
-to maildir-style mailboxes. Setting it will have no effect on other
-mailbox types.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mark-old"></a>3.113. mark_old</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether or not mutt marks <span class="emphasis"><em>new</em></span> <span class="bold"><strong>unread</strong></span>
-messages as <span class="emphasis"><em>old</em></span> if you exit a mailbox without reading them.
-With this option <span class="emphasis"><em>set</em></span>, the next time you start mutt, the messages
-will show up with an “<span class="quote">O</span>” next to them in the index menu,
-indicating that they are old.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="markers"></a>3.114. markers</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the display of wrapped lines in the internal pager. If set, a
-“<span class="quote">+</span>” marker is displayed at the beginning of wrapped lines.
-</p><p>
-Also see the <a class="link" href="reference.html#smart-wrap" title="3.264. smart_wrap">$smart_wrap</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mask"></a>3.115. mask</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">!^\.[^.]</code></span>”</p></div><p>
-A regular expression used in the file browser, optionally preceded by
-the <span class="emphasis"><em>not</em></span> operator “<span class="quote">!</span>”. Only files whose names match this mask
-will be shown. The match is always case-sensitive.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox"></a>3.116. mbox</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/mbox</code></span>”</p></div><p>
-This specifies the folder into which read mail in your <a class="link" href="reference.html#spoolfile" title="3.276. spoolfile">$spoolfile</a>
-folder will be appended.
-</p><p>
-Also see the <a class="link" href="reference.html#move" title="3.132. move">$move</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mbox-type"></a>3.117. mbox_type</h3></div></div></div><div class="literallayout"><p>Type: folder magic<br />
-Default: mbox</p></div><p>
-The default mailbox type used when creating new folders. May be any of
-“<span class="quote">mbox</span>”, “<span class="quote">MMDF</span>”, “<span class="quote">MH</span>” and “<span class="quote">Maildir</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="metoo"></a>3.118. metoo</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>unset</em></span>, Mutt will remove your address (see the “<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>”
-command) from the list of recipients when replying to a message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-context"></a>3.119. menu_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-This variable controls the number of lines of context that are given
-when scrolling through menus. (Similar to <a class="link" href="reference.html#pager-context" title="3.139. pager_context">$pager_context</a>.)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-move-off"></a>3.120. menu_move_off</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, the bottom entry of menus will never scroll up past
-the bottom of the screen, unless there are less entries than lines.
-When <span class="emphasis"><em>set</em></span>, the bottom entry may move off the bottom.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="menu-scroll"></a>3.121. menu_scroll</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, menus will be scrolled up or down one line when you
-attempt to move across a screen boundary. If <span class="emphasis"><em>unset</em></span>, the screen
-is cleared and the next or previous page of the menu is displayed
-(useful for slow links to avoid many redraws).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="meta-key"></a>3.122. meta_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, forces Mutt 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 <code class="literal">0xf8</code>, then this is treated as if the user had
-pressed Esc then “<span class="quote">x</span>”. This is because the result of removing the
-high bit from <code class="literal">0xf8</code> is <code class="literal">0x78</code>, which is the ASCII character
-“<span class="quote">x</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-purge"></a>3.123. mh_purge</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mutt will mimic mh's behaviour and rename deleted messages
-to <span class="emphasis"><em>,<old file name></em></span> in mh folders instead of really deleting
-them. This leaves the message on disk but makes programs reading the folder
-ignore it. If the variable is <span class="emphasis"><em>set</em></span>, the message files will simply be
-deleted.
-</p><p>
-This option is similar to <a class="link" href="reference.html#maildir-trash" title="3.112. maildir_trash">$maildir_trash</a> for Maildir folders.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-flagged"></a>3.124. mh_seq_flagged</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">flagged</code></span>”</p></div><p>
-The name of the MH sequence used for flagged messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-replied"></a>3.125. mh_seq_replied</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">replied</code></span>”</p></div><p>
-The name of the MH sequence used to tag replied messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mh-seq-unseen"></a>3.126. mh_seq_unseen</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">unseen</code></span>”</p></div><p>
-The name of the MH sequence used for unseen messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward"></a>3.127. mime_forward</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the message you are forwarding will be attached as a
-separate <code class="literal">message/rfc822</code> 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 “<span class="quote">ask-no</span>” or “<span class="quote">ask-yes</span>”.
-</p><p>
-Also see <a class="link" href="reference.html#forward-decode" title="3.62. forward_decode">$forward_decode</a> and <a class="link" href="reference.html#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-decode"></a>3.128. mime_forward_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls the decoding of complex MIME messages into <code class="literal">text/plain</code> when
-forwarding a message while <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span>. Otherwise
-<a class="link" href="reference.html#forward-decode" title="3.62. forward_decode">$forward_decode</a> is used instead.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mime-forward-rest"></a>3.129. mime_forward_rest</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-When forwarding multiple attachments of a MIME message from the attachment
-menu, attachments which cannot be decoded in a reasonable manner will
-be attached to the newly composed message if this option is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix-entry-format"></a>3.130. mix_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %c %-16s %a</code></span>”</p></div><p>
-This variable describes the format of a remailer line on the mixmaster
-chain selection screen. The following <code class="literal">printf(3)</code>-like sequences are
-supported:
-
-</p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>The running number on the menu.
-</p></dd><dt><span class="term">%c </span></dt><dd><p>Remailer capabilities.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>The remailer's short name.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The remailer's e-mail address.
-</p></dd></dl></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mixmaster"></a>3.131. mixmaster</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">mixmaster</code></span>”</p></div><p>
-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.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
-“<span class="quote">mixmaster-filter</span>” in /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="move"></a>3.132. move</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: no</p></div><p>
-Controls whether or not Mutt will move read messages
-from your spool mailbox to your <a class="link" href="reference.html#mbox" title="3.116. mbox">$mbox</a> mailbox, or as a result of
-a “<span class="quote"><a class="link" href="configuration.html#mbox-hook" title="13. Using Multiple spool mailboxes">mbox-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cachedir"></a>3.133. message_cachedir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Set this to a directory and mutt will cache copies of messages from
-your IMAP and POP servers here. You are free to remove entries at any
-time.
-</p><p>
-When setting this variable to a directory, mutt needs to fetch every
-remote message only once and can perform regular expression searches
-as fast as for local folders.
-</p><p>
-Also see the <a class="link" href="reference.html#message-cache-clean" title="3.134. message_cache_clean">$message_cache_clean</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-cache-clean"></a>3.134. message_cache_clean</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will clean out obsolete entries from the message cache when
-the mailbox is synchronized. You probably only want to set it
-every once in a while, since it can be a little slow
-(especially for large folders).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="message-format"></a>3.135. message_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%s</code></span>”</p></div><p>
-This is the string displayed in the “<span class="quote">attachment</span>” menu for
-attachments of type <code class="literal">message/rfc822</code>. For a full listing of defined
-<code class="literal">printf(3)</code>-like sequences see the section on <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="narrow-tree"></a>3.136. narrow_tree</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable, when <span class="emphasis"><em>set</em></span>, makes the thread tree narrower, allowing
-deeper threads to fit on the screen.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="net-inc"></a>3.137. net_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-Operations that expect to transfer a large amount of data over the
-network will update their progress every <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a> kilobytes.
-If set to 0, no progress messages will be displayed.
-</p><p>
-See also <a class="link" href="reference.html#read-inc" title="3.235. read_inc">$read_inc</a>, <a class="link" href="reference.html#write-inc" title="3.305. write_inc">$write_inc</a> and <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager"></a>3.138. pager</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">builtin</code></span>”</p></div><p>
-This variable specifies which pager you would like to use to view
-messages. The value “<span class="quote">builtin</span>” means to use the builtin pager, otherwise this
-variable should specify the pathname of the external pager you would
-like to use.
-</p><p>
-Using an external pager may have some disadvantages: Additional
-keystrokes are necessary because you can't call mutt functions
-directly from the pager, and screen resizes cause lines longer than
-the screen width to be badly formatted in the help menu.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-context"></a>3.139. pager_context</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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 will display the line after the last one on the screen
-at the top of the next page (0 lines of context).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-format"></a>3.140. pager_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-%Z- %C/%m: %-20.20n %s%* -- (%P)</code></span>”</p></div><p>
-This variable controls the format of the one-line message “<span class="quote">status</span>”
-displayed before each message in either the internal or an external
-pager. The valid sequences are listed in the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>
-section.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-index-lines"></a>3.141. pager_index_lines</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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 setting 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 <a class="link" href="reference.html#pager-index-lines" title="3.141. pager_index_lines">$pager_index_lines</a>, then the index will only use as
-many lines as it needs.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager-stop"></a>3.142. pager_stop</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the internal-pager will <span class="bold"><strong>not</strong></span> move to the next message
-when you are at the end of a message and invoke the <code class="literal"><next-page></code>
-function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autosign"></a>3.143. crypt_autosign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt 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 <a class="link" href="reference.html#smime-is-default" title="3.152. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
-then OpenSSL is used instead to create S/MIME messages and settings can
-be overridden by use of the smime menu instead of the pgp menu.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-autoencrypt"></a>3.144. crypt_autoencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt to always attempt to PGP
-encrypt outgoing messages. This is probably only useful in
-connection to the “<span class="quote"><a class="link" href="configuration.html#send-hook" title="19. Change settings based upon message recipients">send-hook</a></span>” command. It can be overridden
-by use of the pgp menu, when encryption is not required or
-signing is requested as well. If <a class="link" href="reference.html#smime-is-default" title="3.152. smime_is_default">$smime_is_default</a> is <span class="emphasis"><em>set</em></span>,
-then OpenSSL is used instead to create S/MIME messages and
-settings can be overridden by use of the smime menu instead.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-ignore-subkeys"></a>3.145. pgp_ignore_subkeys</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead,
-the principal key will inherit the subkeys' capabilities. <span class="emphasis"><em>Unset</em></span> this
-if you want to play interesting key selection games.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replyencrypt"></a>3.146. crypt_replyencrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL encrypt replies to messages which are
-encrypted.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysign"></a>3.147. crypt_replysign</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages which are
-signed.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> this does not work on messages that are encrypted
-<span class="emphasis"><em>and</em></span> signed!
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-replysignencrypted"></a>3.148. crypt_replysignencrypted</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, automatically PGP or OpenSSL sign replies to messages
-which are encrypted. This makes sense in combination with
-<a class="link" href="reference.html#crypt-replyencrypt" title="3.146. crypt_replyencrypt">$crypt_replyencrypt</a>, because it allows you to sign all
-messages which are automatically encrypted. This works around
-the problem noted in <a class="link" href="reference.html#crypt-replysign" title="3.147. crypt_replysign">$crypt_replysign</a>, that mutt is not able
-to find out whether an encrypted message is also signed.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-timestamp"></a>3.149. crypt_timestamp</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 <span class="emphasis"><em>unset</em></span> this setting.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-use-gpg-agent"></a>3.150. pgp_use_gpg_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will use a possibly-running <code class="literal">gpg-agent(1)</code> process.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="crypt-verify-sig"></a>3.151. crypt_verify_sig</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>“<span class="quote">yes</span>”</em></span>, always attempt to verify PGP or S/MIME signatures.
-If <span class="emphasis"><em>“<span class="quote">ask-*</span>”</em></span>, ask whether or not to verify the signature.
-If \Fi“<span class="quote">no</span>”, never attempt to verify cryptographic signatures.
-(Crypto only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-is-default"></a>3.152. smime_is_default</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-The default behaviour of mutt is to use PGP on all auto-sign/encryption
-operations. To override and to use OpenSSL instead this must be <span class="emphasis"><em>set</em></span>.
-However, this has no effect while replying, since mutt will automatically
-select the same application that was used to sign/encrypt the original
-message. (Note that this variable can be overridden by unsetting <a class="link" href="reference.html#crypt-autosmime" title="3.39. crypt_autosmime">$crypt_autosmime</a>.)
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ask-cert-label"></a>3.153. smime_ask_cert_label</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-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
-<span class="emphasis"><em>set</em></span> by default.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-use-default-key"></a>3.154. smime_decrypt_use_default_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span> (default) this tells mutt to use the default key for decryption. Otherwise,
-if managing multiple certificate-key-pairs, mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-entry-format"></a>3.155. pgp_entry_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4n %t%f %4l/0x%k %-4a %2c %u</code></span>”</p></div><p>
-This variable allows you to customize the PGP key selection menu to
-your personal taste. This string is similar to <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>, but
-has its own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%n </span></dt><dd><p>number
-</p></dd><dt><span class="term">%k </span></dt><dd><p>key id
-</p></dd><dt><span class="term">%u </span></dt><dd><p>user id
-</p></dd><dt><span class="term">%a </span></dt><dd><p>algorithm
-</p></dd><dt><span class="term">%l </span></dt><dd><p>key length
-</p></dd><dt><span class="term">%f </span></dt><dd><p>flags
-</p></dd><dt><span class="term">%c </span></dt><dd><p>capabilities
-</p></dd><dt><span class="term">%t </span></dt><dd><p>trust/validity of the key-uid association
-</p></dd><dt><span class="term">%[<s>] </span></dt><dd><p>date of the key where <s> is an <code class="literal">strftime(3)</code> expression
-</p></dd></dl></div><p>
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-good-sign"></a>3.156. pgp_good_sign</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: (empty)</p></div><p>
-If you assign a text to this variable, then a PGP signature is only
-considered verified if the output from <a class="link" href="reference.html#pgp-verify-command" title="3.173. pgp_verify_command">$pgp_verify_command</a> contains
-the text. Use this variable if the exit code from the command is 0
-even for bad signatures.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-check-exit"></a>3.157. pgp_check_exit</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-long-ids"></a>3.158. pgp_long_ids</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, use 64 bit PGP key IDs, if <span class="emphasis"><em>unset</em></span> use the normal 32 bit key IDs.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-retainable-sigs"></a>3.159. pgp_retainable_sigs</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, signed and encrypted messages will consist of nested
-<code class="literal">multipart/signed</code> and <code class="literal">multipart/encrypted</code> body parts.
-</p><p>
-This is useful for applications like encrypted and signed mailing
-lists, where the outer layer (<code class="literal">multipart/encrypted</code>) can be easily
-removed, while the inner <code class="literal">multipart/signed</code> part is retained.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-autoinline"></a>3.160. pgp_autoinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This option controls whether Mutt 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.
-</p><p>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</p><p>
-Also see the <a class="link" href="reference.html#pgp-mime-auto" title="3.167. pgp_mime_auto">$pgp_mime_auto</a> variable.
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-replyinline"></a>3.161. pgp_replyinline</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable will cause Mutt 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
-internals for previously checked/flagged messages.
-</p><p>
-Note that Mutt might automatically use PGP/MIME for messages
-which consist of more than a single MIME part. Mutt can be
-configured to ask before sending PGP/MIME messages when inline
-(traditional) would not work.
-</p><p>
-Also see the <a class="link" href="reference.html#pgp-mime-auto" title="3.167. pgp_mime_auto">$pgp_mime_auto</a> variable.
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-show-unusable"></a>3.162. pgp_show_unusable</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 “<span class="quote">disabled</span>” by the user.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-as"></a>3.163. pgp_sign_as</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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. <code class="literal">0x00112233</code>).
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-strict-enc"></a>3.164. pgp_strict_enc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt 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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-timeout"></a>3.165. pgp_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 300</p></div><p>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sort-keys"></a>3.166. pgp_sort_keys</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: address</p></div><p>
-Specifies how the entries in the pgp menu are sorted. The
-following are legal values:
-
-</p><div class="variablelist"><dl><dt><span class="term">address </span></dt><dd><p>sort alphabetically by user id
-</p></dd><dt><span class="term">keyid </span></dt><dd><p>sort alphabetically by key id
-</p></dd><dt><span class="term">date </span></dt><dd><p>sort by key creation date
-</p></dd><dt><span class="term">trust </span></dt><dd><p>sort by the trust of the key
-</p></dd></dl></div><p>
-If you prefer reverse order of the above values, prefix it with
-“<span class="quote">reverse-</span>”.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-auto"></a>3.167. pgp_mime_auto</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-This option controls whether Mutt will prompt you for
-automatically sending a (signed/encrypted) message using
-PGP/MIME when inline (traditional) fails (for any reason).
-</p><p>
-Also note that using the old-style PGP message format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-auto-decode"></a>3.168. pgp_auto_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt 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 <code class="literal"><a class="link" href="gettingstarted.html#check-traditional-pgp"><check-traditional-pgp></a></code> function, mutt will automatically
-check the message for traditional pgp.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-filename"></a>3.169. pgp_mime_signature_filename</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">signature.asc</code></span>”</p></div><p>
-This option sets the filename used for signature parts in PGP/MIME
-signed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-mime-signature-description"></a>3.170. pgp_mime_signature_description</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">Digital signature</code></span>”</p></div><p>
-This option sets the Content-Description used for signature parts in
-PGP/MIME signed messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decode-command"></a>3.171. pgp_decode_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format strings specifies a command which is used to decode
-application/pgp attachments.
-</p><p>
-The PGP command formats have their own set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%p </span></dt><dd><p>Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
-string otherwise. Note: This may be used with a %? construct.
-</p></dd><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
- of a <code class="literal">multipart/signed</code> attachment when verifying it.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The value of <a class="link" href="reference.html#pgp-sign-as" title="3.163. pgp_sign_as">$pgp_sign_as</a>.
-</p></dd><dt><span class="term">%r </span></dt><dd><p>One or more key IDs.
-</p></dd></dl></div><p>
-For examples on how to configure these formats for the various versions
-of PGP which are floating around, see the pgp and gpg sample configuration files in
-the <code class="literal">samples/</code> subdirectory which has been installed on your system
-alongside the documentation.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-getkeys-command"></a>3.172. pgp_getkeys_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is invoked whenever mutt will need public key information.
-Of the sequences supported by <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a>, %r is the only
-<code class="literal">printf(3)</code>-like sequence used with this format.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-command"></a>3.173. pgp_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify PGP signatures.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-decrypt-command"></a>3.174. pgp_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to decrypt a PGP encrypted message.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-clearsign-command"></a>3.175. pgp_clearsign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format is used to create an old-style “<span class="quote">clearsigned</span>” PGP
-message. Note that the use of this format is <span class="bold"><strong>strongly</strong></span>
-<span class="bold"><strong>deprecated</strong></span>.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-sign-command"></a>3.176. pgp_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to create the detached PGP signature for a
-<code class="literal">multipart/signed</code> PGP/MIME body part.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-sign-command"></a>3.177. pgp_encrypt_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to both sign and encrypt a body part.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-encrypt-only-command"></a>3.178. pgp_encrypt_only_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to encrypt a body part without signing it.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-import-command"></a>3.179. pgp_import_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to import a key from a message into
-the user's public key ring.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-export-command"></a>3.180. pgp_export_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to export a public key from the user's
-key ring.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-verify-key-command"></a>3.181. pgp_verify_key_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify key information from the key selection
-menu.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-secring-command"></a>3.182. pgp_list_secring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to list the secret key ring's contents. The
-output format must be analogous to the one used by:
-
-</p><pre class="screen">
-gpg --list-keys --with-colons.
-
-</pre><p>
-This format is also generated by the <code class="literal">pgpring</code> utility which comes
-with mutt.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp-list-pubring-command"></a>3.183. pgp_list_pubring_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to list the public key ring's contents. The
-output format must be analogous to the one used by
-
-</p><pre class="screen">
-gpg --list-keys --with-colons.
-
-</pre><p>
-This format is also generated by the <code class="literal">pgpring</code> utility which comes
-with mutt.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#pgp-decode-command" title="3.171. pgp_decode_command">$pgp_decode_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="forward-decrypt"></a>3.184. forward_decrypt</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the handling of encrypted messages when forwarding a message.
-When <span class="emphasis"><em>set</em></span>, the outer layer of encryption is stripped off. This
-variable is only used if <a class="link" href="reference.html#mime-forward" title="3.127. mime_forward">$mime_forward</a> is <span class="emphasis"><em>set</em></span> and
-<a class="link" href="reference.html#mime-forward-decode" title="3.128. mime_forward_decode">$mime_forward_decode</a> is <span class="emphasis"><em>unset</em></span>.
-(PGP only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-timeout"></a>3.185. smime_timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 300</p></div><p>
-The number of seconds after which a cached passphrase will expire if
-not used.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-with"></a>3.186. smime_encrypt_with</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This sets the algorithm that should be used for encryption.
-Valid choices are “<span class="quote">des</span>”, “<span class="quote">des3</span>”, “<span class="quote">rc2-40</span>”, “<span class="quote">rc2-64</span>”, “<span class="quote">rc2-128</span>”.
-If <span class="emphasis"><em>unset</em></span>, “<span class="quote">3des</span>” (TripleDES) is used.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-keys"></a>3.187. smime_keys</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle
-storage and 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 option points to the location of the private keys.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-ca-location"></a>3.188. smime_ca_location</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable contains the name of either a directory, or a file which
-contains trusted certificates for use with OpenSSL.
-(S/MIME only)
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this defaults to the first existing file in
-the following list: ˜/.smime/ca-certificates.crt ˜/.smime/ca-bundle.crt
-/etc/ssl/certs/ca-certificates.crt.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-certificates"></a>3.189. smime_certificates</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Since for S/MIME there is no pubring/secring as with PGP, mutt 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 option points to
-the location of the certificates.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-decrypt-command"></a>3.190. smime_decrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This format string specifies a command which is used to decrypt
-<code class="literal">application/x-pkcs7-mime</code> attachments.
-</p><p>
-The OpenSSL command formats have their own set of <code class="literal">printf(3)</code>-like sequences
-similar to PGP's:
-
-</p><div class="variablelist"><dl><dt><span class="term">%f </span></dt><dd><p>Expands to the name of a file containing a message.
-</p></dd><dt><span class="term">%s </span></dt><dd><p>Expands to the name of a file containing the signature part
- of a <code class="literal">multipart/signed</code> attachment when verifying it.
-</p></dd><dt><span class="term">%k </span></dt><dd><p>The key-pair specified with <a class="link" href="reference.html#smime-default-key" title="3.201. smime_default_key">$smime_default_key</a>
-</p></dd><dt><span class="term">%c </span></dt><dd><p>One or more certificate IDs.
-</p></dd><dt><span class="term">%a </span></dt><dd><p>The algorithm used for encryption.
-</p></dd><dt><span class="term">%C </span></dt><dd><p>CA location: Depending on whether <a class="link" href="reference.html#smime-ca-location" title="3.188. smime_ca_location">$smime_ca_location</a>
- points to a directory or file, this expands to
- “<span class="quote">-CApath <a class="link" href="reference.html#smime-ca-location" title="3.188. smime_ca_location">$smime_ca_location</a></span>” or “<span class="quote">-CAfile <a class="link" href="reference.html#smime-ca-location" title="3.188. smime_ca_location">$smime_ca_location</a></span>”.
-</p></dd></dl></div><p>
-For examples on how to configure these formats, see the <code class="literal">smime.rc</code> in
-the <code class="literal">samples/</code> subdirectory which has been installed on your system
-alongside the documentation.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-command"></a>3.191. smime_verify_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify S/MIME signatures of type <code class="literal">multipart/signed</code>.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-verify-opaque-command"></a>3.192. smime_verify_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to verify S/MIME signatures of type
-<code class="literal">application/x-pkcs7-mime</code>.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-command"></a>3.193. smime_sign_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to created S/MIME signatures of type
-<code class="literal">multipart/signed</code>, which can be read by all mail clients.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-sign-opaque-command"></a>3.194. smime_sign_opaque_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to created S/MIME signatures of type
-<code class="literal">application/x-pkcs7-signature</code>, which can only be handled by mail
-clients supporting the S/MIME extension.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-encrypt-command"></a>3.195. smime_encrypt_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to create encrypted S/MIME messages.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-pk7out-command"></a>3.196. smime_pk7out_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to extract PKCS7 structures of S/MIME signatures,
-in order to extract the public X509 certificate(s).
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-command"></a>3.197. smime_get_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to extract X509 certificates from a PKCS7 structure.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-signer-cert-command"></a>3.198. smime_get_signer_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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 “<span class="quote">From:</span>” field.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-import-cert-command"></a>3.199. smime_import_cert_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This command is used to import a certificate via smime_keys.
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-get-cert-email-command"></a>3.200. smime_get_cert_email_command</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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).
-</p><p>
-This is a format string, see the <a class="link" href="reference.html#smime-decrypt-command" title="3.190. smime_decrypt_command">$smime_decrypt_command</a> command for
-possible <code class="literal">printf(3)</code>-like sequences.
-(S/MIME only)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime-default-key"></a>3.201. smime_default_key</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-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)
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-client-cert"></a>3.202. ssl_client_cert</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-The file containing a client certificate and its associated private
-key.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-force-tls"></a>3.203. ssl_force_tls</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If this variable is <span class="emphasis"><em>set</em></span>, Mutt 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 <a class="link" href="reference.html#ssl-starttls" title="3.204. ssl_starttls">$ssl_starttls</a>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-starttls"></a>3.204. ssl_starttls</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span> (the default), mutt will attempt to use <code class="literal">STARTTLS</code> on servers
-advertising the capability. When <span class="emphasis"><em>unset</em></span>, mutt will not attempt to
-use <code class="literal">STARTTLS</code> regardless of the server's capabilities.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="certificate-file"></a>3.205. certificate_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.mutt_certificates</code></span>”</p></div><p>
-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.
-</p><p>
-You can also manually add CA certificates in this file. Any server
-certificate that is signed with one of these CA certificates is
-also automatically accepted.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set certificate_file=~/.mutt/certificates
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-sslv3"></a>3.206. ssl_use_sslv3</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable specifies whether to attempt to use SSLv3 in the
-SSL authentication process.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-use-tlsv1"></a>3.207. ssl_use_tlsv1</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable specifies whether to attempt to use TLSv1 in the
-SSL authentication process.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-min-dh-prime-bits"></a>3.208. ssl_min_dh_prime_bits</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="ssl-ca-certificates-file"></a>3.209. ssl_ca_certificates_file</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable specifies a file containing trusted CA certificates.
-Any server certificate that is signed with one of these CA
-certificates is also automatically accepted.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
-
-</pre><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this variable defaults to the example
-mentioned. This file is managed by the “<span class="quote">ca-certificates</span>” package.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-split"></a>3.210. pipe_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><pipe-message></code> function following
-<code class="literal"><tag-prefix></code>. If this variable is <span class="emphasis"><em>unset</em></span>, when piping a list of
-tagged messages Mutt will concatenate the messages and will pipe them
-all concatenated. When <span class="emphasis"><em>set</em></span>, Mutt will pipe the messages one by one.
-In both cases the messages are piped in the current sorted order,
-and the <a class="link" href="reference.html#pipe-sep" title="3.212. pipe_sep">$pipe_sep</a> separator is added after each message.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-decode"></a>3.211. pipe_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><pipe-message></code> command. When <span class="emphasis"><em>unset</em></span>,
-Mutt will pipe the messages without any preprocessing. When <span class="emphasis"><em>set</em></span>, Mutt
-will weed headers and will attempt to decode the messages
-first.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pipe-sep"></a>3.212. pipe_sep</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">\n</code></span>”</p></div><p>
-The separator to add between messages when piping a list of tagged
-messages to an external Unix command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-authenticators"></a>3.213. pop_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an POP server, in the order mutt should
-try them. Authentication methods are either “<span class="quote">user</span>”, “<span class="quote">apop</span>” or any
-SASL mechanism, eg “<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
-This option is case-insensitive. If this option is <span class="emphasis"><em>unset</em></span>
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set pop_authenticators="digest-md5:apop:user"
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-auth-try-all"></a>3.214. pop_auth_try_all</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will try all available authentication methods.
-When <span class="emphasis"><em>unset</em></span>, Mutt will only fall back to other authentication
-methods if the previous methods are unavailable. If a method is
-available but authentication fails, Mutt will not connect to the POP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-checkinterval"></a>3.215. pop_checkinterval</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 60</p></div><p>
-This variable configures how often (in seconds) mutt should look for
-new mail in the currently selected mailbox if it is a POP mailbox.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-delete"></a>3.216. pop_delete</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, Mutt will delete successfully downloaded messages from the POP
-server when using the <code class="literal"><a class="link" href="optionalfeatures.html#fetch-mail"><fetch-mail></a></code> function. When <span class="emphasis"><em>unset</em></span>, Mutt will
-download messages but also leave them on the POP server.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-host"></a>3.217. pop_host</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-The name of your POP server for the <code class="literal"><a class="link" href="optionalfeatures.html#fetch-mail"><fetch-mail></a></code> function. You
-can also specify an alternative port, username and password, ie:
-
-</p><pre class="screen">
-[pop[s]://][username[:password]@]popserver[:port]
-
-</pre><p>
-where “<span class="quote">[...]</span>” denotes an optional part.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-last"></a>3.218. pop_last</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If this variable is <span class="emphasis"><em>set</em></span>, mutt will try to use the “<span class="quote"><code class="literal">LAST</code></span>” POP command
-for retrieving only unread messages from the POP server when using
-the <code class="literal"><a class="link" href="optionalfeatures.html#fetch-mail"><fetch-mail></a></code> function.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-reconnect"></a>3.219. pop_reconnect</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not Mutt will try to reconnect to the POP server if
-the connection is lost.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-user"></a>3.220. pop_user</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Your login name on the POP server.
-</p><p>
-This variable defaults to your user name on the local machine.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pop-pass"></a>3.221. pop_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your POP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you open a POP mailbox.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc
-even if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="post-indent-string"></a>3.222. post_indent_string</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Similar to the <a class="link" href="reference.html#attribution" title="3.16. attribution">$attribution</a> variable, Mutt will append this
-string after the inclusion of a message which is being replied to.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone"></a>3.223. postpone</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not messages are saved in the <a class="link" href="reference.html#postponed" title="3.224. postponed">$postponed</a>
-mailbox when you elect not to send immediately.
-</p><p>
-Also see the <a class="link" href="reference.html#recall" title="3.238. recall">$recall</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postponed"></a>3.224. postponed</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/postponed</code></span>”</p></div><p>
-Mutt allows you to indefinitely “<span class="quote"><a class="link" href="reference.html#postpone" title="3.223. postpone">postpone</a> sending a message</span>” which
-you are editing. When you choose to postpone a message, Mutt saves it
-in the mailbox specified by this variable.
-</p><p>
-Also see the <a class="link" href="reference.html#postpone" title="3.223. postpone">$postpone</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="preconnect"></a>3.225. preconnect</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-If <span class="emphasis"><em>set</em></span>, a shell command to be executed if mutt fails to establish
-a connection to the server. This is useful for setting up secure
-connections, e.g. with <code class="literal">ssh(1)</code>. If the command returns a nonzero
-status, mutt gives up opening the server. Example:
-
-</p><pre class="screen">
-set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \
-sleep 20 < /dev/null > /dev/null"
-
-</pre><p>
-Mailbox “<span class="quote">foo</span>” on “<span class="quote">mailhost.net</span>” can now be reached
-as “<span class="quote">{localhost:1234}foo</span>”.
-</p><p>
-Note: For this example to work, you must be able to log in to the
-remote machine without having to enter a password.
-</p><p>
-When set, Mutt uses the tunnel for all remote connections.
-Please see “<span class="quote"><a class="link" href="optionalfeatures.html#account-hook" title="6. Managing multiple accounts">account-hook</a></span>” in the manual for how to use different
-tunnel commands per connection.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print"></a>3.226. print</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-no</p></div><p>
-Controls whether or not Mutt really prints messages.
-This is set to “<span class="quote">ask-no</span>” by default, because some people
-accidentally hit “<span class="quote">p</span>” often.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-command"></a>3.227. print_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">lpr</code></span>”</p></div><p>
-This specifies the command pipe that should be used to print messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-decode"></a>3.228. print_decode</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Used in connection with the <code class="literal"><print-message></code> command. If this
-option is <span class="emphasis"><em>set</em></span>, the message is decoded before it is passed to the
-external command specified by <a class="link" href="reference.html#print-command" title="3.227. print_command">$print_command</a>. If this option
-is <span class="emphasis"><em>unset</em></span>, 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="print-split"></a>3.229. print_split</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Used in connection with the <code class="literal"><print-message></code> command. If this option
-is <span class="emphasis"><em>set</em></span>, the command specified by <a class="link" href="reference.html#print-command" title="3.227. print_command">$print_command</a> is executed once for
-each message which is to be printed. If this option is <span class="emphasis"><em>unset</em></span>,
-the command specified by <a class="link" href="reference.html#print-command" title="3.227. print_command">$print_command</a> is executed only once, and
-all the messages are concatenated, with a form feed as the message
-separator.
-</p><p>
-Those who use the <code class="literal">enscript</code>(1) program's mail-printing mode will
-most likely want to <span class="emphasis"><em>set</em></span> this option.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="prompt-after"></a>3.230. prompt_after</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If you use an <span class="emphasis"><em>external</em></span> <a class="link" href="reference.html#pager" title="3.138. pager">$pager</a>, setting this variable will
-cause Mutt to prompt you for a command when the pager exits rather
-than returning to the index menu. If <span class="emphasis"><em>unset</em></span>, Mutt will return to the
-index menu when the external pager exits.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-command"></a>3.231. query_command</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This specifies the command that mutt will use to make external address
-queries. The string should contain a “<span class="quote">%s</span>”, which will be substituted
-with the query string the user types. See “<span class="quote"><a class="link" href="advancedusage.html#query" title="5. External Address Queries">query</a></span>” for more
-information.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query-format"></a>3.232. query_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">%4c %t %-25.25a %-25.25n %?e?(%e)?</code></span>”</p></div><p>
-This variable describes the format of the “<span class="quote">query</span>” menu. The
-following <code class="literal">printf(3)</code>-style sequences are understood:
-
-</p><div class="variablelist"><dl><dt><span class="term">%a </span></dt><dd><p>destination address
-</p></dd><dt><span class="term">%c </span></dt><dd><p>current entry number
-</p></dd><dt><span class="term">%e </span></dt><dd><p>extra information *
-</p></dd><dt><span class="term">%n </span></dt><dd><p>destination name
-</p></dd><dt><span class="term">%t </span></dt><dd><p>“<span class="quote">*</span>” if current entry is tagged, a space otherwise
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p><p>
-* = can be optionally printed if nonzero, see the <a class="link" href="reference.html#status-format" title="3.278. status_format">$status_format</a> documentation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quit"></a>3.233. quit</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: yes</p></div><p>
-This variable controls whether “<span class="quote">quit</span>” and “<span class="quote">exit</span>” actually quit
-from mutt. If this option is <span class="emphasis"><em>set</em></span>, they do quit, if it is <span class="emphasis"><em>unset</em></span>, they
-have no effect, and if it is set to <span class="emphasis"><em>ask-yes</em></span> or <span class="emphasis"><em>ask-no</em></span>, you are
-prompted for confirmation when you try to quit.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="quote-regexp"></a>3.234. quote_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^([ \t]*[|>:}#])+</code></span>”</p></div><p>
-A regular expression used in the internal pager to determine quoted
-sections of text in the body of a message. Quoted text may be filtered
-out using the <code class="literal"><toggle-quoted></code> command, or colored according to the
-“<span class="quote">color quoted</span>” family of directives.
-</p><p>
-Higher levels of quoting may be colored differently (“<span class="quote">color quoted1</span>”,
-“<span class="quote">color quoted2</span>”, etc.). The quoting level is determined by removing
-the last character from the matched text and recursively reapplying
-the regular expression until it fails to produce a match.
-</p><p>
-Match detection may be overridden by the <a class="link" href="reference.html#smileys" title="3.265. smileys">$smileys</a> regular expression.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-inc"></a>3.235. read_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-If set to a value greater than 0, Mutt will display which message it
-is currently on when reading a mailbox or when performing search actions
-such as search and limit. The message is printed after
-this many messages have been read or searched (e.g., if set to 25, Mutt will
-print a message when it is at message 25, and then again when it gets
-to message 50). This variable is meant to indicate progress when
-reading or searching large mailboxes which may take some time.
-When set to 0, only a single message will appear before the reading
-the mailbox.
-</p><p>
-Also see the <a class="link" href="reference.html#write-inc" title="3.305. write_inc">$write_inc</a>, <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="reference.html#time-inc" title="3.286. time_inc">$time_inc</a> variables and the
-“<span class="quote"><a class="link" href="tuning.html" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="read-only"></a>3.236. read_only</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, all folders are opened in read-only mode.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="realname"></a>3.237. realname</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This variable specifies what “<span class="quote">real</span>” or “<span class="quote">personal</span>” name should be used
-when sending messages.
-</p><p>
-By default, this is the GECOS field from <code class="literal">/etc/passwd</code>. Note that this
-variable will <span class="emphasis"><em>not</em></span> be used when the user has set a real name
-in the <a class="link" href="reference.html#from" title="3.66. from">$from</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="recall"></a>3.238. recall</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-Controls whether or not Mutt recalls postponed messages
-when composing a new message.
-</p><p>
-<span class="emphasis"><em>Setting</em></span> this variable to is not generally useful, and thus not
-recommended.
-</p><p>
-Also see <a class="link" href="reference.html#postponed" title="3.224. postponed">$postponed</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="record"></a>3.239. record</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/sent</code></span>”</p></div><p>
-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 “<span class="quote"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command to create a “<span class="quote">Bcc:</span>” field with your email address in it.)
-</p><p>
-The value of <span class="emphasis"><em><a class="link" href="reference.html#record" title="3.239. record">$record</a></em></span> is overridden by the <a class="link" href="reference.html#force-name" title="3.61. force_name">$force_name</a> and
-<a class="link" href="reference.html#save-name" title="3.251. save_name">$save_name</a> variables, and the “<span class="quote"><a class="link" href="configuration.html#fcc-hook" title="17. Specify default Fcc: mailbox when composing">fcc-hook</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-regexp"></a>3.240. reply_regexp</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">^(re([\[0-9\]+])*|aw):[ \t]*</code></span>”</p></div><p>
-A regular expression used to recognize reply messages when threading
-and replying. The default value corresponds to the English "Re:" and
-the German "Aw:".
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-self"></a>3.241. reply_self</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>unset</em></span> and you are replying to a message sent by you, Mutt will
-assume that you want to reply to the recipients of that message rather
-than to yourself.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reply-to"></a>3.242. reply_to</h3></div></div></div><div class="literallayout"><p>Type: quadoption<br />
-Default: ask-yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, when replying to a message, Mutt will use the address listed
-in the Reply-to: header as the recipient of the reply. If <span class="emphasis"><em>unset</em></span>,
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="resolve"></a>3.243. resolve</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the cursor will be automatically advanced to the next
-(possibly undeleted) message whenever a command that modifies the
-current message is executed.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-alias"></a>3.244. reverse_alias</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls whether or not Mutt will display the “<span class="quote">personal</span>”
-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:
-
-</p><pre class="screen">
-alias juser abd30425@somewhere.net (Joe User)
-
-</pre><p>
-and then you receive mail which contains the following header:
-
-</p><pre class="screen">
-From: abd30425@somewhere.net
-
-</pre><p>
-It would be displayed in the index menu as “<span class="quote">Joe User</span>” instead of
-“<span class="quote">abd30425@somewhere.net.</span>” This is useful when the person's e-mail
-address is not human friendly.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-name"></a>3.245. reverse_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-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 <span class="emphasis"><em>set</em></span>, the default <span class="emphasis"><em>From:</em></span> line of
-the reply messages is built using the address where you received the
-messages you are replying to <span class="bold"><strong>if</strong></span> that address matches your
-“<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>”. If the variable is <span class="emphasis"><em>unset</em></span>, or the address that would be
-used doesn't match your “<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>”, the <span class="emphasis"><em>From:</em></span> line will use
-your address on the current machine.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="configuration.html#alternates" title="11. Alternative addresses">alternates</a></span>” command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="reverse-realname"></a>3.246. reverse_realname</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable fine-tunes the behaviour of the <a class="link" href="reference.html#reverse-name" title="3.245. reverse_name">$reverse_name</a> feature.
-When it is <span class="emphasis"><em>set</em></span>, mutt will use the address from incoming messages as-is,
-possibly including eventual real names. When it is <span class="emphasis"><em>unset</em></span>, mutt will
-override any such real names with the setting of the <a class="link" href="reference.html#realname" title="3.237. realname">$realname</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="rfc2047-parameters"></a>3.247. rfc2047_parameters</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When this variable is <span class="emphasis"><em>set</em></span>, Mutt will decode RFC2047-encoded MIME
-parameters. You want to set this variable when mutt suggests you
-to save attachments to files named like:
-
-</p><pre class="screen">
-=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=
-
-</pre><p>
-When this variable is <span class="emphasis"><em>set</em></span> interactively, the change won't be
-active until you change folders.
-</p><p>
-Note that this use of RFC2047's encoding is explicitly
-prohibited by the standard, but nevertheless encountered in the
-wild.
-</p><p>
-Also note that setting this parameter will <span class="emphasis"><em>not</em></span> have the effect
-that mutt <span class="emphasis"><em>generates</em></span> this kind of encoding. Instead, mutt will
-unconditionally use the encoding specified in RFC2231.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-address"></a>3.248. save_address</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, mutt will take the sender's full address when choosing a
-default folder for saving a mail. If <a class="link" href="reference.html#save-name" title="3.251. save_name">$save_name</a> or <a class="link" href="reference.html#force-name" title="3.61. force_name">$force_name</a>
-is <span class="emphasis"><em>set</em></span> too, the selection of the Fcc folder will be changed as well.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-empty"></a>3.249. save_empty</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mailboxes which contain no saved messages will be removed
-when closed (the exception is <a class="link" href="reference.html#spoolfile" title="3.276. spoolfile">$spoolfile</a> which is never removed).
-If <span class="emphasis"><em>set</em></span>, mailboxes are never removed.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> This only applies to mbox and MMDF folders, Mutt does not
-delete MH and Maildir directories.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-history"></a>3.250. save_history</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-This variable controls the size of the history (per category) saved in the
-<a class="link" href="reference.html#history-file" title="3.78. history_file">$history_file</a> file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="save-name"></a>3.251. save_name</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-This variable controls how copies of outgoing messages are saved.
-When <span class="emphasis"><em>set</em></span>, 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 <a class="link" href="reference.html#folder" title="3.58. folder">$folder</a> directory with the <span class="emphasis"><em>username</em></span> 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
-<a class="link" href="reference.html#record" title="3.239. record">$record</a> mailbox.
-</p><p>
-Also see the <a class="link" href="reference.html#force-name" title="3.61. force_name">$force_name</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score"></a>3.252. score</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When this variable is <span class="emphasis"><em>unset</em></span>, scoring is turned off. This can
-be useful to selectively disable scoring for certain folders when the
-<a class="link" href="reference.html#score-threshold-delete" title="3.253. score_threshold_delete">$score_threshold_delete</a> variable and related are used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-delete"></a>3.253. score_threshold_delete</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: -1</p></div><p>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked for deletion by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message for deletion.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-flag"></a>3.254. score_threshold_flag</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 9999</p></div><p>
-Messages which have been assigned a score greater than or equal to this
-variable's value are automatically marked "flagged".
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="score-threshold-read"></a>3.255. score_threshold_read</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: -1</p></div><p>
-Messages which have been assigned a score equal to or lower than the value
-of this variable are automatically marked as read by mutt. Since
-mutt scores are always greater than or equal to zero, the default setting
-of this variable will never mark a message read.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="send-charset"></a>3.256. send_charset</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">us-ascii:iso-8859-1:utf-8</code></span>”</p></div><p>
-A colon-delimited list of character sets for outgoing messages. Mutt will use the
-first character set into which the text can be converted exactly.
-If your <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> is not “<span class="quote">iso-8859-1</span>” and recipients may not
-understand “<span class="quote">UTF-8</span>”, it is advisable to include in the list an
-appropriate widely used standard character set (such as
-“<span class="quote">iso-8859-2</span>”, “<span class="quote">koi8-r</span>” or “<span class="quote">iso-2022-jp</span>”) either instead of or after
-“<span class="quote">iso-8859-1</span>”.
-</p><p>
-In case the text cannot be converted into one of these exactly,
-mutt uses <a class="link" href="reference.html#charset" title="3.25. charset">$charset</a> as a fallback.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail"></a>3.257. sendmail</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">/usr/sbin/sendmail -oem -oi</code></span>”</p></div><p>
-Specifies the program and arguments used to deliver mail sent by Mutt.
-Mutt expects that the specified program interprets additional
-arguments as recipient addresses.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sendmail-wait"></a>3.258. sendmail_wait</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-Specifies the number of seconds to wait for the <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a> process
-to finish before giving up and putting delivery in the background.
-</p><p>
-Mutt interprets the value of this variable as follows:
-
-</p><div class="variablelist"><dl><dt><span class="term">>0 </span></dt><dd><p>number of seconds to wait for sendmail to finish before continuing
-</p></dd><dt><span class="term">0 </span></dt><dd><p>wait forever for sendmail to finish
-</p></dd><dt><span class="term"><0 </span></dt><dd><p>always put sendmail in the background without waiting
-</p></dd></dl></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="shell"></a>3.259. shell</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Command to use when spawning a subshell. By default, the user's login
-shell from <code class="literal">/etc/passwd</code> is used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-dashes"></a>3.260. sig_dashes</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-If <span class="emphasis"><em>set</em></span>, a line containing “<span class="quote">-- </span>” (note the trailing space) will be inserted before your
-<a class="link" href="reference.html#signature" title="3.262. signature">$signature</a>. It is <span class="bold"><strong>strongly</strong></span> recommended that you not <span class="emphasis"><em>unset</em></span>
-this variable unless your signature contains just your name. The
-reason for this is because many software packages use “<span class="quote">-- \n</span>” to
-detect your signature. For example, Mutt has the ability to highlight
-the signature in a different color in the builtin pager.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sig-on-top"></a>3.261. sig_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, the signature will be included before any quoted or forwarded
-text. It is <span class="bold"><strong>strongly</strong></span> 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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="signature"></a>3.262. signature</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: “<span class="quote"><code class="literal">˜/.signature</code></span>”</p></div><p>
-Specifies the filename of your signature, which is appended to all
-outgoing messages. If the filename ends with a pipe (“<span class="quote">|</span>”), it is
-assumed that filename is a shell command and input should be read from
-its standard output.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="simple-search"></a>3.263. simple_search</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">˜f %s | ˜s %s</code></span>”</p></div><p>
-Specifies how Mutt should expand a simple search into a real search
-pattern. A simple search is one that does not contain any of the “<span class="quote">˜</span>” pattern
-operators. See “<span class="quote"><a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>” for more information on search patterns.
-</p><p>
-For example, if you simply type “<span class="quote">joe</span>” at a search or limit prompt, Mutt
-will automatically expand it to the value specified by this variable by
-replacing “<span class="quote">%s</span>” with the supplied string.
-For the default value, “<span class="quote">joe</span>” would be expanded to: “<span class="quote">˜f joe | ˜s joe</span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smart-wrap"></a>3.264. smart_wrap</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls the display of lines longer than the screen width in the
-internal pager. If <span class="emphasis"><em>set</em></span>, long lines are wrapped at a word boundary. If
-<span class="emphasis"><em>unset</em></span>, lines are simply wrapped at the screen edge. Also see the
-<a class="link" href="reference.html#markers" title="3.114. markers">$markers</a> variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smileys"></a>3.265. smileys</h3></div></div></div><div class="literallayout"><p>Type: regular expression<br />
-Default: “<span class="quote"><code class="literal">(>From )|(:[-^]?[][)(><}{|/DP])</code></span>”</p></div><p>
-The <span class="emphasis"><em>pager</em></span> uses this variable to catch some common false
-positives of <a class="link" href="reference.html#quote-regexp" title="3.234. quote_regexp">$quote_regexp</a>, most notably smileys and not consider
-a line quoted text if it also matches <a class="link" href="reference.html#smileys" title="3.265. smileys">$smileys</a>. This mostly
-happens at the beginning of a line.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sleep-time"></a>3.266. sleep_time</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 1</p></div><p>
-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.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-authenticators"></a>3.267. smtp_authenticators</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-This is a colon-delimited list of authentication methods mutt may
-attempt to use to log in to an SMTP server, in the order mutt should
-try them. Authentication methods are any SASL mechanism, eg
-“<span class="quote">digest-md5</span>”, “<span class="quote">gssapi</span>” or “<span class="quote">cram-md5</span>”.
-This option is case-insensitive. If it is “<span class="quote">unset</span>”
-(the default) mutt will try all available methods, in order from
-most-secure to least-secure.
-</p><p>
-Example:
-
-</p><pre class="screen">
-set smtp_authenticators="digest-md5:cram-md5"
-
-</pre></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-pass"></a>3.268. smtp_pass</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Specifies the password for your SMTP account. If <span class="emphasis"><em>unset</em></span>, Mutt will
-prompt you for your password when you first send mail via SMTP.
-See <a class="link" href="reference.html#smtp-url" title="3.269. smtp_url">$smtp_url</a> to configure mutt to send mail via SMTP.
-</p><p>
-<span class="bold"><strong>Warning</strong></span>: you should only use this option when you are on a
-fairly secure machine, because the superuser can read your muttrc even
-if you are the only one who can read the file.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smtp-url"></a>3.269. smtp_url</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Defines the SMTP smarthost where sent messages should relayed for
-delivery. This should take the form of an SMTP URL, eg:
-
-</p><pre class="screen">
-smtp[s]://[user[:pass]@]host[:port]/
-
-</pre><p>
-\.\.\. where “<span class="quote">[...]</span>” denotes an optional part.
-Setting this variable overrides the value of the <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a>
-variable.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort"></a>3.270. sort</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: date</p></div><p>
-Specifies how to sort messages in the “<span class="quote">index</span>” menu. Valid values
-are:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>date or date-sent
-</p></li><li><p>date-received
-</p></li><li><p>from
-</p></li><li><p>mailbox-order (unsorted)
-</p></li><li><p>score
-</p></li><li><p>size
-</p></li><li><p>spam
-</p></li><li><p>subject
-</p></li><li><p>threads
-</p></li><li><p>to
-</p></li></ul></div><p>
-You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
-order (example: “<span class="quote"><code class="literal">set sort=reverse-date-sent</code></span>”).
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, this option is set by default to
-“<span class="quote">threads</span>” in /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-alias"></a>3.271. sort_alias</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: alias</p></div><p>
-Specifies how the entries in the “<span class="quote">alias</span>” menu are sorted. The
-following are legal values:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>address (sort alphabetically by email address)
-</p></li><li><p>alias (sort alphabetically by alias name)
-</p></li><li><p>unsorted (leave in order specified in .muttrc)
-</p></li></ul></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-aux"></a>3.272. sort_aux</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: date</p></div><p>
-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 <a class="link" href="reference.html#sort" title="3.270. sort">$sort</a> can, except
-“<span class="quote">threads</span>” (in that case, mutt will just use “<span class="quote">date-sent</span>”). You can also
-specify the “<span class="quote">last-</span>” prefix in addition to the “<span class="quote">reverse-</span>” prefix, but “<span class="quote">last-</span>”
-must come after “<span class="quote">reverse-</span>”. The “<span class="quote">last-</span>” prefix causes messages to be
-sorted against its siblings by which has the last descendant, using
-the rest of <a class="link" href="reference.html#sort-aux" title="3.272. sort_aux">$sort_aux</a> as an ordering. For instance,
-
-</p><pre class="screen">
-set sort_aux=last-date-received
-
-</pre><p>
-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 “<span class="quote"><code class="literal">set sort=reverse-threads</code></span>”.)
-</p><p>
-Note: For reversed <a class="link" href="reference.html#sort" title="3.270. sort">$sort</a>
-order <a class="link" href="reference.html#sort-aux" title="3.272. sort_aux">$sort_aux</a> is reversed again (which is not the right thing to do,
-but kept to not break any existing configuration setting).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-browser"></a>3.273. sort_browser</h3></div></div></div><div class="literallayout"><p>Type: sort order<br />
-Default: alpha</p></div><p>
-Specifies how to sort entries in the file browser. By default, the
-entries are sorted alphabetically. Valid values:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>alpha (alphabetically)
-</p></li><li><p>date
-</p></li><li><p>size
-</p></li><li><p>unsorted
-</p></li></ul></div><p>
-You may optionally use the “<span class="quote">reverse-</span>” prefix to specify reverse sorting
-order (example: “<span class="quote"><code class="literal">set sort_browser=reverse-date</code></span>”).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="sort-re"></a>3.274. sort_re</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-This variable is only useful when sorting by threads with
-<a class="link" href="reference.html#strict-threads" title="3.280. strict_threads">$strict_threads</a> <span class="emphasis"><em>unset</em></span>. In that case, it changes the heuristic
-mutt uses to thread messages by subject. With <a class="link" href="reference.html#sort-re" title="3.274. sort_re">$sort_re</a> <span class="emphasis"><em>set</em></span>, mutt 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 <a class="link" href="reference.html#reply-regexp" title="3.240. reply_regexp">$reply_regexp</a>. With <a class="link" href="reference.html#sort-re" title="3.274. sort_re">$sort_re</a> <span class="emphasis"><em>unset</em></span>, mutt will attach
-the message whether or not this is the case, as long as the
-non-<a class="link" href="reference.html#reply-regexp" title="3.240. reply_regexp">$reply_regexp</a> parts of both messages are identical.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spam-separator"></a>3.275. spam_separator</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">,</code></span>”</p></div><p>
-This variable controls what happens when multiple spam headers
-are matched: if <span class="emphasis"><em>unset</em></span>, each successive header will overwrite any
-previous matches value for the spam label. If <span class="emphasis"><em>set</em></span>, each successive
-match will append to the previous, using this variable's value as a
-separator.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="spoolfile"></a>3.276. spoolfile</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-If your spool mailbox is in a non-default place where Mutt cannot find
-it, you can specify its location with this variable. Mutt will
-automatically set this variable to the value of the environment
-variable <code class="literal">$MAIL</code> if it is not set.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-chars"></a>3.277. status_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-*%A</code></span>”</p></div><p>
-Controls the characters used by the “<span class="quote">%r</span>” indicator in
-<a class="link" href="reference.html#status-format" title="3.278. status_format">$status_format</a>. 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 <code class="literal"><toggle-write></code> operation, bound by default to “<span class="quote">%</span>”). 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).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-format"></a>3.278. status_format</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">-%r-Mutt: %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)---</code></span>”</p></div><p>
-Controls the format of the status line displayed in the “<span class="quote">index</span>”
-menu. This string is similar to <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a>, but has its own
-set of <code class="literal">printf(3)</code>-like sequences:
-
-</p><div class="variablelist"><dl><dt><span class="term">%b </span></dt><dd><p>number of mailboxes with new mail *
-</p></dd><dt><span class="term">%d </span></dt><dd><p>number of deleted messages *
-</p></dd><dt><span class="term">%f </span></dt><dd><p>the full pathname of the current mailbox
-</p></dd><dt><span class="term">%F </span></dt><dd><p>number of flagged messages *
-</p></dd><dt><span class="term">%h </span></dt><dd><p>local hostname
-</p></dd><dt><span class="term">%l </span></dt><dd><p>size (in bytes) of the current mailbox *
-</p></dd><dt><span class="term">%L </span></dt><dd><p>size (in bytes) of the messages shown
-(i.e., which match the current limit) *
-</p></dd><dt><span class="term">%m </span></dt><dd><p>the number of messages in the mailbox *
-</p></dd><dt><span class="term">%M </span></dt><dd><p>the number of messages shown (i.e., which match the current limit) *
-</p></dd><dt><span class="term">%n </span></dt><dd><p>number of new messages in the mailbox *
-</p></dd><dt><span class="term">%o </span></dt><dd><p>number of old unread messages *
-</p></dd><dt><span class="term">%p </span></dt><dd><p>number of postponed messages *
-</p></dd><dt><span class="term">%P </span></dt><dd><p>percentage of the way through the index
-</p></dd><dt><span class="term">%r </span></dt><dd><p>modified/read-only/won't-write/attach-message indicator,
-according to <a class="link" href="reference.html#status-chars" title="3.277. status_chars">$status_chars</a>
-</p></dd><dt><span class="term">%s </span></dt><dd><p>current sorting mode (<a class="link" href="reference.html#sort" title="3.270. sort">$sort</a>)
-</p></dd><dt><span class="term">%S </span></dt><dd><p>current aux sorting method (<a class="link" href="reference.html#sort-aux" title="3.272. sort_aux">$sort_aux</a>)
-</p></dd><dt><span class="term">%t </span></dt><dd><p>number of tagged messages *
-</p></dd><dt><span class="term">%u </span></dt><dd><p>number of unread messages *
-</p></dd><dt><span class="term">%v </span></dt><dd><p>Mutt version string
-</p></dd><dt><span class="term">%V </span></dt><dd><p>currently active limit pattern, if any *
-</p></dd><dt><span class="term">%>X </span></dt><dd><p>right justify the rest of the string and pad with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%|X </span></dt><dd><p>pad to the end of the line with “<span class="quote">X</span>”
-</p></dd><dt><span class="term">%*X </span></dt><dd><p>soft-fill with character “<span class="quote">X</span>” as pad
-</p></dd></dl></div><p>
-For an explanation of “<span class="quote">soft-fill</span>”, see the <a class="link" href="reference.html#index-format" title="3.101. index_format">$index_format</a> documentation.
-</p><p>
-* = can be optionally printed if nonzero
-</p><p>
-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:
-</p><p>
-<code class="literal">%?<sequence_char>?<optional_string>?</code>
-</p><p>
-where <span class="emphasis"><em>sequence_char</em></span> is a character from the table above, and
-<span class="emphasis"><em>optional_string</em></span> is the string you would like printed if
-<span class="emphasis"><em>sequence_char</em></span> is nonzero. <span class="emphasis"><em>optional_string</em></span> <span class="bold"><strong>may</strong></span> contain
-other sequences as well as normal text, but you may <span class="bold"><strong>not</strong></span> nest
-optional strings.
-</p><p>
-Here is an example illustrating how to optionally print the number of
-new messages in a mailbox:
-</p><p>
-<code class="literal">%?n?%n new messages.?</code>
-</p><p>
-You can also switch between two strings using the following construct:
-</p><p>
-<code class="literal">%?<sequence_char>?<if_string>&<else_string>?</code>
-</p><p>
-If the value of <span class="emphasis"><em>sequence_char</em></span> is non-zero, <span class="emphasis"><em>if_string</em></span> will
-be expanded, otherwise <span class="emphasis"><em>else_string</em></span> will be expanded.
-</p><p>
-You can force the result of any <code class="literal">printf(3)</code>-like sequence to be lowercase
-by prefixing the sequence character with an underscore (“<span class="quote">_</span>”) sign.
-For example, if you want to display the local hostname in lowercase,
-you would use: “<span class="quote"><code class="literal">%_h</code></span>”.
-</p><p>
-If you prefix the sequence character with a colon (“<span class="quote">:</span>”) character, mutt
-will replace any dots in the expansion by underscores. This might be helpful
-with IMAP folders that don't like dots in folder names.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="status-on-top"></a>3.279. status_on_top</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Setting this variable causes the “<span class="quote">status bar</span>” to be displayed on
-the first line of the screen rather than near the bottom. If <a class="link" href="reference.html#help" title="3.70. help">$help</a>
-is <span class="emphasis"><em>set</em></span>, too it'll be placed at the bottom.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="strict-threads"></a>3.280. strict_threads</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-If <span class="emphasis"><em>set</em></span>, threading will only make use of the “<span class="quote">In-Reply-To</span>” and
-“<span class="quote">References:</span>” fields when you <a class="link" href="reference.html#sort" title="3.270. sort">$sort</a> by message threads. By
-default, messages with the same subject are grouped together in
-“<span class="quote">pseudo threads.</span>”. This may not always be desirable, such as in a
-personal mailbox where you might have several unrelated messages with
-the subjects like “<span class="quote">hi</span>” which will get grouped together. See also
-<a class="link" href="reference.html#sort-re" title="3.274. sort_re">$sort_re</a> for a less drastic way of controlling this
-behaviour.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="suspend"></a>3.281. suspend</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>unset</em></span>, mutt won't stop when the user presses the terminal's
-<span class="emphasis"><em>susp</em></span> key, usually “<span class="quote">^Z</span>”. This is useful if you run mutt
-inside an xterm using a command like “<span class="quote"><code class="literal">xterm -e mutt</code></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="text-flowed"></a>3.282. text_flowed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will generate “<span class="quote">format=flowed</span>” bodies with a content type
-of “<span class="quote"><code class="literal">text/plain; format=flowed</code></span>”.
-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.
-</p><p>
-Note that <a class="link" href="reference.html#indent-string" title="3.100. indent_string">$indent_string</a> is ignored when this option is <span class="emphasis"><em>set</em></span>.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thread-received"></a>3.283. thread_received</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt uses the date received rather than the date sent
-to thread messages by subject.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="thorough-search"></a>3.284. thorough_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Affects the <code class="literal">˜b</code> and <code class="literal">˜h</code> search operations described in
-section “<span class="quote"><a class="link" href="advancedusage.html#patterns" title="2. Patterns: Searching, Limiting and Tagging">patterns</a></span>”. If <span class="emphasis"><em>set</em></span>, the headers and body/attachments of
-messages to be searched are decoded before searching. If <span class="emphasis"><em>unset</em></span>,
-messages are searched as they appear in the folder.
-</p><p>
-Users searching attachments or for non-ASCII characters should <span class="emphasis"><em>set</em></span>
-this value because decoding also includes MIME parsing/decoding and possible
-character set conversions. Otherwise mutt will attempt to match against the
-raw message received (for example quoted-printable encoded or with encoded
-headers) which may lead to incorrect search results.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tilde"></a>3.285. tilde</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, the internal-pager will pad blank lines to the bottom of the
-screen with a tilde (“<span class="quote">˜</span>”).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="time-inc"></a>3.286. time_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-Along with <a class="link" href="reference.html#read-inc" title="3.235. read_inc">$read_inc</a>, <a class="link" href="reference.html#write-inc" title="3.305. write_inc">$write_inc</a>, and <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a>, this
-variable controls the frequency with which progress updates are
-displayed. It suppresses updates less than <a class="link" href="reference.html#time-inc" title="3.286. time_inc">$time_inc</a> milliseconds
-apart. This can improve throughput on systems with slow terminals,
-or when running mutt on a remote system.
-</p><p>
-Also see the “<span class="quote"><a class="link" href="tuning.html" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="timeout"></a>3.287. timeout</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 600</p></div><p>
-When Mutt is waiting for user input either idleing in menus or
-in an interactive prompt, Mutt would block until input is
-present. Depending on the context, this would prevent certain
-operations from working, like checking for new mail or keeping
-an IMAP connection alive.
-</p><p>
-This variable controls how many seconds Mutt will at most wait
-until it aborts waiting for input, performs these operations and
-continues to wait for input.
-</p><p>
-A value of zero or less will cause Mutt to never time out.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tmpdir"></a>3.288. tmpdir</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-This variable allows you to specify where Mutt will place its
-temporary files needed for displaying and composing messages. If
-this variable is not set, the environment variable <code class="literal">$TMPDIR</code> is
-used. If <code class="literal">$TMPDIR</code> is not set then “<span class="quote"><code class="literal">/tmp</code></span>” is used.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="to-chars"></a>3.289. to_chars</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal"> +TCFL</code></span>”</p></div><p>
-Controls the character used to indicate mail addressed to you. The
-first character is the one used when the mail is <span class="emphasis"><em>not</em></span> addressed to your
-address. The second is used when you are the only
-recipient of the message. The third is when your address
-appears in the “<span class="quote">To:</span>” header field, but you are not the only recipient of
-the message. The fourth character is used when your
-address is specified in the “<span class="quote">Cc:</span>” header field, but you are not the only
-recipient. The fifth character is used to indicate mail that was sent
-by <span class="emphasis"><em>you</em></span>. The sixth character is used to indicate when a mail
-was sent to a mailing-list you subscribe to.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="trash"></a>3.290. trash</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-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.
-</p><p>
-NOTE: When you delete a message in the trash folder, it is really
-deleted, so that you have a way to clean the trash.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="tunnel"></a>3.291. tunnel</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: (empty)</p></div><p>
-Setting this variable will cause mutt 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/SMTP server. Example:
-
-</p><pre class="screen">
-set tunnel="ssh -q mailhost.net /usr/local/libexec/imapd"
-
-</pre><p>
-Note: For this example to work you must be able to log in to the remote
-machine without having to enter a password.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-8bitmime"></a>3.292. use_8bitmime</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-<span class="bold"><strong>Warning:</strong></span> do not set this variable unless you are using a version
-of sendmail which supports the <code class="literal">-B8BITMIME</code> flag (such as sendmail
-8.8.x) or you may not be able to send mail.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will invoke <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a> with the <code class="literal">-B8BITMIME</code>
-flag when sending 8-bit messages to enable ESMTP negotiation.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-domain"></a>3.293. use_domain</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will qualify all local addresses (ones without the
-“<span class="quote">@host</span>” portion) with the value of <a class="link" href="reference.html#hostname" title="3.80. hostname">$hostname</a>. If <span class="emphasis"><em>unset</em></span>, no
-addresses will be qualified.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-envelope-from"></a>3.294. use_envelope_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will set the <span class="emphasis"><em>envelope</em></span> sender of the message.
-If <a class="link" href="reference.html#envelope-from-address" title="3.53. envelope_from_address">$envelope_from_address</a> is <span class="emphasis"><em>set</em></span>, it will be used as the sender
-address. If <span class="emphasis"><em>unset</em></span>, mutt will attempt to derive the sender from the
-“<span class="quote">From:</span>” header.
-</p><p>
-Note that this information is passed to sendmail command using the
-<code class="literal">-f</code> command line switch. Therefore setting this option is not useful
-if the <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a> variable already contains <code class="literal">-f</code> or if the
-executable pointed to by <a class="link" href="reference.html#sendmail" title="3.257. sendmail">$sendmail</a> doesn't support the <code class="literal">-f</code> switch.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-from"></a>3.295. use_from</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will generate the “<span class="quote">From:</span>” header field when
-sending messages. If <span class="emphasis"><em>unset</em></span>, no “<span class="quote">From:</span>” header field will be
-generated unless the user explicitly sets one using the “<span class="quote"><a class="link" href="configuration.html#my-hdr" title="15. User defined headers">my_hdr</a></span>”
-command.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-idn"></a>3.296. use_idn</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will show you international domain names decoded.
-Note: You can use IDNs for addresses even if this is <span class="emphasis"><em>unset</em></span>.
-This variable only affects decoding.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="use-ipv6"></a>3.297. use_ipv6</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will look for IPv6 addresses of hosts it tries to
-contact. If this option is <span class="emphasis"><em>unset</em></span>, Mutt will restrict itself to IPv4 addresses.
-Normally, the default should work.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="user-agent"></a>3.298. user_agent</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will add a “<span class="quote">User-Agent:</span>” header to outgoing
-messages, indicating which version of mutt was used for composing
-them.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="visual"></a>3.299. visual</h3></div></div></div><div class="literallayout"><p>Type: path<br />
-Default: (empty)</p></div><p>
-Specifies the visual editor to invoke when the “<span class="quote"><code class="literal">˜v</code></span>” command is
-given in the builtin editor.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wait-key"></a>3.300. wait_key</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether Mutt will ask you to press a key after an external command
-has been invoked by these functions: <code class="literal"><shell-escape></code>,
-<code class="literal"><pipe-message></code>, <code class="literal"><pipe-entry></code>, <code class="literal"><print-message></code>,
-and <code class="literal"><print-entry></code> commands.
-</p><p>
-It is also used when viewing attachments with “<span class="quote"><a class="link" href="mimesupport.html#auto-view" title="4. MIME Autoview">auto_view</a></span>”, provided
-that the corresponding mailcap entry has a <span class="emphasis"><em>needsterminal</em></span> flag,
-and the external program is interactive.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, Mutt will always ask for a key. When <span class="emphasis"><em>unset</em></span>, Mutt will wait
-for a key only if the external command returned a non-zero status.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="weed"></a>3.301. weed</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-When <span class="emphasis"><em>set</em></span>, mutt will weed headers when displaying, forwarding,
-printing, or replying to messages.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap"></a>3.302. wrap</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-When set to a positive value, mutt will wrap text at <a class="link" href="reference.html#wrap" title="3.302. wrap">$wrap</a> characters.
-When set to a negative value, mutt will wrap text so that there are <a class="link" href="reference.html#wrap" title="3.302. wrap">$wrap</a>
-characters of empty space on the right side of the terminal.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrap-search"></a>3.303. wrap_search</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether searches wrap around the end.
-</p><p>
-When <span class="emphasis"><em>set</em></span>, searches will wrap around the first (or last) item. When
-<span class="emphasis"><em>unset</em></span>, incremental searches will not wrap.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="wrapmargin"></a>3.304. wrapmargin</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 0</p></div><p>
-(DEPRECATED) Equivalent to setting <a class="link" href="reference.html#wrap" title="3.302. wrap">$wrap</a> with a negative value.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-inc"></a>3.305. write_inc</h3></div></div></div><div class="literallayout"><p>Type: number<br />
-Default: 10</p></div><p>
-When writing a mailbox, a message will be printed every
-<a class="link" href="reference.html#write-inc" title="3.305. write_inc">$write_inc</a> messages to indicate progress. If set to 0, only a
-single message will be displayed before writing a mailbox.
-</p><p>
-Also see the <a class="link" href="reference.html#read-inc" title="3.235. read_inc">$read_inc</a>, <a class="link" href="reference.html#net-inc" title="3.137. net_inc">$net_inc</a> and <a class="link" href="reference.html#time-inc" title="3.286. time_inc">$time_inc</a> variables and the
-“<span class="quote"><a class="link" href="tuning.html" title="Chapter 7. Performance tuning">tuning</a></span>” section of the manual for performance considerations.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="write-bcc"></a>3.306. write_bcc</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: yes</p></div><p>
-Controls whether mutt writes out the “<span class="quote">Bcc:</span>” header when preparing
-messages to be sent. Exim users may wish to unset this. If mutt
-is set to deliver directly via SMTP (see <a class="link" href="reference.html#smtp-url" title="3.269. smtp_url">$smtp_url</a>), this
-option does nothing: mutt will never write out the “<span class="quote">Bcc:</span>” header
-in this case.
-</p><p>
-<span class="bold"><strong>Note:</strong></span> On Debian systems, exim4 and postfix strip BCC headers by
-default. The above warning applies to exim3 users, see /etc/Muttrc.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-icon"></a>3.307. xterm_icon</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">M%?n?AIL&ail?</code></span>”</p></div><p>
-Controls the format of the icon title, as long as xterm_set_titles
-is enabled. This string is identical in formatting to the one used by
-“<span class="quote"><a class="link" href="reference.html#status-format" title="3.278. status_format">$status_format</a></span>”.
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-set-titles"></a>3.308. xterm_set_titles</h3></div></div></div><div class="literallayout"><p>Type: boolean<br />
-Default: no</p></div><p>
-Controls whether mutt sets the xterm title bar and icon name
-(as long as you are in an appropriate terminal).
-</p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="xterm-title"></a>3.309. xterm_title</h3></div></div></div><div class="literallayout"><p>Type: string<br />
-Default: “<span class="quote"><code class="literal">Mutt with %?m?%m messages&no messages?%?n? [%n NEW]?</code></span>”</p></div><p>
-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 “<span class="quote"><a class="link" href="reference.html#status-format" title="3.278. status_format">$status_format</a></span>”.
-</p></div></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="functions"></a>4. Functions</h2></div></div></div><p>
-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 <a class="link" href="configuration.html#bind" title="5. Changing the default key bindings">bind</a>
-command.
-</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="generic_map"></a>4.1. generic menu</h3></div></div></div><p>
-The <span class="emphasis"><em>generic</em></span> menu is not a real menu, but specifies common functions
-(such as movement) available in all menus except for <span class="emphasis"><em>pager</em></span> and
-<span class="emphasis"><em>editor</em></span>. Changing settings for this menu will affect the default
-bindings for all menus (except as noted).
-</p><div class="table"><a id="generic_table"></a><p class="title"><b>Table 8.2. Default generic function bindings</b></p><div class="table-contents"><table summary="Default generic function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><top-page></code></td><td>H</td><td>move to the top of the page</td></tr><tr><td><code class="literal"><next-entry></code></td><td>j</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>k</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><bottom-page></code></td><td>L</td><td>move to the bottom of the page</td></tr><tr><td><code class="literal"><refresh></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><middle-page></code></td><td>M</td><td>move to the middle of the page</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><tag-entry></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><next-page></code></td><td>z</td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>Z</td><td>move to the previous page</td></tr><tr><td><code class="literal"><last-entry></code></td><td>*</td><td>move to the last entry</td></tr><tr><td><code class="literal"><first-entry></code></td><td>=</td><td>move to the first entry</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><next-line></code></td><td>></td><td>scroll down one line</td></tr><tr><td><code class="literal"><previous-line></code></td><td><</td><td>scroll up one line</td></tr><tr><td><code class="literal"><half-up></code></td><td>[</td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td>]</td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><tag-prefix></code></td><td>;</td><td>apply next function to tagged messages</td></tr><tr><td><code class="literal"><tag-prefix-cond></code></td><td> </td><td>apply next function ONLY to tagged messages</td></tr><tr><td><code class="literal"><end-cond></code></td><td> </td><td>end of conditional execution (noop)</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><select-entry></code></td><td><Return></td><td>select the current entry</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><current-top></code></td><td> </td><td>move entry to top of screen</td></tr><tr><td><code class="literal"><current-middle></code></td><td> </td><td>move entry to middle of screen</td></tr><tr><td><code class="literal"><current-bottom></code></td><td> </td><td>move entry to bottom of screen</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="index_map"></a>4.2. index menu</h3></div></div></div><div class="table"><a id="index_table"></a><p class="title"><b>Table 8.3. Default index function bindings</b></p><div class="table-contents"><table summary="Default index function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><collapse-thread></code></td><td>Esc v</td><td>collapse/uncollapse current thread</td></tr><tr><td><code class="literal"><collapse-all></code></td><td>Esc V</td><td>collapse/uncollapse all threads</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-pattern></code></td><td>D</td><td>delete messages matching a pattern</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><fetch-mail></code></td><td>G</td><td>retrieve mail from POP server</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><limit></code></td><td>l</td><td>show only messages matching a pattern</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><toggle-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><toggle-write></code></td><td>%</td><td>toggle whether the mailbox will be rewritten</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><quit></code></td><td>q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><show-limit></code></td><td>Esc l</td><td>show currently active limit pattern</td></tr><tr><td><code class="literal"><sort-mailbox></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><tag-pattern></code></td><td>T</td><td>tag messages matching a pattern</td></tr><tr><td><code class="literal"><tag-subthread></code></td><td> </td><td>tag the current subthread</td></tr><tr><td><code class="literal"><tag-thread></code></td><td>Esc t</td><td>tag the current thread</td></tr><tr><td><code class="literal"><untag-pattern></code></td><td>^T</td><td>untag messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-pattern></code></td><td>U</td><td>undelete messages matching a pattern</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><set-flag></code></td><td>w</td><td>set a status flag on a message</td></tr><tr><td><code class="literal"><clear-flag></code></td><td>W</td><td>clear a status flag from a message</td></tr><tr><td><code class="literal"><display-message></code></td><td><Return></td><td>display a message</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><next-new-then-unread></code></td><td><Tab></td><td>jump to the next new or unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-new-then-unread></code></td><td>Esc <Tab></td><td>jump to the previous new or unread message</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pager_map"></a>4.3. pager menu</h3></div></div></div><div class="table"><a id="pager_table"></a><p class="title"><b>Table 8.4. Default pager function bindings</b></p><div class="table-contents"><table summary="Default pager function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><break-thread></code></td><td>#</td><td>break the thread in two</td></tr><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><change-folder></code></td><td>c</td><td>open a different folder</td></tr><tr><td><code class="literal"><change-folder-readonly></code></td><td>Esc c</td><td>open a different folder in read only mode</td></tr><tr><td><code class="literal"><next-unread-mailbox></code></td><td> </td><td>open next mailbox with new mail</td></tr><tr><td><code class="literal"><copy-message></code></td><td>C</td><td>copy a message to a file/mailbox</td></tr><tr><td><code class="literal"><decode-copy></code></td><td>Esc C</td><td>make decoded (text/plain) copy</td></tr><tr><td><code class="literal"><delete-message></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><delete-thread></code></td><td>^D</td><td>delete all messages in thread</td></tr><tr><td><code class="literal"><delete-subthread></code></td><td>Esc d</td><td>delete all messages in subthread</td></tr><tr><td><code class="literal"><edit></code></td><td>e</td><td>edit the raw message</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><flag-message></code></td><td>F</td><td>toggle a message's 'important' flag</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><imap-fetch-mail></code></td><td> </td><td>force retrieval of mail from IMAP server</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><next-undeleted></code></td><td>j</td><td>move to the next undeleted message</td></tr><tr><td><code class="literal"><next-entry></code></td><td>J</td><td>move to the next entry</td></tr><tr><td><code class="literal"><previous-undeleted></code></td><td>k</td><td>move to the previous undeleted message</td></tr><tr><td><code class="literal"><previous-entry></code></td><td>K</td><td>move to the previous entry</td></tr><tr><td><code class="literal"><link-threads></code></td><td>&</td><td>link tagged message to the current one</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><redraw-screen></code></td><td>^L</td><td>clear and redraw the screen</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><mark-as-new></code></td><td>N</td><td>toggle a message's 'new' flag</td></tr><tr><td><code class="literal"><search-next></code></td><td>n</td><td>search for next match</td></tr><tr><td><code class="literal"><next-thread></code></td><td>^N</td><td>jump to the next thread</td></tr><tr><td><code class="literal"><next-subthread></code></td><td>Esc n</td><td>jump to the next subthread</td></tr><tr><td><code class="literal"><print-message></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><previous-thread></code></td><td>^P</td><td>jump to previous thread</td></tr><tr><td><code class="literal"><previous-subthread></code></td><td>Esc p</td><td>jump to previous subthread</td></tr><tr><td><code class="literal"><purge-message></code></td><td> </td><td>really delete the current entry, bypassing the trash folder</td></tr><tr><td><code class="literal"><quit></code></td><td>Q</td><td>save changes to mailbox and quit</td></tr><tr><td><code class="literal"><exit></code></td><td>q</td><td>exit this menu</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><recall-message></code></td><td>R</td><td>recall a postponed message</td></tr><tr><td><code class="literal"><read-thread></code></td><td>^R</td><td>mark the current thread as read</td></tr><tr><td><code class="literal"><read-subthread></code></td><td>Esc r</td><td>mark the current subthread as read</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><save-message></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><skip-quoted></code></td><td>S</td><td>skip beyond quoted text</td></tr><tr><td><code class="literal"><decode-save></code></td><td>Esc s</td><td>make decoded copy (text/plain) and delete</td></tr><tr><td><code class="literal"><tag-message></code></td><td>t</td><td>tag the current entry</td></tr><tr><td><code class="literal"><toggle-quoted></code></td><td>T</td><td>toggle display of quoted text</td></tr><tr><td><code class="literal"><undelete-message></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><undelete-subthread></code></td><td>Esc u</td><td>undelete all messages in subthread</td></tr><tr><td><code class="literal"><undelete-thread></code></td><td>^U</td><td>undelete all messages in thread</td></tr><tr><td><code class="literal"><view-attachments></code></td><td>v</td><td>show MIME attachments</td></tr><tr><td><code class="literal"><show-version></code></td><td>V</td><td>show the Mutt version number and date</td></tr><tr><td><code class="literal"><search-toggle></code></td><td>\\</td><td>toggle search pattern coloring</td></tr><tr><td><code class="literal"><display-address></code></td><td>@</td><td>display full address of sender</td></tr><tr><td><code class="literal"><next-new></code></td><td> </td><td>jump to the next new message</td></tr><tr><td><code class="literal"><pipe-message></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><help></code></td><td>?</td><td>this screen</td></tr><tr><td><code class="literal"><next-page></code></td><td><Space></td><td>move to the next page</td></tr><tr><td><code class="literal"><previous-page></code></td><td>-</td><td>move to the previous page</td></tr><tr><td><code class="literal"><top></code></td><td>^</td><td>jump to the top of the message</td></tr><tr><td><code class="literal"><sync-mailbox></code></td><td>$</td><td>save changes to mailbox</td></tr><tr><td><code class="literal"><shell-escape></code></td><td>!</td><td>invoke a command in a subshell</td></tr><tr><td><code class="literal"><enter-command></code></td><td>:</td><td>enter a muttrc command</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><search></code></td><td>/</td><td>search for a regular expression</td></tr><tr><td><code class="literal"><search-reverse></code></td><td>Esc /</td><td>search backwards for a regular expression</td></tr><tr><td><code class="literal"><search-opposite></code></td><td> </td><td>search for next match in opposite direction</td></tr><tr><td><code class="literal"><next-line></code></td><td><Return></td><td>scroll down one line</td></tr><tr><td><code class="literal"><jump></code></td><td> </td><td>jump to an index number</td></tr><tr><td><code class="literal"><next-unread></code></td><td> </td><td>jump to the next unread message</td></tr><tr><td><code class="literal"><previous-new></code></td><td> </td><td>jump to the previous new message</td></tr><tr><td><code class="literal"><previous-unread></code></td><td> </td><td>jump to the previous unread message</td></tr><tr><td><code class="literal"><half-up></code></td><td> </td><td>scroll up 1/2 page</td></tr><tr><td><code class="literal"><half-down></code></td><td> </td><td>scroll down 1/2 page</td></tr><tr><td><code class="literal"><previous-line></code></td><td> </td><td>scroll up one line</td></tr><tr><td><code class="literal"><bottom></code></td><td> </td><td>jump to the bottom of the message</td></tr><tr><td><code class="literal"><parent-message></code></td><td>P</td><td>jump to parent message in thread</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><mail-key></code></td><td>Esc k</td><td>mail a PGP public key</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><decrypt-copy></code></td><td> </td><td>make decrypted copy</td></tr><tr><td><code class="literal"><decrypt-save></code></td><td> </td><td>make decrypted copy and delete</td></tr><tr><td><code class="literal"><what-key></code></td><td> </td><td>display the keycode for a key press</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="alias_map"></a>4.4. alias menu</h3></div></div></div><div class="table"><a id="alias_table"></a><p class="title"><b>Table 8.5. Default alias function bindings</b></p><div class="table-contents"><table summary="Default alias function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="query_map"></a>4.5. query menu</h3></div></div></div><div class="table"><a id="query_table"></a><p class="title"><b>Table 8.6. Default query function bindings</b></p><div class="table-contents"><table summary="Default query function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><create-alias></code></td><td>a</td><td>create an alias from a message sender</td></tr><tr><td><code class="literal"><mail></code></td><td>m</td><td>compose a new mail message</td></tr><tr><td><code class="literal"><query></code></td><td>Q</td><td>query external program for addresses</td></tr><tr><td><code class="literal"><query-append></code></td><td>A</td><td>append new query results to current results</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="attach_map"></a>4.6. attach menu</h3></div></div></div><div class="table"><a id="attach_table"></a><p class="title"><b>Table 8.7. Default attach function bindings</b></p><div class="table-contents"><table summary="Default attach function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bounce-message></code></td><td>b</td><td>remail a message to another user</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^E</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><print-entry></code></td><td>p</td><td>print the current entry</td></tr><tr><td><code class="literal"><save-entry></code></td><td>s</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><view-mailcap></code></td><td>m</td><td>force viewing of attachment using mailcap</td></tr><tr><td><code class="literal"><reply></code></td><td>r</td><td>reply to a message</td></tr><tr><td><code class="literal"><resend-message></code></td><td>Esc e</td><td>use the current message as a template for a new one</td></tr><tr><td><code class="literal"><group-reply></code></td><td>g</td><td>reply to all recipients</td></tr><tr><td><code class="literal"><list-reply></code></td><td>L</td><td>reply to specified mailing list</td></tr><tr><td><code class="literal"><forward-message></code></td><td>f</td><td>forward a message with comments</td></tr><tr><td><code class="literal"><view-text></code></td><td>T</td><td>view attachment as text</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr><tr><td><code class="literal"><collapse-parts></code></td><td>v</td><td>Toggle display of subparts</td></tr><tr><td><code class="literal"><check-traditional-pgp></code></td><td>Esc P</td><td>check for classic PGP</td></tr><tr><td><code class="literal"><extract-keys></code></td><td>^K</td><td>extract supported public keys</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compose_map"></a>4.7. compose menu</h3></div></div></div><div class="table"><a id="compose_table"></a><p class="title"><b>Table 8.8. Default compose function bindings</b></p><div class="table-contents"><table summary="Default compose function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><attach-file></code></td><td>a</td><td>attach file(s) to this message</td></tr><tr><td><code class="literal"><attach-message></code></td><td>A</td><td>attach message(s) to this message</td></tr><tr><td><code class="literal"><edit-bcc></code></td><td>b</td><td>edit the BCC list</td></tr><tr><td><code class="literal"><edit-cc></code></td><td>c</td><td>edit the CC list</td></tr><tr><td><code class="literal"><copy-file></code></td><td>C</td><td>save message/attachment to a file</td></tr><tr><td><code class="literal"><detach-file></code></td><td>D</td><td>delete the current entry</td></tr><tr><td><code class="literal"><toggle-disposition></code></td><td>^D</td><td>toggle disposition between inline/attachment</td></tr><tr><td><code class="literal"><edit-description></code></td><td>d</td><td>edit attachment description</td></tr><tr><td><code class="literal"><edit-message></code></td><td>e</td><td>edit the message</td></tr><tr><td><code class="literal"><edit-headers></code></td><td>E</td><td>edit the message with headers</td></tr><tr><td><code class="literal"><edit-file></code></td><td>^X e</td><td>edit the file to be attached</td></tr><tr><td><code class="literal"><edit-encoding></code></td><td>^E</td><td>edit attachment transfer-encoding</td></tr><tr><td><code class="literal"><edit-from></code></td><td>Esc f</td><td>edit the from field</td></tr><tr><td><code class="literal"><edit-fcc></code></td><td>f</td><td>enter a file to save a copy of this message in</td></tr><tr><td><code class="literal"><filter-entry></code></td><td>F</td><td>filter attachment through a shell command</td></tr><tr><td><code class="literal"><get-attachment></code></td><td>G</td><td>get a temporary copy of an attachment</td></tr><tr><td><code class="literal"><display-toggle-weed></code></td><td>h</td><td>display message and toggle header weeding</td></tr><tr><td><code class="literal"><ispell></code></td><td>i</td><td>run ispell on the message</td></tr><tr><td><code class="literal"><print-entry></code></td><td>l</td><td>print the current entry</td></tr><tr><td><code class="literal"><edit-mime></code></td><td>m</td><td>edit attachment using mailcap entry</td></tr><tr><td><code class="literal"><new-mime></code></td><td>n</td><td>compose new attachment using mailcap entry</td></tr><tr><td><code class="literal"><postpone-message></code></td><td>P</td><td>save this message to send later</td></tr><tr><td><code class="literal"><edit-reply-to></code></td><td>r</td><td>edit the Reply-To field</td></tr><tr><td><code class="literal"><rename-file></code></td><td>R</td><td>rename/move an attached file</td></tr><tr><td><code class="literal"><edit-subject></code></td><td>s</td><td>edit the subject of this message</td></tr><tr><td><code class="literal"><edit-to></code></td><td>t</td><td>edit the TO list</td></tr><tr><td><code class="literal"><edit-type></code></td><td>^T</td><td>edit attachment content type</td></tr><tr><td><code class="literal"><write-fcc></code></td><td>w</td><td>write the message to a folder</td></tr><tr><td><code class="literal"><toggle-unlink></code></td><td>u</td><td>toggle whether to delete file after sending it</td></tr><tr><td><code class="literal"><toggle-recode></code></td><td> </td><td>toggle recoding of this attachment</td></tr><tr><td><code class="literal"><update-encoding></code></td><td>U</td><td>update an attachment's encoding info</td></tr><tr><td><code class="literal"><view-attach></code></td><td><Return></td><td>view attachment using mailcap entry if necessary</td></tr><tr><td><code class="literal"><send-message></code></td><td>y</td><td>send the message</td></tr><tr><td><code class="literal"><pipe-entry></code></td><td>|</td><td>pipe message/attachment to a shell command</td></tr><tr><td><code class="literal"><attach-key></code></td><td>Esc k</td><td>attach a PGP public key</td></tr><tr><td><code class="literal"><pgp-menu></code></td><td>p</td><td>show PGP options</td></tr><tr><td><code class="literal"><forget-passphrase></code></td><td>^F</td><td>wipe passphrase(s) from memory</td></tr><tr><td><code class="literal"><smime-menu></code></td><td>S</td><td>show S/MIME options</td></tr><tr><td><code class="literal"><mix></code></td><td>M</td><td>send the message through a mixmaster remailer chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="postpone_map"></a>4.8. postpone menu</h3></div></div></div><div class="table"><a id="postpone_table"></a><p class="title"><b>Table 8.9. Default postpone function bindings</b></p><div class="table-contents"><table summary="Default postpone function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><delete-entry></code></td><td>d</td><td>delete the current entry</td></tr><tr><td><code class="literal"><undelete-entry></code></td><td>u</td><td>undelete the current entry</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="browser_map"></a>4.9. browser menu</h3></div></div></div><div class="table"><a id="browser_table"></a><p class="title"><b>Table 8.10. Default browser function bindings</b></p><div class="table-contents"><table summary="Default browser function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><change-dir></code></td><td>c</td><td>change directories</td></tr><tr><td><code class="literal"><display-filename></code></td><td>@</td><td>display the currently selected file's name</td></tr><tr><td><code class="literal"><enter-mask></code></td><td>m</td><td>enter a file mask</td></tr><tr><td><code class="literal"><sort></code></td><td>o</td><td>sort messages</td></tr><tr><td><code class="literal"><sort-reverse></code></td><td>O</td><td>sort messages in reverse order</td></tr><tr><td><code class="literal"><select-new></code></td><td>N</td><td>select a new file in this directory</td></tr><tr><td><code class="literal"><check-new></code></td><td> </td><td>check mailboxes for new mail</td></tr><tr><td><code class="literal"><toggle-mailboxes></code></td><td><Tab></td><td>toggle whether to browse mailboxes or all files</td></tr><tr><td><code class="literal"><view-file></code></td><td><Space></td><td>view file</td></tr><tr><td><code class="literal"><buffy-list></code></td><td>.</td><td>list mailboxes with new mail</td></tr><tr><td><code class="literal"><create-mailbox></code></td><td>C</td><td>create a new mailbox (IMAP only)</td></tr><tr><td><code class="literal"><delete-mailbox></code></td><td>d</td><td>delete the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><rename-mailbox></code></td><td>r</td><td>rename the current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><subscribe></code></td><td>s</td><td>subscribe to current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><unsubscribe></code></td><td>u</td><td>unsubscribe from current mailbox (IMAP only)</td></tr><tr><td><code class="literal"><toggle-subscribed></code></td><td>T</td><td>toggle view all/subscribed mailboxes (IMAP only)</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="pgp_map"></a>4.10. pgp menu</h3></div></div></div><div class="table"><a id="pgp_table"></a><p class="title"><b>Table 8.11. Default pgp function bindings</b></p><div class="table-contents"><table summary="Default pgp function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="smime_map"></a>4.11. smime menu</h3></div></div></div><div class="table"><a id="smime_table"></a><p class="title"><b>Table 8.12. Default smime function bindings</b></p><div class="table-contents"><table summary="Default smime function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><verify-key></code></td><td>c</td><td>verify a PGP public key</td></tr><tr><td><code class="literal"><view-name></code></td><td>%</td><td>view the key's user id</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="mix_map"></a>4.12. mix menu</h3></div></div></div><div class="table"><a id="mix_table"></a><p class="title"><b>Table 8.13. Default mix function bindings</b></p><div class="table-contents"><table summary="Default mix function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><accept></code></td><td><Return></td><td>Accept the chain constructed</td></tr><tr><td><code class="literal"><append></code></td><td>a</td><td>Append a remailer to the chain</td></tr><tr><td><code class="literal"><insert></code></td><td>i</td><td>Insert a remailer into the chain</td></tr><tr><td><code class="literal"><delete></code></td><td>d</td><td>Delete a remailer from the chain</td></tr><tr><td><code class="literal"><chain-prev></code></td><td><Left></td><td>Select the previous element of the chain</td></tr><tr><td><code class="literal"><chain-next></code></td><td><Right></td><td>Select the next element of the chain</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="editor_map"></a>4.13. editor menu</h3></div></div></div><div class="table"><a id="editor_table"></a><p class="title"><b>Table 8.14. Default editor function bindings</b></p><div class="table-contents"><table summary="Default editor function bindings" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Function</th><th>Default key</th><th>Description</th></tr></thead><tbody><tr><td><code class="literal"><bol></code></td><td>^A</td><td>jump to the beginning of the line</td></tr><tr><td><code class="literal"><backward-char></code></td><td>^B</td><td>move the cursor one character to the left</td></tr><tr><td><code class="literal"><backward-word></code></td><td>Esc b</td><td>move the cursor to the beginning of the word</td></tr><tr><td><code class="literal"><capitalize-word></code></td><td>Esc c</td><td>capitalize the word</td></tr><tr><td><code class="literal"><downcase-word></code></td><td>Esc l</td><td>convert the word to lower case</td></tr><tr><td><code class="literal"><upcase-word></code></td><td>Esc u</td><td>convert the word to upper case</td></tr><tr><td><code class="literal"><delete-char></code></td><td>^D</td><td>delete the char under the cursor</td></tr><tr><td><code class="literal"><eol></code></td><td>^E</td><td>jump to the end of the line</td></tr><tr><td><code class="literal"><forward-char></code></td><td>^F</td><td>move the cursor one character to the right</td></tr><tr><td><code class="literal"><forward-word></code></td><td>Esc f</td><td>move the cursor to the end of the word</td></tr><tr><td><code class="literal"><backspace></code></td><td><Backspace></td><td>delete the char in front of the cursor</td></tr><tr><td><code class="literal"><kill-eol></code></td><td>^K</td><td>delete chars from cursor to end of line</td></tr><tr><td><code class="literal"><kill-eow></code></td><td>Esc d</td><td>delete chars from the cursor to the end of the word</td></tr><tr><td><code class="literal"><kill-line></code></td><td>^U</td><td>delete all chars on the line</td></tr><tr><td><code class="literal"><quote-char></code></td><td>^V</td><td>quote the next typed key</td></tr><tr><td><code class="literal"><kill-word></code></td><td>^W</td><td>delete the word in front of the cursor</td></tr><tr><td><code class="literal"><complete></code></td><td><Tab></td><td>complete filename or alias</td></tr><tr><td><code class="literal"><complete-query></code></td><td>^T</td><td>complete address with query</td></tr><tr><td><code class="literal"><buffy-cycle></code></td><td><Space></td><td>cycle among incoming mailboxes</td></tr><tr><td><code class="literal"><history-up></code></td><td> </td><td>scroll up through the history list</td></tr><tr><td><code class="literal"><history-down></code></td><td> </td><td>scroll down through the history list</td></tr><tr><td><code class="literal"><transpose-chars></code></td><td> </td><td>transpose character under cursor with previous</td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="tuning.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="miscellany.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 7. Performance tuning </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 9. Miscellany</td></tr></table></div></body></html>
+++ /dev/null
-.\" -*-nroff-*-
-.\"
-.\"
-.\" Copyright (C) 2009 Antonio Radici <antonio@dyne.org>
-.\"
-.\" This program is free software; you can redistribute it and/or modify
-.\" it under the terms of the GNU General Public License as published by
-.\" the Free Software Foundation; either version 2 of the License, or
-.\" (at your option) any later version.
-.\"
-.\" This program is distributed in the hope that it will be useful,
-.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
-.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-.\" GNU General Public License for more details.
-.\"
-.\" You should have received a copy of the GNU General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-.\"
-.TH smime_keys 1 "May 2009" Unix "User Manuals"
-.SH "NAME"
-smime_keys \- Utility to add S/MIME certificate to the internal database used by mutt
-.SH SYNOPSIS
-.PP
-.B smime_keys
-<operation> [file(s) | keyID [file(s)]]
-.SH "DESCRIPTION"
-The purpose of this tool is to manipulate the internal database of S/MIME certificates
-used by mutt to sign mail messages which will be sent or to verify mail messages received
-and signed with S/MIME
-.SH OPTIONS
-.PP
-.IP \fBinit\fP
-no files needed, inits directory structure.
-.IP \fBlist\fP
-lists the certificates stored in database.
-.IP \fBlabel\fP
-keyID required. changes/removes/adds label.
-.IP \fBremove\fP
-keyID required.
-.IP \fBverify\fP
-1=keyID and optionally 2=CRL
-Verifies the certificate chain, and optionally wether
-this certificate is included in supplied CRL (PEM format).
-Note: to verify all certificates at the same time,
-replace keyID with "all"
-.IP \fBadd_cert\fP
-certificate required.
-.IP \fBadd_chain\fP
-three files reqd: 1=Key, 2=certificate
-plus 3=intermediate certificate(s).
-.IP \fBadd_p12\fP
-one file reqd. Adds keypair to database.
-file is PKCS12 (e.g. export from netscape).
-.IP \fBadd_pem\fP
-one file reqd. Adds keypair to database.
-(file was converted from e.g. PKCS12).
-.IP \fBadd_root\fP
-one file reqd. Adds PEM root certificate to the location
-specified within muttrc (smime_verify_* command)
-.SH NO WARRANTIES
-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.
-.PP
-Mutt Home Page: http://www.mutt.org/
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. Performance tuning</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="The Mutt E-Mail Client" /><link rel="up" href="index.html" title="The Mutt E-Mail Client" /><link rel="prev" href="optionalfeatures.html" title="Chapter 6. Optional features" /><link rel="next" href="reference.html" title="Chapter 8. Reference" /><style xmlns="" type="text/css">
- body { margin-left:2%; margin-right:2%; font-family:serif; }
-.toc, .list-of-tables, .list-of-examples { font-family:sans-serif; }
-h1, h2, h3, h4, h5, h6 { font-family:sans-serif; }
-em.replaceable code { font-family:sans-serif; }
-p { text-align:justify; }
-div.table p.title, div.example p.title { font-size:smaller; font-family:sans-serif; }
-.email, .email a { font-family:monospace; }
-div.table-contents table { border-collapse:collapse; border:1px solid #c0c0c0; }
-div.table-contents table td, div.table-contents table th { padding:5px; text-align:left; }
-div.table-contents table th {
- font-family:sans-serif;
- background:#d0d0d0;
- font-weight:normal;
- vertical-align:top;
-}
-pre.screen, div.note { background:#f0f0f0; border:1px solid #c0c0c0; padding:5px; }
-div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; }
-div.note h3:after { content: ":" }
-div.note { margin-bottom: 5px; }
-
- </style></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 7. Performance tuning</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="optionalfeatures.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="reference.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="tuning"></a>Chapter 7. Performance tuning</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="tuning.html#tuning-mailboxes">1. Reading and writing mailboxes</a></span></dt><dt><span class="sect1"><a href="tuning.html#tuning-messages">2. Reading messages from remote folders</a></span></dt><dt><span class="sect1"><a href="tuning.html#tuning-search">3. Searching and limiting</a></span></dt></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-mailboxes"></a>1. Reading and writing mailboxes</h2></div></div></div><p>
-Mutt's performance when reading mailboxes can be improved in two ways:
-</p><div class="orderedlist"><ol type="1"><li><p>
-For remote folders (IMAP and POP) as well as folders using
-one-file-per message storage (Maildir and MH), mutt's
-performance can be greatly improved using
-<a class="link" href="optionalfeatures.html#header-caching" title="7.1. Header caching">header caching</a>.
-Using a single database per folder may further increase
-performance.
-</p></li><li><p>
-Mutt provides the <a class="link" href="reference.html#read-inc" title="3.235. read_inc">$read_inc</a>
-and <a class="link" href="reference.html#write-inc" title="3.305. write_inc">$write_inc</a>
-variables to specify at which rate to update progress
-counters. If these values are too low, mutt may spend more
-time on updating the progress counter than it spends on
-actually reading/writing folders.
-</p><p>
-For example, when opening a maildir folder with a few
-thousand messages, the default value for
-<a class="link" href="reference.html#read-inc" title="3.235. read_inc">$read_inc</a>
-may be too low. It can be tuned on on a folder-basis using
-<a class="link" href="configuration.html#folder-hook" title="7. Setting variables based upon mailbox">folder-hooks</a>:
-</p><pre class="screen">
-# use very high $read_inc to speed up reading hcache'd maildirs
-folder-hook . 'set read_inc=1000'
-# use lower value for reading slower remote IMAP folders
-folder-hook ^imap 'set read_inc=100'
-# use even lower value for reading even slower remote POP folders
-folder-hook ^pop 'set read_inc=1'</pre></li></ol></div><p>These settings work on a per-message basis. However, as messages may
-greatly differ in size and certain operations are much faster than others,
-even per-folder settings of the increment variables may not be
-desirable as they produce either too few or too much progress updates.
-Thus, Mutt allows to limit the number of progress updates per second it'll
-actually send to the terminal using the
-<a class="link" href="reference.html#time-inc" title="3.286. time_inc">$time_inc</a> variable.</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-messages"></a>2. Reading messages from remote folders</h2></div></div></div><p>
-Reading messages from remote folders such as IMAP an POP can be
-slow especially for large mailboxes since mutt only caches a very
-limited number of recently viewed messages (usually 10) per
-session (so that it will be gone for the next session.)
-</p><p>
-To improve performance and permanently cache whole messages,
-please refer to mutt's so-called
-<a class="link" href="optionalfeatures.html#body-caching" title="7.2. Body caching">body caching</a> for details.
-</p></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tuning-search"></a>3. Searching and limiting</h2></div></div></div><p>
-When searching mailboxes either via a search or a limit action, for
-some patterns mutt distinguishes between regular expression and string
-searches. For regular expressions, patterns are prefixed with
-“<span class="quote">˜</span>” and with “<span class="quote">=</span>” for string searches.
-</p><p>
-Even though a regular expression search is fast, it's several times
-slower than a pure string search which is noticeable especially on large
-folders. As a consequence, a string search should be used instead of a
-regular expression search if the user already knows enough about the
-search pattern.
-</p><p>
-For example, when limiting a large folder to all messages sent to or by
-an author, it's much faster to search for the initial part of an e-mail
-address via <code class="literal">=Luser@</code> instead of
-<code class="literal">˜Luser@</code>. This is especially true for searching
-message bodies since a larger amount of input has to be searched.
-</p><p>
-Please note that string search is an exact case-sensitive search
-while a regular expression search with only lower-case letters performs
-a case-insensitive search.
-</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="optionalfeatures.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="reference.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 6. Optional features </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 8. Reference</td></tr></table></div></body></html>
+++ /dev/null
-#!/bin/sh
-
-#
-# File a bug against the Mutt mail user agent.
-#
-
-#
-# $Id$
-#
-
-#
-# Copyright (c) 2000 Thomas Roessler <roessler@does-not-exist.org>
-#
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-#
-
-SUBMIT="fleas@mutt.org"
-DEBIAN_SUBMIT="submit@bugs.debian.org"
-
-prefix=/usr
-
-DEBUGGER=/usr/bin/gdb
-SENDMAIL=/usr/sbin/sendmail
-sysconfdir=/etc
-pkgdatadir=@pkgdatadir@
-
-include_file ()
-{
- echo
- echo "--- Begin $1"
- sed -e '/^[ ]*#/d; /^[ ]*$/d; s/^-/- -/' $1
- echo "--- End $1"
- echo
-}
-
-debug_gdb ()
-{
- cat << EOF > $SCRATCH/gdb.rc
-bt
-list
-quit
-EOF
- $DEBUGGER -n -x $SCRATCH/gdb.rc -c $CORE mutt
-}
-
-debug_dbx ()
-{
- cat << EOF > $SCRATCH/dbx.rc
-where
-list
-quit
-EOF
- $DEBUGGER -s $SCRATCH/dbx.rc mutt $CORE
-}
-
-debug_sdb ()
-{
- cat << EOF > $SCRATCH/sdb.rc
-t
-w
-q
-EOF
- $DEBUGGER mutt $CORE < $SCRATCH/sdb.rc
-}
-
-case `echo -n` in
-"") n=-n; c= ;;
- *) n=; c='\c' ;;
-esac
-
-
-exec > /dev/tty
-exec < /dev/tty
-
-SCRATCH=${TMPDIR-/tmp}/`basename $0`.`hostname`.$$
-
-mkdir ${SCRATCH} || \
-{
- echo "`basename $0`: Can't create temporary directory." >& 2 ;
- exit 1 ;
-}
-
-trap "rm -r -f ${SCRATCH} ; trap '' 0 ; exit" 0 1 2
-
-TEMPLATE=${SCRATCH}/template.txt
-
-if test -z "$EMAIL" ; then
- EMAIL="`mutt -Q from 2> /dev/null | sed -e 's/^from=.\(.*\).$/\1/'`"
-fi
-
-EMAILTMP=''
-while test -z "$EMAILTMP"
-do
- echo "Please enter your e-mail address [$EMAIL]:"
- echo $n "> $c"
- read EMAILTMP
-
- if test -z "$EMAILTMP"; then EMAILTMP="$EMAIL"; fi
-
- if ! echo "$EMAILTMP" | grep -q @
- then
- echo "$EMAILTMP does not appear to be a valid email address"
- EMAILTMP=''
- continue
- fi
-
- EMAIL="$EMAILTMP"
-done
-
-echo "Please enter a one-line description of the problem you experience:"
-echo $n "> $c"
-read SUBJECT
-
-cat <<EOF
-What should the severity for this bug report be?
-
- 0) Feature request, or maybe a bug which is very difficult to
- fix due to major design considerations.
-
- 1) The package fails to perform correctly in some conditions,
- or on some systems, or fails to comply with current policy
- documents. Most bugs are in this category.
-
- 2) This bug makes this version of the package unsuitable for
- a stable release.
-
- 3) Dangerous bug. Makes the package in question unusable by
- anyone or mostly so, or causes data loss, or introduces a
- security hole allowing access to the accounts of users who
- use the package.
-
- 4) Critical bug. Makes unrelated software on the system (or
- the whole system) break, or causes serious data loss, or
- introduces a security hole on systems where you install the
- package.
-
-EOF
-echo $n "Severity? [01234] $c"
-read severity
-case "$severity" in
-0|[Ww]) severity=wishlist ;;
-2|[Ii]) severity=important ;;
-3|[Gg]) severity=grave ;;
-4|[Cc]) severity=critical ;;
- *) severity=normal ;;
-esac
-
-if test -x $DEBUGGER ; then
- test -f core && CORE=core
- echo "If mutt has crashed, it may have saved some program state in"
- echo "a file named core. We can include this information with the bug"
- echo "report if you wish so."
- echo "Do you want to include information gathered from a core file?"
- echo "If yes, please enter the path - otherwise just say no: [$CORE]"
- echo $n "> $c"
- read _CORE
- test "$_CORE" && CORE="$_CORE"
-fi
-
-echo $n "Do you want to include your personal mutt configuration files? [Y|n] $c"
-read personal
-case "$personal" in
-[nN]*) personal=no ;;
- *) personal=yes ;;
-esac
-
-echo $n "Do you want to include your system's global mutt configuration file? [Y|n] $c"
-read global
-case "$global" in
-[nN]*) global=no ;;
- *) global=yes ;;
-esac
-
-if test -f /etc/debian_version ; then
- DEBIAN=yes
- echo $n "Checking whether mutt has been installed as a package... $c"
- DEBIANVERSION="`dpkg -l mutt | grep '^[ih]' | awk '{print $3}'`" 2> /dev/null
- if test "$DEBIANVERSION" ; then
- DPKG=yes
- else
- DPKG=no
- unset DEBIANVERSION
- fi
- echo "$DPKG"
- echo $n "File this bug with Debian? [Y|n] $c"
- read DPKG
- case "$DPKG" in
- [nN]) DPKG=no ;;
- *) DPKG=yes ;;
- esac
-else
- DEBIAN=no
- DPKG=no
-fi
-
-if rpm -q mutt > /dev/null 2> /dev/null ; then
- echo "Mutt seems to come from an RPM package."
- RPMVERSION="`rpm -q mutt`"
- RPMPACKAGER="`rpm -q -i mutt | sed -n -e 's/^Packager *: *//p'`"
-fi
-
-MUTTVERSION="`mutt -v | awk '{print $2; exit; }'`"
-test "$DPKG" = "yes" && SUBMIT="$SUBMIT, $DEBIAN_SUBMIT"
-
-exec > ${TEMPLATE}
-
-test "$EMAIL" && echo "From: $EMAIL"
-test "$REPLYTO" && echo "Reply-To: $REPLYTO"
-test "$ORGANIZATION" && echo "Organization: $ORGANIZATION"
-
-echo "Subject: mutt-$MUTTVERSION: $SUBJECT"
-echo "To: $SUBMIT"
-test "$EMAIL" && echo "Bcc: ${EMAIL}"
-echo
-echo "Package: mutt"
-echo "Version: ${DEBIANVERSION-${RPMVERSION-$MUTTVERSION}}"
-echo "Severity: $severity"
-echo
-echo "-- Please type your report below this line"
-echo
-echo
-echo
-
-if test "$DEBIAN" = "yes" ; then
- echo "Obtaining Debian-specific information..." > /dev/tty
- bug -p -s dummy mutt < /dev/null 2> /dev/null | \
- sed -n -e "/^-- System Information/,/^---/p" | \
- grep -v '^---'
-else
- echo "-- System Information"
- echo "System Version: `uname -a`"
- test -z "$RPMPACKAGER" || echo "RPM Packager: $RPMPACKAGER";
- test -f /etc/redhat-release && echo "RedHat Release: `cat /etc/redhat-release`"
- test -f /etc/SuSE-release && echo "SuSE Release: `sed 1q /etc/SuSE-release`"
- # Please provide more of these if you have any.
-fi
-
-echo
-echo "-- Build environment information"
-echo
-echo "(Note: This is the build environment installed on the system"
-echo "muttbug is run on. Information may or may not match the environment"
-echo "used to build mutt.)"
-echo
-echo "- gcc version information"
-echo "gcc"
-gcc -v 2>&1
-echo
-echo "- CFLAGS"
-echo -Wall -pedantic -Wno-long-long -Wall -g -O2
-
-
-echo
-echo "-- Mutt Version Information"
-echo
-LC_ALL=C mutt -v
-
-if test "$CORE" && test -f "$CORE" ; then
- echo
- echo "-- Core Dump Analysis Output"
- echo
-
- case "$DEBUGGER" in
- *sdb) debug_sdb $CORE ;;
- *dbx) debug_dbx $CORE ;;
- *gdb) debug_gdb $CORE ;;
- esac
-
- echo
-fi
-
-if test "$personal" = "yes" ; then
- CANDIDATES=".muttrc-${MUTTVERSION} .muttrc .mutt/muttrc-${MUTTVERSION} .mutt/muttrc"
- MATCHED="none"
- for f in $CANDIDATES; do
- if test -f "${HOME}/$f" ; then
- MATCHED="${HOME}/$f"
- break
- fi
- done
-
- if test "$MATCHED" = "none" ; then
- echo "Warning: Can't find your personal .muttrc." >&2
- else
- include_file $MATCHED
- fi
-fi
-
-
-if test "$global" = "yes" ; then
- CANDIDATES="Muttrc-${MUTTVERSION} Muttrc"
- DIRECTORIES="$sysconfdir $pkgdatadir"
- MATCHED="none"
- for d in $DIRECTORIES ; do
- for f in $CANDIDATES; do
- if test -f $d/$f ; then
- MATCHED="$d/$f"
- break
- fi
- done
- test "$MATCHED" = "none" || break
- done
-
- if test "$MATCHED" = "none" ; then
- echo "Warning: Can't find global Muttrc." >&2
- else
- include_file $MATCHED
- fi
-fi
-
-exec > /dev/tty
-
-cp $TEMPLATE $SCRATCH/mutt-bug.txt
-
-input="e"
-while : ; do
- if test "$input" = "e" ; then
- ${VISUAL-${EDITOR-vi}} $SCRATCH/mutt-bug.txt
- if cmp $SCRATCH/mutt-bug.txt ${TEMPLATE} > /dev/null ; then
- echo "Warning: Bug report was not modified!"
- fi
- fi
-
- echo $n "Submit, Edit, View, Quit? [S|e|v|q] $c"
- read _input
- input="`echo $_input | tr EVSQ evsq`"
- case $input in
- e*) ;;
- v*) ${PAGER-more} $SCRATCH/mutt-bug.txt ;;
- s*|"") $SENDMAIL -t < $SCRATCH/mutt-bug.txt ; exit ;;
- q*) exit
- esac
-done
-
+++ /dev/null
-#!/bin/sh
-
-BASEVERSION=2
-
-cleanstruct () {
- echo "$1" | sed -e 's/} *//' -e 's/;$//'
-}
-
-cleanbody () {
- echo "$1" | sed -e 's/{ *//'
-}
-
-getstruct () {
- STRUCT=""
- BODY=''
- inbody=0
- case "$1" in
- *'{') inbody=1 ;;
- *';') return ;;
- esac
-
- while read line
- do
- if test $inbody -eq 0
- then
- case "$line" in
- '{'*) inbody=1 ;;
- *';') return ;;
- esac
- fi
-
- case "$line" in
- '} '*)
- STRUCT=`cleanstruct "$line"`
- break
- ;;
- '}')
- read line
- STRUCT=`cleanstruct "$line"`
- break
- ;;
- '#'*) continue ;;
- *)
- if test $inbody -ne 0
- then
- BODY="$BODY $line"
- fi
- ;;
- esac
- done
-
- case $STRUCT in
- ADDRESS|LIST|BUFFER|PARAMETER|BODY|ENVELOPE|HEADER)
- BODY=`cleanbody "$BODY"`
- echo "$STRUCT: $BODY"
- ;;
- esac
- return
-}
-
-DEST="$1"
-TMPD="$DEST.tmp"
-
-TEXT="$BASEVERSION"
-
-echo "/* base version: $BASEVERSION" > $TMPD
-while read line
-do
- case "$line" in
- 'typedef struct'*)
- STRUCT=`getstruct "$line"`
- if test -n "$STRUCT"
- then
- NAME=`echo $STRUCT | cut -d: -f1`
- BODY=`echo $STRUCT | cut -d' ' -f2-`
- echo " * $NAME:" $BODY >> $TMPD
- TEXT="$TEXT $NAME {$BODY}"
- fi
- ;;
- esac
-done
-echo " */" >> $TMPD
-
-MD5TEXT=`echo "$TEXT" | ./mutt_md5`
-echo "#define HCACHEVER 0x"`echo $MD5TEXT | cut -c-8` >> $TMPD
-
-# TODO: validate we have all structs
-
-mv $TMPD $DEST
+++ /dev/null
-/* base version: 2
- * ADDRESS: char *personal; char *mailbox; int group; struct address_t *next; unsigned is_idn : 1; unsigned idn_checked : 1;
- * BUFFER: char *data; char *dptr; size_t dsize; int destroy;
- * LIST: char *data; struct list_t *next;
- * ENVELOPE: ADDRESS *return_path; ADDRESS *from; ADDRESS *to; ADDRESS *cc; ADDRESS *bcc; ADDRESS *sender; ADDRESS *reply_to; ADDRESS *mail_followup_to; char *list_post; char *subject; char *real_subj; char *message_id; char *supersedes; char *date; char *x_label; BUFFER *spam; LIST *references; LIST *in_reply_to; LIST *userhdrs; unsigned int irt_changed : 1; unsigned int refs_changed : 1;
- * PARAMETER: char *attribute; char *value; struct parameter *next;
- * BODY: char *xtype; char *subtype; PARAMETER *parameter; char *description; char *form_name; long hdr_offset; off_t offset; off_t length; char *filename; char *d_filename; char *charset; CONTENT *content; struct body *next; struct body *parts; struct header *hdr; struct attachptr *aptr; signed short attach_count; time_t stamp; unsigned int type : 4; unsigned int encoding : 3; unsigned int disposition : 2; unsigned int use_disp : 1; unsigned int unlink : 1; unsigned int tagged : 1; unsigned int deleted : 1; unsigned int noconv : 1; unsigned int force_charset : 1; unsigned int is_signed_data : 1; unsigned int goodsig : 1; unsigned int warnsig : 1; unsigned int badsig : 1; unsigned int collapsed : 1; unsigned int attach_qualifies : 1;
- * HEADER: unsigned int security : 11; unsigned int mime : 1; unsigned int flagged : 1; unsigned int tagged : 1; unsigned int appended : 1; unsigned int purged : 1; unsigned int deleted : 1; unsigned int changed : 1; unsigned int attach_del : 1; unsigned int old : 1; unsigned int read : 1; unsigned int expired : 1; unsigned int superseded : 1; unsigned int replied : 1; unsigned int subject_changed : 1; unsigned int threaded : 1; unsigned int display_subject : 1; unsigned int recip_valid : 1; unsigned int active : 1; unsigned int trash : 1; unsigned int zhours : 5; unsigned int zminutes : 6; unsigned int zoccident : 1; unsigned int searched : 1; unsigned int matched : 1; unsigned int attach_valid : 1; unsigned int collapsed : 1; unsigned int limited : 1; size_t num_hidden; short recipient; int pair; time_t date_sent; time_t received; off_t offset; int lines; int index; int msgno; int virtual; int score; ENVELOPE *env; BODY *content; char *path; char *tree; struct thread *thread; short attach_total; LIST *chain; int refno; void *data; char *maildir_flags;
- */
-#define HCACHEVER 0xafe521b0
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# imap/Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-
-
-VPATH = ../../imap
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-subdir = imap
-DIST_COMMON = README $(noinst_HEADERS) $(srcdir)/Makefile.am \
- $(srcdir)/Makefile.in TODO
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES =
-LIBRARIES = $(noinst_LIBRARIES)
-ARFLAGS = cru
-libimap_a_AR = $(AR) $(ARFLAGS)
-libimap_a_LIBADD =
-am__libimap_a_SOURCES_DIST = auth.c auth_login.c browse.c command.c \
- imap.c imap.h message.c utf7.c util.c auth_anon.c auth_cram.c \
- auth_sasl.c auth_gss.c
-#am__objects_1 = auth_anon.$(OBJEXT) \
-# auth_cram.$(OBJEXT)
-am__objects_1 = auth_sasl.$(OBJEXT)
-am__objects_2 = auth_gss.$(OBJEXT)
-am_libimap_a_OBJECTS = auth.$(OBJEXT) auth_login.$(OBJEXT) \
- browse.$(OBJEXT) command.$(OBJEXT) imap.$(OBJEXT) \
- message.$(OBJEXT) utf7.$(OBJEXT) util.$(OBJEXT) \
- $(am__objects_1) $(am__objects_2)
-libimap_a_OBJECTS = $(am_libimap_a_OBJECTS)
-DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)
-depcomp = $(SHELL) $(top_srcdir)/depcomp
-am__depfiles_maybe = depfiles
-COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
- $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
-CCLD = $(CC)
-LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
-SOURCES = $(libimap_a_SOURCES)
-DIST_SOURCES = $(am__libimap_a_SOURCES_DIST)
-HEADERS = $(noinst_HEADERS)
-ETAGS = etags
-CTAGS = ctags
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DHAVE_CONFIG_H
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/imap
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/../imap
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ../../imap
-sysconfdir = /etc
-target_alias =
-top_build_prefix = ../
-top_builddir = ..
-top_srcdir = ../..
-AUTOMAKE_OPTIONS = 1.6 foreign
-GSSSOURCES = auth_gss.c
-#AUTHENTICATORS = auth_anon.c auth_cram.c
-AUTHENTICATORS = auth_sasl.c
-EXTRA_DIST = README TODO auth_anon.c auth_cram.c auth_gss.c auth_sasl.c
-AM_CPPFLAGS = -I$(top_srcdir) -I../intl
-noinst_LIBRARIES = libimap.a
-noinst_HEADERS = auth.h imap_private.h message.h
-libimap_a_SOURCES = auth.c auth_login.c browse.c command.c imap.c imap.h \
- message.c utf7.c util.c $(AUTHENTICATORS) $(GSSSOURCES)
-
-all: all-am
-
-.SUFFIXES:
-.SUFFIXES: .c .o .obj
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign imap/Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --foreign imap/Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-clean-noinstLIBRARIES:
- -test -z "$(noinst_LIBRARIES)" || rm -f $(noinst_LIBRARIES)
-libimap.a: $(libimap_a_OBJECTS) $(libimap_a_DEPENDENCIES)
- -rm -f libimap.a
- $(libimap_a_AR) libimap.a $(libimap_a_OBJECTS) $(libimap_a_LIBADD)
- $(RANLIB) libimap.a
-
-mostlyclean-compile:
- -rm -f *.$(OBJEXT)
-
-distclean-compile:
- -rm -f *.tab.c
-
-#include ./$(DEPDIR)/auth.Po
-#include ./$(DEPDIR)/auth_anon.Po
-#include ./$(DEPDIR)/auth_cram.Po
-#include ./$(DEPDIR)/auth_gss.Po
-#include ./$(DEPDIR)/auth_login.Po
-#include ./$(DEPDIR)/auth_sasl.Po
-#include ./$(DEPDIR)/browse.Po
-#include ./$(DEPDIR)/command.Po
-#include ./$(DEPDIR)/imap.Po
-#include ./$(DEPDIR)/message.Po
-#include ./$(DEPDIR)/utf7.Po
-#include ./$(DEPDIR)/util.Po
-
-.c.o:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c $<
-
-.c.obj:
-# $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ `$(CYGPATH_W) '$<'`
-# mv -f $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
-# source='$<' object='$@' libtool=no
-# DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
- $(COMPILE) -c `$(CYGPATH_W) '$<'`
-
-ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- mkid -fID $$unique
-tags: TAGS
-
-TAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- here=`pwd`; \
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
- test -n "$$unique" || unique=$$empty_fix; \
- $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
- $$tags $$unique; \
- fi
-ctags: CTAGS
-CTAGS: $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
- $(TAGS_FILES) $(LISP)
- tags=; \
- list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
- if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
- done | \
- $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
- END { if (nonempty) { for (i in files) print i; }; }'`; \
- test -z "$(CTAGS_ARGS)$$tags$$unique" \
- || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
- $$tags $$unique
-
-GTAGS:
- here=`$(am__cd) $(top_builddir) && pwd` \
- && cd $(top_srcdir) \
- && gtags -i $(GTAGS_ARGS) $$here
-
-distclean-tags:
- -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
-distdir: $(DISTFILES)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
-check-am: all-am
-check: check-am
-all-am: Makefile $(LIBRARIES) $(HEADERS)
-installdirs:
-install: install-am
-install-exec: install-exec-am
-install-data: install-data-am
-uninstall: uninstall-am
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-am
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
-clean: clean-am
-
-clean-am: clean-generic clean-noinstLIBRARIES mostlyclean-am
-
-distclean: distclean-am
- -rm -rf ./$(DEPDIR)
- -rm -f Makefile
-distclean-am: clean-am distclean-compile distclean-generic \
- distclean-tags
-
-dvi: dvi-am
-
-dvi-am:
-
-html: html-am
-
-info: info-am
-
-info-am:
-
-install-data-am:
-
-install-dvi: install-dvi-am
-
-install-exec-am:
-
-install-html: install-html-am
-
-install-info: install-info-am
-
-install-man:
-
-install-pdf: install-pdf-am
-
-install-ps: install-ps-am
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-am
- -rm -rf ./$(DEPDIR)
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-am
-
-mostlyclean-am: mostlyclean-compile mostlyclean-generic
-
-pdf: pdf-am
-
-pdf-am:
-
-ps: ps-am
-
-ps-am:
-
-uninstall-am:
-
-.MAKE: install-am install-strip
-
-.PHONY: CTAGS GTAGS all all-am check check-am clean clean-generic \
- clean-noinstLIBRARIES ctags distclean distclean-compile \
- distclean-generic distclean-tags distdir dvi dvi-am html \
- html-am info info-am install install-am install-data \
- install-data-am install-dvi install-dvi-am install-exec \
- install-exec-am install-html install-html-am install-info \
- install-info-am install-man install-pdf install-pdf-am \
- install-ps install-ps-am install-strip installcheck \
- installcheck-am installdirs maintainer-clean \
- maintainer-clean-generic mostlyclean mostlyclean-compile \
- mostlyclean-generic pdf pdf-am ps ps-am tags uninstall \
- uninstall-am
-
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-# Makefile for directory with message catalog handling in GNU NLS Utilities.
-# Copyright (C) 1995-1998, 2000, 2001 Free Software Foundation, Inc.
-#
-# This program is free software; you can redistribute it and/or modify it
-# under the terms of the GNU Library General Public License as published
-# by the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-# Library General Public License for more details.
-#
-# You should have received a copy of the GNU Library 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.
-
-PACKAGE = mutt
-VERSION = 1.5.19
-
-SHELL = /bin/sh
-
-srcdir = ../../intl
-top_srcdir = ../..
-top_builddir = ..
-VPATH = ../../intl
-
-prefix = /usr
-exec_prefix = ${prefix}
-transform = s,x,x,
-libdir = ${exec_prefix}/lib
-includedir = ${prefix}/include
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-localedir = $(datadir)/locale
-gettextsrcdir = $(datadir)/gettext/intl
-aliaspath = $(localedir)
-subdir = intl
-
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-MKINSTALLDIRS = ../mkinstalldirs
-mkinstalldirs = $(SHELL) `case "$(MKINSTALLDIRS)" in /*) echo "$(MKINSTALLDIRS)" ;; *) echo "$(top_builddir)/$(MKINSTALLDIRS)" ;; esac`
-
-l =
-
-AR = ar
-CC = gcc
-LIBTOOL = @LIBTOOL@
-RANLIB = ranlib
-YACC = bison -y -d
-YFLAGS = --name-prefix=__gettext
-
-DEFS = -DLOCALEDIR=\"$(localedir)\" -DLOCALE_ALIAS_PATH=\"$(aliaspath)\" \
--DLIBDIR=\"$(libdir)\" -DHAVE_CONFIG_H
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-LDFLAGS = -L/lib
-
-COMPILE = $(CC) -c $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $(XCFLAGS)
-
-HEADERS = $(COMHDRS) libgnuintl.h libgettext.h loadinfo.h
-COMHDRS = gettext.h gettextP.h hash-string.h
-SOURCES = $(COMSRCS) intl-compat.c
-COMSRCS = bindtextdom.c dcgettext.c dgettext.c gettext.c \
-finddomain.c loadmsgcat.c localealias.c textdomain.c l10nflist.c \
-explodename.c dcigettext.c dcngettext.c dngettext.c ngettext.c plural.y \
-localcharset.c
-OBJECTS = bindtextdom.$lo dcgettext.$lo dgettext.$lo gettext.$lo \
-finddomain.$lo loadmsgcat.$lo localealias.$lo textdomain.$lo l10nflist.$lo \
-explodename.$lo dcigettext.$lo dcngettext.$lo dngettext.$lo ngettext.$lo \
-plural.$lo localcharset.$lo
-GETTOBJS = intl-compat.$lo
-DISTFILES.common = Makefile.in \
-config.charset locale.alias ref-add.sin ref-del.sin $(HEADERS) $(SOURCES)
-DISTFILES.generated = plural.c
-DISTFILES.normal = VERSION
-DISTFILES.gettext = COPYING.LIB-2 COPYING.LIB-2.1 libintl.glibc
-DISTFILES.obsolete = xopen-msg.sed linux-msg.sed po2tbl.sed.in cat-compat.c
-
-# Libtool's library version information for libintl.
-# Before making a gettext release, the gettext maintainer must change this
-# according to the libtool documentation, section "Library interface versions".
-# Maintainers of other packages that include the intl directory must *not*
-# change these values.
-LTV_CURRENT=1
-LTV_REVISION=1
-LTV_AGE=0
-
-.SUFFIXES:
-.SUFFIXES: .c .y .o .lo .sin .sed
-.c.o:
- $(COMPILE) $<
-.c.lo:
- $(LIBTOOL) --mode=compile $(COMPILE) $<
-
-.y.c:
- $(YACC) $(YFLAGS) --output $@ $<
- rm -f $*.h
-
-.sin.sed:
- sed -e '/^#/d' -e 's/@''PACKAGE''@/mutt/g' $< > t-$@
- mv t-$@ $@
-
-INCLUDES = -I.. -I. -I$(top_srcdir)/intl
-
-all: all-no
-all-yes: libintl.$la libintl.h charset.alias ref-add.sed ref-del.sed
-all-no: all-no-no
-all-no-yes: libgnuintl.$la
-all-no-no:
-
-libintl.a libgnuintl.a: $(OBJECTS)
- rm -f $@
- $(AR) cru $@ $(OBJECTS)
- $(RANLIB) $@
-
-libintl.la libgnuintl.la: $(OBJECTS)
- $(LIBTOOL) --mode=link \
- $(CC) $(CPPFLAGS) $(CFLAGS) $(XCFLAGS) $(LDFLAGS) -o $@ \
- $(OBJECTS) \
- -version-info $(LTV_CURRENT):$(LTV_REVISION):$(LTV_AGE) \
- -rpath $(libdir) \
- -no-undefined
-
-libintl.h: libgnuintl.h
- cp $(srcdir)/libgnuintl.h libintl.h
-
-charset.alias: config.charset
- $(SHELL) $(srcdir)/config.charset 'i486-pc-linux-gnu' > t-$@
- mv t-$@ $@
-
-check: all
-
-# This installation goal is only used in GNU gettext. Packages which
-# only use the library should use install instead.
-
-# We must not install the libintl.h/libintl.a files if we are on a
-# system which has the GNU gettext() function in its C library or in a
-# separate library.
-# If you want to use the one which comes with this version of the
-# package, you have to use `configure --with-included-gettext'.
-install: install-exec install-data
-install-exec: all
- if test "$(PACKAGE)" = "gettext" \
- && test '' = '$(GETTOBJS)'; then \
- $(mkinstalldirs) $(DESTDIR)$(libdir) $(DESTDIR)$(includedir); \
- $(INSTALL_DATA) libintl.h $(DESTDIR)$(includedir)/libintl.h; \
- $(LIBTOOL) --mode=install \
- $(INSTALL_DATA) libintl.$la $(DESTDIR)$(libdir)/libintl.$la; \
- else \
- : ; \
- fi
- if test 'no' = yes; then \
- $(mkinstalldirs) $(DESTDIR)$(libdir); \
- temp=$(DESTDIR)$(libdir)/t-charset.alias; \
- dest=$(DESTDIR)$(libdir)/charset.alias; \
- if test -f $(DESTDIR)$(libdir)/charset.alias; then \
- orig=$(DESTDIR)$(libdir)/charset.alias; \
- sed -f ref-add.sed $$orig > $$temp; \
- $(INSTALL_DATA) $$temp $$dest; \
- rm -f $$temp; \
- else \
- if test yes = no; then \
- orig=charset.alias; \
- sed -f ref-add.sed $$orig > $$temp; \
- $(INSTALL_DATA) $$temp $$dest; \
- rm -f $$temp; \
- fi; \
- fi; \
- $(mkinstalldirs) $(DESTDIR)$(localedir); \
- test -f $(DESTDIR)$(localedir)/locale.alias \
- && orig=$(DESTDIR)$(localedir)/locale.alias \
- || orig=$(srcdir)/locale.alias; \
- temp=$(DESTDIR)$(localedir)/t-locale.alias; \
- dest=$(DESTDIR)$(localedir)/locale.alias; \
- sed -f ref-add.sed $$orig > $$temp; \
- $(INSTALL_DATA) $$temp $$dest; \
- rm -f $$temp; \
- else \
- : ; \
- fi
-install-data: all
- if test "$(PACKAGE)" = "gettext"; then \
- $(mkinstalldirs) $(DESTDIR)$(gettextsrcdir); \
- $(INSTALL_DATA) VERSION $(DESTDIR)$(gettextsrcdir)/VERSION; \
- $(INSTALL_DATA) ChangeLog.inst $(DESTDIR)$(gettextsrcdir)/ChangeLog; \
- dists="COPYING.LIB-2 COPYING.LIB-2.1 $(DISTFILES.common)"; \
- for file in $$dists; do \
- $(INSTALL_DATA) $(srcdir)/$$file \
- $(DESTDIR)$(gettextsrcdir)/$$file; \
- done; \
- chmod a+x $(DESTDIR)$(gettextsrcdir)/config.charset; \
- dists="$(DISTFILES.generated)"; \
- for file in $$dists; do \
- if test -f $$file; then dir=.; else dir=$(srcdir); fi; \
- $(INSTALL_DATA) $$dir/$$file \
- $(DESTDIR)$(gettextsrcdir)/$$file; \
- done; \
- dists="$(DISTFILES.obsolete)"; \
- for file in $$dists; do \
- rm -f $(DESTDIR)$(gettextsrcdir)/$$file; \
- done; \
- else \
- : ; \
- fi
-
-# Define this as empty until I found a useful application.
-installcheck:
-
-uninstall:
- if test "$(PACKAGE)" = "gettext" \
- && test '' = '$(GETTOBJS)'; then \
- rm -f $(DESTDIR)$(includedir)/libintl.h; \
- $(LIBTOOL) --mode=uninstall \
- rm -f $(DESTDIR)$(libdir)/libintl.$la; \
- else \
- : ; \
- fi
- if test 'no' = yes; then \
- if test -f $(DESTDIR)$(libdir)/charset.alias; then \
- temp=$(DESTDIR)$(libdir)/t-charset.alias; \
- dest=$(DESTDIR)$(libdir)/charset.alias; \
- sed -f ref-del.sed $$dest > $$temp; \
- if grep '^# Packages using this file: $$' $$temp > /dev/null; then \
- rm -f $$dest; \
- else \
- $(INSTALL_DATA) $$temp $$dest; \
- fi; \
- rm -f $$temp; \
- fi; \
- if test -f $(DESTDIR)$(localedir)/locale.alias; then \
- temp=$(DESTDIR)$(localedir)/t-locale.alias; \
- dest=$(DESTDIR)$(localedir)/locale.alias; \
- sed -f ref-del.sed $$dest > $$temp; \
- if grep '^# Packages using this file: $$' $$temp > /dev/null; then \
- rm -f $$dest; \
- else \
- $(INSTALL_DATA) $$temp $$dest; \
- fi; \
- rm -f $$temp; \
- fi; \
- else \
- : ; \
- fi
- if test "$(PACKAGE)" = "gettext"; then \
- for file in VERSION ChangeLog COPYING.LIB-2 COPYING.LIB-2.1 $(DISTFILES.common) $(DISTFILES.generated); do \
- rm -f $(DESTDIR)$(gettextsrcdir)/$$file; \
- done; \
- else \
- : ; \
- fi
-
-info dvi:
-
-$(OBJECTS): ../config.h libgnuintl.h
-bindtextdom.$lo finddomain.$lo loadmsgcat.$lo: gettextP.h gettext.h loadinfo.h
-dcgettext.$lo: gettextP.h gettext.h hash-string.h loadinfo.h
-
-tags: TAGS
-
-TAGS: $(HEADERS) $(SOURCES)
- here=`pwd`; cd $(srcdir) && etags -o $$here/TAGS $(HEADERS) $(SOURCES)
-
-id: ID
-
-ID: $(HEADERS) $(SOURCES)
- here=`pwd`; cd $(srcdir) && mkid -f$$here/ID $(HEADERS) $(SOURCES)
-
-
-mostlyclean:
- rm -f *.a *.la *.o *.lo core core.*
- rm -f libintl.h charset.alias ref-add.sed ref-del.sed
- rm -f -r .libs _libs
-
-clean: mostlyclean
-
-distclean: clean
- rm -f Makefile ID TAGS
- if test "$(PACKAGE)" = gettext; then \
- rm -f ChangeLog.inst $(DISTFILES.normal); \
- else \
- : ; \
- fi
-
-maintainer-clean: distclean
- @echo "This command is intended for maintainers to use;"
- @echo "it deletes files that may require special tools to rebuild."
-
-
-# GNU gettext needs not contain the file `VERSION' but contains some
-# other files which should not be distributed in other packages.
-distdir = ../$(PACKAGE)-$(VERSION)/$(subdir)
-dist distdir: Makefile
- if test "$(PACKAGE)" = gettext; then \
- additional="$(DISTFILES.gettext)"; \
- else \
- additional="$(DISTFILES.normal)"; \
- fi; \
- $(MAKE) $(DISTFILES.common) $(DISTFILES.generated) $$additional; \
- for file in ChangeLog $(DISTFILES.common) $(DISTFILES.generated) $$additional; do \
- if test -f $$file; then dir=.; else dir=$(srcdir); fi; \
- ln $$dir/$$file $(distdir) 2> /dev/null \
- || cp -p $$dir/$$file $(distdir); \
- done
-
-Makefile: Makefile.in ../config.status
- cd .. \
- && CONFIG_FILES=$(subdir)/$@ CONFIG_HEADERS= $(SHELL) ./config.status
-
-# Tell versions [3.59,3.63) of GNU make not to export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-/* Automatically generated by gen_defs. Do not edit! */
-
-#ifdef HELP_C
-const char *HelpStrings[] = {
- N_("null operation"),
- N_("end of conditional execution (noop)"),
- N_("force viewing of attachment using mailcap"),
- N_("view attachment as text"),
- N_("Toggle display of subparts"),
- N_("move to the bottom of the page"),
- N_("remail a message to another user"),
- N_("select a new file in this directory"),
- N_("view file"),
- N_("display the currently selected file's name"),
- N_("subscribe to current mailbox (IMAP only)"),
- N_("unsubscribe from current mailbox (IMAP only)"),
- N_("toggle view all/subscribed mailboxes (IMAP only)"),
- N_("list mailboxes with new mail"),
- N_("change directories"),
- N_("check mailboxes for new mail"),
- N_("attach file(s) to this message"),
- N_("attach message(s) to this message"),
- N_("edit the BCC list"),
- N_("edit the CC list"),
- N_("edit attachment description"),
- N_("edit attachment transfer-encoding"),
- N_("enter a file to save a copy of this message in"),
- N_("edit the file to be attached"),
- N_("edit the from field"),
- N_("edit the message with headers"),
- N_("edit the message"),
- N_("edit attachment using mailcap entry"),
- N_("edit the Reply-To field"),
- N_("edit the subject of this message"),
- N_("edit the TO list"),
- N_("create a new mailbox (IMAP only)"),
- N_("edit attachment content type"),
- N_("get a temporary copy of an attachment"),
- N_("run ispell on the message"),
- N_("compose new attachment using mailcap entry"),
- N_("toggle recoding of this attachment"),
- N_("save this message to send later"),
- N_("rename/move an attached file"),
- N_("send the message"),
- N_("toggle disposition between inline/attachment"),
- N_("toggle whether to delete file after sending it"),
- N_("update an attachment's encoding info"),
- N_("write the message to a folder"),
- N_("copy a message to a file/mailbox"),
- N_("create an alias from a message sender"),
- N_("move entry to bottom of screen"),
- N_("move entry to middle of screen"),
- N_("move entry to top of screen"),
- N_("make decoded (text/plain) copy"),
- N_("make decoded copy (text/plain) and delete"),
- N_("delete the current entry"),
- N_("delete the current mailbox (IMAP only)"),
- N_("delete all messages in subthread"),
- N_("delete all messages in thread"),
- N_("display full address of sender"),
- N_("display message and toggle header weeding"),
- N_("display a message"),
- N_("edit the raw message"),
- N_("delete the char in front of the cursor"),
- N_("move the cursor one character to the left"),
- N_("move the cursor to the beginning of the word"),
- N_("jump to the beginning of the line"),
- N_("cycle among incoming mailboxes"),
- N_("complete filename or alias"),
- N_("complete address with query"),
- N_("delete the char under the cursor"),
- N_("jump to the end of the line"),
- N_("move the cursor one character to the right"),
- N_("move the cursor to the end of the word"),
- N_("scroll down through the history list"),
- N_("scroll up through the history list"),
- N_("delete chars from cursor to end of line"),
- N_("delete chars from the cursor to the end of the word"),
- N_("delete all chars on the line"),
- N_("delete the word in front of the cursor"),
- N_("quote the next typed key"),
- N_("transpose character under cursor with previous"),
- N_("capitalize the word"),
- N_("convert the word to lower case"),
- N_("convert the word to upper case"),
- N_("enter a muttrc command"),
- N_("enter a file mask"),
- N_("exit this menu"),
- N_("filter attachment through a shell command"),
- N_("move to the first entry"),
- N_("toggle a message's 'important' flag"),
- N_("forward a message with comments"),
- N_("select the current entry"),
- N_("reply to all recipients"),
- N_("scroll down 1/2 page"),
- N_("scroll up 1/2 page"),
- N_("this screen"),
- N_("jump to an index number"),
- N_("move to the last entry"),
- N_("reply to specified mailing list"),
- N_("execute a macro"),
- N_("compose a new mail message"),
- N_("break the thread in two"),
- N_("open a different folder"),
- N_("open a different folder in read only mode"),
- N_("clear a status flag from a message"),
- N_("delete messages matching a pattern"),
- N_("force retrieval of mail from IMAP server"),
- N_("retrieve mail from POP server"),
- N_("move to the first message"),
- N_("move to the last message"),
- N_("show only messages matching a pattern"),
- N_("link tagged message to the current one"),
- N_("open next mailbox with new mail"),
- N_("jump to the next new message"),
- N_("jump to the next new or unread message"),
- N_("jump to the next subthread"),
- N_("jump to the next thread"),
- N_("move to the next undeleted message"),
- N_("jump to the next unread message"),
- N_("jump to parent message in thread"),
- N_("jump to previous thread"),
- N_("jump to previous subthread"),
- N_("move to the previous undeleted message"),
- N_("jump to the previous new message"),
- N_("jump to the previous new or unread message"),
- N_("jump to the previous unread message"),
- N_("mark the current thread as read"),
- N_("mark the current subthread as read"),
- N_("set a status flag on a message"),
- N_("save changes to mailbox"),
- N_("tag messages matching a pattern"),
- N_("undelete messages matching a pattern"),
- N_("untag messages matching a pattern"),
- N_("move to the middle of the page"),
- N_("move to the next entry"),
- N_("scroll down one line"),
- N_("move to the next page"),
- N_("jump to the bottom of the message"),
- N_("toggle display of quoted text"),
- N_("skip beyond quoted text"),
- N_("jump to the top of the message"),
- N_("pipe message/attachment to a shell command"),
- N_("move to the previous entry"),
- N_("scroll up one line"),
- N_("move to the previous page"),
- N_("print the current entry"),
- N_("really delete the current entry, bypassing the trash folder"),
- N_("query external program for addresses"),
- N_("append new query results to current results"),
- N_("save changes to mailbox and quit"),
- N_("recall a postponed message"),
- N_("clear and redraw the screen"),
- N_("{internal}"),
- N_("rename the current mailbox (IMAP only)"),
- N_("reply to a message"),
- N_("use the current message as a template for a new one"),
- N_("save message/attachment to a file"),
- N_("search for a regular expression"),
- N_("search backwards for a regular expression"),
- N_("search for next match"),
- N_("search for next match in opposite direction"),
- N_("toggle search pattern coloring"),
- N_("invoke a command in a subshell"),
- N_("sort messages"),
- N_("sort messages in reverse order"),
- N_("tag the current entry"),
- N_("apply next function to tagged messages"),
- N_("apply next function ONLY to tagged messages"),
- N_("tag the current subthread"),
- N_("tag the current thread"),
- N_("toggle a message's 'new' flag"),
- N_("toggle whether the mailbox will be rewritten"),
- N_("toggle whether to browse mailboxes or all files"),
- N_("move to the top of the page"),
- N_("undelete the current entry"),
- N_("undelete all messages in thread"),
- N_("undelete all messages in subthread"),
- N_("show the Mutt version number and date"),
- N_("view attachment using mailcap entry if necessary"),
- N_("show MIME attachments"),
- N_("display the keycode for a key press"),
- N_("show currently active limit pattern"),
- N_("collapse/uncollapse current thread"),
- N_("collapse/uncollapse all threads"),
- N_("Accept the chain constructed"),
- N_("Append a remailer to the chain"),
- N_("Insert a remailer into the chain"),
- N_("Delete a remailer from the chain"),
- N_("Select the previous element of the chain"),
- N_("Select the next element of the chain"),
- N_("send the message through a mixmaster remailer chain"),
- N_("attach a PGP public key"),
- N_("show PGP options"),
- N_("mail a PGP public key"),
- N_("verify a PGP public key"),
- N_("view the key's user id"),
- N_("check for classic PGP"),
- N_("show S/MIME options"),
- N_("make decrypted copy and delete"),
- N_("make decrypted copy"),
- N_("wipe passphrase(s) from memory"),
- N_("extract supported public keys"),
- NULL
-};
-#endif /* MAIN_C */
-
-enum {
- OP_NULL,
- OP_END_COND,
- OP_ATTACH_VIEW_MAILCAP,
- OP_ATTACH_VIEW_TEXT,
- OP_ATTACH_COLLAPSE,
- OP_BOTTOM_PAGE,
- OP_BOUNCE_MESSAGE,
- OP_BROWSER_NEW_FILE,
- OP_BROWSER_VIEW_FILE,
- OP_BROWSER_TELL,
- OP_BROWSER_SUBSCRIBE,
- OP_BROWSER_UNSUBSCRIBE,
- OP_BROWSER_TOGGLE_LSUB,
- OP_BUFFY_LIST,
- OP_CHANGE_DIRECTORY,
- OP_CHECK_NEW,
- OP_COMPOSE_ATTACH_FILE,
- OP_COMPOSE_ATTACH_MESSAGE,
- OP_COMPOSE_EDIT_BCC,
- OP_COMPOSE_EDIT_CC,
- OP_COMPOSE_EDIT_DESCRIPTION,
- OP_COMPOSE_EDIT_ENCODING,
- OP_COMPOSE_EDIT_FCC,
- OP_COMPOSE_EDIT_FILE,
- OP_COMPOSE_EDIT_FROM,
- OP_COMPOSE_EDIT_HEADERS,
- OP_COMPOSE_EDIT_MESSAGE,
- OP_COMPOSE_EDIT_MIME,
- OP_COMPOSE_EDIT_REPLY_TO,
- OP_COMPOSE_EDIT_SUBJECT,
- OP_COMPOSE_EDIT_TO,
- OP_CREATE_MAILBOX,
- OP_EDIT_TYPE,
- OP_COMPOSE_GET_ATTACHMENT,
- OP_COMPOSE_ISPELL,
- OP_COMPOSE_NEW_MIME,
- OP_COMPOSE_TOGGLE_RECODE,
- OP_COMPOSE_POSTPONE_MESSAGE,
- OP_COMPOSE_RENAME_FILE,
- OP_COMPOSE_SEND_MESSAGE,
- OP_COMPOSE_TOGGLE_DISPOSITION,
- OP_COMPOSE_TOGGLE_UNLINK,
- OP_COMPOSE_UPDATE_ENCODING,
- OP_COMPOSE_WRITE_MESSAGE,
- OP_COPY_MESSAGE,
- OP_CREATE_ALIAS,
- OP_CURRENT_BOTTOM,
- OP_CURRENT_MIDDLE,
- OP_CURRENT_TOP,
- OP_DECODE_COPY,
- OP_DECODE_SAVE,
- OP_DELETE,
- OP_DELETE_MAILBOX,
- OP_DELETE_SUBTHREAD,
- OP_DELETE_THREAD,
- OP_DISPLAY_ADDRESS,
- OP_DISPLAY_HEADERS,
- OP_DISPLAY_MESSAGE,
- OP_EDIT_MESSAGE,
- OP_EDITOR_BACKSPACE,
- OP_EDITOR_BACKWARD_CHAR,
- OP_EDITOR_BACKWARD_WORD,
- OP_EDITOR_BOL,
- OP_EDITOR_BUFFY_CYCLE,
- OP_EDITOR_COMPLETE,
- OP_EDITOR_COMPLETE_QUERY,
- OP_EDITOR_DELETE_CHAR,
- OP_EDITOR_EOL,
- OP_EDITOR_FORWARD_CHAR,
- OP_EDITOR_FORWARD_WORD,
- OP_EDITOR_HISTORY_DOWN,
- OP_EDITOR_HISTORY_UP,
- OP_EDITOR_KILL_EOL,
- OP_EDITOR_KILL_EOW,
- OP_EDITOR_KILL_LINE,
- OP_EDITOR_KILL_WORD,
- OP_EDITOR_QUOTE_CHAR,
- OP_EDITOR_TRANSPOSE_CHARS,
- OP_EDITOR_CAPITALIZE_WORD,
- OP_EDITOR_DOWNCASE_WORD,
- OP_EDITOR_UPCASE_WORD,
- OP_ENTER_COMMAND,
- OP_ENTER_MASK,
- OP_EXIT,
- OP_FILTER,
- OP_FIRST_ENTRY,
- OP_FLAG_MESSAGE,
- OP_FORWARD_MESSAGE,
- OP_GENERIC_SELECT_ENTRY,
- OP_GROUP_REPLY,
- OP_HALF_DOWN,
- OP_HALF_UP,
- OP_HELP,
- OP_JUMP,
- OP_LAST_ENTRY,
- OP_LIST_REPLY,
- OP_MACRO,
- OP_MAIL,
- OP_MAIN_BREAK_THREAD,
- OP_MAIN_CHANGE_FOLDER,
- OP_MAIN_CHANGE_FOLDER_READONLY,
- OP_MAIN_CLEAR_FLAG,
- OP_MAIN_DELETE_PATTERN,
- OP_MAIN_IMAP_FETCH,
- OP_MAIN_FETCH_MAIL,
- OP_MAIN_FIRST_MESSAGE,
- OP_MAIN_LAST_MESSAGE,
- OP_MAIN_LIMIT,
- OP_MAIN_LINK_THREADS,
- OP_MAIN_NEXT_UNREAD_MAILBOX,
- OP_MAIN_NEXT_NEW,
- OP_MAIN_NEXT_NEW_THEN_UNREAD,
- OP_MAIN_NEXT_SUBTHREAD,
- OP_MAIN_NEXT_THREAD,
- OP_MAIN_NEXT_UNDELETED,
- OP_MAIN_NEXT_UNREAD,
- OP_MAIN_PARENT_MESSAGE,
- OP_MAIN_PREV_THREAD,
- OP_MAIN_PREV_SUBTHREAD,
- OP_MAIN_PREV_UNDELETED,
- OP_MAIN_PREV_NEW,
- OP_MAIN_PREV_NEW_THEN_UNREAD,
- OP_MAIN_PREV_UNREAD,
- OP_MAIN_READ_THREAD,
- OP_MAIN_READ_SUBTHREAD,
- OP_MAIN_SET_FLAG,
- OP_MAIN_SYNC_FOLDER,
- OP_MAIN_TAG_PATTERN,
- OP_MAIN_UNDELETE_PATTERN,
- OP_MAIN_UNTAG_PATTERN,
- OP_MIDDLE_PAGE,
- OP_NEXT_ENTRY,
- OP_NEXT_LINE,
- OP_NEXT_PAGE,
- OP_PAGER_BOTTOM,
- OP_PAGER_HIDE_QUOTED,
- OP_PAGER_SKIP_QUOTED,
- OP_PAGER_TOP,
- OP_PIPE,
- OP_PREV_ENTRY,
- OP_PREV_LINE,
- OP_PREV_PAGE,
- OP_PRINT,
- OP_PURGE_MESSAGE,
- OP_QUERY,
- OP_QUERY_APPEND,
- OP_QUIT,
- OP_RECALL_MESSAGE,
- OP_REDRAW,
- OP_REFORMAT_WINCH,
- OP_RENAME_MAILBOX,
- OP_REPLY,
- OP_RESEND,
- OP_SAVE,
- OP_SEARCH,
- OP_SEARCH_REVERSE,
- OP_SEARCH_NEXT,
- OP_SEARCH_OPPOSITE,
- OP_SEARCH_TOGGLE,
- OP_SHELL_ESCAPE,
- OP_SORT,
- OP_SORT_REVERSE,
- OP_TAG,
- OP_TAG_PREFIX,
- OP_TAG_PREFIX_COND,
- OP_TAG_SUBTHREAD,
- OP_TAG_THREAD,
- OP_TOGGLE_NEW,
- OP_TOGGLE_WRITE,
- OP_TOGGLE_MAILBOXES,
- OP_TOP_PAGE,
- OP_UNDELETE,
- OP_UNDELETE_THREAD,
- OP_UNDELETE_SUBTHREAD,
- OP_VERSION,
- OP_VIEW_ATTACH,
- OP_VIEW_ATTACHMENTS,
- OP_WHAT_KEY,
- OP_MAIN_SHOW_LIMIT,
- OP_MAIN_COLLAPSE_THREAD,
- OP_MAIN_COLLAPSE_ALL,
- OP_MIX_USE,
- OP_MIX_APPEND,
- OP_MIX_INSERT,
- OP_MIX_DELETE,
- OP_MIX_CHAIN_PREV,
- OP_MIX_CHAIN_NEXT,
- OP_COMPOSE_MIX,
- OP_COMPOSE_ATTACH_KEY,
- OP_COMPOSE_PGP_MENU,
- OP_MAIL_KEY,
- OP_VERIFY_KEY,
- OP_VIEW_ID,
- OP_CHECK_TRADITIONAL,
- OP_COMPOSE_SMIME_MENU,
- OP_DECRYPT_SAVE,
- OP_DECRYPT_COPY,
- OP_FORGET_PASSPHRASE,
- OP_EXTRACT_KEYS,
- OP_MAX
-};
+++ /dev/null
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# m4/Makefile. Generated from Makefile.in by configure.
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-
-VPATH = ../../m4
-pkgdatadir = $(datadir)/mutt
-pkglibdir = $(libdir)/mutt
-pkgincludedir = $(includedir)/mutt
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-build_triplet = i486-pc-linux-gnu
-host_triplet = i486-pc-linux-gnu
-subdir = m4
-DIST_COMMON = README $(srcdir)/Makefile.am $(srcdir)/Makefile.in
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/m4/codeset.m4 \
- $(top_srcdir)/m4/curslib.m4 $(top_srcdir)/m4/funcdecl.m4 \
- $(top_srcdir)/m4/funcs.m4 $(top_srcdir)/m4/gettext.m4 \
- $(top_srcdir)/m4/glibc21.m4 $(top_srcdir)/m4/gpgme.m4 \
- $(top_srcdir)/m4/gssapi.m4 $(top_srcdir)/m4/iconv.m4 \
- $(top_srcdir)/m4/lcmessage.m4 $(top_srcdir)/m4/progtest.m4 \
- $(top_srcdir)/m4/types.m4 $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
- $(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES =
-SOURCES =
-DIST_SOURCES =
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-ACLOCAL = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run aclocal-1.10
-ALLOCA =
-AMTAR = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run tar
-AR = ar
-AUTOCONF = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoconf
-AUTOHEADER = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run autoheader
-AUTOMAKE = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run automake-1.10
-AWK = gawk
-BUILD_INCLUDED_LIBINTL = no
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-CATOBJEXT = .gmo
-CC = gcc
-CCDEPMODE = depmode=none
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CONFIG_STATUS_DEPENDENCIES = $(top_srcdir)/VERSION
-CPP = gcc -E
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-CYGPATH_W = echo
-DATADIRNAME = share
-DBX = no
-DEBUGGER = /usr/bin/gdb
-DEFS = -DHAVE_CONFIG_H
-DEPDIR = .deps
-DOTLOCK_GROUP = mail
-DOTLOCK_PERMISSION = 2755
-DOTLOCK_TARGET = mutt_dotlock$(EXEEXT)
-DSLROOT =
-ECHO_C =
-ECHO_N = -n
-ECHO_T =
-EGREP = /bin/grep -E
-EXEEXT =
-GDB = /usr/bin/gdb
-GENCAT = gencat
-GLIBC21 = yes
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-GMSGFMT = /usr/bin/msgfmt
-GNUTLS_CFLAGS =
-GNUTLS_LIBS = -lgnutls
-GPGME_CFLAGS =
-GPGME_CONFIG = /usr/bin/gpgme-config
-GPGME_LIBS = -lgpgme -lgpg-error
-GREP = /bin/grep
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-INSTALL_PROGRAM = ${INSTALL}
-INSTALL_SCRIPT = ${INSTALL}
-INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
-INSTOBJEXT = .mo
-INTLBISON = bison
-INTLLIBS =
-INTLOBJS =
-INTL_LIBTOOL_SUFFIX_PREFIX =
-ISPELL = no
-KRB5CFGPATH = /usr/bin/krb5-config
-LDFLAGS = -L/lib
-LIBICONV =
-LIBIMAP = -Limap -limap
-LIBIMAPDEPS = $(top_srcdir)/imap/imap.h imap/libimap.a
-LIBOBJS =
-LIBS = -lidn
-LTLIBOBJS =
-MAINT = #
-MAKEINFO = ${SHELL} /home/nightolo/debian-pkg/mutt/mutt/missing --run makeinfo
-MKDIR_P = /bin/mkdir -p
-MKINSTALLDIRS = ../mkinstalldirs
-MSGFMT = /usr/bin/msgfmt
-MUTTLIBS = -lncursesw -lncursesw -L/usr/lib -Wall -g -O2 -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lgnutls -lsasl2 -lgdbm
-MUTT_LIB_OBJECTS = crypt-gpgme.o crypt-mod-pgp-gpgme.o crypt-mod-smime-gpgme.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o pop.o pop_lib.o pop_auth.o smtp.o bcache.o account.o mutt_socket.o mutt_tunnel.o mutt_ssl_gnutls.o mutt_sasl.o hcache.o md5.o mutt_idna.o
-MUTT_MD5 = mutt_md5
-OBJEXT = o
-OPS = $(srcdir)/OPS $(srcdir)/OPS.MIX $(srcdir)/OPS.PGP $(srcdir)/OPS.SMIME $(srcdir)/OPS.CRYPT
-OSPCAT = /usr/bin/ospcat
-PACKAGE = mutt
-PACKAGE_BUGREPORT =
-PACKAGE_NAME =
-PACKAGE_STRING =
-PACKAGE_TARNAME =
-PACKAGE_VERSION =
-PATH_SEPARATOR = :
-PGPAUX_TARGET = pgpring$(EXEEXT) pgpewrap$(EXEEXT)
-PKG_CONFIG = /usr/bin/pkg-config
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-POSUB = po
-RANLIB = ranlib
-SDB = no
-SENDMAIL = /usr/sbin/sendmail
-SET_MAKE =
-SHELL = /bin/sh
-SMIMEAUX_TARGET = smime_keys
-STRIP =
-U =
-USE_INCLUDED_LIBINTL = no
-USE_NLS = yes
-VERSION = 1.5.19
-XGETTEXT = /usr/bin/xgettext
-abs_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/m4
-abs_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/../m4
-abs_top_builddir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu
-abs_top_srcdir = /home/nightolo/debian-pkg/mutt/mutt/obj-i486-linux-gnu/..
-ac_ct_CC = gcc
-am__include = include
-am__leading_dot = .
-am__quote =
-am__tar = ${AMTAR} chof - "$$tardir"
-am__untar = ${AMTAR} xf -
-bindir = ${exec_prefix}/bin
-build = i486-pc-linux-gnu
-build_alias = i486-linux-gnu
-build_cpu = i486
-build_os = linux-gnu
-build_vendor = pc
-builddir = .
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-docdir = /usr/share/doc
-dvidir = ${docdir}
-exec_prefix = ${prefix}
-host = i486-pc-linux-gnu
-host_alias =
-host_cpu = i486
-host_os = linux-gnu
-host_vendor = pc
-htmldir = ${docdir}
-includedir = ${prefix}/include
-infodir = ${datarootdir}/info
-install_sh = $(SHELL) /home/nightolo/debian-pkg/mutt/mutt/install-sh
-libdir = ${exec_prefix}/lib
-libexecdir = ${exec_prefix}/libexec
-localedir = ${datarootdir}/locale
-localstatedir = ${prefix}/var
-mandir = /usr/share/man
-mkdir_p = /bin/mkdir -p
-oldincludedir = /usr/include
-pdfdir = ${docdir}
-prefix = /usr
-program_transform_name = s,x,x,
-psdir = ${docdir}
-sbindir = ${exec_prefix}/sbin
-sharedstatedir = ${prefix}/com
-srcdir = ../../m4
-sysconfdir = /etc
-target_alias =
-top_build_prefix = ../
-top_builddir = ..
-top_srcdir = ../..
-EXTRA_DIST = README
-all: all-am
-
-.SUFFIXES:
-$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am $(am__configure_deps)
- @for dep in $?; do \
- case '$(am__configure_deps)' in \
- *$$dep*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
- && exit 0; \
- exit 1;; \
- esac; \
- done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu m4/Makefile'; \
- cd $(top_srcdir) && \
- $(AUTOMAKE) --gnu m4/Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
- @case '$?' in \
- *config.status*) \
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
- *) \
- echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
- cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
- esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-$(top_srcdir)/configure: # $(am__configure_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-tags: TAGS
-TAGS:
-
-ctags: CTAGS
-CTAGS:
-
-
-distdir: $(DISTFILES)
- @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
- list='$(DISTFILES)'; \
- dist_files=`for file in $$list; do echo $$file; done | \
- sed -e "s|^$$srcdirstrip/||;t" \
- -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
- case $$dist_files in \
- */*) $(MKDIR_P) `echo "$$dist_files" | \
- sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
- sort -u` ;; \
- esac; \
- for file in $$dist_files; do \
- if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
- if test -d $$d/$$file; then \
- dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
- if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
- cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
- fi; \
- cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
- else \
- test -f $(distdir)/$$file \
- || cp -p $$d/$$file $(distdir)/$$file \
- || exit 1; \
- fi; \
- done
- $(MAKE) $(AM_MAKEFLAGS) \
- top_distdir="$(top_distdir)" distdir="$(distdir)" \
- dist-hook
-check-am: all-am
-check: check-am
-all-am: Makefile
-installdirs:
-install: install-am
-install-exec: install-exec-am
-install-data: install-data-am
-uninstall: uninstall-am
-
-install-am: all-am
- @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-am
-install-strip:
- $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
- install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
- `test -z '$(STRIP)' || \
- echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
- -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-
-maintainer-clean-generic:
- @echo "This command is intended for maintainers to use"
- @echo "it deletes files that may require special tools to rebuild."
-clean: clean-am
-
-clean-am: clean-generic mostlyclean-am
-
-distclean: distclean-am
- -rm -f Makefile
-distclean-am: clean-am distclean-generic
-
-dvi: dvi-am
-
-dvi-am:
-
-html: html-am
-
-info: info-am
-
-info-am:
-
-install-data-am:
-
-install-dvi: install-dvi-am
-
-install-exec-am:
-
-install-html: install-html-am
-
-install-info: install-info-am
-
-install-man:
-
-install-pdf: install-pdf-am
-
-install-ps: install-ps-am
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-am
- -rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-am
-
-mostlyclean-am: mostlyclean-generic
-
-pdf: pdf-am
-
-pdf-am:
-
-ps: ps-am
-
-ps-am:
-
-uninstall-am:
-
-.MAKE: install-am install-strip
-
-.PHONY: all all-am check check-am clean clean-generic dist-hook \
- distclean distclean-generic distdir dvi dvi-am html html-am \
- info info-am install install-am install-data install-data-am \
- install-dvi install-dvi-am install-exec install-exec-am \
- install-html install-html-am install-info install-info-am \
- install-man install-pdf install-pdf-am install-ps \
- install-ps-am install-strip installcheck installcheck-am \
- installdirs maintainer-clean maintainer-clean-generic \
- mostlyclean mostlyclean-generic pdf pdf-am ps ps-am uninstall \
- uninstall-am
-
-
-dist-hook:
- for i in $(srcdir)/*.m4 ; do \
- cp -f -p $$i $(distdir) ; \
- done
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-#!/bin/sh
-
-#
-# File a bug against the Mutt mail user agent.
-#
-
-#
-# $Id$
-#
-
-#
-# Copyright (c) 2000 Thomas Roessler <roessler@does-not-exist.org>
-#
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-#
-
-SUBMIT="fleas@mutt.org"
-DEBIAN_SUBMIT="submit@bugs.debian.org"
-
-prefix=/usr
-
-DEBUGGER=/usr/bin/gdb
-SENDMAIL=/usr/sbin/sendmail
-sysconfdir=/etc
-pkgdatadir=@pkgdatadir@
-
-include_file ()
-{
- echo
- echo "--- Begin $1"
- sed -e '/^[ ]*#/d; /^[ ]*$/d; s/^-/- -/' $1
- echo "--- End $1"
- echo
-}
-
-debug_gdb ()
-{
- cat << EOF > $SCRATCH/gdb.rc
-bt
-list
-quit
-EOF
- $DEBUGGER -n -x $SCRATCH/gdb.rc -c $CORE mutt
-}
-
-debug_dbx ()
-{
- cat << EOF > $SCRATCH/dbx.rc
-where
-list
-quit
-EOF
- $DEBUGGER -s $SCRATCH/dbx.rc mutt $CORE
-}
-
-debug_sdb ()
-{
- cat << EOF > $SCRATCH/sdb.rc
-t
-w
-q
-EOF
- $DEBUGGER mutt $CORE < $SCRATCH/sdb.rc
-}
-
-case `echo -n` in
-"") n=-n; c= ;;
- *) n=; c='\c' ;;
-esac
-
-
-exec > /dev/tty
-exec < /dev/tty
-
-SCRATCH=${TMPDIR-/tmp}/`basename $0`.`hostname`.$$
-
-mkdir ${SCRATCH} || \
-{
- echo "`basename $0`: Can't create temporary directory." >& 2 ;
- exit 1 ;
-}
-
-trap "rm -r -f ${SCRATCH} ; trap '' 0 ; exit" 0 1 2
-
-TEMPLATE=${SCRATCH}/template.txt
-
-if test -z "$EMAIL" ; then
- EMAIL="`mutt -Q from 2> /dev/null | sed -e 's/^from=.\(.*\).$/\1/'`"
-fi
-
-EMAILTMP=''
-while test -z "$EMAILTMP"
-do
- echo "Please enter your e-mail address [$EMAIL]:"
- echo $n "> $c"
- read EMAILTMP
-
- if test -z "$EMAILTMP"; then EMAILTMP="$EMAIL"; fi
-
- if ! echo "$EMAILTMP" | grep -q @
- then
- echo "$EMAILTMP does not appear to be a valid email address"
- EMAILTMP=''
- continue
- fi
-
- EMAIL="$EMAILTMP"
-done
-
-echo "Please enter a one-line description of the problem you experience:"
-echo $n "> $c"
-read SUBJECT
-
-cat <<EOF
-What should the severity for this bug report be?
-
- 0) Feature request, or maybe a bug which is very difficult to
- fix due to major design considerations.
-
- 1) The package fails to perform correctly in some conditions,
- or on some systems, or fails to comply with current policy
- documents. Most bugs are in this category.
-
- 2) This bug makes this version of the package unsuitable for
- a stable release.
-
- 3) Dangerous bug. Makes the package in question unusable by
- anyone or mostly so, or causes data loss, or introduces a
- security hole allowing access to the accounts of users who
- use the package.
-
- 4) Critical bug. Makes unrelated software on the system (or
- the whole system) break, or causes serious data loss, or
- introduces a security hole on systems where you install the
- package.
-
-EOF
-echo $n "Severity? [01234] $c"
-read severity
-case "$severity" in
-0|[Ww]) severity=wishlist ;;
-2|[Ii]) severity=important ;;
-3|[Gg]) severity=grave ;;
-4|[Cc]) severity=critical ;;
- *) severity=normal ;;
-esac
-
-if test -x $DEBUGGER ; then
- test -f core && CORE=core
- echo "If mutt has crashed, it may have saved some program state in"
- echo "a file named core. We can include this information with the bug"
- echo "report if you wish so."
- echo "Do you want to include information gathered from a core file?"
- echo "If yes, please enter the path - otherwise just say no: [$CORE]"
- echo $n "> $c"
- read _CORE
- test "$_CORE" && CORE="$_CORE"
-fi
-
-echo $n "Do you want to include your personal mutt configuration files? [Y|n] $c"
-read personal
-case "$personal" in
-[nN]*) personal=no ;;
- *) personal=yes ;;
-esac
-
-echo $n "Do you want to include your system's global mutt configuration file? [Y|n] $c"
-read global
-case "$global" in
-[nN]*) global=no ;;
- *) global=yes ;;
-esac
-
-if test -f /etc/debian_version ; then
- DEBIAN=yes
- echo $n "Checking whether mutt has been installed as a package... $c"
- DEBIANVERSION="`dpkg -l mutt | grep '^[ih]' | awk '{print $3}'`" 2> /dev/null
- if test "$DEBIANVERSION" ; then
- DPKG=yes
- else
- DPKG=no
- unset DEBIANVERSION
- fi
- echo "$DPKG"
- echo $n "File this bug with Debian? [Y|n] $c"
- read DPKG
- case "$DPKG" in
- [nN]) DPKG=no ;;
- *) DPKG=yes ;;
- esac
-else
- DEBIAN=no
- DPKG=no
-fi
-
-if rpm -q mutt > /dev/null 2> /dev/null ; then
- echo "Mutt seems to come from an RPM package."
- RPMVERSION="`rpm -q mutt`"
- RPMPACKAGER="`rpm -q -i mutt | sed -n -e 's/^Packager *: *//p'`"
-fi
-
-MUTTVERSION="`mutt -v | awk '{print $2; exit; }'`"
-test "$DPKG" = "yes" && SUBMIT="$SUBMIT, $DEBIAN_SUBMIT"
-
-exec > ${TEMPLATE}
-
-test "$EMAIL" && echo "From: $EMAIL"
-test "$REPLYTO" && echo "Reply-To: $REPLYTO"
-test "$ORGANIZATION" && echo "Organization: $ORGANIZATION"
-
-echo "Subject: mutt-$MUTTVERSION: $SUBJECT"
-echo "To: $SUBMIT"
-test "$EMAIL" && echo "Bcc: ${EMAIL}"
-echo
-echo "Package: mutt"
-echo "Version: ${DEBIANVERSION-${RPMVERSION-$MUTTVERSION}}"
-echo "Severity: $severity"
-echo
-echo "-- Please type your report below this line"
-echo
-echo
-echo
-
-if test "$DEBIAN" = "yes" ; then
- echo "Obtaining Debian-specific information..." > /dev/tty
- bug -p -s dummy mutt < /dev/null 2> /dev/null | \
- sed -n -e "/^-- System Information/,/^---/p" | \
- grep -v '^---'
-else
- echo "-- System Information"
- echo "System Version: `uname -a`"
- test -z "$RPMPACKAGER" || echo "RPM Packager: $RPMPACKAGER";
- test -f /etc/redhat-release && echo "RedHat Release: `cat /etc/redhat-release`"
- test -f /etc/SuSE-release && echo "SuSE Release: `sed 1q /etc/SuSE-release`"
- # Please provide more of these if you have any.
-fi
-
-echo
-echo "-- Build environment information"
-echo
-echo "(Note: This is the build environment installed on the system"
-echo "muttbug is run on. Information may or may not match the environment"
-echo "used to build mutt.)"
-echo
-echo "- gcc version information"
-echo "gcc"
-gcc -v 2>&1
-echo
-echo "- CFLAGS"
-echo -Wall -pedantic -Wno-long-long -Wall -g -O2
-
-
-echo
-echo "-- Mutt Version Information"
-echo
-LC_ALL=C mutt -v
-
-if test "$CORE" && test -f "$CORE" ; then
- echo
- echo "-- Core Dump Analysis Output"
- echo
-
- case "$DEBUGGER" in
- *sdb) debug_sdb $CORE ;;
- *dbx) debug_dbx $CORE ;;
- *gdb) debug_gdb $CORE ;;
- esac
-
- echo
-fi
-
-if test "$personal" = "yes" ; then
- CANDIDATES=".muttrc-${MUTTVERSION} .muttrc .mutt/muttrc-${MUTTVERSION} .mutt/muttrc"
- MATCHED="none"
- for f in $CANDIDATES; do
- if test -f "${HOME}/$f" ; then
- MATCHED="${HOME}/$f"
- break
- fi
- done
-
- if test "$MATCHED" = "none" ; then
- echo "Warning: Can't find your personal .muttrc." >&2
- else
- include_file $MATCHED
- fi
-fi
-
-
-if test "$global" = "yes" ; then
- CANDIDATES="Muttrc-${MUTTVERSION} Muttrc"
- DIRECTORIES="$sysconfdir $pkgdatadir"
- MATCHED="none"
- for d in $DIRECTORIES ; do
- for f in $CANDIDATES; do
- if test -f $d/$f ; then
- MATCHED="$d/$f"
- break
- fi
- done
- test "$MATCHED" = "none" || break
- done
-
- if test "$MATCHED" = "none" ; then
- echo "Warning: Can't find global Muttrc." >&2
- else
- include_file $MATCHED
- fi
-fi
-
-exec > /dev/tty
-
-cp $TEMPLATE $SCRATCH/mutt-bug.txt
-
-input="e"
-while : ; do
- if test "$input" = "e" ; then
- ${VISUAL-${EDITOR-vi}} $SCRATCH/mutt-bug.txt
- if cmp $SCRATCH/mutt-bug.txt ${TEMPLATE} > /dev/null ; then
- echo "Warning: Bug report was not modified!"
- fi
- fi
-
- echo $n "Submit, Edit, View, Quit? [S|e|v|q] $c"
- read _input
- input="`echo $_input | tr EVSQ evsq`"
- case $input in
- e*) ;;
- v*) ${PAGER-more} $SCRATCH/mutt-bug.txt ;;
- s*|"") $SENDMAIL -t < $SCRATCH/mutt-bug.txt ; exit ;;
- q*) exit
- esac
-done
-
+++ /dev/null
-/* this is an autogenerated file. edit patchlist.sh instead. */
-#include "config.h"
-
-#include <stdio.h>
-#include <stdlib.h>
-
-#include "mutt.h"
-
-void mutt_print_patchlist (void)
-{
- puts ("patch-1.5.13.cd.ifdef.2");
- puts ("patch-1.5.18.rr.compressed.1");
-}
+++ /dev/null
-# Makefile for program source directory in GNU NLS utilities package.
-# Copyright (C) 1995-1997, 2000, 2001 by Ulrich Drepper <drepper@gnu.ai.mit.edu>
-#
-# This file file be copied and used freely without restrictions. It can
-# be used in projects which are not available under the GNU General Public License
-# but which still want to provide support for the GNU gettext functionality.
-# Please note that the actual code is *not* freely available.
-
-PACKAGE = mutt
-VERSION = 1.5.19
-
-# These two variables depend on the location of this directory.
-subdir = po
-top_builddir = ..
-
-SHELL = /bin/sh
-
-
-srcdir = ../../po
-top_srcdir = ../..
-VPATH = ../../po
-
-prefix = /usr
-exec_prefix = ${prefix}
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-localedir = $(datadir)/locale
-gettextsrcdir = $(datadir)/gettext/po
-
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-MKINSTALLDIRS = ../mkinstalldirs
-mkinstalldirs = $(SHELL) `case "$(MKINSTALLDIRS)" in /*) echo "$(MKINSTALLDIRS)" ;; *) echo "$(top_builddir)/$(MKINSTALLDIRS)" ;; esac`
-
-CC = gcc
-GMSGFMT = /usr/bin/msgfmt
-MSGFMT = /usr/bin/msgfmt
-XGETTEXT = /usr/bin/xgettext
-MSGMERGE = msgmerge
-
-DEFS = -DHAVE_CONFIG_H
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-
-INCLUDES = -I.. -I$(top_srcdir)/intl
-
-COMPILE = $(CC) -c $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $(XCFLAGS)
-
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-DISTFILES = Makefile.in.in POTFILES.in $(PACKAGE).pot \
-$(POFILES) $(GMOFILES)
-
-# need two spaces before = as m4/gettext.m4 matches against
-# 'POTFILES[space]=' to add files from POTFILES
-BUILT_POTFILES = $(top_builddir)/keymap_alldefs.h
-
-POTFILES = \
- ../../account.c \
- ../../addrbook.c \
- ../../alias.c \
- ../../attach.c \
- ../../browser.c \
- ../../buffy.c \
- ../../charset.c \
- ../../color.c \
- ../../commands.c \
- ../../compose.c \
- ../../compress.c \
- ../../crypt-gpgme.c \
- ../../crypt.c \
- ../../cryptglue.c \
- ../../curs_lib.c \
- ../../curs_main.c \
- ../../edit.c \
- ../../editmsg.c \
- ../../flags.c \
- ../../handler.c \
- ../../headers.c \
- ../../help.c \
- ../../history.c \
- ../../hook.c \
- ../../imap/auth.c \
- ../../imap/auth_anon.c \
- ../../imap/auth_cram.c \
- ../../imap/auth_gss.c \
- ../../imap/auth_login.c \
- ../../imap/auth_sasl.c \
- ../../imap/browse.c \
- ../../imap/command.c \
- ../../imap/imap.c \
- ../../imap/message.c \
- ../../imap/util.c \
- ../../init.c \
- ../../keymap.c \
- ../../lib.c \
- ../../main.c \
- ../../mbox.c \
- ../../menu.c \
- ../../mh.c \
- ../../mutt_sasl.c \
- ../../mutt_socket.c \
- ../../mutt_ssl.c \
- ../../mutt_ssl_gnutls.c \
- ../../mutt_tunnel.c \
- ../../muttlib.c \
- ../../mx.c \
- ../../pager.c \
- ../../parse.c \
- ../../pattern.c \
- ../../pgp.c \
- ../../pgpinvoke.c \
- ../../pgpkey.c \
- ../../pop.c \
- ../../pop_auth.c \
- ../../pop_lib.c \
- ../../postpone.c \
- ../../query.c \
- ../../recvattach.c \
- ../../recvcmd.c \
- ../../remailer.c \
- ../../rfc1524.c \
- ../../score.c \
- ../../send.c \
- ../../sendlib.c \
- ../../signal.c \
- ../../smime.c \
- ../../smtp.c \
- ../../sort.c \
- ../../status.c \
- ../../thread.c
-
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-
-.SUFFIXES:
-.SUFFIXES: .c .o .po .pox .gmo .mo
-
-.c.o:
- $(COMPILE) $<
-
-.po.pox:
- $(MAKE) $(PACKAGE).pot
- $(MSGMERGE) $< $(PACKAGE).pot -o $*.pox
-
-.po.mo:
- $(MSGFMT) -o $@ $<
-
-.po.gmo:
- file=`echo $* | sed 's,.*/,,'`.gmo \
- && rm -f $$file && $(GMSGFMT) --statistics -o $$file $<
-
-
-all: all-yes
-
-all-yes: $(CATALOGS)
-all-no:
-
-$(top_builddir)/keymap_alldefs.h:
- ( cd $(top_builddir) && $(MAKE) keymap_alldefs.h )
-
-# Note: Target 'all' must not depend on target '$(srcdir)/$(PACKAGE).pot',
-# otherwise packages like GCC can not be built if only parts of the source
-# have been downloaded.
-
-$(PACKAGE).pot: $(POTFILES) $(BUILT_POTFILES) $(srcdir)/POTFILES.in
- rm -f $(PACKAGE).pot $(PACKAGE).po
- $(XGETTEXT) --default-domain=$(PACKAGE) --directory=$(top_srcdir) \
- --add-comments --keyword=_ --keyword=N_ \
- --files-from=$(srcdir)/POTFILES.in \
- && \
- $(XGETTEXT) --default-domain=$(PACKAGE) \
- --add-comments --keyword=_ --keyword=N_ \
- --join $(BUILT_POTFILES) \
- && test ! -f $(PACKAGE).po \
- || ( rm -f $(PACKAGE).pot \
- && mv $(PACKAGE).po $(PACKAGE).pot )
-
-
-install: install-exec install-data
-install-exec:
-install-data: install-data-yes
- if test "$(PACKAGE)" = "gettext"; then \
- $(mkinstalldirs) $(DESTDIR)$(gettextsrcdir); \
- $(INSTALL_DATA) $(srcdir)/Makefile.in.in \
- $(DESTDIR)$(gettextsrcdir)/Makefile.in.in; \
- else \
- : ; \
- fi
-install-data-no: all
-install-data-yes: all
- $(mkinstalldirs) $(DESTDIR)$(datadir)
- @catalogs='$(CATALOGS)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- dir=$(localedir)/$$lang/LC_MESSAGES; \
- $(mkinstalldirs) $(DESTDIR)$$dir; \
- if test -r $$cat; then \
- $(INSTALL_DATA) $$cat $(DESTDIR)$$dir/$(PACKAGE).mo; \
- echo "installing $$cat as $(DESTDIR)$$dir/$(PACKAGE).mo"; \
- else \
- $(INSTALL_DATA) $(srcdir)/$$cat $(DESTDIR)$$dir/$(PACKAGE).mo; \
- echo "installing $(srcdir)/$$cat as" \
- "$(DESTDIR)$$dir/$(PACKAGE).mo"; \
- fi; \
- done
-
-# Define this as empty until I found a useful application.
-installcheck:
-
-uninstall:
- catalogs='$(CATALOGS)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- rm -f $(DESTDIR)$(localedir)/$$lang/LC_MESSAGES/$(PACKAGE).mo; \
- done
- if test "$(PACKAGE)" = "gettext"; then \
- rm -f $(DESTDIR)$(gettextsrcdir)/Makefile.in.in; \
- else \
- : ; \
- fi
-
-check: all
-
-dvi info tags TAGS ID:
-
-mostlyclean:
- rm -f core core.* *.pox $(PACKAGE).po *.new.po
- rm -fr *.o
-
-clean: mostlyclean
-
-distclean: clean
- rm -f Makefile Makefile.in POTFILES *.mo
-
-maintainer-clean: distclean
- @echo "This command is intended for maintainers to use;"
- @echo "it deletes files that may require special tools to rebuild."
- rm -f $(GMOFILES)
-
-distdir = $(top_builddir)/$(PACKAGE)-$(VERSION)/$(subdir)
-dist distdir: $(DISTFILES)
- dists="$(DISTFILES)"; \
- for file in $$dists; do \
- if test -f $$file; then dir=.; else dir=$(srcdir); fi; \
- cp -p $$dir/$$file $(distdir); \
- done
-
-update-po: Makefile
- $(MAKE) $(PACKAGE).pot
- if test "$(PACKAGE)" = "gettext"; then PATH=`pwd`/../src:$$PATH; fi; \
- cd $(srcdir); \
- catalogs='$(GMOFILES)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- echo "$$lang:"; \
- if $(MSGMERGE) $$lang.po $(PACKAGE).pot -o $$lang.new.po; then \
- mv -f $$lang.new.po $$lang.po; \
- else \
- echo "msgmerge for $$cat failed!"; \
- rm -f $$lang.new.po; \
- fi; \
- done
- $(MAKE) update-gmo
-
-update-gmo: Makefile $(GMOFILES)
- @:
-
-Makefile: Makefile.in.in $(top_builddir)/config.status POTFILES.in
- cd $(top_builddir) \
- && CONFIG_FILES=$(subdir)/$@.in CONFIG_HEADERS= \
- $(SHELL) ./config.status
-
-# Tell versions [3.59,3.63) of GNU make not to export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
-# Makefile for program source directory in GNU NLS utilities package.
-# Copyright (C) 1995-1997, 2000, 2001 by Ulrich Drepper <drepper@gnu.ai.mit.edu>
-#
-# This file file be copied and used freely without restrictions. It can
-# be used in projects which are not available under the GNU General Public License
-# but which still want to provide support for the GNU gettext functionality.
-# Please note that the actual code is *not* freely available.
-
-PACKAGE = mutt
-VERSION = 1.5.19
-
-# These two variables depend on the location of this directory.
-subdir = po
-top_builddir = ..
-
-SHELL = /bin/sh
-
-
-srcdir = ../../po
-top_srcdir = ../..
-VPATH = ../../po
-
-prefix = /usr
-exec_prefix = ${prefix}
-datadir = ${datarootdir}
-datarootdir = ${prefix}/share
-localedir = $(datadir)/locale
-gettextsrcdir = $(datadir)/gettext/po
-
-INSTALL = /usr/bin/install -c
-INSTALL_DATA = ${INSTALL} -m 644
-MKINSTALLDIRS = ../mkinstalldirs
-mkinstalldirs = $(SHELL) `case "$(MKINSTALLDIRS)" in /*) echo "$(MKINSTALLDIRS)" ;; *) echo "$(top_builddir)/$(MKINSTALLDIRS)" ;; esac`
-
-CC = gcc
-GMSGFMT = /usr/bin/msgfmt
-MSGFMT = /usr/bin/msgfmt
-XGETTEXT = /usr/bin/xgettext
-MSGMERGE = msgmerge
-
-DEFS = -DHAVE_CONFIG_H
-CFLAGS = -Wall -pedantic -Wno-long-long -Wall -g -O2
-CPPFLAGS = -I/usr/include/qdbm -I/usr/include/qdbm -I/include -I$(top_srcdir)/intl
-
-INCLUDES = -I.. -I$(top_srcdir)/intl
-
-COMPILE = $(CC) -c $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $(XCFLAGS)
-
-POFILES = de.po eu.po ru.po it.po es.po uk.po fr.po pl.po nl.po cs.po id.po sk.po ko.po el.po zh_TW.po zh_CN.po pt_BR.po eo.po gl.po sv.po da.po lt.po tr.po ja.po hu.po et.po ca.po bg.po ga.po
-GMOFILES = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-DISTFILES = Makefile.in.in POTFILES.in $(PACKAGE).pot \
-$(POFILES) $(GMOFILES)
-
-# need two spaces before = as m4/gettext.m4 matches against
-# 'POTFILES[space]=' to add files from POTFILES
-BUILT_POTFILES = $(top_builddir)/keymap_alldefs.h
-
-POTFILES = \
-
-CATALOGS = de.gmo eu.gmo ru.gmo it.gmo es.gmo uk.gmo fr.gmo pl.gmo nl.gmo cs.gmo id.gmo sk.gmo ko.gmo el.gmo zh_TW.gmo zh_CN.gmo pt_BR.gmo eo.gmo gl.gmo sv.gmo da.gmo lt.gmo tr.gmo ja.gmo hu.gmo et.gmo ca.gmo bg.gmo ga.gmo
-
-.SUFFIXES:
-.SUFFIXES: .c .o .po .pox .gmo .mo
-
-.c.o:
- $(COMPILE) $<
-
-.po.pox:
- $(MAKE) $(PACKAGE).pot
- $(MSGMERGE) $< $(PACKAGE).pot -o $*.pox
-
-.po.mo:
- $(MSGFMT) -o $@ $<
-
-.po.gmo:
- file=`echo $* | sed 's,.*/,,'`.gmo \
- && rm -f $$file && $(GMSGFMT) --statistics -o $$file $<
-
-
-all: all-yes
-
-all-yes: $(CATALOGS)
-all-no:
-
-$(top_builddir)/keymap_alldefs.h:
- ( cd $(top_builddir) && $(MAKE) keymap_alldefs.h )
-
-# Note: Target 'all' must not depend on target '$(srcdir)/$(PACKAGE).pot',
-# otherwise packages like GCC can not be built if only parts of the source
-# have been downloaded.
-
-$(PACKAGE).pot: $(POTFILES) $(BUILT_POTFILES) $(srcdir)/POTFILES.in
- rm -f $(PACKAGE).pot $(PACKAGE).po
- $(XGETTEXT) --default-domain=$(PACKAGE) --directory=$(top_srcdir) \
- --add-comments --keyword=_ --keyword=N_ \
- --files-from=$(srcdir)/POTFILES.in \
- && \
- $(XGETTEXT) --default-domain=$(PACKAGE) \
- --add-comments --keyword=_ --keyword=N_ \
- --join $(BUILT_POTFILES) \
- && test ! -f $(PACKAGE).po \
- || ( rm -f $(PACKAGE).pot \
- && mv $(PACKAGE).po $(PACKAGE).pot )
-
-
-install: install-exec install-data
-install-exec:
-install-data: install-data-yes
- if test "$(PACKAGE)" = "gettext"; then \
- $(mkinstalldirs) $(DESTDIR)$(gettextsrcdir); \
- $(INSTALL_DATA) $(srcdir)/Makefile.in.in \
- $(DESTDIR)$(gettextsrcdir)/Makefile.in.in; \
- else \
- : ; \
- fi
-install-data-no: all
-install-data-yes: all
- $(mkinstalldirs) $(DESTDIR)$(datadir)
- @catalogs='$(CATALOGS)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- dir=$(localedir)/$$lang/LC_MESSAGES; \
- $(mkinstalldirs) $(DESTDIR)$$dir; \
- if test -r $$cat; then \
- $(INSTALL_DATA) $$cat $(DESTDIR)$$dir/$(PACKAGE).mo; \
- echo "installing $$cat as $(DESTDIR)$$dir/$(PACKAGE).mo"; \
- else \
- $(INSTALL_DATA) $(srcdir)/$$cat $(DESTDIR)$$dir/$(PACKAGE).mo; \
- echo "installing $(srcdir)/$$cat as" \
- "$(DESTDIR)$$dir/$(PACKAGE).mo"; \
- fi; \
- done
-
-# Define this as empty until I found a useful application.
-installcheck:
-
-uninstall:
- catalogs='$(CATALOGS)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- rm -f $(DESTDIR)$(localedir)/$$lang/LC_MESSAGES/$(PACKAGE).mo; \
- done
- if test "$(PACKAGE)" = "gettext"; then \
- rm -f $(DESTDIR)$(gettextsrcdir)/Makefile.in.in; \
- else \
- : ; \
- fi
-
-check: all
-
-dvi info tags TAGS ID:
-
-mostlyclean:
- rm -f core core.* *.pox $(PACKAGE).po *.new.po
- rm -fr *.o
-
-clean: mostlyclean
-
-distclean: clean
- rm -f Makefile Makefile.in POTFILES *.mo
-
-maintainer-clean: distclean
- @echo "This command is intended for maintainers to use;"
- @echo "it deletes files that may require special tools to rebuild."
- rm -f $(GMOFILES)
-
-distdir = $(top_builddir)/$(PACKAGE)-$(VERSION)/$(subdir)
-dist distdir: $(DISTFILES)
- dists="$(DISTFILES)"; \
- for file in $$dists; do \
- if test -f $$file; then dir=.; else dir=$(srcdir); fi; \
- cp -p $$dir/$$file $(distdir); \
- done
-
-update-po: Makefile
- $(MAKE) $(PACKAGE).pot
- if test "$(PACKAGE)" = "gettext"; then PATH=`pwd`/../src:$$PATH; fi; \
- cd $(srcdir); \
- catalogs='$(GMOFILES)'; \
- for cat in $$catalogs; do \
- cat=`basename $$cat`; \
- lang=`echo $$cat | sed 's/\.gmo$$//'`; \
- echo "$$lang:"; \
- if $(MSGMERGE) $$lang.po $(PACKAGE).pot -o $$lang.new.po; then \
- mv -f $$lang.new.po $$lang.po; \
- else \
- echo "msgmerge for $$cat failed!"; \
- rm -f $$lang.new.po; \
- fi; \
- done
- $(MAKE) update-gmo
-
-update-gmo: Makefile $(GMOFILES)
- @:
-
-Makefile: Makefile.in.in $(top_builddir)/config.status POTFILES.in
- cd $(top_builddir) \
- && CONFIG_FILES=$(subdir)/$@.in CONFIG_HEADERS= \
- $(SHELL) ./config.status
-
-# Tell versions [3.59,3.63) of GNU make not to export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:
+++ /dev/null
- ../../account.c \
- ../../addrbook.c \
- ../../alias.c \
- ../../attach.c \
- ../../browser.c \
- ../../buffy.c \
- ../../charset.c \
- ../../color.c \
- ../../commands.c \
- ../../compose.c \
- ../../compress.c \
- ../../crypt-gpgme.c \
- ../../crypt.c \
- ../../cryptglue.c \
- ../../curs_lib.c \
- ../../curs_main.c \
- ../../edit.c \
- ../../editmsg.c \
- ../../flags.c \
- ../../handler.c \
- ../../headers.c \
- ../../help.c \
- ../../history.c \
- ../../hook.c \
- ../../imap/auth.c \
- ../../imap/auth_anon.c \
- ../../imap/auth_cram.c \
- ../../imap/auth_gss.c \
- ../../imap/auth_login.c \
- ../../imap/auth_sasl.c \
- ../../imap/browse.c \
- ../../imap/command.c \
- ../../imap/imap.c \
- ../../imap/message.c \
- ../../imap/util.c \
- ../../init.c \
- ../../keymap.c \
- ../../lib.c \
- ../../main.c \
- ../../mbox.c \
- ../../menu.c \
- ../../mh.c \
- ../../mutt_sasl.c \
- ../../mutt_socket.c \
- ../../mutt_ssl.c \
- ../../mutt_ssl_gnutls.c \
- ../../mutt_tunnel.c \
- ../../muttlib.c \
- ../../mx.c \
- ../../pager.c \
- ../../parse.c \
- ../../pattern.c \
- ../../pgp.c \
- ../../pgpinvoke.c \
- ../../pgpkey.c \
- ../../pop.c \
- ../../pop_auth.c \
- ../../pop_lib.c \
- ../../postpone.c \
- ../../query.c \
- ../../recvattach.c \
- ../../recvcmd.c \
- ../../remailer.c \
- ../../rfc1524.c \
- ../../score.c \
- ../../send.c \
- ../../sendlib.c \
- ../../signal.c \
- ../../smime.c \
- ../../smtp.c \
- ../../sort.c \
- ../../status.c \
- ../../thread.c
+++ /dev/null
-const char *ReleaseDate = "2009-01-05";
+++ /dev/null
-#! /usr/bin/perl -w
-
-# Copyright (C) 2001,2002 Oliver Ehli <elmy@acm.org>
-# Copyright (C) 2001 Mike Schiraldi <raldi@research.netsol.com>
-# Copyright (C) 2003 Bjoern Jacke <bjoern@j3e.de>
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-
-use strict;
-use File::Copy;
-use File::Glob ':glob';
-
-umask 077;
-
-require "timelocal.pl";
-
-sub usage ();
-sub newfile ($;$$);
-sub mutt_Q ($ );
-sub mycopy ($$);
-
-# directory setup routines
-sub mkdir_recursive ($ );
-sub init_paths ();
-
-# key/certificate management methods
-sub list_certs ();
-sub query_label ();
-sub add_entry ($$$$$ );
-sub add_certificate ($$$$;$ );
-sub add_key ($$$$);
-sub add_root_cert ($ );
-sub parse_pem (@ );
-sub handle_pem (@ );
-sub modify_entry ($$$;$ );
-sub remove_pair ($ );
-sub change_label ($ );
-sub verify_cert($$);
-sub do_verify($$$ );
-
-# Get the directories mutt uses for certificate/key storage.
-
-my $mutt = $ENV{MUTT_CMDLINE} || 'mutt';
-my $opensslbin = "/usr/bin/openssl";
-my @tempfiles = ();
-my @cert_tmp_file = ();
-
-my $tmpdir;
-my $private_keys_path = mutt_Q 'smime_keys';
-die "smime_keys is not set in mutt's configuration file"
- if length $private_keys_path == 0;
-
-my $certificates_path = mutt_Q 'smime_certificates';
-die "smime_certificates is not set in mutt's configuration file"
- if length $certificates_path == 0;
-my $root_certs_path = mutt_Q 'smime_ca_location';
-die "smime_ca_location is not set in mutt's configuration file"
- if length $root_certs_path == 0;
-
-my $root_certs_switch;
-if ( -d $root_certs_path) {
- $root_certs_switch = -CApath;
-} else {
- $root_certs_switch = -CAfile;
-}
-
-
-#
-# OPS
-#
-
-if(@ARGV == 1 and $ARGV[0] eq "init") {
- init_paths;
-}
-elsif(@ARGV == 1 and $ARGV[0] eq "list") {
- list_certs;
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "label") {
- change_label($ARGV[1]);
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "add_cert") {
- my $format = -B $ARGV[1] ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -noout -hash -in $ARGV[1] -inform $format";
- my $cert_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
- chomp($cert_hash);
- my $label = query_label;
- &add_certificate($ARGV[1], \$cert_hash, 1, $label, '?');
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "add_pem") {
- -e $ARGV[1] and -s $ARGV[1] or die("$ARGV[1] is nonexistent or empty.");
- open(PEM_FILE, "<$ARGV[1]") or die("Can't open $ARGV[1]: $!");
- my @pem = <PEM_FILE>;
- close(PEM_FILE);
- handle_pem(@pem);
-}
-elsif( @ARGV == 2 and $ARGV[0] eq "add_p12") {
- -e $ARGV[1] and -s $ARGV[1] or die("$ARGV[1] is nonexistent or empty.");
-
- print "\nNOTE: This will ask you for two passphrases:\n";
- print " 1. The passphrase you used for exporting\n";
- print " 2. The passphrase you wish to secure your private key with.\n\n";
-
- my $pem_file = "$ARGV[1].pem";
-
- my $cmd = "$opensslbin pkcs12 -in $ARGV[1] -out $pem_file";
- system $cmd and die "'$cmd' returned $?";
-
- -e $pem_file and -s $pem_file or die("Conversion of $ARGV[1] failed.");
- open(PEM_FILE, $pem_file) or die("Can't open $pem_file: $!");
- my @pem = <PEM_FILE>;
- close(PEM_FILE);
- unlink $pem_file;
- handle_pem(@pem);
-}
-elsif(@ARGV == 4 and $ARGV[0] eq "add_chain") {
- my $mailbox;
- my $format = -B $ARGV[2] ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -noout -hash -in $ARGV[2] -inform $format";
- my $cert_hash = `$cmd`;
-
- $? and die "'$cmd' returned $?";
-
- $format = -B $ARGV[3] ? 'DER' : 'PEM';
-
- $cmd = "$opensslbin x509 -noout -hash -in $ARGV[3] -inform $format";
- my $issuer_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- chomp($cert_hash);
- chomp($issuer_hash);
-
- my $label = query_label;
-
- add_certificate($ARGV[3], \$issuer_hash, 0, $label);
- my @mailbox = &add_certificate($ARGV[2], \$cert_hash, 1, $label, $issuer_hash);
-
- foreach $mailbox (@mailbox) {
- chomp($mailbox);
- add_key($ARGV[1], $cert_hash, $mailbox, $label);
- }
-}
-elsif((@ARGV == 2 or @ARGV == 3) and $ARGV[0] eq "verify") {
- verify_cert($ARGV[1], $ARGV[2]);
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "remove") {
- remove_pair($ARGV[1]);
-}
-elsif(@ARGV == 2 and $ARGV[0] eq "add_root") {
- add_root_cert($ARGV[1]);
-}
-else {
- usage;
- exit(1);
-}
-
-exit(0);
-
-
-
-
-
-############## sub-routines ########################
-
-sub usage () {
- print <<EOF;
-
-Usage: smime_keys <operation> [file(s) | keyID [file(s)]]
-
- with operation being one of:
-
- init : no files needed, inits directory structure.
-
- list : lists the certificates stored in database.
- label : keyID required. changes/removes/adds label.
- remove : keyID required.
- verify : 1=keyID and optionally 2=CRL
- Verifies the certificate chain, and optionally wether
- this certificate is included in supplied CRL (PEM format).
- Note: to verify all certificates at the same time,
- replace keyID with "all"
-
- add_cert : certificate required.
- add_chain : three files reqd: 1=Key, 2=certificate
- plus 3=intermediate certificate(s).
- add_p12 : one file reqd. Adds keypair to database.
- file is PKCS12 (e.g. export from netscape).
- add_pem : one file reqd. Adds keypair to database.
- (file was converted from e.g. PKCS12).
-
- add_root : one file reqd. Adds PEM root certificate to the location
- specified within muttrc (smime_verify_* command)
-
-EOF
-}
-
-sub mutt_Q ($) {
- my $var = shift or die;
-
- my $cmd = "$mutt -v >/dev/null 2>/dev/null";
- system ($cmd) == 0
- or die<<EOF;
-Couldn't launch mutt. I attempted to do so by running the command "$mutt".
-If that's not the right command, you can override it by setting the
-environment variable \$MUTT_CMDLINE
-EOF
-
- $cmd = "$mutt -Q $var 2>/dev/null";
- my $answer = `$cmd`;
-
- $? and die<<EOF;
-Couldn't look up the value of the mutt variable "$var".
-You must set this in your mutt config file. See contrib/smime.rc for an example.
-EOF
-#'
-
- $answer =~ /\"(.*?)\"/ and return bsd_glob($1, GLOB_TILDE | GLOB_NOCHECK);
-
- $answer =~ /^Mutt (.*?) / and die<<EOF;
-This script requires mutt 1.5.0 or later. You are using mutt $1.
-EOF
-
- die "Value of $var is weird\n";
-}
-
-sub mycopy ($$) {
- my $source = shift or die;
- my $dest = shift or die;
-
- copy $source, $dest or die "Problem copying $source to $dest: $!\n";
-}
-
-#
-# directory setup routines
-#
-
-
-sub mkdir_recursive ($) {
- my $path = shift or die;
- my $tmp_path;
-
- for my $dir (split /\//, $path) {
- $tmp_path .= "$dir/";
-
- -d $tmp_path
- or mkdir $tmp_path, 0700
- or die "Can't mkdir $tmp_path: $!";
- }
-}
-
-sub init_paths () {
- mkdir_recursive($certificates_path);
- mkdir_recursive($private_keys_path);
-
- my $file;
-
- $file = $certificates_path . "/.index";
- -f $file or open(TMP_FILE, ">$file") and close(TMP_FILE)
- or die "Can't touch $file: $!";
-
- $file = $private_keys_path . "/.index";
- -f $file or open(TMP_FILE, ">$file") and close(TMP_FILE)
- or die "Can't touch $file: $!";
-}
-
-
-
-#
-# certificate management methods
-#
-
-sub list_certs () {
- my %keyflags = ( 'i', '(Invalid)', 'r', '(Revoked)', 'e', '(Expired)',
- 'u', '(Unverified)', 'v', '(Valid)', 't', '(Trusted)');
-
- open(INDEX, "<$certificates_path/.index") or
- die "Couldn't open $certificates_path/.index: $!";
-
- print "\n";
- while(<INDEX>) {
- my $tmp;
- my @tmp;
- my $tab = " ";
- my @fields = split;
-
- if($fields[2] eq '-') {
- print "$fields[1]: Issued for: $fields[0] $keyflags{$fields[4]}\n";
- } else {
- print "$fields[1]: Issued for: $fields[0] \"$fields[2]\" $keyflags{$fields[4]}\n";
- }
-
- my $certfile = "$certificates_path/$fields[1]";
- my $cert;
- {
- open F, $certfile or
- die "Couldn't open $certfile: $!";
- local $/;
- $cert = <F>;
- close F;
- }
-
- my $subject_in;
- my $issuer_in;
- my $date1_in;
- my $date2_in;
-
- my $format = -B $certfile ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -subject -issuer -dates -noout -in $certfile -inform $format";
- ($subject_in, $issuer_in, $date1_in, $date2_in) = `$cmd`;
- $? and print "ERROR: '$cmd' returned $?\n\n" and next;
-
-
- my @subject = split(/\//, $subject_in);
- while(@subject) {
- $tmp = shift @subject;
- ($tmp =~ /^CN\=/) and last;
- undef $tmp;
- }
- defined $tmp and @tmp = split (/\=/, $tmp) and
- print $tab."Subject: $tmp[1]\n";
-
- my @issuer = split(/\//, $issuer_in);
- while(@issuer) {
- $tmp = shift @issuer;
- ($tmp =~ /^CN\=/) and last;
- undef $tmp;
- }
- defined $tmp and @tmp = split (/\=/, $tmp) and
- print $tab."Issued by: $tmp[1]";
-
- if ( defined $date1_in and defined $date2_in ) {
- @tmp = split (/\=/, $date1_in);
- $tmp = $tmp[1];
- @tmp = split (/\=/, $date2_in);
- print $tab."Certificate is not valid before $tmp".
- $tab." or after ".$tmp[1];
- }
-
- -e "$private_keys_path/$fields[1]" and
- print "$tab - Matching private key installed -\n";
-
- $format = -B "$certificates_path/$fields[1]" ? 'DER' : 'PEM';
- $cmd = "$opensslbin x509 -purpose -noout -in $certfile -inform $format";
- my $purpose_in = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- my @purpose = split (/\n/, $purpose_in);
- print "$tab$purpose[0] (displays S/MIME options only)\n";
- while(@purpose) {
- $tmp = shift @purpose;
- ($tmp =~ /^S\/MIME/ and $tmp =~ /Yes/) or next;
- my @tmptmp = split (/:/, $tmp);
- print "$tab $tmptmp[0]\n";
- }
-
- print "\n";
- }
-
- close(INDEX);
-}
-
-
-
-sub query_label () {
- my @words;
- my $input;
-
- print "\nYou may assign a label to this key, so you don't have to remember\n";
- print "the key ID. This has to be _one_ word (no whitespaces).\n\n";
-
- print "Enter label: ";
- chomp($input = <STDIN>);
-
- my ($label, $junk) = split(/\s/, $input, 2);
-
- defined $junk
- and print "\nUsing '$label' as label; ignoring '$junk'\n";
-
- defined $label || ($label = "-");
-
- return $label;
-}
-
-
-
-sub add_entry ($$$$$) {
- my $mailbox = shift or die;
- my $hashvalue = shift or die;
- my $use_cert = shift;
- my $label = shift or die;
- my $issuer_hash = shift;
-
- my @fields;
-
- if ($use_cert) {
- open(INDEX, "+<$certificates_path/.index") or
- die "Couldn't open $certificates_path/.index: $!";
- }
- else {
- open(INDEX, "+<$private_keys_path/.index") or
- die "Couldn't open $private_keys_path/.index: $!";
- }
-
- while(<INDEX>) {
- @fields = split;
- return if ($fields[0] eq $mailbox && $fields[1] eq $hashvalue);
- }
-
- if ($use_cert) {
- print INDEX "$mailbox $hashvalue $label $issuer_hash u\n";
- }
- else {
- print INDEX "$mailbox $hashvalue $label \n";
- }
-
- close(INDEX);
-}
-
-
-sub add_certificate ($$$$;$) {
- my $filename = shift or die;
- my $hashvalue = shift or die;
- my $add_to_index = shift;
- my $label = shift or die;
- my $issuer_hash = shift;
-
- my $iter = 0;
- my @mailbox;
- my $mailbox;
-
- while(-e "$certificates_path/$$hashvalue.$iter") {
- my ($t1, $t2);
- my $format = -B $filename ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -in $filename -inform $format -fingerprint -noout";
- $t1 = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- $format = -B "$certificates_path/$$hashvalue.$iter" ? 'DER' : 'PEM';
- $cmd = "$opensslbin x509 -in $certificates_path/$$hashvalue.$iter -inform $format -fingerprint -noout";
- $t2 = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- $t1 eq $t2 and last;
-
- $iter++;
- }
- $$hashvalue .= ".$iter";
-
- if (-e "$certificates_path/$$hashvalue") {
- print "\nCertificate: $certificates_path/$$hashvalue already installed.\n";
- }
- else {
- mycopy $filename, "$certificates_path/$$hashvalue";
-
- if ($add_to_index) {
- my $format = -B $filename ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -in $filename -inform $format -email -noout";
- @mailbox = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- foreach $mailbox (@mailbox) {
- chomp($mailbox);
- add_entry($mailbox, $$hashvalue, 1, $label, $issuer_hash);
-
- print "\ncertificate $$hashvalue ($label) for $mailbox added.\n";
- }
- verify_cert($$hashvalue, undef);
- }
- else {
- print "added certificate: $certificates_path/$$hashvalue.\n";
- }
- }
-
- return @mailbox;
-}
-
-
-sub add_key ($$$$) {
- my $file = shift or die;
- my $hashvalue = shift or die;
- my $mailbox = shift or die;
- my $label = shift or die;
-
- unless (-e "$private_keys_path/$hashvalue") {
- mycopy $file, "$private_keys_path/$hashvalue";
- }
-
- add_entry($mailbox, $hashvalue, 0, $label, "");
- print "added private key: " .
- "$private_keys_path/$hashvalue for $mailbox\n";
-}
-
-
-
-
-
-
-sub parse_pem (@) {
- my $state = 0;
- my $cert_iter = 0;
- my @bag_attribs;
- my $numBags = 0;
-
- $cert_tmp_file[$cert_iter] = newfile("cert_tmp.$cert_iter","temp");
- my $cert_tmp_iter = $cert_tmp_file[$cert_iter];
- open(CERT_FILE, ">$cert_tmp_iter")
- or die "Couldn't open $cert_tmp_iter: $!";
-
- while($_ = shift(@_)) {
- if(/^Bag Attributes/) {
- $numBags++;
- $state == 0 or die("PEM-parse error at: $.");
- $state = 1;
- $bag_attribs[$cert_iter*4+1] = "";
- $bag_attribs[$cert_iter*4+2] = "";
- $bag_attribs[$cert_iter*4+3] = "";
- }
-
- ($state == 1) and /localKeyID:\s*(.*)/
- and ($bag_attribs[$cert_iter*4+1] = $1);
-
- ($state == 1) and /subject=\s*(.*)/
- and ($bag_attribs[$cert_iter*4+2] = $1);
-
- ($state == 1) and /issuer=\s*(.*)/
- and ($bag_attribs[$cert_iter*4+3] = $1);
-
- if(/^-----/) {
- if(/BEGIN/) {
- print CERT_FILE;
- $state = 2;
-
- if(/PRIVATE/) {
- $bag_attribs[$cert_iter*4] = "K";
- next;
- }
- if(/CERTIFICATE/) {
- $bag_attribs[$cert_iter*4] = "C";
- next;
- }
- die("What's this: $_");
- }
- if(/END/) {
- $state = 0;
- print CERT_FILE;
- close(CERT_FILE);
- $cert_iter++;
- $cert_tmp_file[$cert_iter] = newfile("cert_tmp.$cert_iter","temp");
- $cert_tmp_iter = $cert_tmp_file[$cert_iter];
- open(CERT_FILE, ">$cert_tmp_iter")
- or die "Couldn't open $cert_tmp_iter: $!";
- next;
- }
- }
- print CERT_FILE;
- }
- close(CERT_FILE);
-
- # I'll add support for unbagged cetificates, in case this is needed.
- $numBags == $cert_iter or
- die("Not all contents were bagged. can't continue.");
-
- return @bag_attribs;
-}
-
-
-# This requires the Bag Attributes to be set
-sub handle_pem (@) {
-
- my @pem_contents;
- my $iter=0;
- my $root_cert;
- my $key;
- my $certificate;
- my $intermediate;
- my @mailbox;
- my $mailbox;
-
- @pem_contents = &parse_pem(@_);
-
- # private key and certificate use the same 'localKeyID'
- while($iter <= $#pem_contents / 4) {
- if($pem_contents[$iter * 4] eq "K") {
- $key = $iter;
- last;
- }
- $iter++;
- }
- ($iter > $#pem_contents / 2) and die("Couldn't find private key!");
-
- $pem_contents[($key * 4)+1] or die("Attribute 'localKeyID' wasn't set.");
-
- $iter = 0;
- while($iter <= $#pem_contents / 4) {
- $iter == $key and ($iter++) and next;
- if($pem_contents[($iter * 4)+1] eq $pem_contents[($key * 4)+1]) {
- $certificate = $iter;
- last;
- }
- $iter++;
- }
- ($iter > $#pem_contents / 4) and die("Couldn't find matching certificate!");
-
- my $tmp_key = newfile("tmp_key","temp");
- mycopy $cert_tmp_file[$key], $tmp_key;
- my $tmp_certificate = newfile("tmp_certificate","temp");
- mycopy $cert_tmp_file[$certificate], $tmp_certificate;
-
- # root certificate is self signed
- $iter = 0;
-
- while($iter <= $#pem_contents / 4) {
- if ($iter == $key or $iter == $certificate) {
- $iter++;
- next;
- }
-
- if($pem_contents[($iter * 4)+2] eq $pem_contents[($iter * 4)+3]) {
- $root_cert = $iter;
- last;
- }
- $iter++;
- }
- if ($iter > $#pem_contents / 4) {
- print "Couldn't identify root certificate!\n";
- $root_cert = -1;
- }
-
- # what's left are intermediate certificates.
- $iter = 0;
-
- # needs to be set, so we can check it later
- $intermediate = $root_cert;
- my $tmp_issuer_cert = newfile("tmp_issuer_cert","temp");
- while($iter <= $#pem_contents / 4) {
- if ($iter == $key or $iter == $certificate or $iter == $root_cert) {
- $iter++;
- next;
- }
-
- open (IC, ">> $tmp_issuer_cert") or die "can't open $tmp_issuer_cert: $?";
- my $cert_tmp_iter = $cert_tmp_file[$iter];
- open (CERT, "< $cert_tmp_iter") or die "can't open $cert_tmp_iter: $?";
- print IC while (<CERT>);
- close IC;
- close CERT;
-
- # although there may be many, just need to know if there was any
- $intermediate = $iter;
-
- $iter++;
- }
-
- # no intermediate certificates ? use root-cert instead (if that was found...)
- if($intermediate == $root_cert) {
- if ($root_cert == -1) {
- die("No root and no intermediate certificates. Can't continue.");
- }
- mycopy $cert_tmp_file[$root_cert], $tmp_issuer_cert;
- }
-
- my $label = query_label;
-
- my $format = -B $tmp_certificate ? 'DER' : 'PEM';
- my $cmd = "$opensslbin x509 -noout -hash -in $tmp_certificate -inform $format";
- my $cert_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- $format = -B $tmp_issuer_cert ? 'DER' : 'PEM';
- $cmd = "$opensslbin x509 -noout -hash -in $tmp_issuer_cert -inform $format";
- my $issuer_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- chomp($cert_hash); chomp($issuer_hash);
-
- # Note: $cert_hash will be changed to reflect the correct filename
- # within add_cert() ONLY, so these _have_ to get called first..
- add_certificate($tmp_issuer_cert, \$issuer_hash, 0, $label);
- @mailbox = &add_certificate("$tmp_certificate", \$cert_hash, 1, $label, $issuer_hash);
- foreach $mailbox (@mailbox) {
- chomp($mailbox);
- add_key($tmp_key, $cert_hash, $mailbox, $label);
- }
-}
-
-
-
-
-
-
-sub modify_entry ($$$;$ ) {
- my $op = shift or die;
- my $hashvalue = shift or die;
- my $use_cert = shift;
- my $crl;
- my $label;
- my $path;
- my @fields;
-
- $op eq 'L' and ($label = shift or die);
- $op eq 'V' and ($crl = shift);
-
-
- if ($use_cert) {
- $path = $certificates_path;
- }
- else {
- $path = $private_keys_path;
- }
-
- open(INDEX, "<$path/.index") or
- die "Couldn't open $path/.index: $!";
- my $newindex = newfile("$path/.index.tmp");
- open(NEW_INDEX, ">$newindex") or
- die "Couldn't create $newindex: $!";
-
- while(<INDEX>) {
- @fields = split;
- if($fields[1] eq $hashvalue or $hashvalue eq 'all') {
- $op eq 'R' and next;
- print NEW_INDEX "$fields[0] $fields[1]";
- if($op eq 'L') {
- if($use_cert) {
- print NEW_INDEX " $label $fields[3] $fields[4]";
- }
- else {
- print NEW_INDEX " $label";
- }
- }
- if ($op eq 'V') {
- print "\n==> about to verify certificate of $fields[0]\n";
- my $flag = &do_verify($fields[1], $fields[3], $crl);
- print NEW_INDEX " $fields[2] $fields[3] $flag";
- }
- print NEW_INDEX "\n";
- next;
- }
- print NEW_INDEX;
- }
- close(INDEX);
- close(NEW_INDEX);
-
- rename $newindex, "$path/.index"
- or die "Couldn't rename $newindex to $path/.index: $!\n";
-
- print "\n";
-}
-
-
-
-
-sub remove_pair ($ ) {
- my $keyid = shift or die;
-
- if (-e "$certificates_path/$keyid") {
- unlink "$certificates_path/$keyid";
- modify_entry('R', $keyid, 1);
- print "Removed certificate $keyid.\n";
- }
- else {
- die "No such certificate: $keyid";
- }
-
- if (-e "$private_keys_path/$keyid") {
- unlink "$private_keys_path/$keyid";
- modify_entry('R', $keyid, 0);
- print "Removed private key $keyid.\n";
- }
-}
-
-
-
-sub change_label ($ ) {
- my $keyid = shift or die;
-
- my $label = query_label;
-
- if (-e "$certificates_path/$keyid") {
- modify_entry('L', $keyid, 1, $label);
- print "Changed label for certificate $keyid.\n";
- }
- else {
- die "No such certificate: $keyid";
- }
-
- if (-e "$private_keys_path/$keyid") {
- modify_entry('L', $keyid, 0, $label);
- print "Changed label for private key $keyid.\n";
- }
-
-}
-
-
-
-
-sub verify_cert ($$) {
- my $keyid = shift or die;
- my $crl = shift;
-
- -e "$certificates_path/$keyid" or $keyid eq 'all'
- or die "No such certificate: $keyid";
- modify_entry('V', $keyid, 1, $crl);
-}
-
-
-
-
-sub do_verify($$$) {
-
- my $cert = shift or die;
- my $issuerid = shift or die;
- my $crl = shift;
-
- my $result = 'i';
- my $trust_q;
- my $issuer_path;
- my $cert_path = "$certificates_path/$cert";
-
- if($issuerid eq '?') {
- $issuer_path = "$certificates_path/$cert";
- } else {
- $issuer_path = "$certificates_path/$issuerid";
- }
-
- my $cmd = "$opensslbin verify $root_certs_switch $root_certs_path -purpose smimesign -purpose smimeencrypt -untrusted $issuer_path $cert_path";
- my $output = `$cmd`;
- $? and die "'$cmd' returned $?";
- chop $output;
- print "\n$output\n";
-
- ($output =~ /OK/) and ($result = 'v');
-
- $result eq 'i' and return $result;
-
- my $format = -B $cert_path ? 'DER' : 'PEM';
- $cmd = "$opensslbin x509 -dates -serial -noout -in $cert_path -inform $format";
- (my $date1_in, my $date2_in, my $serial_in) = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- if ( defined $date1_in and defined $date2_in ) {
- my @tmp = split (/\=/, $date1_in);
- my $tmp = $tmp[1];
- @tmp = split (/\=/, $date2_in);
- my %months = ('Jan', '00', 'Feb', '01', 'Mar', '02', 'Apr', '03',
- 'May', '04', 'Jun', '05', 'Jul', '06', 'Aug', '07',
- 'Sep', '08', 'Oct', '09', 'Nov', '10', 'Dec', '11');
-
- my @fields =
- $tmp =~ /(\w+)\s*(\d+)\s*(\d+):(\d+):(\d+)\s*(\d+)\s*GMT/;
-
- $#fields != 5 and print "Expiration Date: Parse Error : $tmp\n\n" or
- timegm($fields[4], $fields[3], $fields[2], $fields[1],
- $months{$fields[0]}, $fields[5]) > time and $result = 'e';
- $result eq 'e' and print "Certificate is not yet valid.\n" and return $result;
-
- @fields =
- $tmp[1] =~ /(\w+)\s*(\d+)\s*(\d+):(\d+):(\d+)\s*(\d+)\s*GMT/;
-
- $#fields != 5 and print "Expiration Date: Parse Error : $tmp[1]\n\n" or
- timegm($fields[4], $fields[3], $fields[2], $fields[1],
- $months{$fields[0]}, $fields[5]) < time and $result = 'e';
- $result eq 'e' and print "Certificate has expired.\n" and return $result;
-
- }
-
- if ( defined $crl ) {
- my @serial = split (/\=/, $serial_in);
- my $cmd = "$opensslbin crl -text -noout -in $crl | grep -A1 $serial[1]";
- (my $l1, my $l2) = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- if ( defined $l2 ) {
- my @revoke_date = split (/:\s/, $l2);
- print "FAILURE: Certificate $cert has been revoked on $revoke_date[1]\n";
- $result = 'r';
- }
- }
- print "\n";
-
- if ($result eq 'v') {
- return 't';
- }
-
- return $result;
-}
-
-
-
-sub add_root_cert ($) {
- my $root_cert = shift or die;
-
- my $format = -B $root_cert ? 'DER' : 'PEM';
-
- my $cmd = "$opensslbin x509 -noout -hash -in $root_cert -inform $format";
- my $root_hash = `$cmd`;
- $? and die "'$cmd' returned $?";
-
- if (-d $root_certs_path) {
- -e "$root_certs_path/$root_hash" or
- mycopy $root_cert, "$root_certs_path/$root_hash";
- }
- else {
- open(ROOT_CERTS, ">>$root_certs_path") or
- die ("Couldn't open $root_certs_path for writing");
-
- $cmd = "$opensslbin x509 -in $root_cert -inform $format -fingerprint -noout";
- $? and die "'$cmd' returned $?";
- chomp(my $md5fp = `$cmd`);
-
- $cmd = "$opensslbin x509 -in $root_cert -inform $format -text -noout";
- $? and die "'$cmd' returned $?";
- my @cert_text = `$cmd`;
-
- print "Enter a label, name or description for this certificate: ";
- my $input = <STDIN>;
-
- my $line = "=======================================\n";
- print ROOT_CERTS "\n$input$line$md5fp\nPEM-Data:\n";
-
- $cmd = "$opensslbin x509 -in $root_cert -inform $format";
- my $cert = `$cmd`;
- $? and die "'$cmd' returned $?";
- print ROOT_CERTS $cert;
- print ROOT_CERTS @cert_text;
- close (ROOT_CERTS);
- }
-
-}
-
-sub newfile ($;$$) {
- # returns a file name which does not exist for tmp file creation
- my $filename = shift;
- my $option = shift;
- $option = "notemp" if (not defined($option));
- if (! $tmpdir and $option eq "temp") {
- $tmpdir = mutt_Q 'tmpdir';
- $tmpdir = newfile("$tmpdir/smime");
- mkdir $tmpdir, 0700 || die "Can't create $tmpdir: $!\n";
- }
- $filename = "$tmpdir/$filename" if ($option eq "temp");
- my $newfilename = $filename;
- my $count = 0;
- while (-e $newfilename) {
- $newfilename = "$filename.$count";
- $count++;
- }
- unshift(@tempfiles,$newfilename);
- return $newfilename;
-}
-
-
-END {
- # remove all our temporary files in the end:
- for (@tempfiles){
- if (-f) {
- unlink;
- } elsif (-d) {
- rmdir;
- }
- }
-}
+++ /dev/null
-timestamp for config.h
projects / software / mutt-debian.git / commitdiff